Search Results pos_supplier_reg_u2

Overview

The POS.POS_SUPPLIER_REGISTRATIONS table stores information about supplier registrations and supplier onboarding requests within Oracle E-Business Suite. It is the central repository for supplier self-service registration data captured through the iSupplier Portal, holding both the identifying details of a prospective supplier and the address, tax, and classification attributes gathered during the onboarding workflow. Records move through registration and approval states before a supplier is fully established in the payables and procurement schemas.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is owned by the POS schema. In Oracle EBS 12.1.1 and 12.2.2 the object is documented as VALID with 41 columns. Based on the mined foreign key structure, the table is classified heuristically as satellite-leaning in Data Vault terms: it carries descriptive and mutable attributes describing a supplier registration event or request, rather than acting as a pure hub of business keys or a pure link resolving many-to-many relationships.

Key Information Stored

The surrogate primary key is SUPPLIER_REG_ID (NUMBER(15)), enforced by the unique index POS_SUPPLIER_REG_U1. Two business-key candidates are documented through unique indexes: SUPPLIER_REG_ID via POS_SUPPLIER_REG_U1 and SUPPLIER_NUMBER via POS_SUPPLIER_REG_U2. The index name POS_SUPPLIER_REG_U2 is significant because it enforces uniqueness on the supplier number assigned by the internal buyer during approval, making it the principal business identifier for downstream lookups.

• SUPPLIER_REG_ID — surrogate primary key identifying the registration.
• SUPPLIER_NUMBER — supplier number assigned by the internal buyer during approval; unique business key.
• SUPPLIER_NAME and SUPPLIER_NAME_ALT — primary and alternate supplier names.
• USER_REG_ID — identifies the corresponding record in FND_REGISTRATIONS for the first supplier user.
• VENDOR_PARTY_ID and PO_VENDOR_ID — references to the trading partner and payables supplier once established.
• TAXPAYER_ID, TAX_REGISTRATION_NUMBER, TAX_REG_COUNTRY_CODE, TAX_REG_TYPE — tax identification and registration attributes.
• DUNS_NUMBER — Data Universal Numbering System identifier.
• OU_ID — the operating unit with which the supplier is registered.
• REGISTRATION_TYPE, REGISTRATION_STATUS, REGISTRATION_PURPOSE — workflow classification and state.
• REG_KEY — registration key used for lookup and correlation.
• NI_NUMBER, STANDARD_INDUSTRY_CLASS, SUPPLIER_TYPE — classification attributes.
• ADDRESS_LINE1 through ADDRESS_LINE4, CITY, STATE, PROVINCE, COUNTRY, POSTAL_CODE — supplier address details.

Common Use Cases and Queries

Typical reporting covers pending supplier onboarding requests, status tracking, and reconciliation between registration records and established suppliers. Queries frequently filter on status, operating unit, or tax identifiers. A representative pattern joining to payables:

• Listing registrations by status: SELECT SUPPLIER_REG_ID, SUPPLIER_NAME, SUPPLIER_NUMBER, REGISTRATION_STATUS FROM POS.POS_SUPPLIER_REGISTRATIONS WHERE REGISTRATION_STATUS = :status;
• Operating unit review: filter on OU_ID to isolate registrations belonging to a specific operating unit.
• Tax lookup: use indexes POS_SUPPLIER_REG_N1 (TAXPAYER_ID) and POS_SUPPLIER_REG_N2 (TAX_REGISTRATION_NUMBER) to retrieve registrations by tax identifiers.
• Cross-reference: join VENDOR_PARTY_ID to HZ_PARTIES to resolve the trading partner name, or join PO_VENDOR_ID to establish the approved supplier.
• Duplicate detection: query by SUPPLIER_NAME, DUNS_NUMBER, or TAXPAYER_ID to identify potential duplicate onboarding requests.

Related Objects

The documented relationships anchor the table to master and transactional objects across schemas:

• HZ_PARTIES — joined via VENDOR_PARTY_ID to resolve the supplier trading partner.
• HR_ALL_ORGANIZATION_UNITS — joined via OU_ID to identify the registering operating unit.
• FND_TERRITORIES — joined via COUNTRY to derive territory and address information.
• POS_SUPPLIER_MAPPINGS — references this table through SUPPLIER_REG_ID, linking registration records to their downstream supplier mappings.
• FND_REGISTRATIONS — referenced through USER_REG_ID for the registering supplier user.