Which dates does SAP APO transfer to the ERP system?

Since SAP APO does not use buffer times, only the start and end dates are transferred to the ERP system. The dates scheduled by SAP APO correspond to basic dates in the ERP system. Production dates can only be filled by the ERP system.

There are two different cases:

Which dates does SAP APO adopt from the ERP system?

Depending on the scheduling type specified in the strategy profile (forward or backward scheduling), SAP APO adopts either the basic start or basic end dates from the ERP system, and then schedules the missing basic date on the basis of the PPM. If lead-time scheduling takes place in the ERP system, SAP APO adopts the production start and end dates. However, if lead-time scheduling does not take place in the ERP system, SAP APO adopts only the basic start and end dates.

Which dates does SNP transfer to PP/DS?

SNP transfers the start and end dates to PP/DS, which then reschedules the planned order.

Is the goods receipt processing time taken into account in SNP?

In SNP, the goods receipt processing time is currently only taken into account by the heuristic, not by the optimizer. The prerequisites for this are SAP Notes 424063 and 491469.

How are the changes to a planned order that has already been planned (for example, release of a planned order in the ERP system or adding an operation) taken into account in SAP APO?

SAP APO retains the activity dates of an order that has already been planned in SAP APO as a default, even if this order is again transferred from the ERP system via initial or change transfer, using the CIF compare/reconcile function, or as part of cross-system update logic. In this way, SAP APO avoids unnecessary rescheduling and the original planning situation is retained. This system behavior is valid for the activities Set Up, Process, and Tear Down and for the receipts or requirements that are assigned to these activities.

Dates for the sequence-dependent set-up activities and dates for activities during the goods receipt processing time and the assigned header materials are not retained.

The activity dates are also not retained in the following cases:

If you do not want the planned activity dates to be retained in SAP APO, you can deactivate this setting by using the method ORDER_INB_PROCESSING_DECIDE of the Business Add-In (BAdI) /SAPAPO/CL_EX_CIF_IP. You can also use the method ORDER_INB_REDET_DATES_DECIDE of the same BAdI to deactivate the retention of the activity dates for individual orders.

How are changes to the total quantity of a planned order that has already been planned in the ERP system taken into account in SAP APO?

SAP APO retains the data of the existing order and adopts the quantity changes sent from the ERP system. The system adjusts the requirement and receipt quantities in proportion to the change to the total quantity. Confirmed quantities are not adjusted proportionally. If a quantity-dependent formula for the duration is entered in the Process operation segment of an ERP order, SAP APO adjusts the duration of the activity Produce proportionally.

After a proportional quantity adjustment, SAP APO always reschedules the order. When you work with characteristics-dependent planning, the quantity adjustment in SAP APO is not carried out proportionally; instead the production process model (PPM) is exploded again. If you do not want the system to carry out a proportional quantity adjustment, you can deactivate this setting by using the method ORDER_INB_PROCESSING_DECIDE of the Business Add-In (BAdI) /SAPAPO/CL_EX_CIF_IP.

If you simultaneously change both the total quantity of a planned order or manufacturing order in the ERP system as well as the production version, and these changes are transferred to SAP APO, the PPM is exploded again.

Are components and operations that are added or changed in the ERP system taken into account in the SNP planned order?

No. The SNP planned order only takes into account components and operations from the SNP PPM explosion.

How is assembly scrap integrated?

The PP/DS planned order transfers the yield and scrap quantity to the ERP planned order. In SNP, assembly scrap is currently only supported by the heuristic, not by the optimizer.

Scrap quantity, yield, and total quantity are interpreted in the same was as in PP/DS. The prerequisite for this is SAP Note 458684. For more information about the integration of assembly scrap, see Integration of Routings.

Are capacities integrated?

No. When planned orders are transferred, no capacity requirements are copied from the ERP system. SAP APO determines its own capacity requirements on the basis of the operations in the PPM. There is no reconciliation with the ERP system.

How are

integrated?

See Integration of Bills of Material.

How is the availability check integrated?

The availability check (ATP check) for components in the planned order can be carried out in the ERP system and in SAP APO.