Unpaid Payment Batch In One Calendar Prevents Closing Of Period In A Different Calendar
(Doc ID 2394860.1)
Last updated on MARCH 27, 2019
Applies to:Oracle Fusion Incentive Compensation Cloud Service - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Payments
Unpaid payment batch in one calendar prevents closing of period in a different calendar
We have two BUs, each with its own weekly calendar; the period naming scheme is different but the same set of internal period IDs is used for both.
It occasionally happens that we do payments and close out both periods on the same day, and if the payment batch in one BU hasn't been paid, the period in the other BU can't be closed.
For instance, period 201843 in one BU runs from 20-26 April 2018, and period 2017_18_Wk43 in the other BU runs from 23-29 April 2018. Both these periods have period_id 2018043 but are in different calendars. We completed processing in period 2017_18_Wk43 and paid the payment batch, but the period could not be closed because the payment batch in period 201843 in the other BU had not been paid yet. (The error message was: "You must pay all payment batches and change the statuses for all prior periods to closed to close this period, 2017_18_Wk43.") Once we paid the payment batch in the other BU, we could close the period 2017_18_Wk43.
It seems to me that this check should only be applied to periods in the same calendar. Perhaps this is the intention, but the case where multiple calendars use the same period_ids was not considered?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document