Ansicht
Dokumentation
Integration of Planned Orders (Enhanced) ( RELNAPO_401_INT_SNP-PLAN )
PERFORM Short Reference Vendor Master (General Section)This documentation is copyright by SAP AG.
Short text
Integration of Planned Orders (Enhanced)
Use
Planned orders generated in SAP APO can either be assigned to Supply Network Planning (SNP) or Production Planning and Detailed Scheduling (PP/DS). Previously, planned orders that were created in SAP R/3 and transferred to SAP APO were always mapped as PP/DS planned orders in SAP APO.
Initial data transfer with creation of SNP planned orders in SAP APO
As of SAP APO 4.0 and SAP R/3 Plug-In 2003.1, a planned order generated in SAP R/3 and transferred to SAP APO can be mapped as an SNP planned order also. This applies to planned orders that meet the following criteria:
- The planned order does not yet exist in SAP APO.
- MRP procedure X (without material requirements planning, with BOM explosion) is assigned to the header material of the planned order in SAP R/3.
- The availability date of the header material is outside of the SNP production horizon.
- It is neither a planned order of type "forecast" nor a planned order for project stock or sales order stock.
- The SNP production horizon or extended SNP production horizon has been maintained in the SNP 2 tab page of the product master (transaction /SAPAPO/MAT1).
If the planned orders created in R/3 meet the aforementioned criteria and you want the orders to be mapped as SNP planned orders in SAP APO, you have to set indicator Create planned orders as SNP planned ordersin SAP R/3 when you activate the relevant integration model for planned orders (transaction CFM2). Activating the integration model triggers the initial data transfer of planned orders. If the availability date of the header material is within the SNP production horizon, SAP APO creates a PP/DS planned order, as was previously the case.
Stopping change transfer for SNP planned orders in SAP APO inbound
In an integrated system infrastructure, critical components are usually planned in SNP and the results are published to SAP R/3 at regular intervals. However, non-critical components are often planned in SAP R/3 using material requirements planning (MRP). It is possible for planned orders whose components are planned in both SAP R/3 and SAP APO to be changed in SAP R/3 using BOM explosions or lead time scheduling, even if their header material is assigned with MRP procedure X, which does not really allow for changes to be made. These changes are transferred to SAP APO during change transfer and can cause inconsistencies between SAP R/3 and SAP APO.
As of SAP APO 4.0 and SAP R/3-Plug-In 2003.1, you can set in SNP Customizing that SAP APO will permit transfer from SAP R/3 only for planned orders in the SNP production horizon. To do this, follow this menu path: Basic Settings -> Maintain Global SNP Settings -> Planned Order Integ. As a result, SAP APO does not adopt any changes to SNP planned orders from SAP R/3.
The option: Allow transfer from SAP R/3 for all planned orders is set by default. Planned orders are not filtered out in SAP APO inbound. SAP APO updates all planned orders and planned order changes that are sent from SAP R/3.
If you set the Only allow transfer for planned orders in SNP productn hor. option, all planned orders that meet the prerequisites listed below are filtered out in SAP inbound and are therefore are not updated:
- In SAP R/3, the header material of the planned order is assigned with MRP procedure X (without material requirements planning, with BOM explosion).
- The availability date of the header material is outside of the SNP production horizon.
- The SNP production horizon or extended SNP production horizon has been maintained in the SNP 2 tab page of the product master (transaction /SAPAPO/MAT1).
However, the following transfers are still updated:
- Initial data transfers of planned orders
- Changes to planned orders that are triggered by the Compare/Reconcile Function
- PP/DS planned orders
- New orders created in SAP R/3 (these are automatically created as PP/DS planned orders)
- Planned order deletions
Initial data transfer only for PP/DS planned orders
As of SAP APO 4.0, it is possible to supply PP/DS with current data from SAP R/3 without the SNP results overwriting the data from SAP R/3. For this to be possible, the following prerequisites have to be met:
- In SAP APO, you have to have set the following in SNP Customizing (as described above): Only allow transfer for planned orders in SNP productn hor.
- The Create planned orders as SNP planned orders indicator must notbe set in SAP R/3 when activating the integration model.
During activation of the integration model for planned orders, planned orders that meet the following prerequisites are filtered out in SAP APO inbound and are therefore not updated:
- In SAP R/3, the header material of the planned order is MRP procedure X (without material requirements planning, with BOM explosion).
- The availability date of the header material is outside of the SNP production horizon or the planned order is an SNP planned order.
- The SNP production horizon or extended SNP production horizon has been maintained in the SNP 2 tab page of the product master (transaction /SAPAPO/MAT1).
An initial data transfer is therefore only carried out for PP/DS planned orders.
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Effects on Customizing
There is an extra setting in SNP Customizing for controlling the initial data transfer and change transfer of planned orders from SAP R/3. This setting is called Planned Order Integration and can be found by following this SNP Customizing path: Basic Settings -> Maintain Global SNP Settings -> Plnnd Ord.Integratn. For more information, see Control for Transferring Planned Orders from SAP R/3.
Further Information
Period Category for the SNP Production Horizon
BAL Application Log Documentation General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 7307 Date: 20240420 Time: 181725 sap01-206 ( 117 ms )
