This process describes a typical
scenario for batch record archiving.
The batch for which the batch record
is to be created meets the following requirements:
An approved process order was used to manufacture the
The batch is only assigned to one process order.
Only one incoming inspection lot has been created for the
A batch has been manufactured in
your plant and a batch record must be created and approved for it.
The reasons for this might be, for example, that the usage decision
for the incoming inspection lot cannot be made without or the batch
status cannot be changed from Restricted to
As the header record of the batch record you create a document
info record. The simulation list or the archive file with the R/3
data of the batch record is allocated to this document info record
as the original application file.
You simulate the batch record based on the data currently
existing in the system and check whether it is complete.
If not, you make sure that missing data is added, for example,
by sending all process messages for the order.
If part of the relevant data is stored outside the R/3 System,
you include archive files from non-SAP systems to the batch record.
To do so, you transfer them to the header record of the batch
If it has not been done yet, shop floor control and quality
assurance must now set the following statuses for you to be able to
archive the batch record:
– Order status Technically completed
– Inspection lot status Inspection close completed
When the simulation lists are complete and the status
requirements met, you archive the record.
The archived batch record is approved by you or another person
with the corresponding authorization. To do so, you execute a
The approved record can now be used
as a basis for making the usage decision and changing the batch