Professional Documents
Culture Documents
segments in an
existing chart of
accounts structure?
The chart of accounts structure and structure instance are
fundamental constructs in General Ledger accounting setup and
cannot be altered once they are used. The number of segments, the
segments' order, each segment's label, length, type, and value set
assignment cannot be updated. These components set the
foundation upon which accounting data is recorded for ledgers that
use them. Careful and thoughtful planning must precede all
decisions pertaining to defining the chart of accounts.
9/19/17 | Generic Edit
6. Select File and Save.
9/19/17 | Generic Edit
When the EBS DRM import completes, an output report is generated that
indicates whether the load was successful. If there are errors, there are detailed
instructions for resolving them.
9/19/17 | Generic Edit
Run the request for each value set that must be synchronized.
9/19/17 | Generic Edit
What happens if I upgrade my calendar from Oracle E-Business Suite Release 12?
The migration script assigns a period frequency that most closely matches
your Oracle E-Business Suite Release 12 calendar. When you use the Oracle
Fusion applications Add Year functionality for the first time, you have an
opportunity to review and change the period frequency. The Calendar
Options page opens only for calendars upgraded from Release 12 to allow
one time modification.
Make your changes to the period frequency, adjusting period frequency, and
period name format, including the prefix and separator, as needed. Changes
cannot conflict with the existing upgraded calendar definition. Update the
calendar name and description in the calendar header, as needed, for all
calendars. Period details for a new year are generated automatically based
on the latest calendar options. You can also manually update the calendar.
The modified calendar options affect future years only.
9/19/17 | Generic Edit
What happens when changes are made to an account hierarchy that is referenced in
segment value security rules?
The tree is set from an active to a draft state. The rules referencing the
account hierarchy become ineffective.
After making changes to your hierarchy, you can submit the Process
Account Hierarchies process to automatically run the required steps for
processing account hierarchies updates in one submission, including:
Tree audit
Tree activation
Row flattening
Column flattening
Maintain value set
Maintain account hierarchy
Publish hierarchy
Run the row and column flattening processes for the updated hierarchy
as the flexfield component in the application as well as other hierarchy
processes rely on the flattened hierarchy data to come up with the list of
values available to the user to properly secure the correct account values.
Run the Maintain Value Sets and Maintain Chart of Account Hierarchies
processes, particularly for hierarchy changes to the primary balancing
segment value set if such values are referenced in your primary balancing
segment value based data access sets. These processes update the data
that is required to regulate ledger and data access security by storing:
The period naming format determines the year that is appended to the prefix for
each period in the calendar. For the example, your accounting year has a set of
twelve accounting period with:
Period's date range following the natural calendar month date range.
Calendar period naming format: Select the calendar period format to append the
period's start date's year to the prefix. For the period covering September 1, 2014
to December 31, 2014, then 2014 or just 14, depending on the period format
selected, is appended to each period's name. For the remaining periods covering
January 1, 2015 to August 31, 2015, then 2015 or 15, is appended to each period's
name.
Fiscal period naming format: Select the fiscal period format to always append the
period's year assignment to the prefix. If the accounting periods in the set of
twelve are all assigned the year of 2015, then 2015 or just 15, depending on the
period format selected, is appended to the period name of all 12 periods.
When do I perform row and column flattening for tree versions manually?
Row Flattening and Column Flattening for tree versions need to be manually submitted
under the following scenarios.
If the tree or tree version has any change made to it that would alter the flattened
hierarchy data. For example, adding, moving, and duplicating members. Basically,
anything that impacts the flattened hierarchy data.
If Data Relationship Management (DRM) is used with Oracle Fusion General Ledger,
after running the Load Account Values and Hierarchies process from
the Scheduled Process work area to load chart of accounts reference data from
DRM to Oracle Fusion General Ledger.
When range based hierarchy assignments are supported, if new values are added
that are within the account range assigned to the hierarchy.
Note: In this case, try submitting the flattening programs using the Online Mode first. If the
newly inserted child account value does not appear to be included in the flattened
hierarchy data, then the flattening program has to be submitted using the Force Flattening
Mode, instead of Online Flattening. An issue with the incremental flattening programs can
prevent them from picking up this type of hierarchy change, so full flattening can be
required.
Carefully consider requirements and work with Oracle Support before rebuilding a balances
cube. Use the on-demand programs to rebuild dimension members for each dimension and to
refresh balances to the cubes rather than rebuilding the cube. When you rebuild a cube, the
process rebuilds both the standard and average balances cubes.
To rebuild cubes, run the Create Cubes process. Enter values for the following parameters:
Chart of Accounts
Accounting Calendar
Starting Period
Update an existing calendar before the new periods are needed as future periods, based on
the future period setting in your accounting configuration. If a complete year has been defined
and validated, use the Add Year button to add the next year quickly. Accept or change the new
rows as required. For example, with the Other frequency type calendar, dates may differ from
what the application generates.
When does security take effect on chart of accounts value sets for balances cubes?
For new security policies to be effective, the security policies must be defined before the
account hierarchies are published to the cube. When you create segment value security
rules or change an existing rule that is based on a hierarchical filter, you must republish
the tree version. Use the Publish Account Hierarchies page to republish the tree version
and for the security to become effective.
What happens if I
upgrade my calendar
from Oracle E-
Business Suite Release
12?
The migration script assigns a period frequency that most closely matches your
Oracle E-Business Suite Release 12 calendar. When you use the Oracle Fusion
applications Add Year functionality for the first time, you have an opportunity to
review and change the period frequency. The Calendar Options page opens only
for calendars upgraded from Release 12 to allow one time modification.
Make your changes to the period frequency, adjusting period frequency, and
period name format, including the prefix and separator, as needed. Changes
cannot conflict with the existing upgraded calendar definition. Update the
calendar name and description in the calendar header, as needed, for all
calendars. Period details for a new year are generated automatically based on
the latest calendar options. You can also manually update the calendar. The
modified calendar options affect future years only.