Product: Transaction Manager (formerly vSync)

Business System: GP Enterprise

Article Link: http://help.truecommerce.com/en/articles/4737737-transaction-manager-vsync-odlf-uploading-in-gp

Overview

An ODLF is a document used to be able to export files out of GP Enterprise. This file is formatted to reference and pull data from Microsoft SQL tables. This is translated into an XML format to be consumed by your EDI translator, Transaction Manager. Any document exported out of GP Enterprise requires an ODLF.

Creating ODLFs

During your implementation process, the assigned Integration Specialist will either build or provide an existing ODLF based on the requirements set in the Trading Partner EDI mapping specifications. A 'black hole' ODLF can be provided to pull as much relevant data from GP as possible. For Transaction Manager integrations, this requires coordination with the Integration Specialist to make updates as needed using our Integration Mapping Tool.

Uploading ODLFs

810 (Invoice)

855 (Purchase Order Acknowledgement)

856 (Advance Shipment Notice)


810

Back to top

1. From TrueCommerce Main, go to Customer (Cross-Reference) > Documents.

2. Unlock Code - A Microsoft Integration Specialist will use the unlocker tool to generate this code.

3. Application Code - This needs to match the TM > Trading Partner > Translation > Partner Setup.

4. EDI Status Flag - Set to Production (not used for Transaction Manager integrations).

5. Document Type - Standard 810 (Invoice) or 880 (Grocery Product Invoice) depend on the ODLF used.

6. EDI Version - This needs to match the ODLF (for Transaction Manager integrations, default to 004030).

7. Inv. Mapping Path - Select the ODLF from the path where the ODLFs are saved.

a. Folder - Selecting the file from file browser.

b. Paper w/ pencil - Opens up notepad and allows you to edit the ODLF.

c. 2 paper icon - This will copy the ODLF on SQL and saves it to the path.

d. Save - Saves the ODLF to SQL. ***Please note: If you add a new ODLF, you will need to hit Save or you will get error on the export. ***

8. Multiple ODLFs - These are used if certain scenarios need to go to a different application code or use a separate ODLF.

855

Back to top

1. From TrueCommerce Main, go to Customer (Cross-Reference) > Advanced > PO Ack ODLF.

2. Unlock Code - A Microsoft Integration Specialist will use the unlocker tool to generate this code.

3. Application Code - This needs to match the TM > Trading Partner > Translation > Partner Setup.

4. EDI Status Flag - Set to Production (not used for Transaction Manager integrations).

5. EDI Version - This needs to match the ODLF (for Transaction Manager integrations, default to 004010).

6. Mapping Path - Select the ODLF from the path where the ODLFs are saved.

a. Folder - Selecting the file from file browser.

b. Paper w/ pencil - Opens up notepad and allows you to edit the ODLF.

c. Save - Saves the ODLF to SQL. ***Please note: If you add a new ODLF, you will need to hit Save or you will get error on the export. ***

7. Search type - Select any from the drop down.

8. Search value - Put A in the search value.

856

Back to top

1. From TrueCommerce Main, go to Customer (Cross-Reference) >

2. Unlock Code - A Microsoft Integration Specialist will use the unlocker tool to generate this code.

3. Application Code - This needs to match the TM > Trading Partner > Translation > Partner Setup.

4. EDI Status Flag - Set to Production (not used for Transaction Manager integrations).

5. Container Type - Set to CTN (carton) or PLT (pallet).

6. EDI Version - This needs to match the ODLF (for TM the version should be 004030).

7. ASN Mapping Path - Select the ODLF from the path where the ODLFs are saved.

a. Folder - Selecting the file from file browser.

b. Paper w/ pencil - Opens up notepad and allows you to edit the ODLF.

c. 2 paper icon - This will copy the ODLF on SQL and saves it to the path.

d. Save - Saves the ODLF to SQL. ***Please note: If you add a new ODLF, you will need to hit Save or you will get error on the export. ***

8. Label Layout Path 1/ Label Layout Path 2 - This is used for when customer is printing from GP/ using Label Matrix * see label matrix tab for more info.

9. Multiple ODLFs - These are used if certain scenarios need to go to a different application code or use a separate ODLF.

Did this answer your question?