首页 > 代码库 > The difference between reporting point backflush and milestone confirmation
The difference between reporting point backflush and milestone confirmation
Milestone Confirmation is for Discrete Manufacturing.
Reporting point backflush is for REM. ~~~~~~~ But the settings in Control key are the same for both.
Tcode: CO15 --- Create production order confirmation
If u do confirmation without RP it is like order level confirmation CO15 in discrt all the opeation is confirmed at once.Here u canot use operation wise.
To see the Reporting Point overview after confiramtion at each Reporting Point , you can use MF26, this will give WIP qty to be conformed at each reporting point.
CO19 --- Create time event for production order
When in REM we use MFBF reporting point back flush like CO11n which carried out on operation basis as milestone operation is confirm previous also get confirm.
Reporting point backflush for stock materials
Use
It makes sense to use this function if:
You work with longer lead times, but want to withdraw the components closer to the time they are required for the operation.
You want to calculate work in process.
You want to backflush scrap quantities at the corresponding operation.
If you use reporting point backflushing, the system backflushes all material components that have been consumed and posts the activities carried out at the reporting point operation. It reduces the dependent requirements in the planned orders and updates the statistics in the LIS.
You can use either the mandatory or the optional reporting point backflush.
It makes sense to use the optional reporting point backflush if you usually only backflush at the end of the production process, but you also want to be able to backflush scrap directly at the operation. In addition, the optional reporting point can be used to carry out a WIP calculation at the end of a period.
If you use mandatory reporting point backflushing, you post the quantity that is on the production line at that point in time, for each reporting point. You receive a document for each reporting point. Mandatory reporting point backflush guarantees maximum control over the operation, however, it is more time-consuming.
When you carry out the WIP posting you are temporarily working in mandatory reporting point backflush processing because WIP value entry is carried out in the same way in both optional and mandatory reporting point backflush.
When you define a particular operation as MIlestone operation in routing then it while doing confirmations it acts as reporting point.
From F1 help
Milestone confirmation:
A type of completion confirmation in which several operations in a processing sequence are automatically confirmed. An operation is marked as a milestone operation using its control key.
If you confirm an operation that is marked as a milestone, the system automatically confirms all preceding operations.
If several operations are marked as milestones, they must be confirmed in the order in which they appear in the processing sequence. The system confirms all operations up to the preceding milestone.
Operations that have been confirmed manually are not affected by milestone confirmations.
The difference between reporting point backflush and milestone confirmation