Search Results do_super_group_change




Overview
Explore in AI Chat

Overview

The APPS.FA_SUPER_GROUP_CHANGE_PKG package is a seeded Oracle E-Business Suite PL/SQL package belonging to the Oracle Assets (FA) module. Its documented purpose is to manage changes to the "super group" classification of assets in a corporate book. Super groups are a mechanism used by Oracle Assets to consolidate depreciation for large volumes of similar, low-value assets (for example, a pool of identical personal computers or vehicles) so that depreciation is calculated and tracked at the group level rather than per individual asset.

In Oracle EBS 12.1.1 and 12.2.2, the package is held in the APPS schema with a documented status of VALID, and is classified in the ETRM knowledge base under API classification "OTHER" rather than as a formally published open interface or public API. This classification signals that the package is an internal utility supporting the Super Group functionality rather than a supported integration point. Its single documented entry point, DO_SUPER_GROUP_CHANGE, performs the processing required to reclassify assets into or out of a super group and to keep the associated depreciation and book balances consistent.

Key Procedures and Functions

  • DO_SUPER_GROUP_CHANGE — The sole documented procedure in the package. It is the driving routine that applies a super group change to the affected assets within a given book. When invoked, it evaluates the applicable super group rules, updates asset-level group membership, and recalculates or adjusts depreciation so that the impacted corporate book remains balanced. Because the package is classified as an internal utility, the procedure is not exposed as a supported public interface, and its parameter list is not published in the ETRM documentation.

No public functions are documented for this package. The ETRM metadata records only this one procedure, and no additional subprograms are catalogued.

Tables Accessed

The ETRM documentation lists the following base tables, referenced through APPS synonyms, as dependencies of this package:

  • FA_BOOKS — Stores the asset-level book records (cost, depreciation, and group membership), which are updated to reflect the new super group assignment.
  • FA_BOOK_CONTROLS — Holds book-level control settings, including the super group rules in force for the book, used to validate the change.
  • FA_SUPER_GROUP_RULES — Defines the rules governing super group naming and composition; consulted to determine the correct target group and its attributes.
  • FA_CALENDAR_PERIODS and FA_CALENDAR_TYPES — Provide the depreciation calendar context so that the change is applied in the correct open period.
  • FA_FISCAL_YEAR — Supplies fiscal year information needed to align period and year processing during the change.
  • PLITBLM — The standard Oracle Applications PL/SQL index-by table type used internally for array handling within the packaged logic.

These dependencies confirm that the package performs both read (rules and calendar lookups) and write (asset book balances) operations, consistent with an asset reclassification routine.

Usage Notes

The package is referenced by zero other packages in the ETRM metadata, which reinforces its nature as a standalone internal utility that supports the Super Group feature from the Oracle Assets user interface rather than from downstream code. In practice, super group changes are initiated by a user from the Oracle Assets forms (for example, the asset group definition screens) or through the concurrent programs that drive mass asset reclassification, and the form or concurrent manager invokes FA_SUPER_GROUP_CHANGE_PKG behind the scenes.

Customizations and integrations should not call this package directly. Because it is classified as "OTHER" and its parameters are undocumented, any direct invocation risks incompatibility across patches and upgrades. Where a super group change must be automated, the supported approach is to use the documented Oracle Assets open interfaces and concurrent programs, allowing the seeded logic to invoke this package internally. Developers reviewing the dependency chain should note the simple structure: the package depends only on the listed FA tables and standard types, and nothing else in the schema depends on it.