Configuring ALE for Master Data Governance for Financials

This document describes the configuration steps that are required to enable the exchange of financial data using Application Link Enabling (ALE) for MDG-F.

Prerequisites

Set Up RFC Connections

Set up RFC connections in the MDG hub and MDG target systems:

Run transaction SM59 (configuration of RFC connections) and provide the required RFC destination details.
Define the logical systems in Customizing for SAP NetWeaver. Run transaction SALE and then choose Basic Settings Logical Systems Define Logical System . Enter all target systems as logical systems.
Run transaction SALE and assign the logical system to a client under Basic Settings Logical Systems Assign Logical System to Client .

Define Global Company Codes

If the company code is required for your data, you must define the global organizational units for company code. Run this activity in Customizing for SAP NetWeaver under Start of the navigation path Application Server Next navigation step IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Global Organizational Units Cross-System Company Codes End of the navigation path . Create cross-system company codes and map all company codes in use to the defined global company codes.

Define Global Business Areas

If the business area is required for your data, you must define the global organizational units for business areas. Run this activity in Customizing for SAP NetWeaver under Start of the navigation path Application Server Next navigation step IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Global Organizational Units Cross-System Business Areas End of the navigation path . Create cross-system business areas and map all business areas in use to the defined global business areas.

Procedure

The following steps are required to configure ALE for MDG-F (transaction SALE) in the MDG hub and MDG target system.

Create a Distribution Model

To create a new distribution model in the MDG hub, carry out the following steps in both systems:

Run transaction SALE (Display ALE Customizing) and choose Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views . Alternatively, run transaction BD64 (Display Distribution Model).
In editing mode, create a new model. Choose Create Model View. Enter a short text and a technical name.

Choose Add Message Type for the newly created model. Enter the logical sender system and receiver system and add a message type from the following table. Repeat this step for all required IDoc message types. Afterwards, save your entries.

IDoc Message Type	Description
GLMAST	Master data G/L accounts (Master IDoc)
COSMAS	Master cost center
COGRP1	Cost center groups
COELEM	Cost element master data
COGRP2	Cost element groups
PRCMAS	Profit center master record
COGRP6	Profit center groups

After you have saved your settings, you need to generate a partner profile. Choose Environment Generate Partner Profiles . Select the model view you just have saved and enter the target system. Select immediate processing for the output mode and inbound parameter. Choose the pushbutton Execute.
After you have generated the necessary partner profile, choose Edit Model view Distribute to distribute this model view to your target system.
Enter the target system and repeat step 4 to generate partner profiles on the MDG client.

Enhance Distribution Model for Confirmation Message

The configured distribution model needs to be enhanced to send a confirmation message back from the target client to the client of the MDG hub, as follows:

Enter the client of the MDG hub and call transaction SALE.
Goto Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views . Mark the distribution model you have generated previously.
Select Environment: Change Partner Profile from the dropdown list.
Open Partner Type LS and select the profile of the target system.
Choose the pushbutton Create inbound parameter.
Chose the message type ALEAUD and enter the process code AUD2.Save your entries.

In the client of the target system, the distribution model also needs to be enhanced, as follows:

Enter the client of the target system and call transaction SALE.
Goto Communication Maintain Distribution Model and Distribute Views . Mark the distribution model you have generated previously.
Select Environment: Change Partner Profile from the dropdown list.
Open Partner Type LS and select the profile of the source system.
Choose the pushbutton Create outbound parameter.
Chose the message type ALEAUD, select the receiver port from the selection list, and enter the value ALEAUD01 as the basic type.
Select Transfer Idoc Immed. as the output mode and save your entries.

Define Business Systems

In the client of the MDG hub, a business system for the target client needs to be created as follows:

Call transaction MDGIMG.
Goto General Settings Data Replication Define Custom Settings for Data Replication Define Technical Settings Define Technical Settings for Business Systems .
Choose the pushbutton New Entries.
Enter the business system, logical system, and RFC destination for the target client.

Mark the line of the newly defined business system and select the folder Define Bus. Systems, Bos. Enter all desired business object types:

Business Object Type	Description
158	Cost Center
229	Profit Center
892	General Ledger Account Master
983	Cost Element
984	Cost Element Group
895	Cost Center Group
896	Profit Center Group

Mark each business object type and choose the folder Define Bus. Systems, BOs, Communication Channel. Choose the pushbutton New Entries and select the communication channel 2 Replication via IDoc. Repeat this for all defined business object types.
Save your entries.

Create Replication Models

After the distribution model and the business system have been defined in the client of MDG hub, it is now possible to create a replication model for each IDoc type:

Call transaction MDGIMG.
Goto General Settings Data Replication Define Custom Settings for Data Replication Define Replication Models .
Choose the pushbutton New Entries and define a replication model with name, description, and data model 0G for each IDoc type listed.

For each defined replication model, mark the line of the replication model and select the folder Assign Outbound Implementation. Choose the pushbutton New Entries. Assign the corresponding outbound implementation to each replication model you have defined:

Outbound Implementation	Description
1012	General Ledger Account Master IDoc
1102	Cost Centre IDoc
1112	Cost Centre Group Hierarchy IDoc
1182	Cost Element IDoc
1192	Cost Element Group Hierarchy IDoc
1122	Profit Centre IDoc
1132	Profit Centre Group Hierarchy IDoc

For each outbound implementation you have described in step 4, mark the line of the implementation and select the folder Assign Target Systems for Repl. Model /Outb.Impl. Choose the pushbutton New Entries. Assign the business system with the ERP client of the target system.
Save your entries

Activate Replication Models

Activate the previously defined replication models as follows:

Call transaction MDGIMG.
Goto General Settings Data Replication Define Custom Settings for Data Replication Define Replication Models .
In the table of replication models, mark all replication models you have previously defined.
Choose the pushbutton Activate and check the log for error messages. Successful activation is indicated with a checkmark in the Active column.
Check the log and make sure that all replication models marked have been activated successfully.

Result

You have successfully set up ALE for MDG-F.