Volume_54.2_-_FCCS_Implementation_Best_Practices.pdf

Oracle FCCS best Practice

1. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
1
Shailesh Kumar
Senior Director, EPM Cloud Development
September,2019
Whatyouneedtoknow
before starting an
FCCS implementation
(as the applicationowner)
Public

2. Outline
1.Financial Consolidation and Close Service
2.Understanding Requirements and Design
3.Implementation Best Practices
4.What to watch when writing Custom Calculations?
5.FAQs
6.Consolidation Performance and Diagnostics
7.Understand Monitoring
8.Tutorials
2

3. Evolution of Hyperion Consolidation and Close Solutions
to EPM Cloud
3
Micro Control
Hyperion
Enterprise
Hyperion
Financial
Management
EPM Cloud:
Financial Close
30+ years of experience and best practices allow us to constantly improve and evolve
Financial Data
Management
Financial
Close
Management
Hyperion Tax
Provisioning

4. Key design principles of Financial Close on EPM Cloud
Pre built functionality and out box of content
•Configurations v/s Customizations
•Based off 30+ years of consolidation experience
•Best practices from HFM, Enterprise and practical experience
Holistic approach to Record to Report process that includes
•Consolidations
•Close orchestration
•Supplemental/Ad hoc data collection
•Heavy emphasis on collaborative reporting (dashboards, reports, Office, etc)
Powered by EPM Cloud platform
•Developed for SaaS
•Process driven navigation
•Innovations driven across the platform with a single learning curve (IPA, Chatbots, Machine
Learning)

5. FCCS -Consolidation Capabilities
All major HFM capabilities are now covered
Currency Translation Adjustment
Copy & Clear
Data Lock/Unlock
Configurable Calculations
Configurable Translations
Advanced Consolidations
Ownership Management
Journals –Auto reversing, Attachments, Recurring, Templates
Configurable Consolidation Rules
Extended Dimensionality(Fall ‘18)
Process Mgmt(EOY ‘18)
5

6. FCCS –Beyond Consolidations
Covering all aspects of Financial Close
Supplemental Data Collection
Close Monitoring and Orchestration
Data Management
Integrated Business Processes
Intelligent Process Automation
Autonomous Consolidation
Infolets
Machine Learning (Coming soon)
Mobile and Chatbots(EOY ‘18)
6

7. Focused on Best Practices from 30+ years
experience
Extended close from sub-ledger to final
reporting
Integration with ERP, EPM, & 3
rd
party sources
Consolidate and Report with Confidence
Financial Consolidation and Close
7Copyright © 2016,Oracle and/or its affiliates. All rights reserved. |
Best Practice
Consolidations
Supplemental
data
Workflow Dashboard
Data
Management

8. Understand Requirements andDesign
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 8

9. Follow these Keys toSuccess
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 9
•Know your company’sexpectations.
–Understand the process that needs to besupported.
•Ensure that you understand the measures ofsuccess.
–Keep in mind the entire close process beyond just consolidations.
–Know requirements for DataLoad/Entry performance and consolidation performance.
–Know the granularity of dimension members
•Design the application to meet thoseexpectations.

10. Know Your CurrentProcess
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 10
•Analyze the currentprocesses.
–Understanding the sources of information and thebusiness
•Confirm whether all organizations (such as divisions or businessunits)
follow the business process that youidentified.
–If the process differs between organizations, determine if you want to keep the
current process or adopt a newprocess.
–If you are implementing different solutions for certain organizations, identify the
differences and the organizations to which theyapply.

11. Consolidation and Close Requirements
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 11
Analyze the current processes and determinerequirements.
•Develop a plan to ensure that you have a defined set ofrequirements.
–Without a plan, implementation time could increase, and the model may not
properly reflect businessrequirements.
•Look at what is working and improve the areas that arenot
•What area of the close needs to be optimized? What areas need additional
visibility?
•Do not simply take an existing process and wrap a new tool aroundit.
•If the customer is moving from HFM or other consolidation application
things would be done differently in FCCS, so set that expectation correctly.

12. Consolidation and Close Requirements (continued)
•What tasks do you do during close and who does them?
•Check your close calendar
•Where does the data come from?
•Data feeds from General Ledgers
•Data input via Forms, Journals, or SmartView
•How often is data loaded/entered during the close process?
•Who is the consumer of the data?
•What are the expected Reports?

13. Look at Application Design
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 13
Design your application based on the requirements and understanding
of the current/desired process.
•What capabilities do you want enabled?
•Review the application creation options
•Is supplemental data collection required?
•Is this a multi-currency application?
•Do you need workflow for Journals enabled?
•Etc.
•What dimensionality is requirement for the consolidation reporting?
•Review the existing out of box dimensions and add custom dimensions
•How much historic data do you want to bring into the application?

14. Look at ConsolidationConsiderations (continued)
•Determine if you need to utilize any of the advanced consolidation
features
•Determine the consolidation control method that is applicable
•Determine if you require to use custom calculation rules via insertion
points within local currency, consolidation and/or translation rules.
•Will you utilize advanced organization management capabilities?

15. Understand Your ReportingRequirements
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 15
•Most of the time, reports are the primary objective of theapplication.
–Ensure that the application/dimension design can meet the majority of your
reportingneeds
–FCCS has reports beyond just financial reports, it includes intercompany,
journals, close monitoring and supplemental data collection.
•Review report formats and consider the dimensionsinvolvedfor financial
reports
–Understanding the dimensions on reports will help you configure your application.
For example, look at whether reports are done by custom dimensions or standard
out of box dimensions like year, account, or entity etc.
–Identify all of the requireddimensions.

16. Understand these Key Aspects of ApplicationDesign
•Balance the needs of end users with scalability and the performance requirementsfor
theapplication.
•Meet the needs of reporting requirements of end users whilemeetingapplication
requirements for scalability andperformance.For instance, additional dimension
members or shared hierarchies will impact consolidation performance
Reporting
Requirements of endusers
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 16
Scalability/Performance
Requirements ofApplication

17. Dimensionality Options and UseCases
1
2
3
Standard (mandatory)dimensions
Custom and optionaldimensions
Attribute dimensions forreporting
Use the standard out of box dimensionality and reorder/apply aliases as
needed.
Extend dimensionality with custom/optional dimensions that can beadded
(enabled) or renamed per yourrequirements.
Useful to meet reporting requirements. The relationship between the
dimensions doesn’t change withtime.
5
Multiple hierarchies in adimension
Combine two or more unrelated dimensions into a single dimension to avoid
interdimensionalirrelevance.
4
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 20
Alternate Hierarchies
Use alternate hierarchies when the same members can be grouped under
different parents for top down allocation or reportingpurposes.

18. HFM to FCCS
•Access to methodology and tool
are published.
•HFM to EPM Cloudsolution

19. Implementation Best Practices
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 19

20. Metadata Validation
•Follow up on errors and warnings
•On Demand validation report
•Validation in Simplified UI Dimension Editor

21. Shared Hierarchies
•Shared hierarchies are used to meet reporting needs
•The number of shared hierarchies effects performance
•Top member of alternate hierarchies must have consol
operator as Ignore
•Entity Dimension
•Partial Shares
•Data is copied between members
•Increases the database size and consolidation times
•Other Dimensions
•Data Storage type: Shared
•Shared members have to be after non-shared in hierarchy. Number of shared
hierarchies have an effect on both consolidation and database refresh time.

22. Currencies
•Input Currencies
•Reporting Currencies
•Database Refresh Impact
•Number of currencies have an effect on database refresh time
•Post Process Rates Cube copies the currencies from the Rates cube to the
Consolidation cube

23. Member Formulas
•Level 0 Members Only
•Avoid member formulas on custom dimensions
•Unless required for reporting
•Two Pass Calculations
•Recommended to be used on account dimension only.
Confidential –Oracle Internal/Restricted/Highly
Restricted
23

24. Custom Calculations
•Limit Calculation Scope
•Limit the scope of the calculation using a FIX statement
Confidential –Oracle Internal/Restricted/Highly
Restricted
24

25. Custom Dimensions
•Parent members never share
•Shared members are limited to level 0 members only.
Confidential –Oracle Internal/Restricted/Highly
Restricted
25

26. Loading Data
•Both YTD and Periodic are supported
•YTD overhead since FCCS needs to calculate the periodic amounts
•No zero values
•Do not load zero values
•Ability to load in replace mode for both YTD and Periodic
Confidential –Oracle Internal/Restricted/Highly
Restricted
26

27. Movement Dimension
•Can I create member formulas in the movement dimension
•While you “can” create member formulas for movement dimension members it is
not recommended. It will have a significant impact on consolidation performance.
•Creating Alternate Hierarchies
•Alternate hierarchies are allowed outside Closing Balance but they should roll up to
Total Movements
•The consolidate operator should be ignore otherwise you will get duplicate values

28. Cash Flow –Metadata 1/2
•Movements
•Add primary movements under Movements Subtotal with addition consolidation
operator
•Under FCCS_Cashflowadd Cashflowline items where needed
•Each First level Cashflow_ member will have one or more Mvmtsas children
•Add Mvmts_ members as shared members with subtraction consolidation
operator
•Cash Change hierarchy is not modifiable.

29. Cash Flow –Meta Data 2/2
•Accounts
•Cash flow reported at FCCS_TotalBalance Sheet –
Cash and NonCashaccount
•Do not use any other balance sheet member
to report on cash flow
•Any non FCCS_ direct children added to either
current assets or total assets must be added
under FCCS_TotalNon Cash or FCCS_TotalCash
as appropriate. Additionally, any additional
siblings to Total Liabilitites, Total Assets and Total
Equity must be added to the Cash and NonCash
hierarchy as appropriate.
•NOTE: FCCS_Balancewill not be correct if there
are siblings to Total Liabilities and Total Equities
Confidential –Oracle Internal/Restricted/Highly Restricted29

30. Cash Flow –Overdraft Treatment
•Overdraft accounts added to Current Liabilities
•Overdraft accounts backed out of NonCash
•Overdraft accounts included in Total Cash
Cash Flow analysis/Reporting
Confidential –Oracle Internal/Restricted/Highly Restricted30

31. What is Currency Translation Adjustment (CTA)
•Application setting to use either CTA (Balance Sheet Treatment) or CICTA
(Comprehensive Income Treatment)
•Default is CTA
•CTA reflects the unrealized gains or losses due to foreign exchange
fluctuation over the years in foreign subsidiaries
•Why does this happen
•Certain balance sheet activity is required to be reported at historical rates
•They are not translated using the end of the month rate as other balance sheet
accounts are
•Balance sheets must be balanced when reported. Balanced means Total Assets =
Total Liabilities + Total Equity
•The Foreign Exchange on the historical accounts are transferred to the CTA account
Confidential –Oracle Internal/Restricted/Highly Restricted31

32. Where is Currency Translation Adjustment
•Currency Translation Adjustment will generally either reside in
either:
•Balance Sheet as part of Total Equity
•Balance Sheet as part of Total Comprehensive Income in Other Reserves
•Certain Reporting Standards Require different placements
•USGAAP requires the Balance Sheet Treatment
•IFRS requires the Total Comprehensive Income
Confidential –Oracle Internal/Restricted/Highly Restricted32

33. How is CTA Calculated
•For Historical Accounts the FX is transferred to the CTA/CICTA account
•FX Calculations
•FCCS_FX_Opening
•Calculated
•Untranslated Opening Balance Total * Ending Rate –Translated Opening
Balance Total
•FCCS_FX_Movement
•Untranslated FCCS_Mvmts_Subtotal* Ending Rate –Translated
FCCS_Mvmts_Subtotal
•FCCS_Mvmts_FX_to_CTA
•Transfer of FX calculations for historical accounts to the CTA account on the
balance sheet or to CICTA in Total Comprehensive Income
Confidential –Oracle Internal/Restricted/Highly Restricted33

34. Custom Calculations
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 34

35. Consolidation Process
Consolidation Process divided
into 3 stages. Each tab displays
the calculation process within
each stage:
Calculate local currency
data
Process all translated
(parent currency) data
Perform eliminations and
consolidate

36. System vs. Custom Calculations
System Calculation
Auto-calc by system
Allow override if applicable
Custom Calculation
Pre-defined insertion point
Optional

37. Member Formulas vs. Insertion Rules
Member Formula
•Defined on dimension member
•Simple calculation with no dependencies
•No cross-dimensional reference
•Perfect for ratios as example
•Dynamic calculation during data retrieval
•Commonly used on Account or Custom
•Not recommended on Movement due to Performance

38. Member Formulas vs. Insertion Rules
Insertion Rules
•Execute at defined point of Consolidation Process
•Set of formulas and equations run in sequence
•Control calculation on subset of data vs entire database
•Support complex calculations
•Cross dimensional references
•Use CalcMgras script editor
•Member / Function selector support
•Syntax checker / member validation

39. Insertion Rules –Essbase CalcScript
Essbase Functions
•Support most functions / added new ones in 18.06
•Updated listing per Admin Guide
•Additional functions if needed (TBD)
FCCS Restriction
•FIX dimension not allowed
•Scenario / Year / Period / Entity /View
•System members not allowed in FIX
•Restricted members not allowed as Target

40. FCCS Restricted System Members
Dimension Member Expression
LeftHand
Side
RightHand
Side
Scenario AllMembers No Yes
Year AllMembers No Yes
Period AllMembers No Yes
View AllMembers No Yes
Entity AllMembers No Yes
DataSource FCCS_IntercompanyEliminationsNo Yes
FCCS_JournalInput No Yes
FCCS_SupplementalData No Yes
FCCS_SystemTypes No Yes
FCCS_RateOverride No Yes
FCCS_AccountOverride No Yes
FCCS_PCON No Yes
FCCS_DriverSource No Yes
FCCS_SourceEntities No Yes
Movement FCCS_OpeningBalance No Yes
FCCS_OpeningBalance_Cash No Yes
FCCS_FX_Total_NonCash No Yes
FCCS_ClosingBalanceCash No Yes
System members restricted
•As Destination of calculation
(LHS)
•Members restricted on LHS are
also restricted from the FIX
statement
Consolidation and Currency
dimension
•Specific member restriction is
based on Insertion Rule

41. FCCS Restricted System Members
Dimension Member Expression
LeftHandSideRightHandSide
Account FCCS_CSTATUS No Yes
FCCS_CSTATUSFILTER No Yes
FXRates–Ending No Yes
FXRates–Average No Yes
AverageRate No Yes
EndingRate No Yes
SrcAverageRate No Yes
TgtAverageRate No Yes
SrcEndingRate No Yes
TgtEndingRate No Yes
FCCS_Balance No Yes
FCCS_CTA No Yes
FCCS_CICTA No Yes
FCCS_PercentControl No Yes
FCCS_CurrentRatio No Yes
FCCS_QuickRatio No Yes
FCCS_CashRatio No Yes
FCCS_InventoryTurnover No Yes
FCCS_AssetTurnover No Yes
FCCS_DaysSalesInReceivables No Yes
FCCS_DaysSalesinInventory No Yes
FCCS_GrossProfitMargin No Yes
FCCS_ReturnOnSales No Yes
FCCS_ReturnOnEquity No Yes
FCCS_DebtToEquityRatio No Yes
FCCS_DebtRatio No Yes
FCCS_OpeningBalance_Cash No Yes
FCCS_FX_Total_NonCash No Yes
FCCS_ClosingBalanceCash No Yes
Validation error
when restricted
members are used
as destination or FIX

42. Common EssbaseFunctions
FIX / ENDIFX -control scope
Calculation Member Block
Member Set
•@LIST, @REMOVE, @RELATIVE, @CURRMBR
•@CHILDREN, @DESCENDANTS, @SIBLINGS
Conditional and Logical Operators
•IF .. ENDIF , < > ,= , AND, OR, NOT
Boolean
•@ISMBR , @ISUDA, @ISACCTYPE, @SCHILD, @ISLEV, @ISANCEST
Relationship
•@GEN, @LEV, @CURGEN, @CURLEV
Mathematical
•@ABS, @SUM, @VAR, @ROUND, @MAX, + -* /

43. Common Syntax
Semicolon
•Required at end of each statement
•Example: Sales = Sales * 1.50 ;
•Not needed after FIX and ENDFIX
Double Quotes
•Member names with spaces / special characters / start with number
•Best practice to always use double quotes around member name
•Example: “Cash Ratio” = “Cash” / “Current Liabilities” ;
Cross-dimensional Operator
•Use -> to specify intersection of more than one dimension
•Example: “Sales”->”Changes In Net Income”-> “Product1”

44. Common Issues
NO RESULT–Block creation issue !!!!
Validation Errors
FIX on restricted members
Need member block anchor before IF .. ENDIF
Member name with space not enclosed in “ “
Write to cross-dimensional cells outside of FIX
Shared entity reference within @ISMBR
IF (@ISMBR("[CE-0013-GBP].[LE-0014-CAD]") )
Write to different Entity as target
Mismatch comment /* xxxxxx*/
Deployment Issues
Empty rule vs. commented rule

45. Best Practice
Avoid using @ISMBR on dense dimension as it run in CELL mode
Use member names instead of member alias to ensure it works for all location alias
Do not write to “FCCS_Mvmts_Subtotal” as CalcDim recalculates from its children
Note that “FCCS_Mvmts_Subtotal” cannot be dynamic calc
Use CalcDim on non-aggregated dimensions (not Accounts, Entity, Consolidation, etc.)
Avoid using CLEARDATA
First clears and then write #missing
More efficient to just set member to #missing in one operation
Don’t use on dynamic calcparent member as no need to clear
Entity Dimension
Can’t FIX or use as Target or as Anchor
Can only use in IF condition or as Source

46. Best Practice -Performance
FIX on Sparse Dimensions
•Essbase pull blocks only for combination of sparse dimension members
FIX on Dense Dimension (Account)
•All members will be pulled for each data block
•May result multiple passes to database for info
Performance
•FIX on Sparse dimensions
•Use IF … ENDIF for Dense dimension
•Don’t need CALC DIM or AGG

47. Tighter FIXes
•FCCS internally fixes on Scenario, Year, Period, Entities and View.
•User should FIX on remaining dimensions. Don’t forget to FIX on
dimensions like ‘Intercompany’, ‘Multi-GAAP’, ‘Custom’ etc.
•As above dimensions are not having restricted members, system will
not complain. Calculations may run for undesired members from
these dimensions.
•If a calculation has to run on an entire dimension, restrict calculations
to base members. Example –
• FIX( @LEVMBRS("Product", 0), …. )
•Use IF conditions to limit calculations.

48. Frequently Asked Questions
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 48

49. Can I change properties on dimensions?
No, do not make any changes to the default properties of dimensions.
While this is a common practice for PBCS and Essbase, this will
negatively impact FCCS. Consolidations may not complete, and this
could impact the seeded calculations.

50. Can I change the consolidation operator on Entities from
Ignore to Addition?
No. FCCS has a consolidation script that performs the consolidation of
one entity into another. This property should be set to Ignore.
Otherwise, the results are incorrect.

51. Can I add children to seeded FCCS members that are
initially base members?
Within the dimensions Account, Data Source, Movement and Multi
GAAP (if used), there are FCCS_ seeded members.
If these members have a data storage property of dynamic, they can
have children added to them. If they are store or never share they
cannot.

52. Can I add member formulas to movement members?
While member formulas can be added to movement members, it will
make the consolidation process very slow.

53. Where do shared members go in a dimension?
•Shared members must be added after the non-shared member.
•For example, in the account dimension shown here, cash and equivalents are under
FCCS_Current assets as a non-shared member and under FCCS_Total Cash as a shared
member. Notice that the non-shared member is first in the hierarchy and the shared
member is second. *
* Note that this does NOT apply to the Entity dimension. “Shared” entities are not really shared, they are duplicated. And it is just not practical to always
maintain the duplicate member after the initial member if the client needs to change ownership from period to period.

54. What are common mistakes using Data Management?
•Not adding a currency row to the import profile. The currency row must be
included.
•Trying to load data to an input currency. Data is loaded to “Entity Currency”.
•Assuming the “From Currency” is the Currency row. It is not, as shown in this
screenshot example of the import profile with a correct currency row.

55. Why can’t I export data? I have the period dimension in the
column.
In FCCS, the only dense dimension is the account dimension. So the
account dimension must be in the column in order to natively export
data.
Data management is the recommended mechanism to export data.

56. Why does my cashflownot tie?
Make sure that every new movement member (Mvmts_) is added to both
the FCCS_Closing Balance and the FCCS_Cash Flow hierarchies.
Under FCCS_ClosingBalance, the new movement member should have a
consolidation operation of “addition”, and under FCCS_CashFlow, the
consolidation operation for each movement member should be
“subtraction”.

57. Do I manually add new members to the Intercompany
dimension?
No. When an entity is enabled for intercompany, the system
automatically adds a new member in the Intercompany Dimension.

58. Can I have labels, aliases, and descriptions that are the
same across dimensions?
All labels must be unique across dimensions.Aliases and Descriptions must be unique
within a dimension.
The only exception is in the currency dimension. The alias and description for both
reporting currencies and input currencies can be the same.

59. Can I have alternate hierarchies in the account dimension?
Yes. The Balance Sheet Cash and Non Cash hierarchy is an alternate
hierarchy of the balance sheet accounts.

60. What do I do with Audit Tables?
The best practice is to manually export and truncate the audit tables.
Otherwise, table size can become too large and users cannot log in to
the application.

61. Consolidation Performance and Diagnostics
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 61

62. Consolidation:
Performance Degradation and Functional Issues
1.Bad application design
2.Unnecessary calculations
3.Poorly written configurations/extensions
4.Lack of needed house keeping
Causes

63. Step 1 -Bad Application Design
Incorrect metadata properties can cause errors during consolidation and poor
performance.
Best practices for metadata properties can be checked by
•Simplified Dimension Editor
•Metadata Validator
Fixing the metadata errors are important for consolidation performance and correctness.
All documentation is available here:
https://docs.oracle.com/cloud/latest/financial-consol-
cloud/AGFCC/editing_member_properties_sui.htm#AGFCC-GUID-DC9FF4BE-C8B9-45E2-AF08-
381DD86B26E4
The page is called “Editing Member Properties in the Simplified Dimension Editor”.
Diagnostics of consolidation performance degradation

64. Step 2 –Unnecessary Calculations
•The consolidation process and steps are clearly documented in FCCS.
•By default, FCCS performs many calculations during the consolidation process that may
not be needed for the customer.
•Turning some of these calculations off could improve performance.
Diagnostics of consolidation performance degradation

65. Step 3 –Poorly Written Configurations/Extensions
•The default consolidation logic can be extended by the customer or partner
•The customer specific logic is inserted as part of the overall consolidation process and
can be written as:
•Member formulas
•Calculation logic
•Translation/consolidation overrides
•Poorly written logic in these extensions/configurations can severely cause
performance degradation
Diagnostics of consolidation performance degradation

66. Step 4 –Lack of Needed House Keeping
•Keeping the Consolidation engine tuned by removing unnecessary data blocks and
ensuring the structure is efficiently stored is important for optimal consolidation
performance.
•Doing the necessary house keeping can improve consolidation performance.
Diagnostics of consolidation performance degradation

67. 4A) Clearing Empty Blocks
Click Rules -> Select “Clear Empty Blocks” rule, Click on Launch icon
Select Scenario and Year for which your consolidation performance issue exists
Click on Launch button. After the process finishes, rerun consolidation
Step 4 –Lack of Needed House Keeping

68. 4B) Dense restructure
Click on Consolidation Card and click on user editable rule such as Final Calculations. This
launches Hyperion Calculation Manager.
In Calculation Manager, click Database Properties tool bar button (green icon)
In Database properties expand Planning-><AppName> and check if application's
databases are running,There should be no red box against the database
Click on Consol database and navigate to Statistics tab. Check property named Average
clustering ratio. If the value is near 1 (1 being maximum) then we are good. There is
no need to restructure cube.However, if value shows something like 0.01032828,
then it is time to restructure the cube.
Helpful related article -https://blogs.oracle.com/pa/essbase-bso-data-fragmentation
Step 4 –Lack of Needed House Keeping

69. UnderstandMonitoring
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 69

70. •Oracle releases a patch containing bug fixes, code optimization, and feature updates
on the first Friday of themonth.
•Oracle applies this patch to the test environment of the service during the next
Daily Maintenance window following a patch release.
•Typically, production environments are patched on the third Friday of themonth.
•Oracle notifies Service Administrators of the updates included in eachpatch.
•For minor patch releases, Oracle typically provides one week advance notification
before patching the testenvironment.
•For major updates, Oracle provides a two-month advancenotification.
70
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Plan for MonthlyUpdates

71. •The Activity Report is automatically generated each day to enable Service
Administrators to understand applicationusage.
•It identifies calculation scripts and user Requests that impact applicationperformance.
•It compares service usage and performance from pastreports.
•It is available from the user interface by going to Application, Overview, ActivityReports.
71
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Monitor Your Application with the ActivityReport

72. The Activity Report shows the number of users who accessed theservice.
In addition to the average usage duration for the number of users on a specific day, the report presents
information on the number of users who logged on each day over the last week, users over the last seven
days, and users over the last 30days.
Example: Number of Users Accessing theService
30
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |

73. TheActivityReportshowsthepercentageofuserinterfacerequeststhattookmorethan10secondsto
finishandthetop7requeststhattookthemosttimetocomplete.Eachrequestisauseractionsuchas
signingin,loadingdata,openingorsavingforms,andvalidatingrules.
Example: User InterfaceRequests
31
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |

74. The Activity Report shows the average service response time each hour for the last 24 hours andthe
number of users that used the environment for different ranges ofdurations.
Example: Average Response Time, Number ofUsers
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 74

75. •The Activity Report identifies the consolidation runs that took the longest time to run.
Available information includes the number of times the script was run, POV and the
duration
•The Activity Report shows the 10worst performing queries that took over 15 seconds
toexecute
•The Activity Report identifies the Top 10 queries that were executed for the longest
durations
•The Activity Report identifies the Top 10 queries that are most frequentlyexecuted
Other monitoring
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 75

76. •UsethedownloadfileEPMAutomateUtilitycommandtodownloadthe
ActivityReportandaccesslogstoalocalcomputerifyouneedthemfor
auditpurposes.
•Use the Provisioning Report to identify users who areprovisioned
to access anenvironment
•Access the service as a ServiceAdministrator.
•On the Home page, Click Tools, and then AccessControl.
•Click ProvisioningReport.
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 76
Use the Activity Report and ProvisioningReport

77. Design and Implementation Tutorials
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 77

78. Tour of Financial Consolidation and Close
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 78
This overview gives you a tour of Financial Consolidation and Close Cloud.
https://www.youtube.com/watch?v=ikF3sr0N_aI

79. Tour of Financial Consolidation and Close
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 79
How to set up an application in FCCS
https://www.youtube.com/watch?v=71OVABxUvYQ

80. Basics of consolidation
Understanding the basics of consolidation
https://www.youtube.com/watch?v=dEtxoyXWHfw

81. Basics of consolidation
Translation process as part of consolidation
https://www.youtube.com/watch?v=Ie80T_U-LQ8

82. Basics of consolidation
Calculation logic of the consolidation process
https://youtu.be/c9Hla6APey4

83. Journals management
Basics of getting started with Journals
https://youtu.be/c9Hla6APey4

84. Journals management
Approving of Journals and workflow
https://youtu.be/IczLsYaA1rA

85. Overview: Dimensions in Financial Consolidation and
Close Cloud
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 85
This overview will help you get started with dimensions in Financial
Consolidation and Close Cloud.
https://www.youtube.com/watch?v=j1tr4w_vNR4

86. Managing the Close Process in Financial Consolidation
and Close Cloud
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 86
This overview shows you the highlights of the capabilities that you'll use
in your financial close process.
https://www.youtube.com/watch?v=wcRgPon5laQ

87. Managing the Close Process in Financial Consolidation
and Close Cloud
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 87
Managing the supplemental data collection
https://www.youtube.com/watch?v=nYeRHNpzfgk

88. Overview: Integration in Financial Consolidation and Close
Cloud
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 88
This overview describes integrations in Financial Consolidation and
Close Cloud.
https://www.youtube.com/watch?v=GprETrjaXzE

89. Setup user provisioning and roles
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 10
Setting up roles, user provisioning and understanding security
https://www.youtube.com/watch?v=h56S9sID078

90. Questions?
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. | 90