Skip to main content

[SAP EWM] Error message - /SCWM/DLV_SERIAL002 - Serial number & for product & already exists in warehouse

Issue

When user is trying to enter the serial number manually in EWM, error message serial number already exist is getting displayed

Analysis :

Whenever serial number is assigned to the inbound delivery, as soon as inbound delivery is saved /SCWM/SERI table will be updated with serial number and inbound delivery combination.

Now, when user try to use the same serial number for another inbound delivery by  mistake then system will validate against this table and restrict business user from saving the document.

Below is the solution approach to be followed to fix this issue in this situation

To check if the Serial Number is assigned to a different inbound delivery follow the steps below:

  • Go to transaction code /SE16 and execute table /SCWM/SERI;
  • Select the relevant Product and Serial Number;
  • Execute the selection;
  • You will see a line that contantains the DOCID which has the corresponding SN assigned;
  • Copy the DOCID;
  • Run table /SCDL/DB_PROCH_I;
  • Enter the previously copied DOCID;
  • The inbound delivery number will be displayed.
  • By following these steps, you will be able to identify the inbound delivery associated with the Serial Number.
  • Open the delivery in /SCWM/PRDI transaction and decide if this documents has to be Goods Receipt posted or rejected.
  • You can either delete the Serial Number from the initial inbound delivery if not yet Putaway.

 

Comments

Post a Comment

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.
Post a Comment
Read more

[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
Post a Comment
Read more

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...
1 comment
Read more