Inbound Translation Object Dialog Box
The Inbound Translation Objects dialog box is used to specify which translation objects will be used to process the data defined by this relationship.
The following lists the inbound translation levels (from the lowest level up):
| Translation Level | Description |
|---|---|
| Document | Validate the document against the specified translation object to verify if the document is compliant with the standard and translate from EDI to print or application format. |
| Transaction | Remove the EDI-specific enveloping around a single document. |
| Group | Remove the EDI-specific enveloping around a set of related transactions (the transactions do not have to be the same type). |
| Interchange | Remove the EDI-specific enveloping around groups destined for the same trading partner. |
See the IBM® Sterling Gentran:Server® for Microsoft Windows Communications User Guide for more information.
The following illustrates the Inbound Translation Object dialog box with the Advanced options displayed:

The following describes the parts of the Inbound Translation Object dialog box.
| Part | Function |
|---|---|
| Select Translation Objects Notes:
|
|
| Turn Around/Auto | Displays all turnaround document options. When
a document is received, the turnaround document created is the natural
response document that contains as many elements from the received
document as possible. Note: Select the Auto check box if you want the
defined turnaround process to be automatic. If the Auto box is not
selected, the received document will remain in the In Documents until
it is selected for processing.
|
| Export File/Auto | Displays all registered Export translation objects
relative to the Standard, Version, Transaction Set and Release defined
by this relationship. This allows you to specify that when an EDI
document is received, it will be exported into an output file. Notes::
|
| Displays all print translation objects on the system for the Standard, Version, Transaction Set, and Release defined by the relationship. The selected translation object will be used to print documents received from this partner. | |
| Export File Name | Specify the name of the file to be created or
appended to as a result of performing an export operation. This file
name can contain a mix of alphanumeric characters and formatting characters,
which are replaced by the translator with the runtime value they represent. Notes:
Formatting characters supported:
Note:
The runtime file name is generated once per export. The following is an example of a runtime file name using formatting characters:
|
| Export to Mailbox | |
| Export to Mailbox | Invokes the "Export to Mailbox" function, which
delivers the output of an inbound translation to the Mailbox Server
Manager. This allows the Mailbox Server Manager to act as a message
broker responsible for delivering the data to its final destination. Note: If
you specified the Export File Name, it is still valid and will become
the Attachment Filename. Formatting characters are still valid for
the filename and could cause multiple attachments to be created if
document key is used. For example, if the following filename is used:
a new attachment is created for each document because the document key creates a unique name for each document processed. To set up an export to a mailbox, you must complete the following components on the Inbound Translation Objects dialog box:
|
| Use Partner Default Mailbox and E-mail Address | Specify if the output of the inbound translation is exported to the default mailbox and e-mail address configured for this partner. |
| Recipient Mailbox/ New Mailbox | Select the mailbox to which the output of an inbound
translation is delivered. Optionally, click New Mailbox to display the Create New Mailbox wizard, which allows you to create a new mailbox. |
| Recipient E-mail Address/ Edit Mailbox | Specify the e-mail address to which the output
of an inbound translation is delivered. Optionally, click Edit Mailbox to display the Create New Mailbox wizard, which allows you to edit the mailbox. |
| Content Type/SubType | Specify the content type/sub type of the message containing the output of the inbound translation. |
| Application ID | Specify the application identifier that indicates the destination of the documents. |
| Application Alias Value | Specify criteria for this relationship definition
that is used during the application import function. Example: The application contains data that can generate either an invoice or a credit memo. Use one relationship definition for invoices and another for credit memos. There is a box in the application that defines whether this is an invoice or a credit memo. The box will display CREDIT if a credit memo is created and INVOICE if an invoice is created. Type CREDIT in the Application Alias Value for the relationship defining the credit memo and type INVOICE for the invoice. Note: This box
is only used if you receive translation objects that are defined to
use the Application Alias Value.
|
| Additional Translation Objects | |
| Import | Select other translation objects associated with
the relationship, which gives you the capability to change the system
behavior at the transaction and document translation level. This allows
you to use translation objects that are as partner-specific as required
and/or perform as many functions as required. Note: You must select
a translation object from the Import list if you have created a specific
import translation object for this relationship and if you want to
change the way the system behaves for this partner relationship. Import
translation objects may not be appropriate for an Inbound Relationship.
|
| Data Entry | Select other translation objects associated with
the relationship, which gives you the capability to change the system
behavior at the transaction and document translation level. This allows
you to use translation objects that are as partner-specific as required
and/or perform as many functions as required. Note: You must select
a translation object from the Data Entry list if you have created
a specific data entry translation object for this relationship and
if you want to change the way the system behaves for this partner
relationship (e.g., if you want to change the formatted view of Inbound
data).
|
| Transaction | Select other translation objects associated with
the relationship, which gives you the capability to change the system
behavior at the transaction and document translation level. This allows
you to use translation objects that are as partner-specific as required
and/or perform as many functions as required. Note: You must select
a translation object from the Transaction list if you have created
a specific Transaction Break translation object for this relationship
and if you want to change the way the system behaves for this partner
relationship.
|
| Acknowledge | Select other translation objects associated with
the relationship, which gives you the capability to change the system
behavior at the transaction and document translation level. This allows
you to use translation objects that are as partner-specific as required
and/or perform as many functions as required. Note: You must select
a translation object from the Acknowledge list if you have created
a specific translation object for this relationship and if you want
to change the way the system behaves for this partner relationship.
When the system reconciles an acknowledgement, it maps the acknowledgement to an internal file and then processes it. If you need the system to process acknowledgements differently, you should select an additional translation object from the Acknowledge list. If the transaction set is an acknowledgement and you choose an Acknowledge additional translation object, the system will use the additional translation object in place of the export translation object for acknowledgement reconciliation. |