Ansicht
Dokumentation

RWPCHEADSMD - Prepare Product Catalog IDocs for Changes

BAL Application Log Documentation   General Material Data  
This documentation is copyright by SAP AG.

Purpose

In Application Link Enabling you use this program to distribute changes to basic and structure data (i.e. layout areas and layout hierarchies) of product catalogs by sending the data via change pointers to other systems.

Features

Message type "PCHEAD", displayed in the field Catalog message type should generally be used to distribued basic and structure data of product catalogs (however, see also Note below).

Selection

In the Final date for change pointers, you can enter the date up to which change pointers are to be evaluated. The change pointers are not reset if the Do not evaluate change poiners is selected. The indicatr is usually only selected for the purposes of testing an ALE connection.

If you only select on catalog, you can select the relevant fields from the variants of this catalog that are to be sent. In this case, texts are only distributed in the selected variant languages, ad prices are only distribued in the variant currencies.

In the field Max. layout areas / IDoc, you can enter the maximum number of layut areas that can be sent together in one IDoc. If you expect a lot of errors to occur in the receiving system when IDocs are posted, you should keep this value as low as possible, to make it easier to find these errors. However, if few/no errors are expected, the value should be as high as possible, to obtain best possible performance during transfer.

If you enter a server group in the relevant field, the selected data is sent to the application server of this server group. If the data of several product catalogs is distribued, a separate process is started on the application server for each individual process.

Prerequisites

Catalog data can only be distributed by ALE to network systems for which the necessary settings have been made in Customizing for distribution (ALE).

In particular, the BAPIs ProductCatalog.SaveHeadReplica and ProductCatalog.SaveItemsReplica must be assigned to the systems in the Distribution model (under Model and implement business processes > Maintain distribution model)

ALE distribution of product catalog also requires that the catalog layouts to be distributed have the same layout number for all the systems in a network. In addition, layout numbers of catalogs from various systems that are to be replicated via ALE in the same receiving system cannot be the same, and catalogs created online in the receiving system cannot have the same number as layouts sent via ALE, as if they do, data may be overwritten.

Therefore, in the receiving system, reserve separate layout number ranges for all original systems from which catalog data is to be replicated via ALE.

The necessary steps can be found in Customizing for the product catalog under Assign number ranges to layout in ALE inbound.

Note

In addition to message type PCHEAD (from Release 4.6A), message type PRDCAT (and those referencing it as of Release 4.0A) is available for distributing basic and structure data of product catalogs. PRDCAT should only be used if this is unavoidable for reasons of compatibility, as it will not be taken into consideration in future developments, and all above-mentioned selection options, as well as integrated transfer (with the exception of document IDocs) are not available for this message type.

Vendor Master (General Section)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4188 Date: 20240601 Time: 093009     sap01-206 ( 92 ms )