Results for “gr_recipient_documents”

30 results




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

Overview

GR_RECIPIENT_DOCUMENTS is a table in the GR (Process Manufacturing Regulatory Management) schema of Oracle E-Business Suite, present and VALID in both 12.1.1 and 12.2.2. It functions as a cross-reference entity that maps recipients of regulatory documents to the specific additional documents that should be printed alongside the primary document for that recipient. The ETRM documentation states that this entity is populated only when the ADDITIONAL_DOCUMENT_FLAG on the customer entity is set to 'Y', enabling users to specify the printing of supplemental documents together with the primary document. In practice, this table governs which supporting regulatory artifacts accompany a recipient's main compliance output during document generation.

Following the Data Vault classification heuristic mined from its foreign key structure, this table is best modeled as a link table. It does not store descriptive attributes or historical snapshots of a business entity; instead, it resolves a many-to-many association between two independent entities — recipients and document codes — and therefore serves as a junction or associative entity between them.

Key Information Stored

The documented physical schema for 12.2.2 lists seven columns. The most significant are the two business-key columns that together constitute the primary key, plus the standard EBS audit columns:

  • RECIPIENT_CODE — Identifies the recipient of the document set; part of the composite primary key and a foreign key to GR_RECIPIENT_INFO.
  • DOCUMENT_CODE — Identifies the additional document to be printed; the second component of the composite primary key and a foreign key to GR_DOCUMENT_CODES.
  • CREATED_BY — Standard EBS audit column recording the user who created the row.
  • CREATION_DATE — Standard EBS audit column recording the row creation timestamp.
  • LAST_UPDATED_BY — Standard EBS audit column recording the last user to modify the row.
  • LAST_UPDATE_DATE — Standard EBS audit column recording the last modification timestamp.
  • LAST_UPDATE_LOGIN — Standard EBS audit column recording the login session of the last update.

The unique index GR_RECIPIENT_DOCUMENTS_PK defined on (RECIPIENT_CODE, DOCUMENT_CODE) is the business-key candidate and satisfies the primary key constraint. There is no separate single-column surrogate key documented; the composite of the two business columns serves both as the primary key and the uniqueness guarantee, preventing duplicate recipient-document pairings.

Common Use Cases and Queries

Typical usage centers on determining, for a given recipient, which additional documents must be printed. A representative join retrieves the descriptive recipient and document information behind each mapping:

  • Listing all additional documents for a recipient: SELECT document_code FROM gr_recipient_documents WHERE recipient_code = :recipient_code;
  • Resolving descriptions: join GR_RECIPIENT_DOCUMENTS to GR_DOCUMENT_CODES on DOCUMENT_CODE and to GR_RECIPIENT_INFO on RECIPIENT_CODE.
  • Auditing recently added or changed mappings via LAST_UPDATE_DATE and LAST_UPDATED_BY within a date range.
  • Identifying recipients configured with supplemental documents to reconcile against the ADDITIONAL_DOCUMENT_FLAG on the customer entity.
  • Reverse lookups: finding all recipients that reference a specific DOCUMENT_CODE, useful before retiring or modifying a document code.

Related Objects

The FK relationships documented in the ETRM metadata identify the principal objects this table depends upon or is queried with:

  • GR_RECIPIENT_INFO — joined on GR_RECIPIENT_DOCUMENTS.RECIPIENT_CODE = GR_RECIPIENT_INFO.RECIPIENT_CODE; the parent recipient entity.
  • GR_DOCUMENT_CODES — joined on GR_RECIPIENT_DOCUMENTS.DOCUMENT_CODE = GR_DOCUMENT_CODES.DOCUMENT_CODE; the parent document definition entity.
  • Customer entity (ADDITIONAL_DOCUMENT_FLAG) — controls whether rows are populated for a given customer recipient.
  • Primary document printing processes — the regulatory output generators that consume these mappings to assemble the printed document set.
  • GR_RECIPIENT_DOCUMENTS_PK — the unique index enforcing uniqueness of the recipient-document pairing.

Because the table is a thin link with audit columns only, the majority of business meaning is carried by its two parent tables; join these parents whenever descriptive reporting is required.