The Partner Manager does support generating a 997 acknowledgment for each functional group, but there is an important condition: the functional group type must be different.
If there are multiple GS segments with the same functional group type (for example, all GS segments being of type PO within the same ST segment), then the system generates only a single acknowledgment for that group. This means that even if multiple purchase order groups are included, they are consolidated into a single 997.
On the other hand, if the incoming file contains functional groups of different types (for example, a PO with transaction set 850 and an SM with transaction set 204), the Partner Manager generates a separate 997 acknowledgment for each type. In this case, each functional group type is recognized independently, and the acknowledgments are issued accordingly.
This behavior ensures that acknowledgments correctly reflect the structure of the EDI file while avoiding unnecessary duplication when multiple groups of the same type are present.
Sample of multiple 997 acknowledgements:
To ensure proper acknowledgment processing, it is important that the functional group types (GS) in the X12 file are configured as distinct values for each functional group.
The Partner Manager generates separate 997 acknowledgments only when the functional group types are different. If multiple GS segments share the same type (for example, all GS segments being PO/850), they are consolidated, and only a single 997 acknowledgment is created.
To meet the acknowledgment requirements, review the structure and configuration of your X12 file and confirm that:
By setting up the functional groups with distinct GS values, you can ensure that Partner Manager generates the appropriate number of acknowledgments in line with your trading partner agreements.
005167240

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.