Outbound Translation Process

The following diagram illustrates the outbound translation process:

Outbound Translation Process
Table 1. Outbound Translation Process
Stage Description
1 Use one of the following three processes to initiate an outbound translation:
  • Import a file through the process control system using a timed or polled session. This writes all valid documents to the database with a compliant status and moves the documents to Out Documents. Invalid documents are marked with a non-compliant status and are moved to ?Out Documents.
  • Import an application file. Documents that you import manually are located in the Workspace.
  • Use the Document Editor to enter documents (if there is an appropriate data entry translation object registered with Sterling Gentran:Server®). These documents are located in the Workspace.
2 If you import a file, the translator checks the import definitions from the system configuration to match the file name with a system import translation object.
3 The translator uses the system import translation object to determine which trading relationship (established in Partner Editor) corresponds to each document in the application file, so the system knows which import map to use to process the document.
4 The translator ascertains which import translation object is specified in the trading relationship.
5 The translator uses the import translation object to compliance check the document. If the document is compliant (valid), it is marked OK. If the document is not compliant (invalid), it is marked NotOK.
6 If there is another document remaining in the import file, the translator repeats steps 3 - 5 until all documents are processed.
7 If you manually import a file through the EDI Manager or use the Document Editor, you need to post the compliant document to Out Documents.Once documents are located in Out Documents, they can be sent using the process control system or by using the EDI Manager transmit option.