B2B Addon - XML to X12 conversion issue - missing separators

[rene_press]

Dear SAP Community,

we are implementing an EDI scenario, of type IDOC -> SAP PO -> ANSI X12.

On receiver Side, there is an AS2_Receiver Channel. This channel also performes the XML to X12 conversion by accessing the X12ConverterModule. The field separator is "^" (Caret).

Here is the issue: Fields, that are not mapped in graphical Message Mapping (MM) are supposed to cause an additional "^" delimiter as a placeholder in the X12 message. But this is not the case. If a target field contains a value, it's displayed properly, but if its not present in the XML, no "^" is inserted. As a result, all the fields to the right are shifted and the resulting X12 message is useless!

EXAMPLE:

This is the target Message in ESR, segment ITD from ANSI Invoice (810):

... this is the expected x12 message (generated manually with XML to X12 converter tool in B2B Cockpit):

... but this is the actual resulting X12 message:

--> As you can see in the above examples, the "^" separators from the not-mapped fields are missing. The validation on receiver side fails.

Has anyone seen this kind of error before and knows how to solve this??

Thanks and best regards

René Preß

[HansHougaard]

Facing the same issue.
Customer is asking for this UNB record - UNB+UNOC:3:::7 .......
This means a value of "7" mapped to C_S001/D_0076, while D_0080 and D_0133 should be empty.
This is impossible to achieve.
Fun fact: when running the conversion through the B2B cockpit -> Edifact -> Converter XML to Edifact it works just fine and it doesn't remove the separators. Issue seems to be with the GenericConverterModule used on the receiver com. channel.
We're on PIB2BTOOLKIT 1000.2.0.1.23.20201120084000
Will raise an OSS with SAP.

[rene_press]

Yes that's correct, the B2B converter keeps the separators. Our version is 1000.2.0.1.17.20200907124100 - so it still seems to be unresolved.

OSS Ticket: Good point, let me know the SAP response!

Best regards

René

[former_member686806]

I am facing the same issue, that too only in production which is quite strange, I fixed the issue by mapping constant value as a workaround, but any solution from B2BADDON end,

[rportillo16]

Hello Rene,

Similar issue, I solved it correcting the Interchange version or version release has a wrong character or in other correcting the sender ID or and the receiver ID in order to the match with the outbound. agreement.

Regards,

Roberto Portillo

[former_member630846]

Hey Shab,

Were you able to resolve this issue? Do we have any X12ConverterModule instead of adding "mapWithDefault" for the individual fields.

Please let me know.

[rene_press]

by now there is an update available for the B2BAddon (release 2.0) maybe that solved the issue.

But i didnt try it yet with this or in any other scenrio.

[rene_press]

Hello Shab,

it couldn't be solved the way it was supposed to work. It only worked with adding the "map with default" function in every target field, using an empty string as default. This way, the target field will always be generated with no value as default, and the field seperator appears.

Best regards

René Preß

[former_member621415]

Hi Rene,

I am also facing exactly same issue so I wanted your help and to check with you if you are able to resolve this issue and if yes, how did you found out the issue?

Regards,

Sh