Results for “mtl_planners”

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

Overview

MTL_PLANNERS is a core Inventory (INV) setup table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores planner code definitions. Planner codes are the identifiers assigned to material planners—the individuals or roles responsible for forecasting demand, managing replenishment, and executing MRP and MPS planning activities within a given inventory organization. Because planning responsibility is organization-specific, the same planner may exist under separate definitions in multiple inventory organizations, each with its own planner code, contact e-mail, and associated employee record.

From a Data Vault modeling perspective, the foreign-key structure mined from this table classifies it as hub-leaning. The composite primary key (PLANNER_CODE, ORGANIZATION_ID) functions naturally as a hub business key, while descriptive and audit columns represent the associated satellite attributes. This makes MTL_PLANNERS a sensible candidate for a hub table if the organization is building a Data Vault layer over EBS Inventory data.

Key Information Stored

The table comprises 31 documented columns. The most significant are:

• PLANNER_CODE — the business identifier for the planner, and part of the composite primary key.
• ORGANIZATION_ID — the inventory organization to which the planner definition belongs; the second component of the primary key and the FK to MTL_PARAMETERS.
• DESCRIPTION — free-text name or description of the planner.
• DISABLE_DATE — date on which the planner code was inactivated, supporting historical reporting.
• EMPLOYEE_ID — link to PSB_EMPLOYEES, associating the planner with an HR employee record.
• ELECTRONIC_MAIL_ADDRESS — the planner's e-mail, used by planning and notification workflows.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit Who columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns that track the process which last modified the row.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the standard DFF/extension flexfield columns for client-specific data.

The surrogate/business-key candidate is documented as the unique index MTL_PLANNERS_U1 over (PLANNER_CODE, ORGANIZATION_ID); the primary key constraint is MTL_PLANNERS_PK.

Common Use Cases and Queries

Typical usages include planner lookup lists in planning workbenches, planner-based reporting on supply and demand, and filtering items assigned to a given planner. A basic query retrieves active planners for an organization:

• SELECT p.planner_code, p.description, p.electronic_mail_address FROM mtl_planners p WHERE p.organization_id = :org_id AND NVL(p.disable_date, SYSDATE+1) > SYSDATE;

A join to item master reveals item-level planner assignment:

• SELECT msi.segment1 item, mp.planner_code planner FROM mtl_system_items_b msi, mtl_planners mp WHERE msi.planner_code = mp.planner_code AND msi.organization_id = mp.organization_id AND msi.organization_id = :org_id;

Reporting use cases include planner workload summaries, e-mail distribution lists for planning notifications, and reconciliation of planners to employee records via EMPLOYEE_ID.

Related Objects

MTL_PLANNERS sits at the center of several planning relationships:

• MTL_PARAMETERS — parent organization definition, joined on ORGANIZATION_ID.
• PSB_EMPLOYEES — employee master, joined on EMPLOYEE_ID.
• MTL_SYSTEM_ITEMS_B — item master; references MTL_PLANNERS on PLANNER_CODE and ORGANIZATION_ID.
• CSP_MSTRSTCK_LISTS_ITMS — master stock list items, referencing PLANNER_CODE and ORGANIZATION_ID.
• CSP_PARTS_LOOPS_B — service parts loop definitions, referencing PLANNER_CODE and ORGANIZATION_ID.
• CSP_NOTIFICATIONS — planning notification records, referencing PLANNER_CODE and ORGANIZATION_ID.

Together these relationships confirm MTL_PLANNERS as a dependent reference object within the Inventory planning schema.