Show TOC

 Merge APO and R/3 Data

Use

When an APO planned order is converted into an R/3 production order, certain APO and R/3 data is merged. During this merge, certain information from the APO planned order is copied to the production order.

When the data has been merged, the production order has been saved and, if necessary, the R/3 planned order has been deleted, the R/3 order number is returned.

Features

The header, item and operation data from the R/3 production order and the APO planned order is merged.

Order Header

The following information is copied from the order header of the APO planned order to the R/3 production order.

  • Total order quantity

  • Order scrap quantity

  • Start and end date and start and end time of the order

    This data is only copied over as a suggestion Depending on the settings of the scheduling parameters, dates are then calculated again in the subsequent midpoint scheduling.

  • Production version

  • Explosion date

  • Configuration

  • Order priority

  • ATP status (only if you use the corresponding enhancement)

    See SAP Note 439703 – Transfer of ATP Status to Manufacturing Orders from APO.

Order Items
Primary product/header material

At item level, the following information relating to the primary product is copied from the APO planned order to the R/3 production order.

  • Account assignment (on order creation only)

  • The quantity confirmed by the ATP check

  • ATP overall confirmation date

  • Quantities

Co-product/by-product

At item level, the following information is copied from the APO planned order to the production order.

  • Quantity

  • Material

  • Plant

  • The quantity confirmed by the ATP check

  • Storage Location

    The storage location is only transferred from SAP APO if you work with container resources or MRP areas. Otherwise it is determined using R/3 storage location determination. (See SAP Note 488270 – Incorrect Storage Locations in R/3 ).

  • Configuration

  • Special stock indicator

  • Account assignment

Background documentation 

It is only possible to add input and output products in SAP APO as of SAP APO 3.1.

If output productsare added to the planned order in SAP APO the system copy these to the production order as a by-product or co-product.

The output product is copied as a co-product if the material is defined as a co-product in the material master and a distribution rule exists for the primary product.

Otherwise, the output product is copied as a by-product .

Components

At component level, the following information is copied from the APO planned order to the production order.

  • Material

  • Plant

  • ATP confirmed quantity

  • Operation assignment

  • Storage Location

    The storage location is only transferred from SAP APO if you work with container resources or MRP areas. Otherwise it is determined using R/3 storage location determination.

  • Missing part (status that indicates missing material availability)

  • Configuration and batch data (only in certain processes)

  • Special procurement key

  • Account assignment (to sales order) or WBS element

Operations/Phases

The following information is copied from the APO planned order to the manufacturing order at operation level (or phase level for the process order):

  • Start and end date (for the production order dates are given for the operation segments setup, process, tear down)

  • Work center (resource)

  • Status scheduled/deallocated

    Caution Caution

    No data merge takes place at suboperation level. Therefore, a change of resource in SAP APO at suboperation level is not copied to the manufacturing order in SAP R/3.

    End of the caution.

After the data has been merged, the operations or phase are assigned the status TMEX ( Dates are set by external system ). This status ensures that R/3 scheduling does not reschedule this operation. The status is reset if, for example, a quantity change takes place (in SAP APO or SAP R/3).

When does a status change take place?

Action

Details

Status TMEX is retained

Status TMEX deleted

Deallocate operations

X

Change header quantities

X

Read master data

X

Change operation data

Quantity

X

Only if scrap is entered, otherwise no change possible

Standard values

X

Control key

X

Change of work center

X

Add operation

X

Delete operation

X

Change sequence

When a sequence change take place the statuses of the changed operations are retained.

X

Status retained at predecessor and successor

Lock order

X

Status reset

Technical completion

X

Deletion flag

X

Lock

TMEX set again from SAP APO

Quantity propagation

on confirmation

Operation confirmation with scrap

X

Partial operation confirmation with scrap

X