Results for “cost_object_structure_id”

9 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FEM_COST_OBJECTS is a table owned by the FEM schema within the Enterprise Performance Foundation (EPF) product of Oracle E-Business Suite, documented as VALID at releases 12.1.1 and 12.2.2. Its business description, "Cost Object Members," identifies it as the master repository of the individual cost object members that populate an EPF cost object structure. In the EPF/ETRM data model, a cost object represents the lowest-level intersection of dimensions against which profitability, cost allocation, and financial reporting are performed. Each row in this table defines a single member, resolving up to thirty generic SEGMENT columns, ten USER_DIM_ID slots, and named dimension identifiers (PRODUCT_ID, CUSTOMER_ID, CHANNEL_ID, PROJECT_ID, COMPANY_COST_CENTER_ORG_ID) into a single COST_OBJECT_ID.

The mined Data Vault classification for this object is standalone, which should be read as a modeling suggestion rather than a physical constraint: FEM_COST_OBJECTS behaves as a self-contained reference or dimension hub, with no documented foreign-key dependents pointing into it. Its only mined outbound relationship is PRODUCT_ID → FND_DM_PRODUCTS. The table carries 64 documented columns and is maintained with standard EBS WHO columns and an OBJECT_VERSION_NUMBER for optimistic locking, consistent with a definitional setup table rather than a transactional fact table.

Key Information Stored

The documented primary key is a surrogate: COST_OBJECT_ID, enforced by the unique index FEM_COST_OBJECTS_PK. The business-key candidate is the composite unique index FEM_COST_OBJECTS_U1 over LOCAL_VS_COMBO_ID and COST_OBJECT_DISPLAY_CODE — the latter supplying the human-readable identifier presented to users, and the former tying the member to its value-set/combination context.

The most significant remaining columns include:

  • COST_OBJECT_STRUCTURE_ID — the structure to which the member belongs, the primary grouping key for queries.
  • SUMMARY_FLAG and ENABLED_FLAG — whether the member is a roll-up node and whether it is active.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective-dating window governing valid assignment.
  • SEGMENT1 through SEGMENT30 — the generic segment columns holding the member's dimension values.
  • FINANCIAL_ELEM_ID and LEDGER_ID — linkage to the financial element definition and the ledger context.
  • PRODUCT_ID, CUSTOMER_ID, CHANNEL_ID, PROJECT_ID, COMPANY_COST_CENTER_ORG_ID — named dimension identifiers for the most common EPF dimensions.
  • USER_DIM1_ID through USER_DIM10_ID — extensible slots for customer-defined dimensions.
  • UOM_CODE — unit of measure associated with the member where quantities are captured.
  • PERSONAL_FLAG and READ_ONLY_FLAG — restrict modification of system-delivered members.

Common Use Cases and Queries

Typical use is resolving a cost object identifier to its descriptive dimensions for reporting, validating member completeness before allocations run, and extracting the flattened dimension set for loading into a warehouse or Essbase outline. A common pattern joins the member to its dimensions while filtering on structure and effective dates:

SELECT co.cost_object_id,
       co.cost_object_display_code,
       co.segment1, co.segment2, co.product_id,
       co.summary_flag, co.enabled_flag
FROM   fem.fem_cost_objects co
WHERE  co.cost_object_structure_id = :structure_id
AND    co.enabled_flag = 'Y'
AND    TRUNC(SYSDATE) BETWEEN co.start_date_active
                          AND NVL(co.end_date_active, TRUNC(SYSDATE));

Diagnostic queries frequently aggregate counts of enabled versus disabled members per structure, or identify orphaned members where a named dimension column such as PRODUCT_ID contains a value not present in FND_DM_PRODUCTS. Because the table is definitional and changes infrequently, it is well suited to incremental extraction keyed on LAST_UPDATE_DATE.

Related Objects