Financial Close Management Artifact Listing
Oracle Hyperion Financial Close Management artifacts are listed in the Financial Close Management application group in Oracle Hyperion Shared Services Console.
Note:
The artifacts displayed in Shared Services Console vary by implementation.
About the Artifact Listing
Note the following about the artifact listing:
-
Artifact—Artifact name
-
Description—Artifact description
-
Last Modified Time—If this parameter is supported, reflects the time the artifact was imported. Some artifacts do not support the last modified time parameter.
-
Last Modified User—If this parameter is supported, reflects the user who last modified the artifact. Some artifacts do not support the last modified user parameter.
-
Editable on the File System—If yes, the artifact can be edited on the file system using a text editor. If no, the artifact can be edited only within the product.
-
Dependencies—Lists artifact dependencies. For example, Financial Close Management Integration Types artifacts also require that Financial Close Management Integration Applications artifacts be migrated.
Close Manager Artifacts
Table F-1 Financial Close Management Close Manager Artifacts
Artifact | Description | Last Modified Time | Last Modified User | Editable on the File System? | Dependencies |
---|---|---|---|---|---|
Alert Types | Categorize alerts into types such as hardware failure, software issues, and system failures | Yes | No | Yes—XML | None |
Custom Attributes | Categorize templates, schedules, task types, and tasks | Yes | No | Yes—XML | None |
Filters | Control which records are displayed in list views, dashboards, and report binders. | Yes | No | Yes—XML | Template |
Global Integration Tokens | Enable the creation of parameterized URLs | Yes | No | Yes—XML | Custom Attributes
Note: Global Integration Tokens may be dependent on Custom Attributes, but that is not always the case. |
Integration Applications | Denote an external application with which Financial Close Management is integrated | Yes | No | Yes—XML | None |
Integration Types | A definition of a service provided by an application that is integrated with Financial Close Management | Yes | No | Yes—XML | Integration Applications |
Periods | A hierarchical dimension that designates the time period to which the close activities apply; for example, a month or a quarter | Yes | No | Yes—XML | None |
Task Types | Identify and categorize tasks commonly performed during a close period; for example, Data Entry, or G/L Extract | Yes | No | Yes—Zip
Note: Editing is not recommended because the artifact must be extracted and the format of the compressed contents should be retained. |
Period, Year, Alert Types, Custom Attributes, Integration Applications, Integration Types |
Templates | A set of tasks that are repeatable over close periods. Administrators can create templates for different types of close periods, such as monthly or quarterly. | Yes | No | Yes—Zip
Note: Editing is not recommended because the artifact must be extracted and the format of the compressed contents should be retained. |
Period, Year, Alert Types, Custom Attributes, Integration Applications, Integration Types, Task Types |
User Preferences | Preferences specific to the time zone used for a Financial Close Management application | Yes | No | Yes—XML | None |
Years | A flat list that designates the year to which the close activities apply; for example, 2009, 2010, FY09, or FY10. | Yes | No | Yes—XML | None |
Account Reconciliation Manager Artifacts
Table F-2 Financial Close Management Account Reconciliation Manager Artifacts
Artifact | Description | Last Modified Time | Last Modified User | Editable on the File System? | Dependencies |
---|---|---|---|---|---|
Account Types | Classifies profiles, reconciliations, and adjustments according to a hierarchical structure | Yes | No | Yes—XML | None |
Aging Profiles | A collection of aging buckets | Yes | No | Yes—XML | None |
Currencies | A generally accepted medium of exchange. Financial Close Management seeds currency details such as currency code and symbol which are ISO compliant | Yes | No | Yes—XML | None |
Custom Attributes | Categorize information for easier filtering and searching. Custom attributes are assigned to templates, schedules, task types, and tasks. For example, you can filter a task list to include only tasks with a specific custom attribute. | Yes | No | Yes—XML | None |
Custom Currencies | Currencies that are not ISO compliant | Yes | No | Yes—XML | None |
Dashboard Definitions | Views into schedules and task lists, and high-level summaries into which you can drill down for greater detail | Yes | No | Yes—XML | Filters, CSS Users, Aging Profiles |
Filters | Control which records are displayed in list views, dashboards, and report binders. | Yes | No | Yes—XML | Custom Attributes |
Formats | Determine the method of reconciliation and the information that must be provided before the reconciliation can be sent on for review | Yes | No | Yes—Zip
Note: Editing is not recommended because the artifact must be extracted and the format of the compressed contents should be retained. |
Custom Attributes |
Frequencies | How often reconciliations are prepared and renewed. Frequencies are defined in system settings and are associated with profiles and periods. | Yes | No | Yes—XML | None |
Global Integration Tokens | Enable the creation of parameterized URLs | Yes | No | Yes—XML | Custom Attributes
Note: Global Integration Tokens may be dependent on Custom Attributes, but that is not always the case. |
Global Settings | Contains the Max File Upload, Dataload Context and "Days Before Due Date" system settings. These settings are established by the Administrator and apply to the entire Financial Close Management user base. | Yes | No | Yes—XML | None |
Periods | Unit of time for which an Account Reconciliation is completed; for example, January 2013, February 2013 | Yes | No | Yes—XML | Frequencies |
Power User Security | Security filters on account segments accessed by power users | Yes | No | Yes—XML | Profile Segments, CSS Roles |
Processes | Associate profiles with a specific reconciliation process; for example, the balance sheet reconciliation process or the local GAAP reconciliation process | Yes | No | Yes—XML | None |
Profile Segments | Profile account IDs stored in segments to facilitate filtering and reporting on the values | Yes | No | Yes—XML | None |
Profiles | Contain the configuration settings that determine how and when reconciliations occur | Yes | No | Yes—Zip
Note: Editing is not recommended, because the artifact must be extracted and the format of the compressed contents should be retained. |
Custom Attributes, Formats, Periods, Account Types, Rate Types, Profile Segments |
Rate Types | Associated with foreign exchange rates for use with profiles or reconciliations | Yes | No | Yes—XML | None |
Risk Ratings | Enable classification of profiles and reconciliations according to risk level. Risk ratings can be used to select accounts for reporting, or to facilitate assignment of preparers, frequencies, or other attributes. | Yes | No | Yes—XML | None |
Teams | Defined and provisioned with Preparer, Reviewer, Viewer, and Commentator roles. Then, rather than assigning named users these roles on a profile or reconciliation, the role is assigned to the Team. | Yes | No | Yes—XML | None |
User Preferences | Preferences specific to the time zone used for a Financial Close Management application | Yes | No | Yes—XML | None |
Supplemental Data Manager Artifacts
Table F-3 Financial Close Management Supplemental Data Manager Artifacts
Artifact | Description | Last Modified Time | Last Modified User | Editable on the File System? | Dependencies |
---|---|---|---|---|---|
Currencies | A generally accepted medium of exchange. Financial Close Management seeds currency details such as currency code and symbol which are ISO compliant. | No | No | No | None |
Connections | Details to connect to another application for online integration such as importing metadata or posting data. | Yes | Yes | No | Non |
Data Collection Periods | Combination of Period, Year and Frequency in which form can be deployed for data collection. | No | No | No | Period |
Datasets | A set of attributes used in a supplemental schedule. | Yes | Yes | No | Dimension |
Dimensions | A flat list of records containing metadata that could be referenced in data entry schedules. | Yes | Yes | No | None |
Filters | Control which records are displayed in list views, dashboards, and report binders. | No | No | No | Integration Profile, Form Templates, Data Sets, Dimension, Scenario Dimension |
Form Templates | Definitions of supplemental data schedules that can be deployed to open periods for collecting and reviewing information among stakeholders. | Yes | Yes | No | DataSets |
Frequencies | How often supplemental data is prepared and reviewed. Frequencies are defined in the system and are associated with periods. | No | No | No | None |
Integration Profiles | Definitions of what metadata to be pulled from other applications that have online integration. | Yes | Yes | No | Connection |
Periods | Unit of time for which a supplemental schedule is prepared; for example, January 2015, Quarter1 2014 | Yes | Yes | No | Frequency |
Preferences | Formatting options for a schedule | No | No | No | None |