After the Import

The Import from BOR does not import all aspects for a business object as modeled in the BOR. This is caused by the differences between the model as used in the BOR and the model as used in the LN Studio.

Basically the following aspects are imported:

• The complete BID including the used data types.
• The tables used in the business object as defined in the BOR.
• The BII, including the attribute implementations for the attributes and the attribute implementations that map directly to table columns. For calculated attribute implementations, the mapping is set to ‘not applicable’.

Some examples of limitations:

• Complex mappings (using calculations) are not imported. Also ‘used attributes’ are not defined. Attribute implementations for calculated attributes will get type ‘notApplicable’.
• A number of constructions that were allowed in the BOR cannot be used in the LN Studio. For example, business objects can be modeled without a component, the name of the main component can differ from the business object name, and the structure of components and attributes can be different per method.
• Usually a BID is independent of the implementation. So for example, the data types used in the BID do not have a native data type specified. The data types used in the BII must have a native data type. When using the Import from BOR
• The imported definition does not always follow the (naming) conventions that are used when defining a business interface in the LN Studio from scratch.

Consequently, after importing you must adapt the BID as needed, complete the BII, and solve problems (warnings or errors) as reported.