Results for “igi_ra_customers”

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

Overview

IGI_RA_CUSTOMERS is a table owned by the IGI schema, which supports the IGI – Public Sector Financials International product within Oracle E-Business Suite 12.1.1 and 12.2.2. The table is documented as an extended table that stores additional single third-party customer information. It complements the standard Oracle Receivables customer model (HZ_PARTIES, HZ_CUST_ACCOUNTS, and RA_CUSTOMERS) by holding supplementary attributes required by public sector financials processing that are not captured in the base trading community architecture.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. This classification suggests the table functions independently rather than behaving as a strict hub, link, or satellite. The absence of mined foreign key relationships indicates that IGI_RA_CUSTOMERS is not structurally dependent on other IGI tables within the documented FK graph, though its CUSTOMER_ID column logically corresponds to customer identifiers maintained in the Receivables and Trading Community schemas. The table is small in shape, with eight documented columns, and its primary access path is the unique index IGI_RA_CUSTOMERS_U1 defined on CUSTOMER_ID.

Key Information Stored

The table’s documented physical schema contains eight columns. The most significant are:

• CUSTOMER_ID – The surrogate primary key and the sole business-key candidate, enforced by the unique index IGI_RA_CUSTOMERS_U1. It identifies the single third-party customer record to which the extended attributes apply.
• STP_TYPE – Identifies the straight-through processing (STP) category or classification associated with the customer, used to determine how the customer is handled by IGI public sector processing rules.
• STP_ENFORCE_THRESHOLD – Holds the threshold value that governs enforcement of straight-through processing for this customer, supporting automated validation or exception handling.
• CREATED_BY, CREATION_DATE – Standard Oracle WHO columns recording the user and timestamp of initial row creation, used for audit and lineage.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns capturing the most recent modification user, timestamp, and login session.

The surrogate key (CUSTOMER_ID) is distinct from any business identifier that may exist in the Receivables customer tables. No additional unique indexes or alternate keys are documented beyond IGI_RA_CUSTOMERS_U1, so CUSTOMER_ID is the only documented candidate for row-level uniqueness.

Common Use Cases and Queries

Typical use cases center on reporting and maintaining extended customer attributes for public sector financials. Common queries include:

• Retrieving STP configuration for a customer: SELECT CUSTOMER_ID, STP_TYPE, STP_ENFORCE_THRESHOLD FROM IGI.IGI_RA_CUSTOMERS WHERE CUSTOMER_ID = :p_customer_id;
• Auditing recently created or changed extended customer records using CREATION_DATE and LAST_UPDATE_DATE.
• Joining to Receivables customer tables to enrich customer-level reports with STP attributes.
• Data migration or validation scripts that populate STP_TYPE and STP_ENFORCE_THRESHOLD for newly onboarded single third-party customers.

Because the table is standalone and keyed solely on CUSTOMER_ID, queries are efficient through the IGI_RA_CUSTOMERS_U1 unique index. Reporting extracts should be joined only when a customer-level attribute is required; IGI_RA_CUSTOMERS should not be treated as a driving table for transactional reporting.

Related Objects

ETRM metadata documents no foreign keys, and the Data Vault classification is standalone. Related objects are therefore inferred from the customer domain rather than explicit FK definitions:

• RA_CUSTOMERS – The base Receivables customer table; joins on CUSTOMER_ID.
• HZ_CUST_ACCOUNTS – Trading Community customer accounts; relates via CUST_ACCOUNT_ID to the party model.
• HZ_PARTIES – The party master from which customer identities originate.
• IGI_RA_CUSTOMERS_U1 – The unique index enforcing the CUSTOMER_ID primary key.
• IGI public sector financials APIs and concurrent programs – Process records that consume STP_TYPE and STP_ENFORCE_THRESHOLD.

Because no FK relationships are documented, joins to the above objects should be performed with explicit awareness of the shared customer identifier domain.