Original Message:
Sent: Thu June 26, 2025 03:18 PM
From: Wayne Leishman
Subject: Using TPA to generate Functional acknowledgement (997) but wrong EDI version is showing in payload
I have a processing rule to handle the 850 and one below it to handle the 997.
For the 850 rule I specifically select document X12 4010 850 and for the 997 rule, I specifically select X12 4010 997.
Only for some reason the TPA generates a 997 with an incorrect payload. Here is the payload I see in the transaction monitoring:
ISA12 = 00200 → This indicates Interchange Version 2.0
This is not valid for X12 4010 documents
This version must be 00401 to match document types like X12 4010 997 in webMethods B2B
The question is: why is my 997 payload setting ISA12 to 00200 instead of 00410 ???
------------------------------
Wayne Leishman
Original Message:
Sent: Wed June 25, 2025 04:41 PM
From: engin sarlak
Subject: Using TPA to generate Functional acknowledgement (997) but wrong EDI version is showing in payload
Do you have a conflicting processing rule that has a higher order than the one you need? You can move your processing rule to the top to troubleshoot it.
------------------------------
engin sarlak
Original Message:
Sent: Wed June 25, 2025 09:29 AM
From: Wayne Leishman
Subject: Using TPA to generate Functional acknowledgement (997) but wrong EDI version is showing in payload
Thanks for the reply.
Yes, I see a 997 and the name indicates its X12 4010 997
But in my case, I am asking the Trading Partner Agreement to generate me the functional acknowledgement, and for some reason the generated payload does not conform 100% to this document type.
Could it be a configuration/setting that is setting the wrong EDI version?
I am asking IBM support so I will post the answer here.
If anyone else has ideas, theories and/or things to check, please let me know.
------------------------------
Wayne Leishman
Original Message:
Sent: Tue June 24, 2025 05:37 PM
From: Developer EDI
Subject: Using TPA to generate Functional acknowledgement (997) but wrong EDI version is showing in payload
do you see any list of document types, which has Functional Acknowledgement 997 ? check if any version mentioned for it ?
------------------------------
Developer EDI
Original Message:
Sent: Tue June 24, 2025 12:06 PM
From: Wayne Leishman
Subject: Using TPA to generate Functional acknowledgement (997) but wrong EDI version is showing in payload
Hello all
I am working on a demo in webMethods B2B (SaaS) where I send an X12 4010 850 into wM B2B using Postman. Then I have a processing rule that calls an integration flow service in wM Integration (SaaS) using an Action.
This all works fine.
But now I want to have a Functional Acknowledgement (997) be automatically generated, so I configured my Trading Partner Agreement to do this.
In the TPA I set autoGenerateFA to ON
It seems my 997 is being generated but it does not seem to be using EDI version 4010. Why do I know this? Well, if I look in the Transaction Monitoring I see the 997 but it is not logged separately. It appears as a related transaction here (last row):
Also, when I open the last highlighted entry, and look at the transaction Attributes it shows EDI version of 00200. I believe this should be 00401 ??? (that's what my research tells me anyway)
Is there something I need to set to change the EDI version on my Functional Acknowledgements? I have been looking in the TPA and various other places but I do not see how to make the EDI Version in the auto generated 997 be 00401 instead of 00200.
If anyone has any ideas, please share.
Regards
Wayne
------------------------------
Wayne Leishman
------------------------------