Results for “local_vs_combo_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FEM_ACTIVITIES is a table in the FEM (Enterprise Performance Foundation) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. The Enterprise Performance Foundation provides the shared dimensional and hierarchical infrastructure that underpins Oracle's Enterprise Performance Management applications, including Profitability Manager and related cost and revenue allocation engines. In this context, FEM_ACTIVITIES stores activity members — the discrete units of work, business process, or cost-consuming operation to which costs and revenues are assigned and across which allocations are driven.
Activities function as a core dimension in activity-based costing and management models. Each row represents a single activity member that can participate in allocation rules, driver assignments, and profitability calculations. The table carries a rich set of foreign-key-style references to other foundational dimensions, such as products, customers, channels, projects, tasks, and company cost centers, allowing an activity to be qualified by those attributes.
A Data Vault classification heuristic, mined from the foreign key structure, suggests modeling FEM_ACTIVITIES as a standalone structure rather than a strict hub, link, or satellite. Its single documented outgoing reference (PRODUCT_ID to FND_DM_PRODUCTS) is insufficient to treat it as a conventional link table; it is therefore best understood as a dimension-style member registry with its own surrogate key and embedded descriptive and attribute columns.
Key Information Stored
The documented physical schema for FEM_ACTIVITIES contains 62 columns. The most significant are:
- ACTIVITY_ID — the surrogate primary key, enforced by the FEM_ACTIVITIES_PK unique index. This is the technical identifier used by all downstream references.
- ACTIVITY_DISPLAY_CODE — the human-readable code for the activity member; together with LOCAL_VS_COMBO_ID it forms the business-key candidate enforced by the FEM_ACTIVITIES_U1 unique index.
- LOCAL_VS_COMBO_ID — distinguishes local activity members from combination (combo) members within the activity structure.
- ACTIVITY_STRUCTURE_ID — identifies the activity hierarchy or structure to which the member belongs.
- SUMMARY_FLAG — indicates whether the row is a summary (parent) node or a detail activity.
- START_DATE_ACTIVE / END_DATE_ACTIVE — the effective dating window during which the activity member is active.
- ENABLED_FLAG, READ_ONLY_FLAG, PERSONAL_FLAG — status and ownership controls governing whether the member can be modified or is user-personal.
- PRODUCT_ID — the one documented foreign key, referencing FND_DM_PRODUCTS.
- CUSTOMER_ID, CHANNEL_ID, PROJECT_ID, TASK_ID, COMPANY_COST_CENTER_ORG_ID — dimensional qualifiers linking the activity to customer, channel, project, task, and organization contexts.
- USER_DIM1_ID through USER_DIM10_ID — ten extension slots for user-defined dimensions.
- SEGMENT1 through SEGMENT30 — thirty generic attribute segments used to store additional member-level values.
- OBJECT_VERSION_NUMBER — optimistic locking column, plus the standard WHO audit columns CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
Common Use Cases and Queries
Typical usage centers on resolving activity members for allocations, validating activity codes, and reporting on activity dimension content.
- Looking up an activity by its business code:
SELECT activity_id, activity_display_code, summary_flag, enabled_flag FROM fem_activities WHERE activity_display_code = :code AND local_vs_combo_id = :lvc; - Retrieving active, enabled members within an activity structure:
SELECT activity_id, activity_display_code FROM fem_activities WHERE activity_structure_id = :structure_id AND enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE); - Joining to product master data through the documented FK:
SELECT a.activity_display_code, p.product_number FROM fem_activities a, fnd_dm_products p WHERE a.product_id = p.product_id; - Reporting counts of detail versus summary activities, and auditing recently modified members using LAST_UPDATE_DATE.
Related Objects
- FND_DM_PRODUCTS — referenced by FEM_ACTIVITIES.PRODUCT_ID; the only documented foreign key target.
- FEM_ACTIVITY_STRUCTURES — parent definition of the activity hierarchies referenced by ACTIVITY_STRUCTURE_ID.
- FEM_ACTIVITY_STRUCTURES_B / _TL — base and translated structure definition tables.
- FEM_ALLOCATIONS / FEM_ALLOCATION_RULES — allocation definitions that consume activity members as source or target dimension values.
- FEM_DIMENSIONS — metadata registry describing the activity dimension and its user dimension slots.
- FEM_USER_DIMS — definitions for USER_DIM1_ID through USER_DIM10_ID referenced by activity rows.
- FND_DM_CUSTOMERS, FND_DM_CHANNELS, FND_DM_PROJECTS, FND_DM_TASKS — master tables aligning with CUSTOMER_ID, CHANNEL_ID, PROJECT_ID, and TASK_ID.
- FEM_ACTIVITIES_PK / FEM_ACTIVITIES_U1 — the unique indexes enforcing the primary and business keys described above.
-
Activity Members
-
Cost Object Members
-
TABLE: FEM.FEM_VS_COMBO_RELS 12.1.1
-
TABLE: FEM.FEM_ACTIVITIES 12.1.1
-
TABLE: FEM.FEM_COST_OBJECTS 12.1.1
-
PACKAGE: APPS.FTP_TP_PKG 12.1.1