Search Results rosetta_table_copy_in_p11

Overview

PVX_UTILITY_PVT_W is a public wrapper package in the Oracle E-Business Suite APPS schema, belonging to the Oracle Partner Management (PVX) product family. It exposes a set of utility subprograms that support partner and channel-management functionality, most notably timezone conversion, history logging against partner entities, and business-day calculation. The package is defined with AUTHID CURRENT_USER, meaning its subprograms execute with the privileges of the invoking user rather than the definer; callers therefore require direct grants on the underlying objects. Version metadata in the package header ($Header: pvxwutls.pls 120.1 2008/02/28) indicates the source has been stable since Release 12.0 and is carried forward essentially unchanged into 12.1.1 and 12.2.2. The API classification is OTHER, and ETRM records five documented subprograms. The "_W" suffix follows the standard EBS convention for a thin public wrapper over an internal private package, PVX_UTILITY_PVT.

Key Procedures and Functions

• ROSETTA_TABLE_COPY_IN_P11 — Populates an internal PL/SQL table of type pvx_utility_pvt.log_params_tbl_type from four JTF_VARCHAR2_TABLE collections. The name references the Rosetta-style bulk parameter marshalling pattern used to move indexed VARCHAR2 arrays across the PL/SQL boundary, and the "P11" suffix identifies the specific parameter signature variant.
• ROSETTA_TABLE_COPY_OUT_P11 — The inverse operation, unpacking a log_params_tbl_type table back into the four JTF_VARCHAR2_TABLE output collections. Together the pair allows log-parameter data to be passed into, and returned from, other PVX subprograms as standard JTF table types.
• CONVERT_TIMEZONE — Converts a supplied input date between timezones using a user timezone identifier and a conversion-type indicator, returning the converted date. This supports partner-facing displays and interaction timestamps that must be normalized to the operating user's timezone.
• CREATE_HISTORY_LOG — Creates a history record for a partner-related entity. It accepts entity code and identifier, history category code, message code, partner identifier, access-level and interaction-level flags, comments, the four log-parameter collections, plus standard initialization and commit flags. It returns the EBS standard messaging triple (return status, message count, message data).
• GET_BUSINESS_DAYS — Returns the number of business days between a from-date and a to-date, supporting service-level, escalation, and response-time calculations within partner programs.

Tables Accessed

The only table documented as referenced through APPS synonyms is PLITBLM, the JTF/PLSQL table-to-block mapping table used by the JTF collection framework to materialize PL/SQL index-by tables as bind variables. It is characteristic of the Rosetta copy routines, which rely on that framework to marshal the JTF_VARCHAR2_TABLE_* parameters. Persistent history records produced by CREATE_HISTORY_LOG are written through the private layer, PVX_UTILITY_PVT, and are not enumerated in this wrapper's documented dependency list.

Usage Notes

This is a runtime API package rather than a concurrent-program entry point, and it is not referenced by any other documented package. It should not be called from SQL, since the API is designed for PL/SQL invocation and returns OUT parameters. Typical callers are Oracle Partner Management forms and page logic that need consistent timezone handling, history capture, or business-day arithmetic, and custom extensions that must create PVX history entries with the same semantics as the base product. Because the package is AUTHID CURRENT_USER, custom code should invoke it as APPS or ensure the executing schema holds execute privileges on PVX_UTILITY_PVT_W and the necessary object grants. The ROSETTA_TABLE_COPY_IN_P11 and ROSETTA_TABLE_COPY_OUT_P11 subprograms are utility plumbing intended for use in conjunction with CREATE_HISTORY_LOG, converting between the internal log-parameter table type and the JTF collections exposed on the public signature. In both 12.1.1 and 12.2.2 the documented behavior is identical.