cancel
Showing results for 
Search instead for 
Did you mean: 

System creating only one warehouse task for all pallets in EWM.

Former Member
0 Kudos

Hi Everyone.

Please support me on below issue.

I am transferring product(qty = 280, which is equal to 4 pallets) from distribution plant/SL to PSA SL.

I am expecting system should create 4 WT and so 4 WO. But system is creating only 1 WT and so 1 WO.

More detail:

WPT used:4ABC(lets say) Tsf FG Rework to Prod Supply

WPT is having:

WO Rule :HU03

Activity: STCH

Also.

Creation Cat.: Pick Path

Item Filter          HU03

Limit Value Type: WT

Limit                MX01 (Maximum One Item)

Max. Itm per WO 1

Max. CGr per WO 0

Max.CGrp per HU 0

Max. No. of HUs 0

Min. WTs per HU 0

Max. WTs per HU 0

Also, Please find the activity log for WO creation:

Warehouse order creation started

Warehouse order creation is processing:

1 WTs with directly assigned creation rule

0 WTs with search sequence for determining creation rules

Warehouse order creation called up within a process

Creation rule HU03 used for 1 WTs

Creation rule HU03 is of the type "Pick Path"

Item filter HU03 checked

WT 1XXXXX passed the filter

1 WTs passed,     0 WTs did not pass item filter HU03

Inbound WT sorting rule PIPA used

1 WTs passed,     0 did not pass subtotal filter

Limit value MX01 used for 1 warehouse tasks

Warehouse task 1XXXXX passed limit value

Maximum limit value for 1 warehouse tasks was adhered to

Limit values: current values for these 1 warehouse tasks

Limits for items: minimum 0, maximum 1, current 1

Limits for number of HUs: maximum 999, current 0

Resource management called with queue A.INT.FG

Content provider 02 determined for warehouse order 9639

Warehouse order 9XXXXcreated on the basis of creation rule HU03 with 1 WTs

Please support.

Let me know if more information is required.

Accepted Solutions (0)

Answers (2)

Answers (2)

Sandip_S
Active Participant
0 Kudos

Hi,

Not sure how packspec and capacity works together..

But I guess if storage type having available quantity settings as HU level, system will create 4 WT for four pallets and if it is on storage bin level then it will create 1 task as the available stock is having only one quant.

Probably, you can maintain the quantity classification at the storage type level and same you can maintain correctly in packspec level. also please check the rounding setting which plays very important role while creating the warehouse task.

Thanks,

Sandip

Former Member
0 Kudos

Hi Sandip/Reddy.

Thanks for reply.

Please find more detail about used ST: 1A02

Qty Classific= 1 (Base UoM)

No capacity update: it is not ticked.

Also, Pack spec involve is also haivng Qty Classific= 1 (Base UoM)

Thanks,

Former Member
0 Kudos

More detail about ST.

Sandip_S
Active Participant
0 Kudos

Hi Prashant,

I think its more about picking setting and not the putaway.

What is the quantity classifier you are using for pallet quantity? Maintain the same in storage type settings and check if the same is maintained in packaging specification also.

Also, set the rounding rule as per the business requirement.

Thanks,

Sandip

Former Member
0 Kudos

Hi Sandeep,

Thanks,

Please find the detail.

Qty Classifier in Pallet Qty = 4. ( Customizing for Extended Warehouse Management under  Master Data  Product  Define Unit of Measurement Attributes )

Qty Classifier in ST: 1

Qty Classifier in Packaging Specification = 1.

So do i need to change Qty Classifier in Pallet Qty = 1 ?

Thanks

Sandip_S
Active Participant
0 Kudos

Hi Prashant,

if your packaging specification having these level maintained then try to maintain the same pallet level in storage type level and then try to create task.

Thanks,

Sandip

former_member183610
Active Contributor
0 Kudos

Hi Prasanth,

please check the below document , it may give some over view on your requirement.

C K Reddy

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

the WOCR is not your issue, your WT is. Do you have a log for the WT as well?

Brgds

Juergen

---

Want to learn EWM?

Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm

Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

Former Member
0 Kudos

Hi Juergen,

Thanks for your quick response.

I am new to EWM. Can you please tell me how to get log for WT?

I can see log number for WO but not for WT.

//Regards

Prashant

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

you can find it in the warehouse management monitor - if logging is enabled. Where did you find your WO log?

Brgds

Juergen

Former Member
0 Kudos

Hi Jurgen.

For WO log, I went into Tcode:/scwm/im_pc

Then WT then from WT to WO. i scroller right side and in last column is WO log number.

I took that log no and used in SLG1.

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Kudos

Whoa, never seen that

But the easier way still probably is if you look up the WO in the warehouse management monitor and select More Methods --> Display WO Log. And the same can be done for the WT. If no log is shown, the logging is not enabled.

Brgds

Juergen

Former Member
0 Kudos

Yup  i found the WT work log:

*****   Product WT Creation    *****

For warehouse request SPC 40000000906 10

For product 9XXXXX; quantity 280,00000000000000 CAS

*****   Determine source data - start  *****

Determining source data with storage type:, section:, bin:, HU:

Storage type search fully defined: No entry found

Storage type search with wild card: Search sequence RW01 and rule RW01 found

Determine stock in source storage type 0A8C

Restricted batch stock have been skipped for process type 5A92(8GPP)

Determine stock in source storage bin V-13-17-R

Handling unit type 4PAL determined

Requested quantity rounded to 280,00000000000000 CAS

Source storage bin T-13-17-Ndetermined in storage type 0A8C

*****   Determine destination data - start *****

Storage type search fully defined: No entry found

Storage type search with wild card: Search sequence PB01 and rule  found

Storage type search sequence PB01 found

Destination storage section check is not active in storage type 2A01

Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType

Access table for bin search:

Storage type: 2A01 storage section: **** bin type: BL01 whse pos. eval.: 00000

Storage type: 2A01 storage section: **** bin type: G001 whse pos. eval.: 00000

Start of destination bin search

  1. Stor.type: 2A01, stor.area: ****, bin type: BL01, stock mvmt: 00000 being examined

Storage type 2A01: HUs allowed but not required

Standard putaway behavior (storage type 2A01)

No suitable empty bins found in stor. type 2A01 (section: ****, bin type: BL01)

Capacity check against storage bin 02-02

Packaging specification 8476 determined for storage type 1A02

Level 1 of packaging specification for capacity data was determined

Weight: 4.172 KG are checked

against free capacity 999.999.999.999,999 KG with tolerance 0 KG

Volume: 8.332,80000000000000 CD3 are checked

against free capacity 999.999.999.999,999 CD3 with tolerance 0 CD3

Storage bin 02-02 was found (storage type 2A01)

HU  was checked successfully

  1. Dest. QTY 4.00000000000000 PAL was determined (storage type: 1A02, storage bin:02-02)

Queue determination started with 8GPP/AS40/APS1/    /5A92/B050/B000/STCH

Queue determination number 00001 with X/X/X/X/X

Queue not determined with 8GPP/AS40/APS1/B050/5A92/STCH

Queue determination number 00002 with X/X/X/X/

Queue not determined with 8GPP/AS40/APS1/B050/5A92/

Queue determination number 00003 with X/X/X/ /X

Queue not determined with 8GPP/AS40/APS1/B050/ /STCH

Queue determination number 00004 with X/X/X/ /

Queue not determined with 8GPP/AS40/APS1/B050/    /

Queue determination number 00005 with X/X/ /X/X

Queue not determined with 8GPP/AS40/APS1/    /5A92/STCH

Queue determination number 00006 with X/X/ /X/

Queue not determined with 8GPP/AS40/APS1/    /5A92/

Queue determination number 00007 with X/X/ / /X

Queue not determined with 8GPP/AS40/APS1/    / /STCH

Queue determination number 00008 with X/X/ / /

Queue not determined with 8GPP/AS40/APS1/    / /

Queue determination number 00009 with X/ /X/X/X

Queue not determined with 8GPP/AS40/    /B050/5A92/STCH

Queue determination number 00010 with X/ /X/X/

Queue not determined with 8GPP/AS40/    /B050/5A92/

Queue determination number 00011 with X/ /X/ /X

Queue not determined with 8GPP/AS40/    /B050/ /STCH

Queue determination number 00012 with X/ /X/ /

Queue not determined with 8GPP/AS40/    /B050/ /

Queue determination number 00013 with X/ / /X/X

Queue not determined with 8GPP/AS40/    / /5A92/STCH

Queue determination number 00014 with X/ / /X/

Queue not determined with 8GPP/AS40/    / /5A92/

Queue determination number 00015 with X/ / / /X

Queue determined with 8GPP/AS40/    /    / /STCH

Queue determination number 00001 with X/X/X/X/X

Queue not determined with 8GPP/AS40/APS1/B000/5A92/STCH

Queue determination number 00002 with X/X/X/X/

Queue not determined with 8GPP/AS40/APS1/B000/5A92/

Queue determination number 00003 with X/X/X/ /X

Queue not determined with 8GPP/AS40/APS1/B000/ /STCH

Queue determination number 00004 with X/X/X/ /

Queue not determined with 8GPP/AS40/APS1/B000/    /

Queue determination number 00005 with X/X/ /X/X

Queue not determined with 8GPP/AS40/APS1/    /5A92/STCH

Queue determination number 00006 with X/X/ /X/

Queue not determined with 8GPP/AS40/APS1/    /5A92/

Queue determination number 00007 with X/X/ / /X

Queue not determined with 8GPP/AS40/APS1/    / /STCH

Queue determination number 00008 with X/X/ / /

Queue not determined with 8GPP/AS40/APS1/    / /

Queue determination number 00009 with X/ /X/X/X

Queue not determined with 8GPP/AS40/    /B000/5A92/STCH

Queue determination number 00010 with X/ /X/X/

Queue not determined with 8GPP/AS40/    /B000/5A92/

Queue determination number 00011 with X/ /X/ /X

Queue not determined with 8GPP/AS40/    /B000/ /STCH

Queue determination number 00012 with X/ /X/ /

Queue not determined with 8GPP/AS40/    /B000/ /

Queue determination number 00013 with X/ / /X/X

Queue not determined with 8GPP/AS40/    / /5A92/STCH

Queue determination number 00014 with X/ / /X/

Queue not determined with 8GPP/AS40/    / /5A92/

Queue determination number 00015 with X/ / / /X

Queue determined with 8GPP/AS40/    /    / /STCH

Queue A.INT.FG determined

No workload data is maintained in warehouse number 8GPP

Engineered Labor Standards Calculation

Work Steps for Selection 8GPP AS40 MOVE A:

You have not selected a work step sequence

Warehouse task 1XXXXX created

Warehouse order creation started

Warehouse order XXXX created

former_member183610
Active Contributor
0 Kudos

Hi,

During creation of the WT, one pack spec 8476 is determining for receiving storage type 1A02. go through the packaging specification and observe that , there is no capacity check also.

If you want to get 4 WTs, check and correct the pack spec with specific capacity to create multiple WTs.

C K Reddy