Search Results approve_supplier_reg

Overview

APPS.POS_VENDOR_REG_PKG is the core PL/SQL package that implements the supplier registration lifecycle within Oracle iSupplier Portal in Oracle E-Business Suite 12.1.1 and 12.2.2. The package encapsulates the business logic required to capture, validate, submit, approve, and reject supplier registration requests originating from prospective and existing suppliers. It operates against the POS_SUPPLIER_REGISTRATIONS model, which stores registration header information in normalized form across approval, address, business classification, and account generation entities. The package adheres to the Oracle Application Framework API conventions, returning standardized status codes via FND_API (g_ret_sts_success, g_ret_sts_error) and accumulating messages through FND_MSG_PUB for downstream consumption by the calling user interface.

In the ETRM 12.2.2 classification, the package is designated as an OTHER API type, indicating it is an internal implementation package rather than a formally published public API. It is referenced by two other packages in the EBS schema, which is consistent with its role as a shared service layer for supplier registration processing.

Key Procedures and Functions

• APPROVE_SUPPLIER_REG — Executes the approval workflow for an existing supplier registration, transitioning the registration to approved status and triggering the downstream creation or update of the supplier record in the payables and trading community tables.
• REJECT_SUPPLIER_REG — Processes a rejection action for a registration currently pending approval, recording the decision and any associated reason so that the requester can be notified.
• SUBMIT_SUPPLIER_REG — Validates and submits a supplier registration from a saved or draft state into the approval queue, invoking the required attribute validation logic.
• SEND_SAVE_FOR_LATER_NTF — Issues the notification that a supplier has saved a partially completed registration for later submission.
• IS_OU_ID_VALID — Validates that a specified operating unit identifier is valid and accessible in the current context.
• IS_SUPPLIER_NUMBER_UNIQUE — Checks supplier number uniqueness to prevent duplicate supplier creation.
• IS_TAXPAYER_ID_UNIQUE — Enforces uniqueness of the taxpayer identifier across the supplier population.
• IS_DUNS_NUM_UNIQUE — Enforces uniqueness of the D-U-N-S number during registration.
• IS_TAXREGNUM_UNIQUE — Enforces uniqueness of the tax registration number supplied by the registrant.
• NOTIFY_BANKING_APPROVER — Generates the notification directed at banking approvers when banking information requires their review.
• VALIDATE_REQUIRED_USER_ATTRS — Validates mandatory user attributes captured during registration against the configured attribute requirements.

Tables Accessed

The package maintains registration data through POS_SUPPLIER_REGISTRATIONS and its dependent tables POS_ADDRESS_REQUESTS, POS_ACNT_GEN_REQ, POS_BUS_CLASS_REQS, POS_ATTRPG_CONFIG, and POS_SUPPLIER_MAPPINGS. Supplier and site records are read from AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL, while trading community validation relies on HZ_PARTIES, HZ_PARTY_USG_ASSIGNMENTS, HZ_CLASS_CODE_RELATIONS, and HZ_CODE_ASSIGNMENTS. Configuration and framework data are sourced from FND_USER, FND_PROFILE_OPTION_VALUES, FND_ATTACHED_DOCUMENTS, EGO_DATA_LEVEL_B, and EGO_PAGES_TL.

Usage Notes

POS_VENDOR_REG_PKG is invoked primarily from the iSupplier Portal supplier registration pages and from the internal supplier approval worklist. Customizations and extensions should call the approval, rejection, and submission procedures rather than updating POS_SUPPLIER_REGISTRATIONS directly, since the package enforces status transitions, message propagation, and notification generation. Because the package locks the registration row during review, concurrent invocations against the same supplier_reg_id are serialized; callers should handle the standard error message POS_SUPPLIER_REG_INVALID_ID when a lock cannot be obtained.