IDOC to WS Synchronous Scenario Without BPM

Hi Experts,
I am dealing with Idoc to WS synchronous scenario. Can this be done without BPM??
ALEAUD can make IDOC to handle WS response??
Please suggest.
Regards,
Sushama

Please suggest since BPM involves performance issue
BPM surely has performance issue...only when there are a lot of steps/ logic implemented in it and when the processing load is too much for the XI/ PI server to handle.
The BPM design in your case will be just of following steps: Receive --> SyncSend --> AsyncSend .... excluding Transformation...and a BPM with these steps wont cause a big harm to processing of other messages.
Regards,
Abhishek.

Similar Messages

IDoc to soap synchronous scenario with BPM

Hi,
I am working on IDoc to soap synchronous scenario using BPM. Here i am facing lot of soap exceptions in my production system. I handled the exceptions. The data getting excuted for the first time, the same data(just changed the description)is giving exceptions for the second time. Please let me know why the exceptions are getting, and different type of exceptions and solutions for the same.(Blog also is fine)
Thanks & Regards,
Pragathi.

The data getting excuted for the first time, the same data(just changed the description)is giving exceptions for the second
time.
Ideally you should not get an exception for the same data....can you tell is the description and where are you getting the exception...is it a part of the SOAP message or some object?
An exception might have occured because the description would be something unacceptable by the target application.
and different type of exceptions and solutions for the same
there would be many blogs....your thread would be spammed...better make a search on SDN with exception text that you are getting.
Regards,
Abhishek.

Correlation issue in JMS adapter - SYNC/ASYNC scenario without BPM

Hi,
I am working on a SYNC/ASYNC scenario with JMS adapter without using BPM. My scenario is SOAP<>PI>JMS. I configured the interface as below:
1. SOAP Sender channel
2. JMS Receiver Channel writing to Queue A.
 Module used: a. RequestOneWayBean
 b. WaitResponseBean
 Correlation Settings:
 a. Set JMS Correlation ID to "XI Message ID"
 b. Store JMS CorrelationID of request (Checked)
 c. Set JMS Property to "JMS Correlation Id"
 d. Value = "XI MEssage ID"
3. JMS Sender channel reading from queue B ( I am exporting the message from queue A and importing into queue B)
 Module used: a. NotifyResponseBean
 Correlation Settings:
 a. Set XI MEssage Id to "GUID"
 b. Set XI Conversation ID to "Stored JMS COrrelationID of Request"
I can see the cid in the message from queue A. But I observed thhat the header format of the message in Queue A is "MQSTR".
ISSUE:
1. While writing the message to queue A, below adapter log details(part b) concerned me:
 a. Message '8747a7c2-2b06-11df-8055-005056a70ed6' successfully processed by channel
 b. Could not create acknowledgements for message '8747a7c2-2b06-11df-8055-005056a70ed6'
I am not sure why I am receiving the message that " could not create acknowledgements"
2. While reading the message from the sender channel,I consistently get the error message as below:
 a. XI message ID corresponding to JMS message with ID 'ID:414d51205341504449442e514d202020c67b954b20005602'
 will be created as a new GUID with value '21bca916-424f-41f6-3347-c71090392b58'
 b. Error while processing message '21bca916-424f-41f6-3347-c71090392b58'; detailed error description:
 com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
 found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
Below are the blogs which I have already gone through:
1. JMS Synchronous Scenario without BPM - Correlation Settings and Transactional JMS Session
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
2. Note: 1086303
3. Sync / Async Bridge without BPM
In the note, they mentioned something about header being "MQRFH2". BUt in our case, the header is "MSSTR". Not sure whether it makes any difference.
Please help.
Edited by: GP on Mar 9, 2010 4:24 AM

Hi,
detailed error description:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
This error would generally arose when there are multiple messages, got stuck in the outbound queue. Try to stop both the sender and receiver JMS comunication channels and clear both the inbound and outbound queues.
Once all the messages in the queue are cleraed, try posting the message again.
Regards,
Swetha.

SOAP to IDoc scenario without BPM

Hi,
I have 2 scenario's
1) IDoc-SOAP - -response -- IDoc scenario -- (have found some links to do it without BPM)
2) SOAP -- RFC request -- RFC response -- e-mail (no links found)
how can i achive both these scenario's without BPM. Currently i have these 2 scenarios in our 7.1 version with BPM. but our requirement is to migrate this scenario into 7.4 without BPM(No PO).
please help us to achive this scenario without BPM.
Your help is highly appreciated.
thanks,
Praveen

Hi Kiran,
Could you please let us know the exact requirement. How do you want to send the response back to IDOC?
ASync - Sync Bridge with IDOC sender is not possible in PI 7.0.
If It is something like IDOC --> SOAP --> IDOC , And If the SOAP request is small then you can use SOAP Lookup in IDOC to IDOC Scenario.
In The mapping You can do a lookup and get the response from SOAP(Webservice) and map that to your Target IDOC.
This is one possible way for you without BPM in PI7.0.
Please let me know if you need more details about this.
Thanks
Jyothi A

Error handling in File - XI - SOAP scenario without BPM

Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, Tanja

Hi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo

IDOC to SOAP synchronous scenario

Hi All,
We have an IDOC to SOAP synchronous scenario in which IDOCs are sent to SOAP by calling a service and then SOAP sends a response back to XI . The response is not sent to SAP- R3. Please suggest on this
Thanks

Hello Rajesh,
Thanks for your good justification.
Here I have also replicated same kind of scenario and having same kind of issue.
One thing just wanted to confirm - Even though SOAP adapter expects HTTP 200 response back from webservice, still SOAP channel is getting into red with following , and as we have Alert configured ...Alert mail also receiving as part of Error only. So How can we avoid that response ? Is there have any parameter to handle or suppress the response back?
Thanks!
Goutam

Synch-asynch scenario without bpm's?

Synch-asynch scenario without bpmu2019s can any one help me how to configure this scenario without bpms?

hi ferocious,
That is possible with standard functions and standard module beans.
Possiable1:
From pi 7.1 v , sap provided standard functions like RFC and jdbc of the conversion function group.
Possiable2:
sap provided Standard module beans those are RequestResopnceBean and OnewayResponceBean.
thanks,
bhavanisankar.

Message Split -- File to Idoc Scenario - ( Without BPM )

I have multiple records coming to XI in a File and I have to create Multiple Idocs to R/3.
Due to Complexity of mapping I'm splitting Maaping step into 2 message Mappings.
A-->B
B-->C
In the 2nd Mapping step I'm doing message Split meaning for each Source record I'm creating multiple Idocs ( To be precise each record on the source becomes 4 idocs in the Target.
2nd Mapping step is as follows
Source 1..1
Sourcerecord 0.. Unbounded
 field1 0..1
 field2 0..1
 filed3 0..1
Target
Message 1
 Idoc 1.. Unbounded
 Idoc Structure..
Message 2
 Idoc 1.. Unbounded
Message 3
 Idoc 1.. Unbounded
Message 4
 Idoc 1.. Unbounded
So based on some criteria each record of Source will be mapped to 4 Messages ( 1 each under each Message )
Is it possible to do this without BPM?. Iam sending all these Idocs to same R/3 System.
Thanks for any help..RK

Hi,
See the blog
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Basicly we have 2 ways of handling such scenarios:
- we can use a block step and send multiple IDOCs from our BPM
- we can also do a little trick and send multiple IDOCs from the XI without a BPM
The first approach is a standard XI approach. It involves the use of a BPM
so the speed of this transfer many not be very good in case you'd like to send
hundreds or thousands of IDOCs in just one call.
The second approach uses a little trick that was mentioned several times
on the XI Froum by a number of XI developers but is still not very clear to the XI newbies.
It allows us to send multiple IDOCs without the use of a BPM. Most probably this will be your choice
if you'd like to use such 1:N (IDOCs) scenarios effectively.
Please see the bwlow threads also..
IDOC Splitting
File To IDOC Thru XI
Multi-Mappings in BPM (XI 3.0)
Please let me know , your prob..is solcev or not..
Regards
Chilla..

Multiple IDOC to Multiple IDOC scenario without BPM steps????

Hi
Could you please give me the solution for this ???
I want steps for sending all IDOCs at a time- ---"Multiple IDOC to Multiple IDOC scenario without using BPM".???
thanks
3nadh

Hello,
Refer the below, for certain details!
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi ALE configuration for pushing idocs from SAP to XI
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change XI: IDOC bundling - the "trick" with the occurance change
Regards,
Jilan

Collect IDocs to Single Request message without BPM

Hi Experts,
My scenario is IDoc to SOAP.
PI receives multiple IDoc with same message type. ECC pushed bundled IDOcs to PI via HTTP port.
Ex: <CLFMAS>
 <IDOC1>
 <IDOC2>
 <IDOC3>
The receiver is SOAP channel.
I would like to achieve mentioned output structure without BPM.
Input Structure:
<CLFMAS>1..1
 <IDOC1> 1..999999
 <Employee>1..1
 <EmpID1>1..1
 <Location>0..999
 <JAPAN>0..1
 <Location>
 <FRANCE>
 <Location>
 <BRAZIL>
 </IDOC1>
 <IDOC2>
 <Employee>
 <EmpID2>
 <Location>
 <BRAZIL>
 <Location>
 <JAPAN>
 <Location>
 <USA>
 </IDOC2>
</CLFMAS>
Output structure:
<RequestMessage>1..1
 <GroupListType>1..1
 <GroupList>0..Unbounded
 <JAPAN>1..1
 <EmpID1>0..Unbounded
 <EmpID2>
 <GroupList>
 <BRAZIL>
 <EmpID1>
 <EmpID2>
 </GroupListType>
</RequestMessage>
Pointers will be very helpful.
Thanks
Ray..
Edited by: RayPIUS on Oct 16, 2011 6:21 AM

HI,
-> you go with IDOC packaging concept. we have three approaches collecting idocs,
 1. by using tRFC port
 we need create rfc destination(SM59) and port of tRFC(WE21) and ccreate partner profile(WE20), in partner profile we have to specify the packet size.
 then coming to PI in ID we need to create sender communication channel for IDOC there we have to provide packet size.
2.by using XMLFILE PORT
 Please refer this blog it will help you
 Collecting IDocs without using BPM
3.by using XML HTTP PORT
please go through this blog i hope this will help you
-> IN PI we have message packaging concept.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c?quicklink=index&overridelayout=true
regards,
ganesh.

Synchronous transmission without BPM process

Right now I have a S/A bridge BPM process for HTTP => XI => RFC interface.
However this is taking 5 - 8 seconds to process. On further analysing this process, we found out that WF engine is taking 4 seconds in initialize.
Can I accomplish a synchronous interface without a BPM?

Hi Parimala,
If it just a HTTP>XI>RFC Scenario, it can be achieved without a BPM.
Steps in IR
1) Create DT,MT and MI(both request and response)for HTTP interface
2) Import metadata for RFC Interface into "Import Objects"
3) Create two Message Mappings
1) HTTP REq-->RFCREQ
2) RFC Res-->HTTP Res
4) Create IM for with both REq and RES maps
Steps in ID
1) Create HTTP Business Service. As HTTP Adapter is a built in adapter no CC needed.
2) Add the BS for R/3 and create the Receiver CC for RFC Adapter
3)Create Routing Rules using RD,ID,RA with Receiver CC
Use HTTP Client App to test this.
Hope this helps.
Rgds,
Sam Raju

IDOC to JDBC synchronous scenario

Hi All,
We have the following requirement:
Idoc will be sent from ECC to SAP PI and from PI we update MS SQL server using JDBC receiver adapter synchronously and get the insert/update count as response and send this response back to ECC as ALEAUD or SYSTSTATUS idoc along with the initial IDOC number. So that status of the original idoc gets updated at ECC side.
We have SAP PI 7.31 single stack system.
Following are my queries:
- Can this be achieved using BPM?
- with BPM, how can we send the original IDOC number in the status IDOC which we send back to ECC, is it through correlation feature ?
- Can this be achieved without BPM?
-- How can we send the original IDOC number in the status idoc which we send back to ECC, without using BPM?
Kindly help with suggestions.
Thanks,
Jane

Hi,
Using BPM you can capture the source IDoc no and also response from d/b(insert/update count) using 2:1 mapping in BPM (source IDoc,Resp-->Target IDoc).
Try the below alternative if you don't want to go for BPM.
Use request response bean and use
"GetPayloadValuebean" ,RemovePayloadValueBeanto store the IDoc no in request flow and remove the same from payload while passing to target system .
PutPayloadValueBean to retrieve the saved IDoc no and put it in response structure .Now in response flow you can pass as per your wish
Sync-Async without ccBPM - Process Integration - SCN Wiki
Insert value from Request message to Response message using GetPayloadValueBean and PutPayloadValueBean
Regards
Venkat

Two mappings in one scenario without bpm

Hi,
I am using two different mappings.
Output of one mapping is acting as an input for other mapping i.e source message for second mapping.
Is it possible to do this scenario without using bpm?

hi,
have a look how it works from my weblog:
/people/michal.krawczyk2/blog/2005/11/01/xi-xml-node-into-a-string-with-graphical-mapping
you can use any mapping but you need to
be aware how to input and output structures look like:
https://weblogs.sdn.sap.com/weblogs/images/34500/1_xslt_pierwszy.JPG
BTW
target structure is only checked if you use
graphical mapping
if you use abap or java mappings your target structure
will not be checked (if it's valid) as it is with
graphical mapping
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

JDBC - JavaProxy - JDBC (Synchronous) Interface without BPM ?

Hi,
I was reading the following Blog
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file-rfc-file%28without+bpm%29&
I want to know that, is it possible to develop an interface like below without using BPM :
JDBC - JavaProxy - JDBC
Can we use the same approach as mentioned in above Wiki post for this scenario also.
Regards
Kulwinder

Hello Everyone,
JDBC - JavaProxy - JDBC Sync scenario works using modules similar to File or Jms adapter.
Thanks.

Doubt on Syn/Asyn Bridge scenario without BPM

I followed the how to guide How To Realize a sync-async and async-sync bridge within the Adapter Framework,but issue still exists.
Its a File(QoS:BE)<=>Idoc scenario
1 File adapter sends a sync booking request to idoc(MSG type: FLIGHTBOOKING_CREATEANDRESP)
2 The idoc creates a booking in its system and then sends a async confirmation response(MSG type:
FLIGHTBOOKING_SENDRESPONSE) to the sender(sync file adapter)
In ID, there are 2 receiver determinations and 2 IF determinations for the request and the response.
Sender business system: NWB_FileSystem_XML
Sender CC: Syn_SenderChannel_FileXML
 Parameters Tab
Qos:BE
Poll Interval(secs) : 60
Processing Mode: Delete (Successfully processed files are deleted)
Adapter-Specific Message Attributes: Select File name
Module Tab
Processing Sequence
 AF_Modules/DynamicConfigurationBean 0
 AF_Modules/RequestOnewayBean 1
 CallSapAdapter 2
 AF_Modules/WaitResponseBean 3
Module Configuration
 0 key.0 write http://sap.com/xi/XI/System/File FileName
 0 value.0 message.correlationId
 1 passThrough true
 3 timeout 40000
Receiver CC: Dummy_ReceiverChannel_FileXML
 Parameters Tab
 Adapter-Specific Message Attributes: Select File name
Module Tab
Processing Sequence
 AF_Modules/DynamicConfigurationBean 0
 AF_Modules/NotifyResponseBean 1
Module Configuration
 0 key.0 read http://sap.com/xi/XI/System/File FileName
 0 value.0 message.correlationId
 1 timeout 40000
Receiver business system: nwb_107
Receiver CC: GeneratedReceiverChannel_Idoc
Agreements
Sender Agreement for NWB_FileSystem_XML uses CC: Syn_SenderChannel_FileXML
Receiver Agreement for NWB_FileSystem_XML uses CC: GeneratedReceiverChannel_Idoc
Receiver Agreement for nwb_107 uses CC: Dummy_ReceiverChannel_FileXML
The problems is:
The scenario only executes once and there are 2 XML messages in SXI_MONITOR with status Processed successfully.One of the message from idoc to file has the Acknowledgement MSG status still awaiting acknowledgement
In the runtime workbench,the status of CC:Syn_SenderChannel_FileXML is correctly configured and started.The latest Processing Details of Syn_SenderChannel_FileXML is 3/13/07 9:13:12 PM Processing started
Regards
Ming

The trace of the message from IDOC to File in SXI_MONITOR:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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: PIAPPLUSER</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="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 SAPNWB</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>
<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="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 = NWB</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-03-13T13:13:12Z UTC+8</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 = DBD16497D8475CF186920017314ECFFB</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="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="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0007</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0007</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 sender interface action determination</Trace>
<Trace level="1" type="T">select interface FLIGHTBOOKING_SENDRESPONSE.FLIGHTBOOKING_SENDRESPONSE01*</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="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">system-ID = NWB</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-03-13T13:13:12Z UTC+8</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="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <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="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>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <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="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>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <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="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<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 = XBTO6___0001</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="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">system-ID = NWB</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-03-13T13:13:12Z UTC+8</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="1" type="T">Corresponding internal pipeline SAP_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="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="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">Interface Mapping http://sap.com/xi/XI/Demo/Agency FBOConfirmation_AirlineIDoc2Agency</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <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="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<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="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = NWB</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2007-03-13T13:13:13Z UTC+8</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

IDOC to WS Synchronous Scenario Without BPM

Similar Messages

Maybe you are looking for