Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Process betwen two systems

Former Member
0 Likes
800

There are two different SAP systems and it has been agreed that both systems should be in synchronous with the creation/change of accouonts using some standard transaction. The process should be done using ale/idocs.

How the process can be triggered from the std transaction. Do I need to configure the ale process for this or is there any thing else. Also, how the data flows between these two systems on creation/change the transaction.

There are two different SAP systems and it has been agreed that both systems should be in synchronous with the creation/change of accouonts using some standard transaction. The process should be done using ale/idocs.

How the process can be triggered from the std transaction. Do I need to configure the ale process for this or is there any thing else. Also, how the data flows between these two systems on creation/change the transaction.

5 REPLIES 5
Read only

Former Member
0 Likes
755

Hi,

What acounts are you talking about. What is the transaction you create to do this in SAP.

Please mentioned complete datail.

Regards,

RS

Read only

0 Likes
755

While creating a new GL account or changing a GL account using fspo transaction, the ale process should trigger and the created account data should flow to the other sap system using idocs. Let me know how to do this?

Read only

0 Likes
755

Hi,

Follow these steps.

<b>[1].</b> Create a disctribution model using a<b> transaction BD64</b> for <b>message type GLMAST</b>. Distribute the model view to receiving system.

<b>[2].</b> In Customizing for Distribution (ALE), choose Modeling and Implementing Business Processes _ Master Data Distribution _ Replication of Modified Data _ Activate Change Pointers - Generally. Set the change pointer status to Active, and save this setting. ( or user transaction BD61 )

<b>[3].</b> Choose Modeling and Implementing Business Processes _ Master Data Distribution _ Replication of Modified Data _ Activate Change Pointers for Message Types. Set the change pointer status to Active for the appropriate message type (which is GLMAST in this example), and save this setting.

<b>[4].</b> Choose Modeling and Implementing Business Processes _ Master Data Distribution _ Replication of Modified Data _ Creating IDocs from Change Pointers, and set up periodic jobs for report <b>RBDMIDOC</b> that are regularly used to evaluate and process the change pointers for master data changes.

Now, whenever there G/L account will be created or change, it will send out an IDOC.

To, send all G/L account initially to receiving system you can use <b>transaction BD18</b>.

Let me know if you have any question.

Regards,

RS

Read only

0 Likes
755

Hi,

Where to implement the code for the idoc for filling the segments after doing all those steps. And how to trigger this idoc program?

What needs to be done to set up periodic jobs for report RBDMIDOC. Do we need to do anything inside this program?

Let me clarify asap.

Read only

0 Likes
755

Hi,

You do not need to write a program to fill the IDOC data. SAP does that with standard code.

To setup the period job, look at point-3 of my previouse post. Choose the SPRO path

SPRO
      ----> Basic Component
             ----> Application link Enabling (ALE)
                   ----> Modeling and Implementing Business Processes 
                        ----> Master Data Distribution 
                             ----> Replication of Modified Data
                                  ----> Creating IDocs from Change Pointers

In the above path first select "Define Variant".

- Then it will show you the screen line SE38 with program "RBDMIDOC" and 'variant' option selected.

- hit display button

- on the next screen enter variant name as "GLMAST" and hit create button.

- On the next screen, enter message type as "GLMAST". Hit attribute button on tool bar. Enter description like 'G/L account master data dist.' Hit save twice.

- Hit back button until you come back to SPRO screen.

Now you select Schedule job.

- Enter the job name as "ZGLMAST" and job class as "A".

- Not select "Step" button from toolbar.

- On the next screen. select 'ABAP program' button. Enter program name = 'RBDMIDOC' and select the variant 'GLMAST'.

- Check and save the step and come to the screen of schedule job again

- Now hit the button "start condition'.

- select 'immedaite'

- Check 'periodic job' checkbox

- hit 'period values' button

- On the 'period values' screen, select 'other perido'.

- Enter hours = '1'. ( this is just to define how ofter the job runs. The G/L account master data do not change frequently. You can also schedule to run the job based on Date / time with period value as dialy to run it every night. It is upto you how ofter you want this job to run )

- Check and save settings. Come to the first screen and save the job again.

******************************************************************************************

Since we have activate the change pointers ( step 1 & 2 in my previous post ), whenever a G/L master data is created or changed, it stores the data into change pointer tables. The batch job run at per it schedule. It check if there is any new data in these tables. If it finds data, then it triggers the idoc.

Since you have created distribution model, it sends the idoc to receiving system.

Let me know if you sill have any question.

Regards,

RS

Here you schedule a job for report "RBDMIDOC