Search Results pos_request_utils_pkg




Overview
Explore in AI Chat

Overview

POS_REQUEST_UTILS_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the "OTHER" API category in the ETRM 12.2.2 repository. It belongs to the Oracle iSupplier Portal / Sourcing (POS) product family, which governs supplier self-service registration, sourcing events, and supplier-facing workflow interactions. The package provides a utility layer that internal PL/SQL logic and workflow components call to register, validate, approve, and retrieve supplier and contact information associated with sourcing and registration requests. Because it is a package body rather than a standalone API, its procedures are intended primarily for internal consumption by other POS packages and Oracle Workflow activities rather than as a formally published integration interface. The object resides in a VALID state and is fully compiled against the APPS schema in release 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented package exposes four procedures/functions:

  • POS_SRC_REGISTER_SUPPLIER — Registers a supplier within the sourcing context, creating or updating the registration record used to track that supplier's participation in a sourcing event or registration flow.
  • POS_SRC_APPROVE_RFQ_SUPPLIER — Handles approval of a supplier associated with an RFQ (Request for Quotation), moving the supplier through the approval state required before it can participate in the sourcing event.
  • POS_SRC_GET_SUPPLIER_DET — Retrieves supplier detail information, returning the attributes needed by calling processes to display or validate supplier data during sourcing activities.
  • POS_GET_CONTACT_APPROVED_DET — Retrieves approved contact detail, returning the contact information for a supplier or registration once that contact has passed approval.

Parameter lists are not documented and should not be assumed; the procedures are described here solely by their business purpose.

Tables Accessed

Through APPS synonyms the package reads and writes the following documented tables:

  • FND_USER — Accessed to resolve the application user identity associated with the supplier contact or registering party, linking portal users to their EBS login.
  • POS_CONTACT_REQUESTS — The contact-level registration and approval record. The package inserts, updates, and queries rows here to manage contact approval status and to return approved contact detail.
  • POS_SUPPLIER_REGISTRATIONS — The supplier registration header, used by the registration and approval procedures to create and progress supplier registration records.

Additional dependencies visible in the metadata include PO_VENDORS, PO_VENDOR_SITES_ALL, POS_SUPPLIER_USERS_V, POS_VENDOR_REG_PKG, POS_SPM_WF_PKG1, POS_ORG_HASH_PKG, POS_URL_PKG, and FND_API, indicating the package also reads vendor master data, resolves supplier user information, and integrates with Oracle Workflow and the FND API error-handling framework.

Usage Notes

POS_REQUEST_UTILS_PKG is invoked indirectly. It is referenced by one other database object, and is not referenced by any external database object per the dependency report, confirming it acts as a supporting utility rather than a public entry point. Typical invocation occurs from supplier registration and sourcing pages in iSupplier Portal, from Oracle Workflow function activities in the supplier registration and RFQ approval processes, and from sibling POS packages such as POS_VENDOR_REG_PKG and POS_SPM_WF_PKG1. Custom code should treat these procedures as internal: callers should respect the same FND_API message conventions the package uses for success and error signaling, avoid direct DML on POS_CONTACT_REQUESTS and POS_SUPPLIER_REGISTRATIONS, and rely on the documented procedures to keep registration and approval state consistent. Because the package ships with standard EBS and is not a formalized public API, extensions should be developed against the supported supplier registration interfaces rather than by modifying this package body.