Search Results pos_supplier_registrations




Overview
Explore in AI Chat

Overview

POS_SUPPLIER_REGISTRATIONS is the core transactional table within the Oracle E-Business Suite iSupplier Portal (POS) module. It stores supplier registration submissions and supplier onboarding requests captured either through the iSupplier Portal self-service registration flow or through internal buyer-initiated onboarding processes. Each row represents a single registration request, tracking the supplier's identifying information, address, tax data, registration purpose, and workflow status as it moves from initial submission to approval and eventual creation of a supplier record in Oracle Payables.

From a Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification. The table carries a surrogate primary key (SUPPLIER_REG_ID), descriptive and mutable attributes such as registration status and notes, and foreign keys to HZ_PARTIES, FND_TERRITORIES, and HR_ALL_ORGANIZATION_UNITS. This pattern is characteristic of a satellite attached to a party hub and an operating unit link, rather than a pure hub itself. The shared HZ_PARTIES reference positions the registration record alongside the Trading Community Architecture (TCA) model, making the party relationship the natural hub candidate.

Key Information Stored

The table contains 41 documented columns. The most significant include the surrogate primary key SUPPLIER_REG_ID, which is enforced by the POS_SUPPLIER_REGISTRATIONS_PK constraint and is also the target of unique index POS_SUPPLIER_REG_U1. A second unique index, POS_SUPPLIER_REG_U2, covers SUPPLIER_NUMBER, making it the principal business-key candidate for external identification.

Common Use Cases and Queries

Typical reporting scenarios include tracking pending registrations awaiting approval, auditing supplier onboarding volume by operating unit, and reconciling completed registrations against supplier records in Oracle Payables. A common query pattern filters by status and operating unit:

SELECT r.supplier_reg_id, r.supplier_name, r.supplier_number, r.registration_status, r.ou_id FROM pos.pos_supplier_registrations r WHERE r.registration_status = 'PENDING' AND r.ou_id = :p_ou_id;

Another frequent use is resolving the TCA party behind a registration to compare submitted data against master records:

SELECT r.supplier_name, p.party_name FROM pos.pos_supplier_registrations r, hz_parties p WHERE r.vendor_party_id = p.party_id AND r.supplier_reg_id = :p_reg_id;

Buyers also query the mapping between registrations and workflow records through POS_SUPPLIER_MAPPINGS to trace approval routing.

Related Objects

  • HZ_PARTIES — joined via POS_SUPPLIER_REGISTRATIONS.VENDOR_PARTY_ID = HZ_PARTIES.PARTY_ID; supplies the authoritative TCA party identity.
  • HR_ALL_ORGANIZATION_UNITS — joined via POS_SUPPLIER_REGISTRATIONS.OU_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID; scopes registrations to operating units.
  • FND_TERRITORIES — joined via POS_SUPPLIER_REGISTRATIONS.COUNTRY = FND_TERRITORIES.TERRITORY_CODE; resolves territory and address validation.
  • POS_SUPPLIER_MAPPINGS — references this table via POS_SUPPLIER_MAPPINGS.SUPPLIER_REG_ID; maps registrations to downstream workflow and supplier records.
  • PO_VENDORS / AP_SUPPLIERS — referenced through PO_VENDOR_ID once the registration is approved and a supplier record is created.
  • POS_SUPPLIER_REGISTRATIONS_PK and POS_SUPPLIER_REG_U1/U2 — unique constraints and indexes enforcing the primary and business keys.