Results for “schedule_desc”

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

Overview

PS_SCHD_HDR is the schedule header table within the Oracle E-Business Suite Process Manufacturing Process Planning module (product code GMP). It resides in the GMP schema and stores the defining attributes of production schedules created and consumed by the process planning engine. A schedule represents a planning context — a combination of organization and schedule name — against which process planning, MRP-style netting, and resource sizing are executed. In Oracle EBS 12.1.1 and 12.2.2 this table is a foundational configuration object rather than a transactional table; it carries the parameters, time fences, and horizon definitions that govern how the planning process treats demand and supply across an organization.

From a dimensional modeling perspective, the documented foreign key structure is heuristic hub-leaning. PS_SCHD_HDR is referenced by multiple downstream tables through the SCHEDULE_ID column, while itself referencing only a small set of descriptive and organizational tables. This pattern suggests the table functions as a hub or master entity, with detail, parameter, and sizing information distributed across dependent satellite tables keyed by SCHEDULE_ID.

Key Information Stored

The table contains 30 documented columns. The surrogate primary key is SCHEDULE_ID, enforced by the PS_SCHD_HDR_PK constraint. A second unique index, PS_SCHD_HDR_U1, defines the business key candidate as the combination of ORGN_CODE and SCHEDULE, meaning a schedule name is unique within an organization.

The most significant columns include:

• SCHEDULE_ID — surrogate primary key and the join column used by all dependent planning tables.
• ORGN_CODE — the organization code that owns the schedule; part of the unique business key and a foreign key to SY_ORGN_MST and SY_ORGN_MST_B.
• SCHEDULE — the schedule name or code, the user-facing identifier.
• SCHEDULE_DESC — descriptive text for the schedule.
• STOCK_IND, ORDER_IND — indicator flags controlling whether stock and orders participate in planning.
• EXCESS_IND, CONSUME_IND, CARRY_IND, BLANKET_IND, BPO_IND, BPO_SUGGEST, NONNET_IND — control flags governing excess handling, consumption, carry-forward, blanket orders, blanket purchase order suggestion, and non-netting behavior.
• ACTIVE_IND — denotes whether the schedule is active.
• INNER_TIMEFENCE, OUTER_TIMEFENCE, MRP_HORIZON — planning time fence and horizon boundaries.
• NO_DAYS, NO_WEEKS, NO_4WEEKS, NO_13WEEKS — bucket definitions establishing the planning calendar granularity.
• TEXT_CODE — foreign key to PS_TEXT_HDR for attached textual notes.
• DELETE_MARK, IN_USE — soft-delete and concurrency/usage flags.
• ORGANIZATION_ID — the multi-org organization identifier.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical reporting retrieves active schedule definitions for an organization, or joins the header to its detail and parameter tables. The following patterns are representative:

• List active schedules by organization: SELECT SCHEDULE_ID, SCHEDULE, SCHEDULE_DESC FROM GMP.PS_SCHD_HDR WHERE ORGN_CODE = :orgn AND ACTIVE_IND = 'Y' AND DELETE_MARK = 0;
• Resolve a schedule name to its surrogate key: SELECT SCHEDULE_ID FROM GMP.PS_SCHD_HDR WHERE ORGN_CODE = :orgn AND SCHEDULE = :name;
• Report planning parameters: select INNER_TIMEFENCE, OUTER_TIMEFENCE, MRP_HORIZON, and the bucket columns alongside the schedule name for configuration review.
• Join header to detail for planning output: SELECT h.SCHEDULE, d.* FROM GMP.PS_SCHD_HDR h, GMP.PS_SCHD_DTL d WHERE h.SCHEDULE_ID = d.SCHEDULE_ID;
• Audit schedules with descriptions by joining PS_TEXT_HDR on TEXT_CODE.

These queries are common in planning diagnostics, configuration verification, and extract routines feeding downstream reporting or integration layers.

Related Objects

PS_SCHD_HDR participates in a well-defined relationship network through SCHEDULE_ID and reference columns:

• PS_SCHD_DTL — references PS_SCHD_HDR via SCHEDULE_ID; holds schedule detail lines.
• PS_SCHD_FOR — references PS_SCHD_HDR via SCHEDULE_ID; likely holds forecast or foreign/related schedule data.
• MR_PARM_DTL — references PS_SCHD_HDR via SCHEDULE_ID; parameter detail for planning runs.
• MR_SIZE_TBL — references PS_SCHD_HDR via SCHEDULE_ID; sizing table entries tied to the schedule.
• PS_TEXT_HDR — referenced by PS_SCHD_HDR via TEXT_CODE; provides textual notes.
• SY_ORGN_MST and SY_ORGN_MST_B — referenced by PS_SCHD_HDR via ORGN_CODE; supply organization master data.

Collectively, these relationships confirm PS_SCHD_HDR as the central master for process planning schedules, with dependent tables keyed through SCHEDULE_ID and descriptive context supplied through organization and text reference tables.