Results for “ic_jrnl_mst”

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

Overview

IC_JRNL_MST is the journal master header table within the Oracle Process Manufacturing Inventory (GMI) module of Oracle E-Business Suite. It resides in the GMI schema and serves as the central control record for inventory journal entries generated through process manufacturing transactions, adjustments, and postings. Each row represents a single journal header that groups the detailed journal lines and drives the posting lifecycle within the OPM Inventory application.

In Data Vault modeling terms, the mined relationship structure classifies IC_JRNL_MST as satellite-leaning. This heuristic suggests that the table primarily captures descriptive and transactional context attributes associated with journal activity, anchored by surrogate and business keys, rather than functioning as a pure hub or link. The classification reflects the table's concentration of mutable, descriptive columns alongside its key structures.

Key Information Stored

The table contains 50 documented columns, but the operationally significant attributes are concentrated in the following:

• JOURNAL_ID — the surrogate primary key, uniquely identifying each journal header (index IC_JRNL_MST_PK).
• JOURNAL_NO and ORGN_CODE — the composite business-key candidate defined by unique index IC_JRNL_MST_I1, pairing the journal number with the organizational code under which it was created.
• POSTING_ID — links the journal header to its posting process.
• POSTED_IND — indicates whether the journal has been posted, a critical control flag for period processing.
• PRINT_CNT — tracks how many times the journal has been printed.
• JOURNAL_COMMENT — free-text descriptive commentary attached to the journal.
• TEXT_CODE — foreign key to IC_TEXT_HDR, enabling attached text notes.
• IN_USE — a concurrency/locking flag indicating active processing.
• DELETE_MARK — logical deletion indicator consistent with EBS conventions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns recording who created and last modified the record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the DESCRIPTIVE flexfield (DFF) columns for extensible, client-specific data capture.

Common Use Cases and Queries

Typical workloads include journal posting status reporting, unposted journal identification, and audit reconciliation. A common pattern retrieves all unposted journals for an organization:

SELECT JOURNAL_ID, JOURNAL_NO, ORGN_CODE, POSTED_IND, CREATION_DATE
FROM   GMI.IC_JRNL_MST
WHERE  ORGN_CODE = :orgn_code
AND    POSTED_IND = 'N'
AND    DELETE_MARK = 0;

Business-key lookups typically resolve a journal number within an organization, exploiting index IC_JRNL_MST_I1, while surrogate-key joins use JOURNAL_ID. Reporting queries frequently join to IC_ADJS_JNL to reconcile header-to-line detail, and administrators query PRINT_CNT and IN_USE to diagnose stuck or repeatedly printed journals.

Related Objects

• IC_ADJS_JNL — references IC_JRNL_MST.JOURNAL_ID, providing the adjustment journal detail lines subordinate to each header.
• IC_TEXT_HDR — referenced via IC_JRNL_MST.TEXT_CODE, supplying attached text header content.
• SY_ORGN_MST_B — referenced via IC_JRNL_MST.ORGN_CODE, validating the organization against the base organization master.
• SY_ORGN_MST — also referenced via IC_JRNL_MST.ORGN_CODE, providing organization descriptive context.

These relationships position IC_JRNL_MST as the header entity anchored to organizational master data and to journal detail through IC_ADJS_JNL, forming the core topology for OPM inventory journal processing.