Skip to main content

Removing Short delivery quantity from MRP

Commonly, Business receives less than the ordered quantity from the vendor ie., short delivery will happen then in the case the remaining quantity will still appear in requirements list until it is delivered. If no further deliveries are expected from the vendor then this requirements need to removed from the requirements list else it will mislead the MRP controller. So In order to remove them from MD04 then we need to perform any of the below activities. 

1. Reduce the PO quantity to that GR quantity so that no remaining quantity exists
2. Maintain delivery complete indicator for the PO line item so that remaining quantities will not be displayed in the MRP.

Below is the process steps for reference.






Delivery complete indicator is maintained against the PO line item


Remaining quantity got removed from the MRP list.

Comments

Popular posts from this blog

[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.

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 EWM] Adding custom fields for /SCWM/PACK Screen

If business want to add a custom field to the /SCWM/PACK screen and the requirement is that once business enter value here system will check against the weight in the material master  Step 1 : Structure /SCWM/S_PACK_VIEW_HUHDR need to be appended with the new custom field Step 2 : Then use screen enhancement /SCWM/UI_PACKING /SCWM/EX_WRKC_CHECK_BFR_HU_CMP to include logic specific to validation and updation of the table