Error Message: Deficit of SL Unrestricted-use 2 EA: 21GP84 004 0001
Issue: Queue failed because the stock levels on ECC and EWM are not in sync.
In this case the available stock is less by 2 EA of product 21GP84.
Reason: There are multiple reasons to have the above error triggered. But the main cause of this error is having the stock levels out of sync in both EWM and ECC systems.
Root Cause: There are multiple reasons to have the systems (EWM and ECC) out of sync and queues to fail with Deficit of stock issue, some of them are listed below, 1. When someone manually posts inventory by using the inventory sync program /SCWM/ERP_STOCKCHECK, without checking if there are any open Queues or other process updates. 2. When someone used mass posting transaction /SCWM/POST to change the stock status from available to block or blocked to available, queues are failing if any of the product is out of sync in the system, then it will stop the posting change for all the products in the mass list. 3. If the queue for goods movement EWMMEWMGOODSMVT* is not monitored properly, for all the material movements in EWM system will trigger only on queue name with multiple LUWs and if any of the LUW movement is stuck for any reason, then other LUW’s will get piled up and waiting for the first one to clear.
Resolution:
1. Manual Inventory Sync by using transaction /SCWM/ERP_STOCKCHECK: Business is not supposed to use this transaction to sync the stock levels on ECC and EWM. We have already communicated to the team who are using this transaction in DC W004 and reply from the team and they will stop using this transaction. If they find any issue with stock levels and need help, then they should raise a request and support team will take care of the issue.
2. Mass Posting using transaction /SCWM/POST: Worked with business to understand the reason for using this mass posting transaction and got a confirmation as there is not business reason and the DC team has decided not to use this transaction to do mass posting any more.
Business user explanation why they were using mass posting: “yes, we were converting items from locations that were previously held as Damage storage type locations, (those that automatically changed the stock type to B6), this is no longer a practice for us. Those locations have been converted to regular quarantine locations and will no longer change the stock type; therefore there will no longer be a need to change them in mass.”
3. Monitoring of Goods movement queue EWMMEWMGOODSMVT*: We already have a process of monitoring the queues at regular intervals, but I think it is not happening and we are noticing lot of queues get piled up.
Actions or Recommendations: * Even though we have informed business not to use standard transaction /SCWM/ERP_STOCKCHECK for manual sync of the stock levels. We need to monitor for few days and make sure they are not using the transaction any more or work with SAP Security team to restrict the access of this transaction for business. * As of now we have a schedule to monitor the queues 5 times in 24 hrs (Offshore and Onshore), but at least for next couple of months we need someone monitor the queues hourly to look for the failed queues and if they are holding up any other queues, then just save that LUW. So that others will continue flowing. After that we can take necessary actions on the saved error queue and clear the same. * Apart from monitoring the queues, we have some standard programs to save the failed LUW queues and restart the Queue flow. * RSTRFCDK – Save of qRFC LUW (Inbound) in Saved inbound queue. * RSTRFCIA - RFC TEST: Activate Inbound Queue.
We can use above programs to setup an automated process to save the failed queues and again we need a person to manually monitor the saved failed queues and work for resolution. * Actually there is no business reason to use the mass posting change of the products (transaction /SCWM/POST), but now business is using the same. We need to communicate the business not use this mass posting unless until there is a need for it. Even when they are trying to use this mass posting change transaction, they use large number of products to move from one stock status to another. As standard SAP does not carry out checks against to master data or movement data of the ERP system, if we use /SCWM/POST transaction system does not check Sales order stock, Vendor consignment stock and existence of material master record in the plant. As a result incorrect queue entries are generated in ERP system. * First we need to sync the existing products stock levels on ECC and EWM. * Clear the existing error queues for goods movement and delivery related (Both on ECC and EWM) systems. 