Short text

Deadline Monitoring of Batches

Description
This program suppports deadline monitoring of batches for
batch expiration dates
recurring inspections
Monitoring the batch expiration date
If the batch expiration date is exceeded, transfer postings are made. The follow
ing requirements must be fulfilled for this purpose:
The batch expiration date is exceeded in the opening period, this means:
Current date + lead time > batch expiration date
The indicator for blocking the batch is set.
The following transfer postings are made if these requirements are fulfilled:
If the batch status management in the batch plant is active, the batch status is
changed from "released" to "not released".
If the batch status management in the batch plant is not active, the batch stock
is posted to the blocked stock.
If the indicator for blocking the batch is not set, the system only outputs one
notification in the log.
If the expiration date is not specified in the batch, an inspection is not perfo
rmed.
Monitoring recurring inspections
A recurring inspection is triggered if the date of the next inspection is in the
opening period (see report parameters). This means:
Current date + lead time > date of next inspection
In this case, an inspection lot is opened for each storage location in the batch
stock.
In addition to creating an inspection lot, the batch can also be blocked or the
batch stock can be posted to the inspection stock.
In this case, blocking a batch means:
If the batch status management in the plant is active, the batch status is set i
s changed to "not released".
If the batch status management in the plant is not active, the batch stock is po
sted to the blocked stock.
These changes to the stock can be made at one of the following times:
immediately, when the lot is created
only if the inspection date in the batch is exceeded
In this case, a delayed transfer posting, which leaves the batch stocks in the u
nrestricted-use stock as long as possible, takes place. An accompanying inspecti
on, however, can be performed.
It should be noted that, if a delayed transfer posting is made, the program must
be started every day to ensure that the stocks are blocked correctly.
Note
The execution period of the program must coincide with the lead times for both m
onitoring the batch expiration date and monitoring recurring inspections as othe
rwise the batches cannot be transferred or blocked at the correct time. This mea
ns that the repetition period of the program must be less than or equal to the m
inimum lead time for creating or blocking a batch.
Requirements
The batch master data corresponds to the selection conditions.
Only those batches that fulfill the following conditions are examined:
the batch status is "released".
the unrestricted-use stock is greater than zero.
the stock is not in a HU storage location
An appropriate action is initiated if necessary.
Output
A log containing the processed batches is output.
Furthermore, the actions performed are listed, such as "Inspection lot < > was c
reated" or "Transfer posting document < > was created".
The system also outputs special notifications if problems arise.