| # To load initial system data When you use Object Data Management for the first time, you must load certain initial system data to the relevant ODM tables. This system data is supplied as part of the LN installation kit. To load the initial system data, take the following steps: Copy the system dump files from the Setup_data directory on the installation media to a temporary directory on the LN system host. If File Transfer Protocol (FTP) transfers the files, you must set the Mode field to Binary. On the Object Data Management menu, double-click ODM Configuration > Import > System > Data > Import System Data. The Import System Data (dmsys2210m000) session starts: Enter the path of the directory on the LN system host to which you copied the dump files. Before you click Continue, however, you must perform one last step. In the Import Options area, click either of the following: Append Data and Keep Matching Records: Enables you to retain the matching records. Append Data and Replace Matching Records: Enables you to replace the matching records. Click Continue. Note To import the data into the relevant tables correctly, you must be an LN super user. To import and export system data Object Data Management provides functionality to import and export ODM system data. If you want the system to run in a test environment, and later to import the data to the production environment, you can export the system data. Export data from all the tables listed in the System Table List (dmsys2201m000) session. This session initially lists the basic system tables, such as those tables that are associated with masks, actions, families, and so on. However, if required, you can add tables to this list, depending on the authorizations. Alternatively, you can transfer table contents with the use of the standard LN facilities. Note The sequence numbers assigned to the tables in the table list determine the order in which data is imported from dump files. If you want to modify the list of tables, you must make sure not to cause reference conflicts. To maintain the list of tables to be exported To maintain the list of tables to be exported, on the Object Data Management menu, double-click ODM Configuration > Export / Import System Data > System Table List. The System Table List (dmsys2201m000) session appears, as shown in the following figure, which includes a list of all the tables that will be exported: To add a system table to the list, take the following steps: In the System Table List (dmsys2201m000) session, on the File menu, click New. A new record appears, with the sequence number filled in automatically. Only authorized users can add/modify or delete the System Tables list. The actions for this authorization are defined in ODM Actions. Modify the sequence number, if required. Either type in the package, module, and table number directly, or use the browse arrow from the Table Number field to select the required table from the Table Definitions (ttadv4520m000) session. Click Find to locate the dm package, and the module to which the table belongs. Enter the condition to limit the records to be exported, if required. To export system data To export system data, take the following steps: On the Object Data Management menu, double-click ODM Configuration > Export/Import System Data > Export System Data.. The Export System Data (dmsys2205m000) session appears: Enter the path of the directory on the LN system host in which you want to create the dump files and click Create Dump. To place the Thin_ODM.jar file From LN release onwards, users need not install ODM Client on their desktops. ODM Client needs to be installed only on the remote machine if work areas or vault areas exist on the remote machine. As a result, in these types of cases, in which the client installation on the user's desktop is not required, you must place the thin_odm.jar file on the ERP server in the `$BSE/java` directory. This jar file is part of the server installations and will be available along with the other LN Server Installations DVD. The services of jar file is used when the user wants to perform file operations on files that exist in a remote work area or vault area or while submitting or releasing files to a vault area. |