Results for “fm_text_hdr”

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

Overview

MR_SHDY_HDR is the shop day header table within the Oracle E-Business Suite Process Manufacturing Process Planning module (GMP). It resides in the GMP schema and holds the master definition of a shop day — a discrete calendar unit used by process manufacturers to organize and schedule production activities. Each row represents one shop day, identified by a unique shop day number, and serves as the anchor point for the daily shop calendar and its associated scheduling detail.

The table is documented as VALID in ETRM 12.2.2 and applies equally to 12.1.1 deployments. Its role is primarily organizational and referential: it does not store transaction quantities or inventory balances itself, but it defines the day boundaries against which the shop calendar header (MR_SHCL_HDR) and shop day detail (MR_SHDY_DTL) records are structured. From a Data Vault modeling perspective, the mined foreign key structure suggests a hub-leaning classification — SHOPDAY_NO behaves as a durable business key with relatively stable descriptive attributes, which is the signature of a hub candidate rather than a transactional link.

Key Information Stored

The table documents ten columns. The most significant are:

• SHOPDAY_NO — the primary key, enforced by the unique index MR_SHDY_HDR_PK. This is the business-key candidate that uniquely identifies each shop day and is the column most often joined against downstream calendar tables.
• SHOPDAY_DESC — a descriptive label for the shop day, used for reporting and user-facing calendar displays.
• TRANS_CNT — a counter of transactions associated with the shop day, useful for workload and activity reporting.
• TEXT_CODE — a foreign key reference to FM_TEXT_HDR, linking the shop day to a text or comment block maintained in the FM text header table.
• DELETE_MARK — the standard Oracle EBS soft-delete flag; a non-zero value indicates a logically deleted row that should be excluded from most queries.

The remaining columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — form the standard Oracle EBS audit trail, recording who created and last modified each record and when.

Common Use Cases and Queries

The most common reporting requirement is to list active shop days with their descriptions while filtering out soft-deleted records. A representative pattern follows:

• SELECT shopday_no, shopday_desc, trans_cnt FROM mr_shdy_hdr WHERE NVL(delete_mark,0) = 0 ORDER BY shopday_no;
• Joining to the text table to retrieve associated comments: SELECT h.shopday_no, h.shopday_desc, t.text_code FROM mr_shdy_hdr h, fm_text_hdr t WHERE h.text_code = t.text_code AND NVL(h.delete_mark,0)=0;
• Exploding the shop calendar to obtain the seven day slots defined in MR_SHCL_HDR, using the DAY1 through DAY7 foreign key columns.
• Driving shop day detail reports through a join to MR_SHDY_DTL on SHOPDAY_NO.
• Calendar and capacity planning queries that reconcile shop day definitions with the scheduling data in MR_SHCL_DTL.

Because TRANS_CNT is maintained on the header, it is frequently used as a quick aggregate indicator of day activity without querying the detail table.

Related Objects

MR_SHDY_HDR participates in a well-defined referential network:

• FM_TEXT_HDR — referenced by MR_SHDY_HDR.TEXT_CODE; supplies the text block attached to the shop day.
• MR_SHCL_DTL — the shop calendar detail table, which references SHOPDAY_NO from this header.
• MR_SHDY_DTL — the shop day detail table, joined via MR_SHDY_DTL.SHOPDAY_NO.
• MR_SHCL_HDR — the shop calendar header, which references MR_SHDY_HDR through seven separate columns, DAY1 through DAY7. This seven-way dependency reflects the weekly structure of the process manufacturing shop calendar and makes MR_SHCL_HDR the most significant dependent table.

Together these objects form the calendar infrastructure underpinning process planning and scheduling in GMP, with MR_SHDY_HDR acting as the central day-level hub.