Duplicate Inspection lot creation on Sales Return Inspection 06

[ManjunathR]

Problem: Duplicate Inspection lot creation for sales return process, Inspection lot details: Origine-17 & Inspection type-08

Maintained Master data:

1. Inspection type 06 is activated for sales return inspection

2. Inspection type 08 is activated for Stock Transfer Inspection

3. Inspection Plan for 06 & 08 inspection type activated

Sales Return Process:

1. Return Sale order created: Tcode VA01
2. Outbound delivery created using Tcode: VL01N
3. Inspection lot created with Inspection lot origin/inspection type: 06 Tcode:QA32
4. MIGO: Stock transfer from S/4 storage location to EWM storage location by 453 movement type
5. Inbound delivery created 
6. Goods receipt done by warehouse monitor
7. Inspection lot created (non stock relevant) with Inspection lot origin: 17/inspection type: 08

If we de-activate the inspection type 08, Duplicate inspection lot will not be created but stock transfer can not be worked.

please do the needful, we are awaiting your reply

[ManjunathR]

@ ArnoBrouwer can you help me on this, how to process that configuration as per your statement "change the config to make it IM-HU managed and managed by EWM

[ArnoBrouwer]

Reading above my guess is that the first movement of the return is not received in EWM with an inbound delivery? 

Not an EWM expert, but to solve the double lot and prevent the inbound being created to move the stock to EWM I suggest to directly receive the customer return in EWM with a return delivery. Moving it to another location when return is inspected and found OK would then only be an internal warehouse movement without the need for an additional inbound delivery that triggers the (17)08 inspection.

[ManjunathR]

No Sir, EWM is already in place. After goods receipt via EWM on Inbound delivery, material gets transferred to EWM location but duplicate lot getting created which is non-stock relevant, if we keep that lot as it is, it won't affect anywhere. But it shows in the system as pending and user gets confused that's why need a solution to restrict that lot from creation after goods receipt

[ArnoBrouwer]

Can you check your customizing for movement types: SPRO>Quality Management>Quality Inspection>Inspection lot creation>Inspection for Goods Movements>Movement Type/Update Control/Inspection Lot Origin. For movement 453 the Inspection lot origin should be 05 in the standard system settings for all variants of the 453 movement.

If you have 05 here but still get a 08 lot triggered there is something happening in the system that is not standard.

[ManjunathR]

@ArnoBrouwer Yes Sir same setting is there still creating the Non-stock relevant Inspection lot

[ArnoBrouwer]

Next check: did somebody move the 08 inspection type to another origin? SPRO>Quality Management>Quality inspection>Maintain Inspection Lot Origins and Assign Inspection Types

Origin 05 standard looks like this:

[ManjunathR]

Hi All,

1. If we deactivates the 08 inspection type from that material, inspection lot will not be created but it will not work as client performs plant to plant stock transfer process too.

2. Even if we de-activate the quality inspection at 453 & 311 movement types, still its generating the inspection lot as it is S/4 to EWM stock transfer process at the time of Warehouse task generation.

3. However  if we de-activate the quality inspection at 453 & 311 movement types, the Inspection lot will not be generated in S/4 Hana system.

4. Only Solution i can see is the Enhancement, i.e. whenever the inbound delivery is created and once the warehouse task generates, system will check the movement types (453/311) in Table, if those movement types available there in that table, system will not generate the Inspection lots.

Thanks You

[ArnoBrouwer]

With this remark from you I think it's related to another enhancement that is triggering the lot: "2. Even if we de-activate the quality inspection at 453 & 311 movement types, still its generating the inspection lot as it is S/4 to EWM stock transfer process at the time of Warehouse task generation." Maybe investigate that first before making an enhancement on the QM side.

Also still think the 453 movement should not be the movement that triggers the stock transfer/inbound delivery creation to EWM. This should be the initial receipt of the customer return with a 651 movement. If that movement is received in EWM with an inbound delivery there should be no inbound delivery creation when the 453 movement is done, unless you are moving this between different plants when the 453 is posted.

[ManjunathR]

@ArnoBrouwerAfter Return sale order>Outbound delivery and there 651 movement happening only and inspection lots gets created there.

But after MIGO 453 movement> inbound delivery created and after warehouse task execution and stock moves to unrestricted which is perfect, duplicate non-stock relevant inspection lot getting created which we want to restrict form creation.

[ArnoBrouwer]

Sorry for me not explaining it more clearly.

Please check if the 651 movement is posted to a EWM managed storage location. If that is not the case, change the config to make it IM-HU managed and managed by EWM.

Only after that check if the duplicate lot is still created.

[ManjunathR]

@ ArnoBrouwer can you help me on this, how to process that configuration as per your statement "change the config to make it IM-HU managed and managed by EWM

[emmanuelm1]

Hi,

I suggest that you look on OSS.

I had the same problem on another process (STO with EWM) where I get a duplicate inspection lot 17 & 08.

There was an OSS note which removed the 08 inspection lot.

Best regards,

[ArnoBrouwer]

Is it this one?

3271931 - Inspection lot with origin 17 is created despite QM is deactivated for movement type in OMJJ

Resolution

In order to restrict inspection lot creation in EWM environment, following possibilities can be considered:

A) Use EWM inspection rule to restrict the lot creation for certain document type, item type or other properties. In decentralized EWM landscape, inspection rules are used by default. In embedded EWM landscape, the setting to use inspection rules can be reached at following customizing: transaction SPRO ---> SCM Extended Warehouse Management ---> Extended Warehouse Management ---> Cross-Process Settings ---> Quality Management ---> Basic and Integration ---> Define and Activate Warehouse-Dependent IOTs.

Inspection rules can be maintained in transaction /SCWM/QRSETUP.

B) Check if BAdI /SCWM/EX_QM_INSP_RELEVANCE (method: INSPECTION_RELEVANCE_SET) can be used to prevent inspection lot creation according to the business requirement. This BAdI is available for both decentralized and embedded landscape.