Error or Trace of SOA ABAP Client Prox

Hi all,
i have successfully created ABAP Client Proxy for a WebService and configured the port using LPCONFIG. There i can configure the trace level as well - but now my questeion: where do i find these traces, errors ?
Thanks for any help.
Regards,
André

Hi everybody,
Now have found out on my own that these traces goe's to the files like dev_rfc on the SAP filesystem which can be viewed with AL11. Is there any other tool to have a more user friendly view on these traces as you can not be sure in which of the 10 ore more dev_rfc trace files your errors are in.
Thanks for any help.
André

Similar Messages

ABAP Client proxies: structure/internal table error

Hi All,
We are getting following error when we check for errors in ABAP program for ABAP client proxies:
"RECORDS" is not an internal table - the "OCCURS n" specification is missing.
Let me explain the scenario and proxy objects its generated and proxy objects we are refering in program:
Its syncrounous client proxy scenario.
In XI:
We have DT_Req, MT_Req, DT_Res, MT_Res and MI_Sync_OB (O/p Message: MT_Req, I/P message:MT_Res)
Proxy Objects generated:
ZCO_MI_SYNC_OB
ZMT_REQ
ZDT_REQ
ZDT_REQ_RECORDS
ZMT_RES
ZDT_RES
ZDT_RES_RECORDS
ZDT_RES_RECORDS_TAB
ABAP Code:
REPORT ZTEST_DELETE.
DATA:
lo_history         TYPE REF TO ZCO_MI_SYNC_OB,
lo_sys_exception   TYPE REF TO cx_ai_system_fault,
Structures to set and get message content
lv_history_req_mt TYPE ZMT_REQ OCCURS 0 WITH HEADER LINE,
lv_history_res_mt TYPE ZMT_RES,
lv_history_req_rec TYPE ZDT_REQ_RECORDS,
lv_history_res_rec TYPE ZDT_RES_RECORDS.
lv_history_req_rec-VLAUE = SY-DATUM.
APPEND lv_history_req_rec TO lv_history_req_mt-MT_REQ-RECORDS.
CREATE OBJECT lo_history.
TRY.
Call outbound Proxy
    CALL METHOD lo_history->execute_synchronous
      EXPORTING
        output = lv_history_req_mt
      IMPORTING
        input = lv_history_res_mt.
Error handling
CATCH cx_ai_system_fault INTO lo_sys_exception.
    SKIP 2.
    WRITE:/ lo_sys_exception->errortext.
    RETURN.
ENDTRY.
When we execute this program we get following error:
"REC" is not an internal table - the "OCCURS n" specification is missing.
Can anybody please fogure out the why we getting this error??
We had the similar kind of scenario working. Only one difference in the proxy objects generated:
In working scenario we had the _TAB object genearated for the Req
In our current scenario _TAB proxy is generated for the Res.
Thanx
Navin

Hi Moorthy,
Everything you said is done. Still get the same error.
Hi Mario,
I tried to define with your example a, still I have problem.
I think I kind of figure out the reason.
As I mentioned in the first post (question), proxy object "ZDT_RES_RECORDS_TAB" has created for the object data type DT_RES. The fields in the data type "DT_RES" are already existing in the SAP.
The fields in the data type DT_REQ are not in the SAP, and in the proxy objects its not generated any kind of TABLE. I think this is the reason we are getting error ""RECORDS" is not an internal table - the "OCCURS n" specification is missing." either we define
lv_history_req_mt TYPE ZMT_REQ OCCURS 0 WITH HEADER LINE, OR
lv_history_req_mt TYPE ZMT_REQ,
Does it make sense what I was explaining above???
Any lead on this would be great.
Thanx
Navin

ABAP Client proxies: extract data from the response and update Z table

Hi All,
I have following ABAP code for client proxies:
We have DT_Req, MT_Req, DT_Res, MT_Res and MI_Sync_OB (O/p Message: MT_Req, I/P message:MT_Res)
Proxy Objects generated:
ZCO_MI_SYNC_OB
ZMT_REQ
ZDT_REQ
ZDT_REQ_RECORDS
ZDT_REQ_RECORDS_TAB
ZMT_RES
ZDT_RES
ZDT_RES_RECORDS
ZDT_RES_RECORDS_TAB
ABAP Code:
REPORT ZTEST_DELETE.
DATA:
lo_history TYPE REF TO ZCO_MI_SYNC_OB,
lo_sys_exception TYPE REF TO cx_ai_system_fault,
Structures to set and get message content
lv_history_req_mt TYPE ZMT_REQ OCCURS 0 WITH HEADER LINE,
lv_history_res_mt TYPE ZMT_RES,
lv_history_req_rec TYPE ZDT_REQ_RECORDS,
lv_history_res_rec TYPE ZDT_RES_RECORDS.
lv_history_req_rec-VLAUE = SY-DATUM.
APPEND lv_history_req_rec TO lv_history_req_mt-MT_REQ-RECORDS.
CREATE OBJECT lo_history.
TRY.
Call outbound Proxy
CALL METHOD lo_history->execute_synchronous
EXPORTING
output = lv_history_req_mt
IMPORTING
input = lv_history_res_mt.
Error handling
CATCH cx_ai_system_fault INTO lo_sys_exception.
SKIP 2.
WRITE:/ lo_sys_exception->errortext.
RETURN.
ENDTRY.
Now I have my response data in the internable "lv_history_res_mt-MT_REQ-RECORDS" which is deep structure.
How do I extract data records (multiple) from the above internal table and update to Z table??
Thanx
Navin

Hi Navin,
go to SPROXY, flag structure and search for your table definition. You will find a table definition a field "line" or something, where you find the right structure. Create a new structure with DATA: myStructure type tableStructure. Define a second structure type with your Ztable. Next Loop at internal table into the structure. Inside that loop fill the Zstructure. Insert the Zstrucure (Press F1 on insert to have the syntax you need)
loop at internalTable into intStructure.
zstructure-myField = intStructure-myField.
INSERT ztable FROM zstructure.
endloop.
Regards,
Udo

Soap 1.2 in ABAP client proxies

Hi!
Anyone knows when we will have SOAP 1.2 support in the standalone ABAP proxies. Currently in NW7.0 only SOAP 1.1 seems to be supported (right?).
Information on MTOM, SOAP w. attachments support for standalone ABAP prixies would also be useful...
Regards,
Christian

Hi Andreas,
SOAP 1.2 is not supported, neither in WebAS 6.20 nor in 6.40 as far as I know support is not planed even for next magor release...
The only what I can propose you is to create an OSS and check what shall SAP answer you,
or to downport your applicaiton.
Regards, Angel

Problems with 'COMMIT MISSING' - when using ABAP client proxies

Hi
We have a requirement - wherein while SAP std inbound IDOCs are being processed in the R/3 system- we need to monitor the processing of idocs - by sending relevant information out of the R3 system to a monitoring dashboard - outside of the R/3 environment.
Inorder to accomplish the above, we generated a async. client proxy class in the R3 system by pointing to a XI o/b message interface and that interface mapped on to DB calls - from which the dashboard was bringing up status of idocs being processed in R3
We made a call to the async class method from within the idoc user exit that lies within IDOC_INPUT_ORDERS FM . The user exit chosen to make the call was - after the salesorder processing for the inbound idoc was done in the above FM. We have not given any COMMIT WORK statement after the async client proxy method call within the user exit - since the call was being made from within user exit and we did not want to upset SAP std processing flow.
Now, when the inbound idoc processing is being done by using SAP std program rbdapp01 using parallel processing option of packets, the outbound message generated is in 'COMMIT MISSING' status - whereas - when rbdapp01 is executed in normal mode - the proxy message is sent out ok out of the R3 integration engine.
The program rbdapp01 has a COMMIT WORK statement after each IDOC packet is processed - but still with the parallel processing option - the proxy message stays in th R3 box - with the status 'COMMIT MISSING'
Any thoughts/ pointers on this is appreciated....

Hi Karthik,
I don't think you can get this to work using an asynchronous proxy - except perhaps by spawning an update task to send the data.
Perhaps you can re-cast this as a synchronous interface?
Regards,
Thorsten

ABAP client proxy from WSDL

I have 2 problems in creating abap client proxies using wsdl
1.when i try to create client proxy by giving RPC style wsdl(generated by SAP itself for a RFC) the system throws an error and not allowing to create the proxy
2.The client proxy which i have created for a wsdl(either SAP created document type/any wsdl from commercial websites) gives an error "No receiver could be found"
could somebody please clarify and help me to solve the problem.
Thanks in advance.
Vasanth.

Hi Vasanth,
There are many threads and blogs on this topic.
Choose the search Forum on the Forum page and select "All categories" in the Category field and enter your topic "ABAP client proxy from WSDL" in the search field.
Rgds,
Sam Raju

ABAP Client Proxy without XI

Hello
I am stuggling with writing a client proxy in ABAP to call a Web Service without any use of XI. The help says it is possible, as per the URL below.
On the expanded tree structure on the left pane of the help, navigate to the heading "Programming with Client and Server Proxies" and then "Sending a message".
I have been able to generate a proxy class by consuming a WSDL file and I have also defined a Logical Port.
I have also copied the ABAP code shown on the same Help page, but have been stumped by the definition of ls_request and ls_response. The next line of help goes on to explain that ls_request should be a structure for the Request Message. In the scenario where XI is used, I can understand the concept of defining a structure that is the same as the Request message.
In the scenario of only using ABAP and no XI, I don't understand what I should define the structures for ls_request and ls_response.
Can anyone shed some light on my confusion? Any suggestions gratefully received.
Thanks in advance
tony<a href="http://help.sap.com/saphelp_nw04/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm">SAP Help on ABAP Client Proxies</a>

Welcome to SDN.
check out this weblog.
<a href="/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap">Consuming WebServices with ABAP</a>
input and output structure are automatically generated when creating the client proxy.
click on the structure tab (se80 client proxy definition) and expand the webservice method againt input in the type column you should see a structure name use this for ls_request
ls_request TYPE zxxx_soap_in,
against exporting in types column you can see the type for ls_response.
Hope this is clear.
Regards
Raja

ABAP Server Proxies-- any help docs..?

Hi,
Only after completing my ABAP Client proxies, i found that there was a weblog on it. Now i am trying Server Proxies, i want to maximize the use of SDN. So can somebody tell me where there any any blogs posted on server proxies...?
kindly provide me the good links for Server proxies.
Regards,
Christina.

Hi,
For server proxies,
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Also refer to:
http://help.sap.com/saphelp_nw04/helpdata/en/62/8a5f3c31727d59e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
Regards,
Sridhar
Message was edited by: Sridhar Rajan Natarajan

Error With ABAP Client proxy

Hi All,
 I am trying to use ABAP Client Proxy(Sync). I am getting the error.
1. Message from SXMB_ADMIN on Business system.
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="400" p2="ICM_HTTP_CONNECTION_FAILED" p3="" p4="">HTTP.HTTP_CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:Text language="EN">Error during http receive: Error code: 400 Error text: ICM_HTTP_CONNECTION_FAILED</SAP:Text>
</SAP:ErrorHeader>
2. No message On XI server.
3.Went through the Ravikumar Allampallam's blog
on ABAP ClientProxy .
4. Went through the vijaya kumari's " How do you activate ABAP Proxies?"
5. created connections (sld)and one http connections in SM59. Tested the connections.
6. Went throught the Forms.
Any help would be appriaciated.
Thank you
Ganges Leaves.

Vijaya Kumari,
 1. I have checked it. For XI server these are the values.
 Business System Role : Integration Server.
 Pipe Line url : http://server:8000/sap/xi/engine?type=entry.
8000 is the http port which i see in the SMICM+shift F1.
Thank you
Ganges Leaves

HTTP Error with Status code 403 when using ABAP Server Proxies

Hi All,
I have been working on ABAP Client and Server proxies in my project. The weblogs by Ravikumar, Prateek Shah, Siva Maranani & VijayaKumari were very helpful and thank them all for just helpful and guiding postings.
Interfaces using Client proxies are working fine and have been tested successfully. But I'm facing bit problems with Server Proxies. The scenario is of File to SAP system via XI. Data is coming correct up to Technical routing in pipeline but at call adapter(for Server Proxy to SAP)in XI pipeline I receive Error:
HTTP response contains status code 403 with the description Business Server Page (BSP) Error Error when sending by HTTP (error code: 403, error text: Business Server Page (BSP) Error)
Previously I was receiving authentication and authorization related error of status code 401 and then in communication channel I replaced user profile with a user id having role SAP_XI_APPL_SERV_USER. The basis peron has created new user id with role SAP_XI_APPL_SERV_USER only and that I'm using. I've tried creating a HTTP destination with the created user id and in test connection too receive same error message.
Please help me out with your inputs and understanding on the topic.
Thanks and Best Regards
Prashant Rajani

Hi Prashant,
Please take a look at these threads..They deal with the same problem, and they have been resolved here.
BSP Authorization error
Service cannot be reached . error code 403 the reason forbiddn
403 Error when accessing the server
Hope your issue gets resolved.
cheers,
Prashanth
P.S Please mark helpful answers

ABAP client proxy 401 error

Hi i have generated a ABAP client proxy in my ECC system and sending an outbound message to XI. i get the following error.
HTTP response contains status code 401 with the description Unauthorized Error while sending by HTTP (error code: 401, error text: Unauthorized)
I have tested the following.
1) My sld and ECC system have the integration engine and pipeline settings for the XI Server: http://server:8000/sap/xi/engine?type=entry
2) logon to the URL http://server:8000/sap/xi/engine with user XIAPPLUSER and pwd in the browser because of the error 'Der Aufruf der URL http://server:8000/sap/xi/engine wurde aufgrund fehlerhafter Anmeldedaten abgebrochen'
any sugestions ? using a proxy as target works fine

Hi ,
You seem to have a problem with the XIAPPLUSER logon. Can you check that the user has the appropriate authorizations? Maybe the user is locked? Maybe the password has been incorrectly entered?
XIAPPLUSER should have the role SAP_XI_APPL_SERV_USER.
Also, check that the XI engine service has been activated.
Transaction SICF. Default_host->sap->xi Activate the entire node with all subtrees.
Cheers
Manish

ABAP server and client proxies

Dear All,
what is the diff between ABAP server and client proxies?
Regards,
Ashish goyal

Hi Ashish,
Client proxy means proxy in Sender System, and Server Proxy means proxy in Receiver System.
Have a look to the following links:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm">ABAP Proxy Runtime</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/c9/74246d8ad2447799063d39013e9a11/frameset.htm">Programming with Client and Server Proxies</a>
ABAP Proxies in XI(Client Proxy)
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
ABAP Server Proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Hope this help
Francesco

Problem in ABAP Client Proxy

Hai All,
I am working on ABAP Client Proxy to RFC.
Here i generated the proxies and wen i execute it i am able to see in sxmb_moni but its showing in Green color which is still in process.but i was unable to find the the receiver business system and receiver interface.
I hope some HTTP connection problem.
Can anyone explain me in detail how to create the http connection as i confused here.
Lets say XI(sender) to R3(Receievr)
where proxy is been created in XI system itself and also generated in XI system only.
Can anyone suggets me here as this interface is totally asynchronous.
Thanks,
Kalyan.

Hai Seshagiri,
Thanks a lot.
Am giving you points buddy.Its working.
Cud u plz give me ur Email id.
This is fine but i want implement this interface to further there i am getting errors.So that i can send u the screenshots of those.
Thanks,
Kalyan.
Please read the Forum's Rules of Engagement,
i.e.,
[/thread/117188 [original link is broken];
and refrain from using email correspondence as the main objective of the Forums is to share knowledge.
SDN PI/XI Forum Moderator

ABAP Client Proxy to File (File is not getting generated)

Hi All,
I'm trying out a scenario ABAP proxy --> XI --> FILE.
I have followed the given blog to create ABAP client proxy.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
While executing the ABAP client proxy, the values are properly sent to XI and in the SXMB_MONI the message shows as successful. But the correspoding file is not created.
It seems everything is fine in the receiver adpater(Monitoring) and in the SXMB_MONI also the msg shows successful(receiver side).
The directory path and the corresping file creation parameters also looks fine.
Couldn't figure out what went wrong. Please help me on this.
Thanks,
Ajay.

Hi Smitha,
Please find below the Call Adapter trace
<?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 =</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="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = iscsapapp4w:8010</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="2" type="T">Remote address = 10.191.117.166</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="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 = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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 = B2DD6D78BBF141458DDC0DDE39782DE3</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 = B2DD6D78BBF141458DDC0DDE39782DE3</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 : XBTI0000</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0000</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 = B2DD6D78BBF141458DDC0DDE39782DE3</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="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 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 = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</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">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 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 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 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 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 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 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 level="3" type="T" />
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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 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 without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - ACN_LEGACY2_04_BS</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">2006-04-03T10:24:14Z 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">2006-04-03T10:24:14Z 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 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) ACN_LEGACY2_04_BS MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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 level="1" type="Timestamp">2006-04-03T10:24:14Z 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 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 = XBTOM2__0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="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 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 = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</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">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 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 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 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 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 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 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 level="3" type="T" />
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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">2006-04-03T10:24:14Z 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 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 is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 791955998E03380CA938A0130A348AFB</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 3475AE80930811DAA18DC14C0ABF75A6</Trace>
<Trace level="1" type="T">Interface Mapping http://accenture.com/xi101/ABAPclientProxy IM_Valuemapping</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_Valuemapping_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_Valuemapping_.</Trace>
<Trace level="3" type="T">Load 3475ae80-9308-11da-a18d-c14c0abf75a6, http://accenture.com/xi101/ABAPclientProxy, -1, com/sap/xi/tf/_MM_Valuemapping_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_Valuemapping_.class (http://accenture.com/xi101/ABAPclientProxy, -1) in swcv 3475ae80-9308-11da-a18d-c14c0abf75a6.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_Valuemapping_ completed. (executeStep() of com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z 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">2006-04-03T10:24:15Z 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 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">-ACN_Sender_BS_XI</Trace>
<Trace level="2" type="T">-ACN_LEGACY2_04_BS</Trace>
<Trace level="2" type="T">http://accenture.com/xi101/ABAPclientProxy.MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">Channel found: - ACN_LEGACY2_04_BS - ValueMap_Repl_Receiver1</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z 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 level="1" type="Timestamp">2006-04-03T10:24:15Z CET 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: File</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: File</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): af.nw2.iscsapapp4w</Trace>
<Trace level="3" type="T">URL = http://iscsapapp4w.idcsap.com:51000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = XIISUSER</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>
<Trace level="1" type="Timestamp">2006-04-03T10:24:19Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</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>
</SAP:Trace>
Thanks,
Jothivel.

Error is encountered during import ABAP phase

Hi All,
When trying to install ECC6 on windows 2003 server the below error is encountered during import ABAP phase....Can any one help me in this regard.
CJS-30022 Program 'Migration Monitor' exists
ERROR 2009-07-08 08:39:33
CJS-30022 Program 'Migration Monitor' exits with error code 103.
For details see log file(s) import_monitor.java.log, import_monitor.log.
Thanks
Sandeep Singh DS

hi,
Below are the logs for import_monitor.log and import_monitor.java.log
import_monitor.log :
TRACE: 2009-07-11 21:11:30 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2009-07-11 21:11:30 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
D:\usr\sap\EP2\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error
TRACE: 2009-07-11 21:11:30 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2009-07-11 21:11:30 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
D:\usr\sap\EP2\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -stop_on_error
ERROR: 2009-07-11 21:12:38 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process 'D:\usr\sap\EP2\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL1.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2009-07-11 21:15:10 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'D:\usr\sap\EP2\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2009-07-11 21:15:30
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-07-11 21:15:30
2 error(s) during processing of packages.
import_monitor.java.log
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 2, completed 16, failed 0, total 19.
Import Monitor jobs: running 2, waiting 1, completed 16, failed 0, total 19.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 16, failed 1, total 19.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 16, failed 2, total 19.
Thanks,
Sandeep
Edited by: Sandeep Singh DeviSingh on Jul 13, 2009 11:42 AM

Error or Trace of SOA ABAP Client Prox

Similar Messages

Maybe you are looking for