Possible version conflict, sending purchase order to SUS in MM-SUS scenario

[Former Member]

We are currently trying to get the MM-SUS scenario working. In this

scenario, we create a purchase order in the ERP/MM system. The

purchase order is then transferred into SUS via XI/PI.

After creating a purchase order in the MM system, the purchase order

reaches the SUS system, but then errors-out in the SUS system upon

posting. The specific error is paraphrased as follows:

No interface action for sender or receiver found (from Trace)

PARSE_APPLICATION_DATA

CX_ST_MATCH_ELEMENT

System expected the element http://sap.com/xi/SAPGlobal20/Global;

PurchaseOrderRequest

We suspect a version conflict. The SUS version is 7.01. The XI/PI

system is version 7.11.

Can you confirm or rule-out a version conflict?

The Integration Builder scenario we are using is Plan

Driven Procurement with Supplier Enablement.

We have tryed many variations in Integration Builder, but all

produce errors in SUS. The test tool in Integration Builder also shows errors

for certain message types. The message type ORDERS.ORDERS02

needed to be added manually, and did not come along with the scenario.

Edited by: Bill Guderian on Mar 19, 2010 4:53 PM

[Former Member]

Hello Bill Guderian,

I don't think it should be version issue.

Please check your relevant proxies are green in your SUS system. Transaction sproxy.

Regards,

Pavan

[former_member183819]

Any clue from here.

Note 936003 - ERS Invoice causes conversion error within SRM

When the SRM system attempts to process an ERS Invoice sent from the MM backend, a PARSE_APPLICATION_DATA CX_ST_DESERIALIZATION_ERROR fault is thrown.

Other terms

CX_ST_DESERIALIZATION_ERROR PARSE_APPLICATION_DATA SUS SRM EBP ERS Invoice XI Exchange Infrastructure Mapping

Reason and Prerequisites

This error will occur when the IDOC does not have a VPREI value; it is the result of an error within the divide logic of the XI mapping operation. This operation is performed within the XI system. A calculation of NETWR/MENGE is performed; however, the result is not properly formatted. As such, 72.30/10 produces a result of 7.2300002. This value is too long for the inbound SRM proxy and hence the error is thrown.

Solution

The solution to this problem is to add a FORMATNUM function within the XI mapping operation. This restricts the result to 2 decimal places, which adheres to the definition of the inbound proxy.

Step by step directions on how one implements the FORMATNUM function are as follows:

1. Log into the XI system with SAPGUI

2. Start the Integration Builder:Design tool (for steps on how to do this, review the steps below):

a. Run transaction sxmb_ifr

b. This will cause a browser to come up. Select the Integration Repository link

3. In the left pane, select the Objects tab

4. Navigate to the SAP SRM SERVER ' SAP SRM SERVER 5.0 ' http://sap.com/xi/SRM/SupplierEnablement/Global --> Mapping Objects --> Message Mappings folder

5. Double-click on MM2SUSInvoice

6. The right pane will display the mapping object

7. Select Edit mode

8. In the box that contains the output (Message Type: InvoiceRequest), navigate to InvoiceRequest ' Invoice ' Item ' Price ' NetUnitPrice

9. Double-click on the Amount element and you should see the mapping, represented graphically in the bottom pane

10. In the status line of the graphical editor, select Arithmetic from the list box:

11. To the right of the listbox, scroll until you see the FormatNum function

12. Click on FormatNum, which will cause the function to be added to the graphical editor. You may drag the box as desired

13. Select the connection that binds the if/then/else to the Amount box by grabbing the arrow within the input of the Amount

14. Release the drag of the connection while over the input to the FormatNum box. This will reassign the output of the if/then/else to the input of FormatNum

15. Create a connection between the output of the FormatNum box and the input of the Amount box. You accomplish this by clicking within the output and releasing within the input (respectively).

16. Save the modified mapping object

17. Activate the changes

a. In the left pane, select the Change Lists tab

b. Navigate to the Standard Change List entry

c. Right-click the Standard Change List entry and select Activate

d. Select only MM2SUSInvoice if more than one item is available, and press the Activate button

18. This will complete the required modification.

[former_member183819]

CX_ST_DESERIALIZATION_ERROR PARSE_APPLICATION_DATA SUS SRM EBP ERS Invoice XI Exchange Infrastructure Mapping

SOME DATA MISMATCHING

Note 980867 - Parsing error in SRM-SUS inbound