Search Results update_seed_row

Overview

The APPS.PV_REFERRAL_STATUS_MAPS_PKG package body is a PL/SQL API belonging to the Oracle EBS Partner/Channel Management (PV) product family. Its seed header, pvxtrfmb.pls 120.0, indicates it is a seed data maintenance package rather than a runtime transaction API, which is consistent with its ETRM classification of OTHER. The package manages the PV_REFERRAL_STATUS_MAPS entity, the cross-reference table that maps a referral's internal status_code to an externally visible map_status_code for a given benefit_type. This mapping allows the application to translate internal referral lifecycle states into partner-facing or user-facing statuses without altering the stored transactional data. The body implements the standard Oracle Application Object Library (AOL) seed-data API pattern: insert, lock, update, delete, and load row procedures, each decorated with the WHO columns (creation_date, created_by, last_update_date, last_updated_by, last_update_login) and an object_version_number for optimistic locking.

Key Procedures and Functions

ETRM documents five procedures in this package; no functions are exposed.

• INSERT_ROW — Inserts a single referral status map row. It accepts the referral status map identifier and object version number as IN OUT NOCOPY parameters and the attribute columns as IN parameters. The insert uses DECODE against FND_API.g_miss_num, FND_API.g_miss_char, and FND_API.g_miss_date to convert the API's "miss" sentinels into NULL, satisfying the AOL API convention. The source references the REFERRAL_STATUS_MAP_ID primary key and the OBJECT_VERSION_NUMBER column.
• LOCK_ROW — Acquires a row-level lock by selecting OBJECT_VERSION_NUMBER, BENEFIT_TYPE, STATUS_CODE, and MAP_STATUS_CODE from PV_REFERRAL_STATUS_MAPS with a FOR UPDATE OF clause filtered on REFERRAL_STATUS_MAP_ID. It validates the caller-supplied object version and attribute values against the persisted values, returning an error if they no longer match. This protects concurrent updates in multi-user forms.
• UPDATE_ROW — Updates an existing map record after a successful LOCK_ROW, applying the change to the mapping attributes and advancing the object version number.
• DELETE_ROW — Physically removes a referral status map row identified by its primary key, again after lock validation.
• LOAD_ROW — The seed-data entry point. It performs the insert-or-update logic required to install or upgrade mapping data from a seed loader such as FNDLOAD, tolerating pre-existing rows and refreshing them to the shipped values.

Tables Accessed

The package operates on a single documented table, PV_REFERRAL_STATUS_MAPS, referenced through the APPS synonym. Reads are performed by LOCK_ROW and by LOAD_ROW's existence check; writes are performed by INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOAD_ROW. No other packages are documented as being referenced by this package, and the package is referenced by zero other packages, confirming it is a leaf-level seed maintenance API rather than a shared service.

Usage Notes

Because the package is a seed-data API, it is normally invoked by Oracle's seed loader infrastructure during installation, patching, or upgrade of the PV product, rather than by end users directly. Subscription forms in the Partner Management module may call LOCK_ROW and the modify routines through the standard AOL row-handler pattern when administrators maintain referral status mappings interactively. Customizations and data-migration scripts should call LOAD_ROW in preference to direct DML so that OBJECT_VERSION_NUMBER and the WHO audit columns remain consistent. The user search term update_seed_row does not correspond to a procedure in this package; the equivalent seed-update behavior is provided by LOAD_ROW and UPDATE_ROW. Callers must observe the IN OUT NOCOPY semantics of the identifier and version parameters and supply FND_API "miss" sentinels where a column should be defaulted to NULL.