modify inventory transaction applied date

Hello ​@Furkan Zengin 

Why I can’t do a counting if I did an Aggregate?

What processes are affected for this “Aggregate Inventory Transaction per Period”?

Thanks a lot.

Hi ​@TimeMarBou

Say if you aggregate until 31st of January, then you can still post transactions to 31st of January. But if you aggregate until 1st of February then you cannot create a new transaction for January anymore. Because the system validates last aggregation date and block inventory until this date. 

Once you aggregate inventory transactions, ROUNDIFF postings are created (if any rounding is found) and inventory statistic information is updated. They are about 6 table where monthly statistics are recoded.

Aggregate Inventory Transactions per Period

Hope this helps

Hi ​@Furkan Zengin ,

These transactions has been transferred via a background job that is currently scheduled to run every 6 hours in our environment. So, how often should this job work? I’m asking this because if a receipt from last year is cancelled (for any reason), it gets transferred with today’s date. This causes some differences in ‘Receipt not invoiced yet’ report as if this is not received yet, that we present to our auditors. In the report code logic, I see following rule that I don’t understand the rationale behind it;

  IF (cancelled_date_applied_ <= TRUNC(to_date_)) THEN
            show_receipt_ := FALSE;
         ELSE
            show_receipt_ := TRUE;
         END IF;

For this year, the issue doesn’t occur but it will be presented for last year date.

My understanding is that if there is no option to manipulate applied date for transferred transactions, this job might be more appropriate to run once, just before period is closed. So I’m wondering your insights.

Thanks,

If a receipt is cancelled today, then it creates the GRNI voucher rows today as well and it is correct that it is then shown on the Received not yet invoiced report.

Back to the point: if a transaction is included in the aggregation its applied date cannot be changed, because contrary to the popular belief, it’s not only aggregated inventory values that are calculated. 

It’s also the data for the On Hand Develop per Period screen.

From the financial point of view - the rarer you run it the better. This should be the last step of the month end.

However, I would like to ask experienced supply chain / inventory management consultants to share how the On Hand Develop per Period is really used.

Hello ​@uaksoy 

When you cancel a PO, the close date is set to today. UNRCPT transaction also set to today. So there should not be any problem with GRNI report. At the year end, it was in stock, so in the GRNI report and inventory value. When you cancel it today, it will be dropped from GRNI report and  inventory cost will be removed from inventory value. I don’t  think there may be problem with this.

The only problem at month end/year end is closing date of particular receipt. When the user match anything in the new year but do final posting in previous year then GRNI report will still list the purchase order because close date is in the new year, however the balance of M10/M18 will go to 0 in the previous year. 

Therefore, this will create an imbalance in the GRNI report against GL balance. But it has nothing to do with inventory value per period (I’m assuming no price variance on invoice and your inventory has standard costing)

Long story short, your case will not create a balance issue but there are some other cases that are creating issues and must be traced at the month end.

​@piswpl Panie Piotrze, thank you for contribution :)

Regards

​@Furkan Zengin I hope you’re well my friend. :)

I am not sure you can do this “. When the user match anything in the new year but do final posting in previous year then GRNI report will still list the purchase order because close date is in the new year, however the balance of M10/M18 will go to 0 in the previous year. “

It won’t let you do this I’m sure.

​@piswpl Hi again,

I’m doing good, struggling with GRNI in 1300 with 16 years of data set. You know what i mean :D

So lately, I have good experience with all possible errors in the report.

And yes, if the user performs final posting today but set the voucher date any previous day then close date for the receipt is set to today. This is design of the application. 

I created some scripts to find final posting date of the receipt and modify close date on the Receipt window so it matches with GRNI report against GL account.

Test it and you will see 

Cheers

That is 7.5 then.

​@Furkan Zengin Tested. Do you mean that the receipt date is from the previous period and is just matched this month??

Test the following scenario. It is applicable for cloud too.

So the receipt date is 12 April

Final posting date is 12 April

But user performs final posting 14 April

Close date will be set to 14 April, not 12 April. When you generate GRNI for 13 April, you will see it open in the report however when you get balance of M10/M18 it will not present any balance for particular receipt

Furkan, I cannot see any issue in Cloud.

I have just booked an invoice at 1/11/2023 (preliminary and final), receipt was created a month before, October 2023. The last day the GRNI report shows unmatched record is 31/10/2023.

I remember issues with this report in 7.5 and 8 but now it looks correct to me.

Hi ​@piswpl 

I will present it when we meet for a project :)

Dont waste your time for it