Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Community WIKI SAP Community Welcome, Guest Login Register Search the Community
Purpose
Explains the recurring inspection process.
Overview
This document introduces the settings to create a recurring inspection lot and the generation process.
It includes the following sections:
<Settings>
<Preparation process>
<Inspection lot creation test when batch status is active>
Test case 1: Execute QA07 with “Lot creation only” and “Initial run in days” = 0:
Test case 2: Execute QA07 with “Lot creation only” and “Initial run in days” = 2:
Test case 3: Execute QA07 with “To insp. stock at lot creation” and “Initial run in days” = 2:
Test case 4: Execute QA07 with “Block batch at lot creation” and “Initial run in days” = 2:
Test case 5: Execute QA07 with “To insp. stock at insp. date” and “Initial run in days” = 2:
Test case 6: Execute QA07 with “Block batch at inspection date” and “Initial run in days” = 2:
<Restrictions>
<Settings>
1. OMCT: Batch status activation (Optional)
If you’d like to use the batch status function, you can activate it in t-code OMCT.
For other batch related settings, you may refer to the following document: Overview of Batch Management
2. MM01: Material settings
Activate batch management and set shelf life in the view “Plant data / stor. 1”.
<Preparation process>
To generate an inspection lot with recurring inspection type 09, a batch must exist with unrestricted use stock greater than zero. If batch status management is active, the batch should be in unrestricted
status.
To prepare such a batch, we can post a goods receipt for a purchase order and assign a batch during GR.
2. MIGO: post GR of the PO
3. MSC3N: check the batch status, expiration date and next inspection date
Note:
The expiration date (SLED/BBD) = Date of Manufacture + total shelf life (maintained in material master) = 28.04.2015 + 20 days = 18.05.2015
Next inspection date = last GR date + inspection interval (maintained in material master) = 28.04.2015 + 2 days = 30.04.2015
4. MMBE: check the batch stock. It’s in unrestricted use stock.
Test case 1: Execute QA07 with “Lot creation only” and “Initial run in days” = 0:
Result: No inspection lot is created because next inspection date (30.04.2015) > opening period (29.04.2015)
Test case 2: Execute QA07 with “Lot creation only” and “Initial run in days” = 2:
Result: An inspection lot is created because next inspection date (30.04.2015) < opening period (01.05.2015)
Note: Stock is still in unrestricted use, the status SPRQ is not set.
Test case 3: Execute QA07 with “To insp. stock at lot creation” and “Initial run in days” = 2:
Result: An inspection lot is created because next inspection date (30.04.2015) < opening period (01.05.2015). Stock is posted to quality inspection.
Display the inspection lot in QA03
Test case 4: Execute QA07 with “Block batch at lot creation” and “Initial run in days” = 2:
Result: An inspection lot is created because next inspection date (30.04.2015) < opening period (01.05.2015). Batch status is changed to “Restricted”.
Execute QA11. Post stock to unrestricted use. Change batch status to “Unrestricted”.
Material document with movement type 342 is posted
Test case 5: Execute QA07 with “To insp. stock at insp. date” and “Initial run in days” = 2:
Result: An inspection lot is created because next inspection date (30.04.2015) < opening period (01.05.2015), but stock is not posted to inspection stock as today is 29.04.2015 while next inspection date
has not reached.
Display inspection lot in QA03. Status SPRQ is set, but stock is not in QI.
Display the material document in MIGO. Movement type 322 is used to post stock to QI.
Test case 6: Execute QA07 with “Block batch at inspection date” and “Initial run in days” = 2:
Result: An inspection lot is created because next inspection date (30.04.2015) < opening period (01.05.2015). The batch status is changed to “Unrestricted use” because QA07 is executed on 30.04.2015
when the inspection date has reached.
Display inspection lot in QA03
<Restrictions>
Can’t be storage location specific.
Don’t support consignment stocks.
Don’t support HU-managed storage locations
Don’t support project stocks
Please note the documentation for the report RQAAAS10 (for example in the transaction SE38). Here are the requirements for this report:
The batch master data corresponds to the selection conditions. Only those batches that full fill 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‘
- The stock is not special stock