cancel
Showing results for 
Search instead for 
Did you mean: 

IR content for SUS-PI-EBP integration

Former Member
0 Kudos

hi Friends,

We are implementing SUS-PI7.0-EBP5.0 integration with service procurement scenario. we have installed standard content from SAP for SRM SERVER 5.5 sp 12 & SRM MDM Catalog 2.0 SP 04 and followed the config guide for the scenario.

we could not locate additional content containing required interface & message mapping. Any idea on which additional content should be imported? The config guide specifies

step: You have installed and imported Interface and Mapping Repository content

Where to find: SAP Service Marketplace at service.sap.com/instguides u2192 mySAP SRM u2192 Using SAP EBP 5.0 u2192 Master Guide

but this has not been very useful.

Thanks,

sachin

PS: Points will be awarded for useful answer.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

The issue was resolved.

No IR mappings required for service procurement scenario. Imported BBPCRM SWCV in IR.

Error in proxy is resolved as it was data issue.

0 Kudos

Hi Sachin,

How are you able to address the issue regarding PARSE_APPLICATION_DATA / CX_ST_MATCH_ELEMENT? We are always getting this issue when triggering the abap proxy. See below the full message being returned.

PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX

_ST_MATCH_ELEMENT in /1SAI/TXSB3F3B9D6A1F67E55A2FF Line 285 System expected end

of element '{http://sawes.ws.in.xmlgatev2.sanco.cec.eu}message' XML Bytepos.: 43

7  XML Path: ns0:Envelope_Response(1)ns0:Body_Response(1)ns1:callServicesRespons

e(1)ns1:return(1)ns2:updateXMLEntryResponse(1)ns2:return(1)ns2:response(1)n

Former Member
0 Kudos

Hi All the mapping programs(XSLT) will be available in the software component itself.

You can try one thing.

1) Find the basis software component to your technology in Software component catelog of SLD

2) Assign this software component to your bussiness and technical systems

3) in the IR refresh SLD cache

If it is not working, delete existing the component in IR and again import new software component that you made in 1 and 2 steps

Atleaset this worked for me when we integrate SCM with XI.

Former Member
0 Kudos

hi Rama,

The config guide mentions following steps for these mappings,

Step: You have installed and imported Interface and Mapping Repository content

Where to find: SAP Service Marketplace at service.sap.com/instguides->mySAP SRM-> Using SAP SRM Server 5.5 ® Master Guide

Where can one find this repository content as the config guide does not specify any specific content?

cheers,

sachin

Former Member
0 Kudos

Well we made progress on this and there are no additional mappings required for service procurement scenario.So warning messages in IR can be ignored.

However when transferring vendors from SUS to EBP I get following error, any pointers?

Interface determination for interface SupplierPortalTradingPartner_CreateOrChange_Out of http://sap.com/xi/EBP does not have any mapping associated with it by default. Is this standard?

- <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>Request Message</SAP:P1>

<SAP:P2>CX_ST_MATCH_ELEMENT</SAP:P2>

<SAP:P3>/1SAI/TXSBD7B3215B596D978179C</SAP:P3>

<SAP:P4>XML Bytepos.: 183 XML Path: n0:SupplierPortalTradingPartner(1) Error Text: System expected the element 'SupplierPortalTradingPartner'</SAP:P4>

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXSBD7B3215B596D978179C XML Bytepos.: 183 XML Path: n0:SupplierPortalTradingPartner(1) Error Text: System expected the element 'SupplierPortalTradingPartner')) System expected the element 'SupplierPortalTradingPartner'</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Former Member
0 Kudos

Hi Sachin

This is a standard integration. Importing the component itself will get all mapping and data types. I think it will have Standard configured integration scenario and actions. You will be required to do ID and set in IS. That will work

Thanks

Gaurav

Former Member
0 Kudos

hi Gaurav,

Thanks for reply. Well after successfully importing SRM Server 5.5 content I could not find relevant interface / message mapping in any of the namespaces.

The config guide specifically mentions importing mapping content. Where can one find SUS mapping content required for service procurement scenario?

Any thoughts?

sachin

Edited by: sachin kotalwar on Nov 21, 2008 4:37 PM

prateek
Active Contributor
Former Member
0 Kudos

hi Prateek,

We are doing 'service procurement' scenario & there is no SAP documentation to locate current SUS mapping content.

Thanks,

sachin

Former Member
0 Kudos

HI Sachin

While importing the SWCV did you have integration scenario already existing under the defined namespaces.

It will be proxy based communication and i think that integration scenario will be auto configured. You just need to do is ID.

You need to create RFC from SUS to PI and PI to EBP

There are 5 major business operations that you require

https://www.sdn.sap.com/irj/scn/wiki?path=/display/espackages/service%252bprocurement

Business scenario presentation

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d00dd6c1-e5d3-2a10-4f8d-addf4661...

Thanks

Gaurav

Former Member
0 Kudos

hi Gaurav,

Scenario exists in SRM SERVER 5.5 content SP 13 but many of required SUS mappings are missing.

Thanks,

sachin