Exchange Schemes (daxch0101s000)

	Exchange Schemes (daxch0101s000) Use this session to maintain exchange schemes. Tip Use multilevel exchange schemes to avoid copying a complete exchange scheme structure. To create an exchange scheme, use the General tab to define general data. Define the location of the exchange programs and physical ASCII files in Paths. Specify the details of the ASCII files in the ASCII File Configuration. Use the Special tab to define additional data, if required. Enter the name of the parent exchange scheme if you are using a multilevel exchange scheme Define the subdirectories that can be overruled in Overrule Subdirectories. Define additional details in Text, Multi-Byte, Float and Log settings. Note If you want to add more information, click the Text button on the toolbar to start the text editor. Related topics Introduction to the Exchange module Introduction to the master data business object To use multilevel exchange schemes Relation between logical ASCII files and physical ASCII files To store exchange programs and files Differences and resemblances between regular and non-regular exchanges Exchange Scheme The exchange scheme code. Description Enter a description for the exchange scheme. Owner With the Owner field, you can group and sort exchange schemes in a company. The default value is your LN user code. This way you can use this field to specify the LN user who owns the exchange scheme. However, the value you define does not have to be an LN user. You can use any name to group the exchange schemes, such as 'actual' for schemes that are actually in use, and 'test' for schemes being tested. Or 'financials' for schemes transferring financial data and 'logistics' for schemes transferring logistical data. In the Exchange Schemes (daxch0501m000) overview session select View > Sort by > Exchange Scheme by Owner. Exchange Scheme Text If this check box is selected, additional information is available for this exchange scheme. The information is generated in the text editor. Click Text to start the text editor. Exchange Programs Define the path where the exchange programs are stored. Points of attention You can define a path here once and LN will automatically use it on the fields where the exchange program is required. You do not have to enter the full path again. The path must always be an absolute path, starting from the root directory. If this field is changed you do not have to generate the import program or the export program again. The character # in the path is converted to the current company number during compilation and during execution. Environment variables must be placed between {}. For example, `${HOME}/exchange`. In these situations, the specified path must be within `${BSE}/appdata`: The environment runs within the cloud and Extensibility is enabled. The environment runs within a tenant in a multi-tenant environment. Errors / Log Files Define the path where the error log files are stored. Points of attention You can define a path here once and LN will automatically use it on the fields where the exchange program is required. You do not have to enter the full path again. The path must always be an absolute path, starting from the root directory. If this field is changed you do not have to generate the import program or the export program again. The character # in the path is converted to the current company number during compilation and during execution. Environment variables must be placed between {}. For example, `${HOME}/exchange`. In these situations, the specified path must be within `${BSE}/appdata`: The environment runs within the cloud and Extensibility is enabled. The environment runs within a tenant in a multi-tenant environment. Related topics To use conditions in the exchange module ASCII Files Define the path where the sequential ASCII files are stored. These files are also referred to as physical ASCII files. Points of attention You can define a path here once and LN will automatically use it on the fields where the exchange program is required. You do not have to enter the full path again. The path must always be an absolute path, starting from the root directory. If this field is changed you do not have to generate the import program or the export program again. The character # in the path is converted to the current company number during compilation and during execution. Environment variables must be placed between {}. For example, `${HOME}/exchange`. In these situations, the specified path must be within `${BSE}/appdata`: The environment runs within the cloud and Extensibility is enabled. The environment runs within a tenant in a multi-tenant environment. Related topics Relation between logical ASCII files and physical ASCII files Definition Files Define the path where the data definition file of the sequential ASCII files is stored. Points of attention You can define a path here once and LN will automatically use it on the fields where the exchange program is required. You do not have to enter the full path again. The path must always be an absolute path, starting from the root directory. If this field is changed you do not have to generate the import program or the export program again. The character # in the path is converted to the current company number during compilation and during execution. Environment variables must be placed between {}. For example, `${HOME}/exchange`. In these situations, the specified path must be within `${BSE}/appdata`: The environment runs within the cloud and Extensibility is enabled. The environment runs within a tenant in a multi-tenant environment. If you leave this field empty you must enter the full pathname in the definition file field in the ASCII Files (daxch0102m000) session. If you enter the path of the definition file, you only have to define the file code of the definition file in the ASCII Files (daxch0102m000) session. This path is always an absolute path, starting from the root directory. The character # in a relative path is converted to the company number of the current company to make it absolute. Based on Audit If this check box is selected, the data is imported or exported from audit files, instead of LN tables. This option is useful in a multisite environment. This option only shows that an audit is carried out on one or more tables that are imported or exported. There is no check built into the system. The audit procedure can be overruled for batches in an exchange scheme in the Batches (daxch0104m000) session. For example, the audit is overruled if a batch contains tables that do not use the audit procedure. Note If this field is changed, you do not have to generate the import program or the export program again. Related topics To use audits in the exchange module Based on Indicators If this check box is selected, the first field of each record indicates if the record in the ASCII file must be added, modified, or deleted. For example: i = insert or add d = delete u = update or modify n = new value If the Based on Audit check box is selected, the Based on Indicators check box is automatically selected. The Default Date Format field is automatically set to Date Number. Control Character If this check box is selected, a <CTRL> character is used to separate the ASCII file fields with variable lengths in an ASCII file. For example, if the letter A is defined in the following field as the separator character, it reads <CTRL>A in the ASCII file. If the ASCII file field has a fixed length, this check box is not selected. Note If this field is changed, you do not have to generate the import program or the export program again. Separator Character Enter a character to separate the ASCII file fields with variable lengths in an ASCII file. Allowed values Letters in the range [A-Z] if the Control Character check box is selected. Characters like \, ], ^, and _ For example, if the letter A is defined in the following field as the separator character, it reads <CTRL>A in the ASCII file. Note If this field is changed, you do not have to generate the import program or the export program again. Do NOT use characters that are used in the data fields that have to be exchanged. Enclosing Character Define a character to enclose strings in an ASCII file; for example, " ". Example An ASCII file for currency data has a field separator character \| and an enclosing character ". The record looks as: "USD"\|"American Dollars"\|"US$"\|1.95 The currency code is USD, the description is American Dollars, the currency symbol is US$, and the conversion rate is 1.95. Note Only use enclosing characters if separator characters are used. It makes no difference if an ASCII file with a fixed record length is used. If this field is changed, you do not have to generate the import program or the export program again. Default Date Format The Date Format is defined per field in the ASCII file that is used in an exchange scheme. If no date format is defined for an ASCII file field, the Default Date Format will be used. If the ASCII file field is created using LN audit files, the Default Date Format will be set to `Date Number`. Note If this field is changed, you do not have to generate the import program or the export program again. Parent Exchange Scheme Enter the code of the exchange scheme that is used as the parent in a multilevel exchange scheme. A parent exchange scheme is useful if you want to make small changes to an existing exchange scheme. You only copy those parts of the scheme that you want to change. The batches and table relations that you do not copy are inherited from the parent exchange scheme. Copy Files before Regular Import from Specify the common directory from which you want to import your exchange scheme’s regular import data. Leave this field empty if you don't want to use a common directory. If you want to import the data from an external application, enter the directory used by that application. If you define a common directory from which to copy your Exchange Scheme’s regular import files: LN copies the files from the common directory to the subdirectory of the current import run before the actual import is done. LN only copies files with a file name used in one of you regular import’s active table relations. If any files already exist in the subdirectory of the regular import run with the same file name as the files you want to import, the files you import overwrite the existing files. Related topics Advanced file handling using common directories Copy Files after Regular Export to Specify a common directory to which LN copies the files of an exchange scheme’s regular export run. Leave this field empty if you don't want to use a common directory. If you want to export the data to an external application, enter the directory used by that application. If you define a common directory for your Exchange scheme’s regular exports: LN copies the files from the subdirectory of the current export run to the common directory after the actual export is done. LN overwrites existing files from your exchange scheme’s previous regular export run, but only in the common directory, not in the regular export directory. LN only overwrites files whose file name occurs in the regular export’s active table relation. This enables you to copy more than one exchange schemes regular export files to the same common directory, so that another LN exchange scheme or external application can combine files of more than one Exchange Scheme. If an error in the regular export results in the failure to create a file, the file in the common directory from the regular export’s previous export run is still removed. This prevents the re-importation of the same (old) file from the common directory that was not replaced by the failed file. The error log shows the file creation failed, in which case you must run a non-regular export (and a corresponding non regular import) to exchange the data in the failed file. The files of your Exchange Scheme’s regular export are also exported and stored in a subdirectory (identified by the run number) of the directory you specify in the Overrule Regular Export Subdirectory field of the Exchange Schemes (daxch0501m000) details session. LN does not overwrite the files in the Regular Export Directory. You can only remove the files explicitly via the Remove ASCII Files (daxch2202m000) session, which ensures the safety of your regular export data. You can use the Regular Export Directory files to check previous regular export runs. Related topics Advanced file handling using common directories Overrule Regular Import Subdirectory Enter the subdirectory that must overrule the default subdirectory for a data import on a regular basis. This enables you to use the same directories for import and export, so that you can directly import the exported ASCII files without moving them to another directory if the run numbers of the import and export run are identical. The ASCII files are placed in the default subdirectory during a data export on a regular basis (<exchange scheme>.<run number>.i). If the overruling subdirectory already contains files, the ASCII file is placed in the default directory <export subdirectory>.<run number>. The subdirectory is located in the ASCII file directory. Exchange reads this parameter at runtime. Note The subdirectory can only be overruled if the ASCII file name specified in the Table Relations (Import) (daxch0121s000) session does not contain an absolute path. If this field is changed, you do not have to generate the import program or the export program again. Overrule Regular Export Subdirectory Enter the subdirectory that must overrule the default subdirectory for a data export on a regular basis. This enables you to use the same directories for import and export, so that you can directly import the exported ASCII files without moving them to another directory if the run numbers of the import and export run are identical. The ASCII files are placed in the default subdirectory during a data export on a regular basis (<exchange scheme>.<run number>.i). If the overruling subdirectory already contains files, the ASCII file is placed in the default directory <export subdirectory>.<run number>. The subdirectory is located in the ASCII file directory. Exchange reads this parameter at runtime. Note The subdirectory can only be overruled if the ASCII file name specified in the Table Relations (Import) (daxch0121s000) session does not contain an absolute path. If this field is changed, you do not have to generate the import program or the export program again. Increase Text Number for Text Tables If this check box is selected, the text numbers increase when text tables are imported. If this check box is cleared, the text number is not changed. Existing texts are overwritten if this is allowed in the table and field relations. Thus, tables are handled in the same way as other tables. Note If this field is changed, you must generate the import program or the export program again. Perform Multi-Byte Conversions If this check box is selected, table fields of the Multibyte string type are converted to the local character type. The conversion is done directly after reading the characters in the ASCII file during a data import. When you export, a conversion is done just before the value is written to the ASCII file. Note Errors during multibyte conversions are not logged. If this field is changed, you must generate the import program or the export program again. If you select this check box, the UTF8 Conversions check box is automatically cleared. UTF8 Conversions If this check box is selected, table fields of the Multi-Byte string type are converted to UTF8 format. The conversion is done directly after reading the characters in the ASCII file during a data import. When you export, a conversion is done just before the value is written to the ASCII file. Note Errors during UTF8 conversions are not logged. If this field is changed, you must generate the import program or the export program again. If you select this check box, the Perform Multi-Byte Conversions check box is automatically cleared. Change Float and Double Format If this check box is selected, the values of the db.float and db.double table fields are converted. Use this option if you have problems exporting data based on an audit procedure in a client/server environment that combines a non-Intel application server with an Intel database server. Note If this field is changed, you do not have to generate the import program or the export program again. Do Additional Logging This option is currently not used.