Search Results register_partner_user

Overview

PV_USER_MGMT_PVT_W is a public wrapper package within the Oracle E-Business Suite Partner Management (PV) product family. It exposes the private PL/SQL business logic of PV_USER_MGMT_PVT to external callers through a set of thin, API-compliant entry points. Its principal business function is the registration of trading partners and their associated system users, a core operation in Oracle Partner Management and the Oracle Partner Network (OPN) registration flows. The package is classified as an OTHER API in the ETRM metadata, meaning it is not a fully documented, formally supported public interface but rather an internal wrapper surfaced for specific integration use cases.

The "_W" suffix follows Oracle EBS convention for wrapper packages that adapt a private PL/SQL package for invocation by forms, concurrent programs, or other callers requiring the standard FND API interface signature. Callers searching for "register_partner_and_user" will land here because this package provides the externally visible procedure of that name.

Key Procedures and Functions

The package documents four procedures:

• REGISTER_PARTNER_AND_USER — The primary business procedure. It registers a partner of a specified partner type together with an associated user in a single transactional unit. It accepts the standard FND API control parameters (API version, message list initialization, and commit flags), a partner type discriminator, and returns the standard return status, message count, and message data. Additional parameters carry the partner and user attribute values, many defaulting to FND_API.G_MISS_CHAR or a sentinel number to indicate "not supplied."
• REGISTER_PARTNER_USER — A parallel registration procedure that creates a partner user association, accepting the standard FND control parameters and returning the same status, count, and data outputs. It carries its own set of defaulted attribute parameters for the user record.
• ROSETTA_TABLE_COPY_IN_P5 — A utility procedure used by the Rosetta/BPEL integration layer to marshal an inbound JTF_VARCHAR2_TABLE_100 collection into the private package's PARTNER_TYPES_TBL_TYPE PL/SQL table. It supports bulk transfer of partner type values across the API boundary.
• ROSETTA_TABLE_COPY_OUT_P5 — The inverse utility, copying the private PARTNER_TYPES_TBL_TYPE table content back out into a JTF_VARCHAR2_TABLE_100 collection for consumption by the calling integration service.

Tables Accessed

According to the documented metadata, the package references the PLITBLM table via an APPS synonym. PLITBLM is a standard Oracle EBS interim/staging table used to hold denormalized data during processing, typically as a temporary store for values passed between layered PL/SQL calls or between integration tiers. In this context it supports the registration flow by staging partner type or user attribute values that the private package consumes when building the partner and user records. The metadata lists no other referenced tables, indicating that the substantive DML against partner and user base tables is performed by the underlying private package PV_USER_MGMT_PVT rather than by the wrapper itself.

Usage Notes

PV_USER_MGMT_PVT_W is invoked when a calling program—typically an Oracle Partner Management registration form, a concurrent program, or a custom integration service—needs to register a partner and user without directly depending on the private package. The Rosetta copy procedures indicate it is also surfaced as a web service or BPEL-invoked operation, where collection-based data must be converted between the SOA layer's typed tables and the private package's PL/SQL table structures.

Callers should supply a valid API version number, choose the commit flag according to their transaction control requirements, and always inspect X_RETURN_STATUS together with X_MSG_COUNT and X_MSG_DATA for error handling. Because the ETRM classification is OTHER and the metadata is limited, customizations should avoid tight coupling to the defaulted attribute parameters and should verify behavior against the target release, as the source header indicates the package has been stable since 2006 but remains subject to patch-level changes across 12.1.1 and 12.2.2.