Ansicht
Dokumentation
APO-PPS-PPC: Production Backflush ( RELNAPO_30A_SP1_PPS_PPC )
ROGBILLS - Synchronize billing plans CPI1466 during BackupThis documentation is copyright by SAP AG.
Short text
APO-PPS-PPC: Production Backflush
Use
You use this component if you work in an environment with a high volume of orders with typically small order quantities - often only one piece. The new backflushing function was developed specifically for this "high-volume-scenario" which is particularly common in the Automotive and High-Tech Industries. The backflush can now be carried out significantly faster than has been possible up to now. This is partly due to the new link to the APO system (where the creation of the backflush is separated from the processing of the backflush data) and to the increased separation of the Logistics and Controlling functions.
The backflush data is created in APO due to the systems high availability. The subsequent processes, that is, the execution of the stock postings, are carried out in the R/3 System separately from the creation in APO.
The new backflushing functions are listed below:
- You can backflush in make-to-order repetitive manufacturing and in make-to-stock repetitive manufacturing.
- You can also backflush at reporting points in make-to-order production.
- To speed up the processing in the R/3 system, synchronous and asynchronous goods movements are posted separately.
- The goods receipt in the make-to-order procedure is valuated at goods receipt on the basis of the material consumed. This significantly improves performance.
- WIP (work in process) can be calculated in Controlling
- You can archive the backflushes in R/3 using an archiving object.
- The backflush data is updated in the Business Warehouse (BW) where it can be evaluated
- You can execute the backflush for make-to-order repetitive manufacturing and make-to-order repetitive manufacturing. In this release, you cannot yet backflush production activities or component scrap or excess component consumption.
The backflushing process in R/3 and in APO is as follows for the individual scenarios:
- Make-to-order repetitive manufacturing: Sales orders are created in the R/3 System and the planned independent requirements with their characteristic value assignments are transferred to APO. Here, the finished products and important components are planned using the planning matrix. The less important components are planned in R/3. A creation document is created when backflushing which is used to create the backflushing document in the R/3 system.
- Make to-order repetitive manufacturing:APO planned orders for make-to-stock repetitive manufacturing only have to exist in APO. Production planning and component explosion is carried out in APO. The finished products and important component are planned in APO as in make-to-order repetitive manufacturing and the less important components are planned in R/3. The creation document is also transferred to R/3 where it is converted into a backflushing document. The requirements are reduced in APO and the stock is posted in R/3.
Effects on Existing Data
No link to the Automotive System is required for production backflushing.
Effects on Data Transfer
When creating the backflushes in APO, the relevant data is transferred from R/3 via interfaces (CIF) to the APO System and then transferred back to the R/3 System to be processed.
Effects on System Administration
Effects on Customizing
For the production backflush, you have to maintain the settings for the movement types and for batch and stock determination in the repetitive manufacturing profile. Settings that are mandatory for backflushing in repetitive manufacturing are not valid for the production backflush.
Further Information
IMG texts for the production backflush in the R/3 System: Production Repetitive Manufacturing Production Backflush.
The documentation on the production backflush in the SAP library.
BAL Application Log Documentation CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 4379 Date: 20240423 Time: 143454 sap01-206 ( 77 ms )
