Application Link Enabling (ALE) and Product Data Replication (PDR) – An Overview
Data distribution requirements:
Perform (selective) transport of product data to different target systems, especially with regard to Variant Configuration master data.
Ensure strong, reliable, and fast data distribution.
Use Change Management across system boundaries.
Perform monitoring across different systems.
Don't interfere with or interfere with the data distribution of the live production operation of a system.
Which tools are available for data distribution, and when should which tool be used?
The SAP system differentiates between two distribution options.
On the one hand, there's direct distribution. Here, you use a report that selects the objects that are to be distributed.
Second, it's possible to control the distribution using change pointers. Each change to an object, such as a status change in a material master, can generate a change pointer. This change pointer can create an IDoc (intermediate documents) that control the transport from the outbound to the target system.
For more detailed information, see the SAP documentation on ALE.
If an entire model of the Variant Configuration is to be distributed directly using ALE, a certain sequence must be observed.
Delivered Message Types (IDOCs)
| Material | MATMAS | Bills of Material | BOMMAT |
| Characteristic (Basic Data and Dependencies) | CHRMAS | Classes (Basic Data and Dependencies) | CLSMAS |
| Object Classification | CLFMAS | Global Object Dependency | KNOMAS |
| Configuration Profile | CNPMAS | Variant Table | VTAMAS |
| Variant Table Content | VTMMAS | Constraint -Net | DEPNET |
| Functions | VFNMAS | Documents | DOCMAS |
| Cost Centers | COSMAS | Cost Center Group | COGRP |
| Cost Elements | COELEM | Cost Element Group | COGRP2 |
| Activity Types | COASMAS | Activity Type Group | COGRP5 |
| Rates | COACTV | Change Numbers | ECMMAS |
| Prices and Conditions | COND_A |
Interface designs (LO-VC) are distributed using a BAdI (object name: VariantConfigUI, object type: BUS1401, method: Savem).
Characteristic groups (AVC) are distributed using a BAdI (object name: CharacteristicGroup, object type: CHARGRP, method: Savem).
The valuation of material variants is also distributed via the material master. You need to make settings here in the Global Settings in material master Customizing.
Product Data Replication
A product version is created in a central PLM system. This version consists of consistent data and contains the product structure.
The product version is distributed with the product data replication of the entire product using ALE (Application Link Enabling) technology.
Product Data Replication PDR is used to simplify the distribution of products from a central PLM system to various production systems.
The product data is compiled in the replication workbench. For example, a material master is selected and, as part of a baseline procedure, all related data is collected and transferred to a configuration folder.
The target system is then defined and the responsible recipients are notified. During distribution, either only the delta information or all data is transferred as part of the initial distribution.
PDR Customizing
The basis for the distribution is a so-called distribution model. This must contain all required objects in the source and target system.
Product data replication is based on configuration management. In the standard system, the tool is used to map resumes of products. A lifecycle profile is needed for this. This includes the individual phases of the resumes of products.
We also need an explosion profile. This controls the scope of the data to be distributed. You can restrict which data is to be collected for distribution. This affects:
Plants to Be Considered
Object types that are not to be taken into account
Class types that aren't to be considered
Edges between objects that aren't to be taken into account.
The last point in particular is important. When the objects are collected, all objects that are related can be considered (the so-called "edges"). Without exclusion, almost everything can be distributed quickly, for example, because many materials are linked via classification and there via class hierarchies.
Further technical settings are required in connection with UPS.
Working with Replication Workbench
This figure provides an overview of the work to be performed in the replication workbench.
You have to create a configuration definition in the replication workbench (transaction CRWBD) and assign a lifecycle profile to it.
A configuration folder is created in the configuration definition.
An explosion profile is assigned to the configuration folder.
A controlling object is assigned to the configuration folder. Here's a different SAP system or a different client.
The configuration folder is released to be able to create baselines.
A baseline is created for the configuration folder. This baseline contains the data to be distributed.
To do this, the baseline must be exploded and fixed.
As a result, the baseline contains the data that is to be distributed, which can be viewed as an "explosion result". (FOX Analysis)
A distribution order with a distribution package is created for the baseline, and the distribution is started.