Last updated on JUNE 02, 2016
Applies to:Oracle Assets - Version 12.0.0 and later
Information in this document applies to any platform.
When upgrading from 11i to R12, find loss of functionality in relation to GL PERIOD assignment for journal entries:
Example: Using an annual depreciation calendar in which the period is named JUN-XX (ex JUN-13). This naming convention matches GL naming.
In 11i, all events where booked to the FA period JUN-XX and thus the JE imported into GL with that same period name. In R12, since FA does not send PERIOD NAME to SLA, the customer finds the various annual events are getting mapped to various GL PERIODS instead of the single, expected JUN-XX
FA Annual Dprn Calender
PERIOD JUN-13 = 7/1/12-6/30/13
In 11i ALL transactions in this open period mapped to GL PERIOD JUN-13. In R12, for example, an asset with DPIS of 12/15/2012 gets a GL PERIOD DEC-12 as accounting date = 12/15/2012.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms