Performing Master Data Distribution

Objective

After completing this lesson, you will be able to understand master data distribution with ALE.

Distribute Master Data with ALE

Using the Product Structure Browser, you realized, which data is missing in your target system. Therefore you have to transfer these data from your Engineering to your Production System.

The question is now, how to transfer these data. Some of them need to be transferred immediately, some later.

The following video explains different transfer scenarios for a material. These scenarios also work for other master data.

Distribute Documents with ALE

Simple Distribution of Documents

You have created documents in your engineering system alongside materials and bill of materials. These documents therefore have object links to the materials, are maybe classified, and own originals stored in a secure area.

When distributing these documents, you must pay special attention to the object links and the stored originals.

The document information is then transferred from the source system to the target system using an IDOC (Intermediate Document). The IDOC contain the document and object link information and not the connected object. Therefore you have to distribute the attached objects separately.

Alternative: you use the Product Data Replication, which will be explained later.

Cross-System Access I

When distributing document info records, it is also important to take care on the originals, stored inside a secure storage area.

The first solution could be, that only one secure storage area is used, even inside a distributed system scenario. When this is the case, an identical storage location must be accessible in both systems.

Only the document and location information is distributed between the systems.

If an original needs to be displayed in the target system now, it will be provided from a central content server. In this scenario, there is no caching or original transfer.

Cross-System Access II

As an alternative a multi-level content / cache server scenario could be possible. In this case you are able to define main content servers with connected cache servers. This scenario makes sense, when the SAP systems are distributed around the world and an access to attached document files have to be guaranteed around the clock. The files are then stored in the next available content / cache server to the user.

Distribution of Storage Locations

HTTP Content Servers can be placed close to users. Storage locations are assigned to the users' workplaces and the positions of these storage locations. To speed up check-in, a suitable category based on the user's location is automatically determined for the document. These settings are configured in the SAP system. The potential disadvantages of spatial distribution during reading can be mitigated by caching.

Caching

Depending on the user's workplace (location), read access is made via a special cache server located nearby. If the document is not already in the cache, the cache server retrieves it from the SAP content server. The cache server, similar to the SAP content server, uses a database repository and is accessed via URLs.

Reasons for Caching:

  1. Provides fast network access without slowing down the network.
  2. Caching is not replication; the original remains on the content server.
  3. Cache content can be replenished from the content server at any time, copying only the required documents.

How to distribute Master Data with ALE

Introduction

After the production systems have been connected to the engineering system, the new master data is now created first in the engineering system. These are, for example, documents or materials.

If this master data has reached a certain processing status, for example, the documents have been released, or the materials reach a certain status, these data are distributed from the engineering to the production system.

This can be done with a direct distribution or using a batch job.

Task 1: Work with the Product Browser

However, before any distribution takes place, the data in the source system should be compared with that of the target system. It must be clarified which data have to be transferred and which not, as these data are available inside target system.

Doing so Master Data Specialist Andrea uses the product structure browser, to get an overview of available master data inside engineering and production system.

The following video now shows how Andrea uses the product structure browser with a cross system access.

Task 2: Distribute a Material

Master Data Specialist Andrea has determined that a material exists only in the engineering system. Therefore Andrea decides to distribute the material.

This distribution process is shown in the following video.

Task 3: Check the material inside target system

After Andrea has executed the distribution, she wants to check the data inside production system.

The following video shows how Andrea controls the material inside target system.

Task 4: Distribute a Document

The material was created in the source system along with a document. Now Andrea has the task of distributing this document as well.

The following video shows first a final check of the document inside source system and then the document distribution.

Task 5: Check the document inside target system

The document is now available inside production system.

Master Data Specialist Andrea controls the distribution and the document itself in the target system.

The following video shows the relevant object checks.

Log in to track your progress & complete quizzes