Search Results mass_additions

Overview

FARX_MAD is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Fixed Assets "Mass Additions" process. Mass Additions is the mechanism by which large volumes of asset records can be introduced into Oracle Assets from external feeder systems — most commonly Oracle Payables — and then reviewed, adjusted, and posted as live asset additions in a given asset book. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, which is characteristic of interface and concurrent-processing code intended to run under the APPS account within a standard EBS session.

The package name FARX_MAD follows the FARX convention associated with Oracle Assets extension and interface utilities. The header comment records a version of 120.3 dated 2009, placing the shipped source in the 12.1.x lineage that carries forward into 12.1.1 and 12.2.2. FARX_MAD exposes a single documented entry point and acts largely as an orchestration layer around the Mass Additions interface tables and the Payables distribution data that feeds them.

Key Procedures and Functions

The ETRM metadata documents one procedure for this package:

• MASS_ADDITIONS — the sole documented callable in the package signature. It accepts a book, a queue name, a concurrent request identifier, and a user identifier as inputs, and returns the standard concurrent-program OUT parameters retcode and errbuf. The procedure drives the Mass Additions processing for the specified asset book, operating on the named queue (the queue that categorises prepared mass addition lines, such as POST, UNPOST, DELETE, and similar). The request_id and user_id parameters allow the routine to operate within the context of a concurrent request and to attribute processing to the submitting user, while retcode and errbuf provide the conventional success/failure signalling consumed by the concurrent manager and the request log.

No additional procedures or functions are documented in the package specification; the body is not part of the exposed metadata.

Tables Accessed

The documented table references (through APPS synonyms) span the Assets and Payables data model, which is consistent with a Mass Additions orchestration routine:

• FA_MASS_ADDITIONS — the core interface table holding candidate asset lines awaiting review and posting.
• FA_MASSADD_REP_ITF — the Mass Additions report interface table used to stage reporting output.
• FA_ADDITIONS_B — the base additions table written to when mass additions are posted as live assets.
• FA_BOOK_CONTROLS — book-level control settings that govern posting and period status.
• FA_CATEGORY_BOOKS, FA_CATEGORY_BOOK_DEFAULTS, FA_SYSTEM_CONTROLS — category-to-book assignments, default account and depreciation rules, and system-level controls used to derive asset attributes during posting.
• FA_LOOKUPS_TL — translated lookup values used for validation and code resolution.
• AP_INVOICES, AP_INVOICE_DISTRIBUTIONS — Payables invoice and distribution data that supplies source amounts, dates, and account information for merged mass additions.
• FND_CONCURRENT_REQUESTS, FND_CURRENCIES — concurrent request context and currency conversion information.

Usage Notes

FARX_MAD.MASS_ADDITIONS is most typically invoked from a concurrent program — the Mass Additions process launched from the Assets responsibility, or a related custom concurrent program that supplies the book, queue, request ID, and user ID. Because the parameters include retcode and errbuf, it conforms to the standard concurrent-program API signature and is suited to registration as a PL/SQL concurrent executable. The package is documented as being referenced by one other package, indicating it is called from a higher-level wrapper rather than directly by forms in all cases. Custom code should call the procedure only within an initialized EBS session under APPS, supplying a valid book and queue, and must check retcode for errors before relying on the outcome.