Search Results psb_defaults_s

Overview

APPS.PSB_COPY_DATA_EXTRACT_PVT is a private PL/SQL package body in the Oracle E-Business Suite HR/Payroll product family (product code PSB, associated with Oracle Advanced Benefits and related HRMS configuration utilities). Its core business function is to support the copy or duplication of compensation data extract configuration across entities, defaults, attributes, position sets, and element definitions. Configuration data such as default rules, span item attributes, and entity set memberships are frequently reused between business groups or benefit plans; manually re-keying such hierarchies is error-prone and time consuming. This package provides the programmatic engine that clones an existing configuration graph so administrators can replicate a working setup into a new context without rebuilding each component.

The package is classified as PVT, indicating that it is an internal implementation package rather than a public API. It is designed to be invoked by the data extract copy process and by adjacent private packages rather than by external consumers.

Key Procedures and Functions

The ETRM metadata documents five entry points within the package body:

• COPY_ATTRIBUTES — Duplicates attribute definitions and their associated values (typically span item attributes) from a source configuration to a target configuration. It works in conjunction with PSB_ATTRIBUTE_VALUES_PVT and the PSB_ATTRIBUTE_VALUES_S sequence.
• COPY_ELEMENTS — Replicates element-related records used in data extracts, iterating over pay element definitions and their options so that element-driven extracts remain functional after the copy.
• COPY_POSITION_SETS — Copies account position sets, delegating core validation and insert logic to PSB_ACCOUNT_POSITION_SET_PVT while reading from PSB_ACCOUNT_POSITION_SETS.
• COPY_DEFAULT_RULES — Duplicates default rule configuration, including default assignments, account distributions, and allocation rule percentages, using the corresponding _PVT packages and _S sequences to generate new primary keys.
• GET_DEBUG — A utility function that returns the debug flag state, allowing the copy routines to emit diagnostic output through FND_FILE and FND_MESSAGE when FND_GLOBAL logging is enabled.

No public parameter signatures are documented, and the procedures should be treated as internal call sites of the copy process.

Tables Accessed

The package reads from and writes to the following documented tables (via APPS synonyms):

• PSB_DATA_EXTRACTS — the master extract definition that anchors the copy operation.
• PSB_DEFAULTS, PSB_DEFAULTS_S, PSB_DEFAULT_ACCOUNT_DISTRS, PSB_DEFAULT_ACCOUNT_DISTRS_S, PSB_DEFAULT_ASSIGNMENTS, PSB_DEFAULT_ASSIGNMENTS_S — default rule headers, account distributions, and assignment rows, with the _S tables supplying surrogate key values.
• PSB_ATTRIBUTE_VALUES, PSB_ATTRIBUTE_VALUES_S — attribute value rows attached to defaults.
• PSB_ACCOUNT_POSITION_SETS — position set definitions referenced by defaults.
• PSB_ENTITY, PSB_ENTITY_S, PSB_ENTITY_ASSIGNMENT, PSB_ENTITY_SET, PSB_ENTITY_SET_S — entity, entity assignment, and entity set structures that scope the extract.
• PSB_PAY_ELEMENTS, PSB_PAY_ELEMENT_OPTIONS — element definitions consumed by COPY_ELEMENTS.
• PSB_SET_RELATIONS — relationships between sets that must be recreated for the new configuration.

Usage Notes

PSB_COPY_DATA_EXTRACT_PVT is invoked indirectly. It is referenced by one other package and is not referenced by any database object itself, confirming its role as a leaf-level implementation library. Typical invocation occurs from the PSB copy data extract concurrent program or from the associated configuration form, which collects a source and target extract identifier and then delegates to these procedures. Because it depends on FND_API, FND_MSG_PUB, and FND_FILE, it participates in the standard EBS error-handling and logging framework, and GET_DEBUG controls diagnostic verbosity. Custom code should not call this package directly; developers extending extract-copy functionality should use the supported public API or the seeded concurrent program instead, as the PVT designation signals that the interface may change without notice across 12.1.1 and 12.2.2 releases.