ALE Transfer of Variant Configuration Data:  

This document describes ALE (Application Link Enabling) distribution of master data for variant configuration between SAP systems. 

Here we will see one example to transfer material master from K01(100) to K01(300)           

ü  Run Transaction code BD10:

Logical system: Fill the target system ID where we want to send the Data.

Here we are sending material master data to 300 Client so, system ID – X08CLNT300

Message Type: To move every master data we need enter correct message type. Here in our case we are moving material master so standard message type is “MATMAS”

Note: 

      1. Read further document to know the VC Masters data message types.

      2.  The data to be transferred is interdependent, so we advise you to transfer data in                                    the sequence, which we shown below.

1. Characteristics and Characteristic Values:

Most objects for variant configuration are dependent on characteristics. For this reason, characteristics must be transferred first.

Message type: CHRMAS
Transaction Code: BD91

2. Classes

When you use ALE to distribute classes, the characteristic assignments are also transferred.

Message type: CLSMAS
Transaction Code:       BD92

3. Variant Table Structures

These are the variant tables that are created to support data maintenance.

Message type: VTAMAS
Transaction Code:       CLD3

4. Variant Table Contents

Once the structures of the variant tables have been distributed, their contents can be transferred.
Message type: VTMMAS
Transaction Code:       CLD4

5. User-Defined Functions (Variant Functions, VC Functions)

User-defined functions in variant configuration let you use function modules that you have written, to check and infer characteristic values.
The distribution of functions only transfers the framework (texts, characteristics, and so on). The function modules that belong to the functions must be transferred first, using the standard transport system.
Message type: VFNMAS
Transaction Code:       CUFD

6. Object Dependencies (Except Constraints)

Dependencies (preconditions, selection conditions, procedures, and actions) usually refer to characteristics, characteristic values, variant tables, and variant functions. For this reason, dependencies must be distributed after this other master data. The dependencies transferred here are global dependencies. Local dependencies are transferred with the objects to which they are assigned. For example, if you created a selection condition as a local dependency for a BOM item, this dependency is transferred when you use ALE to distribute the BOM (bill of material).

Message type: KNOMAS
Transaction Code:       CLD2

7. Constraints

Message type: KNOMAS
Transaction Code:       CUK2
All Constrain move with the NET Dependency (Constrain Net) There is no separate Transaction code for Constrain. 

8. Constraint Nets

Message type: DEPNET
Transaction Code:       CUK2

9. Assignment of Dependencies to Characteristics and Characteristic Values

The characteristics are transferred once more to do this. Start ALE distribution for characteristics again, and the system transfers the assignments.
See point 1: Characteristics and Characteristic Values

10. Configurable Materials

Depending on how many configurable materials you have, you can use ALE to distribute them or create them in the target system. The other materials in BOMs for configurable materials are transferred to the target client by the usual data transfer.
Message type: MATMAS
Transaction Code:       BD10

11. Configuration Profiles

Configuration profiles must be distributed after the configurable materials, because the key of the material identifies the profile. During the ALE process, the dependencies for the configuration profile are also transferred, and are reassigned to the profile in the target client. At the same time, the class assignments belonging to the configurable material (in the variant class) are transported.
Message type: CNPMAS
Transaction Code:       CLD1

12. Classification

You only need to distribute classifications if you have classified materials. Classifications in the variant class are transported with the configuration profile (CNPMAS).
Message type: CLFMAS

13. Material Variants

If you use ALE to run Distribution of Material Variants, you can send the values assigned during configuration in the IDocs of the material master.

Message type: MATAMS

14. Bills of Material

Material BOMs for configurable materials can be distributed using ALE. The transfer also assigns the dependencies for BOM items to the items. Make sure that the dependencies and all the materials required already exist in the target system.
If material variants are assigned to the BOM, there may be problems transferring the super BOM.

Message type: BOMMAS
Transaction Code:       BD30

15. Interface Design

Interface design the consider CU50 – Simulation of result screen TAB’s. TAB’s has group of features.

Message type: VCUI_SAVEM

Transaction Code:           CUID

16. Change Master

Message type: ECMMAS
Transaction code: CC92

Pre-requisites:

Activate the change pointer @ BD50 for message type ECMMAS

Create IDOC @ BD21 Transaction.