Ansicht
Dokumentation
ALE - Distribution of master data via lists: Changes to Customizing ( RELNALE_30D_ALET_LISTING )
General Data in Customer Master CL_GUI_FRONTEND_SERVICES - Frontend ServicesThis documentation is copyright by SAP AG.
Short text
ALE - Distribution of master data via lists: Changes to Customizing
Description
In Release 3.0D there is change in the way that master data is distributed via lists. It is now not only possible to allocate lists to materials, customers and vendors but also to specify explicitly the message type for which this list is to be used.
This change can be explained best with the help of an example. We will assume that the raw materials raw01, raw05 and raw08 and the finished products fin02, fin05 and fin11 are to be distributed to the LOGISTIC system. The raw materials are to be distributed using the MATPUR message type, which has been derived from the SAP message type MATMAS and contains purchasing data only. Similarly, the finished products are to be distributed using the MATSAL message type, which contains sales data only. The distribution is to be controlled with the help of two lists: DIST_PUR, which contains the raw materials raw01, raw05 and raw08, and DIST_SAL, which contains the finished products fin02, fin05 and fin11.
Previously (up to Release 3.0C) it was only possible to specify in Customizing that all the materials from the lists DIST_PUR and DIST_SAL were to be distributed to the LOGISTIC system. It was not possible to specify the message types explicitly. In this example, when changes to the MATPUR message type, that is purchasing data, were sent, then a change to the sales material fin05 would have been sent also.
This has now been changed in Release 3.0D. It is now possible to specify explicitly that the DIST_PUR list is to be used for the MATPUR message type and the DIST_SAL list for the MATSAL message type.
The settings maintained up to Release 3.0C for list distribution are converted via the RBDXBDLT XPRA when the Release 3.0D Put is done. If the settings in this area are not changed after the Put, then the system will continue to work in the same way as before.
Damage caused to data by errors
Software/hardware requirements
Installation information
Effects on System Administration
Effects on Customizing
Effect on batch input
Changes to the Interface
Changes in procedure
Procedure for removing dataset errors
Dependent functions
Planning
Further notes
BAL_S_LOG - Application Log: Log header data Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 2673 Date: 20240418 Time: 013337 sap01-206 ( 65 ms )