Working multiple RFC's with BPM

Hi All,
I have 3 RFCs as RFC1, RFC2, and RFC3. I need to execute RFC1. If it is success I need to call RFC2 and after that RFC3. Is it possible to do using BPM?
Regards,
Nithya

Hi Nitya,
Instead of going for BPM and complicating the scenario, You can do it this way.
First trigger RFC1 from R/3 and send a request.
then check the RFC1 response received and if its a success trigger RFC2 else end the scenario there and similar case with RFC3.
And if at all some error with RFC3,call RFC2 there so that you don't need to start it again with RFC1.
Hope this helps.
Thanks,
Vijaya.

Similar Messages

Step by step File to RFC Scenario with BPM

hi
for the following scenario i m following the webblog
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
i have successfully created the design phase
in the configuration stage
i need to create a business system or business service will do to create the communication channel
i have not created the systems so i feel i should not create the business systems
i would like to create the business service
so in only one business service can i assign all the communication channel
useful answers will be rewarded
Regards
JM

There are 3 parts of communication: Sender service to Integration Process (Asynch.), Integration Process to RFC (Synch.), Integration Process to Receiver Service (Asynch.)
The configurations should be like as follows:
Sender Service to IP
Receiver determination:
Sender Service->Request Outbound Message Interface->Integration Processs.
Interface Determination:
Sender Service->request Outbound Message Interface->Integration Process->Request Outbound Abstract Interface. (No interface Mapping is required as the interfaces share the same structure.)
Sender Agreement:
Sender Service->request Outbound Message Interface->Integration Process->Request Outbound Abstract Interface>FileRFC_Send
IP to RFC
Receiver determination:
Integration Process->Request Outbound Abstract Interface->Business service.
Interface Determination:
Integration Process->Request Outbound Abstract Interface->Business service->RFC Structure->Corresponding Interface Mapping between file structure and RFC structure.
Receiver Agreement:
Integration Process->Request Outbound Abstract Interface->Business service->RFC_Receiver
IP to Receiver Service:
Receiver determination:
Integration Process->Response Inbound Abstract Interface->Business service.
Interface Determination:
Integration Process->Response Inbound Abstract Interface->Business service->Response Inbound Message Interface. (No interface Mapping is required as the interfaces share the same structure)
Receiver Agreement:
Integration Process->Response Inbound Abstract Interface->Business service->FileRFC_Receive.
Hope you find this useful.
Regards,
Amitabha

Proxy_RFC_Proxy with BPM

Hi Experts,
i have scenario like Proxy-RFC-Proxy with BPM.
i am sending request from proxy it goes to RFC,while i am checking in the SXMB_MONI in the sender backend sap system it is showing status like schedule , how to solve this problem ,please suggest me.
Regards,
Sudeepth

Hi Experts,
In this scenario I am getting success flag , some times it is getting outbound status is Scheduled and some times Q status is showing stop symbol .From this status i am getting these kind of error in the PI system SXMB_MONI is
com.sap.engine.interfaces.messaging.api.exception.ConfigException: SLDAccess set to true, but not available.
I was check all need full checking in the SLD and also Tcode SLDCHECK , all connections are clear and active .
Still i am facing the same problem in the SXMB_MONI in PI system.
Please suggest me how to resalve the problem .
Thanks in advance.
Sudeepth.

FILE2FILE with BPM

Hi All,
Now i am working on FILE2FILE scenario with BPM Asynchronous.
i created 4 message interfaces.
1.BPM_SENDER_MI
2.BPM_SENDER_MI_ABSTRACT
3.BPM_RECEIVER_MI
4.BPM_RECEIVER_MI_ABSTRACT
Message Mapping is
BPM_SENDER_MT2BPM_RECEIVER_MT
Interface Mapping is
BPM_SENDER_MI_ABSTRACT2BPM_RECEIVER_MI_ABSTRACT
My Integration Process:
Receove--->Transformation--->Send.
Now i got confusion in Integration Directory.
Please let me clear that,
how many comm channels required ?
And how many receiver determinations, interface determinations, sender agreements & receiver agreements required for me?
Anybody have the solution, Please get back to me ASAP.
I am very thankful to you in advance.
Regards,
Nagarjuna.

Hi Nagarjuna,
if inside your BPM you really have only ONE transformation, then I suggest to you do NOT use a BPM, because it's not necessary !
your performance will decrease with the BPM... (remind BPM=workflow).
Moreover if you have NOT a BPM, your config will be easier:
Sender --> Mapping --> Receiver
Note: and in SXI_MONITOR you will have ONE message line.
And in case of BPM, you have;
1. Sender --> (no mapping) --> BPM
2. BPM --> (no mapping) --> Receiver
Remind: the mapping is done in your BPM.
Note: and in SXI_MONITOR you will have TWO message lines.
So there is no good point use BPM if you just have one transformation into your BPM.
BPM has to be used when you want to impelement a workflow flow, with correlation, alert, merge, split, etc...
Hope this help.
Mickael
Edited by: Mickael Huchet on Apr 15, 2008 8:23 AM

Send multiple records to rfc without using BPM

Dear Experts,
Could you please help on the following scenario.
I need to send multiple customer master data records from a file to rfc without using BPM.
The following is the mapping i am using
source Target( RFC)
====== =============
Tree occurance type Tree occurance
cust_mt 1..1
 customer 0..unbound -
> ztest_cust( rfc ) 1..1
 cname 1..1 -
> cname 0..1
 cno 1..1 -
> cno 0..1
 bank -
> bank 0..1
 item : 0..unbound
 code -
> code 0..1
 name -
> name 0..1
 location -
> location 0..1
1. Multiple banks possible for one customer
2. Multiple customers possible in datafile from mdm
Problem 1:Only one customer record from file is being sent to RFC thouth many records are in the file, the second, third .. and so on records not being sent to rfc.
Problem 2:
if add o.. unbound for the rfc occurance, <messages>,<message1> tags are getting added in message mapping, and no single customer record sent to rfc..
Your help is rewarded with good points.
Appreciate your help.
Thanks.
sravya.

Hi VJ,
Thank you for the immediate reply.
one more thing, when i tried to change the occurences of ztest_cust( rfc) to 0..unbound,
I am not seeing the occurances updated in the imported rfc structure.
The following is the wsdl for rfc, could you please help me to add occurances 0..unbound.
Thanks a lot.
sraya.
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:rfc="urn:sap-com:document:sap:rfc:functions" name="ZTEST_CUST" targetNamespace="urn:sap-com:document:sap:rfc:functions">
 <wsdl:documentation>
 test for mdm
 </wsdl:documentation>
 <wsdl:types>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions">
 <xsd:element name="ZTEST_CUST">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="CNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="10" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="CNO" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="10" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="BANK" minOccurs="0">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="item" type="ZST_CUST" minOccurs="0" maxOccurs="unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
 <xsd:element name="ZTEST_CUST.Response">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="BANK" minOccurs="0">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="item" type="ZST_CUST" minOccurs="0" maxOccurs="unbounded" />
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
 <xsd:complexType name="ZST_CUST">
 <xsd:sequence>
 <xsd:element name="CODE" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="60" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="NAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="60" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LOCATION" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="60" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:schema>
 </wsdl:types>
 <wsdl:message name="ZTEST_CUST.Input">
 <wsdl:part name="parameters" element="rfc:ZTEST_CUST" />
 </wsdl:message>
 <wsdl:message name="ZTEST_CUST.Output">
 <wsdl:part name="parameters" element="rfc:ZTEST_CUST.Response" />
 </wsdl:message>
 <wsdl:portType name="ZTEST_CUST.PortType">
 <wsdl:operation name="ZTEST_CUST">
 <wsdl:input message="rfc:ZTEST_CUST.Input" />
 <wsdl:output message="rfc:ZTEST_CUST.Output" />
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="ZTEST_CUST.SAPBinding" type="rfc:ZTEST_CUST.PortType">
 <rfc:binding style="rfc" />
 <rfc:type name="ZST_CUST">
 <ifr:container xmlns:ifr="urn:sap-com:ifr:v2:metamodel" xmlns:xlink="http://www.w3.org/1999/xlink">
 <ifr:descriptor>
 <ifr:description language="EN">
 test
 </ifr:description>
 </ifr:descriptor>
 <ifr:properties>
 <ifr:sourceSystem />
 <ifr:sourceClient>
 020
 </ifr:sourceClient>
 <ifr:release>
 640
 </ifr:release>
 <ifr:category>
 structure
 </ifr:category>
 <ifr:unicode1>
 true
 </ifr:unicode1>
 <ifr:unicode2>
 true
 </ifr:unicode2>
 <ifr:isFlatStructure>
 true
 </ifr:isFlatStructure>
 </ifr:properties>
 <ifr:definition>
 <ifr:internalLength1>
 180
 </ifr:internalLength1>
 <ifr:internalLength2>
 360
 </ifr:internalLength2>
 <ifr:fields>
 <ifr:field name="CODE" category="simple">
 <ifr:descriptor />
 <ifr:properties>
 <ifr:helpValuesSupported>
 false
 </ifr:helpValuesSupported>
 <ifr:offset1>
 0
 </ifr:offset1>
 <ifr:offset2>
 0
 </ifr:offset2>
 </ifr:properties>
 <ifr:definition>
 <ifr:scalarType>
 <ifr:definition>
 <ifr:type>
 CHAR
 </ifr:type>
 <ifr:abapType>
 C
 </ifr:abapType>
 <ifr:length>
 60
 </ifr:length>
 <ifr:internalLength1>
 60
 </ifr:internalLength1>
 <ifr:internalLength2>
 120
 </ifr:internalLength2>
 <ifr:decimals>
 0
 </ifr:decimals>
 </ifr:definition>
 </ifr:scalarType>
 </ifr:definition>
 </ifr:field>
 <ifr:field name="NAME" category="simple">
 <ifr:descriptor />
 <ifr:properties>
 <ifr:helpValuesSupported>
 false
 </ifr:helpValuesSupported>
 <ifr:offset1>
 60
 </ifr:offset1>
 <ifr:offset2>
 120
 </ifr:offset2>
 </ifr:properties>
 <ifr:definition>
 <ifr:scalarType>
 <ifr:definition>
 <ifr:type>
 CHAR
 </ifr:type>
 <ifr:abapType>
 C
 </ifr:abapType>
 <ifr:length>
 60
 </ifr:length>
 <ifr:internalLength1>
 60
 </ifr:internalLength1>
 <ifr:internalLength2>
 120
 </ifr:internalLength2>
 <ifr:decimals>
 0
 </ifr:decimals>
 </ifr:definition>
 </ifr:scalarType>
 </ifr:definition>
 </ifr:field>
 <ifr:field name="LOCATION" category="simple">
 <ifr:descriptor />
 <ifr:properties>
 <ifr:helpValuesSupported>
 false
 </ifr:helpValuesSupported>
 <ifr:offset1>
 120
 </ifr:offset1>
 <ifr:offset2>
 240
 </ifr:offset2>
 </ifr:properties>
 <ifr:definition>
 <ifr:scalarType>
 <ifr:definition>
 <ifr:type>
 CHAR
 </ifr:type>
 <ifr:abapType>
 C
 </ifr:abapType>
 <ifr:length>
 60
 </ifr:length>
 <ifr:internalLength1>
 60
 </ifr:internalLength1>
 <ifr:internalLength2>
 120
 </ifr:internalLength2>
 <ifr:decimals>
 0
 </ifr:decimals>
 </ifr:definition>
 </ifr:scalarType>
 </ifr:definition>
 </ifr:field>
 </ifr:fields>
 </ifr:definition>
 </ifr:container>
 </rfc:type>
 <wsdl:operation name="ZTEST_CUST">
 <ifr:container xmlns:ifr="urn:sap-com:ifr:v2:metamodel" xmlns:xlink="http://www.w3.org/1999/xlink">
 <ifr:descriptor>
 <ifr:description language="EN">
 test for mdm
 </ifr:description>
 </ifr:descriptor>
 <ifr:properties>
 <ifr:sourceSystem />
 <ifr:sourceClient>
 020
 </ifr:sourceClient>
 <ifr:release>
 640
 </ifr:release>
 <ifr:package>
 $TMP
 </ifr:package>
 <ifr:akhNode />
 <ifr:released>
 external
 </ifr:released>
 <ifr:outbound>
 false
 </ifr:outbound>
 <ifr:synchronous>
 true
 </ifr:synchronous>
 <ifr:asynchronous>
 false
 </ifr:asynchronous>
 <ifr:unicode1>
 true
 </ifr:unicode1>
 <ifr:unicode2>
 true
 </ifr:unicode2>
 </ifr:properties>
 <ifr:definition>
 <ifr:parameters>
 <ifr:parameter name="CNAME">
 <ifr:descriptor>
 <ifr:description language="EN">
 Character Field Length = 10
 </ifr:description>
 </ifr:descriptor>
 <ifr:definition>
 <ifr:scalarType name="CHAR10">
 <ifr:properties>
 <ifr:helpValuesSupported>
 false
 </ifr:helpValuesSupported>
 <ifr:fixedValuesListDefined>
 false
 </ifr:fixedValuesListDefined>
 <ifr:mixedCaseSupported>
 false
 </ifr:mixedCaseSupported>
 <ifr:signedNumber>
 false
 </ifr:signedNumber>
 </ifr:properties>
 <ifr:definition>
 <ifr:type>
 CHAR
 </ifr:type>
 <ifr:abapType>
 C
 </ifr:abapType>
 <ifr:length>
 10
 </ifr:length>
 <ifr:internalLength1>
 10
 </ifr:internalLength1>
 <ifr:internalLength2>
 20
 </ifr:internalLength2>
 <ifr:decimals>
 0
 </ifr:decimals>
 <ifr:outputLength>
 10
 </ifr:outputLength>
 </ifr:definition>
 </ifr:scalarType>
 </ifr:definition>
 <ifr:properties>
 <ifr:direction>
 in
 </ifr:direction>
 <ifr:class>
 import
 </ifr:class>
 <ifr:type>
 scalar
 </ifr:type>
 <ifr:optional>
 true
 </ifr:optional>
 <ifr:basedOnDictionaryReference>
 true
 </ifr:basedOnDictionaryReference>
 </ifr:properties>
 </ifr:parameter>
 <ifr:parameter name="CNO">
 <ifr:descriptor>
 <ifr:description language="EN">
 Character Field Length = 10
 </ifr:description>
 </ifr:descriptor>
 <ifr:definition>
 <ifr:scalarType name="CHAR10">
 <ifr:properties>
 <ifr:helpValuesSupported>
 false
 </ifr:helpValuesSupported>
 <ifr:fixedValuesListDefined>
 false
 </ifr:fixedValuesListDefined>
 <ifr:mixedCaseSupported>
 false
 </ifr:mixedCaseSupported>
 <ifr:signedNumber>
 false
 </ifr:signedNumber>
 </ifr:properties>
 <ifr:definition>
 <ifr:type>
 CHAR
 </ifr:type>
 <ifr:abapType>
 C
 </ifr:abapType>
 <ifr:length>
 10
 </ifr:length>
 <ifr:internalLength1>
 10
 </ifr:internalLength1>
 <ifr:internalLength2>
 20
 </ifr:internalLength2>
 <ifr:decimals>
 0
 </ifr:decimals>
 <ifr:outputLength>
 10
 </ifr:outputLength>
 </ifr:definition>
 </ifr:scalarType>
 </ifr:definition>
 <ifr:properties>
 <ifr:direction>
 in
 </ifr:direction>
 <ifr:class>
 import
 </ifr:class>
 <ifr:type>
 scalar
 </ifr:type>
 <ifr:optional>
 true
 </ifr:optional>
 <ifr:basedOnDictionaryReference>
 true
 </ifr:basedOnDictionaryReference>
 </ifr:properties>
 </ifr:parameter>
 <ifr:parameter name="BANK">
 <ifr:descriptor>
 <ifr:description language="EN">
 test bank type
 </ifr:description>
 </ifr:descriptor>
 <ifr:definition>
 <ifr:complexType xmlns:xlink="http://www.w3.org/1999/xlink" name="ZST_CUST" type="structure" xlink:role="type" xlink:href="/Content?TYPE=type&NAME=ZST_CUST" />
 </ifr:definition>
 <ifr:properties>
 <ifr:direction>
 inout
 </ifr:direction>
 <ifr:class>
 tables
 </ifr:class>
 <ifr:type>
 structure
 </ifr:type>
 <ifr:optional>
 true
 </ifr:optional>
 <ifr:basedOnDictionaryReference>
 true
 </ifr:basedOnDictionaryReference>
 </ifr:properties>
 </ifr:parameter>
 </ifr:parameters>
 </ifr:definition>
 </ifr:container>
 </wsdl:operation>
 </wsdl:binding>
</wsdl:definitions>

File to RFC scenario with no BPM

I want to create File to RFC scenario with no BPM. I want to invoke RFC synchronously to verify that I'm getting correct response back, but i dont wanna process the response. So, In SXMB_MONI i can check the response back from RFC right? Or do I need to have BPM if want to see the response back from RFC?
What kind of business system i need to create for RFC? can i use same business system for both File and RFC? I'm using one Business System created on Third party technical system, which i'm using for file Input, also for RFC. Is that OK?
Thanks,
Deepesh

Hi,
I need to have BPM if want to see the response back from RFC? ... yes
The BPM will help you find the response very comfortable.
What kind of business system i need to create for RFC? can i use same business system for both File and RFC? I'm using one Business System created on Third party technical system, which i'm using for file Input, also for RFC. Is that OK? ..Yes you can .
Regards
Agasthuri Doss

JDBC to RFC with BPM

Hi,
Please find details of my scenario.
Oracle(VIEW)
Sender JDBC--> PI--
> RFC request
and RFC response I need to update some other table in Oracle using storeprocedure.
and have one more storeprocesdure to update the View so that I will not get duplicate entry.
I am not using UPDATE statement in JDBC sender communication channel, insted of that to update VIEW I am using storeprocedure.
Please let me know how I can achive it with BPM.
Thanks,
Bhupesh

Hi,
1) If the structure send by JDBC is not acceptable by the BPM then you need one Mapping in JDBC ---> BPM flow.
2) If the structure send by JDBC is same as the receiving structure of BPM then no need of Mapping.
3) You will need one Mapping to map JDBC req message to the RFC req message; one mapping program to convert RFC response to the JDBC stored-procedure message....
So your scenario with mappings will be:
JDBC --> Interface Determination (Mapping Optional as per pt.1) -
> BPM
BPM <-> Interface Determination (Request-Response Mapping) <--> RFC
In the above mapping program your ABS MI of BPM should have below MTs
Req Message -
> Original Message Received from JDBC
Response Message ---> Message which needs to be send to the JDBC stored-procedure.
Now your IN SYNC MI at the RFC end should have below MTs
Req Message ---> RFC request message
Resp Message ---> RFC response massage.
Then in the Interface Detremination of BPM <----> RFC flow develop a IM with below mapping programs:
Request Mapping between ---> MessageFromJDBC_to_RFCRequest
ResponseMapping between ---> RFCResponse_to_JDBCStoredProcedure
BPM -
> JDBCStoredProcedure
For this flow there is no need of Mapping program...
using the above mappings programs you can ensure that there is no Transformation step in your BPM...this is to help you in achieving a good performance out of your BPM...
You need a Syns ABS and Sync IN message Interface for BPM <---> RFC communication.
Regards,
Abhishek.

How does RFC adapter with EO/EOIO work? Kindly help!

Hi Experts,
How does a sender or receiver RFC adapter works when QOS is EO or EOIO (Async)? In other words, for EOIO, are the messages are queued? How does this queueing work? Does it use FIFO logic? where do we specify the max limit of messages that can be queued?
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
In my Async RFC - XI scenario sometimes XI is able to receive the messages but sometimes it doesnot even though the sender system is UP and running.
I cannot see any messages in SXMB_MONI even though the sender has sent the messade.
Why RFC adapter is behaving like this? What could be the issue?
Kindly help!

EOIO: How does this queueing work? Does it use FIFO logic?
>> yes it uses FIFO logic in EOIO.
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
>>>noof rfc connections we are using for connecting to XI to RFC minmum is 1 maximum is 50 bydefault. you increase this value by changing the default setting.
How does RFC adapter with EO/EOIO work? Kindly help!
Posted: Mar 21, 2007 4:15 AM
Hi Experts,
How does a sender or receiver RFC adapter works when QOS is EO or EOIO (Async)? In other words, for EOIO, are the messages are queued? How does this queueing work? Does it use FIFO logic? where do we specify the max limit of messages that can be queued?
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
Why RFC adapter is behaving like this? What could be the issue?
>>check ur sender RFC adapter. chekc whether data is sent from RFC . see logs in R/3.

File to RFC with BPM

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" ?>
- 
- <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>

Multiple Image Upload with save to database not working in IE anymore

Since updating IE to SP3 ADDT Multiple Image Upload with save to database does not work anymore in IE. It will show a regular file upload field, an does not allow selection of multiple files. It does work in Firefox, but not all my clients use firefox.
PSE Advice.

I would consider buying some pluggins from dmxzone.com. They
may cost a
bit upfront but in the long run, you've probably be saving a
lot of
headaches.
http://www.dmxzone.com/
If time's an issue, with these plugins, you could probably
be up and
running in a half hour. George has some really nice pluggins
for
Dreamweaver and well worth the money.
Peter Raun wrote:
>
I am going crazy here
> I will see if i can explain my problem here. . .
> I am trying to use the multiple image upload with save
to database function in
> the developer toolbox, and it work just fine, it lets me
select where to store
> the filename in database and where i want to save the
actual image on the
> server. It is wery easy to use if you just want these
functions.
> But i would also like to give every image a gallery id
in the database, so i
> can sort them out afterwards, its not whery smart to
upload a lot of images to
> a folder, and in the database you just have an image id
and an filename, i cant
> sort them into galleries with these to collums. . . . So
i guess i have to do
> something with the "additional fields" when i am
creating the server behavior
> but i cant figure out what to do?? i would have liked if
i could have made an
> list/menu with all of the availible galleries, and chose
the one that i whould
> add images too and then that gallery id whould be added
to those images in the
> database.
> I have also tried to pass on an url parameter and then
use that as a default
> value in the "additionel field" section but without any
luck at all. . . I hope
> someone here has an idea, that could help me out. . .
> It is sooooo easy to do this, when you are uploading ONE
image at a time, i
> cant figure out why it has to be sooooo hard when using
"multiple image
> upload"
>

How to loop through single XML File and send multiple RFC calls?

I am looking for the best approach to use for making multiple RFC calls (can be sequential) using a single XML file of data. I have been attempting to get a BPM loop working, but to no avail. My RFC only accepts a single set of delivery input and I have been told to try to work with it as is.
input xml sample:
<?xml version="1.0" encoding="UTF-8"?>
<ProofOfDelivery>
 <POD>
 <delivery_number>1</delivery_number>
 <carrier_name>UPS</carrier_name>
 </POD>
 <POD>
 <delivery_number>2</delivery_number>
 <carrier_name>UPS</carrier_name>
 </POD>
</ProofOfDelivery>
I need to make a synchronous RFC call for each set of POD data.
Thanks in advance!

Thanks for the inputs.
I tried with a BPM and multi-mapping transformation before a ForEach block. I am getting this error:
Work item 000000028028: Object FLOWITEM method EXECUTE cannot be executed
Error during result processing of work item 000000028029
com/sap/xi/tf/_ProofOfDeliveryMultiMapping_com.sap.aii.utilxi.misc.api.BaseRuntimeExceptionRuntim
Error: Exception CX_MERGE_SPLIT occurred (program: CL_MERGE_SPLIT_SERVICE========CP, include: CL_
Probably because I am not making/using the container objects properly. Here is a screenshot of my BPM. Can anyone spot my issue or point me to an example on this sort of container use?
[http://kdwendel.brinkster.net/images/bpm.jpg|http://kdwendel.brinkster.net/images/bpm.jpg]
Thanks

File to idoc with BPM

Hi All,
I have one File to IDoc Scenario. Now I want to throw posting error in a file.
i.e., if mapping goes not well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a file(Flat file) will be created at sending system side.
I am planning to design this scenario with BPM. Now end user requires a akwoledgement for this scenario eithere it may be succsess or failure in file format. If succsess the file will be created with succsess information(any format), either failure also file will be created with error information. The user requires only file format b'coz this file will be read by another java application (user didn't require to his mail).
Can anybody suggest the solution for this:
1. How to generate aknowledgement file for sucsess or failure.
2. How to use this file to idoc scenario in BPM with out using Alert configuration or Mail adapter.
Regards,
Konala.

Hi,
As you know Idocs are used for asynch communication, only was to get acknowledgemnet is using ALEAUDIT. For your scenario there can be one work around. When you post IDoc in the, in that function module after the posting is done call one more RFC with the the success/failure message which will trigger RFC to File sceanrio.
If you get any other solution, please post it back to same thread.
Thanks,
Prateek

Need Help in File to Multiple Receivers Sceanrio without BPM

Hi Friends,
My sceanrio is picking the PO data from file and creating SO in multiple receivers. I configured multiple receivers in Receiver Determination and it is working fine.
Since i use multiple receivers i can't make this sceanrio as synchronous one. But i want to know the generated SO number. Is there any way to get this? Or should i use BPM?
Thanks & Regards,
Senthil.

Hi
I think you can do this with BPM only.
As per multicast pattern you can send a message to multiple receivers and waiting for a response message from each of the receivers.
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Thanks
Prasad Nemalikanti

1 xml file to multiple xml files with 200 records in each

Hello Experts,
I have below scenario.
Please suggest me which might be the best approch to work on.
1) XML file to XML file
I will have 1 pretty huge XML file which i need to break in multiple XML files with 200 records each.
1) first approch i can have bpm in which i can split the file according to my requirement.
2) Second approch i can create 2 scenarios in which 1st scenario will pick up XML file and create multiple flat files with File content conversion. Second scenario will pick up all these flat files and create XML files.
2) XML file to XML file
Or i can have multiple files with 1 record per file and i need to merge in multiple XML files with 200 records in each.
So its kind of 1:N or M:N scenarios.
Please tell me which is might be better performance and design wise.
Or if you have any idea in any other way i can do this, then please reply as soon as possbile.
Please tell me if you have OS command for the same or some script to run or anything which i can implement.
Thanks,
Hetal

what is your senario? is it File to File?
You can use multi mapping concept without BPM. You can handle the 200 records per message logic in the multimapping.
Regards,
Praveen Gujjeti.

Scenario's performance with BPM vs without BPM in PI 7

hello,
Please send me the presentation, blogs describing the performance issues in PI 7
also, the docs differenciating a normal scenario's performance (without BPM) vs the scenario with BPM...
What are the enhancements made to BPM in PI 7 for performance increase?
Regards,
Nikhil.
******Each useful reply will be awarded*******
Edited by: nikhil a on Feb 7, 2008 6:10 AM

BPM Performance: Integration processes are executed on the Integration Server at runtime by the Business Process Engine. Since the Integration Server is the central resource for message exchange, you must ensure that it is not overloaded; otherwise, this can lead to bottlenecks or performance problems.
Resource Consumption
Every step of an integration process uses Integration Server resources.
●      Every message that is sent to the Process Engine is duplicated.
●      Every message that is sent from the Process Engine is duplicated.
●      A work item is created for the process itself and for every step the process contains.
This means that for a process that just receives one message that is sent without being processed further, four messages and three work items are created.
For this reason, you must ensure that you take Integration Server resources into account when you define integration processes.
Resource Consumption of Different Step Types and Transactional Behavior
Different step types consume different amounts of system resources:
●      Step types with high resource consumption:
     ○       Receive step
     ○       Send step
Asynchronous send steps with acknowledgments in particular consume a lot of system resources. In the case of synchronous send steps, consumption depends on the target system.
     ○       Receiver determination
     ○       Transformation step
In transformation steps, resource consumption is dependent on the mapping called. In general, process steps that generate work items internally are relevant for process performance. Transformation steps (either for message split or merge) also include a mapping step and can be quite expensive. This should be taken into consideration during scenario design.
     ○       Block
     ○       Wait step
●      Step types with low resource consumption:
     ○       Control step
     ○       Multiple condition
     ○       Fork
     ○       Loop
     ○       Undefined step
If you design the transactional behavior of an integration process so that the following steps are not performed as separate transactions, you can improve performance significantly:
●      Transformation step
●      Receiver determination
●      Send step (synchronous or asynchronous)
Transactional Behavior of an Integration Process
Use
You can now influence transactional behavior in the definition of an integration process in the process editor. This enables you to improve performance.
Transaction:
A transaction is a sequence of processing steps that are either fully executed, or not executed at all. If the system cannot fully execute a transaction, it rolls back all processing steps within the transaction. This means that the system can return to the state before the transaction was begun.
The transaction control mechanism for integration processes is not a central transaction manager for an entire system landscape. The transaction control mechanism cannot roll back any processing steps outside the Integration Server.
Transaction Boundaries
You have the option of defining the start or end of a block as the boundary of a transaction.
●      In the case of the start of a block, you can define that the system is to start a new transaction.
●      In the case of the end of a block, you can define that the system is to end the transaction being started (COMMIT WORK). The system ends the transaction that is currently open, regardless of whether it has been started or not. For example, if no new transaction was started at the start of the block, the last transaction started is continued instead.
By making appropriate settings for the start and end of a block you can expand transactions. This means that the database needs to be accessed less often, and enables you to improve system performance
Transactional Behavior for Specific Step Types
At runtime, the system normally creates a separate transaction for each step. The transaction then covers this step only. However, you can influence the transactional behavior of particular step types. In the step properties, you can define that the system is not to start a new transaction when the step is executed. The system then executes the step in the transaction that was started at the time of execution. Consequently, no background work item is created for the step and the database does not need to be accessed. In this way you can improve system performance.
You can influence the transactional behavior of the following step types:
●      Send step
You can influence the transactional behavior when sending messages both synchronously and asynchronously, and when sending acknowledgments
     Transformation Step
     Receiver Determination Step
Optimizing Transactional Behavior:
●      Memory requirements
Expanding transactions and executing specific steps without creating a new transaction may increase the burden on the main memory. If the burden on the main memory is too great, you must redefine transactions, or define that a new transaction is to be created for the step concerned.
●      Troubleshooting in the workflow log
The technical view of the workflow log does not show any detailed information for steps for which no work item was created. If an error occurs, the workflow log displays the error information for the last executed step. The following example illustrates this:
A process contains a transformation step that is executed within an expanded transaction. When the transformation step is executed, an error occurs in mapping and the system rolls back the transaction. Since no work item was created for the transformation step, the workflow log does not have an entry for the transformation step. The error information is entered in the last executed step in the workflow log.
EXAMPLE:
For an example of resource consumption, see the BPM scenario described in the XI sizing guide:
The inbound SOAP messages are handed over to the BPE, which triggers a two-step process consisting of message reception and sending. The processed messages are then sent to a receiver by using the SOAP channel; no mapping.
The SAPS value for this scenario, in which 10 kB messages are processed, is 1300 (processing one process instance each second). A simple XI proxy scenario, for example, requires 140 SAPS process-ing one message each second. This gives you an idea of the resource requirements using BPM.
Example:
In the original implementation, two separate JCBC calls were made to retrieve a sales order document header and the line items. This data then was transformed to the IDoc format of the receiving application using a transformation. Then, using a loop step, one IDoc at a time was sent to the backend application. - This sub optimal design resulted in poor performance caused by following design flaws:
                Separate retrieval of header and line items with the JDBC adapter
               Transformation within ccBPM to combine retrieved header and line items
               IDoc back end connection for one document at the time
In the improved version below, both the JDBC call and the transformation were removed from the ccBPM. The retrieval of the source messages is done via a synchronous call with two mappings in the integration engine of XI that generate the required format for the receiving system. Therefore, it is not necessary to add an additional transformation step in the ccBPM. Additionally, the IDoc adapter connecting to the target system is used to handle multiple IDocs inside one XI message. Therefore, it is not necessary to add a loop operation within the ccBPM either. In this particular implementation, the described changes resulted in a 20x performance improvement!
IMP LINKS:
3bf550d4-0201-0010-b2ae-8569d193124e.pdf
43e8e190-0201-0010-3ea1-d6f996cb4124.pdf
70ada5ef-0201-0010-1f8b-c935e444b0ad.pdf
c071d7bb-0601-0010-d6b8-f4e4dc7f1e20.pdf

Working multiple RFC's with BPM

Similar Messages

Maybe you are looking for