Scribd
Upload
580 views13 pages

ALE Configuration - IDOC FB70

This document provides instructions for setting up ALE (Application Link Enabling) to distribute master data between SAP systems. It describes how to create a distribution model view using transaction BD64 to define sender, receiver, and message types. Common message types like GL, CO (cost objects), and PR (profit centers) are listed. It also explains how to generate partner profiles, distribute the model view, enter master data, schedule background jobs to run ALE periodically, and automate the distribution process using change pointers and scheduling program RBDMIDOC.

Uploaded by

amitjajoo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
580 views13 pages

ALE Configuration - IDOC FB70

This document provides instructions for setting up ALE (Application Link Enabling) to distribute master data between SAP systems. It describes how to create a distribution model view using transaction BD64 to define sender, receiver, and message types. Common message types like GL, CO (cost objects), and PR (profit centers) are listed. It also explains how to generate partner profiles, distribute the model view, enter master data, schedule background jobs to run ALE periodically, and automate the distribution process using change pointers and scheduling program RBDMIDOC.

Uploaded by

amitjajoo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 13

Setup ALE

Use transaction BD64 to access the ALE Distribution Model set-up screen
Use the “Create model viw” button to create a new model view

This model view will hold the distribution rules, which contain the following:
 Sender client
 Receiver client
 Message type
Then select the Model View, and use the “Add message type” button to add new
message types. The message type determines which data is to be distributed.

For each message type, select the sender, receiver and message type.

Typical message types are:


 GLMAST – GL account master data
 COSMAS – cost centre master data
 COELEM – cost element master data
 PRCMAS – profit centre master data
 COGRP1 – cost centre groups
 COGRP2 – cost element groups
 COGRP6 – profit centre groups

Internal orders and WBS elements don’t work very well using this method, as they are
tagged with an “origin system” and can only be changed in that system!!
Once the message types have been added, select “Environment – Generate Partner
Profiles” from the top menu.

Here simply select the “Collect IDocs and transfer” option on the outbound process.
This is to ensure that the process doesn’t hog all the online dialog sessions when it is
run…you won’t be very popular!

It is also possible to generate the profiles by system. Just enter the required system in
the Partner System box at the top.
When all is ready, execute the transaction.

You will get a report listing what has been created, what exists already and what is
missing.

What you will need before this step is the following:


 A logical client name for each system that you are attempting to connect with.
These must exist in the source client.
 A RFC connection between the source client and all systems set-up in the
model view.

Ask BASIS to do this.


Once the transaction has been run, it is possible to see what it has set-up.

Select “Environment – Change Partner Profile”

You will end up here:

It is possible to drill down into each message type to view / change the settings:
Now, the Model View needs to be distributed to all systems that will receive data.

This will move the Model View settings onto all receiving systems. You will then
need to logon to each receiving system, and generate the Partner Profiles there.

This concludes the setup process.


Run ALE

In this path you will find all the master data objects that can be distributed via ALE.
Complete the data as required in each screen:

Then schedule the job to run as a background job. This also ensures that you don’t
hog all the system resources.

The progress of the ALE distribution can be monitored using BD87.


Automating the Distribution
The ALE distribution can be automated. This is achieved by activating “Change
Pointers” for the message types. These are then stored in a table and sent via a
periodic job that you can schedule to run anytime.
Run “Activate Change Pointers – Generally”

Then run “Activate Change Pointers – For Message Types”

Find your message types and “tick” them.


Now you need to set-up the background job to pick-up these change pointers:

Create variants for your message types, based on program RBDMIDOC. Then
schedule the program to run periodically, using these variants.

NOTE: If you use this method to distribute, the sending and receiving message type
must be set to “transfer IDoc immediately” or else they will just accumulate in BD87.

You might also like