Results for “recipient_code”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GR_RECIPIENT_ADDRESSES is a table owned by the GR schema within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite. Its documented purpose is to store multiple address records associated with a customer or recipient, allowing a single regulatory recipient to be linked to more than one physical or postal address. This supports scenarios in process manufacturing where regulatory documentation, material safety data sheets, labels, or compliance correspondence must be dispatched to several distinct locations maintained for the same recipient.
In ETRM 12.1.1 and 12.2.2 the table is reported with a status of VALID and eight documented columns. The relationship metadata classifies this object as a link under a heuristic Data Vault model. This is a modeling suggestion rather than a physical implementation: the table resolves many-to-many style relationships between recipient records and address master records, which is the characteristic behaviour of a link entity in a Data Vault design.
Key Information Stored
The table is deliberately narrow, with the documented column list focused on identification and auditing rather than descriptive address text. The most important columns are:
- ADDR_ID — identifier of the address, participating in the primary key and referenced against the address master table.
- RECIPIENT_CODE — identifier of the regulatory recipient or customer; the second component of the primary key and a foreign key to the recipient information table.
- ADDRESS_TYPE — classifies the address, such as a shipping, billing, or regulatory contact address, and is validated against the recipient address types table.
- CREATED_BY, CREATION_DATE — standard audit columns capturing who created the row and when.
- LAST_UPDATED_BY, LAST_UPDATE_DATE — audit columns recording the most recent modification.
- LAST_UPDATE_LOGIN — the login identifier associated with the last update, used for audit and troubleshooting.
The single documented unique index, GR_RECIPIENT_ADDRESSES_PK, is defined on the composite of ADDR_ID and RECIPIENT_CODE. This makes the pair a business-key candidate as well as the surrogate enforcement mechanism: a recipient cannot be associated twice with the same address. Descriptive address attributes such as street, city, and postal code are expected to reside in the referenced address master rather than in this table.
Common Use Cases and Queries
Typical usage centres on resolving which addresses belong to a recipient and which address type each represents. Reporting queries commonly join the table to the address master and the recipient information table to produce a complete recipient address listing for regulatory output.
- Address lists for a recipient: select all rows for a given RECIPIENT_CODE, sorted by ADDRESS_TYPE.
- Address type validation: resolve ADDRESS_TYPE against GR_RECIPIENT_ADDR_TYPES to display a meaningful description.
- Data quality and audit reports: query CREATED_BY, CREATION_DATE, LAST_UPDATED_BY and LAST_UPDATE_DATE to identify stale or recently changed relationships.
- Duplicate detection: group by ADDR_ID and RECIPIENT_CODE to confirm uniqueness, since the primary key already enforces it.
A representative pattern joins recipient information to this table and then to the address master:
SELECT ri.recipient_code, ra.address_type, am.* FROM gr.gr_recipient_info ri, gr.gr_recipient_addresses ra, sy.sy_addr_mst am WHERE ri.recipient_code = ra.recipient_code AND ra.addr_id = am.addr_id;
Related Objects
The foreign key metadata identifies three directly related objects that carry the semantic detail this link table omits:
- SY_ADDR_MST — the address master holding the actual address attributes; joined on GR_RECIPIENT_ADDRESSES.ADDR_ID = SY_ADDR_MST.ADDR_ID.
- GR_RECIPIENT_INFO — the parent recipient/customer record; joined on GR_RECIPIENT_ADDRESSES.RECIPIENT_CODE = GR_RECIPIENT_INFO.RECIPIENT_CODE.
- GR_RECIPIENT_ADDR_TYPES — lookup of valid address type codes; joined on GR_RECIPIENT_ADDRESSES.ADDRESS_TYPE = GR_RECIPIENT_ADDR_TYPES.ADDRESS_TYPE.
Together these three parents supply the descriptive and validating context for the link rows and should be included in any extraction that requires human-readable regulatory address output.
-
Contains multiple address information for the customer.
-
This entity will only be populated if the ADDITIONAL DOCUMENTFLAG on the customer entity is set to 'Y'. It allows the user to specifythe printing of additional documents with the primary document. Anexample of this might be the primary doc
-
Contains a table which holds the information for which document is to be printed from the Sales Order Processing information.
-
Contains transaction information, such as who received what and when.
-
This entity will only be populated if the ADDITIONAL DOCUMENTFLAG on the customer entity is set to 'Y'. It allows the user to specifythe printing of additional documents with the primary document. Anexample of this might be the primary doc
-
Contains multiple address information for the customer.
-
Contains additional customer specific information.
-
Contains a table which holds the information for which document is to be printed from the Sales Order Processing information.
-
Contains additional customer specific information.
-
View: GR_RECIPIENT_INFO_V 12.2.2
Contains the rows for the recipients information table
APPS.GR_RECIPIENT_INFO_V·↳ GR_DISCLOSURES·↳ GR_RECIPIENT_INFO·↳ GR_REGIONS·Explore GR module →
-
Contains transaction information, such as who received what and when.
-
View: GR_RECIPIENT_INFO_V 12.1.1
Contains the rows for the recipients information table
APPS.GR_RECIPIENT_INFO_V·↳ GR_DISCLOSURES·↳ GR_RECIPIENT_INFO·↳ GR_REGIONS·Explore GR module →
-
VIEW: GR.GR_SELECTION# 12.2.2
-
VIEW: GR.GR_SELECTION# 12.2.2
-
VIEW: GR.GR_RECIPIENT_INFO# 12.2.2
-
VIEW: GR.GR_RECIPIENT_INFO# 12.2.2
-
TABLE: GR.GR_SELECTION 12.1.1
-
TABLE: GR.GR_SELECTION 12.2.2
-
TABLE: GR.GR_RECIPIENT_INFO 12.2.2
-
TABLE: GR.GR_RECIPIENT_INFO 12.1.1