Search Results parent_manager_id

Overview

FII.FII_COM_CC_MAPPINGS is a transaction-data table owned by the FII (Financial Intelligence) schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. According to the ETRM object documentation, the table "contains associations between cost center manager and line of business dimension." In practice it functions as the mapping repository that links a company, its cost center, the cost center manager, and the line of business (LOB) dimension used by Oracle's financial intelligence and profitability reporting components. Records are stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and all associated indexes reside in APPS_TS_TX_IDX.

The table carries an FND Design Data registration of FII.FII_COM_CC_MAPPINGS and is flagged VALID in the ETRM metadata repository. A useful heuristic modeling suggestion is that this object behaves as a link table in a Data Vault sense: it resolves many-to-many associations between companies, cost centers, managers, and lines of business rather than acting as a standalone hub or a descriptive satellite. It does reference PN_COMPANIES_ALL through COMPANY_ID, and it is itself referenced by the APPS.ENI_DBI_GL_BASE_MV materialized view, indicating its role as a feeder of summarized financial reporting structures.

Key Information Stored

The most significant columns capture the enterprise structure and its ownership relationships:

• COMPANY_COST_CENTER_ORG_ID — the company cost center organization identifier; this column is the target of the unique index FII_COM_CC_MAPPINGS_U1 and therefore functions as the most precise business-key candidate.
• COMPANY_ID and COST_CENTER_ID — the company and cost center identifiers. Together they form the composite unique index FII_COM_CC_MAPPINGS_U2, making them the second documented business-key candidate and the natural join path to company and cost center definitions.
• MANAGER_ID — the cost center manager identifier.
• LOB_ID and VALID_MGR_FLAG — the line of business identifier and a flag indicating a valid manager (documented as MANAGER_ID > 0).
• PARENT_MANAGER_ID and PARENT_LOB_ID — the parent manager and parent line of business identifiers, supporting hierarchy roll-up and reporting structures.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide audit traceability.

The documented schema contains thirteen columns. Informational (non-unique) indexes FII_COM_CC_MAPPINGS_N1 through N3 support access paths on COST_CENTER_ID/COMPANY_ID, PARENT_MANAGER_ID, and PARENT_LOB_ID respectively.

Common Use Cases and Queries

Typical uses include validating manager-to-LOB assignments, resolving cost center ownership for financial reporting, and supplying the dimensional data consumed by GL-based materialized views. A basic extraction follows the documented query text:

• SELECT COMPANY_COST_CENTER_ORG_ID, COST_CENTER_ID, COMPANY_ID, MANAGER_ID, LOB_ID, VALID_MGR_FLAG, PARENT_MANAGER_ID, PARENT_LOB_ID FROM FII.FII_COM_CC_MAPPINGS;
• Reporting by manager hierarchy: filter on PARENT_MANAGER_ID or join MANAGER_ID to the manager hierarchy to roll up subordinate cost centers.
• LOB analysis: aggregate cost centers by LOB_ID and PARENT_LOB_ID, optionally restricting to VALID_MGR_FLAG = 'Y' to exclude unassigned managers.
• Company-level drill: join COMPANY_ID to PN_COMPANIES_ALL to enrich reports with company attributes.

Related Objects

The documented dependency and foreign-key metadata identifies the following significant relationships:

• FII.PN_COMPANIES_ALL — referenced through COMPANY_ID; the authoritative source of company definitions.
• APPS.ENI_DBI_GL_BASE_MV — a materialized view that references FII_COM_CC_MAPPINGS, consuming its mapping data for GL reporting.
• FI — listed as a referencing dependency, indicating the financial intelligence component that uses this table.
• The unique indexes FII_COM_CC_MAPPINGS_U1 and U2 and the non-unique indexes N1–N3 are the primary physical access structures supporting joins on company, cost center, manager, and LOB.

The table does not reference any other database object besides PN_COMPANIES_ALL, confirming its position as a standalone mapping/link structure that is read by downstream reporting objects rather than by further dependent foreign keys.