All existing configs available in Gebindekonfiguration in PP_Order

[metas-dh]

Is this a bug or feature request?

Bug?

What is the current behavior?

When creating a PP_Order for Convenience Salad, and you check field for Gebindekonfiguration, you can select all existing Gebindekonfigs, for all products.

Which are the steps to reproduce?

1. Create a PP_Order for Convenience Salat
2. In field Gebindekonfiguration, start writing sth: => all existing Gebindekonfigs that were used before (e.g. in material receipt), for different products, are selectable, including LU (see pic)

What is the expected or desired behavior?

Only the existing ones available for Convenience Salat shall be selectable?Including LU?

[metas-dh]

Results of IT1 tested in e2e

Gebindekonfiguration in PP_Order

• if PP_Order was created automatically by Material Dispo, then the packing item from sales order is set: OK
• not all existing Gebindekonfigs that were already used are selectable: OK
• the Gebindekonfigs already used for the product that shall be produced are selectable => if i have the product received in an earlier PP_Order, with:
  • No Packing Item, qty: 20,
  • No Packing Item, qty: 10
  • No Packing Item, qty: 10
  • 1 LU with 2 IFCO 6410 x 10 Stk, then these are all selectable as Gebindekonfig for the new PP_Order; shouldn't the Gebindekonfiguration selectable be the one(s) set for the product, in M_HU_PI_Item_Product? @metas-mk @teosarca wdyt?

[metas-dh]

=> checked with metas-mk: NOK:

• No Packing Item shall be selectable as Gebindekonfig, but not with a certain qty, just in general
• same for IFCO 6410: shall be selectable as in normal Gebindekonfig in TU-CU Allocation set in Product (so if you order Qty: 100, the Gebindekonfig would be 10 IFCO 6410 x 10 Stk)

[metas-rc]

Notes for IT

• I changed the validation to only show the LUTU Configs that respect the qty from the PPOrder
• I cannot provide the No Packing Item as Gebindeconfig with no certain quantity, because all the quantities are mandatory in the M_HU_LUTU_Configuration table => I wouldn't be able to bring up one with no qty
• Also, there is no way of manually creating newLUTU Configs, so for now we must rely on the ones that already exist.

Please, check again with Mark and see if we need a followup to make it possible to have the features above.

[metas-dh]

checked with metas-mk: M_HU_LUTU_Configuration table shall not be used for this, since you cannot change it and the configs only appear when HUs are created (and therefore it all depends on already existing HUs instead of the CU-TU Config of the product); @metas-rc pls ping metas-mk for infos on how to procede further