Results for “gr_recipient_info_v”

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

Overview

GR_RECIPIENT_INFO_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 view owned by the APPS schema and defined within the Process Manufacturing Regulatory Management (GR) product family. It exposes recipient information associated with regulatory disclosure distribution — that is, the parties and addresses to which regulatory documents, cover letters, and supporting materials are dispatched. The object status is documented as VALID in the ETRM (E-Business Suite Technical Reference Manual) metadata for release 12.2.2.

The view provides a single flattened result set joining recipient master data with region and disclosure descriptions, allowing reporting and integration layers to retrieve recipient records without directly navigating the underlying normalized tables. Because the view also exposes the INVOICE_ADDRESS column, it is frequently located by searches such as "invoice_address," which typically originate from users attempting to trace where invoice mailing information is stored for a regulatory recipient.

Underlying Base Objects

The documented DBA metadata identifies the following base objects referenced by the view definition:

• GR_RECIPIENT_INFO (SYNONYM) — the primary source of recipient rows, aliased as RI.
• GR_DISCLOSURES (SYNONYM) — the lookup source for disclosure descriptions, aliased as D.
• GR_REGIONS (SYNONYM) — the lookup source for region descriptions, aliased as R.

The join predicates are defined with outer-join syntax ((+)) on both lookups: RI.REGION_CODE = R.REGION_CODE (+) and RI.DISCLOSURE_CODE = D.DISCLOSURE_CODE (+). This ensures that a recipient row is returned even when no matching region or disclosure record exists, making the view suitable for left-outer-join reporting scenarios. The ROWID of the base recipient record is exported as ROW_ID, providing a stable row identifier for downstream processing.

Key Columns

The view projects all recipient attributes from GR_RECIPIENT_INFO plus two descriptive columns from the lookup tables. Significant columns include:

• RECIPIENT_CODE, RECIPIENT_NAME — unique identifier and descriptive name of the regulatory recipient.
• DOCUMENT_CODE — the regulatory document type associated with the recipient.
• TERRITORY_CODE, REGION_CODE, REGION_DESCRIPTION — geographic segmentation; REGION_DESCRIPTION is resolved from GR_REGIONS.
• DISCLOSURE_CODE, DISCLOSURE_DESCRIPTION — disclosure type; DISCLOSURE_DESCRIPTION is resolved from GR_DISCLOSURES.
• INVOICE_ADDRESS — the invoice mailing address used when regulatory correspondence must be routed to a billing contact.
• SHIPPING_ADDRESS — the physical delivery address for the recipient.
• ADDRESS_TO_PRINT, UPDATE_ADDRESS_FLAG, ADDITIONAL_ADDRESS_FLAG — control flags governing which address is rendered on printed regulatory output.
• ADDRESS_TO_PRINT, DOCUMENT_PRINT_FREQUENCY, COVER_LETTER_ID, ADDITIONAL_DOCUMENTS_FLAG — printing and cover-letter configuration.
• DISCLOSE_ALL_INGREDIENTS_FLAG, PRINT_RECIPIENT_PRODUCT_CODE — disclosure scope control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical applications of this view include regulatory mailing-list generation, disclosure distribution audits, and integration extracts that feed external document management or labeling systems. The INVOICE_ADDRESS column is most commonly searched when a business requirement demands that invoice correspondence be directed to the correct recipient address.

The following query lists recipients together with their invoice address and resolved region and disclosure descriptions:

SELECT recipient_code,
      recipient_name,
      invoice_address,
      region_description,
      disclosure_description
  FROM apps.gr_recipient_info_v
 WHERE invoice_address IS NOT NULL
 ORDER BY recipient_name;

A second common pattern restricts output to recipients whose printing configuration requires use of the invoice address:

SELECT recipient_code, recipient_name, invoice_address
  FROM apps.gr_recipient_info_v
 WHERE update_address_flag = 'Y'
    AND address_to_print IS NOT NULL;

Because the view is a simple projection with outer joins and no aggregation, it can be queried directly by Oracle Reports, BI Publisher, OA Framework pages, and custom PL/SQL without materialization concerns. Note that the outer joins are implemented with legacy (+) syntax, which is fully supported in 12.1.1 and 12.2.2 but should be converted to ANSI LEFT OUTER JOIN syntax in any custom objects built on top of it.