Hyperion Financial Close Management (FCM) (MOSC)

MOSC Banner

Aging violations...how are they meant to be used?

edited Apr 27, 2017 5:00AM in Hyperion Financial Close Management (FCM) (MOSC) 2 commentsAnswered

We had been looking to use aging violations as a way to find reconciliations that had Transactions after the period's close date (booked into the next period).

For example, for March 2017, we're using April 2 as the End Date for March. We add on a 5 day max age limit for our recs (as our close week is 5 days long, 4/3-4/7).

We were hoping these 5 days would push the "acceptable" Transaction Dates to 4/7. We hoped this would put any Transaction Date of 4/8 and beyond as an aging violation, as they were booked/resolved in the period of April 2017.

However, because Age is defined as (Period End Date - Transaction Date), any date past Period End Date will be negative. And you cannot put a negative value for Maximum Age Limits, it must be positive.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center