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.

Similar Messages

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>

JDBC to RFC synch RFC call not executing.

Hi,
I am working on the synchronous JDBC to RFC without BPM. After completing design and config when I test the complete scenario the data from databse is not getting updated in R/3. And I do not see any errors in MONI. But when compared the moni logs I observed the following between the working scenario and not working scenario.
Working scenario log in MONI:
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ECS300</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/XI/System">InterfaceCollection</SAP:Interface>
- <SAP:Mapping notRequired="S">
<SAP:ObjectId>YYgNVKC9PTCW4JlMapfxZQ==</SAP:ObjectId>
<SAP:SWCV>IrmTYNPLEdqKItGjlusuXw==</SAP:SWCV>
Not working log from the MONI:
++++++++++++++++++++++++
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ECS300</SAP:Service>
<SAP:Interface namespace="http://my_Own_namespace">JDBC_Rfc_Synch_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>28ZZbGggOw6UcnigDXMD7A==</SAP:ObjectId>
<SAP:SWCV>IrmTYNPLEdqKItGjlusuXw==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
Could some body point me where I am doing wrong ?
Thaks
Steve.

Hi Steve,
I think the error is because your database table is expecting some kind of input and the input you are passing has some error in it.Just cross check the table using DESCRIBE <tablename> with the data you are trying to enter.
Also Just look at Query SQL Statement part ubnder this link,
http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
Regards,
abhy

File to RFC with multiple records using BPM Scenario Error...!!!

Hello Guru's,
I have done the File to RFC with multiple records using BPM scenario as per the Materiel available in the sdn.sap. This involves BAPI (BAPI_MATERIEL_AVAILABILITY). I have done exactly the same what is their in the materiel. SXI_CACHE is also giving return value " 0 ". File is getting deleted from the source directory, but no file in target directory. SXMB_MONI is also showing no error (black Flag). BPM is also error free. Checked the interfaces also.
Can any one tell me what mistake would i have done.
Thanks in advance.

Hi,
There is one similar discussion I found,
FTP TO RFC using BPM
Thanks
Swarup

Rfc(Syn)- BPM- JDBC connection breaks for job in 2Hrs

Hi All,
I have a scenario Rfc(Syn)->BPM->JDBC.
Problem i am facing is after 2Hr of execution of scenario. SAP & XI connectivity breaks down.
But to process full data it requires 5-6Hr connectivity because store procedures taking time(for 500 records).
Is there any solution for above problem?
Can we use ABAp Proxy instead of Rfc(i.e. ABAP Proxy->BPM->JDBC), If possible How?
Thanks & Regards

hi,
>>>>I have a scenario Rfc(Syn)->BPM->JDBC.
sync??? you can/should only use sync
if the response time is around 30 seconds
so change the interface to async
>>>>Can we use ABAp Proxy instead of Rfc(i.e. ABAP Proxy->BPM->JDBC), If possible How?
yes but you still have to do it in an async way
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Question regarding JDBC - XI -RFC

Hi all,
I have a scenario which XI will get data from database (using jdbc adpater) then send data to execute in RFC. This is an asynchronous call. My question is that.
1. If XI can get many records from database in 1 select, will it send many records to RFC at once? Is there any way i could tell XI to split input data into many message (1 message for each record) without using BPM? or Is it possible or better to set import parameter of RFC into table to get many record from XI at once?
2. If i manage to make 1 message for each record, Could i use queue for sending data to RFC? I want the first record to be completed before sending second record. Since this is an asynchronous call, I'm not sure that XI could be able to know when to send the second record or Do I have to make it synchronous call to get return response from RFC after RFC finish execution and use BPM to get return response before sending next data to RFC.
Any suggestion from expert?
Thanks,
Pavin

Hi
1. If XI can get many records from database in 1 select, will it send many records to RFC at once? Is there any way i could tell XI to split input data into many message (1 message for each record) without using BPM? or Is it possible or better to set import parameter of RFC into table to get many record from XI at once?
Yes you can do multi mapping 1:N without BPM
Message Splitting Using the Graphical Mapping Tool
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
2. If i manage to make 1 message for each record, Could i use queue for sending data to RFC? I want the first record to be completed before sending second record. Since this is an asynchronous call, I'm not sure that XI could be able to know when to send the second record or Do I have to make it synchronous call to get return response from RFC after RFC finish execution and use BPM to get return response before sending next data to RFC.
You can queue to process one by one. Response can be obtained with or without BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file-rfc-file(Without%2bBPM)
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/jdbcTOJDBC
JDBC to RFC Mapping Problem.
Thanks
Gaurav

RFC- XI- JDBC- XI- RFC

Hi All,
Can we do RFC->XI->JDBC->XI->RFC scenario without BPM?
In this SAP-RFC executed with SELECT and Table name
And SAP-RFC expect data from JDBC connection.
If not then what could be the expected steps of BPM?
Regards

Hi,
Are you talking about a Sync call. I mean are the Sender and Receiver RFC are the same. If it is a Sync step you can do without a BPM.
Like RFC will initiate the process the XI and the the data is selected from JDBC and the response is given back to RFC.
If the above is not the case you can avoide using BPM by having to separate scenarios.
1. Scenario 1 RFC --> XI --> JDBC
2. Scenario 2 JDBC --> XI --> RFC
If there are some dependencies or due to some constraints if you need to use BPM then you will have the steps like
Receiver Async(RFC)Send Sync(JDBC)Send Async(RFC)
Thanks,
Prakash

JDBC- XI- RFC(V.V.Urgent)

Hi ,
JDBC->XI->RFC
I am Integrating Oracle database with SAP(RFC).
How should adapter knows some thing updated in Oracle.
How Should the Triggers in Oracle.How we have to write Query in XI..
Points Will be awarded for the Solution..
Regards,
Jayasimha

Hi
Refer the below links ...
check the below blogs
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
/people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
See the below links also ..
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response - XI: How-to on JDBC receiver response
JDBC Response /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
Receiver JDBC scenario - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
/people/ajay.kumar/blog/2005/03/24/writing-bsp-for-sap-r3-version-46
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
/people/prasad.illapani/blog/2006/10/25/how-to-check-jdbc-sql-query-syntax-and-verify-the-query-results-inside-a-user-defined-function-of-the-lookup-api
/people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
/people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue
/people/sap.user72/blog/2005/12/22/new-to-xi
Rewards point if useful

JDBC to RFC Sync Error

Dear All,
I'm creating JDBC to RFC Sync scenario.
Configured according to below link,
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/12/04/jdbc-to-jdbc-synchronous-scenario-with-rr-beans-and-without-bpm-and-rfc-lookup
Sender JDBC structure is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_JDBC_To_RFC_Source xmlns:ns0="http://FiletoFile.com">
 <row>
 <A>12</A>
 34
 </row>
</ns0:MT_JDBC_To_RFC_Source>
But in Test tab of MM_REQ is showing Red.
Why its showing red?
PFA the attached Screenshot.
Thanks,
Arthita

Hi Arthitha
You cannot create structure of some kind and use completely different kind of input payload.
If your expected payload is of format
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_JDBC_To_RFC_Source xmlns:ns0="http://FiletoFile.com">
 <row>
 <A>12</A>
 34
 </row>
</ns0:MT_JDBC_To_RFC_Source>
Then your Data type should be created as below
Regards
Osman

JDBC to RFC synchronous scenario (Urgent).

Dear forum,
My requirement is data is populated in oracle data base.we are fecthing the data from database through XI and sending it to R/3. RFC is sending the response (suceess/failure) to XI. And XI is updating the status message into database.
For this,I have done the JDBC - RFC - JDBC syncronous scenario using BPM. .I got the successfull message under message monitering.Problem is I cannot able to find the data for RFC and JDBC reciever.
Please find the following Configuration steps for the above scenario
3 data types
JDBC request, JDBC response one dummy structure to capture RFC response messages.
3 message types for the above data types
5 message interfaces.
OB request,
OB ABS request,
IB Asyn for dummy,
Syn ABS (JDBC req and dummy structure),
IB JDBC response.
4 message mappings.
Mapping between JDBC request to JDBC request dummy.
Mapping between JDBC request dummy to RFC request.
Mapping between RFC response to JDBC response dummy.
Mapping between JDBC response dummy to JDBC response.
3 Interface Mappings.
JDBC request to JDBC request dummy.
JDBC request dummy to RFC request and RFC response to JDBC dummy response(Synchronous request and responce) .
JDBC dummy response to JDBC response.
Integration Process.
Used following steps.
Recieve step asynchronous -> Send synchronous -> Send asynchronous
I can able to see the payload for sender under communication channel.But the data is not reached to RFC.can any one help me to come out of this problem.
Points will be awarded for helpfull answers.
Thanks & Regards,
Naresh.K

Hi Seshagiri,
We are trying the same scenario with out using BPM.
Following steps has been done in design(IR).
2 data types for JDBC request & JDBC response.
2 message types for the above data types.
1 outbound synchronous message Interface.
2 message mappings (JDBC request -> RFC request) and (RFC response -> JDBC response)
1 Interface Mapping.
Could you please let me know how to maintain the collaborative profiles & and agreement details in Configuration(ID).
Your valuable assistence is required to complete the interface.
Thanks in advance.
Kind Regards,
Naresh.K

Can you explain steps in the Async and Sync scenarios JDBC to RFC.

Hi,
Can you explain some basic steps in the Async and Sync scenarios for sending data from JDBC to RFC.
Like,
The data is picked up from the database table through JDBC adapter.
It is passed on to SAP by calling the RFC. RFC gets executed
successfully. The status is returned by the RFC. The status needs to be
updated back into the SQL database table.
Is this a sync case or async case.
What si the diffrences in the sync and async scenarios in the above JDBC to RFC scenarios.
Soorya

hi check the below link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5474f19e-0701-0010-4eaa-97c4f78dbf9b
JDBC Synchronous call using BPM
Data Types -
1) File Input
2) JDBC Req
3) JDBC Response
4) File Response of similar type of JDBC Response.. ( This you can avoid also..let it be for first time)
Message Types
4 for each data type
Message Interfaces
1) Async, Outbound, Interface, to receieve the file
2) Async, Inbound , Interface to send the file from XI
3) Async, Absract , Interface of type File message type to recieve the message in the BPM
4) Sync, Abstract Interface with Req message type as File Request, and Response Message type as a file Response
5) Sync , Inbound interface for JDBC with Input message type as a JDBC Request and Output Message type as a JDBC Response
Message Mapping:
1)Mapping between File Req to the JDBC req
2) JDBC Response to File Response
Interface mapping:
1) Sender Interface as a Sync,Abstract Interface created for the file type and target interface as Synchrnous JDBC interface.
Use corresponding mapping for Req and Resp..
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Step by step cofig for jdbc-- xi-- rfc adapter.

hi,
all
can any one post any doc.. for the scenario
jdbc--> xi -->rfc
thanx
all sdn's

Hi ! Dantuluri
U couldnt find the direct weblog
JDBC receiver
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
JDBC sender
/people/yining.mao/blog/2006/09/13/tips-and-tutorial-for-sender-jdbc-adapter
IDoc sender
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Refer the below links also for this scenario
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
For any issues check this blog:
/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi
also refer these .....
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
Try this also .....
/people/laxman.molugu/blog/2006/08/13/integration-with-databases-made-easy-150-part-1
Re: Idoc triggering from a transaction
Message Mapping - JDBC to IDoc
Re: JDBC - System/Application Acknowledgement
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Process Integration (PI) & SOA Middleware
Pls reward if useful

JDBC to RFC & Mail

Scenario:
In JDBC to RFC
Output of above sender adapter will pass through 1:N mapping to generate individual records as separate message.
Each individual records is passed to attached XSLT to genarate RFC format message
RFC response has to be evaluated for errors. If there are errors there should be an email to a support group (we have to use email adapter here)
Along with the email, if there are errors, we need to update the source table.
How to acheive this using bpm?
i mean how many
Data Types,Message Types,Service Intrefce (obibabs),message mapping & operation mapping in IR
SenderAgreement,ReceiverAgreement,InterfaceDetermination,and ReceiverDetermination in ID
Thanks
Sri

How to trigger a mail adapter from BPM??
I need to fetch the data from database table through XI, and mapping to Synchronous RFC. Then, RFC response is send to both JDBC and email also. I am using BPM scenario for this. Please, let me know, how can I map with RFC response to email and JDBC. How can I handled in BPM scenario.
Can you please suggest me steps.
Thanks You
Edited by: Srilak on Mar 8, 2011 3:49 AM

File to JDBc to File using BPM

Hi All,
I want to create a scenario for JDBC to File. But i want to trigget this scenario and not to schedule it. So i have one option to put a file in any ftp folder and the this file will trigger my JDBC->file scenario hence my scenario becomes like File(Trigger)->JDBC->File.
I have added Receive and Send Steps in my scenario and it is ok for JDBC->File scenario. But to add this triggering mechanism i think i need to add on more receiver step which will receive file. I tried to add one more receive step at start but it is asking for Correlation... Here i am confused as i don't know why to use correlation in my scenario.....? Can anybody please suggest me how to use correlations in my case?
I just want to receive a flat file which will trigger JDBC->File Scenario.
Thanks,
Rohan.

It is just a simple select query.... will i need to make it sync then also....?
Yes if u use BPM.
It is possible to trigger the interface without BPM directly polling the database using JDBC sender as i earlier said.
With BPM, even for the select query, do message mapping. Do not assign any field from file to JDBC structure. Just assign the constants. This way select query ll be called. Map the output of select query to the receiver file structure.
Ur scenario BPM config would be similar to
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Regards,
Prateek

Help on RFC to JDBC and JDBC to RFC

Help on RFC to JDBC and JDBC to RFC
Hi Gurus
I have the scenario where an RFC will be triggered in SAP , to write to a DB2 database and insert new records in a table
and vice versa the JDBC has to read som data from a table based on a primary key, mark them as read for not be read next time and send the data to an RFC where a table in SAP will be updated.
I have never worked with JDBC before , pls advice.
is there any new issue to consider in PI 7.0 regarding JDBC
Thanks.

The requirement looks standard,
SEARCH IN SDN FOR JDBC scenarios,you will find many docs for sender as well as Receiver.
>
> is there any new issue to consider in PI 7.0 regarding JDBC
>
no issue with PI7.0.
Regards,
Raj

JDBC to RFC with BPM

Similar Messages

Maybe you are looking for