Search Results cua_pending_batch

Overview

FA_MASSPTFR_PKG is the Oracle Assets (FA) package that implements the business logic behind the Mass Transfer feature. Mass Transfer allows an organization to move many assets between distributions, locations, general ledger accounts, and employees within a single controlled batch, rather than editing each asset individually. The package orchestrates validation and execution of these bulk asset reassignments for a given book and batch name, keeping the FA_MASS_EXTERNAL_TRANSFERS staging table synchronized with FA's core asset and distribution tables. It is an internal, "noship" API (classified OTHER) that is not intended as a public callable interface, and it is not referenced by any other documented package, indicating it is invoked directly by the Assets concurrent programs and forms that drive the mass transfer workflow.

Key Procedures and Functions

• DO_MASS_TRANSFER — The principal public driver procedure. It processes the transfer lines for a specified book type code and batch name, operating within a parent/child request partitioning scheme (parent request id, total requests, request number) so that large batches can be split across parallel concurrent workers. It accepts the calling interface identifier to distinguish the originating UI or program, tracks the maximum external transfer identifier consumed, and returns success and failure counts along with a return status to the caller. Internally it drives the private VALIDATE_TRANSFER function and manages the batch as a unit of work.
• ALLOCATE_WORKERS — The companion procedure that partitions the work of a mass transfer batch among multiple concurrent request workers. Given the size of the pending batch, it determines and assigns the workload that DO_MASS_TRANSFER subsequently processes per request number, enabling scalable parallel execution.

A private helper, VALIDATE_TRANSFER, is documented within the same body. It applies the business rules for a single transfer line—confirming the book type, batch, from/to asset and distribution, location, GL code combination, employee, transaction type, and transfer units/amount—and returns a boolean indicating whether the line is valid for posting. It is not part of the public surface.

Tables Accessed

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

• FA_MASS_EXTERNAL_TRANSFERS — the staging table holding individual transfer lines awaiting processing; the primary read/write work area.
• FA_MASS_UPDATE_BATCH_HEADERS — records the batch header that groups mass transfer lines and tracks batch status.
• FA_BOOKS and FA_BOOK_CONTROLS — supply book context, set of books, and period/control information needed to validate and post transfers.
• FA_DEPRN_PERIODS — validates the accounting period into which the transfer is being recorded.
• FA_DISTRIBUTION_HISTORY — the distribution records updated when assets are transferred between distributions, locations, GL accounts, or employees.
• FA_LOCATIONS — validates source and destination locations.
• FA_TRANSACTION_HEADERS — receives the transaction header generated for the transfer.
• GL_CODE_COMBINATIONS — validates the from/to general ledger account combinations.
• PER_PERIODS_OF_SERVICE — is consulted for period-of-service context relevant to the assets moved.
• DUAL and PLITBLM — used for utility/single-row selects and PL/SQL table handling.

Usage Notes

FA_MASSPTFR_PKG is invoked in the context of the Oracle Assets Mass Transfer concurrent program and the related mass transfer forms, not as a standalone public API. The caller submits a request against a book and batch; ALLOCATE_WORKERS splits the batch, and each spawned worker executes DO_MASS_TRANSFER for its assigned request number, returning success/failure counts and status that the program reports back. Because the package is flagged noship and has no downstream references, customizations should not call these procedures directly; instead, customers should use the supported Mass Transfer UI or concurrent program and rely on FA_MASS_EXTERNAL_TRANSFERS as the staging surface. When diagnosing a pending batch—the concept captured by the search term "cua_pending_batch"—inspect FA_MASS_EXTERNAL_TRANSFERS and FA_MASS_UPDATE_BATCH_HEADERS for lines that remain in an unprocessed or error status, and check the concurrent request output produced by the mass transfer workers. Corrective action is normally to re-run or resubmit the mass transfer concurrent program for the affected batch rather than to modify package internals.