Table 4 Default Data Cell Colors

Cell Color Indication Off-white This is an input cell. You can enter or edit data manually. Light green Allows allocations/derived data. Medium green This cell is read-only. Dark green This cell has no write or read access/derived data. Red Invalid intersection of dimension members. You cannot enter data in invalid cells. Yellow Yellow indicates one of these conditions: Data in the cells has been modified but has not yet been saved. The input status is OK, but the status of the adjustment is not OK (CH, CN or TRN). If the status is CN for node level adjustments, you must run Force Calculate Contribution to clear up the adjustment member status. Gray This cell contains locked/derived data. Blue This is a header cell. Black This is the active cell.
Table 5 Calculation Statuses

Status Description OK None of the data for the specified Scenario, Year, Period, Entity, and Value dimensions has changed. OK ND OK ² No data. The calculation has been effectively run, but no calculations were run for NODATA. OK SC OK ² System changed. Some of the data for the specified Scenario, Year, Period, Entity, and Value dimensions has changed. For example, a new rules file or metadata file has been loaded. CH Needs Calculation. At least one data cell for the specified Scenario, Year, Period, Entity, and Value dimensions has been changed, or metadata parameters or rules have changed. As a result, other data cells in this Scenario, Year, Period, Entity, or Value dimension may not be up to date because calculation logic has not been run. For base-level entities, the data cell may have been entered by manual data entry or by a bulk data file load. For any entity, the data cell may have been entered by a journal posting. CH ND Needs Calculation ² No Data. This indicates the first time that calculation will be performed on the cell. TR Needs Translation. The selected Value dimension member is not the entity¶s default currency, and its translated values may not be up to date. TR ND Needs Translation ² No Data. This indicates the first time that translation will be performed on the cell. CN Needs Consolidation. The data for the specified Scenario, Year, Period, Entity, and Value dimensions may not be up to date because data for a child entity has changed, data for the same entity's default currency has changed, or metadata parameters or rules have changed. CN ND Needs Consolidation. The parent has no data, but data for a child entity has changed. This indicates the first time that consolidation will be performed on the cell. Locked The data for the specified Scenario, Year, Period, Entity, and Value dimensions has been locked by an administrator and can no longer be modified by manual data entry or calculations. NODATA No data exists for the specified Scenario, Year, Period, Entity, and Value dimensions. NoAccess The user does not have rights for the specified dimension member.

Data Grid Tasks
You can perform these tasks from data grids on the Web: Setting Grid Rows and Columns Entering or Editing Data Setting the Point of View on the Web

Data Grid Options
These options are available for data grid cells: Viewing Cell Information Adding Cell Text Viewing Cell Adjustments Adding Line Item Detail Calculation Process Translating Data

Beige This cell contains locked/derived data. Dark gray This cell is read-only. you must run Force Calculate Contribution to clear up the adjustment member status. If the status is CN for node level adjustments. Yellow Yellow indicates one of these conditions: Data in the cells has been modified but has not yet been saved. The input status is OK.Consolidating Data Locking Data Viewing Cell History Viewing Destination and Source Transactions Running Entity Transaction Detail Reports Running Allocations Process Management Options These Process Management options are available from data grids. Information Start Promote Reject Sign Off Submit Approve Publish These options are also available from the Process Control module. but the status of the adjustment is not OK (CH. Light gray This cell has no write or read access/derived data. and select Process Control. in the File Browser. You can enter or edit data manually. take one of these actions: Highlight a cell in a data grid that is set up for Process Management. Pink Invalid intersection of dimension members. To access Process Management options. right-click and select Manage Process. Blue This is a header cell. Table 8 Line Item Detail Options Task View Multiple Periods View Single Period Insert Line Item Detail Clear Line Item Detail from a Single Period Clear Line Item Detail from Multiple Periods Delete Line Item Detail from Multiple Periods Windows Data Grid No Yes Yes Yes No No Web Data Grid No Yes Yes Yes No No Data Forms Yes Yes Yes Yes Yes Yes Consolidation Status The consolidation status of a base level or parent entity can change as a result of several actions: Changing the organization structure Adding or deleting accounts . Table 6 Default Data Cell Colors Cell Color Indication Off-white This is an input cell. Light green This cell allows allocations/derived data. expand Tasks and Data Tasks. CN or TRN). You cannot enter data in invalid cells. To use the Process Control module.

It must be an Asset. Also. the account cannot have children. . For regular journals. designated as calculated in metadata). the parent must allow adjustments for child entities. The entity and the parent must be valid dimensions. the entity must allow adjustments. you must enter a valid parent. the system validates the journal. which display intercompany transactions by transaction ID IC Matching templates. The journal must have the appropriate status for the action to be performed. which display a list of intercompany transactions IC Matching by Account reports. Line items must exist for the journal. Revenue. Journal Validation When you submit. or Balance Recurring account. If you are posting a journal to <Parent Currency Adjs>. the entity must be a child of the specified parent for the journal entity. that is. You can also drill down from an Intercompany Matching Report to view intercompany transactions. If you are posting a journal to a node. which display intercompany transactions based on selected accounts IC Matching by Transaction ID reports. The system also checks for the Organization by Period application setting when you attempt to post node journals. Flow. print. It cannot be calculated through a roll-up. The entity must be a child of the specified parent. Balance. the period must be opened The Value dimension must be an adjustment dimension. Node journals must have valid parent-entity combinations. The system checks for these conditions: The period must be a base period for the scenario¶s base frequency. When you post or unpost a journal. The account must be a base account and cannot be calculated (that is. The account must be valid. approve. Liability. or post a journal. The entity must be active for the parent for the period in which you are posting. and delete reports. which display the intercompany transactions that are to be eliminated during consolidation Intercompany Transaction reports. which display information for a journal or list of journals based on criteria that you select in the Journals module Intercompany Partner (ICP) Matching reports. Expense.Modifying entity attributes Entering data in data grids. Opening Reports You can generate these types of reports: Data Explorer reports. and you can save. which contain settings that you frequently use for auto-matching intercompany transactions You can apply report style sheets. or loading data from external sources Posting or unposting journals Posting or unposting intercompany transactions Reloading rules Changing percent consolidation Changing currency rates You can view the consolidation status from the Explore Data module on the Desktop or on the Web. which display information from data grids Journal reports.

If the Value dimension is <Entity Currency>. the total debits must equal the total credits. the total debits must equal the total credits for each entity. For a balanced journal. If an ICP is specified. but you can select [ICP None]. The subcube containing the line item cell cannot be locked. All intersections must be valid. the custom dimensions cannot have children. The cell cannot be designated as a NoInput cell using rules. For a balancedbyentity node journal. that is. the total debits must equal the total credits for each node. . the parent and children entities must have the same currency. or left blank. The ICP dimension cannot be ICP Top. ICP Entities. The custom dimensions cannot be designated as calculated in metadata and cannot be calculated through a roll-up. For a balanced by entity regular journal. the account must be set up as an ICP account. the parent entities in the journal can have different currencies.All other dimensions must be valid. For a balanced-by-entity node journal. but they must have the same currency as their children entities.

Sign up to vote on this title
UsefulNot useful