Hello all

This one is driving me crazy.

I have a demo where I submit an EDI doc (X12 4010 850) to webMethods B2B SaaS from Postman. The demo was originally creating in my wM B2B tenant version 11.2.10.0.735, June 2025 (this is the version before IWHI came out).

In wM B2B I have the doc type defined and active. I have two partners, with identifiers and are Active. I have a processing rule that has criteria on my specific sending and receiving partners AND the doc type (X12 4010 850). In my rule I call a wM Integration flow service. I also have a TPA for my sender/receiver combo. 

When I submit the EDI 850 payload to my wM B2B tenant, the processing works. I see the following:

Notice the original 850 arrives as EDINT, then it gets put into X12 4010 850, and the other related transactions are shown. On the line that says COPYSENT, that is where my wM Integration Flow Service is called.

This is all good.

Now that I have access to the new IWHI environment, I exported my solution from wM B2B and Integration (v11.2.*) into the new tenant. For wM B2B I just used the Asset Movement Export/Import. Seemed to work fine except I had some issues with the X12 4010 850 doc not being there, but if I tried to create it or import it, then the UI complained and said it already existed. I reached out to R&D and they asked me to import with overwrite. I did that and the doc appeared. Remember this is in the new environment. I then verified and tweaked my other demo assets (Partners, rules, TPAs) since I had to adjust the partner identities due to other profiles using the same identities.

I then tweaked my Postman settings and Body/payload to use the new identities in the HTTP header and the EDI payload. I added my authentication and sent the request. It comes back as 200, but when I look at my transaction results, for some reason it is not going from EDIINT to X12 4010 850, and I do not see the other related transactions in the transaction UI. As shown above. I see the EDIINT business document, and that is the only transaction. Nothing related. You can see below my multiple tests, after trying various setting changes. Notice the User status of UNMATCHED below? F

Summary of the issue

• What I'm doing: Sending an AS2 message from Postman into IBM webMethods B2B SaaS. The payload is a valid X12 4010 850 (ISA11=U, ISA12=00401, GS08=004010). Partner IDs line up using ZZ (Mutually Defined):

  • Sender = 567893456 (AS2-From + ISA06/GS02 + partner identities)

  • Receiver = 321654987 (AS2-To + ISA08/GS03 + partner identities)

• What should happen (works in my older SaaS environment from July 2025):
  The inbound EDIINT transport doc is promoted to a child X12 4010 850 business document; my X12 rule then runs (user status like COPYSENT).

• What actually happens now (new SaaS release):
  Only the EDIINT document is persisted and routed (user status UNMATCHED). No child X12 4010 850 is created, so X12 rules never trigger.

Evidence (new environment)

• In the transaction's Content for the payload part (ediintdata):
  Content-Type: application/edi-x12; charset=us-ascii, Content-Transfer-Encoding: binary, body starts with ISA* (no BOM/whitespace).

• Business document "X12 4010 850" is Active.

• Processing rules: I even tried a catch-all inbound rule for X12 4010 850 (no partner filters, highest priority, Stop processing=On). It never fires because the X12 doc never gets created.

• Partners: Sender and receiver both have EDIINT AS2 and Mutually Defined (ZZ) identities matching the ISA/GS and AS2 headers.

What I tried (summary)

• Ensured single Content-Type: application/edi-x12; charset=us-ascii (removed any text/plain).

• Switched Postman to Body: Binary upload (US-ASCII, no BOM).

• Tested both segment terminators ~ and ! with consistent ISA control counts.

• Aligned AS2-From/To + ISA/GS + partner identities (ZZ/ZZ), mirroring the working July setup.

• Verified that the payload starts with ISA* at byte 0 and part headers show application/edi-x12.

• Created a catch-all X12 rule above default; also tested with more specific rules.

• Considered TPAs; left default because TPAs apply after recognition and shouldn't block promotion.

Ask / suspected cause

Given that the AS2 part is correctly typed and the payload is clean, yet no X12 child document is created (while the same pattern worked in July), this looks like a promotion regression in the new wM B2B SaaS release. I'm looking for guidance or confirmation:

• Is there any new setting or known issue that would block EDIINT → X12 promotion under these conditions?

I'm happy to provide a failing Transaction ID, the exact .edi file, and screenshots of ediintdata headers and rule order.

Note: I attached two EDI payloads I have tried. Both are essentially the same, except one file uses ~ terminator and the other !

Any thoughts or assistance is appreciated.

Attachment(s)

EDIX12_4010_850_sample1.edi   630 B 1 version

EDIX12_4010_850_sample1 diff terminator.edi   630 B 1 version

This has been solved.

For some reason in my new IWHI wM B2B environment the processing rules for EDIINT were not enabled. Special thanks to IBM support.

I had to activate the following rules:

Now after sending my EDI to wM B2B from Postman, I see the transactions I expected.

So be aware that if you start working with a brand new IWHI environment, some of the things you expect to be enabled, may not be :)