Skip to Content
Technical Articles
Author's profile photo Hanumantharao C

Early inspection lot generation on release of Production order thorugh 1704 inspection type in S/4 HANA 1809


The Purpose of this blog to explain How to generate early inspection lot for EWM managed Materials through 1704 inspection type.

Business scenario:

Business want to have final inspection lot on release of Production order for final assembly or sub assembly, which are EWM managed Materials and business want to post stock into same inspection lot as QI Stock till final confirmation.

Solution in SAP:

As per the requirement, Business expecting to have early inspection lot. Since Materials are EWM managed, we should use 1704 inspection type for final goods inspections.

There is no ContolinspLot settings in 1704 inspection type to select early inspection lot option, which is available in 04 inspection type.Even though there is no such option in 1704 inspection type, same functionality can be achieved by using Presampling concept for Production order/ Process order.

  1. Prerequisites:

1.1.SAP Notes

We must check whether following SAP Notes are implemented in system or Not. If Not, we must implement.

2610300 – Inspection document not created for batch subitems with zero quantity

2749295 – No inspection document update after changing process order

2783544 – Pre-Sampling in Production: Inspection Lot not created during Order Release.

1.2. Configuration

1.2.1 QBEXTP must be activated for pre-sampling in production by using transaction BF11

1.2.2 We must activate the Presampling field in IOT-4 (Inspection object type). This can be done through below I­­MG path.

IMG (transaction SPRO) > SCM Extended Warehouse Management >> Extended Warehouse Management >>> Cross-Process Settings >>>> Quality Management >>>>> Basics and integration >>>>>> Warehouse-Dependent Activation of Inspection Object Type.


The purpose of this setting is to activate the process to create the inspection document that is released before goods receipt posting. This applies only to inspection object type (IOT) 4 Q-Inspection Product/Batch Inbound Delivery.

If you activate this process, Inspection planning is always performed at activation of delivery.
This inspection process does not block the goods receipt for the internally produced goods in SAP Extended Warehouse Management. If the final decision is set for the inspection document, all further goods receipts for the same product/batch are posted to the stock category as configured for the logistical follow-up action.

1.3. Master data

We must maintain the inspection rule for the warehouse where goods receipts happen for Production order/ Process order through T-Code /SCWM/QRSETUP. For this, we must select Inspection process as i.e. Presampling in Production and 1704 as inspection type

By maintaining all above prerequisites, we can get the early inspection lot upon release of Production order/ Process order.

  1. Generation of Early inspection lot:

2.1. On release of Production order:

Manufacturing team create the Production order / Process order and release the order. Once Production order / Process order get released, System generate the inspection lot and same will reflect in QA32 work list.

If business assign the batch number (Either manually or automatic) during goods receipt, then there will not be any batch number in the inspection lot initailly, but batch number will get update once GR done for this production order.

If the business assigns the batch number (Either manually or automatic) during creation/ release of production order, same batch number will get update in the inspection lot, once it gets created.

Since there is no GR, system shows the actual qty as zero initially and there will not be any Material document associated with this inspection lot.

2.2 After Goods receipt from Production order:


After Goods receipt for the production order, Actual lot Qty get updated and there will be Material document/documents associated with this inspection lot.


  1. Sometimes, Presampling (QM-EWM) may not generate the early inspection lots in S/4 HANA 1809 even though all required configuration done, the reason for this is “In SMQ2, the queue QI* resp. QIPP* may not registered for processing. Hence the records will wait in queue and cannot be processed which is why system is not generating inspection lots, so we have to register the queue(s) accordingly”
  2. If the business user takes the UD before final confirmation of production order, system will generate the one more inspection lot for the same production order so we have to keep the inspection lot with out UD till final confirmation of production order to avoid multiple inspection lots for same Production order.


By Maintaining the above-mentioned prerequisites, we can generate the early inspection lot successfully for EWM managed Materials through presampling concept.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Madhu Vadlamani
      Madhu Vadlamani

      Nice Blog.



      Author's profile photo Phuoc Nguyen
      Phuoc Nguyen

      Hi Hanu

      Very detailed and useful blog!

      Do you have any idea about why the Actual lot quantity does not get updated after GR from production order?

      All settings are the same as in your blog. I am using embedded S/4 1909 EWM.


      Thank you.

      Author's profile photo Hanumantharao C
      Hanumantharao C
      Blog Post Author


      We have to impliment belwo S Notes also if you find any issues


      2772971 Inspection update after first goods receipt
      2760463 Deletion flag is set on process order, but inspection document is not cancelled
      2749279 Losmenge wird fälschlicherweise nicht erhöht, obwohl Stichprobe noch nicht berechnet wurde
      2821657 Inspection Lot Summary not working properly with Advanced Production Integration
      2902476 Lot size update after results recording

      Author's profile photo Phuoc Nguyen
      Phuoc Nguyen

      Hi Hanu

      My system component is S4CORE 104, so I tried to implemented note 2821657 and 2902476. Other notes do not support S4CORE 104. Unfortunately, the actual GR quantity still does not get updated after GR from production order.

      Could you help what am missing?

      Author's profile photo Hanumantharao C
      Hanumantharao C
      Blog Post Author

      could you please share the test data with inspection lot, batch, material documents

      Author's profile photo Phuoc Nguyen
      Phuoc Nguyen

      Hi Hanu


      I set EWM IOT settings with Inspection Setup Origin “No inspection rule” since I want to centrally manage QM data from material master.






      After Production order is released, Inspection lot gets generated.












      Batch data of the finished goods in inspection lot.













      After GR posting for the finished goods into EWM warehouse number, the GR quantity does not get updated into the inspection lot. As a result, I cannot make usage decision to change stock type from Quality Inspection into Unrestricted-use or Blocked stock.

      Highly appreciate your help!

      Phuoc Nguyen





      Author's profile photo Hanumantharao C
      Hanumantharao C
      Blog Post Author

      Did you maintain the Q* in SMQR transaction to the Queue from EWM to S/4

      Author's profile photo fuokku guen
      fuokku guen

      Hi Hanu

      I already registered Q* in SMQ, but after GR is posted no queue starting with Q is generated. That makes me really confusing what is missing.


      Author's profile photo Rahul Ghanekar
      Rahul Ghanekar

      Hi Hanu,

      we are getting below message in ABAP dump, any idea about this???

      Short text of the error message:
      Inbound queue name QIPPC5VCLNT1001003608 cannot be used for classic qRFC
      Long text of the error message:
      When you called classic qRFC, you used an inbound queue name that
      cannot be used with classic inbound qRFC. This queue name has been
      implemented for bgRFC instead.
      System Response
      Check whether this queue name is supposed to be used for classic
      inbound qRFC or outbound bgRFC.
      You can use entries in a Customizing table to specify whether a
      queue name can be used for classic qRFC. Queue name prefixes are
      stored in this Customizing table. Any queue names that match the
      prefixes in this table are not permitted as queue names for classic
      In some circumstances you can delete the registration of the queue
      name prefix in transaction SBGRFCCONF.
      The queue name prefix can be deleted only if no more inbound bgRFC
      queues exist with this prefix. Since this Customizing table is a
      cross-client table, there can also be no queues with this prefix in

      any other clients. You can use transaction SBGRFCMON to check this.
      Procedure for System Administration
      Technical information about the message:
      Message class....... SR
      Number.............. 321

      Author's profile photo Hanumantharao C
      Hanumantharao C
      Blog Post Author

      Hi Rahul,

      Please check with your EWM consultant and Basis consultant. they can help you in Queue related issues

      Author's profile photo R K
      R K

      Hi Hanu,

      For EWM 950,What could be the workaround if 1704 inspection lot not generated due to master data maintenance issue in production.Configuration is already setup for early lot release and  lot not generated on release.GR ,Putaway completed.

      master data is corrected later.

      now how to generated inspection lot with1704 type.

      Author's profile photo Hanumantharao C
      Hanumantharao C
      Blog Post Author

      The purpose of early inspection lot is to get inspection lot upon release of production order or process order. if lot was not generated due to master data set up, Do the GR reversal and maintain master data and  stock type as quality inspection in production order and do GR again.

      Author's profile photo Rudra Narayan
      Rudra Narayan


      I am facing an issue in this process.

      The early inspection lot is generated fine in my case but when I create the inbound delivery in SAP EWM it again creates a new Inspection document and in turn creating a new Inspection lot in SAP S/4 ERP . Thereby, I am now having 2 Inspection lots in SAP ERP before GR.

      Note :I am trying in decentral EWM system.

      Any one faced this issue ?