Problem in SOAP to IDOC & File scenario
Hi,
My scenario is SOAP ->IDOC and FILE,when I run the scenario IDOc was processed and File was not created at the target system.I maintained LS name for sender SOAP and IDOC business service.Nothing was maintained in adapter spec identifiers for Recer business service(i.e For target File CC).This was working fine in Dev.After Importing another scenario which uses same business service,this didnt stp working?
what could be the reason?
Thanks,
RP
Edited by: RP@261 on Oct 21, 2008 10:59 PM
> my imported scenario and existing scenario in QA using same sender business service.After importing the other scenario,existing scenario is failed to create files at target system even though it shows successful in MONI.
>
Check the target dir permission once again from your BASIS team. Reconfirm the the target dir name in receiver CC also.
> Should we maintain Logical system in adapter specific identifiers for Recr File CC also??? I create a file in BI application server from recr File CC.
>
No, for creating a file you don't require this. This is required only in case of IDOC.
> my scenario is
> (SOAP sender) --> TO IDOC & FILE ..i maintained LS name in sender BS where SOAP CC is created and also at Recr BS where IDoc CC is created. The other Recr BS for File where I didn't.IS it required ?
>
For File recever BS, No need.
Similar Messages
-
IDoc- File scenario: can you explain thses acknowledgments?
Hi,
I have an idoc->file scenario. in sxmb_moni I can see a green "OK" mark for my message in acknowldgment status column. when I dblclick the message, I can see my original message and 2 acknowldgment messages under this one in the top left.
1 acknowledgement is the OK one, the 2nd one is of type AckNotSupported.
When I dlbclick the OK one ack and click the idocoutbound, I can see:
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>450</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000257842</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
and when I dblclick the 2nd ack and IdocOutbound, I see:
<SAP:MANDT>450</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000257862</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
<SAP:MESCOD />
450 is the client of my IE, not the sender SAP system.
What should all this mean? What does each ack mean and why do I get 2 of them?
When I check the Idoc no. in XI, there is no such IDoc. Where are these Idocs sent from?
POINTS WILL BE ASSIGN FOR SURE FOR CORRECT ANSWER.
Thanks, Oliangreen:
hoplist
<?xml version="1.0" encoding="UTF-8"?>
<!-- Response -->
<SAP:HopList SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
<SAP:Engine type="IS"/>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>
<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
<SAP:Info>ARTMAS.0000000000026370:20080610211506</SAP:Info>
</SAP:Hop>
<SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
<SAP:Engine type="IS">is.12.shlxiqcis1</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
<SAP:Hop timeStamp="2008-06-10T21:15:13Z" wasRead="true">
<SAP:Engine type="AE">af.xiq.shlr3qdbs3</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
<SAP:Info/>
</SAP:Hop>
</SAP:HopList>
content
<?xml version="1.0" encoding="UTF-8"?>
<!-- Response -->
<SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>350</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000258080</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP/>
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
<SAP:MESCOD/>
<SAP:MESFCT/>
<SAP:SNDPOR>SAPXIQ</SAP:SNDPOR>
<SAP:SNDPRN>SHLSYSQAS</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC/>
<SAP:RCVPOR>SAPR3Q</SAP:RCVPOR>
<SAP:RCVPRN>R3QCLNT330</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC/>
<SAP:TEST/>
<SAP:SERIAL/>
<SAP:EXPRSS/>
<SAP:STD/>
<SAP:STDVRS/>
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD/>
<SAP:SNDSAD/>
<SAP:SNDLAD/>
<SAP:RCVSAD/>
<SAP:RCVLAD/>
<SAP:STDMES/>
<SAP:REFINT/>
<SAP:REFGRP/>
<SAP:REFMES/>
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY/>
</SAP:IDocOutbound>
Red one:
<?xml version="1.0" encoding="UTF-8"?>
<!-- Response -->
<SAP:HopList SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
<SAP:Engine type="IS"/>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>
<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
<SAP:Info>ARTMAS.0000000000026370:20080610211506</SAP:Info>
</SAP:Hop>
<SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
<SAP:Engine type="IS">is.12.shlxiqcis1</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
<SAP:Hop timeStamp="2008-06-10T21:15:13Z" wasRead="true">
<SAP:Engine type="AE">af.xiq.shlr3qdbs3</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
<SAP:Info/>
</SAP:Hop>
</SAP:HopList>
content
<?xml version="1.0" encoding="UTF-8"?>
<!-- Response -->
<SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>350</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000258083</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
<SAP:CIMTYP/>
<SAP:MESTYP>ALEAUD</SAP:MESTYP>
<SAP:MESCOD/>
<SAP:MESFCT/>
<SAP:SNDPOR>SAPXIQ</SAP:SNDPOR>
<SAP:SNDPRN>SHLSYSQAS</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC/>
<SAP:RCVPOR>SAPR3Q</SAP:RCVPOR>
<SAP:RCVPRN>R3QCLNT330</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC/>
<SAP:TEST/>
<SAP:SERIAL/>
<SAP:EXPRSS/>
<SAP:STD/>
<SAP:STDVRS/>
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD/>
<SAP:SNDSAD/>
<SAP:SNDLAD/>
<SAP:RCVSAD/>
<SAP:RCVLAD/>
<SAP:STDMES/>
<SAP:REFINT/>
<SAP:REFGRP/>
<SAP:REFMES/>
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY/>
</SAP:IDocOutbound> -
Production Time Issues on IDOC---File Scenario
Hi All,
We have done all the IDOC--File scenarios Successfully in DEV System.
Now its time to Production and Go-Live.
Q1) Assume If Bulk messages are Failed in RWB-----Receiver CC Due to some error, Then how to Handle these Error messages
Regards
SumanHi Mahesh,
This is My Trace File
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- <!-- ************************************
-->
<Trace level="1" type="T">User: 116866</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="2" type="T">Tunneling needed?</Trace>
<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
<Trace level="3" type="T">Sender Interface</Trace>
<Trace level="3" type="T">WP_PLU.WP_PLU03 urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPPIS</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
<Trace level="2" type="T">Port : SAPPIS</Trace>
<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">RFCDest :</Trace>
<Trace level="2" type="T">Release : 700</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Direct : 1</Trace>
<Trace level="2" type="T">SAPREL : 700</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
<Trace level="2" type="T">Port : SAPPIS</Trace>
<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
<Trace level="2" type="T">Cimtyp :</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">Create XML-Control Record</Trace>
<Trace level="2" type="T">Create XML-Data Records</Trace>
<Trace level="3" type="T">Create data Record E1WPA01</Trace>
<Trace level="3" type="T">Create data Record E1WPA02</Trace>
<Trace level="3" type="T">Create data Record E1WPA03</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA04</Trace>
<Trace level="3" type="T">Create data Record E1WPA05</Trace>
<Trace level="3" type="T">Create data Record E1WPA07</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
<Trace level="3" type="T">Create data Record E1WXX01</Trace>
</Trace>
<Trace level="2" type="T">party-scheme: ALE#KU</Trace>
<Trace level="1" type="T">party normalization error: scheme = ALE#KU</Trace>
<Trace level="2" type="T">Set Sender Routing-object</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<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="3" type="T">system-ID = PSX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = 116866</Trace>
<Trace level="1" type="Timestamp">2008-05-05T13:15:27Z INDIA</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 = 481ADC34F6CF1214E1000000AC10100D</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 481ADC34F6CF1214E1000000AC10100D</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0001</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0001</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 481ADC34F6CF1214E1000000AC10100D</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface WP_PLU.WP_PLU03*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition 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="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</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 CENTRAL</Trace>
<Trace level="3" type="T">system-ID = PSX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = 116866</Trace>
<Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA</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 CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start with given receiver C086 -</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - BS_Soap_Service_Qty</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_Soap_Service_Qty MI_POS_Itemmaster_OB</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_POS_Itemmaster_OB</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO0___0002</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</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">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="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</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 CENTRAL</Trace>
<Trace level="3" type="T">system-ID = PSX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = 116866</Trace>
<Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA</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 CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping C5523ABE7D9A35BDABE2082468D67E41</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 1FB1D8C0010B11DD9AB1F535AC101018</Trace>
<Trace level="1" type="T">Interface Mapping http://sub-sapretail-pos.com/Itemmaster IM_POS_Itemmaster_OB</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_POS_Itemmaster_multi_OB_</Trace>
<Trace level="3" type="T">Dynamic Configuration ( http://sap.com/xi/XI/System/IDoc SNDPOR SAPPIS ) ( http://sap.com/xi/XI/System/IDoc SNDPRN PISCLNT900 ) ( http://sap.com/xi/XI/System/IDoc SNDPRT LS ) ( http://sap.com/xi/XI/System/IDoc RCVPOR A000000015 ) ( http://sap.com/xi/XI/System/IDoc RCVPRN C086 ) ( http://sap.com/xi/XI/System/IDoc RCVPRT KU ) ( http://sap.com/xi/XI/System/IDoc MESTYP WP_PLU ) ( http://sap.com/xi/XI/System/IDoc IDOCTYP WP_PLU03 ) ( http://sap.com/xi/XI/System/IDoc CIMTYP )</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_POS_Itemmaster_multi_OB_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_POS_Itemmaster_multi_OB_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_POS_Itemmaster_multi_OB_ completed. (executeStep() of com.sap.xi.tf._MM_POS_Itemmaster_multi_OB_</Trace>
<Trace level="3" type="T">Dynamic Configuration ( http://sap.com/xi/XI/System/IDoc RCVPOR A000000015 ) ( http://sap.com/xi/XI/System/IDoc SNDPRT LS ) ( http://sap.com/xi/XI/System/IDoc RCVPRN C086 ) ( http://sap.com/xi/XI/System/IDoc SNDPOR SAPPIS ) ( http://sap.com/xi/XI/System/IDoc SNDPRN PISCLNT900 ) ( http://sap.com/xi/XI/System/IDoc CIMTYP ) ( http://sap.com/xi/XI/System/IDoc IDOCTYP WP_PLU03 ) ( http://sap.com/xi/XI/System/IDoc MESTYP WP_PLU ) ( http://sap.com/xi/XI/System/IDoc RCVPRT KU )</Trace>
<Trace level="1" type="T">ContentType application/xml</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-Subhiksha_PIS_subprd1</Trace>
<Trace level="2" type="T">-BS_Soap_Service_Qty</Trace>
<Trace level="2" type="T">http://sub-sapretail-pos.com/Itemmaster.MI_POS_Itemmaster_OB</Trace>
<Trace level="2" type="T">Channel found: - BS_Soap_Service_Qty - CC_POS_Itemmaster_OB_Qty</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Unknown channel type: SOAP</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: SOAP</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">return fresh values from cache</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="3" type="T">URL = http://psxprd:51000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = PIISUSER</Trace>
<Trace level="3" type="T">Cached = X</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Regards
Suman -
Hallo Everybody,
In one of the requirements,for the interface design which involves IDOC-FILE scenario we have a req as:-
Multiple IDOCs would be sent from SAP R/3 to SAP XI. Each IDOC can have 0-4 segments and for each segment a file needs to created.
The files needs to be FTPed to a location, only if all the IDOCs have been processed successfully.
Requirement:
1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
2) We need to send a notification from XI, in case any IDOC processing fails.
3) How do we check in XI, if all the IDOCs have been processed successfully.
Please suggest me with some good stategies to resolve this issue.
Appreciations and Rewards in line.
Regards,
YounusHi
Are you planning to use BPM as it suits your requirement.
To collect the idocs in small bunches refer
Collecting IDocs without using BPM
1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
BPM will allow you to wait for the time all IDOC are processed
2) We need to send a notification from XI, in case any IDOC processing fails.
BPM exception handling will allow this functionality even to the exact field you want to send notification
3) How do we check in XI, if all the IDOCs have been processed successfully.
Set Acknowledgment for IDOC's
refer
Posting multiple IDocs with Acknowledgement
Thanks
Gaurav -
Soap -- XI -- IDOC/RFC scenario
Hello,
I have a jsp page that working in tomcat server.
I want to send values from jsp page to xi to r/3. I think it will have
soap-- xi -- IDOC/RFC scenario
Pls send me pdf /doc to implemet it
RegardsHi,
Please Refer the Following Links
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Regards
Khanna -
Hello,
I am doing IDOC - File scenario.
(source is DEBMAS and reciever end, there is flat DT with no heirarchies as of now. )
The requirement is that if the segment at the source side has multiple lines of " sold to party " values, then customer bill should also have multiple lines with account number different for each line. Can I acheive this using "split by value"? if yes please help me.
Regards,
HarithaUse the sold-to-party node to create the row node of the file...if some of the elements in the sold to party node have to duplicated/repeated use the one as many function.
-
Dear SDN,
We have to develop something like this:
An IDoc is generated from an ABAP Business System. Using content based routing conditions the IDoc must be sent to different FTP servers. The problem is that the IDoc must be written in its "native plain" format, not in XML format.
Any ideas?hi Gustavo,
2 ways
1. https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
2. send the idoc from R3 in native IDOC (file port) and just tranport it via XI
both ways will produce native IDOC:)
for file ports you can check out my book
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a> -
How to use a existing Business Service in IDoc-File Scenario
Hi Experts,
I am new to XI.
I am working on a IDoc to File scenario where in i am importing the CREMAS.CREMAS03 IDoc from the R/3 System.
When i try to create a Business Service in Configuration Scenario Object in Integartion Directory, i get a message saying "SAP system ID ER1 and client 800 already exist in service | CLNT800ER1".
Can i reuse this Business Servie in my Configuration Object?
If yes, can you please guide me How to go about it?
Thanks for the effort.
Cheers
Gaurav RaghavU may directly use it.
Just select the business service wherever required. It is not necessary that the Business Service is present in ur configuration scenario. But if u still want it, u may add it using "Add to Scenario" option from other configuration scenario or from Objects tab
Regards,
Prateek -
IDoc output type not getting configured in IDoc-File scenario
Hello
I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
1] Created output type
2] Created partner function as EDI LS for this output type
3] Configured RSNASTED as Processing Routines for output type
4] Included this output type in the Header output procedure
5] Configured XI system as the partner in partner profile with appropriate Message control
Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
I checked in SPRO but could not find such flag.
Does anyone had came across such output type configuration.
Thanks in advance.
I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
Regards
RajeevHi,
Please check the following
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Copy NEU to ZNEU or YNEU
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
G.Ganesh Kumar -
Idoc- File scenario: Read a data field in IDOC and name the file with it
Hi All,
I am configuring an IDOC to File scenario.
I have a requirement where I need to read one of the IDOC data field and use that as the name of the File.
E.g: If the IDOC data field-1 = '123456', then I need to name the output file as '123456'.
Is it possible to do this. Appreciate your help on same.
Thanks
ShirinTry this code..
desired field from IDoc will be input parameter to UDF
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
conf.put(key,a); // a is input parameter
String ourSourceFileName = conf.get(key);
return ourSourceFileName;
Also, check Adapter specific message attributes in file adapter, check filename -
Segment filtering in IDoc -File scenario
Hello
I am currently working on IDoc to File scenario where I am distributing changes in materials to legacy systems. For the same I am using MATMAS IDoc and planning to use change pointers to track the changes of the same.
The scenario is working fine but from fine-tuning perspective can i filter some of the segments from IDoc because I am hardly using few data from MATMAS IDoc.I checked the distribution model in R3 but i guess it allows us to define data filters.
Thanks in advance.
Regards
Rajeevhi,
thanks for the reply but i found one transaction in SAP BD56 where I guess we can specify segments to be filtered.
Regards
Rajeev -
Mapping issue from Invoice (Idoc - file) scenario
Dear All,
I am working on Idoc to File scenario and i have a requirement like..
INVOICE02
E1EDP01
E1EDP05
BETRG
E1EDP05
KSCHL
BETRG etc
condition :
If KSCHL not equals to space then map all BETRG's to a target field which is not mandatory. Sometimes E1EDP05 may not contain KSCHL and when i set the context to E1EDP05 level its not considering the BETRG values, it behaving lik taking up the condition part and summing part seperately.
It would be really great if anybody comes up with some ideas.
Thanks a lot
HariKSCHL ----> exists
-----------------------> And ------->ifWithoutElse -------------> Target
KSCHL Then(BETRG)
-------> equalS ---> Not
Constant(blank)
Context of KSCHL should be above that of E1EDP05
I hope that Target node is repeating -
0...unbounded.
Regards,
Abhishek. -
HOW TO TEST SOAP SENDER TO FILE SCENARIO
Hi gurus,
I have designed and configured SOAP to file scenario.
I have used http://xyz namespace in design time.
I have created two business systems for this sceanrio.
I have downloaded and installed soap client on my system.
When I open this soap client it is asking
1)URL
2)load request from
3)In the editor request tab what should i give.
4)wht is the response tab here
I want to send data to XI from SOAP and then to file.
Please help how to give data and how to get the data format to give in the requst editor?
Points will B rewarded
Regards
SreeniHi,
You can use a SOAP client like Altova XML spy for posting a message to XI.
The best way to do this is to use the generated wsdl for creating a soap request.
once the wsdl file is picked up by the soap client, it automatically generates the url.
now the response which comes back to the soap client is usually a http status code of successful post. (since u r performing an async scenario)
also ensure u use the j2ee port while genrating the wsdl using the "Create Webservice" option in Int Directory.
Also chk the link for the weblog on sender soap scenario.
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
Hope this helps.
Award points if found helpful
Cheers!!
Sidharth -
Corrupt XML file encoding utf-8 special chars (IDOC - File scenario)
Dear experts,
I have a problem with the XML output files of XI and could not find the answer in one of the current posts.
I'm sending Master Data from R/3 with IDOCs through XI to a FTP directory. These files include characters as Á, Ê, etc.
The XI server includes the utf-8 encoding in the output XML message. However, when opening these files I receive errors (tried it in multiple programs). It tells me that Á is not utf-8.
It will not accepts Á. I was under the impression that utf-8 included extended Latin and thus would accept these characters. Thus implying that the message was created wrong. Also importing these files into MDM import manager gives errors.
All rfc destinations are on Unicode.
By the way, we experience the same problem when syndicating files from the MDM server.
Any suggestions?
Cheers.
* Will reward points for helpful answers.Hi,
Check out this guide..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
make use of the messagetransformbean - http://help.sap.com/saphelp_nw04/helpdata/en/57/0b2c4142aef623e10000000a155106/content.htm
Also for further ref: go thru this thread - Change encoding from utf-8 to iso-8859-1 in JMS receiver!
regards
sasi.........
<b>Reward if useful</b> -
Problem with Idoc-file scenario
Hi Sdn
In my scenario I am sending data from R/3 using Idoc.I am using Change Pointer in SAP side. My receiver adapter is File adapter, generating a .CSV file.
Now whenever there is ny change in the data in SAP side, Idoc will get triggered and data will come to XI and file will get generated. Now the requirement is, the file shud contain only the changed data with header ,other fields shoud be blank and comma-separated. I don't have ny receiver file structure.
my questions:
1. How much helpful is 'file content conversion' in this case??
2. if mapping is required, how can we do the mapping??
3. Is there any standard mapping function, so that we can check every field with condition and then map them (1:1)?
plz help me.
Thanx in advance.> Hi Sdn
>
> In my scenario I am sending data from R/3 using
> Idoc.I am using Change Pointer in SAP side. My
> receiver adapter is File adapter, generating a .CSV
> file.
> Now whenever there is ny change in the data in SAP
> side, Idoc will get triggered and data will come to
> XI and file will get generated. Now the requirement
> is, the file shud contain only the changed data with
> header ,other fields shoud be blank and
> comma-separated. I don't have ny receiver file
> structure.
>
> my questions:
>
> 1. How much helpful is 'file content conversion' in
> this case??
You have to use it in order to convert to csv
> 2. if mapping is required, how can we do the
> mapping??
in message mapping
> 3. Is there any standard mapping function, so that we
> can check every field with condition and then map
> them (1:1)?
you can use 'if' or ifWithoutElse to check the condition
> plz help me.
> Thanx in advance.
Maybe you are looking for
-
Can I use one subscription of Acrobat Pro XI for my 3 different computers I use?
Can I use one subscription of Acrobat Pro XI for my 3 different computers I use?
-
HT1349 I bought my sons' I-Pod. How do I erase his music and apps and add my own?
I just bought my son's I-pod touch. How do I erase his music and apps and addmy own? Thanks, Dulciejo
-
LINK TO GET DATA FROM Oracle9i Spatial
Hi estimated friends In this moment I am carrying out some tests of functionality with Maps created in MapInfo to load them into Oracle9i Spatial. I have loaded data to Oracle from MapInfo without any trouble, when I do it the EasyLoader create a .ta
-
Error in displaying master page content in overflowing pages
Hi All, I am having a master page with logo, bill to party address and item details. The logo and bill to party are in a separate sub form of the master page and the item details are in the design view of the page. My problem is when the item details
-
Creating hyperlinks between articles in InDesign DPS
Hi, Having trouble getting text hyperlinks between articles to work when uploaded to the iPad, the hyperlink was created from text with a navto:articlename url in the hyperlinks panel. I am using CS5.5 and folio builder 1.1.3, if anyone could point m