Functionality
In ALE outbound of ALE distribution
of product catalogs, this module triggers the sending of basic andstructure data (i.e. layout areas and layout hierarchies) of a productcatalog to specific receiving systems.
You can use the parameter "RequestChanges" to control whether thespecified data is sent "directly" (i.e. in full) or on the basis ofchange pointers. If change pointers are used, the data is ony sent ifit has been changed before the date entered in "CreationDateTo".
The possible receiving systems and the scope of data to be replicatedare determined on the basis of the entries entered in the ALEdistribution model for BAPI "ProductCatalog.SaveHeadReplica". However,you can also use parameters "VariantIds" and "Recipients" to makefurther restrictions in addition to those in the distribution model.
You can use parameter "MaxAreas" to define the number of IDocs overwhich the data (more precisely the layout areas) are split. If youexpect errors to occur during inbound processing, it may be advisableto enter as many IDocs as possible, to make error handling and theposting of data easier.
Information relating to the objects actually distributed (catalogs,reference customers, materials, layout areas and IDocs) are returned inthe parameters "ReplicatedCatalogIds", "ReplicatedCustomerIds","ReplicatedMaterialIds", "ReplicatedAreaKeys" and"CommunicationDocuments".
All messages are returned in parameter "Return".

Example

Notes
For the data to be created and changed, you need authorization foractivity "Create IDocs" for the catalog in question for authorizationobject "W_PCAT_MTN".
A separate IDoc segment "ExtensionIn" and function exit"Exit_Saplwpca_001" of SAP enhancement "Wpca001" are available forcustomer enhancements.
"ProductCatalog.ReplicateItems" is a method available for the item dataof a product catalog.

Further information

Description
You can use the parameter "CatalogID" to send the number of the catalogto be replicated to the BAPI. If this field is blank, the data of allcatalogs (according to the conditions in the distribution model) issent. Data cannot be sent if the distribution model does not allowthis.
For further information, see ther data elementdocumenation.

Description
If the parameter "RequestChanges" is selected, all non-processed changepointers for product catalogs up to the date in the parameter"CreationDateTo" are analyzed. All changes to catalogs made up to thisdate are sent to the recipient(s). If "RequestChanges" is blank, theparameter is ignored.

<(>&<)>MEANING<(>&<)>
The maximum number of layout areas distributed together in one IDoc canbe specified in parameter MAXAREAS. A maximum of 999 layout areas arepossible per IDoc. A default value of 500 is displayed.

Description
This parameter is used to transfer to the receiving systemmodifications to catalog data that has already been replicated.
This parameter can contain the following values:

• 'X'

This value indicates that only modified (according to change pointers)product catalog data is replicated. In this, all change pointers thathave not been modified up to the "CreationDateTo" date are analyzed. Aprerequisite for this is that the change pointers for message typePCHEAD are activated in Customizing for distribution (ALE).

• ' ' (no value)

"No value" is the standard setting and indicates that all productcatalog data is replicated, regardless of change pointers.

Note
This parameter should not be used if explicit recipients have beenentered in the "Recipients" parameters, as the change pointers for allrecipients are then reset and further recipients may no longer be takeninto consideration.

Description
If this indicator is selected, the change pointers to be selected arenot set to complete. This means they are available for a repeatexecution. As a result, the function can be tested.

Description
If IDocs are created, their keys are returned in table"CommunicationDocuments".

Description
The possible receiving systems are determined via the ALE distributionmodel. You can use the parameter "Recipients" to restrict the number ofreceiving systems. If the parameter "Recipients" is blank, the productcatalog data is sent to all allowed recipients (allowed recipients arethose entered in the distribution model for BAPI"ProductCatalog.SaveHeadReplica"). Once the module is ended, allreceiving systems to which IDocs were sent are returned in this tableparameter.

Note
Distribution using change pointers is not possible if recipients areexplicitly entered, as in this case, the change pointers for theserecipients are reset, and further recipients may no longer be takeninto consideration.

Description
The keys of the distributed layout areas are returned in table"ReplicatedAreaKeys".

Description
The numbers of the distributed catalogs are returned in table"ReplicatedCatalogIds".

Description
The numbers of the reference customers that are used in the distributedcatalogs are returned in table "ReplicatedCatalogIds".

Description
The numbers of the materials that are used in the variants of thedistributed catalogs are returned in table "ReplicatedMaterialIds".

Description
This structure is used to return the return code to the callingprogram.
For information on the significane of the individual fields in thestructure, see the relevant data element documentation on theindividual fields.

Value range
Type,,ID ,, Number
E,, B1 ,, 004
E,, W+ ,, 401
E,, W+ ,, 402
E,, W+ ,, 424
E,, W+ ,, 425
I,, W+ ,, 426
I,, W+ ,, 427
I,, W+ ,, 428
E,, W+ ,, 500

Description
If you entered a catalog for the parameter "CatalogId", you can use theoptional table parameter "VariantIds" to restrict the variants of thiscatalog that are to be copied rather than use the variants to be copiedaccording to the distribution model. All texts (e.g. texts for layoutareas) are only distributed in the languages of the selected variants.

Notes
If no catalog number was entered, this paramter must not be filled.