Stock sorting "FIFO" (WDATU) during WT creation does not work if stock is in SubHUs

[Mathew_S72]

Hi EWM experts,

did you also observe that stock determination during WT creation does not work correctly (WDATU,VFDAT is not considered) if stock is in SubHUs ?

The FORM qmat_sort likes to sort the CT_QMAT according VFDAT,WDATU,OUTCON,GUID_PARENT which is fine (because this is our sorting rule)

BUT: CT_QMAT-WDATU is empty

... so sorting does not make sense.

But why is WDATU empty for all the available stock ?

It is because the physical stock is in a Sub-HU. From that point on, /SCWM/AQUA-WDATU is empty, only physical stock contains the correct WDATU.

If the physical stock is not in a SubHU, available stock shows the same WDATU as the physical stock and everything works as expected.

How should this ever work, if /SCWM/AQUA-WDATU (VFDAT) is used for sorting but not filled if stock is nested ? Storage type has /SCWM/V_T3010-AVQLVL=space

We would expect that /SCWM/AQUA-WDATU(VFDAT) behaves equally as "addition to stock" during packing of nested HUs, meaning /SCWM/AQUA-WDATU shows (oldest/newest) or rejects nesting (packing) according to /SCWM/V_T3010-MIXGR

Any ideas would be appreciated 🙂

Thanks & best regards,
  Matthias

Typical stock looks like this .. stock identifying fields are equal so we have only 1 AQUA, just different GR dates for each physical stock in SubHUs

available stock is this

[Mathew_S72 · Accepted solution]

🙂it was caused by an SAP EWM error in FM /SCWM/AQUA_DATA_DETERMINE

SNOTE https://me.sap.com/notes/0003127733 (and dependent one's) will fix it.

Be aware that storage type /SCWM/V_T3010-MIXGR is space by default, which means "most recent date dominates". This is an unlucky default for real life, as it makes old stock to new stock, if you just put another Sub-HU (with newer WDATU) to same Top-HU containing already a Sub-HU with older stock.

Better use /SCWM/V_T3010-MIXGR=2 to ensure that /SCWM/AQUA geds WDATU+VFDAT from the oldest physical stock