The Global Artifacts directory contains substitution variables, business rules, Calculation Manager rulesets, spread patterns, smart lists, common dimensions, exchange rates, task lists, composite forms, custom menus, Planning unit hierarchies, and report mappings artifacts.
Standard dimensions associated with more than one plan type are listed under Common Dimensions. This section also includes any associated attribute dimensions.
Table 39. Global Artifacts
Artifact | Description | Last Modified Time | Last Modified User | Editable on the File System? | Dependencies |
---|---|---|---|---|---|
Substitution Variables | Global placeholders for information that changes regularly | No | No | No | None |
Business Rules—Rules[1] | Logical expressions or formulas that are created within an application to produce a preferred set of resulting values | Yes | No | Yes—XML | None |
Business Rules—Sequences* | An ordered grouping of business rules created with Business Rules | Yes | No | Yes—XML | None |
Business Rules—Macros* | A reusable part of a business rule that can be referenced by other business rules and macros to save you time when you are writing business rules and sequences | Yes | No | Yes—XML | None |
Business Rules—Global Variables* | A variable that is used in more than one business rule or macro | Yes | No | Yes—XML | None |
Business Rules—Project* | An instance of EPM System products grouped together in an implementation; for example, a Planning project may consist of a Planning application, an Essbase cube, and a Financial Reporting server instance | Yes | No | Yes—XML | None |
Calculation Manager Rulesets[2] | Objects that contain rules and other rulesets that can be calculated simultaneously or sequentially | Yes | Yes | Yes—XML | None |
Spread Patterns | A custom spreading pattern that determines how data is distributed from a parent to its children. The pattern is available from the Mass Allocate and Grid Spread menus. | No | No | Yes—XML | None |
Smart Lists[3] | Custom drop-down lists that users access from data form cells (instead of entering data) | No | No | Yes—XML | None |
Common Dimensions—Attribute‡ | A type of dimension that enables analysis based on the attributes or qualities of dimension members. Associated with common standard dimensions. | Yes | No | Yes—XML | None |
Common Dimensions (Standard—Account)‡ | A dimension type that makes accounting intelligence available. Only one dimension can be defined as Accounts. | Yes | No | Yes—XML | None |
Common Dimensions (Standard—Version)‡ | Possible outcome used within the context of a scenario of data; for example, Budget - Best Case and Budget - Worst Case where Budget is scenario and Best Case and Worst Case are versions | Yes | No | Yes—XML | None |
Common Dimensions (Standard—Currency)‡ | A dimension representing currency | Yes | No | Yes—XML | None |
Common Dimensions (Standard—Entity)‡ | A dimension representing organizational units; for example: divisions, subsidiaries, plants, regions, products, or other financial reporting units | Yes | No | Yes—XML | Currency dimension gets loaded first |
Common Dimensions (Standard—Year)‡ | A dimension representing the fiscal or calendar year for data | Yes | No | Yes—XML | None |
Common Dimensions (Standard—Scenario)‡ | A dimension for classifying data; for example, Actuals, Budget, Forecast1, and Forecast2 | Yes | No | Yes—XML | Period and Year dimensions, Exchange Rates |
Common Dimensions (Standard—Period)‡ | A dimension representing time periods, such as quarters and months | Yes | No | Yes—XML | Year |
Exchange Rates | A numeric value for converting one currency to another; for example, to convert 1 USD into EUR, the exchange rate of 0.8936 is multiplied with the U.S. dollar. The European euro equivalent of $1 is 0.8936. | Yes | No | Yes—XML | Currency, Period, and Year |
Task Lists | A detailed status list of tasks for a particular user | Yes | No | Yes—XML | If task is of type Business Rule, then associated Business Rule. If task is of type Data Form, then associated Data Form. If task is of type Workflow, then Planning Units. |
Composite Forms | Displays members from several data forms simultaneously so you can; for example, enter data into one grid and see the results—such as Total Revenue—aggregated in another | Yes | No | Yes—XML | Associated Data Forms and Business Rules. |
Custom Menus | Menus that administrators create that are company- or application-specific. Users can right-click a member and select a menu item to open a URL, data form, workflow, or business rule. | Yes | No | Yes—XML | If menu is of type Business Rule, then associated Business Rule. If menu is of type Workflow, then Planning Units. |
Planning Unit Hierarchies | Specifies which application planning units and members are part of the budget process | Yes | Yes | Yes—XML | Entity, Scenario, Version and other associated dimensions. |
Report Mappings | Maps dimensions between Planning applications and reporting applications to enable reporting on Planning data in a reporting application, aggregations and queries on Smart Lists, and linking Planning data to multiple reporting applications for consolidations | Yes | Yes | Yes—XML | Associated dimensions and Smart Lists. |