| Convert BOR to Runtime (tlbct1210m000) |  |
| use.session.to convert the Business Objects in the BOR to run time. Note This session is only relevant for business objects that are modeled through the Business Object Repository. External applications must be able to access the information in a Business Object and to perform particular actions, for example, an external application must be able to create a sales order or simply read information from a sales order. Which information is accessible, and which actions can be performed, is modeled in the BOR. The BOL is the run-time component that will perform the actions by exposing methods. The current session generates or regenerates the run-time components based on the modeling information in the BOR. The session performs the following actions, depending on the options you select: Create external reference tables in dictionary. Create software components: external Reference DALs, Public Layer BOL DLLs, Protected Layer BOL DLLs. Fill those BOL DLLs with the correct content, and recreate content for those components. Compile those BOL DLLs. Report progress and (error) results to the user. The session creates the following types of objects: Server – Public Methods library: These methods can be called from the outside world. These methods perform the XML handling of the incoming messages and are, therefore, set oriented. The methods use methods in the protected library to retrieve or send data. These libraries are generated completely. Server – Protected Methods library: These methods are used to perform tasks that come from the public methods or from other Business Objects. These libraries are the successor of the integration libraries. The standard methods will call DAL2 methods and handle the List and Show methods. These libraries are also generated completely. Server – Public Interface Conversion library: These hooks can be called from the outside world, where developers or customers can realize specified hooks. These libraries contain the logic of the public calculated fields, which are partly generated and partly user defined. Server – Protected Specific Methods library: These methods or hooks cannot be called from the outside world, where developers or customers can realize specified methods/hooks. These libraries do not contain standard methods. When the libraries are generated, only empty functions are created. New or existing DLLs can be called from here. Server – Protected Interface Conversion library: These methods or hooks cannot be called from the outside world. The methods contain empty functions or hooks by default. The logic of protected calculated fields must have been programmed manually. Note You can skip the generation of particular components. If a Business Object expires, the BOL components of that Business Object also expire. The session reports changes in the software components. For example, which Specific methods have been added, or which Specific methods are present but must not be present in a BOL. You can only create and change components in your current package VRC. Related topics To Model a Business Object
Fields | Description
Generate Reference Tables | If this check box is selected, reference tables are generated. Refer to the Tables (ttadv7111m000) session for more information.
Generate Public Methods | If this check box is selected, the BOL objects for the public methods are generated.
Generate Public Hooks for Interface Conversion | If this check box is selected, the BOL objects for the hooks for interface conversion in the public layer of the Business Object are generated. Note The hooks for interface conversion are only used for calculated fields.
Generate Protected Methods | If this check box is selected, the BOL objects for the protected methods are generated.
Generate Protected Specific Methods | If this check box is selected, the BOL objects for the protected specific methods are generated.
Generate Protected Hooks for Interface Conversion | If this check box is selected, the BOL objects for the hooks for interface conversion in the protected layer of the Business Object are generated. Note The hooks for interface conversion are only used for calculated fields.
Compile Scripts | If this check box is selected, the scripts are compiled.
Compile in Debug | If this check box is selected, the scripts are compiled in debug mode.
Always regenerate Scripts | If this check box is selected, the scripts are always regenerated.
Print Scripts | If this check box is selected, the scripts are printed.
Report Only Errors | If this check box is selected, only errors are reported. The results of the conversion and script regeneration and/or compilation are not printed.
Current Package Combination | A combination of several different packages with specific VRCs. A package combination represents a complete usable version of ERP LN. In the User Data (ttaad2500m000) session, each user is linked to a package combination, that determines which version of the software the user can use. In the Companies (ttaad1100m000) session, each company is linked to a package combination, to indicate which version of ERP LN is appropriate to handle the data in that company.
Package VRC | package VRC, package
Package VRC | package VRC, version
Package VRC | package VRC, release
Package VRC | package VRC, customer
Description | The description of the package.
Module | A part of a package consisting of a number of related software components, such as sessions, tables, program scripts, reports, forms and menus. For example, the General Ledger module in Financials. A module code consists of three characters. For example, the General Ledger has the code "gld".
Module | A part of a package consisting of a number of related software components, such as sessions, tables, program scripts, reports, forms and menus. For example, the General Ledger module in Financials. A module code consists of three characters. For example, the General Ledger has the code "gld".
Business Object | A Business Object is an object understandable by the business, such as a purchase order or an organizational unit. A Business Object has information stored in the Business Object attributes, such as the purchase order number or the organizational unit name. A Business Object also contains a set of actions, known as Business Object methods, that can manipulate the Business Object attributes, such as create purchase order and list organizational units. From a development perspective, a Business Object is a collection of tables and functions that manipulate these tables that are implemented simultaneously as one group during the development phase. A Business Object is identified by the combination of a package code, module code, and Business Object code.
Business Object | A Business Object is an object understandable by the business, such as a purchase order or an organizational unit. A Business Object has information stored in the Business Object attributes, such as the purchase order number or the organizational unit name. A Business Object also contains a set of actions, known as Business Object methods, that can manipulate the Business Object attributes, such as create purchase order and list organizational units. From a development perspective, a Business Object is a collection of tables and functions that manipulate these tables that are implemented simultaneously as one group during the development phase. A Business Object is identified by the combination of a package code, module code, and Business Object code.
Commands | Description
Continue | Converts the Business Objects in the selection to run time.
Change Curr. PVRC | Starts the Change Current Package VRC of User (ttadv0140s000) session.