This function is an enhancement for updating the batch where-used list using a batch-specific update for materials manufactured in repetitive manufacturing. This allows for a link between produced batches and the actual component batches used to produce them. The enhanced update is performed during the backflush in repetitive manufacturing.
The batch where-used list must be active in Customizing for
Batch Management
under
.
Multibatch evaluation must be activated for the repetitive manufacturing profile in Customizing for
Repetitive Manufacturing
under
using the
Update Batch Where-Used List
indicator
Note
If you want to create postprocessing records cumulatively, you must work with single postprocessing records.
For more information on backflush in repetitive manufacturing, see Confirmation and Backflush (PP-REM) .
The multibatch functions are possible for each type of confirmation. In order that the batch where-used list in repetitive manufacturing is consequent, the following conditions must be fulfilled:
The component is subject to a batch management requirement.
The produced batch is given.
The multibatch function is activated.
You can define additional consistency checks using the user exit EXIT_SAPLBARM_001.
The following scenarios are covered:
Assembly backflush, reporting point backflush, component backflush: For each, goods and scrap backflush including document cancellation, document-neutral cancellation, cancellation for document-neutral cancellation (transactions MFBF, MF42N, MF41, MF12)
Postprocessing using single postprocessing records (transaction MF47, report RMSERI13)
Postprocessing with transaction COGI
Separated backflushing processes (transaction MF70, report RMSERI70)
Display
You can use the
Multibatch Evaluation
indicator on the selection screen of the batch where-used list to display existing data for the multibatch function.
Backflush without Goods Receipt
The batch where-used list can also be updated for produced batches that have not yet been posted into stock.
This can occur for
Reporting point processing
Scrap backflush
Component backflush