Generating the Runtime

The business object implementation for LN is generated by right-clicking the BII and selecting Implementation > Generate Infor LN Implementation.

When generating, the LN Implementation Generator may report violations of LN-specific constraints. Constraint violations are likely to result in errors when generating or errors at runtime when invoking the business object in LN.

The following happens in LN:

Two libraries are generated. The library code is derived from the BII’s implementation identifier.
A lookup entry is created, which is used at runtime to route the invocation of a business object method to the library implementing the public interface for that business object.

Note: If related software projects and activities are defined for your interface project, the libraries are generated in these activities. For details, see "Creating an interface project" in the LN Studio online help.

Compilation errors in the generated libraries are reported. Usually, these compilation errors will only occur for the hooks you included in your BII, or in case of constraint violations or problems reported by the LN Studio. However, not all problems are reported directly to the user, in some cases the compilation error is the only feedback you get on a problem.

Note:

If a BOR-based business object already exists in a previous version and you want to generate from the LN Studio, the following libraries must be duplicated to the new version and set on expired:

This is not done automatically! For example, if the implementation identifier is ppmmm999 then the following libraries will be regenerated in the new version:

ppmmmbl999sb00
ppmmmbl999st00

The following libraries will not be used anymore:

ppmmmbl999sc00,
ppmmmbl999sf00
ppmmmbl999sm00

They must be set on expired in the new version.