Show TOC

 Batch Where-Used List

Purpose

This component determines how a batch is created and used in Production Planning PP through various stages of production and displays the result in a list.

You can use this to find out:

  • In which other batches a batch was used

  • From which other batches a batch was created

This is important in the case of complaints and questions about product safety if the composition of semi-finished and finished products has to be documented across all production levels. The material type is not important.

As well as batches, the system also displays production orders, manufacturing orders, subcontract orders, and vendor batches. This enables you to trace a batch’s progress through each stage of production.

The list is used for all plants, but can also be restricted to certain plants.

For batches in other areas, for example Sales and Distribution ( SD) or Warehouse Management ( LE-WM) , the Pick-Up List shows where batches are used.

Integration

Batch where-used records form the basis of the batch where-used list. Batch where-used records are formed from the data from inventory postings and reversal postings in Materials Management ( MM ).

The function includes transfer postings between various batches, but not transfer postings from plant to plant or transfer postings from storage location to storage location.

The various batches in Production Planning are linked via:

  • Production orders

  • Process orders

  • Subcontract orders

The function only displays batches for which a receipt posting or issue posting has been carried out. Batches that were chosen when an order was released are not displayed.

As well as Batch Management (LO-BM) , you need the following components:

Scope of batch where-used list

Required component

Transfer Postings

Materials Management (MM )

Production orders, process orders

Production Planning (PP, PP-PI)

Prerequisites

  • Batch management requirement

All materials that are part of the batch where-used list must be subject to management in batches.

  • Batch where-used file

You can only create a batch where-used list if the receipt records and issue records are stored in the batch where-used file.

You will find further information in the section Make settings for batch where-used list in Customizing for Batch Management.

Features

You can analyze or display the batch usage from either a top-down or bottom-up view. Top-down means that the usage of the batches is displayed. In contrast, bottom-up shows the origins of the batches. The results of the analysis are displayed as a graphical tree.

You can find the call for the batch where-used list under Start of the navigation path Logistics Next navigation step Central Functions Next navigation step Batch Management Next navigation step Batch Usage Next navigation step Display End of the navigation path .

The options Expand transfer postings and Expand even when quantity = 0 are activated as standard.

Note Note

You can use the user parameter DFCHVW to change the default settings for the selection screen.

End of the note.

Display Current Batch Status

You can activate this option if batch status management is active in the relevant system. Because the current batch status must always be read separately from the database and this value is not always of interest, this option is not activated in the standard system, which helps improve the runtime.

Settings for Enhanced Display

The options for an enhanced display only appear on the selection screen if the relevant functions are active in the system, and/or the relevant data has already been updated.

Constraints

You cannot use the batch where-used list function for purchase orders or production orders with account assignment because goods receipts are entered without specifying a batch number.

When several output batches are produced in a process order or a production order, the system forms a total for the input and output batches in the batch where-used list. With regard to the order number of the process order or production order, the batch where-used list cannot distinguish between various inputs/outputs (charges).