ECC - XI - SRM : Scheduling Agreement Failing

[former_member189558]

Hi,

We are sending scheduling agreement from ECC-MM 6.0 to SRM-SUS 5.5 via PI7.

On the inbound side of SRM it is throwing the following error:

Error during XML => ABAP conversion (; error ID: ; ( )) PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Request Message; error ID: CX_ST_REF_ACCESS; (/1SAI/TXS00000000000000000003 XML Bytepos.: 2123 XML Path: ns0:PurchaseOrderRequest(1)PurchaseOrder(2)Item(10)PurchasingContractReference(4)ItemID(2) Error Text: Error accessing the ref. node 'ITEM_ID')) Error during XML => ABAP conversion (Request Message; error ID: CX_ST_REF_ACCESS; (/1SAI/TXS00000000000000000003 XML Bytepos.: 2123 XML Path: ns0:PurchaseOrderRequest(1)PurchaseOrder(2)Item(10)PurchasingContractReference(4)ItemID(2) Error Text: Error accessing the ref. node 'ITEM_ID')) Error accessing the ref. node 'ITEM_ID'

In XI:

Outbound Interface: DELINS.DELFOR02

Inbound Interface: PurchaseOrderRequest_In | http://sap.com/xi/SRM/SupplierEnablement/Global (BuSysContext "SUS_S40CLNT300")

Interface Mapping: MM2SUSDeliverySchedule | http://sap.com/xi/SRM/SupplierEnablement/Global (LOCINSUS 100)

Please help us on this.

[Former Member · Accepted solution]

Sometimes there could be problem in the pre-delivered content but the error is being trapped in the SUS ssytem. If you are using pre-delivered content then make sure you have relevant/latest(relevant for ECC-MM 6.0 to SRM-SUS 5.5 via PI7) SWCV/patch imported in XI. Also check for any OSS notes available for this scenario.

We had a issue with the pre-delivered MM-XI-SUS content, but for a different scenario. The messages were being stuck in SUS queues with an error thrown from the ABAP proxy because of datatype mismatch for the Purchase Order number and a fix was made in XI for MM-SUS mapping through the note 754356.

[former_member189558 · Accepted solution]

Hello Anand,

Yes.. in fact we found in SAP document that SA with PO reference is presently not supported... so I reactivated the reference segement and it started working...

Cheers,

Himadri

[former_member189558]

Mentioned on my last post

[Former Member]

Hi,

Looks like there is some processing being done on the field 'ITEM_ID' in the SRM system.

Recheck, if the incoming message has this field and if the value within this field is correct.

Regards,

Smitha.

Message was edited by:

Smitha Rao

[Former Member]

Hi,

after sending scheduling agreement from ECC-MM 6.0 tp PI.

Go to PI Tcode : SXMB_MONI , double click the message , expand inbound message and double click the payload and test this payload in your mapping...whether your mapping has defined correctly or not.

Regards,

Venu.

[former_member189558]

Hi Venu,

You did not get it...

From XI side it is Ok .. message passed successfully to SRM ...

On the SRM side in SXMB_Moni .. it is giving the error while calling the standard inbound proxy.

Any idea...

Cheers,

Himadri