Search Results cua_pending_book

Overview

APPS.FA_CUA_MASS_UPDATE1_PKG is the core PL/SQL package body that implements the mass update engine for Oracle Assets (Fixed Assets) in Oracle E-Business Suite 12.1.1 and 12.2.2. Mass update enables organizations to apply a common set of changes to many assets simultaneously, such as reclassifying a category, adjusting depreciation attributes, transferring assets between books, or changing distribution lines. Rather than requiring users to open and modify each asset individually, the package accepts a defined batch of assets and applies the requested change consistently across the entire set.

The package is classified as an "OTHER" API rather than a formally published open interface, which indicates it is an internal implementation utility invoked by the Assets mass update forms and concurrent programs rather than a supported integration point for external systems. The source header identifies it as FACMUP1MB.pls, version 120.6, last updated in 2009, and it is referenced by two other packages within the EBS codebase. The user's search term cua_pending_book relates to mass update batches in which a target book has been staged but not yet processed; the package logic governs how those pending book changes are resolved and applied.

Key Procedures and Functions

The documented procedures and functions (nine total) perform distinct roles within the mass update process:

• GET_END_DATE — Returns the calculated end date for an asset's life based on the book, prorate date, and life in months. Historical bugfix 1055453 replaced an earlier cursor that queried calendar periods with a direct ADD_MONTHS calculation, because the original logic returned an incorrect date when the life extended beyond defined calendar periods.
• CALC_LIFE_ENDDATE — An overloaded companion to GET_END_DATE that populates an end date and returns error code, stage, and stack information through OUT NOCOPY parameters, supporting the API error-handling framework.
• CALC_LIFE — Computes the life value applied during a mass update, typically derived from the category-book relationship when no explicit life is supplied.
• UPDATE_CATEGORY — Applies category changes to the batch of assets, re-deriving associated category-book and method attributes.
• PROC_CONC — The concurrent program entry point that drives mass update processing when launched from the Submit Mass Update or Mass Copy concurrent programs.
• PROCESS_BATCH — Iterates the batch header and detail records, validating batch-level parameters and dispatching each asset for processing.
• PROCESS_ASSET — Handles update logic for a single asset, including book-level validation and pending book resolution.
• DO_TRANSFER — Executes transfers of assets between books or distribution sets as part of the batch.
• DO_ADJUSTMENT — Applies financial adjustments to asset cost or depreciation resulting from the mass update.

Tables Accessed

The package reads and writes a broad set of Assets tables through APPS synonyms. Batch control data resides in FA_MASS_UPDATE_BATCH_HEADERS and FA_MASS_UPDATE_BATCH_DETAILS, which store the user-defined selection criteria and per-asset staging rows, including any pending book assignment. Asset master and financial attributes are read from FA_ADDITIONS and FA_BOOKS, while book-level rules come from FA_BOOK_CONTROLS and FA_DEPRN_PERIODS. Category and method derivation relies on FA_CATEGORIES, FA_CATEGORY_BOOKS, and FA_METHODS. Calendar-related calculations reference FA_CALENDAR_PERIODS, FA_CALENDAR_TYPES, and FA_FISCAL_YEAR. Distribution changes use FA_DISTRIBUTION_HISTORY and FA_HIERARCHY_DISTRIBUTIONS, and lease-based assets are validated against FA_LEASES.

Usage Notes

FA_CUA_MASS_UPDATE1_PKG is invoked internally by the Oracle Assets mass update forms and by the Mass Update concurrent program (often referred to in the context of CUA — common user access — mass update functionality). It is not intended for direct invocation from custom code; organizations requiring programmatic mass updates should use the supported FA_MASS_* open interfaces or the Assets public APIs. Because the package manipulates FA_BOOKS and FA_MASS_UPDATE_BATCH_* directly, any custom call risks bypassing standard validation and audit logic. When troubleshooting a "cua_pending_book" condition, the relevant diagnostics are the batch header and detail rows, which reveal the target book staged for processing and whether PROCESS_BATCH has advanced the batch to completion.