Defining Interchange-Level Sender/Receiver Pair Information

Editing and Deleting Interchange-Level Sender/Receiver Pair Information

When you are using non-standard processing, Module for EDI uses the sender and receiver identified on the group envelope header to retrieve the Trading Networks profiles for the sender and receiver and to obtain a partner-specific EDITPA for the sender/receiver pair, if one exists.

The group envelope header in a EDI document contains only the value for the sender and receiver without the corresponding EDI ID qualifier code. For example, it might contain the D-U-N-S number for the sender (186704136), but not the EDI ID qualifier (01) that indicates that the value is a D-U-N-S number. Both the EDI ID qualifier and the value for the partner are required for Module for EDI and for Trading Networks to obtain the correct profiles and EDITPA to process the document.

You define interchange-level sender/receiver pair information to provide the EDI ID qualifiers for the group level senders and receivers. Using the WmEDIforTN home page you define the EDI ID qualifier to use for the group sender and group receiver based on the interchange sender/receiver pair. In other words, when an EDI document has a specific interchange sender/receiver pair, you specify the group EDI ID qualifiers that you want Module for EDI and Trading Networks to use for the group header sender and receiver.

Additionally, when you define the interchange-level sender/receiver pair information, you can specify information that services you create to form outbound EDI documents can use. Specifically, you can define the information to form the interchange headers for outbound EDI documents.

Module for EDI stores the interchange-level sender/receiver pair information that you define in the EDIEnvelope table, which is a Module for EDI-specific table in the Trading Networks database.

To define interchange-level sender/receiver pair information, perform the following procedure for each interchange-level sender/receiver pair that you expect in the EDI documents that you want Module for EDI to process.

Tip:
If you want to define information for an interchange sender/receiver pair that is similar to a pair you have already defined, you can copy the information for the existing pair and modify it. For instructions, see Editing and Deleting Interchange-Level Sender/Receiver Pair Information.

To define information for an interchange-level sender/receiver pair

1. Open Integration Server Administrator if it is not already open.

2. In the Solutions menu of the navigation panel, click EDI. Integration Server Administrator opens a new browser window to display the Module for EDI home page.

3. From the Module for EDI home page, in the Partner Set Up menu of the navigation panel, click Manage Interchange Info.

4. Click Add Interchange Information.

5. In the ID Qualifiers section of the screen, specify the following to identify a specific interchange sender/receiver pair:

For this ID Qualifiers field...	Specify...
Sender ID	The sender ID for the interchange-level sender. For example, if the sender is identified with a D-U-N-S number in the interchange header, specify the sender's D-U-N-S number.
Sender Qualifier	The EDI ID qualifier that corresponds to the sender ID. For example, 01 for a D-U-N-S number.
Receiver ID	The receiver ID for the interchange-level receiver.
Receiver Qualifier	The EDI ID qualifier that corresponds to the receiver ID.

6. In the Envelope Information section of the screen, specify the production mode of the documents being exchanged between the trading partners. Select Production, Testing, or Custom.

7. In the Inbound Information section of the screen, specify the following information that the Module for EDI uses when processing an inbound EDI document:

For this Inbound Information field...	Specify...
Create Doc	Whether you want Module for EDI to save the interchange document to the Trading Networks database when processing a document from the interchange sender/receiver pair defined in the ID Qualifiers section of the screen. Specify either Yes or No. Note: If you select to save the document, Trading Networks sets both the sender and receiver that it associates with the saved documents as Unknown. Trading Networks is unable to associate the actual sender and receiver because that would require the sender and receiver to have a profile, and when you use non-standard processing, you do not create profiles for interchange-level senders and receivers.
GS Sender Qualifier	The EDI ID qualifier that corresponds to the sender value on the group header in the document. Specify * (asterisk) if you want to use the EDI ID qualifier from the interchange header.
GS Receiver Qualifier	The EDI ID qualifier that corresponds to the receiver value on the group header in the document. Specify * (asterisk) if you want to use the EDI ID qualifier from the interchange header.

8. In the Inbound Information - Control Number Validation section of the screen, specify the following settings that Module for EDI uses when validating interchange control numbers in an inbound EDI document. For more information about how these settings are used, see Trading Networks Attributes and EDI Documents.

Note:
To set up control number validation for group control numbers, use the ControlNumberManagement EDITPA variables, which are described starting with wm.b2b.editn.TPA:EDITPA IS Document Type When Using Non-Standard Processing.

For this Inbound Control Number Validation field...	Specify...
Validate inbound envelope control numbers	Whether you want Module for EDI to verify the control numbers in the interchange header when processing a document from the interchange sender/receiver pair defined in the ID Qualifiers section of the screen. Specify either Yes or No.
Duplicate control number action	The action you want Module for EDI to take when it encounters a duplicate control number in an interchange header.
	Select...	To have Module for EDI
	Error & Continue	Module for EDI logs the error; then continues to process the EDI document that contains the invalid control number normally.
	Process Normally	Module for EDI logs a warning; then continues to process the EDI document that contains the invalid control number normally.
	Reject	Module for EDI logs the error and does not process the document normally. Module for EDI does not split the EDI document. Typically, Module for EDI splits an inbound EDI based on the EDITPA splitOption variable and sends the documents it splits out to Trading Networks for processing. However, if you select Reject, Module for EDI sends the document without splitting it to Trading Networks processing rules. Additionally, Module for EDI sets the Trading Networks custom attribute EDI Status as follows: For a duplicate control number, sets the custom attribute EDI Status to Duplicate Control Number. For an out-of-sequence control number, sets the custom attribute EDI Status to Out of Sequence Control Number. Note that this is for the Out of sequence control number action field that is described below. You can use the custom attribute EDI Status in processing rule criteria. You should create a processing rule to handle this rejected document. For information, see Defining Processing Rules to Handle Documents with Invalid Control Numbers.
Out of sequence control number action	The action you want Module for EDI to take when it encounters an out-of-sequence control number in an interchange header. Select Error & Continue, Process Normally, or Reject. For a description of these settings, see the descriptions of the settings above for Duplicate control number action. You can later force processing of the out-of-sequence document if you want. For more information, see Reprocessing Documents with Out-of-Sequence Control Numbers.

9. In the Inbound Information - FA Generation section of the screen, specify the following information that Module for EDI uses to determine whether it should automatically generate functional acknowledgments (FAs) for inbound EDI document and settings for generating the FAs. For more information about automatic FA generation, see Automatically Generating Functional Acknowledgments.

a. In the Auto Generate FA field, specify whether you want to turn automatic FA generation on as follows:

Specify...	To have Module for EDI...
On	Always automatically generate FAs.
Per Document	Automatically generate FAs based on the indicator flag in the interchange header (ISA14 ore UNB09).
Off	Never automatically generate FAs.

b. In the FA Level field, specify the level of detail that you want Module for EDI to acknowledge in the FAs that it generates as follows:

Specify...	To have Module for EDI acknowledge at the...
Default	Envelope level (group for ANSI X12 and interchange for UN/EDIFACT)
TransactionSet	Transaction set level
Segment	Segment level
Element	Element level Note: If you are generating FAs at the element level, be sure to configure the maximum number of errors to report per FA transaction. For more information, see Configuring the Maximum Number of Transaction Errors.

c. In the Process Document field, specify how you want Module for EDI to process a transaction, group, or UN/EDIFACT interchange based on its FA status. Use this field to define the FA statuses that are acceptable and unacceptable.

For acceptable FA statuses, Module for EDI processes a transaction, group, or UN/EDIFACT interchange using its normal processing. For unacceptable FA statuses, Module for EDI performs different processing.

Specify...	If you want...
All	Acceptable FA statuses: all statuses Unacceptable FA statuses: no FA statuses are unacceptable
Only Accepted	Acceptable FA statuses: Accepted Unacceptable FA statuses: Not Allowed Rejected Partially Accepted Accepted, But Errors Were Noted
Not Rejected	Acceptable FA statuses: Not Allowed Partially Accepted Accepted, But Errors Were Noted Accepted Unacceptable FA statuses: Rejected

For more information, see Defining Actions Module for EDI Takes Based on FA Status.

d. In the Generate Control Number field, specify how Module for EDI is to generate the control numbers that are used in the interchange and group headers of the FAs that are automatically generated. Select one of the following:

Specify...	To have Module for EDI...
From Inbound Document	Use the control numbers from the corresponding headers of the inbound EDI document that the FA acknowledges.
Random	Randomly generate control numbers for the interchange and group headers of the FA.
From Control Number Table	Obtain the control numbers from the EDIControlNumber table.

e. In the Syntax Error Status field, specify how you want Module for EDI to report the syntax error status for a transaction, group, or UN/EDIFACT interchange. The Module for EDI uses the syntax error status along with the logical error status and child transaction rejected status (if applicable) to determine the FA status for a transaction, group, or UN/EDIFACT interchange.

Specify...	To have Module for EDI...
Rejected	Report the syntax error status as Rejected if syntax errors are encountered. Select this option if you want to reject elements that have syntax errors.
Accepted, But Errors Were Noted	Report the syntax error status as Accepted, But Errors Were Noted if syntax errors are encountered. Select this option if you want to know whether there are syntax errors, but do not want to reject an element because of them.
Accepted	Report the syntax error status as Accepted regardless of any syntax errors that might be encountered. Select this option if you do not want to check for syntax errors.

f. In the Logical Error Status field, specify how you want Module for EDI to report the logical error status for a transaction, group, or UN/EDIFACT interchange.

Module for EDI uses the logical error status along with the syntax error status and child transaction rejected status (if applicable) to determine the FA status for a transaction, group, or UN/EDIFACT interchange.

Set the status as follows:

Specify...	To have Module for EDI report the logical errors as...
Rejected	Rejected if they are encountered. Specify this option if you want to reject elements that have logical errors.
Accepted, But Errors Were Noted	Accepted, But Errors Were Noted if they are encountered. Specify this option if you want to know whether there are logical errors, but do not want to reject an element because of them.
Accepted	Accepted regardless of any logical errors that might be encountered. Specify this option if you do not want to check for logical errors.

g. In the Child Transaction Rejected Status field, specify how you want Module for EDI to report the child transaction rejected status for a group or UN/EDIFACT interchange.

The child transaction rejected status indicates whether child elements of a group or UN/EDIFACT interchange have an FA status of "Rejected".

Specify one of the following:

Specify...	To have Module for EDI...
Rejected	Report the child transaction rejected status as: Rejected if the FA status of any of the child transactions is either Rejected or Accepted, But Errors Were Noted. Accepted if the FA statuses of all the child transactions are Accepted.
Partially Accepted	Report the child transaction rejected status as: Rejected if the FA statuses of all of the child transactions are Rejected. Partially Accepted if the FA status of at least one child transaction is Accepted, but the FA status of other child transactions are Rejected, Accepted, But Errors Were Noted, or both. Accepted, But Errors Were Noted if the FA statuses of the child transactions are Rejected, Accepted, But Errors Were Noted, or both, and no child transactions are Accepted. Accepted if the FA statuses of all the child transactions are Accepted.
Accepted, But Errors Were Noted	Report the child transaction rejected status as: Rejected if all the child transactions are Rejected. Accepted, But Errors Were Noted if the FA statuses of the child transactions are Rejected, Accepted, But Errors Were Noted, and Accepted. Accepted if the FA statuses of all the child transactions are Accepted.

10. In the Outbound Information - FA Generation section of the screen, specify the following information that Module for EDI uses to for the sender and receiver in the BizDocEnvelope that it creates for the FA. When defining a Trading Networks processing rule to deliver the FA, you use the BizDocEnvelope information when defining the processing rule criteria.

For this Outbound Information - FA Generation field...	Specify...
Sender	The trading partner that you want to identify as the sender of the FA for Trading Networks processing.
Receiver	The trading partner that you want to identify as the receiver of the FA for Trading Networks processing.
Add Group	Whether to add a group to the FA.
	Select...	To have Module for EDI...
	Yes	Add a group to the FA.
	No	Not add a group to the FA. This is the default.
Control Number With Leading Zero	Whether to pad control numbers in the FA with leading zeros.
	Yes	Pad control numbers in the FA with leading zeros.
	No	Do not pad control numbers with leading zeros.

11. In the Outbound Information - Delimiters section of the screen, specify the following information that a service you create to form outbound EDI documents can use:

For this Outbound Information - Delimiters field...	Specify...
Segment	The segment terminator for the outbound EDI document (for example, "+"). The default is the new line character.
Field	The field separator for each EDI segment (for example, !). The default is the "*" character.
SubField	The separator for composite elements (e.g, *). The default is the ":" character.
Release	The release character for the outbound EDI document (for example, "?").
Decimal	The decimal separator to use in the outbound EDI document. If you want the outbound document to use the European format, specify the "," character. For example, using the European format a number would be formatted as 100,10 (European format) instead of 100.10, as is common in the US.

12. In the Outbound Information - Envelope Information section of the screen, specify the following information that a service you create to form outbound EDI documents can use to form the interchange headers:

For this Outbound Information - Envelope Information field...	Specify...
ISA01	The value to use for the ISA01 element of an ANSI X12 interchange header in the outbound EDI document.
ISA02	The value to use for the ISA02 element of an ANSI X12 interchange header in the outbound EDI document.
ISA03	The value to use for the ISA03 element of an ANSI X12 interchange header in the outbound EDI document.
ISA04	The value to use for the ISA04 element of an ANSI X12 interchange header in the outbound EDI document.
ISA011	The value to use for the ISA11 element of an ANSI X12 interchange header in the outbound EDI document.
ISA012	The value to use for the ISA12 element of an ANSI X12 interchange header in the outbound EDI document.
ISA014	The value to use for the ISA14 element of an ANSI X12 interchange header in the outbound EDI document.
UNB01	The value to use for the UNB01 element of a UN/EDIFACT UNB header in the outbound EDI document.
UNB06	The value to use for the UNB06 element of a UN/EDIFACT UNB header in the outbound EDI document.
UNB07	The value to use for the UNB07 element of a UN/EDIFACT UNB header in the outbound EDI document.
UNB08	The value to use for the UNB08 element of a UN/EDIFACT UNB header in the outbound EDI document.
UNB09	The value to use for the UNB09 element of a UN/EDIFACT UNB header in the outbound EDI document.
UNB10	The value to use for the UNB10 element of a UN/EDIFACT UNB header in the outbound EDI document.
UNB11	The value to use for the UNB11 element of a UN/EDIFACT UNB header in the outbound EDI document.

13. Click Save Changes. Module for EDI adds the information you defined for the interchange sender/receiver pair identified in the ID Qualifiers section of the screen to the EDIEnvelope table in the Trading Networks database.