Results for “active_ind”

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

Overview

MR_SHCL_HDR is the shop calendar header table in Oracle EBS Process Manufacturing (GMP) Process Planning. It resides in the GMP schema and holds the master definition of each shop calendar, providing the controlling record through which working-day patterns, active status, and daily capacity attributes are defined for a manufacturing organization. Each row represents one calendar, uniquely identified by the surrogate primary key MR_SHCL_HDR_PK on the CALENDAR_ID column. The table is the parent of a small family of dependent objects: shop calendar day detail (MR_SHCL_DTL), scheduling detail (PS_SCHD_DTL), and message table records (MR_MESG_TBL) all carry CALENDAR_ID as a foreign key back to this header.

Heuristic Data Vault classification of this object is satellite-leaning. The table carries descriptive and state attributes attached to a calendar business key rather than participating in a many-to-many resolution, which is the typical pattern of a Data Vault satellite. Analysts modeling the GMP calendar domain in a vault architecture should consider treating MR_SHCL_HDR as a satellite on the calendar hub, with CALENDAR_ID serving as the durable business key that links to the surrounding dependent structures.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains 20 columns. The most significant are:

• CALENDAR_ID — the surrogate primary key (MR_SHCL_HDR_PK) and the column referenced by every child table.
• CALENDAR_NO and CALENDAR_DESC — the user-facing calendar identifier and its description. CALENDAR_NO is the strongest business-key candidate alongside CALENDAR_ID.
• ACTIVE_IND — indicates whether the calendar is currently in use for planning.
• DAY1 through DAY7 — seven columns each holding a foreign key to MR_SHDY_HDR, the shop day header. Together they define the weekly working-day pattern applied by the calendar.
• DAILY_WORK_HOURS — the standard productive hours per working day, used in capacity and scheduling calculations.
• TEXT_CODE — foreign key to MR_TEXT_HDR, holding associated textual notes or instructions.
• IN_USE and DELETE_MARK — concurrency and logical-deletion flags.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard Oracle EBS audit columns maintained by the application.

The unique index MR_SHCL_HDR_PK on CALENDAR_ID is the documented business-key candidate. Seed or reference data loaded during implementation typically populates CALENDAR_NO, CALENDAR_DESC, the DAY1–DAY7 pattern, and DAILY_WORK_HOURS.

Common Use Cases and Queries

Typical reporting needs include listing active shop calendars for a plan, resolving the weekly work pattern, and auditing which calendars remain referenced by scheduling records. A representative query joining to resolve the daily pattern is:

• SELECT h.calendar_id, h.calendar_no, h.calendar_desc, h.active_ind, h.daily_work_hours, d.day1, d.day2, d.day3, d.day4, d.day5, d.day6, d.day7 FROM gmp.mr_shcl_hdr h, gmp.mr_shcl_dtl d WHERE h.calendar_id = d.calendar_id AND h.delete_mark = 0;
• Calendar utilization audit: join MR_SHCL_HDR to PS_SCHD_DTL on CALENDAR_ID to identify calendars referenced by scheduling detail records.
• Active-calendar lookup: SELECT calendar_no, calendar_desc, daily_work_hours FROM gmp.mr_shcl_hdr WHERE active_ind = 'Y' AND NVL(delete_mark, 0) = 0;
• Day-pattern validation: join each of DAY1 through DAY7 to MR_SHDY_HDR on the shop day header primary key to confirm the referenced day definitions exist and are valid.

Reporting on available capacity should always filter on ACTIVE_IND and DELETE_MARK, since logically deleted calendars remain physically present.

Related Objects

The following objects are the most significant adjacent tables in the GMP schema:

• MR_SHDY_HDR — the shop day header, referenced seven times through MR_SHCL_HDR.DAY1 through DAY7. This is the strongest structural relationship in the table.
• MR_TEXT_HDR — referenced by MR_SHCL_HDR.TEXT_CODE for associated text definitions.
• MR_SHCL_DTL — the shop calendar detail table, referencing MR_SHCL_HDR.CALENDAR_ID; holds the expansions of the calendar pattern.
• PS_SCHD_DTL — scheduling detail, referencing MR_SHCL_HDR.CALENDAR_ID, linking calendars to production schedules.
• MR_MESG_TBL — the message table, referencing MR_SHCL_HDR.CALENDAR_ID for calendar-scoped messages.

Collectively these relationships place MR_SHCL_HDR at the center of the shop calendar definition model, with seven dependent shop-day references and three child tables keyed by CALENDAR_ID.