Search Results fem_cost_objects_pk

Overview

FEM.FEM_COST_OBJECTS is a core Enterprise Performance Foundation (EPF/ETRM) table that stores the resolved cost object members used by Oracle EBS Profitability Manager, Enterprise Planning, and related cost management applications. Each row represents a single fully-qualified cost object — meaning a unique combination of dimension member identifiers drawn from the cost object structure defined against the ledger. The table functions as the persisted cross-reference between human-readable display codes and the numeric surrogate identifiers generated by the cost object structure engine, allowing downstream allocations, profitability rollups, and cost assignments to reference members without re-resolving the segment hierarchy on every transaction.

In Data Vault terms, the mined relationship metadata classifies this object as standalone (no outgoing links other than PRODUCT_ID → FND_DM_PRODUCTS), and the presence of a surrogate key with a natural business key suggests modeling it as a hub with the display code combination acting as the business key. Practically, however, the wide column set of dimension foreign keys means an analyst may instead treat it as a satellite of the cost object structure. Both readings are defensible; the standalone classification is the heuristic suggestion.

Key Information Stored

The table persists 64 documented columns. The most operationally significant are:

• COST_OBJECT_ID — surrogate primary key (index FEM_COST_OBJECTS_PK); the internal identifier referenced by transactions and allocations.
• COST_OBJECT_DISPLAY_CODE — VARCHAR2(2000) human-readable code, unique in combination with LOCAL_VS_COMBO_ID via index FEM_COST_OBJECTS_U1. This is the column surfaced by the user's search term cost_object_display_code.
• LOCAL_VS_COMBO_ID — value-set combination identifier joining to the local value set describing the cost object.
• COST_OBJECT_STRUCTURE_ID — the structure definition that generated this member.
• LEDGER_ID — the ledger context in which the cost object is valid.
• FINANCIAL_ELEM_ID — financial element resolved for the member.
• SUMMARY_FLAG — distinguishes summary (parent) members from detail members.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating.
• Dimension member identifiers: PRODUCT_ID, CUSTOMER_ID, CHANNEL_ID, PROJECT_ID, and COMPANY_COST_CENTER_ORG_ID.
• USER_DIM1_ID … USER_DIM10_ID — extensible user-defined dimensions.
• SEGMENT1 … SEGMENT30 — composite segment columns holding element display codes.
• Standard audit columns (CREATION_DATE, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER) and ENABLED_FLAG, PERSONAL_FLAG, READ_ONLY_FLAG.

Common Use Cases and Queries

Typical usage involves resolving a display code to its surrogate id, or listing active cost objects in a ledger:

SELECT cost_object_id, cost_object_display_code, summary_flag, ledger_id
FROM   fem.fem_cost_objects
WHERE  cost_object_display_code = :p_code
AND    ledger_id = :p_ledger
AND    enabled_flag = 'Y'
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                          AND NVL(end_date_active, SYSDATE);

Reporting queries frequently join to FND_DM_PRODUCTS on PRODUCT_ID to attribute cost to product hierarchies, and filter on SUMMARY_FLAG = 'N' to restrict to detail-level members. Because Oracle labels this object Internal Use Only, direct SQL should be confined to read-only reporting and never used for transactional inserts or updates — all maintenance should pass through standard Oracle Programs (Profitability Manager concurrent requests).

Related Objects

• FND_DM_PRODUCTS — joined via FEM_COST_OBJECTS.PRODUCT_ID = FND_DM_PRODUCTS.PRODUCT_ID; the only documented foreign key relationship.
• Cost object structure definition tables — referenced via COST_OBJECT_STRUCTURE_ID.
• Local value set / combination tables — referenced via LOCAL_VS_COMBO_ID.
• Ledger definitions (GL_LEDGERS) — joined on LEDGER_ID.
• Financial element definitions — joined on FINANCIAL_ELEM_ID.
• Profitability/allocation staging tables that consume COST_OBJECT_ID as a fact-side key.

All object access must respect Oracle's Internal Use Only restriction and be exercised only through supported applications interfaces.