Ansicht
Dokumentation
Retention of the Activity Dates Planned in SAP APO (New) ( RELNAPO_401_INT_FIXACT )
rdisp/max_wprun_time - Maximum work process run time General Material DataThis documentation is copyright by SAP AG.
Short text
Retention of the Activity Dates Planned in SAP APO (New)
Use
If you change a planned or production order in SAP R/3 that has already been planned in SAP APO (through a release or the addition of operations, for example) and you transfer this change to SAP APO, SAP APO previously rescheduled the activities for this order automatically. This could result in the entire planning situation in SAP APO being changed.
As of SAP APO 4.0 and SAP R/3 Plug-In 2003.1, SAP APO retains the activity dates for an order that was already planned in SAP APO as standard, whether this order was transferred using an initial or change transfer, through the CIF compare/reconcile function, or retransferred as part of cross system update logic. As a result, SAP APO prevents undesired rescheduling and the original planning situation is retained.
This new system behavior applies for setup, processing, and teardown activities, as well as for receipts and requirements that are assigned to these activities.
Dates for sequence-dependent setup activities are not included, nor are dates for activities for the goods receipt processing time or assigned header materials.
Activity dates are also not retained in the following situations:
- Change of order quantity in SAP R/3
- Change of characteristics in SAP R/3
- Re-explosion of master data in SAP APO and SAP R/3
- Change to production version in SAP R/3 or a change to the production process model in SAP APO
- Confirmation of operations/manufacturing orders in SAP R/3
If you do not want to use the retention of activity dates planned in SAP APO, you can deactivate this using method ORDER_INB_PROCESSING_DECIDE of business add-in (BAdI) /SAPAPO/CL_EX_CIF_IP. You can also use method ORDER_INB_REDET_DATES_DECIDE of the same BAdI to deactivate the retention of activity dates for individual orders.
Effects on Existing Data
Effects on Data Transfer
Effects on System Administration
Effects on Customizing
Further Information
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up ROGBILLS - Synchronize billing plans
This documentation is copyright by SAP AG.
Length: 2460 Date: 20240416 Time: 173446 sap01-206 ( 50 ms )
