Results for “pos_upgrade_users”

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

Overview

The POS_UPGRADE_USERS table is an operational tracking table within the POS schema, which provides the foundation for Oracle iSupplier Portal (ISP) in Oracle E-Business Suite 12.1.1 and 12.2.2. According to the ETRM object registry, the table is owned by the POS schema and carries a VALID status in the documented environment. Its stated purpose is to record all users that have been upgraded for iSupplier Portal, making it an audit and reconciliation artifact generated during the migration or onboarding of supplier and customer portal accounts.

The table is not a transactional or master-data entity. It is a staging and audit structure whose lifecycle is tied to upgrade programs that convert legacy supplier or customer records into ISP-enabled users. The ETRM metadata classifies this object heuristically as satellite-leaning based on its foreign-key topology. In Data Vault modeling terms, POS_UPGRADE_USERS behaves like a satellite: it records descriptive attributes and status flags about an upgrade event, attached by a foreign key to a hub entity, HZ_PARTIES. It is not itself a hub (no deduplicated business key of its own) nor a link (it does not resolve many-to-many relationships between two hubs). This classification should be treated as a modeling suggestion rather than a definitive architectural statement.

Key Information Stored

The documented physical schema for 12.2.2 contains 11 columns. Among the most significant are the following:

• USER_NAME — the ISP login or user identifier being upgraded; a primary business-key candidate for reconciliation reports.
• CUSTOMER_ID — foreign key to HZ_PARTIES, tying the upgraded user to the underlying trading partner or party record.
• VENDOR_ID and VENDOR_CONTACT_ID — identifiers linking the upgrade record to the supplier organization and its contact, where the upgraded party is a supplier rather than a customer.
• UPGRADED — status indicator that flags whether the upgrade completed successfully for that user.
• ERROR_MESSAGE — diagnostic text captured when an upgrade fails, essential for remediation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns providing the audit trail for when and by whom each row was inserted or amended.

The ETRM documentation does not publish a surrogate primary key column for this table, nor does it enumerate unique indexes. In the absence of a documented surrogate key, USER_NAME combined with the party or vendor identifiers serves as the practical business-key candidate for de-duplication.

Common Use Cases and Queries

The primary use case is post-upgrade verification: confirming which users were processed and identifying those that failed. A typical reconciliation query returns failed upgrades with their diagnostic messages:

• SELECT user_name, customer_id, vendor_id, error_message FROM pos.pos_upgrade_users WHERE upgraded = 'N';

A second use case counts successful upgrades by party to validate migration completeness against the expected supplier or customer population, joining to HZ_PARTIES for party names. A third use case supports audit reporting, using the WHO columns to prove when an upgrade batch ran and which concurrent program or user initiated it. Because the table is upgrade-scoped rather than transactional, it is generally queried directly and is not exposed through standard ISP self-service pages.

Related Objects

• HZ_PARTIES — joined via POS_UPGRADE_USERS.CUSTOMER_ID = HZ_PARTIES.PARTY_ID. This is the only documented foreign key and the principal relationship.
• HZ_CUST_ACCOUNTS — for resolving a party to its customer account context.
• PO_VENDORS / AP_SUPPLIERS — supplier master records referenced conceptually by VENDOR_ID and VENDOR_CONTACT_ID.
• FND_USER — the EBS user repository used to confirm whether the upgraded ISP login exists.
• ISP access-control views such as POS_SUPPLIER_USERS — used to compare pre- and post-upgrade user provisioning.

No PL/SQL APIs, forms, or concurrent program interfaces are documented in the ETRM excerpt for this table. Its population is presumed to occur through a one-time upgrade script or concurrent process executed during ISP implementation.