on 02-20-2007 11:59 PM
Y'all,
I'm, stucked with the SRM-SUS content delivered for XI...
We have imported the TPZ file into XI, we have done all the settings in both systems (like enable XI), communication channels are OK, etc...
But when trying to post a PO from SRM to SUS, in XI monitor appears the following error:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to determine name of mapping program</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Since i have reviewed all the objects created while the TPZ file was imported, no interface mapping was created for (SRM) PurchaseOrderRequest_Out -> PurchaseOrderRequest_In (SUS)...
I can not change the objects or create new ones, the SWCV is marked as read-only and i couldn't try to add a mapping program.
This is the part of the main message in the "request mapping" pipe step:
<SAP:Sender>
<SAP:Service>BS_SRD_BACKEND</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/SRM/Procurement/Global">PurchaseOrderRequest_Out</SAP:Interface>
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SRD500_DEV</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/SRM/SupplierEnablement/Global">PurchaseOrderRequest_In</SAP:Interface>
<SAP:Mapping notRequired="M">
<SAP:ObjectId>oxryscSwOQSSmyDEB6ZRuQ==</SAP:ObjectId>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/SRM/Procurement/Global">PurchaseOrderRequest_Out</SAP:Interface>
</SAP:Main>
Please help, useful answers will be rewarded...
Regards,
Gerardo.
Hi Gerado,
Hey check the following note
Note 793669 - FAQ: SUS in SRM 4.0 with XI 3.0
Also, if it doen't work, try reimporting it again.
Regards,
Akshay
Also, check the following note
Note 705541 - XI 3.0 (Support Package 1 and higher): Importing XI Content
Message was edited by:
Akshay Salunke
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ak,
Man, thnks for your reply, i've checked the notes that you mentioned and i've found the following: Note 754356 - SUS-XI: Current SUS message mapping. That mentions some errors on message mapping from SRM to SUS, it contains a TPZ file that i suppose that contains mapping contents, so maybe if i import it will help me.
Let me try and i will acknowledge.
Regards,
Gerardo.
Jai,
I have tried to create a message mapping in other SWCV and use it in the ID (receiver determination - agreement) but then a different error message came:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Technical Routing
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
<SAP:P1>-BS_SRD_BACKEND</SAP:P1>
<SAP:P2>-SRD500_DEV,http://sap.com/xi/SRM/Procurement/Global.PurchaseOrderChangeRequest_Out</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver agreement found for sender -BS_SRD_BACKEND to receiver -SRD500_DEV,http://sap.com/xi/SRM/Procurement/Global.PurchaseOrderChangeRequest_Out</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
So, i tried deleting the message mapping to return to the "NO_MAPPING_FOUND" and then something rare happened:
The NO_MAPPING_FOUND message dissapeared and a new one came but not in the central engine, it is raised in the SUS side integration engine:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion (; error ID: ; ( )) PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Request Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXS00000000000000000006 XML Bytepos.: 3859 XML Path: nr1:PurchaseOrderRequest(1) Error Text: Fin del elemento {http://sap.com/xi/SAPGlobal/Global}PurchaseOrderRequest previsto)) Error during XML => ABAP conversion (Request Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXS00000000000000000006 XML Bytepos.: 3859 XML Path: nr1:PurchaseOrderRequest(1) Error Text: Fin del elemento {http://sap.com/xi/SAPGlobal/Global}PurchaseOrderRequest previsto)) Fin del elemento {http://sap.com/xi/SAPGlobal/Global}PurchaseOrderRequest previsto</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I don't know this kind of error, so if you please can help me to find the solution will be great.. I will reward helpful/useful replies.
BR,
Gerardo.
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.