3365958 - Unexpected adjustment of Event Based WIP/Variance postings when 'DLV' indicator is set manually

Unexpected adjustment of Event Based WIP/Variance cost occurs when 'DLV' indicator is set manually.

SAP S/4HANA Cloud

User set 'DLV' indicator manually when order is not fully delivered.

Usually, status 'DLV' should be automatically set when final Goods Receipt(GR) post to orders.
For each goods receipt of orders, the posting date of GR will be saved and updated as 'Delivery Date' in backend table(AFPO-LTRMI). 
With the status of DLV indicator set, system will find the 'Delivery Date' and use it as a condition to adjust the Event Based WIP/Variance postings, this is current system logic and it's not going to be changed.

There could be situation that user set the DLV indicator manually and causing unexpected adjustment of event based order postings.

For example, user manually set DLV&TECO indicator for order on date 07/31/2023 on the purpose of closing orders in period 07/2023,
the intended behavior is to reverse event based WIP and post variance in period 07/2023.

However, at that time, order is not fully delivered and the last goods receipt was posted on date 06/26/2023, which updates the 'Delivery Date' as 06/26/2023.
Since DLV status has a higher priority than TECO, with the status of DLV and delivery date as '06/26/2023', system is trying to cancel WIP and post variance in period 06/2023 and not in period 07/2023.

To avoid same issue happen in the future, it's suggested you not to set 'DLV' indicator manually,
if you have requirement to close the order even when GR is not fully delivered, kindly set 'TECO' indicator instead.

 

DLV, TECO, AFPO-LTRMI, AFPO, LTRMI, Delivery Date, Event Based, Event Based WIP, Event Based Variance, Postprocess Event-Based Errors - Product Costing. , KBA , CO-FIO-OBJ-CL-2CL , Closing (Public Cloud) , Problem

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions