文本案例成果implementing-general ledger

1、Oracle Fusion General LedgerRelease 11(R11) General Accounting DashboardSnapshot of key balances and period close activitiesDrill down to transaction screens and reportsKey Product Features: General LedgerInfolets:Close CalendarOpen SubledgersAP and AR Reconciliation pany ReconciliationJournals and

2、I/C TransactionsRevenues and ExpensesAllocationsKey Product Features: General LedgerExtensive spreadsheets for entering journals and correcting journal import errors, Multi-currency journalsJournal copyRobust, wizard-like allocations with Calculation ManagerRecurring Journals/Allocations across peri

3、ods and across ledgers pany allocations to allocate balances across ledgersJournal Approval that leverages AMX (Approvals Management Extension)JournalsTranslation, revaluations, and currency conversionSpreadsheet-based currency rates upload (daily and historical rates)Support for multiple accounting

4、 representations (i.e., IFRS and local rules)Multi-Currency & Multi-GAAPCollaborate with colleagues about specific journals, reports, and period close activitiesWatch this video about Oracle Social Network integration in Fusion Financial Applications (2 mins)Collaboration (OSN)Key Product Features :

5、 General Ledger (continued)Flexible chart of accounts (up to 30 segments)Multiple balancing segments (up to 3)Segment value security to prevent certain users from viewing certain sensitive account balancesDate-effective hierarchies (trees)Multi-dimensional reporting and analysis on live dataSelf-ser

6、vice access to reports from Financial Reporting Center Mobile Financial Reporting CenterSunburst Visualization Tool for Reporting and AnalysisAccount Monitor to track anomalies in account balances in real-timeFR for board-room ready financial reportsSmartView for interactive, ad hoc reporting and an

7、alysis within a spreadsheet Reporting & AnalysisWatch this video about SmartView (2 mins)Watch this video about the Financial Reporting Center (3 mins)Key Product Features : General Ledger (continued)Centralized Close Monitor to monitor the close status of subledgers and ledgers Watch this video abo

8、ut the Close Monitor (2 mins)Reconciliation reports to reconcile AP and AR with GL with drill downs to underlying transactionsDrill down capability from target ledger balances to source ledgers if balances were transferred(Cloud Implementations) Integration with Oracle Hyperion Planning and Budgetin

9、g Cloud Service(Non-Cloud Implementations) Integration with Oracle EPM (i.e., Hyperion Planning and Budgeting, Hyperion Financial Close Management, Hyperion Disclosure Management)Period CloseKey Product Features: General Ledger (continued)Close MonitorKey Product Features: General Ledger Centralized

10、 setup using Functional Setup ManagerFile-based spreadsheet loaders for upload /maintenance of segment values and hierarchiesMigration of setup data across instances (i.e., test and production)Rapid Implementation Spreadsheets to create the following:SetupMultiple legal entitiesMultiple ledgers (one

11、 per country)Multiple business unitsAccounting CalendarAccount Defaulting to Other Setup UIsDocument and Journal SequencingAccount CombinationsCross-Validation RulesKey Product Features: General Ledger(R11) Enterprise Structures Setup Report to validate your configurationThis is especially useful af

12、ter uploading your enterprise structure using the Rapid Implementation spreadsheetDiagnostic tests to perform health check and data validation on the following : SetupChart of Accounts Value Sets and Values Account Hierarchies Versions Accounting Calendars Legal Entities and Legal Reporting Units Le

13、dgers SetupDocument and Journal Sequences (includes Accounting and Reporting SequencesKey Product Features: Diagnostic DashboardKey Setup Tasks: Rapid Implementation for Financials Task ListKey Setup Tasks: Financials Setup TasksImplementation ConsiderationsAlways create a few extra periods in advan

14、ce of the initial period. You cannot change the calendar later.Foreign currency translation cannot be performed in the initial period opened for your ledger. Consider defining a complete prior year. Do not change the name of the period after you have opened the period.Accounting CalendarYou must fir

15、st define a balance level reporting currency BEFORE you run translation in the target currency.Currency TranslationBest practice is to always use the ADFdi spreadsheet “Create Budgets by Spreadsheet” task in the GAM Dashboard.The following are ignored for Budget Upload to the Essbase Cube:Cross Vali

16、dation RulesSegment Value Security RulesData Access Set SecurityNote: Only Budget Scenario Security is followedBudget UploadImplementation ConsiderationsMust create your value sets then COA structure and instance before assigning values to the value sets.You must deploy your chart of accounts before

17、 use.If enabling segment value security, users will not be able to use the values until you explicitly grant them access.If you want segment value security to apply for reports, you should consider using the reporting hierarchy that has been published to Essbase Cubes. You may need 2 different hiera

18、rchies: One for Reporting users & another for data entry folks.In setup UIs, if Segment Value Security is enabled, you will see account combinations with those secured values but if you try to update the field, you wont be able to use those secured values.For transaction and reporting UIs, if Segmen

19、t Value Security is enabled, you will NOT be able to view and use the secured values.If using a Company and pany Segment that share the same values, segment value security rules apply at the value set level. So if you want to secure access to company values, best practice is to NOT share the same va

20、lue set for both segments.Use the validation type of “Independent “or “Table Validated” with the Data Type of “Character” and Subtype of “Text.” Have a one to one mapping between a chart of accounts structure and instance. In other words, do not have multiple instances associated with the same struc

21、ture. Chart of AccountsImplementation Consideration Hierarchies Foundation of ReportingImplementation Considerations: HierarchiesCarefully consider different hierarchy requirements for reporting, allocations, cross validation rules, revaluations, and chart of accounts mapping. You should use a diffe

22、rent hierarchy for reporting & analysis and allocations.Hierarchies used for reporting & analysis and allocations cannot have the same child value rolling up to 2 different parents. When using hierarchies for reporting and allocations, you must publish them to create the Essbase cubes.Always create

23、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.Non-reporti

24、ng and non-allocation hierarchies CAN have the same child rolling up to multiple parents. Hierarchies used for cross validations, revaluations, segment value security, and chart of accounts mapping have to be defined within the SAME hierarchy. The hierarchy must then be associated with a chart of ac

25、counts instance. You can only associate one hierarchy with a chart of accounts instance, per segment. It is best practice to create a top-most root node (Level 0) unless the hierarchy is used for cross validations, revaluations, or chart of accounts mapping. For the latter, you need at least three l

26、evel 0 nodes for easy selection.Hierarchies (Trees)Implementation Considerations: HierarchiesManually submit the Process Account Hierarchies under the following scenarios:When a new tree or tree version is defined.If the tree or tree version has changes that would alter the flattened hierarchy data,

27、 such as adding, moving, or duplicating members, or anything that impacts the flattened hierarchy data.If Data Relationship Manager (DRM) is used with Fusion GL, after running the Load Account Values and Hierarchies (LoadMasterData) program from ESS to load chart of accounts reference data from DRM

28、to Fusion GL.If new COA values are added that are within the account range assigned to the hierarchy. Process Account Hierarchies (New in R9) automatically run the following processTree Audit and Tree ActivationTree Row FlatteningTree Column FlatenningMaintain Value SetsMaintain Account HierarchiesP

29、ublish Hierarchies (you can choose not to run this process)Process Account Hierarchies for any hierarchy changesImplementation Considerations: Segment Value SecurityDo I need segment value security?Implement segment value security if you need to control access to parent and detail values across any

30、chart of accounts segment across all financial applications.Is it different from data access set security?Data access set security controls access to ledgers and primary balancing segment values only in Fusion General Ledger. We mend using data access security to secure your primary balancing segmen

31、t values, and segment value security to secure all other segment values.How is it different from cross validation rules?Cross-validation rules only prevent the creation of new account combinations in case the underlying segment values violate the validation rules you specify. Segment value security

32、controls the access to the values of each chart of accounts segment, irrespective of the values in other segments.Implementation Considerations: Segment Value SecuritySegment value security is enforced in Oracle Fusion Applications wherever the charts of accounts values are used.When entering journa

33、lsYou can only use account values for which the access is granted using segment security rules. When running reports or performing inquiry against a ledgerYou can only view financial data for accounts for which the access is granted using segment security rules. When viewing setup objectsIf accounts

34、 specified in the setup include references to an account with values you have not been granted access to, you can see the account but will not be able to use that secured value if you select to modify the setup.Implementation Considerations: Segment Value SecuritySegment value security is enabled at

35、 the value set level and will affect all chart of accounts that reference that value set.Securing a value set denies access to all values by default. Users that need to access values will need to be specifically granted access.When enabling or disabling segment value security for a value set, you ne

36、ed to re-deploy your key accounting flexfield.Implementation Considerations: Segment Value SecurityCreate custom external roles for the purpose of grouping segment value security rules to be assigned to one or more users. Plan for the number of segment value security external roles you need to repre

37、sent unique segment value security profiles across your users. You can assign multiple security rules related to a particular segment value security profile to the same segment value security role (Think of these roles as SVS rule sets) Create these roles ahead of defining the segment value security

38、 rules so that the roles are available. Assign the rules to roles once you have defined them to create a complete data security policy.Assign a segment value security role to the users that require that particular SVS data security profileSegment Value Security Rules Operators21You may use any of th

39、e following operators in your conditions to secure your segment values:OperatorUsageEqual toSecures a specific detail value. You cannot use this operator to secure a parent value.Not equal toSecures all detail values except one that you specify. You cannot use this operator to secure a parent value.

40、 BetweenSecures a range of detail values. Is descendant ofSecures the parent value itself and all of its descendants, including mid-level parents and detail values. To use this tree operator, you must specify an account hierarchy (tree) and a tree version. However, the security rules apply across al

41、l tree versions of the specified hierarchy, as well as all hierarchies associated with the value set.Is last descendant ofSecures the last descendants (i.e. the detail values) of a parent value. To use this tree operator, you must specify an account hierarchy (tree) and a tree version. However, the

42、security rules apply across all tree versions of the specified hierarchy, as well as all hierarchies associated with the value set.Segment Value Security Rules with HierarchiesSegment value security rules must be defined before account hierarchies are published to cube to be effective.For changes wi

43、th hierarchical segment value security rules, or changes in a referenced hierarchy, republish the tree versions affected by the rule change for rules to be effective in the cube.Multiple processes need to be run for hierarchy changes, including auditing, activating, row and column flattening. For ch

44、anges to the primary balancing segment hierarchy, you also need to run the value set and hierarchies maintenance programs to ensure effective security enforcement.You can submit the Process Account Hierarchies program to automatically run these account hierarchies related processes in one submission

45、. Implementation ConsiderationsSubmit the Publish Chart of Accounts Dimension Members and Hierarchies program to update the balances cube for chart of accounts value set and hierarchy changes. If you did NOT make changes to the hierarchy assigned to a value set, select YES to Publish Detail Values O

46、nly. Publishing Dimension Members and Hierarchies to the Balances CubeSegment Value vs. Data Access Set SecuritySegment value security rules assigned to the user via his various roles that reference the same secured value set are always in effect simultaneouslyData access set security can be a littl

47、e different depending whether working with those General Ledger features that are based directly on the balances cube versus those that are not. User can be assigned multiple data access sets referencing the same balances cube.When working on features not directly related to the balances cube, the s

48、pecific ledger and primary balancing segment values access as defined in the users selected data access set will apply.When working directly with the balances cube, the cumulative effect of the users combined data access sets for that cube will be enforced. User will simultaneously have access to th

49、e sum of all primary balancing segment values for all ledgers granted to him via his combined data access sets when working with the balances cube.Trouble ShootingIssuePossible ResolutionCOA Deployment ErrorRe-run the deployment process and expand the progress details window to determine the point o

50、f failure. Ensure the required qualifiers (primary balancing and natural account segments) are defined. Make sure the tree that has been assigned to a value set referenced in a COA structure instance is ACTIVE. In order for the deployment process to proceed, at least one active version must be set f

51、or the tree. Make sure all chart of accounts instance definitions are completely defined.Tree Version Audit Process Fails When Activating VersionMake sure parent values have the summary attribute set correctly.Make sure you did NOT mistakenly assign children to child values. Fix could be as simple a

52、s switching the summary attribute flag. However, if you mistakenly made a parent value a child value and posted transactions to that account then a more intensive data fix may be required. Tree Hierarchy Defined in Fusion GL is Not Available in Essbase GL Balances CubesSubmit the process to propagat

53、e and update required account hierarchies to the Essbase GL balances cube from the Publish Account Hierarchies page.Check that the Publish option is enabled for the versions that are to be published.Check that a Request ID is returned and the process completes successfully after clicking the Publish

54、 action button.Trouble Shooting (continued)IssuePossible ResolutionError in Publish Account Hierarchies or Publish Chart of Accounts Dimension Members and Hierarchies programsMake sure all users sign out of Financial Reporting, Smart View, and Calculation Manager during the submission of the publish

55、 process. You cannot have users connecting to the cube while running these programs.Enabled or disabled flexfield security policies are not in effect for Essbase GL balances cubeEnabled or disabled flexfield security policies are not automatically applied to the Essbase cube if these were set after the cube was created. Account hierarchies must be republished in order to apply newly enabled or disabled flexfield security policies.Note: Flexfiel