Search Results add_basic_information

Overview

JA_CN_PS_FA_BI_EXP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM API classification of OTHER. Its stated purpose, per the package header, is to export the Basic Account Information of Fixed Assets for Public Sector (PS) organizations operating within the Chinese localization (JA_CN) of Oracle EBS. The package is defined with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the definer, which is consistent with a reporting or export utility intended to be called from within the APPS execution context. The source file is identified as JACNFAAS.pls, with an internal module prefix constant GV_MODULE_PREFIX set to JA_CN_PS_FA_BI_EXP_PKG. The package was created on 10-AUG-2010 by Wuhua Liu, and the design traceability is captured in the document TDD_1213_FIN_GL_P_CNAOV2_FA.doc. It is documented in ETRM for both 12.1.1 and 12.2.2, where it functions as a specialized extraction layer over the standard Fixed Assets data model, restricted to the public sector accounting requirements of the Chinese localization.

Key Procedures and Functions

The package exposes a single documented public procedure, ADD_BASIC_INFORMATION. Its declared purpose is to export the Basic Account Information of Fixed Assets for public sector organizations. According to the parameter documentation embedded in the specification, the procedure accepts an input set describing the scope of the extraction: a legal entity identifier, a ledger identifier, an accounting year, a from-period, and a to-period. These parameters collectively define the accounting and organizational boundary within which fixed asset basic account information is gathered and returned. The procedure does not return a value through the specification signature; its behavior is oriented toward producing an export result set for downstream reporting or interface consumption. Because the ETRM metadata lists only this one procedure, no other callable units are documented for this package.

Tables Accessed

Although the package specification itself does not enumerate the tables it uses, the documented dependencies list the following APPS synonyms as referenced tables: FA_BOOK_CONTROLS_SEC, FA_CATEGORY_BOOKS, FA_DEPRN_PERIODS, FA_DISTRIBUTION_HISTORY, FA_TRANSACTION_HEADERS, GL_PERIOD_STATUSES, and JA_CN_LEDGER_LE_BSV_GT. These are consistent with the procedure's purpose. FA_BOOK_CONTROLS_SEC and FA_CATEGORY_BOOKS supply the depreciation book and category book configuration needed to determine which asset books and categories fall within scope. FA_DEPRN_PERIODS and GL_PERIOD_STATUSES are used to map the supplied accounting year and period range to open or valid depreciation and GL periods. FA_DISTRIBUTION_HISTORY and FA_TRANSACTION_HEADERS provide asset assignment and transaction-level detail underpinning the basic account information. JA_CN_LEDGER_LE_BSV_GT is a Chinese localization global temporary table that resolves the relationship between ledgers, legal entities, and balancing segment values, which is essential for correctly scoping the export to a legal entity and ledger combination.

Usage Notes

JA_CN_PS_FA_BI_EXP_PKG is typically invoked as a supporting utility rather than as a user-facing form handler. In practice it is called from concurrent program logic, from a PL/SQL wrapper, or from custom localization code that needs to extract fixed asset basic account information for public sector reporting in China. The package is referenced by one other package within the documented dependency set, indicating it participates in a broader localization call chain. Because it is declared AUTHID CURRENT_USER, callers must ensure the executing user has the necessary privileges on the underlying FA and GL objects; in the standard APPS concurrent manager context this is satisfied by the APPS schema itself. When invoking the procedure, the legal entity, ledger, accounting year, and period-from/period-to values must be supplied consistently with the GL period status data, since the procedure relies on period mappings to constrain the extraction. No initialization or cleanup steps are documented, and the specification defines no public constants other than the module prefix.