DSN, problems after add-on ARBCI1 - ARBCI2 upgrade

[FerrariT]

Dear Experts.

We upgrade Add-on from ARBCI1 Level 0011 to 0015 and from ARBCI2 Level 0009 to 0011.

During processes re-testing, we found some errors.

Errors probably related to “External Format Conversion”.

The result is these two problems:

• No more than 10 PO items can be sent to Supplier. If more than 10, all the PO items greater than 10 will have the item code (material number) corrupted on iDoc (Segment E1EDP19 001, field IDTNR)
• The PO received by Supplier has the PO number with leading zeros and the side effect is that ReceiptRequest will not match the po item. In past PO number was (as desired) without leading zeros.

Can someone help us ?

We have also open an SAP OSS Note/Incident without any reply from 25th of November

May we need to open a Critical Incidents also on Connect ?

Any suggestion to solve the problem ?

Best Regards.

Thanks.

[Prem_Tracz]

Hello Terry,

Both issues sound like defects although you may need to clarify what do you mean by 'material number getting corrupted on IDOC'.

For ReceiptRequest issue, I would only see if external format conversion step in SPRO actually impacts how the PO number is send.

Sorry for facing these issues, hope you will get a resolution quickly.

Regards,

[FerrariT]

Hi.

For "material number getting corrupted on IDOC", this is the example.

PO item 90 with material XXXX, item 100 material YYYY.

Idoc segment for item 90 is material XXXX.

Idoc segment for item 100 is material XXXX (instead YYYY)

For "ReceiptRequest ", this is the example.

PO number 12345 sent to AN with 0000012345 (insted 12345 as in past)

ReceiptRequest sent to AN with reference to 12345 (as in past).

I'm pretty sure the root cause is the new wrong management on output conversion.

Best Regrds.