1.

Synopsis/Business Background
There are various methods and tools for creation of Master Data in SAP, these methods need to be performed in every system where Master data is required manually. An effective way of creating and maintaining various types of master data will save a lot of time both for Consultants and End users especially during the development and testing phase. SAP has identified this need and has given a very beautiful and effective tool which can be used to transmit the Master data from and between different systems and clients in SAP. The tool is known as ALE (Application link enabling). Hence, my focus in this white paper is to put down my experience on using this Master data distribution model which can be easily setup with very minimal configuration steps and without much of technical knowledge.

2. Functionality of the tool

The tools helps in maintaining various Master data in SAP like GL accounts, Cost center, Profit center, Cost center hierarchy, Profit center hierarchy etc, across the landscape. (Development server / Acceptance server / Regression server, pre production & Production server) Steps for setting the configuration (BD67)

1. Identification of Server which will be used as a Master data repository. This 2. 3.

4. should be created under the node Master data distribution which is SAP standard. E.g. Development box (Golden client) Identification of various other environments within the Landscape for which Master data will be distributed from the source server. E.g. Acceptance server, Regression, Quality etc Identification of the various Master data which will be used within the distribution model e.g. GL accounts, Cost center, profit center etc. The Master data is identified in terms of Message types a. GL account GLMAST (controlled at Company code level) b. Cost center COSMAS (controlled at Controlling area level) c. Profit center PRCMAS (controlled at Controlling area level) d. Cost center group COGRP1 (controlled at Controlling area level) e. Profit center group COGRP6 (controlled at Controlling area level) Assign the Message types to the various Receiving servers. Assign any Filters to restrict the master data distribution by Controlling area or Company code. E.g. specify the values for which only master data should be distributed.

5.

6.

Steps to run the Master data distribution:

2/15/2012 Version #

1 of 3

1. Create the master data within the Repository system. Usually master data can be
created manually or using any tool (LSMW, BDC) for bulk data. 2. Send the master data from the Repository system. (Select the respective values and message type which should be transmitted . performed within the Repository system) 3. Get the master data into the Receiving system. (Select the values and message type which should be transmitted. Performed within the Receiving system)
Repository system GL Account : 1000000 Company code : 9999 Message Type : GLMAST Transaction code: BD18

Same GL account distributed across servers

GL Account : 1000000 Company code : 9999 Message Type : GLMAST Transaction code: BD19 Acceptance System

GL Account : 1000000 Company code : 9999 Message Type : GLMAST Transaction code: BD19 Quality system

GL Account : 1000000 Company code : 9999 Message Type : GLMAST Transaction code: BD19 Production system

The table below describes some of the Master data which can be distributed along with Message types available for each of Master data and transaction codes used for Send & Get functions for Master data distribution. Master Data GL Accounts Cost center Profit center CC group PC group WBS element Internal order Cost element Activity type Message type GLMAST COSMAS PRCMAS COGRP1 COGRP6 Send transaction code BD18 BD16 KE77 KAVB KE79 CJAL KOA1 BD24 BD25 Get Transaction code BD19 BD17 KE75

COAMAS

BD26

3. Benefits of using the ALE

ALE has many benefits: Application data can be distributed between different releases of SAP systems Data can continue to be exchanged after a release upgrade without requiring special maintenance

2/15/2012 Version #

2 of 3

 Customers can add their own enhancements Communication interfaces enable connections to non-SAP systems. More recent SAP and R/2 systems can communicate with each other. ALE has functions for monitoring messages flows and handling communication problems.

2/15/2012 Version #

3 of 3