| Import Data Dictionary (ttiex1285m000) |  |
| use.session.to import the dictionary data and software components from the dumps created by the Export Data Dictionary (ttiex1280m000) session. Using this session is useful, e.g. when You want to load components, that were exported from a design VRC, into a "live" package VRC. Components that were delivered to a customer, must be imported into a package VRC on the customer's system. To import software components: Enter the path where the dump(s) are stored. Enter the path where the software components must be installed. This path is only used if no path has been defined in the Directories of Software Components (ttadv1115m000) session. Specify import options For example: specify whether existing components can be overwritten and whether the dumps must be removed after installation. Click Import to start the import process. Note After importing software components in a package VRC, you must make sure that the VRC's runtime data dictionary is updated. Depending on the type of software components imported, run the following sessions: Create Runtime Data Dictionary (ttadv5210m000) Compile Program Scripts / Libraries (ttadv2230m000) Compile Reports (ttadv3240m000) Create Runtime Data Dictionary (Forms and Menus) (ttadv5214m000) The table definitions and domains generated by the Create Runtime Data Dictionary (ttadv5210m000) session are used by the other sessions. Therefore this session must be executed first. Related topics To use a details session
Fields | Description
Path Sequential Dumps | The path where the dumps, created by the Export Data Dictionary (ttiex1280m000) session, are stored.
Path Runtime Dictionary | The path where the software components, such as forms, objects, or menus, will be installed. This path is only used if no path has been defined in the Directories of Software Components (ttadv1115m000) session. The default path is ${BSE}/application.
Overwrite | An indication whether components must be overwritten, if they already exist in the target package VRC.
Overwrite Alignment | Indicates whether alignment and lengths of domains may be overwritten. Alignment/length of domains may be changed in session Modify Codes Alignment (ttadv4107m000). For example: The "tcitem" (Item Code) domain is currently right-aligned. The dump files that are imported contain a customized "tcitem" domain, which is left-aligned. When this check box is selected, the existing "tcitem" domain will be overwritten by the customized domain. When this check box is cleared, the customized "tcitem" domain will not be imported. When you import domains with a changed alignment or a changed length, you must reconfigure tables in the Convert to Runtime Data Dictionary (ttadv5215m000) or the Create Runtime Data Dictionary (ttadv5210m000) session.
Delete dumps after installation | If this check box is selected, Tools deletes the dumps that contain the dictionary data and software components to be imported, after the installation. If you clear this check box, you can reuse the dump files after installation. If you don't need the dumps anymore, you can remove them via the operating system.
Write software components in other Package VRC | If this check box is selected, you can specify the package VRC into which the software components will be imported. If this check box is cleared, the components are imported into a VRC with the same code as the VRC from which they were exported. If such a VRC does not exist in the target environment, a new VRC is generated first, and the components are imported into that new VRC. For example: the dumpfiles contain software components that were exported from the "tc B61O a dsgn" VRC on a development server. The dumpfiles must be installed in an ERP LN environment on another server. This environment does not contain a "tc B61O a dsgn" VRC. If you select this check box, you can specify an existing "tc" VRC into which the components will be imported. If you clear this check box, a new "tc B61O a dsgn" VRC is generated and the components are imported into that VRC. Since this VRC is new, it is not linked to any package combination. So, before you can run the new software, you must include the VRC in the derivation path of a package combination.
Version | The version of the package VRC into which the components are imported.
Release | The release of the package VRC into which the components are imported.
Customer | The customer code of the package VRC into which the components are imported.