Professional Documents
Culture Documents
Enterprise Structures
Sreeni Devireddy
Platform Technology Solutions
Oracle Development
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted
Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 3
Agenda
1 Enterprise Structures
2 Reporting Structures
3 Ledgers
4 Rapid Setup
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 4
Agenda
1 Enterprise Structures
2 Reporting Structures
3 Ledgers
4 Rapid Start
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 5
Enterprise Structures
Axes
201
200 (US2)
V (Corp)
202
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 15
Reporting Structures
Example
Number of segments
Segment sequence
Segment names Company LoB Account Cost Center Intercompany
Segment prompts
Segment labels
Default values sets
Cost Center
Intercompany
Second Balancing
Default values sets
Number of segments
Segment sequence
Segment names
Company Value Set Account Value Set Company Value Set
Segment labels
Default values sets
Company LoB Account Cost Center Intercompany Company LoB Account Cost Center Intercompany
Company LoB
Account Value Set
Intercompany
• Create (empty) value sets first, then add the sets to your structure / instance and then define the
values for the value set
• Share the same value sets across multiple charts of accounts to facilitate consolidation if the values
are the same and have the same meaning
• You must use independent validation and the data type of character for your chart of accounts value
sets.
• Remember security is enabled at the value set level and applies to all segments that use that value set
• If security rules are applied to the shared value set used for both the company and intercompany
segments, you can experience problems with intercompany values used to record transactions with
balancing segment values outside the values that are use for the legal entities in your ledger
Company LoB
Account Value Set
Intercompany
Company LoB
Account Value Set
Intercompany
Company LoB
Account Value Set
Intercompany
Company LoB
Account Value Set
Intercompany
• Important!
• Always create at least two hierarchy versions before creating any financial reports or
allocations. This will force the fully qualified member name path to be generated and
refers to the full tree name and tree versions. This will minimize report maintenance
if you must add tree versions in the future
• Best Practices (Doc ID 1520970.1)
Account Combinations • Applies at the value set level. If a value set is secured, every
usage of the value set in a segment is secured
Segment Value Security
• Cross Validation Rules whether a value of a particular segment
Cross Validation Rules can be combined with specific values of other segments
• Use cross-validation rules in combination with dynamic
insertion
• Differs from segment validation, which controls the values you
can enter for a particular segment
• Revise cross-validation rules at any time, but remember that
they only prevent the creation of new invalid account
combinations
• Cross-validation rules do not affect existing accounts
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 31
Reporting Structures
Example
201
200 (US2)
V (Corp)
202
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 41
Rapid Implementation for Fusion Financials
Why?
• A way to get customers live in the minimum amount of time
• Capture the absolute minimum amount of data required
• Use the 80/20 rule
• Default the most common options
• Hide complex and advanced set up
• Advanced configurations can be added later where required
• Also applicable for setting up Demos, Test envs., Conference Room Pilots, etc