SAP VC Master Data Distribution Using ALE
Introduction:
SAP Variant Configuration (VC) Master Data can be distributed across the different Clients /Systems in the
organizations using ALE functionality of SAP.
Master Data Includes the following objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Characteristics and Values
Classes
Variant Table Structures
Variant Table Contents
User Defined Functions
Object Dependencies (Selection Conditions, Pre Conditions and Procedures)
Dependency Nets
Configurable Materials
Configuration Profiles
Bill of Materials
User Interface
Message Types Used for VC Master Data:
Characteristics and Values: Most objects for variant configuration are dependent on characteristics. For this
reason, characteristics must be transferred first.
Message Type used for Characteristic and value transfer is CHRMAS.
SAP Transaction: BD91
Classes: During the ALE distribution of the classes, the characteristic assignment also transferred.
Message Type used for Class transfer is CLSMAS
SAP Transaction: BD92
Variant Table Structure: Variant table structures created to support the maintenance of the data relevant for
variant configuration.
Message Type used for Variant Table Structure transfer is VTAMAS
SAP Transaction: CLD3
Variant Table Contents: After distribution of the variant table, table contents can be transferred.
Message Type used for Variant Table Contents transfer is VTMMAS
SAP Transaction: CLD4
User Defined Functions: User defined variant functions are used to check and infer the characteristic values.
In side these function, ABAP function modules are used.
Note:The distribution of functions only transfers the framework (Characteristics, texts, etc.,) the function
modules used in functions must be transported first using the standard SAP transport management system.
Message Type used for User Defined Functions transfer is VFNMAS
SAP Transaction: CUFD
Object Dependencies: The dependencies transferred here are global object dependencies. Local object
dependencies are transferred with the objects to which they are assigned.
Message Type used for Object Dependencies transfer is KNOMAS
SAP Transaction: CLD2
Constraint Net (Dependency Net): These also can be distributed as of release 4.5
Message Type used for Dependency Net transfer is DEPNET
SAP Transaction: CUK2
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 used for Material transfer is MATMAS
SAP Transaction: BD10
Configuration profiles: These 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 used for Configuration Profile transfer is CNPMAS
SAP Transaction: CLD1
Super BOM: 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.
Message Type used for Material BOM transfer is BOMMAT
SAP Transaction: BD30
User Interface: You can use ALE to transfer interface designs for variant
configuration.The distribution of interface designs uses BAPI technology
Message Type used for User Interface transfer is VCUI_SAVEM
SAP Transaction:CUID
