The difference between reporting point Backflush and milestone confirmation

Milestone Confirmation is for discrete manufacturing.

Reporting point Backflush are for REM. ~~~~~~~ but the settings in Control key is the same for both.

TCODE:CO15---Create production order confirmation

If u do confirmation without RP it's like order level confirmation CO15 in DISCRT all the opeation are confirmed at Once.H ere u canot use Operation wise.

To see the Reporting Point overview after confiramtion at each Reporting point, you can use MF26, this would give WIP qty To is conformed at each reporting point.

CO19---Create time event for production order

When in REM we use MFBF reporting-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 the This function if:

• The longer leads times, but want to withdraw the components closer to the time they is required for the Operatio N.

• 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 is backflushes all material components which have been consumed and posts The activities carried out on 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 PR Ocess, but you also want to be able to backflush scrap directly at the operation. In addition, the optional reporting point can is 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's on the production line at that point in t IME, for each reporting point. You receive a document for each reporting point. Mandatory reporting point Backflush guarantees maximum control over the operation, however, it's more time-consuming.

When you carry out the WIP posting is temporarily working in mandatory reporting point backflush processing because W IP value entry is carried out in the same-in both optional and mandatory-reporting point backflush.

When you define a particular operation as MIlestone operation on routing then it while doing confirmations it acts as repo Rting Point.

From F1 Help

Milestone Confirmation:

A type of completion confirmation in which several operations in a processing sequence is automatically confirmed. An operation are marked as a milestone operation using its control key.

If you confirm an operation, which is marked as a milestone, the system automatically confirms all preceding operations.

If Several operations is marked as milestones, they must be confirmed on the order in which they appear in the processing Sequence. The system confirms all operations the preceding milestone.

Operations that has been confirmed manually is not affected by milestone confirmations.

The difference between reporting point Backflush and milestone confirmation