Search Results pft_acct_rel_cons_rules

Overview

The APPS.PFT_BR_ACCT_REL_CONS_PVT package body is a private PL/SQL component within the Oracle E-Business Suite (EBS) Treasury and risk management / financial consolidation framework. Its principal business function is to support the lifecycle management of Account Relationship Consolidation Rule definitions. Consolidation rules in EBS define how balances from source account relationships are aggregated, eliminated, or otherwise mapped into target consolidation entities. This package isolates the low-level record-handling logic required to copy and delete the constituent detail records of such rule definitions, allowing higher-level public APIs to manipulate complete Account Relationship Consolidation Rule objects as reusable templates.

The package is classified as PVT (private), indicating it is not a supported public API and is intended for internal consumption by sibling packages and framework components. The single documented table reference, PFT_ACCT_REL_CONS_RULES, confirms its role as a persistence-layer helper for consolidation rule metadata. The header revision 120.0 dated 2005/06/06 is consistent with the earlier-generation PFT object family that has been preserved and carried forward across the 12.1.1 and 12.2.2 release streams.

Key Procedures and Functions

Two procedures are documented for this package body:

• COPYOBJECTDEFINITION — The public body of the package. Its documented purpose is to create all the detail records of a new Account Relationship Consolidation Rule definition (the target) by copying the detail records of another existing rule definition (the source). This supports duplicating a consolidation rule as a starting point for a new definition, and internally it delegates to the private CopyAcctRelConsRec helper. Because it is a procedure, it does not return a value; callers are expected to pre-allocate the target object definition identifier.
• DELETEOBJECTDEFINITION — Removes the detail records associated with a given Account Relationship Consolidation Rule definition. It is the counterpart operation to the copy routine and is typically invoked when a rule definition is deleted, so that no orphaned consolidation rule records are left behind in the underlying table.

Both procedures are driven by an object definition identifier, which is the standardized handle used throughout the PFT framework to reference a logical definition entity. The private specification also declares CopyAcctRelConsRec and DeleteAcctRelConsRec as the record-level workers that perform the actual table operations.

Tables Accessed

The documented table referenced by this package is PFT_ACCT_REL_CONS_RULES, accessed through an APPS synonym. This table stores the detail records that make up an Account Relationship Consolidation Rule definition — that is, the individual rule lines that describe how source account relationships are consolidated into target relationships or entities. The CopyObjectDefinition procedure reads the rows belonging to the source object definition and inserts equivalent rows for the target object definition, stamping them with the supplied user and creation date. The DeleteObjectDefinition procedure removes the rows associated with the object definition being discarded. No other tables are documented as being touched, which underscores the focused, single-purpose nature of the package.

Usage Notes

As a private (PVT) package, PFT_BR_ACCT_REL_CONS_PVT is not intended to be called directly by end users or by external customizations. In a standard Oracle EBS 12.1.1 or 12.2.2 environment it is invoked by the framework that manages Account Relationship Consolidation Rule definitions, most commonly as a consequence of a user action in the relevant setup or consolidation configuration form — for example, when a user copies or deletes a consolidation rule definition. The ETRM metadata records that this package is referenced by zero other packages, which suggests it is a leaf-level utility whose callers invoke it directly rather than through further nesting, or whose callers are not tracked within the same metadata set.

Because the procedures rely on the caller to supply valid object definition identifiers, created-by user identifiers, and creation dates, any direct usage in custom code must first obtain those values from the authoritative definition repository. Functional administrators should treat the package as an implementation detail: the supported interface for consolidating account relationship rules is the corresponding form or public framework API, not this private body. Changes to its internal record-handling logic between 12.1.1 and 12.2.2 should be assumed to be transparent to that supported interface.