Ansicht
Dokumentation
Transportation and Shipment Scheduling Dependent on SNP Master Data ( RELNAPO_401_ATP_VSTPTERM )
CL_GUI_FRONTEND_SERVICES - Frontend Services General Data in Customer MasterThis documentation is copyright by SAP AG.
Short text
Transportation and Shipment Scheduling Dependent on SNP Master Data
Use
As of SAP APO 4.0, you can choose if Transportation and Shipment Scheduling is executed depending on SNP master data or on condition data. Until now, condition data was always used in scheduling.
This is of particular relevance for vendor-managed inventory (VMI) sales orders, because the system uses the SNP master data for scheduling when VMI orders are created. When the order is changed and published to SAP R/3, Transportation and Shipment Scheduling, which calculated other dates depending on condition data until now, is called up. If you activate Extended Scheduling for VMI Sales Orders in SAP APO 4.0, and the destination location is a VMI customer, and the location-dependent product master data exists, Transportation and Shipment Scheduling now also determines the dates depending on the SNP master data.
If you do not activate Extended Scheduling for VMI Sales Orders or the destination location is not a VMI customer or no location-dependent product master data exists, the system does not determine the dates depending on the SNP master data, but on the condition data.
In Global Available-to-Promise (Global ATP) and SAP R/3 documents, you can also schedule depending on SNP master data.
Effects on Existing Data
If you change over the scheduling of SAP R/3 documents to SNP master data, documents created before this change are rescheduled according to the new logic if data that is relevant for scheduling is changed.
Effects on Data Transfer
Effects on System Administration
If you use the customer exit /SAPAPO/SAPLVCRM_001 or /SAPAPO/SAPLVCRM_002, you may have to adjust the implementation.
Effects on Customizing
- If you want to schedule VMI sales orders in SAP APO, you activate the extended scheduling in the implementation guide (IMG) under Advanced Planning and Optimization -> Supply Chain Planning -> Supply Network Planning (SNP) -> Vendor-Managed Inventory -> Activate Extended Scheduling.
- If you create VMI sales orders in SAP APO and transfer them to SAP R/3, in Customizing you have to assign the shipping condition of the relevant SAP R/3 document to the means of transport with which the VMI order was created in SAP APO. To do so, in the SAP APO implementation guide choose Global Available-to-Promise (Global ATP) -> Transportation and Shipment Scheduling -> Interfaces -> Define Assignment of Default Means of Transport to Shipping Conditions.
- If you also want to schedule SAP R/3 documents depending on SNP master data, the following prerequisites must be fulfilled:
- Extended Scheduling is activated (see above)
- The location of the ship-to party is defined as a VMI customer
- Location-dependent master data exists for the material/plant combination
- An active integration model exists for the related material/plant combination of the document for Global ATP or an active integration model exists for the related material/plant/ship-to party combination for VMI scheduling (the prerequisite for this is SAP R/3 4.6B or higher)
Further Information
Release information for Vendor-Managed Inventory
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 4304 Date: 20240425 Time: 103303 sap01-206 ( 76 ms )
