Search Results ld_start_date

Overview

JA_CN_PS_FA_BI_EXP_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. Its name and dependencies identify it as part of the Oracle Financials for China localization layer (the JA_CN prefix denotes the China country-specific module). The suffix FA_BI_EXP indicates that the package extracts or exports Fixed Asset (FA) balance and basic information for Chinese statutory reporting and statutory ledger integration.

In the Chinese localization, fixed asset data must be reconciled with the Chinese statutory ledger and reported in formats required by local tax and accounting authorities. This package produces that fixed asset basic information, drawing on asset book controls, depreciation periods, transaction history, and the Chinese statutory ledger structures exposed through JA_CN_LEDGER_LE_BSV_GT. It is classified as a private, internal helper package (API classification OTHER); it is not referenced by any other database object, so it is invoked directly by concurrent programs, forms, or the localization setup rather than through a public API surface.

Key Procedures and Functions

• ADD_BASIC_INFORMATION — The single documented program unit in this package body. It assembles and returns or emits the "basic information" set for fixed assets required by the Chinese statutory FA BI export. In practice it gathers corporate book and asset details for a given ledger, legal entity, and depreciation period, formats them into the layout expected by the downstream Chinese localization report, and writes the output (typically via FND_FILE for concurrent program output). No parameter list is documented in the ETRM metadata; the routine should be treated as an internal procedure whose interface is not published for external callers.

Tables Accessed

The documented dependency list shows the package reading the following base and localization objects:

• FA_ADDITIONS_V — the asset additions view supplying asset identification and descriptive attributes.
• FA_BOOK_CONTROLS_SEC — the security-enabled book control view, used to restrict processing to the books the requesting user or responsibility may access.
• FA_CATEGORY_BOOKS — category-to-book setup, providing the depreciation rules and category context for each asset.
• FA_DEPRN_PERIODS — depreciation period calendar, used to determine the fiscal/accounting period ranges to be reported.
• FA_DISTRIBUTION_HISTORY — assignment of assets to accounting distributions (cost centers, accounts), needed for the statutory ledger layout.
• FA_TRANSACTION_HEADERS — fixed asset transaction headers for additions, adjustments, retirements, and transfers within the reporting window.
• GL_PERIOD_STATUSES — General Ledger period status, used to confirm that the reported periods are open or closed as expected.
• JA_CN_LEDGER_LE_BSV_GT — the Chinese localization ledger/legal entity balance summary global temporary table, which ties fixed asset amounts to the Chinese statutory ledger.

It additionally calls JA_CN_CFS_DATA_CLT_PKG, JA_CN_UTILITY, FND_FILE, and FND_LOG for data collection, utility conversion, file output, and debug logging respectively.

Usage Notes

JA_CN_PS_FA_BI_EXP_PKG is an internal localization utility. It is expected to be invoked from a Chinese Fixed Asset statutory reporting concurrent program or from localization setup code that needs the FA basic information extract. Because the package body is not referenced by any other database object, direct calls must come from an external driver such as a concurrent program executable or a form-level routine.

All table references resolve through APPS synonyms, so the package relies on standard APPS grants and does not bridge schemas directly. The inclusion of FA_BOOK_CONTROLS_SEC indicates that output is filtered by book security, and FND_LOG support means the routine can be traced at a chosen logging level during troubleshooting. The package name matches its own dependency entry, confirming internal self-reference used by the collection logic. The object is VALID in both 12.1.1 and 12.2.2, and its behavior is essentially identical across the two releases because it operates on the same underlying FA and GL data model.