Skip to Content
author's profile photo Former Member
Former Member

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.



Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Jul 04, 2008 at 06:50 AM

    Hi Sravya,

    Whenever you choose 0.unbounded in MEssage tab of MM

    structure like



    with occurence one to one will appeare.

    Make sure that you have not mapped these two fields else you will get mapping exception

    because your message that will enter into XI will not have these two tags so if these two fields with 1-1 are mapped and they does not appeare in input it will throw exception so leave them without mapping. XI will take care of that as it is appended by XI only.

    How you will MAP :

    you will have o.......unbounded occurence of <CUSTOMER> at source side and o.....unbounded for RFC .it will come Automatocally when you will select o.unbounded in Message of MM

    Map Source root with 0......Unbounded occuernce of Target RFC's root node . So it will crate that many no. of RFC node at the Target side.

    USe BPM :

    Exception can be easly raised,

    No need to use Inhanced MApping for this purpose.

    Now Comming to final and main Design

    take a block in mode ForEach(can be found in Block Property).

    Take a send step and make it synch.

    Consider Four Nodes Of RFC Root are Created at Target side

    So with the setting For each they will be Considered as a Individual messages rather than Considering it as Whole as one message.

    Also Block will Ask you for Multiline Element and Current Element.

    You should have a Conatiner two VAriable that will contain the Message Type of RFC Declare one as Multiline and other as normal.

    Give Multiline Variable in Multiline Element Option and The NOrmal One as a Current Element

    So it will Come to know what it has to do.

    Now You will get Response to every Record(Customer Info)

    You have to collect these Mwessages in Container .

    USe Mapping to View in Desire Formate.

    REvert if Not Cleare

    Reward Points if HElpful


    Sunil Singh

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 30, 2008 at 10:41 PM


    After importing the RFC in to PI, take the WSDL from there and edit the occurances in WSDL. Now upload this WSDL as external definition. Then use it in the mapping. It should solve the problem.

    Otherwise is have your RFC changed to take multiple customer details in one go as input.


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 02, 2008 at 02:53 AM


    u go with the option(1) what Jai Shankar had given and at the same time use Node Functions, in node functions use REMOVE CONTEXT function, so that u problem will be rectified.

    Source filed -

    >Remove Context----

    >Target field.

    U try to do the mapping like above mentioned.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.