Ansicht
Dokumentation

RBDSESRCP - Site Recipe Distribution

Addresses (Business Address Services)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Title

Sending Site Recipes

Purpose

This report is used to distribute site recipes.

You can use this report to process the following scenarios for distributing site recipes.

,,- Distributing one or more new site recipes to one or more target systems

,,- Distributing one or more existing site recipes to one or more target systems

,,- Evaluating change pointers and, depending on the result, creating, changing, or deleting site recipes in one or more target systems

Integration

Prerequisites

Prerequisites for distributing site recipes:

,,- The Customizing settings in the source and target systems must be identical

,,- The distribution model must be maintained in the source and target systems (ALE scenario)

,,- For distribution via change pointer, the change pointer must be activated for the message type PPE_SREC and the change pointers in general must be activated

,,- The change-relevant fields for the message type PPE_SREC must be maintained

,,- The partner profiles must be maintained for the message type PPE_SREC with the basic IDoc type PPE_SREC01

Features

Selection

You can control the individual processing runs with the selection parameters.

- Site Recipe

The user can use these selection fields to specify which site recipe(s) is/are to be used for distribution.

- Replicate

This parameter causes all the site recipes found with the "Site recipe" selection fields to be read from the source system. They are then distributed to one or more target systems. If they do not already exist in the target system, they are created. Otherwise, they are changed.

- First Initialization

This parameter causes all the site recipes found with the "Site recipe" selection fields to be read from the source system. They are then distributed to one or more target systems. The site recipes are created in the target system. In doing so, the system performs a check, since the site recipe must not already exist in the target system.

- Reporting for Change Pointers

This parameter causes the change pointers that refer to the site recipes to be evaluated. If the change pointers are active, all changes to site recipes are recorded. The affected recipes and activities (create, change, delete) are transferred to the target system. The entries in the "Site Recipe" selection fields are ignored in this case.

- Changed On

If the "Reporting for Change Pointers" parameter is activated, all the change pointers that were created up to the entered "Changed on" date are evaluated.

- Time

If the "Reporting for Change Pointers" parameter is activated, all the change pointers that were created up to the entered "Time" are evaluated.

- Logical System

The "logical system" identifies the target system. If you specify a logical system, the recipes are distributed to this system if all the necessary settings (partner profile, ...) have been defined. If you do not specify a logical system, all the systems that are intended for distribution are determined.

Standard Variants

Output

Once the site recipes have been sent, the system outputs a list of recipes that were processed.

You can check the processing status of each recipe by displaying the log. Since processing is carried out asynchronously, you can only check the processing status up to the point the outbound IDoc was created in the source system.

All of the messages that occurred are also stored in the application log and can be displayed via the PVS object.

Activities

Site recipe distribution does not include the distribution of documents, change statuses, characteristics, classes, or classifications. These objects have to be processed using separate distribution scenarios.

,,- Change statuses must be distributed, before the site recipes. Only change statuses that are assigned to an external number rangecan be distributed.

,,- Documents must be distributed before the site recipes.

,,- Characteristics that do not exist in the target system must be distributed before site recipes.

,,- If the class does not yet exist in the target system, it must be distributed before the site recipes.

,,- The classification must be distributed after the site recipes.

Example

Vendor Master (General Section)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4764 Date: 20240601 Time: 114758     sap01-206 ( 80 ms )