Results for “stp_common_ref”

20 results




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

Overview

IGI_RA_ADDRESSES_ALL is a table owned by the IGI schema within Oracle E-Business Suite, delivered as part of the IGI – Public Sector Financials International product family. As documented in the ETRM 12.2.2 physical schema, the object is a VALID standalone table with 11 columns and a single unique index, IGI_RA_ADDRESSES_U1, defined on ADDRESS_ID. Its description identifies it as an extended table that stores additional single third-party site information, meaning it supplements — rather than replaces — the core address and site records maintained elsewhere in the EBS data model, providing Public Sector Financials-specific attributes layered on top of standard party site data.

Because the documented relationship data classifies this object as standalone and no foreign-key relationships are mined from the schema, a Data Vault modeling heuristic would suggest treating IGI_RA_ADDRESSES_ALL as a hub or satellite candidate keyed on ADDRESS_ID, rather than as a link table. This is a modeling suggestion derived from the absence of documented FK dependencies, not a prescribed design.

Key Information Stored

The most significant columns documented for this table are:

  • ADDRESS_ID — the surrogate primary key, also enforced by the unique index IGI_RA_ADDRESSES_U1. It is the single documented business-key candidate and the column through which this table is correlated to the broader address/site model.
  • STP_COMMON_REF — a common reference attribute supporting the single third-party site extension.
  • STP_ALT_ADDR — holds alternate address information for the third-party site.
  • STP_SUPPLIER — records the supplier associated with the third-party site.
  • STP_SITE_INACTIVE_DATE — the date on which the third-party site became inactive.
  • ORG_ID — the operating unit identifier, enabling multi-org (business group) data segregation and reporting.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns capturing audit and concurrency metadata.

The surrogate key ADDRESS_ID is distinct from the business-key candidate represented by the same column within the unique index; the remaining STP_* columns carry the functional Public Sector extension payload, while ORG_ID and the WHO columns provide organizational and audit context.

Common Use Cases and Queries

Typical usage centers on reporting and reconciliation of third-party site information within Public Sector Financials, filtered by operating unit and active status. A common pattern joins the table to itself or to address sources on ADDRESS_ID while restricting by ORG_ID:

  • Identifying inactive third-party sites: SELECT ADDRESS_ID, STP_SUPPLIER, STP_SITE_INACTIVE_DATE FROM IGI.IGI_RA_ADDRESSES_ALL WHERE STP_SITE_INACTIVE_DATE IS NOT NULL AND ORG_ID = :p_org_id;
  • Auditing recent maintenance by user and date: ... WHERE LAST_UPDATED_BY = :p_user AND LAST_UPDATE_DATE >= :p_from_date;
  • Listing alternate addresses for suppliers: ... WHERE STP_ALT_ADDR IS NOT NULL ORDER BY STP_SUPPLIER;
  • Common reference validation: ... WHERE STP_COMMON_REF = :p_ref AND ORG_ID = :p_org_id;

Because the table is standalone, queries rely on ADDRESS_ID and ORG_ID as the principal selection and correlation predicates; the WHO columns support audit and incremental extraction for downstream reporting.

Related Objects

The documented FK/PK metadata records no foreign-key relationships for this object, so it is best described as standalone. Consequently, related objects are those that share the ADDRESS_ID correlation and the broader address/site and party model, rather than documented FK dependents. Significant relationships to consider include:

  • Standard address tables keyed on or referencing ADDRESS_ID in the Oracle party model.
  • Third-party site records referenced through ADDRESS_ID and ORG_ID.
  • Supplier-related objects correlated through STP_SUPPLIER.
  • Public Sector Financials extension tables sharing the IGI schema and ORG_ID partitioning.
  • Reporting views and concurrent programs within IGI – Public Sector Financials that consume ADDRESS_ID.

Join columns are ADDRESS_ID (shared with the address/site model) and ORG_ID (for operating-unit-scoped joins). Any additional relationships should be validated against the site-specific ETRM documentation, as the metadata provided documents only the primary key and unique index.