SRM - ECC Integration

Hi all,
We have 2 SRM systems : SRM 7.0 & 1 ECC system : ERP 6.0 (Ehp 4).
Is it possible for us to integrate these 2 SRM systems with 1 ECC in the backend?
If yes then what major settings will be required? If no what could be the reason?
Thanks,
Nikhil.

Nikhil,
Normally multiple backend systems are connected to one SRM system for centralizing procurement in SRM.
You should be able to connect multiple SRM systems to same backend. It would be similar to what you do for two SRM systems with one backend each. Since each SRM system will have different logical system, it should not be a problem.
I am curious on the business need for two SRM systems.
SG

Similar Messages

ECC integration with Crystal report 2008

Hello,
If some one have guide of ECC integration with Crystal report 2008 ? Please share me I need to integrate ECC to crystal 2008 integration.
Regards,
Sankar.G
Basis Cosultant

Do not cross post.
Read the "Rules of Engagement"
Regards
Juan

SRM-ECC PO Business Content

We are implementing SRM -EXtended Classic Scenario.
The PO is created in SRM and a copy is sent back to ECC. Therefore PO is avialable in both the SRM & ECC systems to be pulled into BI. In BI we have serperate content available for Procurement Analysis in ECC(based on LO cockpit) and SRM area. (under 0SRM & 0SCM). The contents /data model look very different.
Any benefits/pitfalls in using either of the business content for SRM procurement reporting?
Any ideas anyone

Holger,
Can't you have the iView open up another browser, and within the new page/on lauched brower have the SRM iviews based on user role?
James

Can I work backward from APO CIF function module to ECC Integration Model

On our APO box, I have activated the "new-style" BAdI which is called by the CIF function module /SAPAPO/CIF_TLANE_INBOUND:
CALL BADI lr_ref_cif_enhance->inbound_tlane
How can I find out what the business analysts have to do in their ECC Integration Model
to make sure that the CIF_TLANE_INBOUND function module is called when the Integration Model is activated (so that the BAdI will also fire)?.
Our current Integration Model does fire the BAdI /SAPAPO/IF_EX_TR_TRANSFER , but not the "enhance inbound tlane" BAdI called by CIF_TLANE_INBOUND.
So ...to restate the question:
How do I figure out what I have to tell the business analysts to do in their Integration Model to make sure that CIF_TLANE_INBOUND is called when the model is actrivated ???

Hi David,
I was away in a long meeting and just came back. A quick check in another R/3 (Enterprise) system showed the following:
There is no FM in the R/3 Enterprise box as CIF_TLANE_SEND and in APO (SCM4.1)
/SAPAPO/CIF_TLANE_INBOUND. This is not surprising esp when I check the other system versions based on which I did the initial research. It was ECC 6.0 with Enterprise Extension DFPS switched on (checked SWF5) and the APO system SCM 5.0.
Lucky me I checked the internal Sandbox systems instead of my client systems otherwise I would have posted there is no FM CIF_TLANE_SEND
Forget the SD Scheduling Agreement object I mentioned in the previous reply. That master data object will not trigger FM CIF_TLANE_SEND. I found the correct FM for it CIF_SDLS_SEND on R/3 side and /SAPAPO/CIF_TPSCO_INBOUND on the APO side.
So you have to necessarily use the BADI or User Exit enhancements for TPSRC and NOT TLANE.
In any case if its a Contract or Scheduling Agreement or Purchasing Inforecord master in R/3 (or ECC any version) then TPSRC is the FM used to create External Procurement Relationships (txn /SAPAPO/PWBSRC1) in APO during CIF transfer. Also a corresponding Transportation Lane (txn /SAPAPO/SCC_TL1) gets created when the Procurement Relationship is added in APO. Otherwise you can always manually create a transportation lane in APO which is an important master data for External Procurement Order / Requisition creation in APO.
Hope this helps. I am logging off for today - so no more further digging. But thanks to you I discovered another small "blackbox" of SAP. Will blog on this some time later - till then you can take a look at the [CIF Wiki|https://wiki.sdn.sap.com/wiki/display/SCM/CIF] page.
Best regards,
Somnath

How do we replicate product categories from SRM/ECC in to SUS system

How do we replicate product categories from SRM/ECC in to SUS system in srm 7.0

Hi Gopal,
Are you confused between SUS & ROS? If you meant ROS, it is advised to create local product categories in ROS under COMM_HIERARCHY.
Let us know your exact requirements.
Regards,
Nikhil

BW powered by HANA with ECC integration

Dear Experts,
Kindly help me for step by step BW 7.4 Powerd HANA and ECC system integration & configuration.
Regards,
Sri.

Dear Dinesh,
Thanks for Quick reply.
Same only BW and ECC integration, But now SAP BW 7.4 not dual stack, ABAP and JAVA stacks are separate..many changes is there. Do you have any idea about same host, same SID installation for BW 7.4 ABAP stack & BW 7.4 Java stack on HANA Database.
SAP BW 7.4 Java to ECC integration is some wizard will be there.
the same way in ABAP stack any transaction or wizard is there or not.
Kindly help for this.
Regards,
Srini

SRM and ECC integration

Hi Gurus,
We are in a phase of integrating SRM with ECC, so that any master data created in ECC should be replicated in SRM etc...
Can any one provide me detail step by step configuration required to integrate SRM with ECC?
Any material witll be helpful.

Hi sanju,
see these links
https://www.sdn.sap.com/irj/sdn/articles-community?prtmode=print&startindex=261 - 38k
https://www.sdn.sap.com/irj/sdn/articles?startindex=21 - 46k
www.sap-press.com/product.cfm?account=&product=H2900 - 34k
thanks
karthik
reward me idf usefull

SRM-PI-ECC Integration issue

Hey All
There is some issue coming in Central Contact management scenario.
SRM 7.0
ECC 6.0 EHP 4
PI
*below is the error details we get in SXMB_MONI of SRM Sytem* <REMOVED BY MODERATOR>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_UNEXPECTED</SAP:Code>
<SAP:P1><></SAP:P1>
<SAP:P2><Fault></SAP:P2>
<SAP:P3 />
<SAP:P4>ST: ST_XMS_MSGHDR30_SOAP_FAULT</SAP:P4>
<SAP:AdditionalText>System expected the element 'Fault'</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unexpected XML element <>; <Fault> was expected System expected the element 'Fault'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Narender
Edited by: Prateek Raj Srivastava on Mar 5, 2011 4:49 PM

Thanks Buddy.
We have some progress. Now data passed from SRM to PI and now stucked in ECC. The XML file in SXMB_MONI in ECC, shows the staus "Transfer to External Application" and in ECC SMQ2 Queue XBQRCCR4400000066 stucked with status "STOP".
While dubugging the relevant we are getting the error '"COMMNICUTION_FAILURE"
And the Payload .xml file is as below :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:TimeSent>2011-03-11T07:14:32Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SS1CLNT200</SAP:Service>
<SAP:Interface namespace="" />
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ES1CLNT200</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/APPL/Global2">PurchasingContractSRMReplicationRequest_In</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/APPL/Global2">PurchasingContractSRMReplicationRequest_In</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
<SAP:QueueId>CCR4400000066</SAP:QueueId>
</SAP:ReliableMessaging>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2011-03-11T07:14:32Z" wasRead="false">
<SAP:Engine type="BS">SS1CLNT200</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2011-03-11T07:14:32Z" wasRead="false">
<SAP:Engine type="IS">is.01.auvimel00s971</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2011-03-11T07:14:33Z" wasRead="false">
<SAP:Engine type="BS">ES1CLNT200</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20110311</SAP:Date>
<SAP:Time>181433</SAP:Time>
<SAP:Host>AUVIMEL00S962</SAP:Host>
<SAP:SystemId>ES1</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>MSSQL</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>003</SAP:ProcStatus>
<SAP:AdapterStatus>007</SAP:AdapterStatus>
<SAP:User>RFCUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>001</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_RECEIVER</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>RECEIVER</SAP:PipelineIdExternal>
<SAP:PipelineElementId>1DC6B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_INBOUND_PROXY</SAP:PipelineService>
<SAP:QIdInternal>XBQRCCR4400000066</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">SND_CENTR</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">AC1E020C11E44D79CBD9E0A7</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="MSGID">E04BAF35835783F182AD005056A12FA9</SAP:EOReferenceOutbound>
<SAP:MessageSizePayload>2929</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>11916</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>2929</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>258</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IENGINE</SAP:AdapterInbound>
<SAP:AdapterOutbound>PROXY</SAP:AdapterOutbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>57</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.211</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.256</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.257</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.274</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.274</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.387</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_INBOUND_PROXY</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.39</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:System xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://www.sap.com/webas/712/soap/features/runtime/metering/" name="CallingType">SA</SAP:Record>
</SAP:System>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/XI/engine/?type=entry</Trace>
<Trace level="1" type="T">Work Process ID: 4580</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = E04BAF35835783F182AD005056A12FA9</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EOIO</Trace>
<Trace level="1" type="T">Queue-Id = CCR4400000066</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBQRCCR4400000066</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBQRCCR4400000066</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface PurchasingContractSRMReplicationRequest_In</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/APPL/Global2</Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Work Process ID: 2348</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">ROLLBACK WORK requested by application</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:payload-E04BAF31EF9CE7F189DE005056A10467sap.com">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Can anyone suggest what can be issue ?
Thanks
NAP

SRM-ECC org structure integration

Hi,
Can anyone suggest an RFC/BAPI to fetch SRM organisational structure in ECC.We do not have HR implemented and therefore there is no org strucuture in ECC but it does exist in SRM.
I have Z-table in ECC with fields sap id,manager id,Role(mgr,VP etc) to be filled from SRM.
Thanks in advance.

Hi Guys,
In addition to my message above, I'm adding the error below so that somebody can better understand the issue here.
Information on where terminated
 Termination occurred in the ABAP program "CL_BBP_ES_EMPLOYEE_MYS========CP" -
 in "IF_BBP_ES_EMPLOYEE~GET_RL_UNIT_IDS".
 The main program was "SAPLBBP_SC_UI_ITS ".
 In the source code you have the termination point in line 45
 of the (Include) program "CL_BBP_ES_EMPLOYEE_MYS========CM008".
 The termination is caused because exception "CX_BBP_ES_INTERNAL_ERROR" occurred
 in
 procedure "USER_DETAIL_GET" "(FORM)", but it was neither handled locally nor
 declared
 in the RAISING clause of its signature.
 The procedure is in program "SAPLBBP_SC_APP "; its source code begins in line
 6 of the (Include program "LBBP_SC_APPF35 ".
=========================================================
return parent org.-units of all paths
SORT lt_struc BY seqnr.
LOOP AT lt_struc REFERENCE INTO lr_struc WHERE otype = 'O'.
 IF lv_level IS INITIAL.
 lv_level = lr_struc->level.
 ELSEIF lv_level <> lr_struc->level.
 EXIT.
 ENDIF.
 ls_rl_unit-otype = lr_struc->otype.
 ls_rl_unit-objid = lr_struc->objid.
 ls_object-otype = lr_struc->otype.
 ls_object-objid = lr_struc->objid.
 CALL FUNCTION 'HR_OBJECTBUPA_GETBUPA'
 EXPORTING
 is_object = ls_object
 IMPORTING
 es_hrobjbupa = ls_rl_bupa
 EXCEPTIONS
 object_type_not_allowed = 1
 OTHERS = 2.
 IF sy-subrc <> 0
 OR ls_rl_bupa-bupaguid IS INITIAL.
 RAISE EXCEPTION TYPE cx_bbp_es_internal_error.
 ENDIF.
 ls_rl_unit-guid = ls_rl_bupa-bupaguid.
 APPEND ls_rl_unit TO rt_reportingline_unit.
ENDLOOP.
ENDMETHOD.
Thanks
Debashish

SRM, MDM, ECC integration for central contract management.

Hi there,
I am questioned by a client with respect to the possibility of the following scenario -
1. There are several SAP back end systems in place.
2. SRM 7.0 will be implemented as single sourcing system.
3. The SAP back end systems carry different material master codes for the same material and this will remain the same and no cleaning effort to have a unique code across all systems is going to be done.
4. If we use MDM in the mix - will it be possible for the SRM system to act as a central contracting solution and create a central contract with the unique material code in MDM.
5. On distribution of this contract across to individual SAP back end system the back end should map the MDM code to correct material code in that respective system.
Any insights with respect to if this is possible with some enhancements or not at all possible will be highly appreciated.
Thanks and Regards,
Shantanu Joshi

Hello Shantanu Joshi
Your business scenario is standart MDM functionality
More about how it works you can read from:
MDM overview
and standart help links (see scenarios part):
http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
Regards
Kanstantsin

SRM -- MDM -- ECC integration for central contract management for SRM 7.0

Hi there,
I am questioned by a client with respect to the possibility of the following scenario -
1. There are several SAP back end systems in place.
2. SRM 7.0 will be implemented as single sourcing system.
3. The SAP back end systems carry different material master codes for the same material and this will remain the same and no cleaning effort to have a unique code across all systems is going to be done.
4. If we use MDM in the mix - will it be possible for the SRM system to act as a central contracting solution and create a central contract with the unique material code in MDM.
5. On distribution of this contract across to individual SAP back end system the back end should map the MDM code to correct material code in that respective system.
Any insights with respect to if this is possible with some enhancements or not at all possible will be highly appreciated.
Thanks and Regards,
Shantanu Joshi

Hello Shantanu Joshi
Your business scenario is standart MDM functionality
More about how it works you can read from:
MDM overview
and standart help links (see scenarios part):
http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
Regards
Kanstantsin

SAP SRM - ERP INTEGRATION

Hello,
we are designing application architecture. Our landscape is:
- ECC 6.0
- SRM 5.0
- XI 7.0
We are thinking of using XI as middleware even for those scenario in which in not required (es. Contract Managament):
In particular every time we have a communication based on IDOC we want to use XI as communication middleware. Pure RFC integration will not use XI.
Has anyone some experience on this?
Thanks
antonio

Hi
Some related Links ->
Re: Upgrade SRM on 4.7 to ECC 6.0
Re: EBP 3.0 Integration with ERP 2004
SRM@ERP2005
Re: SRM-R/3 Service Packages
Problem transferring deletion status to ERP from SRM
SRM 4.0 (SERVER 5.0) integration
Re: SRM add-on configuration
Re: Integration between SRM and 5 R/3 backends
RFC connection problem during SRM - R/3 integration
Re: ECC 5.0 & SRM / EBP
Re: SRM as ADD On in ECC6.0
Please go through the following SAP OSS Notes, which will help ->
Note 963000 - Usage and release of SRM as AddOn to ECC in ERP2005
Note 863532 - Release Restrictions mySAP SRM 2005
Note 931020 - SRM connection to an ERP 2005 (ECC 600) back end
Note 917523 - Release note SRM Server 5.5 Support Package 05
Note 1014414 - SRM 5.0 SP stack 08(03/2007) SAPKIBKT08 release/info note
Note 872533 - FAQ - Middleware
Note 740536 - No objects in administration console
Note 874589 - SRM 4.0 connection to an ERP 2005 system
Note 862290 - Connection to ECC 5.0 back end
Note 995771 - System Landscape Copy for SAP SRM 4.0 and 5.0
Regards
- Atul

SRM ERP integration

Hi ,
Can somebody please let me know where I can find manul steps to integration ECC 6.0 into SRM 7.0.
I have checked at market place, it has automated steps guide..
Best Regards,
Tushar.

Dear Thusar,
Looks like this is what you're looking for:
http://help.sap.com/saphelp_nwce711core/helpdata/en/15/710890e69a450ea82f5f4f2fa4d308/frameset.htm
I am going to connect SRM 7.0 (NW7 EHP1) to ERP6 (NW7).
What is the version of SRM and ERP that you integrate? Have you successfully integrate them?
Thank you very much.

SRM data integration in EP with XI 3.0

Hi friends,
Our client wants us to integrate Purchasing related documents from SRM into the EP 6.0 using XI 3.0 as a integration software. We would like to show the SRM related XML document in an iview format in the EP 6.0. I would like to know if any body in SDN had similar situation and how they accomplished this. Client does not want to implement standard BP for SRM.
Appreciate your time.
Steve.

Hi Steve,
Hope these links give more information
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1334 [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
/people/saravanakumar.kuppusamy2/blog/2005/02/07/interfacing-to-xi-from-webdynpro
/people/sap.user72/blog/2005/09/15/connecting-to-xi-server-from-web-dynpro
EBP - XI - SUS configuration
R/3(MM) -XI- SUS Scenario Error
Re: XML Message Not Generated in SUS SRM 4.0
For XI Context, check out this
https://service.sap.com/swdc > search for all categories>XI content SRM
Regards
Vishnu

Stack overflow error when connecting to SRM with integrated ITS

When I try to connect to SRM Server through Integrated ITS, it is giving me the error "Stack overview, giSAPWP is null or not an object. Kindly let me know how to resolve the error.

Hi Arun,
Are you running with Portal ?
If yes, could you confirm the following point :
- portal and ITS of the SRM system run under the same protocol (both under http or https, ELSE it is not possible),
- portal and ITS of the SRM system are in the same domain
Kind regards,
Yann

SRM - ECC Integration

Similar Messages

Maybe you are looking for