Results for “addr_id”

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

Overview

SY_ADDR_MST_VW1 is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered under the GMA - Process Manufacturing Systems product family. As documented in the ETRM repository, its purpose is narrow and explicit: it exposes the address identifier (ADDR_ID) alongside the first two lines of a mailing address. The view is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2 environments, indicating that it is a supported and structurally stable object across these releases.

The view abstracts the party/address master data held in the underlying address table into a lightweight, purpose-built projection. Because it surfaces only three columns, it is well suited to LOV definitions, address lookup queries, label printing, and third-party integrations that require a compact address reference without the overhead of the full master record. This makes it a useful building block for both report development and interface programs that need a quick, human-readable identification of an address record associated with an ADDR_ID.

Underlying Base Objects

The view is defined over the synonym SY_ADDR_MST, which resolves to the address master table within the APPS schema. The ETRM metadata for this release confirms the dependency on this single base object.

The view definition documented in the ETRM repository is:

• SELECT ADDR_ID, ADDR1, ADDR2 FROM SY_ADDR_MST

Notably, the view definition references ADDR1 and ADDR2, which are aliased or exposed as ADDR_DISPLAY1 and ADDR_DISPLAY2 in the documented column listing. This indicates that the presentation layer of the view applies a renaming convention for clarity, distinguishing the raw address lines from their display-oriented counterparts. Because the view is a simple, non-join projection, it inherits the validity and accessibility of the underlying synonym, and any change to SY_ADDR_MST structure would directly propagate to this view.

Key Columns

• ADDR_ID — The primary address identifier. This is the key value used to join to other address-aware entities and is typically the column returned when an LOV selection is made.
• ADDR_DISPLAY1 — The first line of the address, corresponding to ADDR1 in the base table. This generally contains the primary address line, such as a street name or building designation.
• ADDR_DISPLAY2 — The second line of the address, corresponding to ADDR2 in the base table. This typically holds supplementary address information such as suite, floor, or locality data.

The naming of ADDR_DISPLAY1 and ADDR_DISPLAY2 reinforces the view's role as a display-focused projection rather than a comprehensive data source. No city, state, postal code, or country columns are exposed, which confirms that the view is intended for concise identification of an address, not for full postal formatting.

Common Use Cases and Queries

The most frequent use of SY_ADDR_MST_VW1 is as the source for an address LOV or as a lookup for populating a display field when an ADDR_ID is known. A typical query retrieving the identifier with its two display lines is:

• SELECT ADDR_ID, ADDR_DISPLAY1, ADDR_DISPLAY2 FROM APPS.SY_ADDR_MST_VW1 WHERE ADDR_ID = :p_addr_id;
• SELECT ADDR_ID, ADDR_DISPLAY1, ADDR_DISPLAY2 FROM APPS.SY_ADDR_MST_VW1 WHERE UPPER(ADDR_DISPLAY1) LIKE UPPER(:search_term) || '%';

These patterns are common in Process Manufacturing reports and custom integrations where a user selects an address and the first two lines must be echoed back to the screen or printed document. Because the view is a thin wrapper, it performs efficiently in these scenarios and does not require joins to resolve the display values. Developers integrating with external systems frequently reference it to obtain a compact, validated address representation keyed by ADDR_ID.