Search Results get_xml_tag

Overview

JA_CN_UTILITY is an Oracle E-Business Suite 12.1.1 / 12.2.2 PL/SQL package body owned by the APPS schema. It serves as a shared utility library for the JA (Asia/Pacific Localizations) China functionality set, centralizing low-level logic that is reused across the Chinese localizations of General Ledger and related financial modules. Its documented status is VALID, and it is classified as an "OTHER" API rather than a formal public application programming interface.

The package provides common services that other China-localization programs depend upon: resolving the ledger and chart of accounts context, validating flexfield and account structures, verifying accounting period ranges, retrieving lookup values and profile options, generating concurrent output, and producing XML output with correct character encoding. Because the metadata records that JA_CN_UTILITY is referenced by 83 other packages, it functions as a foundational dependency for the broader JA_CN module family rather than as an end-user-facing component.

Key Procedures and Functions

The package exposes 36 documented procedures and functions. The principal groups are:

• Context resolution: GET_SOB_AND_COA, GET_SOB, and GET_COA return the set of books (ledger) and chart of accounts context required by downstream China-localization routines.
• Validation: CHECK_PROFILE, CHECK_NAT_NUMBER, CHECK_ACCOUNT_LEVEL, CHECK_CASH_RELATED_ACCOUNT, and CHECK_ACCOUNTING_PERIOD_RANGE perform configuration, account, and period-range checks before processing proceeds.
• Account structure and flexfield access: FETCH_ACCOUNT_STRUCTURE, GET_BALANCING_SEGMENT_VALUE, and GET_LOOKUP_CODE / GET_LOOKUP_MEANING retrieve key flexfield structure and lookup information.
• Ledger and balancing segment support: POPULATE_LEDGER_LE_BSV_GT populates the ledger/legal-entity/balancing-segment value global temporary table used by other China reports and programs.
• Concurrent output and XML: OUTPUT_CONC, SUBMIT_CHARSET_CONVERSION, SUBMIT_XML_CHARSET_CONVERSION, CHANGE_OUTPUT_FILENAME, GET_XML_ENCODING, GET_XML_TAG, and ADD_SUB_ROOT_NODE manage concurrent output files, character-set conversion, and XML document generation with the correct encoding declarations and root/sub-root nodes.

Tables Accessed

The package reads application reference and configuration data primarily through APPS synonyms. Flexfield metadata is drawn from FND_FLEX_VALIDATION_TABLES, FND_FLEX_VALUES, FND_FLEX_VALUES_TL, FND_FLEX_VALUE_SETS, FND_ID_FLEX_SEGMENTS, FND_ID_FLEX_STRUCTURES, and FND_SEGMENT_ATTRIBUTE_VALUES. Ledger and accounting context is sourced from GL_LEDGERS, GL_CODE_COMBINATIONS, GL_ACCESS_SETS, GL_LEDGER_NORM_SEG_VALS, GL_LEDGER_RELATIONSHIPS, GL_PERIOD_STATUSES, and GL_SETS_OF_BOOKS. Lookups come from FND_LOOKUPS and FND_LOOKUP_VALUES, while China-localization configuration is read from JA_CN_DFF_ASSIGNMENTS, JA_CN_SYSTEM_PARAMETERS_ALL, and JA_CN_LEDGER_LE_BSV_GT. Concurrent processing support is provided via FND_CONCURRENT, FND_REQUEST, FND_FILE, FND_PROFILE, and the FND_LOG, FND_MESSAGE, and FND_FLEX_EXT utility packages. Dynamic SQL and XML generation rely on DBMS_SQL and DBMS_XMLGEN.

Usage Notes

JA_CN_UTILITY is not intended for direct end-user invocation. It is called programmatically by the 83 dependent packages documented in the ETRM as well as by China-localization concurrent programs and forms that require its validation, context-resolution, and XML-output services. Customizations and extensions to the JA_CN China localizations should invoke these documented procedures rather than duplicate their logic, since the package embeds the standard ledger, flexfield, and period-range validations enforced by Oracle. Because the API classification is OTHER, Oracle does not guarantee backward compatibility of its signature; implementers upgrading between 12.1.1 and 12.2.2 should revalidate any direct dependencies. The metadata confirms that JA_CN_UTILITY itself is not referenced by any database object at the schema level, reinforcing its role as a top-level shared library within the APPS layer. All access occurs under the APPS schema and Oracle Proprietary, Confidential Information terms apply.