IDoc- XI scenario (IDoc should be sent by XI client 500)
Hi,
I'd like to set up a scenario mentioned in the subject. As a source SAP system I'd like to use XI client 500. XI client 100 is used as Integration Engine. How can I generate some IDoc from the source SAP system (XI cl 500) to import it into the repository?
Or do I have to use the R/3 as the source system?
Do you know some helpful links about the IDoc creation and so on?
Thanx, Peter
Hi Peter,
To import idocs in the IR, you need to perform the followinf steps:
1) In a SWCV you have a field Imported objects, right click on the link which then shows import of import of SAP objects, please click on that.
2) A window appears which for <b>Application Server, Systenm number, Username and Password.</b> Please check the system name and its client before moving further. It should be XIserver and client--500 in your case. If it's not there then double click on your SWCV and change it.
3) Enter the values in these fields, for example system number would be the same as it is given in the SAP logon window.
3) Here you can see links for IDOCs and RFCs and you can import the IDOC you want.
Hope this solves your problem.
Thanks and Regards,
Varun Joshi
Similar Messages
-
Issues in IDoc Sender Scenario:IDoc with errors added
Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
ChilankaHi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<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> -
IDoc Collection Scenario (IDoc to Mail Interface)
Hi,
I am configuring IDoc to Mail Scenario using BPM.
I gone through following link for develop the scenario. I am still unable to complete the scenario.
Collect Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
I have done following steps in my configuration. Please correct my steps if i am wrong.
Source is Outbound Invoice IDoc (SAP System).
Target is Inbound EDI 810 format send as a email(Mail System).
1. Create an Abstract Interface for Invoice IDoc(MI_IDoc_ABS)
2. Create a Message Interface for EDI 810 for Inbound(MI_EDI810_IN)
3. Create an Abstract Interface for EDI 810(MI_EDI810_ABS)
4. Message Mapping between Outbound IDoc and Abstract Invoice IDoc. I did this as per one of the above link. but did not understand the importance of this. On Message tab of Message Mapping, it shows the occurance as 1 for both source and target. I did not see the mention of this mapping in the BPM. Not sure if this was required?(MM_IDoc_ABS)
5. Message mapping between Abstract Invoice IDoc to Abstract EDI 810. On the message tab of message mapping, occurance of Source message is changed to 0-unbounded and occurance of target is kept as 1.(MM_EDI810_ABS)
6. Define Interface Mapping for above mappings
a) IM_IDoc_ABS - Outbound Invoice IDoc + MI_IDoc_ABS
MM_IDoc_ABS
b) IM_EDI810_ABS - MI_IDoc_ABS + MI_EDI810_ABS
MM_EDI810_ABS
7. Create a BPM in Integration process. Define 3 Containers namely
a) collectIDoc - Abstract Interface - MI_IDoc_ABS
b) collectIDocList - Abstract Interface - MI_IDoc_ABS(Multiline)
c) targetFile - Abstract Interface - MI_EDI810_ABS
8. Create a Block and define a infinite while loop with Block. Condition to be defined as (1=1)
9. Define a deadline block withing Block with duration = 5minutes
10. Define a Correlation in Correlation editor as SNDPOR as a ID.
11. Define a recieve step inside infinite while loop with following properties
Message = collectIDoc
Start Process = Checked
Use Correlation = Correlation
Activate Correlation = Correlation
Correlation
SNDPOR = collectIDoc./INVOIC02/IDOC/EDI_DC40/SNDPOR
12. Define Container operation next to recieve step. properties are
Target = collectIDocList
Operation = Append
expression = collectIDoc
13. Outside the block, there is Transformation Step with following properties
Interface Mapping = IM_EDI810_ABS
Source message = collectIDocList
Target message = targetFile
Acknowledgement = None
Reciever From = Send Context
Now the next step is to define Communication Channel and Receiver determination, Interface determination in the Integration Directory.
I don't know, how to go further on these steps.
In addition, could you please validate my above steps.
I appreciate your help.
Thanks,
GowriHi Bhavesh,
Thanks for the directions and help. I appreciate your help. I understand the steps but i am unable to implement it.
I have few more questions on above answer.
a) Do i have to create Sender Agreement?
b) Do i have to import bmp process in Integration Process in Integration Directory?
The steps that i carried out in Integration Directory.
1. Create a Scenario EDI810_Scenario
2. Create a party called EDI810_Party and EDI810_Service.
3. In EDI810_Service, Receiver tab has interfaces defined. MI_EDI_IN and MI_IDoc_ABS. In sender tab, it is INVOIC.INVOICE02 (IDoc) and MI_EDI810_ABS.
4. Define a receiver communication channel CC_EDI810_Receiver(RFC).
5. Business System for SAP is defined in Service without Party.
6. Defined Sender communication channel CC_IDoc_Sender(IDoc)
7. Create Interface Determination (First)
Properties are
Sender Service : SAP Business System
Sender Interface : INVOIC.INVOICE02 (IDoc)
Sender Namespace : IDoc namespace
Receiver Party : EDI810_Party
Receiver Service : EDI810_Service
Configured Inbound Interface is
MI_IDoc_ABS and IM_IDoc_ABS
8. Create Interface Determination Determination (Second)
Properties are
Sender Service : BPM_IP (Bpm process is imported in Integratio directory)
Sender Interface : MI_EDI810_ABS
Receiver Party : EDI810_Party
Receiver Service : EDI810_Service
Configured Inbound Interface is
MI_EDI_IN. I do not see IM_EDI_ABS in the list. How do i get that.
What step did i miss?
Thanks,
Gowri -
Missing response message in Idoc - WS scenario
Hello
I 'm missing a response message in the follwing scenario:
Idoc-> XI -> Web service (SOAP)
A Matmas idoc is sent from R/3 to XI. In XI the Idoc is
mapped to a SOAP message and sent to a web service.
The Message Interface for the SOAP call is synchronous
and has a PushMaterialSoapOut and a PushMaterialSoapIn
messsage, which is defined in the WSDL from the
web service and imported into XI Repository.
Everything is working fine but I do not get the response
message. The web service has sent the response message. I
have traced the firewall logs and i have seen the
response.
What is wrong? Is it basically possible to have a
scenario like this?
The message must have arrived somewhere, since the web
server does not throw an exception. But where is it?
Thank you in advance
ThomasHello Stefan
>Scenarios with IDOCs are always async. Therefore you
>cannot have a response.
Ok, so I have to use BPM.
>How do you want to process the response? What should
>happen in the sender system?
I was thinking about an ALEAUD idoc which is sent back
to R/3. Therefor I have created an synchronous message
interface with the MATMAS idoc as outgoing message and an
ALEAUD as incoming message. Accordingly I have a message
mapping for the response message.
An other reaction to the response message could be to set
the message to status failed. But this is the next issue.
>In some scenarios you might use a BAPI instead of an
>IDOC for synchronous message processing, but this
>depends of many circumstance depending ofyour business
>requirement.
The process in SAP R/3 is fixed. To move to BAPI is not
an option.
Regards
Thomas -
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 -
I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k -
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> -
Scenario: Idoc - XI - external system (Idoc)
Hello,
I am trying to send an idoc from an sap 4.6c system to an external system. The external system is supporting idcos with trfc. This scenario is currently working with ALE. Now i have to set XI between these two systems.
My problem is to set up the communication channel in the integration builder (configuration) for the external system. The idoc is waitung in XI to transport. So the step XI-> external system causing problems.
My settings are:
adapter type: idoc
transport protocol: idoc
message protocol: idoc
adapter engine: integration engine
rfc destination: xyz (is working fine)
interface version: sap release 4.0 or higher
port: ??
sap release 46c
My problem is the port. should i set up a port in idx1? But the external system is not an sap system and so i dont have a client.
In XI i have defined a port in transaction we21 (transactional rfc) for the external system with rfc destination xyz. But if i enter that port in communication channel i got error messages.
Thanks for any help.Hi christian,
i'm also working in IDOC scenario between ECC to XI to MDM, if u have any document or snapshot then pls fwd it to me.
[email protected]
Thanks,
Jitendra -
IDoc Packaging in IDoc 2 IDoc Scenario
Hi every one,
Can anyone please throw some light on the following:
Use of Idoc packaging in an Idoc2Idoc scenario. I dont have any clue about this.
Reg,This should be rather straight forward, if you are using XI to pass IDocs from system to system then you actually don't really have to do any mapping. There are some other good discussions on this topic:
idoc to idoc
IDOC packaging
Re: IDOC to IDOC Scenario
This is a good document on the topic:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
You can import the IDoc data types and go about creating the rest of your scenario, usnig the IDoc adapters and ALE
I would definitely also check out this document on configuring the IDoc adapter:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098 -
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 -
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> -
Doubt about RFC Destination in FILE to IDOC Async scenario
hi
In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
Any specific reason.
Thanks in advance.First you need to have a clear understading of how the idoc adapters works.
In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
Hope this answers your ques.
cheers
*Raj*
*POINTS IF SATISFIED WITH ANSWER. -
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. -
Synchronous IDoc - SOAP scenario
Hi all,
Our current scenario is like this: SAP (Idoc) -> XI -> SOAP (Idoc). The receiver system will reply with an ALEAUD Idoc as in: legacy (IDoc over SOAP) -> XI -> SAP IDoc).
We have a requirement to wait with sending the next IDoc from XI to receiver Web Service on legacy side until we get an ALEAUD IDoc back for the previous IDoc sent to the Web Service.
How can we implement this?
Is BPM necessary?
As far as I know you can only set the QoS for sender adapters, and the SAP Idoc scenarios are always asynchronous. But we can implement a synchronous send step in a BPM with ALEAUD as response message. This will solve our problem, correct?
Any other way? We would like to avoid using BPM.
Any help with this is highly appreciated!
Br,
KennethThanks for your reply, Udo:)
I am currently building the BPM now.
So, you are saying that I cannot create an inbound sync MI with input message IDOC and response message ALEAUD?
We want to send ACC_GL_POSTING IDoc (or identical structure) to a Web Service and receive the ALEAUD from the legacy system through a Web Service published on XI. We want to relate these two so that the BPM finishes when it receives the ALEAUD, and can then send the next ACC_GL_POSTING IDoc.
I have created the following objects in repository:
MI_ACCGLPOSTING_ASY_ABS (in receive step in BPM)
MI_ACCGLPOSTING_ALEAUD_SYN_ABS (in send step in BPM)
MI_ACCGLPOSTING_ALEAUD_SYN_IN (used for receiver interface towards legacy SOAP adapter)
MI_ALEAUD_ASY_ABS (used for send step in BPM)
I believe no mappings are necessary since we are not doing any conversions.
Can you please confirm that this looks correct, and also provide what settings I need in Directory?
Thanks a bunch!
-Kenneth -
IDoc acknowledgement scenario using ALEAUD01 IDoc type
Hi All,
I have a query, regarding IDoc acknowledgement scenario using ALEAUD01 IDoc type as mentioned below.
In a scenario where we configure and send ALEAUD01 to sender as acknowledgement of the IDoc’s received, is there any way how do we make sure that IDoc’s received by target SAP system has sent the acknowledgement successfully. Would there be any key information in the ALEAUD01 IDoc, which refers to the IDoc/data sent?
Thanks
RajendraI needed 24 seconds to know the answer
I took the word ALEAUD01 into Google and added site:help.sap.com in the search field
Among the first 10 results was one with the subject
Acknowledgment Messages
one click to open and skimming through the text ....
And opening one of the other hits in Google told me even which field is having this info
Maybe you are looking for
-
Memory not recognized on MSI Neo4 Platinum SLI
I just installed another 512mb of RAM on this system: MSI Neo4 Platinum SLI 2 x 512mb Corsair XMS XL PRO 1 x 512mb Corsair XMS XL (the one that doesnt work) IDE HDD Windows XP PRO BIOS, and every program i run that can see system specs shows that the
-
Canon S750 printer not working after upgrading to Leopard
Leopard is brilliant, and everything works after I upgraded from Tiger except... my Canon S750 printer gives error messages and fails to print. This is VERY annoying. I can't seem to find an S750 driver for OS X 10.5 on Canon's web site. So, what to
-
Oracle Portal in other Languages
We are running Oracle Portal 9.0.4.1, we are trying to explore Oracle Portal in other languages, Can you please share which all languages can Portal be implemented? Documentation if any and other useful information. Regards Murali
-
Convert Eclipse ME project to Java ME SDK 3.0
Hi I've created a j2me midlet in eclipse and would now like to import or convert the project to use with new Java ME SDK 3.0. Any help would be appreciated? Thanks
-
E-Commerce 5 - changes not visible after Check In
Hello all, I have made some changes to a few .jsp files on the SHRWEB development components. To do so we did the following procedure . Our Basis created a track and I imported it to the Netweaver. I created a project for the inactive version of the