File To RFC without BPM

Dear Friends,
My scenario is File to RFC , file is picking from third party and that file parameters are updated in ecc and response is updated in third party system
using XI.
For this one I created data types,message types,message interfaces and message mapping for sender , receiver and response.
In interface mapping I have small doubt i.e how many interface mappings needed for this scenario.
In integration directory how many receiver determination and interface determination needed.
please suggest me.
Regards,
Shalini Shah

Hi Shalini,
U need to create 2 interfaces at sender side(1 is for file request & 2nd for file response) and one interface at ur receiver side for RFC.
Refer File to RFC blogs with out BPM u may find lot of stuff to ur requirement.
Regards,
Edited by: farook shaik on Sep 20, 2008 7:53 AM
Edited by: farook shaik on Sep 20, 2008 7:55 AM

Similar Messages

File content conversion in File-to-RFC without BPM

Hi,
I am using FCC for file to RFc scenario.
My input record is in the following format:
Header record
data rec1
data rec2
Trailer record..
The parameters are used in File content conversion:
Recordset Name : Header,item
Recordset Structure: Header,1,item,*
key field name : data1
and in additional parameters:
Header.fieldNames            HI,GenDate,Ftype,Fname,Fdate
Header.keyFieldValue       Fname
Header.fieldFixedLengths 1,8,1,50,8
Header.endSeparator        nl
item.endSeparator             nl
item.fieldNames                  DATA1,DATA2,DATA3,DATA4
item.keyFieldValue             item
item.fieldFixedLengths       231,240,241,120
item.lastFieldsOptional       YES
Can anyone check whether any parameters are left, b'cos the file is not being read with this settings. and in the C.C its just showing file processing successfully but not able to see the actual file.

Hi,
I assume you have header, item and trailer structure in source file.
Source Data Type will be as follows.
RecordSet
--> Header
      --> KeyField(Value OH)
      --> H1
      --> H2
--> Item
      --> KeyField (Value OL)
      --> I1
      --> I2
-->Trailer
      --> KeyField (Value OT)
      --> T1
      --> T2
Where Item Strucutre can come multiple times.
Please use following settings.
Recordset name: RecordSet
RecordSet Structure: Header,1,Item,*,Trailer,1
Key Field Name: KeyField
Header.fieldNames: KeyField,H1,H2
Header.fieldFixedLengths: 2,3,4
Header.processFieldNames: fromConfiguration
Header.keyFieldValue: OH
Header.LastFieldsOptional: YES
Item.fieldNames: KeyField,I1,I2
Item.fieldFixedLengths: 2,5,6
Item.processFieldNames: fromConfiguration
Item.keyFieldValue: OL
Item.LastFieldsOptional: YES
Trailer.fieldNames: KeyField,T1,T2
Trailer.fieldFixedLengths: 2,8,9
Trailer.processFieldNames: fromConfiguration
Trailer.keyFieldValue: OT
Trailer.LastFieldsOptional: YES
Regards,
Gouri

File-To-RFC without using BPM

hey guys
is a File-To-RFC scenario possible without using BPM? i have gone through the blog by Arpit Seth ( /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit ) but it uses BPM.
i am new to XI and not very comfortable with BPM.
please let me know if BPM is the only way out or are there some other methods too.
Also under what circumstances one should use BPM?
thanx in advance.
aamir suhail

Hi,
it's a standard non BPM scenario
(you can find many weblogs like this)
the only different thing is the RFC signature import
(inside repository)
and the use of different channels (file and RFC)
you can find many examples in my XI FAQ
(document section)
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

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>

How to PI call R/3 RFC without BPM.

Hi Expert.
Why PI direct call RFC probably is not a possibility of doing without BPM.
It makes RFC of separate way, it calling it is made Report program where there is a possibility of doing.
Different adapter where it becomes direct call, RFC piece bay occupational calling there probably is not a possibility of doing.

Krishna Moorthy P, Thank you so much your answer.
I add question.
My scenario is very simple.
Case 1. File to RFC to JDBC Scenario. (Sync)
 Using BPM. PI call File adatper, and PI call RFC Function, and RFC return data send to PI to JDBC.
Case 2. QRFC to JDBC Scenario.(Async)
 Using se37 for back job. So, Back job Function send to PI to JDBC.
In this two case, to what kind of is the efficiency better.
I think that case 2 is performance better case1.
It isn't like that? Krishna Moorthy P
I wating for your answer.
Message was edited by:
 JuYeop Kim

File sender adapter:FILE to IDOC without BPM, can't see in SXMB_MONI.

Hi all
I have a FILE - XI - IDOC Async scenario without BPM.
I configured FILE sender adapter and IDOC receiver adapter. I made a mapping to transfer file data to the structure of IDOC.
Now when i am trying to load the file using command prompt, i cud see nothing in the monitoring. Whereas if i go to the communication channel monitoring of runtime workbench, i saw that CC is polling correctly and was reading the file also.
And also wen i saw in the processed folder which i mentioned in the CC configuration for the ARCHIVE DIRECTORY, i saw that file got transferred to the folder also.
I don't understand why i cant see anything in the monitoring.
Could anybody help me to rectify the problem. Is there anything i m missing ?
Regards
Naina

Rajesh/Amar
TCode:: SXMB_ADM->Integration engine configuration->specific configuration->runtime
Trace_Level = 3 then you can get all MONI PIPELINE Steps also
I did this change but cudn't see anything in SXMB_MONI.
This is how i have configured my process:
http://wiki.sdn.sap.com/wiki/display/XI/FiletoMultipleIDOCSplittingwithoutBPM
But instead of IDOC splitting i have simple FILE - XI -IDOC scenario.
I have configured everything exaclty the same way it is mentioned here. But for me the process is not visible at all.
I can't even see the first request message in the monitoring.
This is the message i can see in the communication channel monitoring:
2010-05-24 09:07:41 Success Channel CC_*: Entire file content converted to XML format
2010-05-24 09:07:41 Warning Channel CC_*: Empty document found. Proceed without sending message
2010-05-24 09:07:41 Success File "/xyz/ABC.txt" archived after processing
Is there any problem with the file and that could be the reason it cant convert the file to the request message MT_REQUEST and thus am not able to see anything in monitoring.
help me guys....this is a simple process and i m stuck...its frustrating
Regards
Naina

File to RFC using BPM

hey guys
i m doin a synchronous File to RFC scenario using BPM and getting a 'NO receiver found error' in MONI,i checked my File as well as RFC adapter in RWB,the sender File adapter is green,RFC adpater is also green and the receiver file adapter is green but says 'no message processing until now'
i m takin help from the followin blog
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
the error in MONI is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checked SM58 as well but it does not have any error XML messages.
and idea where shuld i check?
i check my mappin by using payload from MONI,mapping is working fine
thanx
ahmad
Message was edited by:
Ahmad ansari

Hi Ahmad,
In which step is the error occurring?
Have you checked your BMP status using SXMB_MONI_BPE?
PS: Usefull link: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c">How To Monitor Integration Process (ccBPM)</a>
Regards,
Sergio

Rfc to rfc without bpm scenario

Hi,
I am trying to do RFC to RFC scenario without BPM.but in sender communication channel following error is coming.
Sender channel 'CC_RFC2RFC_SENDER' for party '', service 'BS_RFC2RFC11' (internal name 'RfcServer[CC_RFC2RFC_SENDER]')
Server data: {jco.server.gwhost=192.168.2.12, jco.server.progid=program_rfc2rf, jco.server.gwserv=sapgw00, jco.server.unicode=0}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=000, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=bcuser, jco.client.sysnr=00, jco.client.ashost=192.168.2.12}
Current pool size: 1, maximum pool size : 1
Can anyone please tell me the cause of this error.??
Thanks
Rabi

Hi Priyanka,
I did as you had told but it is again showing same problem.
Will you please help me to resolve it?
Thanks
Rabi

Multiple files to idoc without bpm

Hi
I have gone through the previous threads and came to know that n:1 is not possible without bpm. But in case of idocs you can collect them in r/3 system itself using RSEOUT00 program. But if my scenario is like.......you have 10 files which are coming through ftp and we have to send the idoc to the target system. Is there any way to do this scenario without bpm ??
Thanks
kumar

Hi palnati !
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Multiple IDocs without BPM(occurance change)
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
In case you have multiple IDoc types ref:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Have a look at this blog.. Might be helps to you..
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2748. [original link is broken] [original link is broken] [original link is broken]
Pls reward if useful

Multimapping(File to RFC) using BPM...issue!!!

Hi
Am working on following scenario:
#Two request files merged to map to RFC request ( 2:1mapping )
RFC response is split into two response messages( 1:2 ).
I have done the whole thing in BPM that looks somewhat like this :
Fork(Rec1 , Rec2)-> Transformation1(2:1 map) -> Send(Synchronous BAPI call) -> transformation(1:2 map) -> send(Response 1) -> send(Response 2)
1st part i.e File Merge(2:1) works fine and the request is formed as desired. Next step when synchronous call is made to the RFC the response recieved is where i am facing issues. I dont get the expected response and eventually the following steps fail.
When tested the same RFC(BAPI_SALESORDER_SIMULATE ) in tx SE37 with same data it works fine.
But when same data is sent from XI it returns a error message in place of the response.
Error Message states "Please enter SoldToParty or ShipToParty Number" .
Irony is sold-to-party is sent in the request message and can be seen in payload in monitoring.
Any kinda help is appreciated !!!

> 1. Make sure that bapi commits...there will be a check box option in RFC receiver CC side for this.
>2. Make sure that Sold to party/bill to party field is of 10 char before passing it to SAP.
@ Santosh :
I checked the tab in CC but still the same issue...Do we need to add something to the Name/Value section below that?
And yeah I am sending 10 digits only..
BTW do we need something additional when we call a BAPI from XI apart from the data we normally use in tx SE37.
Can my Configuration be a problem?
For this synchronous call in BPM I have created :
a) 2 interface determinations...One from BPM to ECC and another from ECC to BPM. But both are without any operation mapping as the message types are same & both are synchronous...
b) 1 receiver determination i.e : from BPM to ECC.
c) 1 receiver agreement.

Sending files with and without BPM in one Interface.

Hi All,
I have to send three files to my receiver system. 2 files of same structure after little mapping need to be merged into single file (Using BPM) and once this is successful the third file needs to be posted without any mapping.
I have thought of
1. using two communication channels activated using a UNIX script externally
2. using two comm channels with a activation time difference, i.e the 3rd file should be polled after some time when the first two files polled, but this is not helpful as if the two files doesnt process properly then 3rd file is not desired.
Now my question is can we do this scenario using 1 comm. channel with EOIO , masking or anyother option.
Note: the third file should always be send after the processing of the first two files completes successfully.
Thanks & Regards.

1. put two file in source folder and make synch scenario using BPM ,
2. put third file in some other folder than source folder.
3. after getting successful synch file responce, in the synch receiver file channel run OS command to put third file from other folder to source folder.
hows that ???

Is it possible with out BPM- update transaction from flat file - XI -RFC

Hi
my requirment is: i need to update 2 values transaction(ks01)
Required data we get in flat file(Val1,Val2), that data needs to be updated in transaction KS01 in r/3 system.
Scenario is: Flat file - XI - Rfc -KS01.
im have come across couple of doubts while thinking this way:
->is it possible using fie -to- rfc scenario to update KS01 transaction in R/3 system through RFC, if possible some body please explain the complete process to implement this scenario.
->is it possible file -to- rfc without BPM in XI
can somebody please help out me, how can i approach for the above requirment
-> help would be appriciated and thanks in advance
Regards
Rajesh

The BAPI / RFC corresponding to your requirement is :
BAPI_COSTCENTER_CREATEMULTIPLE
You scenario on a high level would be FILE-XI-RFC
in your IR, map the corresponding fields of the fiel to the fields in the BAPI's interface.
As BAPI is synchronous , you may have to use BPM to implement the Asynch-Sync bridge.
Regards,
Ravi

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 screen shots

Do any body is having simple File to RFC without using BPM screen shots or URLS please provide me

Mclaren,
If the mapping part is clear then u have to look for Adapter monitoring. Since the file is coming in , I suggest u to look for Receiver RFC Adapter. U can monitor the adapter , by chosing
RWB - Component Monitoring( Component With status -All) Click Display
- Choose adapter engine from component nodes.
- In the bottom of the page click adapter monitoring/Component Monitoring(depends on ur SP)
- In the list of adapters choose RFC and choose ur comm.channel and check the status of it.
Best regards,
raj.

FTP TO RFC using BPM

hello
I am creating a scenario of
File to RFC, Using BPM where in again input from File and updating using RFC in multiple steps...( Not creating a scenario of FTP to RFC to FTP )
do i have any web-blog or step wise guide for above scenario
Regards,
Keith

Hello Keith,
The file to RFC scenario can be implemented in the following steps,
1. In the design, create the requsite DataType, MessageType and MessageInterfaces. One message interface will be outbound asynch and the other will be inbound async.
2. Do the message mapping and also the interface mapping as required.
In the configuration, the following has to be done,
1. Create 2 communication channels. One for file as sender and the other for RFC as the receiver.
2. Create 1 sender agreement and 1 receiver agreement. In the sender agreement give your FILE communication channel and in the receiver agreement give your RFC communication channel.
3. Then, do the receiver determination, interface determination.
4. In each of this, the sender service is the business system you have created and the receiver service is the system in which your RFC resides.
Regards,
Bhavesh

File To RFC without BPM

Similar Messages

Maybe you are looking for