File to RFC set up
Hi Guys,
I am setting up a FTP to RFC (SAP ECC 6.0) set up using PI 7.0.
Is there any guideline that I am look up ?
Regards
Freddy
hi,
>>>Is there any guideline that I am look up ?
yes - you need to start with searching first
Regards,
Michal Krawczyk
Similar Messages
-
ERROR IN FILE--XI--RFC SCENARIO. BAPI did not UPDATE the DATABASE TABLE
Hi
I have created a scenario FILE -XI- RFC
File is picked by file adapter - Its working fine
I have used BPM
In RFC side i used BAPI_INCOMINGINVOICE_CREATE
Its working fine and return an Invoice Number and Fisical year .
When i Check this in the R/3 System , in Invoice no Does not Exist .
Message mapping is ok
SXMB_MONI all are ok
Receiver file i got the invoice no and fisical year .
The Problem is " DATABASE TABLE DID NOT UPDATED "
So should i do BAPI_COMMIT seperately ........
Any solution ................
VERY VERY URGENT .....
thanks in advance
B.Judehi jude,
Commit Control for Single BAPI Calls
If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values , S, I, and W are displayed. All other values are regarded as errors.
To change this setting, set the indicator BAPI Advanced Mode.
<b>In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.</b>
Regards,
Mandeep Virk -
Hi Experts,
I have a requirement of FILE TO RFC (BAPI_ABC) synchronous .Everything is ok with it.
But Once I have called BAPI_ABC, I need to call BAPI_TRANSACTION_COMMIT and pass it the hardcoded string u201CXu201D to save the changes made in SAP.
For this in Target Side of mapping i have called this bapi after BAPI_ABC. this wont work.
because with synchronous intefaces we can't do multimapping(1..2)
now when will I call this comit bapi,?
and What will be the probable solution for it.
Shall I use BPM or Proxy. but my client requirement is "everything should be done in PI side only"
Kindly reply it with your best.
Regards,
SumitHello,
I had similar problem and i could resolve this issue with help of SAP Note 1342143 - RFC Adapter: WAIT during call to BAPI_TRANSACTION_COMMIT.
So all you need it is to set up next:
In receiver RFC adapter
Check "Advanced Mode"
Check "Commit Handling for Single BAPI Calls"
Add the following Name-Value pair to the table:
Name: BAPICommitWait
Value: true
BR,
Dzmitry -
File to RFC synchronous scenario stopped Picking the files
Hi Experts,
We have a File to RFC synchronous scenario. Till yesterday night it is working fine.
But suddenly it is stooped working.In moni, i can see the failed messages with the Mapping error " Can not create target element, values missing in the queue context "
No Payload in moni / communication channel monitoring / Message monitoring. I've noticed that, wrong files placed in the To-be- processed files and the adapter picked those files and failed in mapping.
I tried by stop and start the communication channel / did some dummy changes in the communication channel and activated. cleared the cache.
But still the communication channel is not working.when i stop and start the communication channel it will try to process the wrong files and failed.
Give me your valuable inputs to resolve this issue.
Regards
Bhargava krishnaHi Bharghav,
Please go through the below,
Symptom
FTP Adapter is being used in the business scenario for message processing.
During file processing it is noticed, that the FTP sender channel stops
polling. There is no error in the channel monitor or the trace/log files
and the polling jobs are correctly displayed in the AFW scheduler table.
The issue is observed after a network connection issue with the FTP server.
In order to remove the hanging locks from the FTP Adapter, the parameter
'ftp.timeout' setting is required to be set, which releases the lock once
the timeout value is expired. But in the above situation, the value for the
'ftp.timeout' is not taken properly while establishing the data connection
by File Adapter.
Other terms
FTP Adapter, sender, FTP, adapter, timeout, stalled, network, hang, polling
Reason and Prerequisites
Program error
Solution
The hanging situation has now been improved by code changes. Please see
section "SP Patch Level" of this note for a list of updated software
components.
To get this correction available in your Support Package you need to apply
the patch matching to your Support Package version as per the instructions
in the NetWeaver Support Package Stack guide which can be found on the SAP
Service Marketplace as described in SAP Note 952402.
Thanks & Regards
Uday.S -
Mine is a File toXI to RFC scenerio.
File in DAT format is picked up fro FTP and send to XI. XI further sends it to BI server through RFC adapter. The thing is due to some reasons I hav deliberately entered wrong data uid and password] for XI to BI connection in sm59 and in the RFC adapter. Initially just wished to see wether the data movement between File aServer to XI takes place properly.
Activated the components and carried out the Tools - Test Configuration.
It is giving following error:
Receiver Agreement
More over when ever I place the file in the specified soure path ....I don see any RESULTS IN sxmb_moni or messege monitoring .
But Communication channel monitoring shows GREEN for file adapter.
My query is if sender File adapter is green and polling, why do i not see the same in messee monitoring and sxmb_moni.
Pls comment.
Pls revert back if anything is not clear.Hi,
just for check - in ID in sender file comm channel, set mode to delete and see if your test file in source directory is getting deleted.........if it is deleted, then in comm chnnel monitoring, you will get yur msg and also in SXMB_MONI...........if the file is not deleted, then check for file permissions to pick the file..
Regarding your No receiver agreement found error, in ID just create the reciver agreement for your sneder system, reciver sytem, receiver interface namespace data.............activate it and restart your msg in SXMB_MONI.
Regards,
Rajeev Gupta -
File- XI- RFC (Error: Received HTTP response code 500..)
Hi,
I am working on File->XI->RFC scenario, getting Processed Successfully status in "SXI_MONITOR".
But Data is not posted in SAP R/3. I check <b>Runtime Workbench </b> Getting following Error in one step.
Can any one help me in analyzing the error.....??????
2006-06-09 14:36:32 Success output 1149888992513 Channel WEBMETHOD_SENDER_SOAPFMTEST: Send binary file "/usr/sap/transx42/data/xi_input.xml". Size 175 with QoS EO
2006-06-09 14:36:38 Success output 1149888998592 Application attempting to send an XI message asynchronously using connection AFW.
2006-06-09 14:36:39 Success output 1149888999757 Trying to put the message into the send queue.
2006-06-09 14:36:40 Success output 1149889000823 Message successfully put into the queue.
2006-06-09 14:36:40 Success output 1149889000824 The application sent the message asynchronously using connection AFW. Returning to application.
2006-06-09 14:36:41 Success SAPEngine_System_Thread[impl:5]_12 1149889001577 The message was successfully retrieved from the send queue.
2006-06-09 14:36:41 Success output 1149889001591 File "/usr/sap/transx42/data/xi_input.xml" deleted after processing
2006-06-09 14:36:41 Success SAPEngine_System_Thread[impl:5]_12 1149889001745 The message status set to DLNG.
<b>2006-06-09 14:37:47 Error SAPEngine_System_Thread[impl:5]_12 1149889067522 Transmitting the message to endpoint http://SAPR3001.bently.com:8042/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500..</b>
2006-06-09 14:37:47 Success SAPEngine_System_Thread[impl:5]_12 1149889067585 The asynchronous message was successfully scheduled to be delivered at Fri Jun 09 14:42:47 PDT 2006.
2006-06-09 14:37:47 Success SAPEngine_System_Thread[impl:5]_12 1149889067695 The message status set to WAIT.
2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367587 Retrying to send message. Retry: 1
2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367587 The message was successfully retrieved from the send queue.
2006-06-09 14:42:47 Success SAPEngine_System_Thread[impl:5]_9 1149889367643 The message status set to DLNG.
2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368435 The message was successfully transmitted to endpoint http://SAPR3001.bently.com:8042/sap/xi/engine?type=entry using connection AFW.
2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368471 The message status set to DLVD.
2006-06-09 14:42:48 Success SAPEngine_System_Thread[impl:5]_9 1149889368472 The message was successfully delivered.
Thanks & RegardsHi Umesh,
I think, the reason is because of huge number messages ..
Also just go to RFC adapter, activate the adapter,refresh the cache and try it..
following guide will help you to solve problem~
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
Just refresh the cache-The following guide will help you on that~
https://websmp101.sap-ag.de/~sapidb/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Refer these SAP notes- 807000,803145
(some hints)
Regards,
Moorthy -
File to Rfc to File in pi7.1
Hiii,,
Iam trying file to rfc to file scenario...when iam montoring sender commuication channel it shows below mentioned error...wat may the issue..help me out
"Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.service.administration.api.cpa.CPAChannelStoppedException: Channel stopped by administrative task.. Setting message to status failed"
With Regards..
DineshHi,
I checked the namespace its rite...whether i have to check the same namespace in sap system...if yes, where to find it..
I guess your File CC configuration is not correct. Namespace will be your source interface namespace in PI. This is a very basic question and should be searched on SDN / SAP Help before posting here.
Go through this SAP Help ...
http://help.sap.com/saphelp_nw04/Helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htm
Regards,
Neetesh -
Hi ,
I am doing File to RFC Scenario.
My file get picked and I able to view the audit log under RWB message monitoring.
Here I am getting the error
u201CTransmitting the message to endpoint dest://XI_INTEGRATION_SERVER using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message using HTTPTransmitter. Reason: java.net.MalformedURLException: unknown protocol: dest.
Can any one tell me what is the reason.
Regards, NavneetHi Prakasu,
I am using PI 7.1 version .
When I opened SMICM there I am finding the HTTP Port as 52000.and the BS at SLD are also using the same Port in URL..
And when i verified with the Basis they confirmed that Exchange profile is set correctly.
But My file adapter is still not able to send the data to IS.
Than I configured a scenario file to file without IR object and in this case data is coming to IS and it is succesfull also.
what is the reason that in this case file adapter not able to push the data to IS.
I used File adapter with NFS protocol.
regards,
navneet -
File-PI-RFC scenario with extraction of contents in the filename
Hi All,
I am working on File to RFC scenario.
Here the file name is like 'ABCD_XYZ_1234_DATE' where the date is in yyyymmdd format.
I have to read this filename & the date in the filename is to be mapped with one of the RFC parameter.
Also how would I trigger the Interface if the file resides in PI server or on local mchine.
How to configure the processing parameters in sender comm channel if I want to read the file after every 15 mins?
Thanks,
Amit PatilHi,
By writing simple UDF in your mapping you can Acheive this
Try this Once
DynamicConfiguration dynamicconfiguration = (DynamicConfiguration)param.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File", "FileName");
String MyFileName = dynamicconfiguration.get(key);
String str[] = MyFileName.split("_");
return str1[1];
Map this to the date parameter(RFC) in the mapping .
If the file resides on Local machine then you can use FTP and if it is on PI server then NFS as Transport protocol.
If you want read the file for every 15 min there are 2 options
1) Set the poll interval time to 900 sec
2) Configure ATP in RWB
Configuring ATP in RWB :
http://www.dataxstream.com/2010/11/configuring-availability-time-planning-in-sap-pi/
Thank & Regards,
Deepthi -
Doubts in File to RFC scenario
<u><b>Scenario we are working on:</b></u>
Legacy System -> Flat File -> XI2.0 -> RFC -> SAP R/3 470 ( WAS 620 )
<u><b>What we have done till now:</b></u>
1. Created technical system for XI server and the SAP 620 ( target system )
2. Created business system for XI Server and target system
3. Created a software product for legacy system and the corresponding technical system and the business system
4. Defined the business scenario in Repository including Actions, Message Interface, Message Type, Data Type (for source file), Imported RFC signature from target system, message mappings and message interfaces.
5. Configured the file adapter.
6. Configured business scenario in Integration Directory including interface determination and receiver end points
<u><b>Where we are stuck:</b></u>
1. Currently I have created the entire set of objects under the new software component I created for source system. I want to know how to decide under which software component should I create the design objects, e.g under the software component for source system, or under the software component for target system or am I supposed to create a new product altogether including all the software components in my scenario.
2. What is the significance/dependency of namespace in the design process?
3. I have configured the inbound file adapter (attached is the configuration file). How do I integrate it with the Integration server? In other words where to specify the link between my business scenario the file adapter. How do they talk to each other?
4. We are not able to configure the RFC adapter. Can we get a configuration file for a working adapter? Are there any pre-requisites for the RFC adapter configuration? Also once configured how will it talk to Integration Server?
5. Is it possible to use proxies on Integration server in our scenario? Our XI system is installed on WAS 620 with J2EE 620 and the target system is also WAS 620.
6. Is it possible to send email notification from XI in case or any errors e.g while accepting the file, while mapping, or while passing to target systemHi Satinder,
Below are the answers for your questions:
Regards
Prasad
Netweaver RIG-XI
SAP Labs LLC.
Ans1: If you are creating a new sceanrio, you can create a product and a software component in SLD and import the software component into Int.Repository. You can define 1 namespace or mutliple namespaces under this SC.
It all depends on how are desiging your objects in SLD, Int Rep etc. This can be done in various ways.
Ans2:
Namespaces Definition:
Namespaces in the Integration Builder are namespaces in the sense of XML namespaces that are sub-divided further into semantic units within the Integration Builder software component versions. Objects of a namespace can only be shipped as part of the corresponding software component version and not separately.
XML Namespace Definition: An XML namespace is a collection of names, identified by a URI reference , which are used in XML documents as element types and attribute names
RFC2396
IETF (Internet Engineering Task Force) RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
Use
The following types of namespaces exist in SAP Exchange Infrastructure:
· Repository namespaces are displayed in the Integration Builder (Design) navigation tree. They are all assigned to a software component version but are used differently:
¡ Repository namespaces are used to avoid naming conflicts. For objects of the same object type, it is not possible to have duplicate object names within a repository namespace. In other words, a repository namespace is a quantity in the Integration Repository in which the object names are unique.
¡ Software component versions are used to define shipment units. It is not possible to ship objects in a namespace (business scenario objects, business process objects, interface objects, mapping objects, and adapter objects) on their own. Instead, they are shipped as a part of the relevant software component version.
Although repository namespaces are assigned to the software component version in the navigation tree, the software component version does not affect the uniqueness of the object names.
· XML namespaces are used as identifiers for message instances or customer-specific fields in the instance. You can specify XML namespaces as an attribute of (fault) message types and data type enhancements.
· Namespaces in the System Landscape Directory (SLD), which have nothing to do with repository or XML namespaces (see: Namespace).
· Internal namespaces, which are required in message instances, for example. The internal namespace for fields in the message header is: http://sap.com/exchange/MessageFormat, for example. These namespaces are of no further interest for SAP XI users.
Ans3: Check the Adpater Documentation. In your case, the legacy system will be creating a file in the file system where the file adpater is installed.You have to mention this path in your FA configuration. Once the FA is running, The file is polled automatically. The parameter defined in the config file will send direct the message to XI server. For Ex:
XMB.TargetURL=http://:8000/sap/xi/engine?type=entry
Ans4: Check the documentation for RFC Adapter Config. Once configured it will talk to XI via JCO. send me an email if you have more questions.
Ans5: Yes you can use Proxies as your target system is was620.
Ans6: this is possible in XI-3.0 -SP04 as the SMTP adpater is available. You have to model the message in XI-3.0 when to send an email message. -
File to Rfc scenario,not updated in rfc
Hi,
File to RFC scenario,not updated in RFC?
i checked communication channels ,smq1,smq2,sm58,cache refresh.but issue was not solved.
Please advise where need to check?
Thanks
AmitaHi Amita,
First check whether the configuration between PI and ECC has been set up properly.
Are you using a stand RFC or custom RFC?
Import the RFC metadata from ECC to PI and use that structure in your service interface and configure the remaining objects that we normally do.
Now, try to process the file and check in the communication channel, whether file Adapter is able to pick up and send the message to PI system.
If the message is successfully processed through PI system then check the messages in Queues. Also, check the RFC communication channel in the adapter engine.
Follow the process, you might get some clue regarding the issue. -
File to RFC scenario - receiver determination problems
Hi ,
Im trying to work out a flat file to RFC scenario, and am facing problems in configuring the receiver determination .
While creating my receiver determination, in the configured receivers, when i click on the F4 help to select service, i do not see the business system that i configured in SLD .
This system i have configured as an WAS ABAP system and provided all relevant data. I can also import objects from this system into IR, so i dont think i have set it up wrongly. I have also created RFC destination .
Is there some setting that has to be made that im missing ? Could somebody point out why im not able to see this system in the list of business services available at receiver configuration time ?
Thanks,
Joe
I also cleared the SLD cache by the way.. that didnt work either .
Message was edited by:
Joe SteinThanks a lot for you replies guys , but problems still not solved ;
1. I looked at the blog given and ive done everything pretty much as given . My problem lies in not finding the business system itself in the list of services for the configured receiver. How to implement this has not been shown in the blog.
2. I tried refreshing the cache and checking again, but it still doesnt show me the necessary step.
SOS !
I checked in the inbound system , and found that an RFC wasnt created for the XI system . I created that but i still cant see this system as a business system when i try to create the receiver determination . Do i need to recreate the technical system in the landscape to incorporate this change ?
Any pointers at all ??
Message was edited by:
Joe Stein -
Scenario File to RFC (BAPI): BAPI not executed successful
Hi Dear Friends!
At execution of asynchronous Scenario File to RFC (BAPI BAPI_ACC_DOCUMENT_POST)
I have the following error in RWB Communication Channel (RFC receiver):
- Error: 2007-07-25 11:08:25 EEST: Message processed for interface BAPI_ACC_DOCUMENT_POST:
com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message
to remote system:com.sap.aii.af.rfc.core.client.RfcClientBapiException:
BAPI not executed successful
Simultaniously <b>Test Configuration</b> was executed successfully. And mapping is good.
But I don't any message in <b>target system</b> in <b>sxmb_moni</b> (formed by BAPI).
In <b>XI system</b> I see in <b>sxmb_moni</b>:
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface mi_sender*</Trace>
<Trace level="1" type="T">select interface namespace urn:file:to:bapi</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
Please help me understand my error.
With the best regards,
Natalia MaslovaHi, Dear Friends! Thanks for support!
My settings of
Connection between systems:
DX7 01 (client 001) - XI Integration Server and DE2 13 (client 200) - target system.
Phisically both systems are in one server: 10.20.30.24 (srv24)
Business system DE2_200 has Communication Channel: cc_bapi_r, its settings (in Integration Builder Configuration):
Adapter Type: RFC
Receiver
Transport Protocol: RFC
Message Protocol: RFC (RFC XML)
Adapter Engine: Integration Server
RFC Client Parameter:
RFC Server Type: SAP System
Application Server: 10.20.30.24
System Number: 13
Authentication Mode: Use Logon Data for SAP System
Logon User: n_maslova
Logon Password: *******=*******
Logon Language: EN
Logon Client: 200
Maximum Connections: 1
x Advanced Mode
x Send 'Confirm Transaction'
x Commit Handling for Single BAPI Calls
x BAPI Advances Mode
Successful RETURN-TYPE Values: 0
As I understand these settings are the settings of RFC-destination for target system DE2 13 (200) from XI (DX7 01 001).
In SLD, Business system DE2_200 is defined as:
Integration:
Role: Application System
Related Integration Server: DX7_001
Technical System: DE2 on srv24
Client: 200 of DE2
Logical System Name: DE1CLNT200
In target system DE2 13 (200) with the help of transaction sm59 I created
RFC-destination DX7_001 of type H:
Technical setting parameters:
Target Host: 10.20.30.24
Prefix Path: /sap/xi/engine/?type=entry
Service Number: 8001
Registration and Safe:
SSL: Non active.
SSL: client certificate: DFAULT SSL-client
Enter to system:
Language: EN
Client: 001
User: PIAPPLUSER
Status PW: saved
Password: ********
After that in this system DE2 13 (200) with the help of transaction sxmb_adm I set in Integration Engine -> Configuration -> Configurate Integration Engine
(Change Global Configuration Data):
Role of Business System: Application System
Related Integr. Server: dest://DX7_001
Best regards,
Natalia -
What are the connections to be done for file-to-RFC scenario in XI & R3 ?
Hi,
What are the connections to be done for file-to-RFC scenario in XI & R3 & also if it is RFC-to-File .
I need to know what type connections used for file-to-RFC in backend .
In SLD it should be Third Party or WEB AS ABAP..Hi Nandan,
Perform the following configurations...
<b>SAP XI</b>
<b>1) RFC Destination (SM59)</b>
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
<b>2) Create Port (IDX1)</b>
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
<b>SAP R/3</b>
<b>1) RFC Destination (SM59)</b>
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
<b>2) Create Port (We21)</b>
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
Regards
San
Remember to set the thread to solved when you have received a solution there is a Way. -
Hi Friends,
I have done File to RFC scenario Using BPM. I have completed the scenario. I have tested the scenario using Test Configuration in ID. It is exectiong fine. It is notshowing any errors. But i am not getting the output. I think it is not enterting into BPM. Could you please suugest where will be the problem.Hi...
The below is the error i got.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="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 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 = ssisup70:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 172.18.139.205</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 = P70</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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 = CA0A4EFA21B04ADF1A269F73F1D08B92</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 = CA0A4EFA21B04ADF1A269F73F1D08B92</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 : XBTI0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0006</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 = CA0A4EFA21B04ADF1A269F73F1D08B92</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface FileRequest_OUT_MI*</Trace>
<Trace level="1" type="T">select interface namespace http://File2R3</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = P70</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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">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: - RFC_BPM</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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">2008-06-19T05:13:45Z 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) RFC_BPM FileRequest_AI</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: FileRequest_AI</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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">2008-06-19T05:13:45Z 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 = XBTOK___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 level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = P70</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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">2008-06-19T05:13:45Z 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 already defined in interface determination</Trace>
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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">2008-06-19T05:13:45Z 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">-File_Service</Trace>
<Trace level="2" type="T">-RFC_BPM</Trace>
<Trace level="2" type="T">http://File2R3.FileRequest_AI</Trace>
<Trace level="2" type="T">create outbound binding for Process Engine</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-06-19T05:13:45Z 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">2008-06-19T05:13:45Z 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">Channel for Process Engine: PE</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 = PE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_CALL_BPE_BULK</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_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message CA0A4EFA21B04ADF1A269F73F1D08B92</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface FileRequest_OUT_MI*</Trace>
<Trace level="1" type="T">select interface namespace http://File2R3</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 FileRequest_AI*</Trace>
<Trace level="1" type="T">select interface namespace http://File2R3</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="T">Destination not found:</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 008</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Maybe you are looking for
-
Hello everyone, like most people on this site, I am having difficulties understanding and fixing my Macbook Pro. About a month ago my computer screen went black, the computer was unresponsive, and it started making a beeping noise. I restarted the co
-
Dynamic range: NEED SOME HELP (any help i can g
here's the reason i am here:so lately i've decided to dump the idea of playing movies on my xbox360 and started using my hometheater PC to play it. since it has a X-fi extreme Music on it. and i do like it better because the xbox360's decoder down sa
-
Unable to create a drill through or drill down report
Hello I am new to report builder (or any SQL related tools) and I am still learning to do a many things. Background: I have managed to design a pie-chart report that shows Number of Assets, and when they were maintained. The fields I have for the t
-
my pascode wont work, ive tried the recovery mode but that wont work because of a network connection error, what do i do
-
Problem with sap 4.7ee with 640kirnal
Hi All, I installed sap 4.7ee kernal level is 640. I am not able to work BRTOOLS. If I am using BRTOOLS it giving error. wht to use here Regards, Sateesh J