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

Root cause

Creation of inspection lot with origin 17 is controlled by EWM and during inspection planning EWM coding is triggered. Therefore, setting to prevent inspection lot creation in movement type customizing at ERP side (transaction OMJJ) is not considered.

Solution Approach

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.

Comments

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...

SAP Logistics

Search This Blog