Results for “pos_sup_products_services”

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

Overview

The POS_SUP_PRODUCTS_SERVICES table is a core data object within the Oracle E-Business Suite iSupplier Portal (POS) module. It stores supplier product and service classification records, allowing buyers and suppliers to categorize the goods and services a supplier is capable of providing. The object resides in the POS schema and is registered as VALID in ETRM releases 12.1.1 and 12.2.2. This classification data supports supplier registration, sourcing qualification, and spend categorization activities within the iSupplier Portal framework.

From a Data Vault modeling perspective, the mined FK structure suggests that this is a standalone object, indicating it behaves as an independent hub or reference entity rather than a dependent link or pure satellite. Practically, it functions as a classification hub keyed on CLASSIFICATION_ID, with descriptive attributes (the flexfield segments and status) acting as satellite-style payload. This heuristic should be treated as a modeling suggestion rather than a mandated design.

Key Information Stored

The table is physically documented with 29 columns. The most significant include:

• CLASSIFICATION_ID — the surrogate primary key, uniquely defined by POS_SUP_PRODUCTS_SERVICES_PK and reinforced by the unique index POS_SUP_PRODUCTS_SERVICES_U1, making it the strongest business-key candidate.
• VENDOR_ID — identifies the supplier to whom the classification belongs; the primary linkage to the supplier master.
• SEGMENT1 through SEGMENT20 — the key flexfield segments that capture the product and service taxonomy assigned to the supplier. These carry the substantive classification payload.
• SEGMENT_DEFINITION — holds the flexfield structure definition controlling how the segments are interpreted.
• STATUS — indicates whether the classification record is active or inactive.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit and concurrency tracking.

Common Use Cases and Queries

Typical uses include supplier qualification reporting, iSupplier Portal self-service maintenance, and integration with sourcing or spend analysis. A common pattern retrieves active classifications for a supplier:

• SELECT classification_id, vendor_id, segment1, segment2, status FROM pos.pos_sup_products_services WHERE vendor_id = :vendor_id AND status = 'A';
• Reporting by segment value to determine how many suppliers fall into a given product or service category, joining to the supplier master on VENDOR_ID.
• Auditing additions and updates by filtering on CREATION_DATE or LAST_UPDATE_DATE ranges.
• Populating external procurement analytics extracts using the full SEGMENT1..SEGMENT20 set plus SEGMENT_DEFINITION for flexfield resolution.

Related Objects

Although the mined relationship data classifies this table as standalone, the following objects are the most significant references based on the documented join columns:

• POS_SUP_PRODUCTS_SERVICES_PK / POS_SUP_PRODUCTS_SERVICES_U1 — the primary key and unique index definitions over CLASSIFICATION_ID.
• Supplier master tables joined via VENDOR_ID (e.g., AP_SUPPLIERS / PO_VENDORS) for supplier name and status.
• iSupplier Portal supplier profile and registration views that surface classification data to suppliers.
• Sourcing and qualification objects that consume supplier product/service classification for eligibility screening.
• Spend and procurement analytics extracts keyed on VENDOR_ID and the flexfield segments.