File Process in File 2 Proxy in PI 7.1

Hi
I am working on a File to Proxy scenario where File will have multiple records, When I execute the scenario whole content of the file is coming as single record,
I want to process the each record at a time from the file, Can anyone let me know how to process the each single record at a time from the file
Thanks
PR

PR,
Try to read the file as record by record. Proabably there might be some error in reading the file with your content conversion. If you can give the content conversion parameters you used and one sample file somebody can help you out PR.
Else if you want to read the whole file as one record which you think is the correct process then you may need to write either java mapping or abap mapping.
Regards,
---Satish

Similar Messages

File 2 Proxy Process in PI 7.1

working on File to Proxy Scenario and I gave the File content conversion as below. Incoming file contains 3 record structures Header, Record & Trailer File is getting processes only where there is only one record in the record structure
The error which I receive is
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 2 according to structure 'Record':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
Please suggest what needs to be done on this
Thanks
PR
Document Name : MT_TW_AK
Document NameSpace : http://aiwcd.com/Claims_Management(CM)_Rel2.0
RecordSet Name : FROISROIAcknowledgement
RecordSet Structure : Header,1,Record,*,Trailer,1
Recordset Sequence : Ascending
Recordsets Per Message : *
KeyField Name :TransactionSetID
Key Field Type : String (Case Sensitive)
IgnoreRecordsetName : true
Header.fieldNames :TransactionSetID,SenderID,ReceiverID,DateTransmissionsent,TimeTransmissionsent,OriginalTransmissionDate,OriginalTransmissionTime,TestProductionCode,InterchangeVersionID
Header.fieldFixedLengths: 3,25,25,8,6,8,6,1,5
Header.keyFieldValue : HD1
Header.lastFieldsOptional : true
Record.fieldNames :TransactionSetID,RecordSequenceNumber,DateProcessed,TimeProcessed,InsurerFEIN,ClaimAdministratorPostalCode,ClaimAdministratorFein,AcknowledgementTransactionSetID,ApplicationAcknowledgmentCode,InsuredReportNumber,ClaimAdministratorClaimNumber,JuridictionClaimNumber,MaintenanceTypeCode,MaintenanceTypeCodeDate,RequestCode,FreeFormText,NumberofErrors,MaintenanceTypeCorrectionCode,MaintenanceTypeCorrectionCodeDate,JurisdictionBranchOfficeCode,ClaimAdministratorAlternatePostalCode,NumOfErrors
Record.fieldFixedLengths: 3,9,8,6,9,9,9,3,2,25,25,25,2,8,3,60,2,2,8,2,9,19
Record.keyFieldValue : AKC
Record.lastFieldsOptional: true
Trailer.fieldNames:TransactionSetID,DetailRecordCount,TransactionCount
Trailer.fieldFixedLengths: 3,9,9
Trailer.keyFieldValue : TR2
Trailer.lastFieldsOptional : true
ignoreRecordsetName: true

Hi PR,
I see few things may need a change. First .lastFieldsOptional is obselete now and must not be used. Please see this help for this:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
> Recordsets Per Message : *
You can leave this blank
> ignoreRecordsetName: true
You have given twice. If you give once is OK.
Also the error might be saying you are missing few fields in the last. Since fixed length file if you dont have field you should have spaces in teh file. check that also. Also try to give sample file here so that somebody can help you out.
Regards,
---Satish

Unable to process file to proxy 40 mb file

Hi Friends,
I am encountering the error when i am trying to send 40 mb file via file to proxy, SAP PI Version is 7.1
Error Message in RWB:
Transmitting the message to endpoint http://p1342134dev200.test.lichtsinfotech.co.uk:50000/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/system failed,due
to:com.sap.engine.interfaces.messagingException:Error transmitting the message
over HTTP.Reason.java.io.IOException:Error writting to server.
Can anyone help on this.
Thanks,
Venkat.

Hi Venkat,
Can you check if this blog might help
Message size as source of performance bottleneck
Regards,
Mark

Manage multiple versions(ID CS,CS2,CS3,CS4) of INDD files Indesign proxy for PC

Dear scripters,
I have multiple version of ID installed in my system. I have ID CS,CS2,CS3 and CS4. While I am opening (double click) the ID CS file, automatically the file opening in CS4. For solving this problem I have searched in the forums I found there is a program called INDESIGN PROXY for MAC OSX. It manages the problems well.
Now I am in the process of developing the application same like that for windows using VB. Here is my observation about Indesign proxy.
1. While user double clicks the Indesign file the argument is not passing to the Indesign.exe, but the argument passes to the Indesign proxy. Something like this
"C:\Program Files\Adobe\Adobe InDesign CS4\InDesign.exe" "%1"
to this
"C:\Program Files\IDproxy\proxy.exe" "%1"
2. The proxy exe lists all the version of IDs in a dialog box. If user selects CS2, the proxy exe passes the command argument something like this
"C:\Program Files\Adobe\Adobe InDesign CS2\InDesign.exe" "%1"
3. Now the file will open in correct version.
I am comfort with VB forums and coding but I am struck getting the file path while user double click's the file. I short need to get the file path of "%1" argument.
I think I am detailed.
Kindly advice me how can I proceed more?
Thanks
regards
a r u l
vpublish.net

I don't think it's a mistake.
"InDesign CS4 (3.0)"
means: this is the OM for InDesign 3.0 (i.e., InDesign CS) that is contained in InDesign CS4.
Wait -- do you mean there might be a difference between "the OM for InDesign 4.0 (i.e., InDesign CS2) that is contained in InDesign CS4" and, say, "OM for InDesign 4.0 (i.e., InDesign CS2) that is contained in InDesign CS5" ?
Why on earth would anyone need that? I imagine it's not because even with versioning the 'older' scripts may not behave the same -- there must be dozens of mails about versioning not working ... I mean, if Adobe knows what causes older scripts to stop working (because, if I understand you correctly, they retroactively change it in the documentation for older versions), wouldn't it be yet easier to not cause those changes?

Combine 2 files as input for file to proxy scenario

Hello,
Is it possible to combine to files into 1 message ?
We've got 2 csv files (1 header and 1 item) and we would like to have this in 1 xi message, processed later by a proxy.
Any idea's how to do this ?
regards

Hi,
>>Never worked with BPM before, are you aware of an example somewhere that I can have a look at on the internet ?
need to search sdn.. if i find one i will paste it here
Update
http://wiki.sdn.sap.com/wiki/display/BPX/BPMPatternMultiIfconditionExplained%28stepbyStep+Procedure%29
/people/milan.thaker/blog/2008/07/23/correlation-150-runtime-behavior-of-bpm
>>what when there are several files currently waiting ? let's say 2 header files and 2 item files ? does the system know which one he has to combine ?
Say you have a file with header details for company A,B,C and another one for D,E,F... And you have two separate files for their Line items... so each Header (or line item) file will generate a instance of BPM and it will be complete for the other file to come and complete the fork step..
and here co-relation of the common field plays a role
Regards
Suraj

File to Proxy in PI 7.1

Hi
I am working on File to Proxy Scenario and I will be receiving the text file from the sender,
There are three segments in the File from the sender (Header, Record, Trailer), and need to process the single message each time,
Do I need do the content conversion to convert the Text file into the xml (Proxy),
Thanks
PR

yes, first you have to convert to a XML format your plain file. and later send the data to proxy.
Regards

File to Proxy issue

Hi Experts,
I have the following req.
sender sends CSV file to R/3 via Proxy, R/3 responds back with a msg. This response has to be sent to same location where CSV file got picked.
Iam not using BPM for this.
I got stuck while sending the response back. Message mapping is used to send the file to Proxy data type, proxy response to response format of the sender system.
In Interface mapping, i can see request, response mappings.
DO I need to have one more receiver agreement to send the resonse back as CSV file, if so what I need to put in sender Service, what I need to put in receiver service, reciever interface
or
Do I need to use BPM for this requirement??

I have tried this, but I'm getting error
From SP 19 on XI 3.0 and SP 10 on PI 7.0, a File - RFC - File ( Asynch - Synch ) scenario can be done without a BPM.
Steps:
Integration Repository
1 Outbound Synch message Interface and 1 Inbound Synch Message Interface.
Integration Directory
1. The Receiver Determination , Interface Determination will be the same as in HTTP - RFC synch scenario. Create the Sender File Adapter, Receiver RFC Adapter and Receiver File Adapter.
2. Sender Agreement will be for the Sender File Adapter. Sender Agreement uses the Synch Outbound Message Interface.
3. Receiver Agreement will be for the Receiver RFC adapter. Receievr Agreement will use the RFC as thge Inbound Message Interface.
4. We need to add a few modules in the Sender File Adapter.
Go to the Modules Tab of the Sender File Adater, and add the following modules in the same sequence,
Number - ModuleName - Type - ModuleKey
1- AF_Modules/RequestResponseBean - Local Enterprise Bean - 1
2- CallSapAdapter-Local Enterprise Bean - 2
3-AF_Modules/ResponseOnewayBean-3
Parameters
ModuleKey - ParameterName - ParameterValue
1 - passThrough - true
3-receiverChannel - Receiver File Adapter Name
3-receiverService - Receiver Business Service/ System
my question
1) How to create receiver agreement separately here.
The error I'm getting in RWB is
2008-08-05 11:16:14 Success Channel CC_FILE_SENDER_PBX: Entire file content converted to XML format
2008-08-05 11:16:14 Success Send text file "feed.csv" from FTP server "ISFTP:\sap_feed", size 479457 bytes with QoS EO
2008-08-05 11:16:14 Success RRB: entering RequestResponseBean
2008-08-05 11:16:14 Success RRB: suspending the transaction
2008-08-05 11:16:14 Success RRB: passing through ...
2008-08-05 11:16:14 Success RRB: leaving RequestResponseBean
2008-08-05 11:16:14 Success ROB: entering ResponseOnewayBean
2008-08-05 11:16:14 Success ROB: resuming the transaction
2008-08-05 11:16:14 Success ROB: calling the module processor ...
2008-08-05 11:16:14 Success MP: Entering module processor
2008-08-05 11:16:14 Success MP: Processing local module localejbs/CallSapAdapter
2008-08-05 11:16:14 Success MP: Leaving module processor
2008-08-05 11:16:14 Success ROB: returned with response: false
2008-08-05 11:16:14 Success ROB: leaving ResponseOnewayBean
2008-08-05 11:16:14 Error Attempt to process file failed with java.lang.NullPointerException

File occasionally stuck in staging on File Poller Proxy Service

Hi All,
I'm having some problems with a File Poller Proxy Service. The Proxy reads xml files in a polling shared directory and puts the message in a queue. The files are small (<1kbytes).
The problem is that occasionally the file gets stuck in the staging directory and never gets to the jms queue. If I cut the file and paste it again in the polling directory, it gets processed fine.
Any ideas?
Thanks.

I have one cluster on the web logic server with 4 managed servers in it.
The proxy runs on ms1, and the staging directory is on a different physical server shared folder.

File to Proxy Validation

Hi
I have scenario file-xi-proxy
file contains the Header detail and trailer record
i have to validate the header, detal and trailer records
In header record i have to validate if header record is not there then stop the processing and same as with tralier record. In header i have to validate on Pay roll date
In detail record i have to validate aganist the Personnel ID and cost center
how can we do that in XI
venkat

Hi,
In your scenario two ways you can validate the data.
1) Before the data reaches into SAP system ie in XI system during Mapping or before mapping i,e in Adapter Module in the Sender side
2) this option, is in the receiver applications side. ie. Validations will be taken care in the SAP system i.e in ABAP server proxy code.
Generally, it is prefer to more business critical validations in the Application System ie Receiver Application System (ABAP Server Proxy)
In this, you can have more flexibility of the validations as you are validating some of the SAP payroll informations as Personal ID etc.
Based on the complexity and flexibility of the requirement, you can either do this in the XI (if XI, ie Sender Adapter Module or Mapping) or in the ABAP proxy
Rgds,
Moorthy

File to Proxy ABAP - Split message possible?

Hi experts,
I am facing a slight problem with my scenario, I designed flat file to proxy Abap, it works fine, the problem is that my flat file tend to be a bit too large in term of volume (about 15Mo) and I would like to divide the file in multiple messages.
I managed to do that by putting in the recordset structure : NAME, 500.
It divides the file content in several messages in XI, the problem is that each Proxy call processes a program that deletes and replaces a table. Hence, it only takes in account the last message.
Is there a way to deal with that? maybe to precise that all the messages sent are part of the same source.
Kind regards,
Jamal

From your description, this program of yours is executed within a transactional context. Each execution of the program will be independent of each other.
If you need your messages to be executed within the same transaction, then you need to reunite the separate messages into a unique transaction again, meaning, you need to merge the messages back into one, or correlate them somehow.
Anyway, 15 MB is hard but not unfeasible. With proper sizing/tunning, you should be able to run it in a single execution.
But if split at XI is indeed necessary and you don't want to merge again in XI (wouldn't make much sense, would it?), you need to develop something on the receiver side (Z ABAP) to hold the entries and only when the file is finished, call the initial program.
Regards,
Henrique.

File To Proxy Error ICM HTTP CONNECTION FAILED

Dear All ,
Iam Doing File to Proxy Scenario.
XML File is picked by XI Adapter is Properly and if i go and Check in SXMB_MONI,
It is Showing Status is Scheduled for outbound processing and if i see in Que Status is stop with red symbal .If I Click on QueueID it is opening the inbound qRFC Monitoring ,there if click on Queue Name it is showing Status :SYSFAIL,If I Click on SYSFAIL it is Showing the XI Error CLIENT_RECIVE_FAILED.INTERNAL:Que Stop, If I Click on QueueName it is showing while Executing the Functiomodule SXMS_ASYNC_EXE It is having prob i thik showin Error Text :CLIENT_RECIVE_FAILED.INTERNAL:Que Stop,If I Click on Quename it is showing a program RSXMB_SELECT_MESSSAGES is Similar to our SXMB_MONI ,here it is showing the Status Falg Red ,If I Click on that message it is opening the pipeline steps , here while calling Adapter Showing red symbal giving the Error Message ICM_HTTP_CONNECTION_FAILED
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please help me its urgent.
Regards
Kumar

hi
This is the problem relleated to the HTTP connections, since using the proxy theXML travels to the destination, on your receiveing system make sure HTTP service are active.
in R/3 run this report :SPROX_CHECK_HTTP_COMMUNICATION you will get the error then proceed with the below steps to fix it.
YOur HTTP seriveces on the R/3 have some problem.....
Goto SMICM>goto>servicess you should see the HTTP service running with the ABAP port entry, if this is up then check
SICF--->press f2 you should not have any proxy check there.....
if these are fine then problem is with the Sproxy configuration........

File to Proxy Scenarion

Hi,
All Iam doing File to Proxy Scenarion.
File is picked up by XI Properly and Pushing in to R/3 also Successful.When I checked in R/3 SXMB_MONI ,My Status is Scheduled and Green status.If I go and checked in to the Trace Is giving following.
<?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="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=receiver</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SED</Trace>
<Trace level="1" type="T">client = 110</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = CSYAM</Trace>
<Trace level="1" type="Timestamp">2007-10-09T02:15:06Z CET</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 = AB0B13E0760B11DCC45100118566337F</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0008</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 *</Trace>
<Trace level="1" type="T">select interface namespace</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 MI_APAR_Proxy*</Trace>
<Trace level="1" type="T">select interface namespace http://com.starhub/FICO-BILLING-APAR</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>
</SAP:Trace>
Please help us,its urgent.
Regards
KUMAR

Hey kumar,
What you can do step by step is as follows:
1. Go to SMQ2 and ctivate/delete the queues, then re-run your scenario. If problem solved well and good.
2. If problem is not solved, then use tcode <b>SICF</b> -> F8 and check the default_host->sap--->XI. check if all the services are active or not. if active then it will be in pure black color. if not active then activate it and then your scenario. If problem solved well n good.
3. If problem is not solved yet, then use tcode <b>SM59</b> and test HTTP connectioin.
SM59 ---> open "HTTP connection to ABAP system" ---> double click on "INTEGRATION_DIRECTORY_HMI".
Now pree the connection test button and select the "Accept all further Cookies" check box and press "Yes". If test results are positive i.e. if there is no error then test your scenario and if you have problem please consult with your Basis persion.
I hope all above mention setps will resolve your problem.
Regards,
Sarvesh
*****Reward Points, if it helped you.

File to proxy ..HTTP_RESP_STATUS_CODE_NOT_OK error in sxmb_moni??

Hi friends..
in file to proxy.. i am getting error like this..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""><SAP:Category>XIServer</SAP:Category><SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code><SAP:P1>500 </SAP:P1><SAP:P2>Internal Server Error</SAP:P2><SAP:P3></SAP:P3><SAP:P4></SAP:P4><SAP:AdditionalText><html><head><title>SAP Web Application Server Error</title>
<style type="text/css">
body { font-family: arial, sans-serif;}
</style>
</head>
<BODY text="#172972" link="#808080" vlink="#808080"
alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0"
marginheight="0" marginwidth="0">
<table height="61" width="100%" border="0" cellspacing="0"
cellpadding="0"><tr><td background="http://dceazar01:8010/sap/public/icman/img/bluebar_tile.gif"
height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP Web Application Server
</font></td><td width=75% align="right" nowrap><font face=arial
size="-1" color="white"><a href="http://help.sap.com/">Help
</font></td><td width=5% nowrap></font></td> </tr></table>
</td><td rowspan=2 width=122 height=61 valign=top><img src=
"http://dceazar01:8010/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td>
</tr><tr><td background="http://dceazar01:8010/sap/public/icman/img/graybar_tile.jpg" height="31">
</td></tr>
</table>
<br><br>
<table width=800>
<tr><td width=50 nowrap>
</td><td>
<H2><b>500 Internal Server Error</b></H2><br><hr><br>Internal Server Error(-1)<br><br><hr>
<table border="0">
<tr><td>Error:</td><td>-1</td></tr>
<tr><td>Version:</td><td>6040</td></tr>
<tr><td>Component:</td><td>HTTP_PLG</td></tr>
<tr><td>Date/Time:</td><td>Sun Jan 7 12:04:44 2007
</td></tr>
<tr><td>Module:</td><td>http_plg_mt.c</td></tr>
<tr><td>Line:</td><td>3505</td></tr>
<tr><td>Server:</td><td>dceazar01_SRD_10</td></tr>
<tr><td>Detail:</td><td>No handler defined for this URL</td></tr>
</table>
<p></p>
</td></tr></table>
<table><tr><td width=50 nowrap></td>
<td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2005, SAP AG</a></FONT></td></tr></table></SAP:AdditionalText><SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage><SAP:Stack><b>HTTP response contains status code 500 with the description Internal Server Error
Error when sending by HTTP (error code: 500, error text: Internal Server Error)</b></SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
please guide me..
regards
Ram

hi friends..
trace is like this...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Party normalization: receiver </Trace>
<Trace level="1" type="T">Receiver scheme external = </Trace>
<Trace level="1" type="T">Receiver agency external = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = dcexi0602.aaaa.com:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.150.113.48</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<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>
<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 = DGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSERDGX</Trace>
<Trace level="1" type="Timestamp">2007-01-07T12:48:42Z CET </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>
<Trace level="1" type="T">Message-GUID = 6799BA809E4D11DBB72AF6C9E0007003</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>
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 6799BA809E4D11DBB72AF6C9E0007003</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 : XBTI0004</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0004</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 = 6799BA809E4D11DBB72AF6C9E0007003</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>
<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="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="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>
<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">----------------------------------------------------- </Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = DGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSERDGX</Trace>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET </Trace>
<Trace level="1" type="T">----------------------------------------------------- </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></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">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<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>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS    = 0001</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0002</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0003</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0004</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0007</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0008</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0009</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET 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>
<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>
<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 without given receiver </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: - SAP_ERP_azar_DEV </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">2007-01-07T12:48:43Z CET 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">2007-01-07T12:48:43Z CET 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>
<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>
<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) SAP_ERP_azar_DEV InterfaceCollection </Trace>
<Trace level="2" type="T">...valid InbIf without Condition: InterfaceCollection </Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET 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>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET 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>
<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>
<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>
<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 = XBTOE1__0000</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>
<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>
<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="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>
<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">----------------------------------------------------- </Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = DGX</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSERDGX</Trace>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET </Trace>
<Trace level="1" type="T">----------------------------------------------------- </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></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">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<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>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS    = 0001</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0002</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0003</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0004</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0007</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0008</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0009</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET 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">2007-01-07T12:48:43Z CET 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>
<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>
<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 is already determined in the interface determination </Trace>
<Trace level="3" type="T">Object ID of Interface Mapping DA461E413F303668931A977B9D811191 </Trace>
<Trace level="3" type="T">Version ID of Interface Mapping B2CF8EF067FF11DBA742D7830A967135 </Trace>
<Trace level="1" type="T">Mapping-Object-Id:DA461E413F303668931A977B9D811191 </Trace>
<Trace level="1" type="T">Mapping-SWCV:B2CF8EF067FF11DBA742D7830A967135 </Trace>
<Trace level="1" type="T">Mapping-Step:1 </Trace>
<Trace level="1" type="T">Mapping-Type:JAVA </Trace>
<Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_MM_M_StockMov_To_SAP_ </Trace>
<Trace level="3" type="T">Dynamic configuration is empty </Trace>
<Trace level="3" type="T">Multi mapping required. </Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_M_StockMov_To_SAP_. </Trace>
<Trace level="3" type="T">Load b2cf8ef0-67ff-11db-a742-d7830a967135, http://aaaa.com/xi/PROCESS/PPE/ERP_MES, -1, com/sap/xi/tf/_MM_M_StockMov_To_SAP_.class. </Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_M_StockMov_To_SAP_.class (http://aaaa.com/xi/PROCESS/PPE/ERP_MES, -1) in swcv b2cf8ef0-67ff-11db-a742-d7830a967135. </Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_M_StockMov_To_SAP_ completed. (executeStep() of com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
<Trace level="3" type="T">Message Type 1 Number of messages 1 </Trace>
<Trace level="3" type="T">Dynamic configuration is empty </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET 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">2007-01-07T12:48:43Z CET 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>
<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>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<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">-Bs_MES_Stock_proxy </Trace>
<Trace level="2" type="T">-SAP_ERP_azar_DEV </Trace>
<Trace level="2" type="T">http://aaaa.com/xi/PROCESS/PPE/ERP_MES.MI_IN_S_StockMov </Trace>
<Trace level="2" type="T">Channel found: - SAP_ERP_azar_DEV - CC_IN_XI_Proxy </Trace>
<Trace level="2" type="T">no header mapping defined </Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET 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>
<Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace>
<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>
<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>
<Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
<Trace level="3" type="T"> </Trace>
<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 = IENGINE</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>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
<Trace level="1" type="T">Sender: Header mapped to</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = Bs_MES_Stock_proxy</Trace>
<Trace level="1" type="T">Receiver: Header mapped to</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = SAP_ERP_azar_DEV</Trace>
<Trace level="1" type="T">Party denormalization: sender </Trace>
<Trace level="1" type="T">Sender target scheme = </Trace>
<Trace level="1" type="T">Sender target agency = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Party denormalization: receiver </Trace>
<Trace level="1" type="T">Receiver target scheme = </Trace>
<Trace level="1" type="T">Receiver target agency = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">Addressing mode: url</Trace>
<Trace level="3" type="T">Host = dceazar01</Trace>
<Trace level="3" type="T">Port = 8010</Trace>
<Trace level="3" type="T">Transport protocol = HTTP      1.0</Trace>
<Trace level="3" type="T">Message protocol = </Trace>
<Trace level="3" type="T">Path = sap/xi/engine?type=receiver</Trace>
<Trace level="2" type="T">Auth mode: basicSAP</Trace>
<Trace level="3" type="T">Conversion of language from char2 to char1 EN</Trace>
<Trace level="3" type="T">User = asar</Trace>
<Trace level="3" type="T">Client = 400</Trace>
<Trace level="3" type="T">Language = E</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 SAP </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 = 500 </Trace>
<Trace level="3" type="T">Deserializing message object... </Trace>
<Trace level="3" type="System_Error">HTTP-client: error response= <html><head><title>SAP Web Application Server Error</title>
<style type="text/css">
body { font-family: arial, sans-serif;}
</style>
</head>
<BODY text="#172972" link="#808080" vlink="#808080"
alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0"
marginheight="0" marginwidth="0">
<table height="61" width="100%" border="0" cellspacing="0"
cellpadding="0"><tr><td background="http://dceazar01:8010/sap/public/icman/img/bluebar_tile.gif"
height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP Web Application Server
</font></td><td width=75% align="right" nowrap><font face=arial
size="-1" color="white"><a href="http://help.sap.com/">Help
</font></td><td width=5% nowrap></font></td> </tr></table>
</td><td rowspan=2 width=122 height=61 valign=top><img src=
"http://dceazar01:8010/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td>
</tr><tr><td background="http://dceazar01:8010/sap/public/icman/img/graybar_tile.jpg" height="31">
</td></tr>
</table>
<br><br>
<table width=800>
<tr><td width=50 nowrap>
</td><td>
<H2><b>500 Internal Server Error</b></H2><br><hr><br>Internal Server Error(-1)<br><br><hr>
<table border="0">
<tr><td>Error:</td><td>-1</td></tr>
<tr><td>Version:</td><td>6040</td></tr>
<tr><td>Component:</td><td>HTTP_PLG</td></tr>
<tr><td>Date/Time:</td><td>Sun Jan 7 13:48:43 2007
</td></tr>
<tr><td>Module:</td><td>http_plg_mt.c</td></tr>
<tr><td>Line:</td><td>3505</td></tr>
<tr><td>Server:</td><td>dceazar01_SRD_10</td></tr>
<tr><td>Detail:</td><td>No handler defined for this URL</td></tr>
</table>
<p></p>
</td></tr></table>
<table><tr><td width=50 nowrap></td>
<td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2005, SAP AG</a></FONT></td></tr></table></Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
<Trace level="2" type="T">Switch back to normalized party (HTTP response)</Trace>
<Trace level="1" type="T">Sender scheme external = </Trace>
<Trace level="1" type="T">Sender agency external = </Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="T">Party normalization: receiver </Trace>
<Trace level="1" type="T">Receiver scheme external = </Trace>
<Trace level="1" type="T">Receiver agency external = </Trace>
<Trace level="1" type="T">Receiver party external = </Trace>
<Trace level="1" type="T">Receiver party normalized = </Trace>
<Trace level="2" type="T">Undo header mapping (HTTP response) </Trace>
<Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = Bs_MES_Stock_proxy</Trace>
<Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="1" type="T">Party = </Trace>
<Trace level="1" type="T">Agency = </Trace>
<Trace level="1" type="T">Scheme = </Trace>
<Trace level="1" type="T">Service = SAP_ERP_azar_DEV</Trace>
<Trace level="2" type="T">Sender: Header after undo of mapping</Trace>
<Trace level="2" type="T">Party = </Trace>
<Trace level="2" type="T">Agency = </Trace>
<Trace level="2" type="T">Scheme = </Trace>
<Trace level="2" type="T">Service = Bs_MES_Stock_proxy</Trace>
<Trace level="2" type="T">Receiver: Header before undo of mapping</Trace>
<Trace level="2" type="T">Party = </Trace>
<Trace level="2" type="T">Agency = </Trace>
<Trace level="2" type="T">Scheme = </Trace>
<Trace level="2" type="T">Service = SAP_ERP_azar_DEV</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>
<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>
please guide me ...
regards
Ram

PI 7.1 EHP1 - Unable to find missing file (File to Proxy) - AAE

Hi Friends,
We have one File to Proxy scenario which is configured using ICO (Integration Configuration) - AAE. In this, the MDM system places every day n number of files at 9:30 PM IST in FTP server. (No of file ex: 16180, 12500, 6000) like this. It is a one time process everyday. Our PI file channel is shceduled at 10:30 PM ISTto pick and process those files. Once all files are picked, those moved to archive directory.
Then problem is It is difference between files in archive directory and processed messages in PI. Ex:
Sep 30 --> Files --> 16179 (Archive) --> 16178 (Processed in PI), Oct 2 --> Files -->12492 (Archive) --> 12490 (PI).
Everyday 1 or 2 files are missing in PI. We set the polling interval as 2 hrs and keep the channel active for 8 hrs.
1) The file names are unique.
2) Though payload are same in some of the files, the file is processed.
The MDM log says 16179 files were exported successfully.
Is AAE miss any one file / two files ? Really it is confusing for us how to compare this and find the missing one.
Friends, could you please clarify from your experience how to solve this.
Thanking you.
Kind regards,
Jegathees P.

Hello,
Please check at PI side how much messages get processsed that day..is there any error in RWB.
Messages count in pi and MDM should match if files are processed succesfully from MDM side.
Regards
Monica
Edited by: monica bhosale on Oct 4, 2011 12:32 PM

Help Required - File to Proxy (Performance Issue)

Hi All,
One of my file to proxy scenario is taking 3 to 4 days to execute.
Basically XI picks up a file of 2-3 lakh records and pushing it to SAP via ABAP proxy. On the ABAP side, a BDC call is made to process the data. But the whole scenario takes 3 to 4 days for execution.
The scenario is an Asynch scenario and BPM is not used as its a very straight forward scenario.. Also the file can't be splitted as say each 10,000 records bcoz all of these records are interrelated and has to go to SAP end in a single shot.
Is there anything which can be done on either XI or ABAP side to optimize the scenario?.
Thanks,
Joe.

Joe,
Can you give more details?
Is this an Asynch call or a synch call?
Are you using a BPM, etc, maybe there is something wrong in the way you have designed your interface.
Proxies are supposed to provide the best perfromance and the fact that it is taking such a long time is really strange, and so maybe if you can give us details on your interface , some reason for this issue can be found out.
Meanwhile also look into this guide,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ada5ef-0201-0010-1f8b-c935e444b0ad
Regards
Bhavesh

File Process in File 2 Proxy in PI 7.1

Similar Messages

Maybe you are looking for