integration with ERP: error in mapping of RFx response?

[Karsten_Haubold]

Dear all,

I'm integrating SAP Sourcing Wave 7 On Demand with ERP 6.0 EhP 6 and create integrated RFPs in Sourcing out of ERP RFQs. This interface (REQOTE.ORDERS05) is working fine, but I have problems with the response interface (MI_OB_RFx_Response) where the integrated RFP number is transferred into the item text of the ERP RFQ.

The response xml from Sourcing is successfully imported into the PI, but the content is not mapped in message mapping MM_Response_RFx_To_PurchaseRequisition, i.e. the resulting message ET_CROSSREF that is transferred to RFC function module BBP_ES_PR_RFQ_UPDATE is empty.

As I did not make any changes to this interface I suspect that there are errors or issues with the content delivered from SAP, but I found nothing in SAP net or SCN about this.

Does anybody of you have any experiences with this interface and have aany hints that could help me?

Many thanks in advance,

Karsten

[Karsten_Haubold · Accepted solution]

Dear all,

to demonstrate the empty message I add an image of the test results.

I also get the same results with interface MI_OB_Award_To_Purchase_Order when I try to create a PO in ERP out of a Sourcing award:

It would be nice if anyone can give me hints what is wrong here!

Kind regards,

Karsten

[Former Member · Accepted solution]

Hi Kartsen,

Problem cause may be a different namespace within the message. Check if namespace of the SAP Package within SAP PI and namespace configured in SAP Sourcing under Setup -> System Setup -> Integrated System Configuration inside PI URL are equal. Namespace in PI URL must be same as in SAP Package imported into PI system.

You can simply test it in message mapping before making any changes, just change namespace inside message for testing purpose and execute mapping. If you succed with mapping go to sourcing system and change namespace as stated above.

[Karsten_Haubold · Accepted solution]

Hello Tomasz,

thanks, that helped a lot. After I changed the namespace in the xml documents the message mapping went fine and I got results.

My problem is now that the URL in integrated system setting is correct (http://sap.com/xi/ESourcing/SRMJS/OP), but the xml documents have only http://sap.com/xi/ESourcing/SRMJS as namespace. Where is the /OP lost? And what could be the reason?

Our PI namespace is http://sap.com/xi/ESourcing/SRMJS/OP after a standard import by the basis guys. According to the configuration guide it should be http://sap.com/xi/ESourcing/SRMJS - without /OP. Could this difference be the reason and the namespace is hardcoded in the Sourcing system?

Kind regards,

Karsten

[Former Member · Accepted solution]

Check what namespace is in Setup -> System Properties , sapintegration set, property name ExportHandler.outertag.attribute.value. This should be second place to check.

And you are absolutely right there is difference between config guide and package delivered by SAP.

[Karsten_Haubold · Accepted solution]

Hello Tomasz,

thanks for the fast replies!

I checked and found several ExportHandler.outertag properties. For ExportHandler.outertag.attribute.value the note states that it is used to publish agreements.

I guess for my scenarios (RFX response, award to PO) I need the following properties set: RfxExportHandler.outertag.receiptexport and ScenarioAcceptedProposalHandler.outertag.PO, according to the notes for these properties.

None of these properties are set in my system. I will ask our system owner to set them, then I will test again. I'll let you know the results.

Best regards,

Karsten

[Karsten_Haubold · Accepted solution]

Hi Tomasz,

I was able to test today the interface with the new system property RfxExportHandler.outertag.receiptexport set. Unfortunately, this worked not as expected and the interface is still not working.

With the property set, the outer tag is set to

<http://sap.com/xi/ESourcing/SRMJS/OP xmlns:ns0="http://sap.com/xi/ESourcing/SRMJS"> instead of the correct <ns0:MT_Response_RFx xmlns:ns0="http://sap.com/xi/ESourcing/SRMJS/OP">.

This means the /OP is still missing in the URL and I still have to find out why this is deleted by the Sourcing system.

Thanks for your help,

Karsten

[Karsten_Haubold · Accepted solution]

Hi experts,

do you have any suggestions on my problem? I can't be the first one who integrates Sourcing and SAP ERP 🙂

Best regards

Karsten

[Former Member · Accepted solution]

Hi Karsten,

In my system I have this property ExportHandler.outertag.attribute.value  defined only once, on my system context and this is defined together with ExportHandler.outertag.attribute.name = xlmns:ns0.

I changed atrribute value to other namespace and run an RFX import as usual. After import was finished I got a response from sourcing and inside there was a different namespace, exactly same I put in property ExportHandler.outertag.attribute.value. So seems it's valid for response.

The only thing i would suggest is to check system context for which this property and value is defined.

I changed this property after system installation according to namespace defined in E-SOURCING SRM JAVA SERVER 7.0 software component because in integration guide there was different one.

I haven't done any other changes in system configuration.

Importing RFX, sending responses to ERP and contract publishing to ERP work fine, we use a Sourcing 7.0.

[Karsten_Haubold · Accepted solution]

Hello Tomasz,

thanks for the clarification. The problem is solved now after I implemented both system properties.

Best regards

Karsten

[Former Member]

i am planning to install sourcing 9.0, can you pls help me how to install sourcing 9.0..

it should be install in nw 7.3 sp03,

so i have to install java stack only or

abap stack only..

Regards,

Vinoth.R