Results for “gr_recipient_addr_types”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GR_RECIPIENT_ADDR_TYPES is a reference (lookup) table in the Oracle E-Business Suite Process Manufacturing Regulatory Management (GR) module. It stores the set of address type codes and their human-readable descriptions that are used to classify recipient locations falling outside the two standard address categories of shipping and invoice. In practice, the table acts as a controlled vocabulary that allows regulatory compliance and product safety correspondence—such as material safety data sheet distribution, hazardous material notifications, and agency reporting—to be directed to recipients identified by role rather than by transaction default.
The table is owned by the GR schema and is documented in ETRM 12.2.2 as VALID, containing seven columns. Its primary key is defined by the constraint GR_RECIPIENT_ADDR_TYPES_PK over the single column ADDRESS_TYPE. Because that key is a natural business code rather than a generated surrogate, the table functions as a small, stable code list. Under a heuristic Data Vault classification the structure is hub-leaning: ADDRESS_TYPE behaves as a business key and the descriptive and audit columns are satellite-style attributes that could be modelled separately.
Key Information Stored
The most important columns documented for this table are:
- ADDRESS_TYPE — the business key and sole component of the GR_RECIPIENT_ADDR_TYPES_PK unique index. This code is the value propagated to dependent tables to classify a recipient address.
- DESCRIPTION — the translatable or display text that explains the meaning of the address type to end users on forms and reports.
- CREATED_BY — the application user identifier that inserted the address type row.
- CREATION_DATE — the date and time the row was originally created.
- LAST_UPDATED_BY — the application user identifier responsible for the most recent modification.
- LAST_UPDATE_DATE — the timestamp of the most recent modification, used by EBS concurrency and audit reporting.
- LAST_UPDATE_LOGIN — the login identifier associated with the most recent session that changed the row.
There is no separate surrogate key; the primary key is the business key itself. Consequently, referential integrity and uniqueness are enforced directly on ADDRESS_TYPE, and the audit columns mirror the standard WHO-column pattern used throughout EBS seeded and setup tables.
Common Use Cases and Queries
Typical usage includes validating address type codes during recipient setup, populating LOVs and value sets on the recipient address form, and reporting on which categories of recipients exist for a given operating unit or regulatory program.
A simple validation query confirms whether a code supplied by a downstream process is valid:
- SELECT ADDRESS_TYPE, DESCRIPTION FROM GR.GR_RECIPIENT_ADDR_TYPES WHERE ADDRESS_TYPE = :p_address_type;
An LOV population query orders the values for display:
- SELECT ADDRESS_TYPE, DESCRIPTION FROM GR.GR_RECIPIENT_ADDR_TYPES ORDER BY DESCRIPTION;
A usage count joins to the recipient address table to show how many addresses carry each type:
- SELECT t.ADDRESS_TYPE, t.DESCRIPTION, COUNT(a.ADDRESS_TYPE) FROM GR.GR_RECIPIENT_ADDR_TYPES t LEFT JOIN GR.GR_RECIPIENT_ADDRESSES a ON a.ADDRESS_TYPE = t.ADDRESS_TYPE GROUP BY t.ADDRESS_TYPE, t.DESCRIPTION;
Audit reporting leverages LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recently maintained reference data. Because the table is small and slowly changing, queries are inexpensive and can be embedded in concurrent programs without performance concern.
Related Objects
The most significant dependent object is the recipient address table itself. The documented foreign key GR_RECIPIENT_ADDRESSES.ADDRESS_TYPE references GR_RECIPIENT_ADDR_TYPES.ADDRESS_TYPE, making this table the parent in a one-to-many relationship. Additional relevant objects include:
- GR_GR_RECIPIENT_ADDRESSES — child table holding recipient address records; joined on ADDRESS_TYPE.
- GR_RECIPIENT_ADDR_TYPES_PK — the primary key constraint and unique index over ADDRESS_TYPE.
- Recipient and MSDS distribution setup forms — UI components that resolve the ADDRESS_TYPE code to its DESCRIPTION via LOV.
- Standard EBS audit/WHO triggers — populate CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
Modifications to existing ADDRESS_TYPE codes must be avoided once child rows exist, since the parent key value is physically stored in GR_RECIPIENT_ADDRESSES and protected by the foreign key constraint.
-
Contains additional address types and descriptions that fall outside of the standard shipping and invoice addresses
-
Contains additional address types and descriptions that fall outside of the standard shipping and invoice addresses
-
12.2.2 DBA Data 12.2.2
-
Contains multiple address information for the customer.
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
Contains multiple address information for the customer.
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
eTRM - GR Tables and Views 12.2.2
GR XML mapping table
-
eTRM - GR Tables and Views 12.1.1
GR XML mapping table
-
eTRM - GR Tables and Views 12.2.2
GR XML mapping table
-
eTRM - GR Tables and Views 12.1.1
GR XML mapping table
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1