SAP Program RQAAAS10 - 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 following 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 arefulfilled:
        • 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 onlyoutputs one notification in the log.
            If the expiration date is not specified in the batch, an inspection isnot performed.

            Monitoring recurring inspections
            A recurring inspection is triggered if the date of the next inspectionis 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 inthe batch stock.
            In addition to creating an inspection lot, the batch can also be blockedor 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 is changed to "not released".
              • If the batch status management in the plant is not active, the
              • batch stock is posted 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 stocksin the unrestricted-use stock as long as possible, takes place. Anaccompanying inspection, however, can be performed.
                  It should be noted that, if a delayed transfer posting is made, theprogram must be started every day to ensure that the stocks are blockedcorrectly.
                  Note
                  The execution period of the program must coincide with the lead timesfor both monitoring the batch expiration date and monitoring recurringinspections as otherwise the batches cannot be transferred or blocked atthe correct time. This means that the repetition period of the programmust be less than or equal to the minimum lead time for creating orblocking a batch.

                  Precondition
                  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 an HU storage location.

                  • The stock is not special stock.

                  • 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 created" or "Transfer posting document < > was created".
                    The system also outputs special notifications if problems arise.