Hi there
Our month end processing is held up by the time it takes to process the Transfer Work Task - Reposting Transactions option each month.
The vast majority of these transactions never go to Finally Posted status.
Can someone please explain the benefits of running this process and is it mandatory that the process be ran as it seems to be a very time-consuming option.
On the other hand, what’s the effect of not running this transfer.
Thanks
Alan
We are on version 24R1. We have a nightly scheduled job to run the transfer job. So not sure if same for you but found it frustrating at month end as it was preventing us from closing as well. IFS identified an object property you can update so then it’s just a “Warning” at month end vs hard stop. (which is how apps9 worked for us). We track time on work tasks but have it going in & out of the same gl account as we do not need Financial reporting on this time entry. So yes, not ideal to force us to post to the GL in order to use the functionality but it is what it is. I didn’t find a way around this. This is our work around then. We are using 60 days grace period: Test in your environment as to what works best but hope this helps!
Hi
Thank you for your response, its much appreciated!
Currently, we don’t have the process setup as a scheduled job.
Your point as regards month-end closing is well noted as this is a real issue for our Finance team as this process certainly slows down their closing, causing much frustration.
So, in your screenshot by setting the Object LU Maintenance to have a 60-day retention period does this then produce a Warning in the Validate Transactions in Progress process rather than an Error and Hard Stop?
We are on APPS10 UPD27
The information that you have provide so far has been really helpful
Thanks
Alan
Correct, having that setting will post a Warning vs an ERROR in month end close depending on how many days you give it. Therefore those transactions would just post to the next open month vs that current month. If you don’t care which month the time transactions post to, then warning should be sufficient but you should confirm with the Finance staff if that’s acceptable and test it for your version. We don’t track time as a financial impact therefore do not care which month it posts to as it’s just going to a clearing account and being netted against each other in T1/T2 . We care more about tracking the hours against the functional object id side of things.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
