Distribution to Decentralized Systems

Use

You distribute data to create decentralized systems and to keep the data they contain up to date.

Prerequisites

You have configured the following settings for product data replication (PDR):

Application Link Enabling (ALE)

You have configured the standard ALE Customizing settings (set up the RFC destination, distribution model, and so on).

You make these settings in Customizing by choosing Logistics – General Product Data Replication Application Link Enabling (ALE) Modeling and Implementing Business Processes.

Note
SAP ships the ISDFPS_SETUP DFPS System Structure of Decentralized System template for creating distribution modules.

End of the note.
Document Distribution

You have activated the event type linkages for document distribution and verified the workflow Customizing settings.

You make these settings in Customizing by choosing Logistics – General Product Data Replication Workflow Settings for Product Data Replication Document Distribution .

Configuration Management

You are familiar with the relevant standard profiles in Customizing under Start of the navigation path Logistics – General Next navigation step Product Data Replication Configuration Management Define Explosion Profiles. End of the navigation path The following explosion profiles are provided in the standard system:

Explosion Profiles

Explosion Profile	Description	Use
DFPS_A	DFPS replication (structure)	Domestic base (organizational structure, administrative chain of command, and wartime establishment)
DFPS_E	DFPS replication (operation)	Operational structure
DFPS_LES	DFPS replication (LES in operation)	Distribution to Logistics Execution System
DFPS_PMAEB	DFPS PM – Change authorization objects	Objects that are required when change authorization is forwarded
DFPS_PMAEN	DFPS PM – Forwarding change authorization	Objects that are required for a consistent data status when change authorization is transported
DFPS_PMNOT	DFPS PM notification	Dependent data in the maintenance notifications (dynamic FOX explosion)
DFPS_PMORD	DFPS PM order	Dependent data in the maintenance order (dynamic FOX explosion)
DFPS_PMRUC	DFPS PM – Redistribution	Profile automatically created from DFPS_PMRUV (objects and assignments excluded)
DFPS_PMRUV	DFPS PM – Redistribution TEMPLATE	Objects and assignments that are not to be excluded (template for DFPS_PMRUC)

For the dynamic FOX explosion, you define assignments of explosion profiles for object types in Customizing under Start of the navigation path Defense Forces & Public Security Next navigation step Distributed System Landscape Application-Specific Settings Distributed Maintenance Explosion Profile for Dynamic FOX Explosion. End of the navigation path

Uniform Packaging Service

In Customizing under Logistics – General Product Data Replication Application Link Enabling (ALE) Uniform Packaging Service (UPS) Define Packet Types ,you have made the following settings:
- Packet Types
  
  Packet type SAP_REPLI is shipped in the standard system for the distribution process. This packet type has been extended to include the object types required for the Defense Forces & Public Security component.
- Automatic Activity Control (Outbox)
  
  You define for each packet type whether it is to be posted automatically or manually in the target system.
- Automatic Activity Control (Inbox)
  
  You define for each packet type whether it is to be sent automatically or manually in the source system.
  
  In Customizing under Defense Forces & Public Security Distributed System Landscape Application-Specific Settings Distributed Maintenance Assign UPS Package Types ,you have assigned the packet types that you use .

In particular, see SAP Notes 1127288 (for setting up decentralized systems) and 758625 (for including the component-specific infotypes in the ALE mechanisms).

Features

Technology

The system uses the following standard components:

Product Data Replication
- Replication Workbench
  
  This is a tool based on the product structure browser that can be used to control the entire product data replication process.
  
  Note
  Instead of the standard transaction CRWBD, you can use transaction /ISDFPS/CRWBD, which supports the additional, component-specific authorization checks. Also see Triggering the Distribution of a Force Element .
  
  End of the note.
- Configuration Management
  
  This is a standalone application whose objects (configuration folder and baseline) are integrated directly in the replication workbench.
  
  The configuration folder stores the product portfolio and enables systems and users to register. The baseline for a configuration folder contains the exploded structure across the objects defined in the configuration folder.
- Document Distribution
  
  A tool that is responsible for distributing data.
  
  A workflow controls whether e-mails are sent to registered e-mail recipients and/or whether ALE distribution packets are generated, in which IDocs are sent to registered receiving systems.
- Framework for Object Explosion (FOX)
  
  The FOX enables you to explode large numbers of objects of any type quickly and simultaneously. Based on one or more initial objects, dependent objects that are related to the initial object are determined in a recursive explosion process.
- Uniform Packaging Service (UPS) or ALE distribution unit
  
  A delivery note that can send an entire list of generated IDocs to different destinations where it posts them in a consistent manner.
  
  Note
  End of the note.
  
  Instead of the standard transaction UPS and transactions UPS01 to UPS04, you can use transaction /ISDFPS/UPS and transactions /ISDFPS/UPS01 to /ISDFPS/UPS04, which all support the additional, component-specific authorization checks.
Application Link Enabling

Application Link Enabling (ALE) can also be used to create and use distributed applications. ALE involves exchanging messages between SAP applications in a controlled manner while storing data consistently. Applications are integrated by means of synchronous and asynchronous communication rather than by a central database.

ALE comprises the following three layers:
- Application services
- Distribution services
- Communication services

Distribution Process

The distribution process involves three stages :

All the master data for the root force element and all lower-level force elements are determined using the FOX and written to the baseline. See also FOX Objects and Object Relationships .
- Explosion profiles DFPS_A and DFPS_E are used to determine the distribution scope.
- From a technical perspective, evaluation paths DFPS_PD1 to DFPS_PD3 are used for both explosion profiles for the structure explosion (customers do not need to change any Customizing settings).
The UPS creates and sends the related IDocs.

The corresponding UPS object types are available in Customizing under Logistics – General Product Data Replication Application Link Enabling (ALE) Uniform Packaging Service (UPS) Define Object Types .
The data is then posted in the target system in a sequence that makes sense from a business perspective.

For a list of the objects distributed using PDR and ALE , see Distributed Objects .

Note Note

Product Data Replication is also used in maintenance to distribute transaction data. See also Distribution of Transaction Data .

End of the note.

Special Handling of Individual Data

Certain scenarios require that certain data be distributed at least once, even if it no longer belongs to the root force element. Such data is therefore added to the distribution scope separately:

Customers/vendors

In stage two, Business Add-Ins (BAdIs) are used to add to the UPS package all the customers and vendors related to the plants that are relevant for the force elements determined.
Additional material master data and functional locations

For more information, see Addition of Objects to the Distribution Scope .
Filtering at plant level

To minimize the number of IDocs to be sent, you can use a filter in level 2 (UPS) for objects of type “material BOM”, “batch master record” (provided this is defined at plant level), and “MRP area”, which restricts which objects are distributed to which system at plant level. To specify the filter values, use the DFPS: UPS Plant Filter application (transaction /ISDFPS/UPS_WRK_MAIN). If no plant is specified for a system, the data is not filtered.

In contrast to standard ALE filters, consistency problems in UPS packages can be avoided by using this filter.
Maintenance orders and notifications for the equipment determined in stage one

Explosion profiles DFPS_PMORD and DFPS_PMNOT are used to trigger another FOX explosion in order to determine any additional objects that depend on the orders and notifications found.
Persons, positions, relationships

Persons and positions, as well as relationships to persons and positions are added by means of the ALE layer in stage two . From a technical perspective, evaluation paths DFPS_PD4 to DFPS_PD9 are used.
For information about distributing task organizations configured decentrally, see Decentralized Task Organization .
The following master data can be distributed during system setup initially by means of complete distribution (via transports):
- G/L accounts
- Activity types
- Cost elements
- Phrases (for dangerous goods master)
  
  This data does not need to be distributed in its entirety if the specified data exists in an adequate state in the template system and is subsequently copied to the decentralized system by means of a system copy.
  
  G/L accounts, activity types, and cost elements are also distributed at a later stage by means of change pointers.

While the data is being distributed, the process of initial user distribution is also triggered.

Delta Distribution of Master Data

Once the decentralized system has been provided with master data, you can schedule the FOX explosion and the distribution process using a batch job.

Adding and changing data are regarded as delta distribution processes. This ensures that changes to the organization are distributed to the decentralized system by means of delta distribution.

During the delta distribution process, the delta distribution of users is also triggered.

Distribution from the Decentralized to the Central System

The process of distributing data from the decentralized system to the central system is analogous to the process in the reverse direction. It uses the same standard mechanisms and the component-specific special conditions stated here also apply. You make the necessary Customizing settings in the relevant decentralized system.