Skip to Content

ODO status in condition record: PPF on ODO header not triggered based on HU header change

Hi,

we have a PPF on ODO header which we want to schedule based on ODO header status ‚DPS‘ (given in condition records).

DPS is reached once all HUs have reached the staging step. However, this does not trigger a change on ODO header as header status are not saved on DB (always calculated dynamically). So PPF schedule conditions on ODO header are not evaluated.

Any idea how to trigger the ODO actions here?

Thanks a lot for any help!

Hendrik

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Apr 25 at 11:22 AM

    Hello Hendrik,

    Unfortunately a scheduling condition based on the ODO will not be helpful in this situation. Packing and staging happens without the delivery being in the memory as a business object with all its data. The ODO will only have the status when it is read into the memory and the status is recalculated. This is essential for a good performance in packing and staging but unfortunately there is also the limitation that you cannot react on this status change with your conditions.

    I would recommend to approach the process from another direction. When an HU arrives at the staging area you have the HU and the warehouse task/ order in the memory and the system can make decisions based on them. Maybe it is an option to implement a BAdI that is executed at the warehouse task confirmation (if arriving at storage type... trigger ...)?

    Regards,
    Katrin

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks Katrin. We implemented our own logic now. We schedule a PPF action on HU level in case the HU has reached a status where it is ready to be shipped (packing step completed or staging step reached). This action will trigger PPF determination on delivery header so we will be able to schedule PPF actions based on delivery header status change at this point in time.

      Not sure whether this might kill our performance but we will observe and see how it goes ;-)