Unloading and Loading Trading Partner Library Data

Use Trading Partner Library Load (35.17.7) to create new trading partner and supporting document definition data based on the contents of imported source files XML files created using Trading Partner Document Unload. Each file represents a complete trading partner document.

You can select individual trading partner documents from a list, or load all the documents in a specified directory at the same time.

Optionally, you can also decide which specific components of the XML files have records created in the destination domain.

Note: This program does not check or enforce data integrity for records you choose not to import. For example, you can choose to create document definitions but not the associated transformation definition. This action does not cause the import process to generate an error message.

Use the first frame to identify the source directory for imported files, as well as the domain to which domain-specific types of records are loaded. To select all documents in the directory, leave Import set to Select All. If you want to select from a list of documents in the specified directory, set Import to Select Some to display another frame when you press Go. When you finish selecting documents, press Go.

Note: To select a single file, you can also press the up and down arrow keys with the cursor in the Import field. The system scrolls through all the documents in the specified directory. When the document you want to load displays, press Go.

Use the Components field to control which specific types records are created as a result of the load. When that field is Select All, the system loads all of the records from each selected XML file. Set the field to Select Some to display a list of available record types. Deselect any types that you do not want to load.

You can also control whether the source ID (stored in the XML file when it was created using Trading Partner Library Unload) is used as part of the new record names. If you choose to use it, you can specify whether it appears as a prefix or as a suffix.

Subsequent frames display several types of information about the document currently being loaded. You can update many of the fields as needed.

1 The system determines if cross-reference records exist for the specified target domain. You are prompted to create new cross-references if necessary. If no target domains are available, the system prompts you to select an existing eCommerce domain as the target.

2 Only when the target domain has not had eCommerce Control initialized, the next frame displays the fields from that program. You can update default values as needed; an additional field lets you specify the process log directory that is associated with the newly created EC subsystem record.

• If one of the fields includes a directory that does not exist, the system prompts you to create it. If you respond No, you can still enter the directory path and create it later in the file system.

• The system creates a sequence ID record (ordinarily defined in EC Number Range Maintenance) called eComNRM. It is assigned to all the sequence ID fields in the eCommerce Transaction Control frame.

• When you load multiple documents during a single session, this frame displays only when the first document is loaded. Control settings apply to all the documents in the target domain.

3 For outbound definitions only, the system next displays Transmission Group Maintenance fields. If necessary, you can edit them, or change the Name field to associate a different existing transmission group with the trading partner. If you update the directory path or subsystem, the system validates the new values.

4 The system then displays the trading partner ID from the load data and prompts you to change it before proceeding.

5 The error handling and sequence ID counter fields display from Trading Partner Maintenance. You can update them as required.

6 The Trading Partner Document Records frame displays. As required, select a record to update its settings, including error handling and sequence ID counters, as well as TP location cross-references. You can update a subset of the fields; for example, you can reference a different address/site combination. You can also enter e-mail addresses to receive status messages during document processing.

7 The program checks for any existing definitions that match the data being loaded and displays a list of duplicates, along with an Overwrite setting. If the trading partner definition is a duplicate, it is listed first, with Overwrite set to Yes. If you change the field to No, the system cancels the load process for this trading partner.

All other duplicate records have Overwrite set to No. For each one that you change to Yes, the system displays information about where the existing record is used. It then prompts you to rename the new record, overwrite the existing record with the new definition, or keep the existing one.

9 If the document references user-defined functions, the system compiles the code and saves the files in the function directory specified in eCommerce Control.

10 If multiple documents are selected for loading, the system repeats the load process for the next document on the list.

11 After you have completed all the documents, the system lists the files that were loaded. It also indicates whether any errors occurred. A log file called filename-import.log is created in the specified input directory.

To use this program to support bank payments in the Financials AP and AR modules, load a bank-specific file for each financial institution with which you want to exchange data. The load process creates mapping records that let the system process incoming files correctly, as well as generate outbound files that meet the requirements of the receiving bank. Additionally, it updates a set of financial setup tables that define the payment format for each bank.

Follow these steps to do the basic EDI setup needed for bank payments.

See QAD Financials User Guide for information about setting up bank payments.

Note: Unless you have experience with EDI eCommerce implementations, accept all other default values.

3 If not already defined, set up cross-reference between the target eCommerce processing domain and the application domain.

4 For documents that the bank sends you, such as AR bank statements, specify the inbound directory where the system looks for files to process in eCommerce Control.

5 For documents that you send to the bank, such as AP payment instructions, specify in the Transmission Group frame the directory where the system creates exported files.

Note: The default Transmission Group name matches the Trading Partner ID and also maps to the bank format name.

Use Trading Partner Library Unload (35.17.8) to create XML files containing document definition data. You can control which domains, trading partners, and trading partner documents are included in the exported files. The system creates one XML file for each document.

Note: This program does not check or enforce data integrity. For example, you can choose to export document definitions but not the associated transformation definition.

Use the first frame to select the documents to write to XML files. The system provides three levels of granularity (domain, trading partner, trading partner document). You can either have the system export all the records, or manually select the records from a list by setting the associated field to Select Some. On each level, when you choose to select records manually, you can specify filter criteria to limit the items that are selected by default when the list is displayed.

From the selection list, use the space bar to toggle the Export field between Yes and No in the character UI. In the QAD .NET UI, use the check box to select records. When you finish selecting records at each level, press Go or click Next to move to the next selection field.

You can also specify which prefix the system adds to the exported XML files. When Use TP As Source Domain is Yes, the file name is in the form domain name-trading partner ID-document ID.xml. When the field is No, you can add your own prefix in the Source ID field; this prefix replaces the domain name.

The program creates an activity log for each document in the specified dump directory. It shows the document definitions that were unloaded, a list of any non-QAD functions required to support transformation, and any error messages that were generated during processing.

Additionally, if transformation processing calls for user-defined functions, the system attempts to find the program files in the Function Directory specified in eCommerce Control. If it finds the files, it includes the source code in the XML file. The functions can then be created during the load process.