All Collections
Business System Integrations
Dynamics GP (Enterprise)
General
Dynamics GP (Enterprise) - Document Flow with Transaction Manager
Dynamics GP (Enterprise) - Document Flow with Transaction Manager

Using Dynamics GP Enterprise and Transaction Manager? Want to know how your documents get from your machine to EDI? Check this article out.

Micah A. Parker avatar
Written by Micah A. Parker
Updated over a week ago

Product: Dynamics GP (Enterprise)


The Enterprise version of Dynamics GP was built to consume a fixed-length Flat-File known as a TDF - while Transaction Manager leverages the power of node based flat files known as XML. In order for the two machines to talk, some conversion takes place which can sometimes be a little confusing.

This article will breakdown the entire process to help you understand what's happening behind the scenes.

Terminology


TDF

A fixed-length (positional) flat file used by Dynamics GP to read/write data to be communicated with external programs (Transaction Manager/Gentran)

XML

A node based flat file used by Transaction Manager to read/write data (provides the additional power of xPath)

Cloud/FTP

An online hosted storage - a simple place (usually hosted by TrueCommerce) to send files for processing

Cloud/FTP solutions are used to eliminate the need for every computer to be able to talk to each other, and instead provide a single point any computer can send their data, so that other applications (such as Dynamics GP or Transaction Manager) can read them without needing access to the same computer reducing complication

Cloud FTP Bridge

A service provided by TrueCommerce that automatically uploads/downloads file to and from the Cloud/FTP between your Server and Transaction Manager

CrazyTalk

The application that converts between your Fixed-Length files (TDF) and XML

Mapping Manager (Integrations)

A special mapping solution provided within Transaction Manager that allows the XML files to run logic to alter or map the data to X12 EDI to be sent to your Trading Partner

ODLF

An outbound-only trigger system that allows outbound documents such as Invoices, and ASNs to have their data-points configured so that you can define where in Dynamics GP the Segment/Elements pull data from

X12 EDI

The core standard used within the North American regions for sending and receiving EDI data across two partners (you and the Trading Partner) that ultimately gets sent/received by the Trading Partner.

TcNet

The TrueCommerce Network - since TrueCommerce is your VAN in this instance, we use our TcNet to pass data back and forth with your Trading Partners through this network.

Inbound Documents


An inbound document, is one that originates from your Trading Partner to be sent to you.

Trading Partner sends to Network(tcNet) → Transaction Manager → Mapping Manager/Integrations → XML (Cloud/Local) → CrazyTalk → Fixed-Length File → GP (vSync)

Whenever a Trading Partner sends you a document - it firsts gets sent from them to our network (TcNet) as raw EDI which gets received into Transaction Manager's Inbox ready to be processed.

Once it's processed - this then gets sent to the Received box of Transaction Manager, and is sent through the Integration Layer where the Mapping Manager tool will process the EDI and convert it into an XML format. Here is where we can do custom logic to your data to alter or manipulate with various logic to better suit your business needs.

Once the data converts, it's sent either to a local file location for your system to process - or it's passed to the Cloud/FTP solution hosted by TrueCommerce to be picked up

  • IF it is sent the Cloud/FTP - you'll need a program to pull that data into your server, TrueCommerce offers a solution known as Cloud FTP Bridge which can be used - this is most common solution

Once the data is received into the system, CrazyTalk will convert the XML into a fixed-length file known as a TDF for Dynamics GP to be able to understand.

Here, you'll open the vSync/TrueCommerce module inside Dynamics GP - and select "Process" to receive your document. At this point, the file is deleted and the data is imported into Dynamics GP and has been successfully received.

Outbound Documents


An outbound document - is one that is originating from you to be sent to your Trading Partner

GP (ODLF) → Fixed-Length File → CrazyTalk → XML → (Cloud/Local) → Transaction Manager (IMT) → Network(tcNet)

To send a document to a Trading Partner, you'll need to start within the vSync/TrueCommerce module inside Dynamics GP - selecting the document you wish to process, and selecting the Process button within the appropriate module to initiate

Once that initiates, the system checks the ODLF and builds the file based on the configuration set within the ODFL telling it what segment/elements to pull data into and from where within Dynamics GP

The file produce is the TDF - which gets picked up automatically by CrazyTalk and converted to an XML

IF using a Cloud/FTP solution - Cloud FTP Bridge or similar program will monitor the folder, see the XML file and upload it to your Cloud/FTP.

From here - Transaction Manager will attempt to import any file it sees whenever a user selects Import from within the Outbox which will then process the XML file through the Mapping Manager tools allowing custom logic/manipulation to proceed converting the XML into EDI

Once the Send button is selected in the Outbox, the document will be moved to the Sent folder as it goes through the network via TcNet and is finally sent to the Trading Partner

rev 8/8/22

Did this answer your question?