03/02/2017 1 Jonathan Eemans JE Consulting
Master data distribution
in SAP
Implementation guide
03/02/2017 2
Master data distribution in SAP
A typical SAP landscape consists of a
– development
– acceptance
– production
environment and possible other environments (training, transition etc.).
And there can be multiple SAP landscapes with different environments.
Often master data is created separately in the different environments of a
certain landscape or multiple SAP landscapes. This is time consuming!
Master data distribution can automate this process easily using IDoc’s and
ALE.
Introduction
03/02/2017 3
Master data distribution in SAP
IDoc's (Intermediate Documents) are standard SAP format for electronic
data interchange between systems (Intermediate Document). IDoc's are
created and dispatched in distributed systems using message types and
SAP business object methods (BAPIs).
The integration technology Application Link Enabling (ALE) is an important middleware tool in SAP's Business Framework Architecture. It incorporates the exchange of business information across these systems whilst ensuring consistency and integrity of the data.
In the case of master data distribution the same transaction that was performed on the sending system is again performed on the receiving system with the data contained in the IDoc. It can be set up in such a way that any changes made to specific fields in master data tables can automatically trigger off the ALE distribution process for that particular master data object.
IDoc's and ALE
03/02/2017 4
Master data distribution in SAP
The documentation of IDoc's can be displayed via transaction WE60.
An IDoc consists of... One Control Record: It includes all the control information of the IDoc,
including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The structure of the control record is the same for all IDoc's.
One or many Data Records: The data records contain the actual data that needs to be exchanged. An IDoc can have multiple data records, such as header information and detail lines.
One or many Status Records: Status records are attached to the IDoc as the IDoc achieves different milestones. At every milestone, a status code, date, and time are assigned. Status records help you determine whether an IDoc is in error.
IDoc documentation
03/02/2017 5
Master data distribution in SAP
Transaction: SALE - ALE Customizing
The following steps are important for IDoc’s:
Create background ALE user;
Maintain number ranges;
Global company codes;
Change pointers;
Define logical systems;
Setup RFC destination;
Create Port;
Define distribution model;
Distribute distribution model;
Generate Partner Profile.
ALE with IDoc setup
03/02/2017 6
Master data distribution in SAP
In order to work with IDoc's in FICO you have to define global company
codes and assign global company codes to chart of accounts and company
codes.
Setup: global company code
System A
CoCd 1 GCoCd A
CoCd 2 GCoCd B
…
System B
GCoCd A CoCd 9999
GCoCd B CoCd 9998
…
03/02/2017 7
Master data distribution in SAP
Changes to master data
objects are managed using
the Shared Master Data
(SMD) tool. The SMD tool is
connected to the change
document interface.
If you want to be able to
distribute changes to master
data, you must write change
pointers at the same time as
the change documents in the
sending system (not needed
in the receiving system).
Setup: change pointers
03/02/2017 8
Master data distribution in SAP
Change pointers are activated generally…
…and change pointers are activated for message type.
Setup: change pointers
03/02/2017 9
Master data distribution in SAP
The distribution of systems makes it necessary to be able to identify every
system individually within a network. The "logical system" is used to do this.
A logical system is an application system within which the applications are
co-ordinated to work in one database. In the SAP sense of the word, a
logical system corresponds to a client.
Setup: set up logical system
03/02/2017 10
Master data distribution in SAP
You define the technical parameters for the RFC destinations.
This must be set up for all the logical destinations manually. RFC
destinations are client independent.
The Remote Function Call is controlled via the parameters of the RFC
destination.
The RFC destinations must be maintained in order to create an RFC port
Setup: create RFC destinations
03/02/2017 11
Master data distribution in SAP
A port definition controls the medium of communication.
Since memory-to-memory transfer is used, a transactional RFC (tRFC) port
is created in SAP.
Setup: create port
03/02/2017 12
Master data distribution in SAP
The senders and recipients are determined from a distribution model that
maintains a list of messages exchanged between two systems and their
direction of flow.
Setup: define distribution model
03/02/2017 13
Master data distribution in SAP
Once you have created a distribution model in the sending system you can
distribute it to the other systems.
Setup: define distribution model
03/02/2017 14
Master data distribution in SAP
Once you have created a distribution model you can generate partner
profiles or create them manually.
Partner profile
Setup: generate partner profile
In partner profile
you can define if
mail is sent to
SAP Inbox in case
of error and to
whom.
03/02/2017 15
Master data distribution in SAP
Every x min the following programs are executed in sending system …
RBDMIDOC: create IDoc's from change pointers (G/L
Accounts, Cost Elements, Activity Types, Profit Center, Cost
Center, Profit Center Group and Cost Center Group etc.)
Every x min the following programs are executed in the receiving systems…
RBDMANI2: process IDoc's in error.
Setup: IDoc job scheduling
03/02/2017 16
Master data distribution in SAP
Specific transactions exist for mass transferring of IDoc's. These
transactions can be used during migration.
Migration of master data using ALE
Data TransactionCode
G/L Account BD18
Cost Element BD24
Activity Type BD25
Cost Element Group KAVC
Profit Center KE77
Cost Center BD16
Profit Center Group KE79
Cost Center Group KAVB
! Check your system settings before mass transfer, i.o.w. try not to
crash your system.
! OSS Note 384971 - System parameters for a high interface load.
03/02/2017 17
Master data distribution in SAP
IDoc's’ can be monitored via different transactions such as
WE02 / WE05 – IDoc List,
WE07 – IDoc Statistics, and
WE09 – IDoc Search.
Follow up IDoc’s in SAP
03/02/2017 18
Master data distribution in SAP
IDoc’s can be searched via creation date, IDoc type, message type,…
Variants can be saved for search criteria used regularly.
Follow up IDoc’s in SAP
03/02/2017 19
Master data distribution in SAP
In case an IDoc was not send correctly, i.e. error passing to port, error in
ALE etc., the IDoc can be resend afterwards via SA38 RBDOUTPU.
IDoc error handling @ outbound side
03/02/2017 20
Master data distribution in SAP
In case an IDoc was not dispatched immediately, the IDoc can be resend
afterwards via SA38 RBDOUTPU.
IDoc error handling @ outbound side
03/02/2017 21
Master data distribution in SAP
In case an IDoc was not received correctly, e.g. customising setting of new
field status group was imported after G/L Account was transferred with new
field status group, the IDoc can be reprocessed afterwards via SA38
RBDINPUT.
IDoc error handling @ inbound side
03/02/2017 22
Master data distribution in SAP
In case an IDoc was not received correctly, i.e. error passing to port, error in
ALE etc., the IDoc can be reprocessed afterwards via SA38 RBDINPUT.
IDoc error handling @ inbound side
03/02/2017 23
Master data distribution in SAP
In case an IDoc was not transferred automatically, the IDoc can be resend
afterwards via SA38 RBDINPUT.
IDoc error handling @ inbound side