Prerequisites for the Production Process

For this process you must fulfill the prerequisites described in the following section in SAP APO and SAP R/3. In addition, you must also have a SAP R/3 system with a suitable Plug-In.

Legacy Data

For performance reasons, the following prerequisites should be met before the first initial data transfer:

All manufacturing orders that are no longer relevant for planning should be technically completed.

All manufacturing orders that are no longer required should be archived.

Integration of Master Data/Integration Model

Master Data

The following master data must be transferred from SAP R/3 to SAP APO:

Material master of the header material

Material master of all components planned in SAP APO

Work centers

Bills of material (BOMs) and work centers

If you work with sources of supply for in-house production in SAP APO, you must carry out the following activities:

Create production versions in SAP R/3.

The source of supply for in-house production is generated from the production version.

Therefore in SAP R/3 you must:

Create a valid production version in the material master.

In the material master on the MRP 4 tab page, choose the setting Selection by Production Version (setting 2 or 3 ) for the selection of the BOM alternative. (See Create Production Version in SAP R/3 ).

This graphic is explained in the accompanying text.

If you change a production order (with source of supply for in-house production) in SAP APO and have not created a production version in SAP R/3 , the master data in the R/3 order is read again when the order is transferred from SAP APO to SAP R/3. The receive a message in the application log.

Errors may occur during the transfer. See SAP Note 328925 ‑ R/3 Order without BOM or Production Order .

Transfer BOMs and routings that are linked via a production version as the source of supply for in-house production to SAP APO.

Integration Model

In SAP R/3 you must have created an active integration model for movement and master data.

Order Reservations

To ensure that reservations for a manufacturing order are transferred to SAP APO, a material must be assigned to the reservation and the material/plant combination must be contained in an active integration model for materials.

This graphic is explained in the accompanying text.

So that reservations for a manufacturing order are reduced when a goods issue in SAP APO take place, the materials to which the reservation is assigned must be contained in an active integration model for manual reservations.

See SAP Note 421940 – No Reduction of Order Reservations in APO.

Co-Products and By-Products

Co-products and by-products are created in SAP APO as output products for the order. So that they are transferred to SAP APO with the manufacturing order, active integration models for manufacturing orders must exist for these materials.

For goods issues for the by-products there must also be an active integration model for manual reservations.

Order Operations and Phases

So that the operations and phases of a manufacturing order are transferred to SAP APO, the following prerequisites must be met:

A work center must be assigned to the operation or phase.

The work center must be contained in an active integration model for the target system.

A scheduling-relevant control key must be assigned to the operation.

The operation must not be a rework operation.

The operation must not have a duration of zero. This does apply to the operation segment setup which becomes a sequence-dependent setup activity in SAP APO.

If you are working without a production process model (PPM) or production data structure (PDS) or if you add operations manually, the following prerequisites must also be met:

The scheduling parameters must allow for the generation of capacity requirements.

The control key of the operation must allow for the generation of capacity requirements.

A scheduling formula and capacity formulas must be assigned to the work center.

Operations and Operation Dates

Operations

The following operations are transferred to SAP APO:

Operations with scheduling-relevant control key

Operations with valid scheduling formulas

Operations with work centers that are contained in an active integration model

Operations with a duration greater than zero

This graphic is explained in the accompanying text.

You can use the following enhancements to control that operations with a duration of zero are also transferred:

Enhancement CIFPPM01 - Core Interface for APO: Enhancements for PPM Model

Customer Exit EXIT_SAPLPGS1_002

Enhancement PPAPO003 - Production Order R/3->APO: Check if Operation is APO-Relev.

Customer Exit EXIT_SAPLCOVA_002

For more information about the Customer Exit EXIT_SAPLCOVA_002 see the SAP Notes 367658 – Filtering Out Operations from Orders in the CIF and 368968 ‑ Example source code for Note 368621 .

Operation Dates

The operation dates are determined using the following rules:

The operation dates are determined by SAP APO.

If an R/3 order with operations and components that are not relevant for APO is transferred to SAP APO, these are not copied to the APO order.

This graphic is explained in the accompanying text.

For more information about how the transfer of operations in production process models and production data structures depends upon the transfer of resources, see the SAP Notes 214597 - CIF-PPM: Maintenance of Master Data in R/3 and 367658 – Filtering Out Operations from Orders in the CIF .

After they have been transferred back to SAP R/3 from SAP APO, the operations that are integrated into SAP APO are assigned the status TMEX ( Scheduling in External System ).

SAP R/3 then determines the dates of the operations that are not APO-relevant (see SAP Note 354894 – Dates, Buffers and Goods Receipt Processing Time ) during midpoint scheduling.

This graphic is explained in the accompanying text.

SAP recommends that operations that are relevant for scheduling are transferred to SAP APO (that is, operations with a duration greater than zero and assigned components).

If you want the system to reconcile the receipt and requirement dates for components and items in SAP R/3 and SAP APO, see the SAP Note 354894 – Dates, Buffers and Goods Receipt Processing Time . In the scheduling parameters of the order type in SAP R/3 you should define automatic scheduling in order to adjust the dates of the operations that are not APO-relevant to those of the operations that are APO-relevant.

For more information about scheduling, see the SAP Note 684356 – Date Transfer Between R/3 and APO .

Goods Issue

To transfer goods issues – including those that are posted retroactively – to SAP APO, you must create an integration model for manual reservations for the relevant material/plant combination.

Strategy Profile for Integration

Choose the strategy profile in Customizing for Integration with SAP Components under Integration of SAP SCM and SAP R/3 → Basic Settings for Data Transfer → Maintain Strategy Profiles

For integration, you should choose a strategy with the following settings:

Scheduling Mode Infinite Scheduling

Validity Periods of Orders Do Not Consider

Planning Direction Backward + Reverse

This graphic is explained in the accompanying text.

You should avoid using optimizing strategies in the integration profile.

(See SAP Note 394113 – Date Shift Between R/3 and APO and 417461 – Scheduling Error When Transferring Orders to SAP APO ).

You should also see the following SAP Notes:

460107 – Fallback Strategy to Avoid Scheduling Errors

397989 – PP/DS Scheduling (Documentation) (This Note includes example scheduling results and documentation about PP/DS scheduling.)

For more information, see Define Detailed Scheduling Strategies .

Business Add-Ins (BAdIs) and Enhancements

See CIF Enhancements and BAdIs for In-House Production with Planned and Manufacturing Orders .