Process order with DLV status are not settled

[ssaher412]

Hello Experts,

We have two process orders which are having DLV status set on 24.11.2024 which falls on P11. We ran the job's for collective order settlement on 25.11.2024. The variances for these two orders were not calculated and in result the orders were not settled. When we ran the collective settlement on 30.11.2024 which falls in P12, these orders were settled. My question here is the DLV status was set in P11 still why system has not calculated or settled the order when we ran the settlement process on 25.11.2024.

Any help will be highly appreciated, Thanks in advanced.

[ssaher412]

Hello Experts,

I have checked these orders, these are actually settled. We have jobs which are being used to run the settlement process. So these orders were delivered on the evening of 24/11/2024 at 17:15:00 and the job for variances were ran on 23/11/2024 at 22:00:00 and after that the actual settlement job was ran on 24/11/2024 at 01:00:00. So my question is if these orders are delivered on evening of 24/11/2024 at 17:15:00 and the settlement job which was ran earlier in the mid-night of 24/11/2024 at 01:00:00 and completed in 10 mins, how this job settled the orders which are not delivered when the job was running.

Thanks in advance.

[Saif_Ali_Sabri]

AI was used to create this answer:

In SAP S/4HANA, the settlement of process orders depends on several factors, including the status of the order (DLV status in your case), the timing of the settlement job, and the settings for when variances are calculated and settled. From the scenario you've described, it seems like there is some confusion regarding the timing of the settlement job and the delivery of the process orders.

Here are some key points to consider in explaining this behavior:

1. Settlement Timing and Order Status (DLV):

   • The DLV status indicates that the order has been delivered, but the system will still wait for the settlement job to run in order to calculate and post variances.
   • The delivery time of 17:15:00 on 24.11.2024 is the time when the goods were physically delivered, but the settlement job doesn't necessarily need to wait for the exact time of delivery. It operates based on the data available at the time of execution, such as goods movement and related costing data.

2. Settlement Job Execution Timing:

   • The settlement job was executed at 01:00:00 on 24.11.2024 (before the delivery time), but it appears that it still managed to settle the orders.
   • The key here is that settlement jobs in SAP can process orders that have already met the required conditions for settlement (such as delivery completed) even if they were executed before the delivery happened. The system likely picked up the orders based on their planned status and delivery completion in the system, not strictly tied to the real-time delivery timestamp.

3. Settlement Period and Variance Calculation:

   • The fact that the orders were not settled when the collective settlement was run on 25.11.2024 (which was still in period P11) and were only settled in period P12 (on 30.11.2024) suggests that the system's variance calculation and settlement process was tied to the fiscal periods (P11 and P12). The process orders were likely flagged as settled in P12, which might have been due to their costing periods being updated or closed in a way that aligned with P12.
   • Settlement jobs can also have a time buffer, which means they can settle orders as long as the necessary data (costs, quantities, etc.) is available at the time of job execution, even if the actual delivery happens after the job execution.

4. Processing Time for Settlement Jobs:

   • The fact that the job ran for only 10 minutes and still processed orders delivered later indicates that the system's processing logic does not rely on the real-time delivery timestamp but rather on data completeness, such as whether the goods movement and costs have been posted in the system correctly by the time the settlement job runs. This is why the settlement job was able to process and settle the orders even though their actual delivery occurred after the settlement job started.

Key Takeaways:

• The settlement job may have processed the orders based on the information available in the system up until the time the job was executed, including any completed deliveries or movements recorded earlier.
• The settlement process considers the order status and accounting data rather than just the delivery timestamp.
• The reason the orders were not settled on 25.11.2024 is likely due to the fiscal period (P11) not having the required variances calculated or finalized, and the system properly settling them in P12 after that data was processed.

[ssaher412]

Hi @Saif_Ali_Sabri the order settlement does not execute till we have DLV or TECO status set for the process order. In my case both these statuses were absent when the order was settled. As per your details I came to know that system can still considered the order if it don't have the DLV or TECO active which I don't feel true. There might be different possibility of considering this order for settlement.

[Saif_Ali_Sabri]

The settlement job can settle orders that were delivered after the job started but before it finished. This is because the system processes transactions in real-time and updates continuously. So, even if the settlement job started at 01:00:00, it would still include orders delivered up until 17:15:00, as long as the job was still running.

[ssaher412]

Hi @Saif_Ali_Sabri the settlement job was not running more than 10 min, it got finished at 01:10:00, still it has settled the orders which were delivered at 17:15:00.