Results for “message_code”

50+ results




Overview
Explore in AI Chat

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

Overview

GMP.GMP_PROCESS_MSG_APS is a table within the Oracle E-Business Suite Process Manufacturing Process Planning module (GMP). Per the documented ETRM metadata for releases 12.1.1 and 12.2.2, it is formally described as the "APS Process Update Message table" and is explicitly flagged as currently not used. This designation means that although the object remains VALID in the data dictionary and carries a complete physical schema of twelve columns, the Advanced Planning and Scheduling (APS) integration path that would ordinarily populate it is inactive in standard deployments. The table therefore persists primarily as a legacy structural artifact retained for schema continuity and backward compatibility across the two release families.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. This is a modeling suggestion rather than a certification: the table hangs off a parent identifier and carries descriptive, message-oriented attributes rather than acting as an independent hub or a pure many-to-many link. In practice it behaves as a dependent detail structure associated with a single parent process header.

Key Information Stored

The table's physical schema comprises twelve documented columns, of which the most significant are summarized below.

  • PROCESS_UPD_ID — Part of the composite primary key and the foreign-key column referencing the parent header table. It identifies the process update event to which the message line belongs.
  • LINE_NO — The second component of the composite primary key, providing line-level sequencing within a given process update identifier.
  • MESSAGE_CODE — The message classification code describing the nature of the APS process update message.
  • PARAMETER1 through PARAMETER4 — Four generic parameter columns holding message-specific substitution or context values.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording row creation context.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification context.

The surrogate primary key is the composite GMP_PROCESS_MSG_APS_PK, defined over PROCESS_UPD_ID plus LINE_NO. No separate single-column unique index or alternate business-key candidate is documented in the ETRM metadata; the composite PK is the sole documented uniqueness constraint. Because the table is unused, these columns carry no live transactional data in a standard implementation.

Common Use Cases and Queries

Given the "currently not used" status, the practical value of this object lies in schema auditing, impact analysis, and upgrade readiness rather than operational reporting. Typical scenarios include verifying whether any residual rows exist before decommissioning integration code, and confirming referential integrity against the parent header during data migration exercises.

A representative existence check is straightforward:

  • SELECT COUNT(*) FROM GMP.GMP_PROCESS_MSG_APS; — establishes whether any legacy rows remain.
  • SELECT PROCESS_UPD_ID, LINE_NO, MESSAGE_CODE FROM GMP.GMP_PROCESS_MSG_APS ORDER BY PROCESS_UPD_ID, LINE_NO; — enumerates any surviving message lines.
  • SELECT m.* FROM GMP.GMP_PROCESS_MSG_APS m JOIN GMP.GMP_PROCESS_HDR_APS h ON m.PROCESS_UPD_ID = h.PROCESS_UPD_ID; — joins child message lines to their parent header rows.

These queries support pre-upgrade impact assessments and documentation of dormant APS integration objects. No standard concurrent program or report is documented as consuming this table.

Related Objects

The documented foreign-key relationships and the surrounding GMP APS structures define the objects of consequence:

  • GMP.GMP_PROCESS_HDR_APS — The parent header table. The foreign key GMP_PROCESS_MSG_APS.PROCESS_UPD_ID references GMP_PROCESS_HDR_APS, making this the primary dependency and the required join path.
  • GMP_PROCESS_MSG_APS_PK — The composite primary-key constraint over PROCESS_UPD_ID and LINE_NO that governs row uniqueness.
  • Sibling APS process structures in the GMP schema — Detail and header variants that share the PROCESS_UPD_ID context and mirror the parent-child pattern demonstrated here.

Because the object is dormant, no documented views, APIs, or concurrent programs reference it in the ETRM extract. Any dependency analysis should begin with the parent header join and treat this table as a dependent satellite of that structure.