E-sourcing / SPM / BW / ECC integration

Dear Gurus,
I know the question seems to have been asked several times, but none of the different answers could give me a full overview of the technical architecture of the 4 components that could be involved in the full procurement process scope. I hope this is the right forum to ask the question as SPM forum could be another option...So, I would like you to correct me if I am wrong...
Here is the current status of my customer:
- He has implemented E-Sourcing 9 (on premise)
- He integrated E-sourcing with its ERP (master data for the contract are replicated to ECC, and material master data is sent from ECC tp E-Sourcing)
- He has SPM licenses
- He wants some reporting on the E-Sourcing processes (duration of RFx projects, baselines after first quotations from suppliers, etc). Business requirements are still at a high level, not very deeply detailed
Here is my understanding of what we can do, what we can not do, and what we should do
- At the moment, there are some reporting features available in E-Sourcing out of the box.
- Some adhoc queries could be done through E-Sourcing
- There is no standard way to extract data from E-Sourcing to be able to integrate them into BW (not SPM, but a regular BW without the SPM content activated) directly. The only way is to develop on the J2EE platform the programs to extract flat files, and then load them into BW
- Even if we install SPM on the BW server and the ECC instance (direct datasource as we are with an on-premise approach), I could not get the data from E-sourcing regarding RFx processes without using a flat file approach.
Based on that, I think we should do the following:
1) implement SPM to get the full ROI on the license and leverage the full SPEND analysis that SOM can give
2) implement the direct datasource approach in ECC to feed SPM
3) develop the flat files approach to extract data from E-Sourcing
Steps 1 and 2 need to be performed together, whereas step 3 could be separated as we could use regular BW technology to upload data in it.
Here are my questions regarding E-Sourcing and SPM:
- Am I right when I say that the only way to get data out of E-Sourcing for RFx process is through flat files (SPM implemented or not) ?
- if we decide to implement SPM, do we really still need an J2EE platform, as I thought BI 4.x would be the java runtime platform ?
- if we really need a java stack, can we reuse the J2EE engine of E-Sourcing, as for now, the regular BW we implemented does not have any Java stack, because we are using BI 4.0 as the reporting platform ?
I know it is a lot of questions....Your advice will be very helpful in leveraging E-Sourcing and SPM prodcuts.
Thanks
PY

Hi Bhakti
The official Forum for Spend Performance Management is here: SAP Spend Performance Management
And hence your post was unnoticed by the SPM community.
I see a lot of activity on this post, so not sure if this question is still open. If it is, I would recommend you to a start fresh post in the SPM forum with your scenario details and I will respond.
Details of SPM documentation can be found in the blog post:
/people/rohit.kamath/blog/2010/07/20/spm-documentation
Also for more information on Spend Performance Management, visit the BPx community page for SPM at:
Spend Analytics
Regards
Rajesh

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

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

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

Source SPM template for CURR_DS (Z_SADSECC6TCURR) to map

anyone have idea what is source SPM template for CURR_DS (Z_SADSECC6TCURR) to map, I have extracted the data to BI and maintained necessary tables in BI as well, but i am unable to find standard template to map the CURR data source .. Neither create new template.
For others its direct templates are available not CURR? Can someone give me tips to build CURR template?
Regards,
Mahesh

Hi Mahesh,
SPM uses the standard currency tables for any currency conversion in the application. If you already have currency populated in the standard BW tables you don't have to load the same data again using the SPM data load mechanism.
Having said this if you want to load data using flat files, you need 2 files one for the currency conversion rate and second file for currency conversion factor.
Regards,
Rohit

Integration of E-Sourcing & SPM

Hi everyone,
We are having a scenario where, we need to integrate E-Sourcing with SPM. I need some guides or existing documents that can be used for the same.
Thanks,
Bhakti

Hi Bhakti
The official Forum for Spend Performance Management is here: SAP Spend Performance Management
And hence your post was unnoticed by the SPM community.
I see a lot of activity on this post, so not sure if this question is still open. If it is, I would recommend you to a start fresh post in the SPM forum with your scenario details and I will respond.
Details of SPM documentation can be found in the blog post:
/people/rohit.kamath/blog/2010/07/20/spm-documentation
Also for more information on Spend Performance Management, visit the BPx community page for SPM at:
Spend Analytics
Regards
Rajesh

BW Myself source system in ECC 5.0 while Export DataSource!!

Hello BW Experts,
When we do Export DataSource for a DataMart eg:ODS, we have to again select our Myself BW source system and replicate our datasource to see it visible in the infosource tree with our DataMart name starting with 8*.
Plz clarify these Qs:
1. Can we perform "Generate Export dataSource " for customer generated DataMarts and replicate them in Myself BW source (Other than Business Content DataMarts??)??
2. Which is the Myself BW system in the ECC 5.0 version as everything is integrated and used being the source system as T90CLNT800 with the client 800and with a single userID and password.
Note:I could not find my generated Datasource for my customer generated DataMart to replicate the same using T90CLNT800 context menu.
Plz throw some light on this!!
regards,
Sapster...Points will be awarded.

Hi,
You dont need to replicate the datasource after the generate export datasource. You can find your 8* datamart in the infosource by using any of these 2 methods:
1. Goto the top most of the info-source i.e. "Infosources" -> right click -> Insert lost nodes. You should be able to find your datamart.
2. Goto settings (menu) -> Display generated objects -> show generated objects.
Hope this helps.
Bye
Dinesh

Standard PML Message XSD Import in PI Gives Error ::AII -PI-ECC Integration

Hi Experts,
We are currently integrating the AII system with ECC using PI as a middleware. We are trying to post one type of message in AII which will check the tag event in that message and do the required action in AII.
Now point is AII team is expecting a PML mesage as below -
<?xml version="1.0" encoding="utf-8" ?>
- <pmlcore:Sensor xmlns:pmlcore="urn:autoid:specification:interchange:PMLCore:xml:schema:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:autoid:specification:interchange:PMLCore:xml:schema:1 ./PML/SchemaFiles/Interchange/PMLCore.xsd">
<pmluid:ID xmlns:pmluid="urn:autoid:specification:universal:Identifier:xml:schema:1" />
- <pmlcore:Observation>
<pmlcore:DateTime>2012-02-08T16:41:26.760</pmlcore:DateTime>
<pmlcore:Command>TAG_DECOM_BATCH</pmlcore:Command>
- <pmlcore:Data>
- <pmlcore:XML>
<PRODUCT>TRN_PROD_13</PRODUCT>
<BATCH_ID>ATRN_PROD13B</BATCH_ID>
<LogicalDeviceID>DG_AMBOISE_LINE_1</LogicalDeviceID>
</pmlcore:XML>
</pmlcore:Data>
</pmlcore:Observation>
</pmlcore:Sensor>
And they have also provided the standard PML message xsd to us but when we are importing it in to XI it is giving the below error -
Change list activated; note the following information
Check result for External Definition: PML | urn:sugata_PI_LFTP: Document check found errors
Cause: Loaded document contains incorrect XSD definition
Name of '/schema/element("XML")' starts with 'xml'
as we can see in the above XML there is a tag called <pmlcore:XML> if we change this to something like <pmlcore:ABC>
it is imported successfully and we can see the message structure in the XSD also.
As PML XSDs are standard so the AII team is also not changing the same as mentioned above.
Please advise how can we import this XSD in PI with tag name XML?
Another question, which is very confusing to us - is PI able to send PML message as mentioned above? or PI will send a simple XML as below -
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_Batch_DECOMM xmlns:ns0="http://pfizer.com/serialization/batch_expiration">
- <Observation>
<DateTime>2012/02/08</DateTime>
<Command>TAG_DECOM_BATCH</Command>
- <Data>
- <XML>
<PRODUCT>F000000211</PRODUCT>
<BATCH_ID>00000TESTAII001</BATCH_ID>
<DOCUMENT_NO>0000000004811027</DOCUMENT_NO>
<LogicalDeviceID>DG_GLOBAL</LogicalDeviceID>
</XML>
</Data>
</Observation>
</ns0:MT_Batch_DECOMM>
and AII will convert it to PML message using some PML engine or PML converter in AII?
Request your urgent help in this regard. Any help will be appreciated and rewarded.
The standard XSDs we are using are - PMLCore.xsd and Identifier.xsd , first one is referring the second one.
Thanks
Sugata B Majumder

Hi Mark,
Thanks for the input. I have also thought the same using XSLT or JAVA as in PI7.1 the tag XML is not allowed in xsd. But I got surprise when I have created a data type having a field name as XML and xsd for this has been successfully generated.
Any ways I have handled the entire structure target payload creation in XSLT. here is the XSLT code I have written-
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
   <xsl:comment>
   This XSLT Mapping is designed to handle the PML structure required by SAP AII system.This XSL Transformation will create PML Standard Message in SAP PI.
   Author: majums15
</xsl:comment>
<pmlcore:Sensor xmlns:pmlcore="urn:autoid:specification:interchange:PMLCore:xml:schema:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:autoid:specification:interchange:PMLCore:xml:schema:1 ./PML/SchemaFiles/Interchange/PMLCore.xsd">
<pmluid:ID xmlns:pmluid="urn:autoid:specification:universal:Identifier:xml:schema:1" />
      <pmlcore:Observation>
      <pmlcore:DateTime>
     <xsl:value-of select="substring(//EDI_DC40/CREDAT,1,4 )" />
<xsl:text>-</xsl:text>
<xsl:value-of select="substring(//EDI_DC40/CREDAT,5,2 )" />
<xsl:text>-</xsl:text>
<xsl:value-of select="substring(//EDI_DC40/CREDAT,7,2 )" />
<xsl:text>T</xsl:text>
<xsl:value-of select="substring(//EDI_DC40/CRETIM,1,2)" />
<xsl:text>:</xsl:text>
<xsl:value-of select="substring(//EDI_DC40/CRETIM,3,2)" />
<xsl:text>:</xsl:text>
<xsl:value-of select="substring(//EDI_DC40/CRETIM,5,2)" />
</pmlcore:DateTime>
        <pmlcore:Command>TAG_DECOM_BATCH</pmlcore:Command>
        <pmlcore:Data>
          <pmlcore:XML>
           <xsl:element name="PRODUCT">
           <xsl:value-of select="//ZBATMAS/IDOC/ZE1BATMAS/MATNR" />
            </xsl:element>
             <xsl:element name="BATCH_ID">
             <xsl:value-of select="//ZBATMAS/IDOC/ZE1BATMAS/LICHA" />
              </xsl:element>
            <xsl:element name="LogicalDeviceID">
             <xsl:text>DG_GLOBAL</xsl:text>
              </xsl:element>
             <xsl:element name="DOCUMENT_NO">
             <xsl:value-of select="//ZBATMAS/IDOC/EDI_DC40/DOCNUM" />
              </xsl:element>
            </pmlcore:XML>
        </pmlcore:Data>
      </pmlcore:Observation>
    </pmlcore:Sensor>
</xsl:template>
</xsl:stylesheet>
Thanks
Sugata B

ECCS - Integration of an operative FS version with a FS Item Hierarchy

Dear collegues,
I'm trying to create a FS Item Hierarchy on ECCS as a copy from the FS Version (T011) but I'm not able to get the GL accounts as a position, but only the previous node of the tree, I mean, no gl account is populated as a position.
I had already integrated the Chart of positions as a copy from my group chart of accounts but I haven`t managed to go further.
Can somebody help?
Thanks in advance!
Rushid
Has somebody ever come across the same problem?
Edited by: Rushid Rush on Aug 25, 2010 8:56 AM

I have finally noticed it is not possible instead you create as many nodes as group accounts. It means a lot of work but this way it works.

InfoProviders versus Queries Data Source for BO SAP Integration

Hi All,
I would like to know if there is any discussion or suggestion on commonly used choice of data source for BO with SAP Integration. I do know there is a best practices suggestion from Ingo on Webi and the choice is to use queries so that we could leverage the functionalities of calculated key figures, exit variables and etc. But as I see from another website it claims that this will slow down the access of data using queries.
Thanks
David

Hi Ingo,
Is there any slide presentations from anyone that has that kind of information? We are in the midst of implementation right now and are selecting the method. I need to come out with pros and cons of the choices that we have in order for us to select the best one even though from my gut feeling I would still prefer the Queries.
Especially it will also make use of aggregates and also data flow size might be fewer due to variable that exists. Compared to using MultiProvider, it might transfer the whole data lot and if we were to create parameter there in Crystal or something else it will filter data only from there onwards.
Please correct me if I am wrong.
Thanks
David Yee

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

Pos to ecc integration

Hi
presently i am working in retail project,where i need to integrate pos to ecc6.0, so my client asked for presentation about xi,how xi will enhance his process so that he can go for implementing xi.so i want to address about the following issues
1)how xi will enhace business process
2)limitations of xi
3)what are the possible interfaces of pos to ecc
and apart from above, any main issues i need to address
so i request you to provide any links or materials it will be great help to me
regards
ramya

Hi Ramya,
Before doing answer to your Q's, can you please reply back for my doubts....
1) On Which Application this POS is running at presently??
2) Can they Expose their Application as Webservice or not??
3) How many Stores that your client have to integrate??
Please go through this guide for better Idea
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ck/te%2b-%2bpost-voided%2btransaction
ISR to Triversity Integration
Regards
Seshagiri

Can anyone explain how the LO data source flows from ECC to BI up to cubes?

Dear all,
Can anyone explain step by step (HOW THE DATA FLOWS)....By taking 2LIS_11_VAHDR from SD , starting from Activate Data source in ECC to Info Cube in BI7.0. Please this will be helpful -
Thanks for the advance answers...
Edited by: harishk.225 on Dec 23, 2011 9:56 AM

Hi Harish,
First go to RSA5 in ECC select your datasource 2LIS_11_VAHDR and activate it.
After activatin check in RSA6 whether the datasoure activated properly or not.
Then log on to BI sytem Select datasource and click on replicate.
Then Create Infocube infopackage ,Transformation, DTP ...entire flow. But dont schedule it because there is no data in SETUP Tables.For full load first we need to run statistical set up , so that data should come to SETUP Table.
Now go to ECC enter T.CODE OLI7BW to filled up the SETUP Table for datasource 2LIS_11_VAHDR.
It will ask you for Run Name etc give the run name and time limit and execute it.
If you get some error then first delete the SETUP Table by using Transaction Code LBWG.
In LBWG it will ask you for applicatiion number , give 11 i.e for sales datasourc and execute it.
Data will get deleted from SETUP Table. To check data is deleted or not in SET UP Tabe go to database table MC11VA0HDRSETUP. Always remember the name of SETUP Table will be Extract Structure followed by SETUP.
EX : If extract structure name is MC11VA0HDR then name of the SETUP Table will MC11VA0HDRSETUP.
If data gets deleted then again go to 0LI7BW and run the Statistical Setup then agan check in MC1VAOHDRSETUP table contains data or not.
Then trigger the Infopackage and DTP in BI. Above steps was for full load.
Now to Load deltas follow below steps.
First Create INIT at BI side which enable delta at ECC Side.
Then go to ECC and execute T.CODE LBWE.
LBWE is LO Cockpit Work Bench. There we have folowng functions 1.Maintan Datasource. 2.Maintain Extract Structure. 3. Job Control. 4.Delta Type 5.. Activate/deactivate.
If you want to add any new field to your datasource then to to Maintain Extract Strucutere remeber before adding or modififying datasource first we should deactivate datasource by using 5th function Activate/Deactivate.
Then select DELTA TYPE in delta type we have four types of delta. 1. Delta Queue (RSA7) 2. Queued Delta (LBWQ)
3. Unserialized (SM13) , 4. Seriaized (SM13)
If you select Delta queue then deltas drectly come to RSAT.
if you select Queued Delta deltas goes to LBWQ then you have perform V3 job by using Job Control function to move data from LBWQ to RSA7. Remeber to BI data always goes from RSA7 only.
If you select Unserealized then delta goes to SM13 again you have to perorm V3 Job to move deltas in RSA7.
Serialize update is not in used in Lo-cockpit.
There is a differerence between DELTA QUEUE , QUEUED DELTA, UNSERIALIZE UPDATE. Pls find the differences on net.
Then select your delta type and create deltas dtp in BI and start loading .
Hope this help you.
In RSA7 we have two tables delta and repeat delta, to know the functionality of this please search for the documents on net.
Regards,
Asim

Upgrading Source System to ECC 6.0 - What is my role in BI

Hi, Our Production R/3 System is being upgraded from 6.4 to ECC.60. The machine and client will remain exactly the same. Before and after the R3 Upgrade what will I have to do from a BI System Perspective?
Hope and Pray?
Thanks...

Hi......
In general, you should take care of some things when you upgrade your BW system. If it is R/3 upgrade then you should look at functional areas you use from R/3 and analyze if R/3 features you use has been changed. You can find a lot of information about new features and changes in SAP R/3 Enterprise Release 4.70 Release notes .
Before Upgrade
If you use Logistic Cockpit, please make sure that you know notes 328181, 396647, 380078.
These are absolutely prerequisit notes for using Logistic Cockpit.
Never change the extract structure (communication structure) when there is data in SM13 or in the DeltaQueue!
Never upgrade your PlugIn System when you have data in SM13 or in the DeltaQueue!
SM13 and RSA7 have ALWAYS to be EMPTY BEFORE you apply any changes to communication structures, extract structures or any referenced Data Dictionary object or BEFORE you upgrade your PlugIn system!!!
SM13 and RSA7 have to be EMPTY also when you apply PlugIn Support Packages!
After Upgrade
458305-OLTP system upgrade: What should I be aware of afterwards?
Note 458305 - OLTP: System upgrade or SP - What should I be aware of after
Note 301192 - Procedure after upgrading an R/3 source system
Note 359412, there may be some others
Some general information about R/3 upgrade you can get here:
http://www.finsvc.duke.edu/finsvc/sapr3/Training/beyondbasics/BeyondBasics.pdf
http://searchsap.techtarget.com/featuredTopic/0,290042,sid21_gci912111,00.html
Hope this helps you.....
Regards,
Debjani.....
Edited by: Debjani Mukherjee on Sep 29, 2008 10:36 PM
Edited by: Debjani Mukherjee on Sep 29, 2008 10:37 PM

E-sourcing / SPM / BW / ECC integration

Similar Messages

Maybe you are looking for