When Can We Assign New SLA Definitions
(Doc ID 1634611.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Cost Management - Version 12.1.3 and later
Information in this document applies to any platform.
Qn1:I have defined a new SLA rule in an attempt to break out the COGS by cost element.
We upgraded to R12 at the beginning of 2014 and activity has been occuring in all Ledgers using the seeded SLAM "Standard Accrual'.
In a test instance I copied all definitions (now user) and found that I cannot assign the new Application Accounting Definition (owner = user) to the seeded Standard Accrual SLAM (owner = Oracle).
I found however that if I copied the SLAM itself to create a new HY Standard Accrual (owner = user) then I can assign my new Application Accounting definition to that.
However, the only way I can see to change the SLAM is to go to the Ledger definition and change it. Having not done this before I would like to understand if this is normal and whether the first time any custom SLA rules are created it is expected and safe to update/change the SLAM on the ledger from the accounting set-up manager.
Qn2:What is recommended Oracle best practice, e.g. "just do it anytime", "make sure all users are out of the system and that there are no transactions 'Unprocessed' for SLA? etc.
i.e. Can I just change the SLAM (repoint the ledger to a new one) any day at any time regardless on ongoing user activity in the system?
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