Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WC00 (Package) IS-R: General customizing
IMG Activity
| ID | W_OE_EG_WL_0101 | Distribution Chain Control |
| Transaction Code | S_ALR_87005968 | IMG Activity: W_OE_EG_WL_0101 |
| Created on | 19981222 | |
| Customizing Attributes | W_OE_EG_WL_0101 | Distribution Chain Control |
| Customizing Activity | W_OE_EG_WL_0101 | Distribution Chain Control |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | W_OE_EG_WL_0101 |
In this step, you can maintain a reference plant for each distribution chain. Maintenance is only provided here for store distribution chains. (category: store distribution chain)
You can set the maintenance of the reference plants at client level in the section "General Control, Retail Master Data".
Within retail, you should be able to maintain data for a material on different organizational levels.
Subsequent maintenance transactions can then be carried out on an aggregated level.
The plants to be accessed by the specification of an aggregated level are defined by the membership of a plant to a plant category (distribution center/store) and to a distribution chain.
Changes on an aggregated level can of course only affect the subordinate plants if these have not been maintained differently.
For the listing, the inheritance of the change is then carried out independent of whether the material is listed in the corresponding plants or not (only the existence of the corresponding segment is decisive here).
The maintenance of logistics data on these levels is of course also possible for a material group reference material. However, in contrast to materials used in operations, only the data is physically stored on the correspondingly specified levels for the material group reference material; there is no new creation of individual records for each plant when you specify an aggregated level.
In order to do this, a plant must also be defined under which the respective data can be stored and which can also be specified again for later changes. To achieve this, you should be able to define so-called reference plants with the following validity:
- for all plants of a plant category (= store/distribution center) (In the section General control, Retail master data)
- for all plants of a plant category which belong to a certain distribution chain (only relevant to store distribution chains).
Data maintained differently is recognized on material/plant level.
These plants are not also changed when changing the data of a material on an aggregated level.
Requirements
Your system is configured as an SAP Retail System.
- The reference plant must belong to the respective plant category.
- You can only maintain reference plants for each distribution chain for retail distribution chains.
- A reference plant for a store distribution chain must always be a store of this distribution chain.
- The reference plants must always be different for different distribution chains since otherwise the user would always maintain the same data when entering different distribution chains.
- A reference material for a distribution chain must not correspond to the reference plant at client level (General control, retail master data)
Further notes
- A reference plant can only be changed if there is no alternative material data for the new reference plant (for any material).
The reference plant is accessed for this (if a record is found, the change is rejected). - A reference plant can then be defined later for a distribution chain or a plant category if there is no alternative material data for this reference plant.
- A reference plant cannot be deleted
The following rules apply to the maintenance of reference data in integrated material maintenance:
- Reference data can only be maintained for all distribution centers or all stores if reference plants are also defined on this level.
- Reference data can only be maintained for a distribution chain if a reference plant has been defined for the distribution chain.
- The organization levels on plant category level remain empty for the maintenance of the reference data.
- For the maintenance of reference data on distribution chain level, only the distribution chain is specified; the store field remains empty.
- For the maintenance of the data for a special plant, the plant is specified and all other organizational levels remain empty.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | W_OE_EG_WL_0101 | 0 | HLA0006434 | Logistics Basic Data |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TVKOV_W | V - View | SM30 | 0000000000 | Generated table maintenance: V_TVKOV_W |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
