Search Results pos_profile_change_request_pkg




Overview
Explore in AI Chat

Overview

APPS.POS_PROFILE_CHANGE_REQUEST_PKG is a PL/SQL package in the Oracle E-Business Suite supplier lifecycle management (SLM) module, delivered in the APPS schema with a VALID status. It provides the approval and rejection processing logic for supplier profile change requests, the mechanism through which suppliers registered in iSupplier Portal submit proposed amendments to their company information and Oracle EBS administrators or approvers accept or decline those amendments. Profile change requests may target addresses, contacts, business classifications, and product and service offerings, and the package supports both single-request and multi-request (bulk) processing of each of these categories. By centralising the approval workflow logic, the package ensures that an approved change is propagated to the corresponding supplier records only after the request has passed the internal review process, thereby maintaining the integrity of the supplier master data held in the Oracle Trading Community Architecture (TCA) and supplier tables.

Key Procedures and Functions

The documented API enumerates twenty-nine procedures and functions. They fall broadly into four families, each concerning one type of change request:

Within each family, the single-request procedures act on one request identifier, while the MULT_ variants process a set of requests in a single call, which is the mode typically used by the administrative approval screens. The CHG_*_REQ_APPROVAL procedures handle the detailed approval of a change request, and FORMAT_ADDRESS performs address formatting, typically for display or storage consistency.

Tables Accessed

The package reads and writes several categories of tables through APPS synonyms. Request staging tables such as POS_ADDRESS_REQUESTS, POS_CONTACT_REQUESTS, POS_CONT_ADDR_REQUESTS, POS_BUS_CLASS_REQS, and POS_PRODUCT_SERVICE_REQUESTS hold the pending changes and their status. Business classification attributes are stored in POS_BUS_CLASS_ATTR and POS_BUS_CLASS_ATTR_S, and supplementary address notes in POS_ADDRESS_NOTES. Supplier mapping data resides in POS_SUPPLIER_MAPPINGS. Master data that is updated on approval is held in TCA tables including HZ_PARTIES, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_CONTACT_POINTS, and HZ_RELATIONSHIPS, with FND_USER used for approval audit and user context. The package also references POS_BUS_REC_TBL and PO_TBL_NUMBER as PL/SQL collection types.

Usage Notes

The package is referenced by POS_PRODUCT_SERVICE_UTL_PKG, POS_VENDOR_REG_PKG, and other packages, and is itself dependent on the SYS.STANDARD package. It is normally invoked indirectly from the iSupplier Portal and supplier management concurrent programs and forms when an approver acts on submitted change requests, rather than being called directly by end users. Customers extending the approval workflow should reuse these procedures instead of writing directly to the underlying request tables, so that approval side effects on TCA and supplier data remain consistent.