Results for “ic_cldr_hdr_pk”

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

Overview

The IC_CLDR_HDR table is a core setup and reference object within the Oracle E-Business Suite GMI – Process Manufacturing Inventory module. Its documented purpose is to store header information for the inventory calendar. Each row defines an inventory fiscal year for a specific organization, while the individual calendar periods belonging to that fiscal year are stored separately in the IC_CLDR_DTL table. This header/detail split allows an installation to define many organizations and many fiscal years without duplicating period attributes at the header level.

From a Data Vault modeling perspective, the mined FK structure classifies IC_CLDR_HDR as satellite-leaning. This is a modeling suggestion: the table carries descriptive attributes tied to a composite business key rather than acting as a pure hub or a many-to-many link. Implementers designing a warehouse layer should treat (ORGN_CODE, FISCAL_YEAR) as the durable business key and the remaining descriptive columns as satellite attributes.

Note that the ETRM metadata records this table as “Not implemented in this database” for the source instance, meaning the columns visible in a given environment may vary. The object nonetheless remains part of the documented Process Manufacturing Inventory schema.

Key Information Stored

The primary key is defined as IC_CLDR_HDR_PK, a composite key over two columns. Both columns are business-key candidates rather than a generated surrogate; there is no documented single-column surrogate identifier.

• ORGN_CODE — Organization code. Part of the composite primary key and a foreign key to SY_ORGN_MST. Identifies which inventory organization the calendar belongs to.
• FISCAL_YEAR — The fiscal year defined by this header row. The second component of the composite primary key. Periods within this year are enumerated in IC_CLDR_DTL.
• TEXT_CODE — Foreign key to IC_TEXT_HDR, providing an association to the text/notes framework used throughout GMI for attaching descriptive or instructional text.

The combination of ORGN_CODE and FISCAL_YEAR is the documented unique business key. Every dependent structure, most notably the period detail rows, is resolved through these two columns rather than through a synthetic number.

Common Use Cases and Queries

Typical usage centers on inventory period management, period-close reporting, and validation that a fiscal calendar exists before transaction processing. A standard lookup resolves a header for an organization and year and joins to the detail rows:

• Listing all fiscal years defined for a given organization: SELECT FISCAL_YEAR FROM IC_CLDR_HDR WHERE ORGN_CODE = :orgn;
• Confirming calendar definition before opening a period, joining header to detail on both key columns: SELECT h.ORGN_CODE, h.FISCAL_YEAR, d.* FROM IC_CLDR_HDR h, IC_CLDR_DTL d WHERE h.ORGN_CODE = d.ORGN_CODE AND h.FISCAL_YEAR = d.FISCAL_YEAR AND h.ORGN_CODE = :orgn;
• Resolving attached notes via the text framework: SELECT t.* FROM IC_CLDR_HDR h, IC_TEXT_HDR t WHERE h.TEXT_CODE = t.TEXT_CODE AND h.ORGN_CODE = :orgn;
• Integrity checks that every header has at least one detail period, and that every ORGN_CODE values resolves in SY_ORGN_MST.

Reporting use cases include period-close dashboards, calendar-coverage audits, and data-migration validation when moving calendars between environments.

Related Objects

• IC_CLDR_DTL — The principal dependent table. It references IC_CLDR_HDR through the composite (ORGN_CODE, FISCAL_YEAR) relationship and holds the individual calendar period definitions.
• SY_ORGN_MST — Organization master. IC_CLDR_HDR.ORGN_CODE references this table, anchoring each calendar to a valid inventory organization.
• IC_TEXT_HDR — Text header table. IC_CLDR_HDR.TEXT_CODE references it, enabling narrative or instructional content to be attached to a calendar header.
• IC_CLDR_HDR_PK — The primary key constraint enforcing uniqueness of the (ORGN_CODE, FISCAL_YEAR) business key.

Together these objects form the calendar backbone used by Process Manufacturing Inventory for period definition and control.