Configuring the sending of functional acknowledgment

A functional acknowledgment can be set up for the receiver of an EDI message in Transformation Services. The functional acknowledgment is configured in a similar way for ASC X12 and UN-EDIFACT messages. In this example of a functional acknowledgment, an ASC X12 message is used. In such a business process, Transformation Services receives an ASC X12 EDI message such as ASC X12 830 Planning Schedule with Release Capability Planning Schedule, ASC X12 850 Purchase Order, or ASC X12 862 Shipping Schedule. Transformation Services extracts the header and the trailer from the source message. Sender and receiver are interchanged. The extracted header and trailer of the source message are used to create a new outbound EDI message with message type ASC X12 997 Functional Acknowledgment. This functional acknowledgment message is sent to the sender of the original inbound source message.

To configure a functional acknowledgment for an incoming ASC X12 message:

Select Transformation Services > Configuration > Transformation Rules.
Click the Drill down button of an incoming ASC X12 message for the specific Partner ID of the trading partner.
In the detail view of the Transformation Rules page, click Edit.
Select the Acknowledgment check box for the message and click Save to save the changes.
Select Transformation Services > Configuration > Partner IDs.
To add a partner ID setup, click Create and specify this information:

Partner ID

Select the partner ID from the drop-down list. The partner ID must be the same ID that is used for the incoming ASC X12 EDI message.

Message Type

Select the message type ASC X12 997 Functional Acknowledgment from the drop-down list.

Message Direction

Select Outbound from the drop-down list.

EXS Partner ID

Select the partner ID that is used by Exchange Services to access a defined message exchange configuration from the drop-down list. The partner ID must identify the same communication partner that is used for the incoming ASC X12 EDI message.

Sender ID / Receiver ID

Specify the sender ID and the receiver ID. Sender ID and receiver ID must be the same identification numbers that are used for the incoming ASC X12 EDI message.

Additional Sender ID / Additional Receiver ID

Specify the additional sender ID and the additional receiver ID. Additional sender ID and additional receiver ID must be the same identification numbers that are used for the incoming ASC X12 EDI message.

ISA/UNB Qualifier for Sender / ISA/UNB Qualifier for Receiver

Specify the code qualifiers that are used to qualify the sender ID and the receiver ID of the ISA/UNB segments in the message. Normally, the qualifiers should be the same that are used for the incoming ASC X12 EDI message. To verify the qualifiers, check the guideline of your OEM.
Specify the other field information as required and click Save to save the new partner ID setup.
Select Transformation Services > Configuration > Transformation Rules.
To add a transformation rule, click Create and specify this information:

Message Direction

Select Outbound from the drop-down list.

Partner ID

Select the partner ID from the drop-down list. The partner ID must be the same ID that is used for the incoming ASC X12 EDI message.

Message Type

Select the message type ASC X12 997 Functional Acknowledgment from the drop-down list.

Style Sheet Name

Select the style sheet that is used for the transformation from the drop-down list. If there are no special requirements from the trading partner, you can use the generic ASC X12 style sheet Acknowledge_A9201_997.
Specify the other field information as required and click Save to save the new transformation rule.
When an ASC X12 EDI message comes in, the ASC X12 997 Functional Acknowledgment message is generated after all master data are retrieved.