Search Results pqp_assignment_attributes

Overview

APPS.PQP_COPY_EAT is a PL/SQL package body in the Oracle E-Business Suite HRMS/Payroll module (product code PQP) that supports the Extract Attributes framework used for payroll and benefits data extracts. The package name abbreviates "copy extract attributes." Its primary business function is to clone the configuration of Extract Attribute definitions — including the associated user-defined tables — from one extract definition to another, prefixing the newly created objects so that the copied structures can coexist with the originals within the same business group.

This functionality is significant during implementations, upgrades, and testing cycles, where a working extract configuration must be duplicated and retargeted without manually re-keying every attribute row. The header comment pqpcpext.pkb 115.1 indicates the file has been stable since an early release of the product line, and the presence of the package in APPS under 12.1.1 and 12.2.2 confirms it remains part of the shipped EBS codebase. The package is classified as OTHER, meaning it is not a formally published open interface but is still callable from other internal code.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package body:

• COPY_EXTRACT_ATTRIBUTES — Copies the set of Extract Attribute rows belonging to a source extract definition into a newly created extract definition. It accepts identifiers for the current and new extract definitions, a prefix used when naming the copied objects, and a business group identifier that scopes the new configuration. Internally, the procedure opens a cursor over PQP_EXTRACT_ATTRIBUTES keyed by the current extract definition, loops through each attribute, and for each one creates a corresponding user table and attribute record under the new definition. It retrieves the new extract name from BEN_EXT_DFN and resolves user table names from PAY_USER_TABLES. A validation check raises the predefined message PQP_230541_EXTRACT_PREFIX_NULL when no prefix is supplied, since the prefix is mandatory for generating unique object and table names. Sequence values for the new attribute rows are drawn from PQP_EXTRACT_ATTRIBUTES_S.

No other procedures or functions are documented in the ETRM extraction. However, the body text references a companion package, PQP_COPY_UDT, whose COPY_USER_TABLE function performs the underlying user table duplication that COPY_EXTRACT_ATTRIBUTES depends upon. This delegation keeps responsibility for user table cloning in a separate package.

Tables Accessed

• PQP_EXTRACT_ATTRIBUTES — The driving table. The procedure reads all attribute rows for the source extract definition and writes the copied attribute rows for the new definition.
• PQP_EXTRACT_ATTRIBUTES_S — Sequence used to obtain primary key values for the newly inserted extract attribute records.
• BEN_EXT_DFN — The extract definition table, read to obtain the name of the target (new) extract definition, which is used when generating names for the copied attributes.
• PAY_USER_TABLES — The payroll user table registry, read to resolve the user table name associated with a given user_table_id, supporting correct naming of the cloned user tables.
• DUAL — Used solely to fetch the next sequence value.

Usage Notes

This package is typically invoked from the Oracle HRMS Extract Definition setup forms or from configuration utilities that provide users with a "copy" or "duplicate" action against an existing extract definition. It may also be called from concurrent programs or from custom migration scripts that programmatically clone extract configurations between business groups or environments. Because the procedure writes directly to extract attribute and user table structures, it should be run only by users with appropriate HRMS setup privileges and within a controlled transaction, and callers should ensure a valid business group and a non-null prefix are supplied. The package is referenced by one other package in the EBS schema, indicating it is a dependent component of a broader extract administration flow rather than an entry point that end users call directly.