| Import Patch (ttiex1284m000) |  |
| Use this session to import the contents of a patch file into a package VRC in your ERP LN environment. A patch is a collection of components, such as sessions, forms and program scripts. To import a patch: Enter the path of the patch file. 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. Important! Use this session only to import patches that were created in the Patch Codes (ttiex4500m000) session. Do not use this session to import patches that were created in the Product Maintenance and Control (PMC) module. To import PMC solutions, use the Install Solution/Patch (ttpmc2205s000) session. For details on PMC, refer to: PMC recipient procedure PMC distributor procedure
Fields | Description
Pathname Patch File | The path, including the filename, where the patch file is 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.
Extract Only | If this check box is selected, the components of the patch file are extracted to the folder that is specified in the Path to extract to field. The patch is not installed. Extraction is useful, if you want to check which components are included in the patch: one of the extracted files, "dump.l", contains a list of all components. The same list is also stored in the patch's content list ("<patch file name>.content" file). The content list is generated automatically when a patch is created.
Path to extract to | The folder to which the components of the patch file are extracted, when the Extract Only check box is selected. This folder contains a sub folder with the name of the package VRC from which the components were exported. This sub folder contains the following files: components: lists the names of the extracted files. dump.e: contains information on the errors that occurred. dump.l: contains a list of the software components that are in the patch. dump <abbreviation> 01.Z. This is a compressed file containing exported software components. The abbreviation consists of an alphabetic character. Various files are generated, depending on the component selection for the export process. Examples of file names are dump d 01.Z (domains), dump f 01.Z (forms) and dump s 01.Z (sources).
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 patch file after installation | If this check box is selected, Tools deletes the patch file, after the installation. If you clear this check box, you can reuse the patch file after installation. If you don't need the patch file anymore, you can remove it 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 patch file contains software components that were exported from the "tc B61O a dsgn" VRC on a development server. The patch file 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. Note This check box and the target VRC are selected automatically, if a target VRC was specified during the creation of the patch, in the Patch Codes (ttiex4500m000) session. You can not clear this check box when it was selected automatically.
Version | The version of the package VRC into which the components are imported. The VRC is selected automatically, if a target VRC was specified during the creation of the patch, in the Patch Codes (ttiex4500m000) session.
Release | The release of the package VRC into which the components are imported. The VRC is selected automatically, if a target VRC was specified during the creation of the patch, in the Patch Codes (ttiex4500m000) session.
Customer | The customer code of the package VRC into which the components are imported. The VRC is selected automatically, if a target VRC was specified during the creation of the patch, in the Patch Codes (ttiex4500m000) session.