Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
VL (Package) WS-SHP: General Processing for Shipping
IMG Activity
| ID | SIMG_XXLEIDW2024 | Vendor Master |
| Transaction Code | S_ALR_87003607 | IMG Activity: SIMG_XXLEIDW2024 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_XXLEIDW2024 | Vendor master |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_XXLEIDW2024 |
For the replication of inbound deliveries in the decentralized system, it is not necessary that the vendor masters of the vendors specified in the inbound deliveries exist in this system. The inbound delivery can be generated in the decentralized system without the vendor master. Be aware, however, that you cannot fully perform all inbound delivery processing functions. For example, the count list for the inbound delivery or the partner definition in the inbound delivery are not completely set up and the conversion of stock from own stock to consignment stock cannot be initiated in the decentralized WMS. The missing vendor master does not mean that the inbound deliveries cannot be selected by vendor. However, you cannot use a vendor match code.
If the vendor master is to be distributed, the central ERP system is the leading system for maintaining this master record. In the ERP system, the vendor master is created and distributed to the decentralized WMS. For warehouse activities, you need the general vendor data. Whether you also need the purchasing organisation data depends on the use of the vendor master in the decentralized WMS.
The following basic rules apply:
Distribute only the necessary master data so that the WM system remains able to operate.
Be aware that you must manually maintain all necessary Customizing settings for the vendor master in the decentralized WMS.
For general information on master data distribution, refer to the ALE documentation Master Data Distribution.
Reduction for vendor master
To distribute not all vendor master data, reduce the standard IDoc CREMAS (see also: ALE documentation Create reduced message type for master data).
The reduced IDoc must contain the following segment:
- E1LFA1M - Segment for general vendor data
Within the individual segments, you can also carry out reductions at field level. To do this, deactivate the fields that you do not need.
Vendor master distribution
The vendor master distribution is carried out based on the reduced message type and controlled through the filter objects. The filters define the amount of data to be distributed. Set the filters appropriately so that only vendor master data relevant for the decentralized WMS is distributed, that is, the basic data and, if required, the data of the relevant purchasing organisation.
If you define a purchasing organisation as the filter, then only the segment of this purchasing organisation is distributed. All other segments independent of the purchasing organisation are passed on without being filtered. The master data can also be distributed using classes. In this case, only vendor masters of a specific class are distributed to the decentralized WMS (see also: ALE documentation Distribution Using Classes.) To maintain the required settings, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution -> Distribution Using Classes.
Address data distribution
The addresses are distributed through stand-alone IDos separately from the vendor master. If the address distribution is defined in the distribution model, the dependent addresses are automatically distributed with the vendor master. For more information on the distribution of addresses in connection with the customer/vendor master, refer to documentation Distribution model proposal: customer and vendor masters.
Example
Reduced IDoc CREMAS:
CREMAS02
|
---# E1LFA1M (*) Segment for general vendor data
|
|------E1LFA1A (+) Segment for general vendor data - extension
|------E1LFM1M (+) Segment for purchasing organisation data
All fields of the individual segments are activated.
Requirements
Standard settings
Recommendation
Activities
- Reduce the standard message type CREMAS for the distribution of the vendor master. To maintain the message type, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution -> Create reduced message type for master data.
- Perform all additional activities (such as activating the change pointer, setting the distribution using classes) for the new message type you have created. To do this, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution.
- So that the vendor master changes can be distributed, you must schedule a report that evaluates the change pointers and generates the IDocs. To schedule the report, go to ALE Customizing and choose Distribution (ALE) -> Scheduling Periodic Processing -> Scheduling IDoc Creation from Change Pointers.
- Check within ALE if further activities such as serialized distribution are still necessary.
- Maintain the distribution model for the new message type you have created. Maintain this message together with all other distribution objects when the distribution model is generated. If the address data is also to be distributed, activate distribution model generation for the address data as well.
Further notes
Business Attributes
| ASAP Roadmap ID | 255 | Create Interfaces |
| 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 | SIMG_XXLEIDW2024 | 0 | ALR0000093 | Central Processing |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
