Results for “flm_ekb_horizontal_plan_temp”

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

Overview

FLM_EKB_HORIZONTAL_PLAN_TEMP is a transient staging table owned by the FLM (Flow Manufacturing) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It supports the horizontal planning process within Oracle Flow Manufacturing, functioning as an intermediate workspace where the Kanban planning engine materializes projected on-hand balances, demand, and replenishment figures across a rolling date horizon for a given kanban plan and pull sequence. Rather than storing the permanent planning result, the table holds the row-level working set that the plan generation or plan review concurrent program assembles before results are presented or persisted in the durable planning tables.

Under the heuristic Data Vault classification mined from its foreign key structure, the table is modeled as standalone. It carries no downstream dependents in the documented relationship graph, which is consistent with a temporary scratch table whose lifespan is bounded by a single planning run. The absence of inbound foreign keys reinforces the transient nature of the object.

Key Information Stored

The table is defined with 25 columns and a single unique index, FLM_EKB_HORIZONTAL_TEMP_U1, whose uniqueness is enforced on PLANNING_TEMP_ID. This column is the surrogate primary key and the only documented business-key candidate; all other attributes are descriptive or dimensional references.

• PLANNING_TEMP_ID — surrogate primary key and unique identifier for each staged planning row.
• KANBAN_PLAN_ID — foreign key to MRP_KANBAN_PLANS, identifying the kanban plan that owns the row.
• PULL_SEQUENCE_ID — foreign key to MTL_KANBAN_PULL_SEQUENCES, identifying the pull sequence under analysis.
• ORGANIZATION_ID — inventory organization context for the planning row.
• INVENTORY_ITEM_ID — the item being planned.
• SUBINVENTORY_CODE and LOCATOR_ID — the storage location detail for the projected balances.
• PLAN_DATE — the horizon date to which the projections on the row apply.
• BEGINNING_ONHAND, AVAILABLE_ONHAND — opening and available quantity positions.
• EXPECTED_RECEIPTS, DAILY_DEMAND, ADJUSTED_DAILY_DEMAND — supply and demand drivers used in the horizontal calculation.
• CARDS_ONHAND, CARDS_REPLENISHED — kanban card counts derived from the plan.
• SAFETY_STOCK_DAYS, ADJUSTED_SAFETY_STOCK_DAYS, SAFETY_STOCK_TARGET — safety stock parameters and computed target.
• ITEM_UNIT_COST, INVENTORY_VALUE — costing figures carried for valuation reporting.

The standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATED_LOGIN follow Oracle EBS conventions and support traceability of who populated the staging rows.

Common Use Cases and Queries

The primary use case is plan extraction and validation: developers and analysts query the table to inspect the projected horizontal picture for a specific kanban plan before the data is committed to permanent storage. A typical query joins to MTL_KANBAN_PULL_SEQUENCES and MRP_KANBAN_PLANS to resolve plan and sequence identifiers:

SELECT t.planning_temp_id, t.plan_date, t.beginning_onhand,
  t.daily_demand, t.cards_onhand, t.safety_stock_target
FROM flm.flm_ekb_horizontal_plan_temp t
WHERE t.kanban_plan_id = :plan_id
ORDER BY t.pull_sequence_id, t.plan_date;

Secondary scenarios include reconciliation of on-hand versus available balances, review of safety stock targets against adjusted demand, valuation reporting through ITEM_UNIT_COST and INVENTORY_VALUE, and diagnostics when the horizontal planning concurrent program fails or produces unexpected card counts. Because rows are transient, reports should always filter by KANBAN_PLAN_ID or PLANNING_TEMP_ID rather than assuming a persistent dataset.

Related Objects

The documented foreign keys establish the most significant relationships from this staging table to the core Flow Manufacturing planning entities:

• MRP_KANBAN_PLANS — joined via KANBAN_PLAN_ID; the parent plan definition.
• MTL_KANBAN_PULL_SEQUENCES — joined via PULL_SEQUENCE_ID; defines the line-side pull logic being planned.
• MTL_SYSTEM_ITEMS_B — resolved via INVENTORY_ITEM_ID for item attributes.
• MTL_ITEM_LOCATIONS — resolved via LOCATOR_ID for locator details.
• ORG_ORGANIZATION_DEFINITIONS or MTL_PARAMETERS — resolved via ORGANIZATION_ID for organization context.
• MTL_ONHAND_QUANTITIES / MTL_ONHAND_QUANTITIES_DETAIL — the operational on-hand source used for reconciliation.
• CST_ITEM_COSTS — the source of ITEM_UNIT_COST values used in the populated rows.

As a standalone staging object, the table is consumed by the Flow Manufacturing planning programs and reporting logic rather than referenced by other persistent tables, so it should be treated as an internal, execution-scoped artifact within the FLM schema.