SAP EWM SUPPORT INCIDENTS

1. After Delivery distributed to EWM, Delivery is in block mode ( RED light) , can’t create picking
warehouse task or put away task for Deliveries?

Resolution:

Reason 1: Due to no serial Number for the Product in the delivery, delivery is in the block mode,
Adding the serial number for the products allows system to create the pick task. ( If product is
serialized product)

Reason no 2: If the material is batch managed and no batch maintained in S4 delivery, it will be
distributed in Block mode. Solution maintains the batch to the product then delivery becomes
unblocked status.

Reason no 3: Due to no Goods Movement bin delivery was In the block mode, by adding the Goods
Movement bin manually delivery status changed from Block to Available (Green Mode),There was
no Goods Movement bin assigned with the combination of Warehouse process Type.

2. Handling Unit Inconsistencies/Stock Bin Inconsistencies errors, system could not able to create
picking task even stock is available in bin.

Due to some Issues sometimes Stock will have inconsistencies, to Clear the Inconsistencies we
usually have the Check Monitor - /N/SCWM/CHM_LOG

Click on AD-HOC

pg. 1 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Select the stock and bin and Click on Show Selection.

Provide the Data and click on Execute.

pg. 2 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Right click and then click on add missing entry to clear the inconsistency for the stock.

3. Could not fully determine destination data while creating the put away task for the inbound
delivery?

Reason1: Check put away strategies are in place or not.

Reason2: check master data like PACI assigned to product master data or not (If my STSS
determination is dependent on PACI).

Reason3: If HU type check is ticked in storage type configuration and check HU/SBT combination
entries for your warehouse and storage types.

Reason 4: Maintain correct Optimize access strategy for storage search for put away.

Reason5: Due to Exceeded Weight system was not creating Put away Task, Create the Put away task
manually or update the bin capacity if still empty space is available in bin to resolve the issue .

4.While Creating Staging Area Warehouse Task system was throwing the error as PSA not assigned
to WorkCentre.

Assign the PSA using T Code- CR03

5. The stock for the Product A, Available in 2 different bins, due to negative stock allowed for the
Storage Type, the system creating the task from Single bin,

Now how to pick the delivery stock from two bins to satisfy delivery quantity?

While Picking We can use Exception Code BIDP Partial Pick Denial and Pick available stock, for
remaining qty system will redirect to another bin.

6.Acknowledge PO Due to Date Varience

Date was different in PO as compared to IBD; system was throwing a warning Message while
creating IBD In VL31N

pg. 3 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

7. Material does not exist in storage location AFS error , we get this error once put away done in
EWM and trying to update the stock transfer from ROD to AFS in S4 side.

Extend Material Master in MMSC and Reset the Queue

8.Picking task is not Creating for Outbound Delivery

Reason1: The stock type is different for the line item due to incorrect storage location in the Sales
order and OBD.

Reason 2: check Removal strategies.

Reason3: Stock may be in Non pickable location or on the resource.

9.A reason code must be entered error while scarping the stock in /N/SCWM/ADGI?

While Scrapping the Stock, there was no reason code entered due to that system was unable to post
the stock in S4, reversed the Task and Re-entered the Movement Reason and posted the Scrapping

10. Account Type K is not assigned to Document type WL

Configuration is missing from FICO side.

11. Command for QRFC LUW Execution , this error we get while GR updation or PGI updation to S4
( This is Queue error, can find in SMQ2)

Due to Multiple Screen open, the delivery got stuck in the queue as Command QRF, To clear the
queue reset the queue.

12. Application Log could not convert queue – This is also Queue error – at the time of put away
task creation.

Due to No Empty bin found system could not create put away task.

13.PPF Action is not Triggered for Delivery Note ,although Condition Records are
maintained?

solution: Check Printer Assignment in Transaction: /N/SCWM/SR_PRINT and SU3

➔ /N/SCWM/SR_PRINT

pg. 4 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

➔ SU3

14. Could not able process the Picking WO in RF device to the newly create bin, system throwing
the error : Warehouse Order is not intended to process.

Ans: Bins which created newly has no assignement of activity area,

Resource can be process the WO with the help of queues, if no activity area assigned to bin, so
there will be no queue determination to the WO.

To resolve this do bin sorting to the bin , so that activity area will be assigned to the bins. So that
WO can be assigned to the queue.

15. After GR in ewm system throwing the erro /SCWM/NRTO not maintained for the warehouse ?

Maintatin the number ranges for the warehouse

16. unable to create the bin, error warehouse assignment in not available ?

Assign the SCU to warehouse, so that system will allow to create the stoage bin.

pg. 5 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

17.RF Screen Verifications are not working , in RF for a particular user ?

solution: Usually, Screen Verifications works based on Presentation Device – Display Profile
and Personalization Profiles.

➔ Check Presentation and Display Profile Assignment in Transaction: /N/SCWM/PRDVC

➔ Check the Resource and Presentation Device Assignment in Transaction:

/N/SCWM/RSRC

➔ Assignment of User and Personalization Profile in Transaction: /N/SCWM/USER

18.Labels were not Printing although Spool was generated?

Resolution: Sometimes Due to Printer Gets Offline due to that system keeps the Spool in
Waiting or with Blank Status, once we Restart the Printer, Prints will automatically trigger on the
Printer

Transaction: SP02

pg. 6 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

19.During Stock Migration for Serialized Products, Once the stock is Uploaded in the
System Serial Numbers were not Updating to S4 (IQ03) what could be the reason for this?

solution: Due to None - Serial No Usage in the Serial No Procedure, system was not updating
the serial numbers to S4, after changing the serial no usage from NONE to OBLIGATORY system
is Updating the serial numbers to S4

20.Posting Only Possible in Periods 2021/06 and 2015/04

pg. 7 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
solution:

T-Code: MMPV

Input the Company Code, Select Check and Close Period and click on Execute.

System has closed the previous period.

pg. 8 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

21. Exception code WR17 Error-It is basically HU related Issue while Inbound delivery
distributed from S4 to EWM? HU issue?

Resolution:

Step-1: Copy delivery number and delete the queue,

Step-2: Then update that delivery with status ‘A’ in Functional Module: /SPE/DELV_RESET_DIST_STATUS

Step-3: After that go to vl32n and enter the delivery and hit enter.

Step-4: Go to total content and delete the Hus, after deleting go to pack Hus and give delivery
number and Box hit enter, After the go to pack material select handling unit and material click
on pack. Then save it delivery distributed to EWM and check in PRDI transaction.

22.RF ERROR: Quantity # differs from number of serial numbers # (/SCWM/DLV_SERIAL203)

Occasionally the process of the RF serial numbers could write an incorrect number of serial numbers in
relation to the part in the handling unit. This can happen for a variety of reasons, but the following
business process will rectify the situation to get the handling unit to repack WorkCentre.

Resolution:

User is on the RF and Press Goods Receipt for the RF:

User encounters Error screen indicating the “Quantity # differs from number of serial numbers

pg. 9 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Enter into transaction /N/SCWM/PRDI with the delivery number for the problem delivery

Search by the delivery number

Validate for the line item, that the number serial numbers assigned is correct. If not correct,
please contact your system administrator.

Select the HU tab. Select the handling unit that is causing the issue on the RF and click the
Goods Receipt icon.

pg. 10 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Repeat for each instance of HU issues.

We now need to create the warehouse task to move the HU from the GR-ZONE to the Inbound
Repacking WorkCentre. With the delivery header line selected, Select Inbound Delivery >
Follow-on Functions > Warehouse Tasks.

Select the Handling Units tab, Click the Select All icon and then the Create and Save Icon.

pg. 11 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Warehouse Order will create and the tasks will auto execute to the inbound repacking
WorkCentre. Please continue with the receiving process.

23. Batch for Serial Number ** differs from Document Batch

Resolution:
There will be instances when the master batch of the serial number equipment does not exist. This will
happen when attempting to do a posting change to a different batch for business reasons (batches auto
create when entering them in MIGO or in EWM without need for an ad hoc process – Inventory movements
do not synchronously update equipment masters). The following will provide a queue error view and how
to clear the error.

Summary:

1. Get batch number from WH Task (Use Monitor)

2. Go to /nIQ09 – enter Serial number from error (F8) and enter the batch number obtained from WH
Task into the Master Batch field. This Master batch field will have a different number from the one
in the WH task and that is the issue. Save after entering correct task number into Master Batch
field and SAVE. Only 900 series numbers can have a batch number, NOT a 300 series. Ensure
correct entry.
3. Re execute the error. Should go away. Sometimes it comes up with a new Serial number with
error again. Follow same process again for that serial number till error goes away.

pg. 12 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
24.Queue Error – Full Delivery Required (ZFULLDELQERROR)

Resolution:

When deliveries from sales orders are zeroed out (not deliveries from projects), there is a full
delivery requirement assigned to each item. The zeroing of the delivery does not satisfy the
requested amount this a queue error when posting to ECC, Full delivery is required, is created.
To fix this, the C in the database table needs to be taken out.

The transaction ZFULLDELQERROR is a Z- progarmmme has been created to handle this

situation and only remove these “C” values when there is an applicable queue error in the
system.

After zeroing out the delivery in PRDO, use the transaction steps and process to clear the queue:

1) In the monitor, the queue error for delivery shows with message text “Full delivery is
required”.

2) Enter into transaction /NZFULLDELQERROR

3) The Remove Full Delivery Flag for Delivery Items program will show. Leave the test mode
check box checked and select Execute.

4) A message will show if the delivery can be deleted. This indicates there is a queue error
for “Full delivery is required” (NOTE: Program only works for this queue error). Go
back to previous screen by selecting the F3 key.

pg. 13 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
5) Uncheck the Test Mode checkbox and Select the Execute icon.

6) A message for updating the delivery will show. This indicates the “C” has been removed
for the delivery items and the queue error can now be cleared.

7) Back on the queue error, Select the line and Select the Execute icon.

8) Queue error is now cleared, and the delivery will post in ECC for zero on the line items.

pg. 14 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
25.Could not Conver t Queue WMTH0000*

Resolution:

This error occurs either on the inbound or outbound side.

1. Outbound – The outbound team did not create the Pick HU correctly. They use
/SCWM/ADHU (create WH tasks) as a work around to create their own tasks. They might
have already taken the del to PGI with manually created tasks. Check system for status
of HU. In above instance, the User created a Higher-Level HU and did not nest lower-
level HU in it, was therefore empty and could not be processed.

If they have completed all steps, then just delete the error.

2. Inbound – The Put away Strategy does not exist in the Product Master. A job updates the
strategy if new product is created. This strategy would have to be updated and then the
error reprocessed.

If Business Object says “Handling Unit” then Object Key is the HU number, similarly for inbound
or outbound deliveries.

Got same Q error again.

SMQ2 shows same error.

Double click on above

pg. 15 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Double click again

Then you see Display logs as below.

Shows WPT was not determined. Normally this means the WOCR was not determined correctly.

Now go to Monitor. You see WOCR was determined correctly.

Go to Monitor – Documents – WH task.

Enter task number from original Q error (Business Object and Bus Object key) 100000046704.

Take this Outbound delivery number as below and go to Monitor – Outbound del – and pull up.

See below – WOCR was determined.

pg. 16 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

In these cases, it can be determined that during repacking of the product the POSC step was
not passed to the new HU. There will be no way to fix this queue error, this can now be deleted.

So, in this case the Q error can be deleted as mentioned on page 1 of this document.

Either in SMQ2 or in the Queue Error monitor screen. Above is the SMQ2 screen. Select as
above and just hit delete (Trash can)

If the delivery has been processed already, just delete the error. If it is locked, tell user to get out of
it, reprocess the error.

pg. 17 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
26. Post Goods movement in ERP (from EWM), after clicking the PGI button in
/SCWM/PRDO.

Resolution:

Errors like one below need research. In the example below, this was a customer return to a
stock PO. Person who added lines to the sales order did not enter the Account Assignment. The
Business Object Key here is the WH task, and the SAP Order number is mentioned in the
message Text.

This was a return to a Stock PO. Customer was shipped to product earlier, but they asked us to
hold till later. So, this was brought in against a stock PO to be shipped back to customer. No
purchase requisition was supposed to be created since we already had stock.

27. Queue Error – System Status CRTD is Active – BI-000000-00

Resolution:

1) Queue error is showing the in the monitor message queue list for “System Status CRTD
is active (WBS BI-######-##)

2) Enter Transaction /ncj20n (Project Builder)

pg. 18 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
3) Select the Open icon.

4) In the WBS Element field, Type in the value from the queue error. Click the green
checkmark icon.

5) The project will show with the system status referencing CRTD. Ensure the Layer 1 is
selected (highlighted).

pg. 19 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
6) Select Edit, Status and then Release (Click on Release).

7) The status will change to REL and the status will show set on the bottom of the screen.

8) Select the Save icon.

9) A success changed message should show on the status bar.

10) Return to the message queue screen and select the queue error. Select the Execute
icon.

pg. 20 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

11) The original error for WBS BI-000481-03 was cleared successfully and if not other errors
for the goods movement were existent the queue error would disappear. This example
has further issues with more CRTD projects. Repeat the full steps of the walkthrough as
necessary until the queue error clears.

28.More Serial Numbers than Exist in Delivery, If scanned more serial numbers than the
quantity in inbound while unloading and GR.

pg. 21 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Resolution:

pg. 22 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

pg. 23 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

pg. 24 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

pg. 25 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
SPRO Settings – Raise Message with SAP. Sends 8 Serial numbers instead of 4 and 4.

Immediate needed for regular inbounds. But Send Full GR option below required for Posting
changes. Ticket with SAP. Cannot use Expected GR.s

pg. 26 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
29.Queue Error: No Unique Jurisdiction Code Cannot be Determined

A queue error shows for the following in the warehouse monitor:

The message text references an application log so going to SMQ2 to view the error text will be
necessary. Once drilled down to the error message (in this case for delivery 80005087) the log
shows there is no unique jurisdiction code assigned to the delivery.

This happens because there is multiple to choose from. This is happening in the background
during dashboard delivery creation. User manually enter the one-time ship address and the
system doesn’t determine the code.

Resolution:

It will be necessary to do the following:

1. Reset the distribution status for the delivery in ECC.

2. Delete the queue error.
3. Update the jurisdiction code on the one-time ship-to address on the ECC delivery.
4. Redistribute the delivery to EWM.

Do the following to complete those steps:

Go into SE16 and search by the LIKP the delivery number with the issue:

pg. 27 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Locate the filed VLSTK and validate the value shows for B:

pg. 28 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
Contact a developer to debug table entry to change the value of B (distributed) to A (relevant) for
the delivery. This will reset the distribution status of the delivery and allow for our updating of
the tax jurisdiction code.

Once the above table entry is adjusted, go back into SMQ2 and delete the queue for the delivery
in error (This needs to take place, else the redistribution of the delivery will get stuck in the
queue again):

Go to VL02N and search by the delivery in question:

Select the address button next to the ship-to party number (this is where the manual one-time
ship to address is entered):

pg. 29 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Update the language in the communication section and select the plus icon in the Street
Address section:

pg. 30 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
Click in the Tax Jurisdiction field and select the search button (or press F4):

A selection screen will show with the appropriate information for tax code determination, select
the green check mark:

Possible entries will show, select the appropriate tax jurisdiction code

NOTE: If unsure of the code, please reach out to Finance SAP IT department for assistance.

pg. 31 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
Once selected, the value will update in the address screen, Select the green check mark:

Select the save icon:

The delivery will redistribute to EWM:

Go into EWM and validate the delivery distributed successfully. If it doesn’t show, please see
your system administrator.

pg. 32 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
30. Queue: Status of at least one serial number is not allowed

/scwm/diff_analyzer

Posted the difference at the item level

pg. 33 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Go back to monitor to see if I can complete the queue error from the difference analyzer posting

Error still exists.

Resolution:

Get serial number data from queue container at item level then go into iq09 to view up the serial
numbers to see status.

Iq09 view

pg. 34 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

I’ll get into change mode, then select all and select the details view

I’m checking in the equipment master for the last goods movement date to see if it’s ahead of
the queue created on date. The queue created on date is the date of goods movement it’s
attempting to do so I want to ensure that each equipment master has last date of goods
movement on that date or before. Change the value is needed.

pg. 35 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

Modified the appropriate equipment masters, then attempted to clear queue.

Queue has cleared

pg. 36 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
31. Queue Error Resolution for “User Status #### is active (NWA ####### ####)

Resolution:

1) Queue error for status PLAN or other is showing for a particular network and item
number within the network (Example below is network 4010047 and item number 0010).

2) Enter into transaction /ncj20n (Project Builder)

3) The project builder screen will show. Select the open icon.

4) There will be three options for opening the project. In the Network field, Enter in the
Network number from the queue error. Select the Open icon (Green Checkmark).

pg. 37 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

5) The project infomraiton will show. Take note of the item number that is causing the
issue in the queue (0010 in this example).

6) Select the line item before Selecting Edit > Status > User Status > Set & Pass On

7) The user status pop-up will show. Select status POST and Select the Green check mark
icon.

pg. 38 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

8) A user status window will show referencing the status has been set. Select the Green
Checkmark icon.

9) Select the Save icon and Select the Exit icon.

pg. 39 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

10) In the monitor message queue view, Select the queue error and Select the Execute icon
(this will retrigger the queue message to attempt to post).

11) The message will disappear indicating the posting was successful.

12) As a validation step, it would be recommended to ensure the delivery posted in VL03N
under the Status Overview tab. Ensure the delivery has a goods movement (GM column)
status of C in which it indicates complete.

pg. 40 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS

32. Turn on serialization for the material

Resolution:

Sometimes Serialized Products Created without Serial No Profile, to turn on Serialization for the Materials
Add Serial No Profile in General Plant View and WM Execution View to Make the Product Serialized and
add the serial number requirement in Table level in /SCWM/SERH or /SCWM/SERH2

Material Master:

pg. 41 ROHELA TECH IT SOLUTIONS

 SAP EWM SUPPORT INCIDENTS
Table: /SCWM/SERH2

pg. 42 ROHELA TECH IT SOLUTIONS