Cancellation from SUS hangs in XI interface

[Former Member]

Hi All,

We are implementing the SRM-SUS scenario on our SRM 5.0 system.

The PO is transferred from SRM to SUS. In SUS the vendor creates a purchase

order response which is transferred to SRM.

Then the vendor confirms the PO and after approval in SRM, the goods

receipt is created in SRM. So far, so good.

Now the vendor wants to cancel his confirmation. When transferring this

confirmation from SUS to SRM, the system throws an exception in the XI interface.The message says:

StandardMessageFault

An error occurred within an XI interface: Exception

occurredA:BBP_PD:002 -Interface data contains errors A:BBP_PD:002 -

Interface data contains errors Programm:

CX_BBP_BD_ERROR===============CP; Include:

CX_BBP_BD_ERROR===============CM002; Line: 57

I implemented note 1056865, but this did not solve our problem.

Can anyone help me on this issue.

Thanks,

Martijn

[Former Member]

Hi

<b>Please see the following SAP OSSNotes, which will definitely help.</b>

Note 922190 - SRM-SUS: Confirmation response can not be identified in SUS

<u>Other related OSS Notes -></u>

Note 1026638 - GR Output Integration with MM-SUS Scenario for R/3 <= 47-

Note 1051424 - Incorrect display of SUS Confirmations status

Note 1026326 - Cannot accept GR with role SAP_EC_SUS_INVOICER

Hope this will help.

Regards

- Atul

[Former Member]

Hi Atul,

We had already applied Note 922190 to our system.

Unfortunately without result.

Our problem occurs when in SUS the vendor cancels the confirmation.

When transferring this cancellation, the document does not arrive in SRM, because of the interface error.

Regards,

Martijn

[Former Member]

Hi

<u>By any chance, have you looked at the following SAP OSS Notes as well -></u>

<u>Note 890260 Contact person not replicated from SUS to EBP

Note 793118 Date check in XML inbox less strict

Note 744635 POR XML inbound, problem with leading zeros in PO number</u>

Hope this will help.

Regards

- Atul

[Former Member]

Hi Atul,

Thanks for your response.

Unfortunately these notes are not applicable, as we are on

SP7 of SRM SERVER 5.5.

Regards,

Martijn