Skip to Content
avatar image
Former Member

How to make use of Multiple Origin Composition if my table is not on my gateway system

Hello Guys, my exercise is to make use of the Multiple Origin Composition functionality to read and update data from the table PA0002 which exist on two of our Backend Systems but sadly not on the gateway system I’ve to use.

My Approach:

I created on both Backend Systems a Function Group called “Z_ODATA_PA0002” and inside it I created my Function Modules:

  1. READ_ENTITY_PA0002
  2. READ_PA0002
  3. UPDATE_PA0002

Which manage all the database calls. (Code is 1:1 on both backend systems)

I also created a structure and a table type which I transported to my gateway system to be able to give them as parameters to my RFC. For the beginning I just wanted to work with three fields, PERNR, VORNA, NACHN.

Then I created a SEGW Project on my Gateway System, inside its CRUD Methods I call my RFC Function Modules. I’m receiving my data, but the when I add “;mo” to my service to enable MOC functionality, I see that “SAP__Origin” always says that the data origin is my gateway system, not one of my backend systems.

I guess I did something wrong, hopefully some of you can help me with my problem and maybe explain what I did wrong :).

How I did it in the past (It worked):

I created a ZMOC Table on all my systems share the same name and type. Then I created a SEGW Project called “ZMOC” on all three Systems and implemented all the crud methods on all the systems (same code on all 3 systems). Then I added the system aliases to my gateway service. And it worked, I was able to read data from all my systems with the right Origin. And update worked as well.

I really appreciate your help,

best regards,

Jan Bednarski

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers