Results for “copy_record”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.FV_COPY_YE_RECORDS_PKG package is a Treasury/Year-End (YE) utility within the Oracle E-Business Suite Federal Financials and Treasury subsystem. Its name derives from the "FV" application prefix, which is associated with Treasury functionality (specifically the Year-End records management area, evidenced by the FV_YE_* table family). The package provides a single documented procedure, COPY_RECORD, whose purpose is to copy year-end grouping records from an existing source group into a newly defined grouping configuration.

In the EBS 12.1.1 and 12.2.2 releases, this package is classified by ETRM as an OTHER API, meaning it is not a formally published public API but rather an internal utility used by the Treasury application layer. It carries AUTHID CURRENT_USER, indicating that it executes with the privileges of the calling schema rather than the definer, which is consistent with a helper routine invoked from within the APPS schema context. The header comment traces the source file to FVYECPGS.pls, version 120.2.12010000.2, dated 2009/12/23, with modifications tied to Bug 1575992.

Key Procedures and Functions

The package exposes exactly one documented procedure:

• COPY_RECORD — Copies a year-end record definition from an existing group into a new treasury symbol and fund group context. Based on the documented parameter names, it accepts a ledger identifier, the source group identifier (the "old" group), the new time frame, the new fund group code, the new treasury symbol, and the closing method. The procedure's role is to replicate the year-end sequence and account composition associated with the original group so that a new group can inherit an equivalent structure without manual re-entry. Modification notes in the header reference Bug 1575992, which affected the time_frame and closing_method parameters.

No additional public functions or procedures are documented for this package. Internally it is expected to perform insert/select operations across the referenced tables to materialize the copied records.

Tables Accessed

The package references the following tables (by APPS synonym), which fall into distinct functional clusters:

• GL_LEDGERS — Supplies the ledger context; the ledger identifier parameter is typed from gl_ledgers.ledger_id, anchoring the copy to a specific accounting ledger.
• FV_YE_GROUPS — The primary year-end group definition table; the source group is selected here, and the closing method is sourced from this table.
• FV_TREASURY_SYMBOLS — Provides the treasury symbol and time frame attributes that determine where the copied records are targeted.
• FV_YE_GROUPS_ID_S — Sequence/identifier generator for new year-end group records.
• FV_YE_GROUP_SEQUENCES and FV_YE_GROUP_SEQUENCES_S — Hold the sequence definitions belonging to a group; the copy operation replicates these into the new group and generates their new identifiers.
• FV_YE_SEQUENCE_ACCOUNTS and FV_YE_SEQUENCE_ACCT_S — Hold the account assignments attached to each sequence; these are duplicated along with their parent sequences.
• DUAL — Used for simple single-row operations, such as sequence lookups or existence checks.

The consistent use of _S suffixed tables indicates Oracle sequence-backed identifier generation during the insert phase of the copy.

Usage Notes

As an internal Treasury utility, FV_COPY_YE_RECORDS_PKG.COPY_RECORD is typically invoked when users set up a new year-end group that mirrors an existing one. In the EBS 12.1.1 and 12.2.2 Treasury forms (the Fund/Year-End maintenance screens), this procedure would be triggered from a forms-based "Copy" action, where the user selects a source group and supplies the new time frame, fund group code, and treasury symbol. It is not registered as a concurrent program in its own right.

Because ETRM reports zero dependent packages, the procedure is a leaf node in the dependency graph — nothing else in the APPS schema calls it, reducing the blast radius of any modification. Custom code should avoid calling it directly unless the caller reproduces the exact ledger and group context required; the procedure assumes valid source data and does not appear to perform defensive validation beyond what the table constraints enforce. Testing should focus on the referenced Bug 1575992 behavior around time_frame and closing_method.