Confirmation 

Use

The confirmation is used for the order monitoring. It documents the status of production orders and operations in the production cycle.

You can carry out the order monitoring for AFS materials at SKU level. That means, for example, that you can confirm the number of SKUs for an operation. With AFS you can track per order or per operation how far the production of SKUs for an AFS material has progressed (see Confirmations).

Features

You confirm AFS materials in the SAP standard application. You can carry out the confirmation for a production order (CO15) or for an operation (CO11 or CO11N).

·         For an order confirmation (CO15), all SKUs for a production order are processed in the same step. You cannot display the planned AFS data. The system proposes the yield to be confirmed; the yield also contains the scrap quantity and cannot be changed. The quantity is always a default value, regardless of the setting you make for the confirmation parameters (transaction OPK4) in Customizing. You still cannot enter a partial confirmation.

·         For an operation confirmation (CO11, CO11N), you can either confirm all SKUs for an operation in one step, or confirm one SKU or a bundle of SKUs. If the material is bundled, the quantity to be confirmed is proposed at bundle level, otherwise at SKU level. You can adjust the requirement quantity in line with the quantity to be confirmed, or adjust the planned scrap quantity in line with the actual scrap quantity.

If you work with assembly scrap, the quantity entered at bundle level is treated as the gross quantity, which is the planned quantity plus the scrap quantity. It is then used accordingly for the calculation of the net quantity and scrap quantity at SKU level or bundle level. The gross quantities are then correctly updated and you can confirm the scrap quantity correctly.

With AFS you can post goods movements at SKU level in the confirmation and you can maintain changed data, such as quantity, storage location or batch. This is only valid for backflushes and automatic goods receipts. This way you can maintain the data at SKU level, which is transferred from the production and is relevant for the goods movement, both for your backflushed AFS components and for the AFS finished product.

Then you can enter every change in your production cycle up to the posting to the stock and down to SKU level. By flagging the delivery as final delivery, you specify for each SKU that you do not expect further goods receipts for this SKU. You can catch delays in deliveries to customers, for example.

With report J_3AFAUF you can correct many errors related to scrap in existing production orders. Note that the report is only issued in English.

AFS Restrictions

·        AFS does not support collective entry, fast entry or progress confirmation.

·        After the delivery posting, the production order displays the delivered quantity at material level. The confirmation fills the delivered quantity at SKU level, after the confirmation has been posted.

·        The withdrawn quantity is not displayed for AFS components in the overview of the goods movements.

·        You cannot add AFS materials that are not maintained in the production order when you are in the goods movements overview. However, this is possible for SAP standard components that belong to an AFS header material.

·        Note that AFS does not support operation scrap.

·        If the option Adjustment quants in order to act.vals is activated in Customizing under Define production scheduling profile, the standard system changes the planned operation quantity for subsequent operations to, for example, the scrap quantity entered in the first operation. The respective AFS operation data is not adjusted if the actual data is considered in the confirmation. As a result, the sum of the planned AFS operation quantity is different than the standard quantity. Components that belong to reduced operations are reduced by the standard. However, the AFS quantities are not adjusted.