Search Results p_profile_option_value




Overview
Explore in AI Chat

Overview

JA_CN_HISDATA_MIG_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and declared with AUTHID CURRENT_USER. Its stated purpose, taken from the package specification header, is to provide CNAO (China National Accounting Office) Version 1 to Version 2 data migration procedures. The package therefore exists to support an upgrade path for the Chinese localizations delivered under the JA (Asia/Japan-adjacent) product family, reconciling historical journal and cash-flow data from an earlier CNAO V1 model into the structures used by CNAO V2.

The object is classified as OTHER in the ETRM 12.2.2 repository, meaning it is not a formal public API but an internal migration utility. It is not referenced by any other package, confirming that it is a top-level migration driver rather than a shared library. The header records a creation date of 05-Jan-2011 by Chongwu Li, with subsequent updates through 13-Apr-2011 addressing bugs 11691910, 11683977, 11904408, and 12349159. The JA_CN_HISDATA_MIG_PKG is therefore most relevant to releases in the 12.1.1 to 12.2.2 window where the CNAO statuatory accounting functionality was being reworked.

Key Procedures and Functions

The documented procedures number five:

  • UpdateGLCashlines — migrates cash-flow-related line data held in GL_JE_LINES. Its documented behaviour is to copy values from a descriptive flexfield (DFF) column named AttributeN into the Global_Attribute6 column. The header lists inputs including chart of account ID, legal entity ID, ledger ID, ledger name, legal entity name, and period name, the last of which confirms the procedure operates at period granularity. Notably, the user search term p_ledger_name corresponds to the P_LEDGER_NAME parameter documented for this procedure.
  • UpdateGLItemizationlines — migrates itemization detail on GL entry lines, again working against the GL journal line data.
  • UpdateItemizationlines — the JA-specific counterpart, operating on the CNAO itemization structures rather than the generic GL lines.
  • MigrateHisDataCFS — migrates CFS (cash flow statement) historical data into the CNAO V2 repositories.
  • MigrateHisDataDE — migrates the corresponding DE (detail entry / disclosure) historical data.

The metadata also references a MigrateHisData procedure in the source listing, though the ETRM repository documents only the five procedures above. No parameter lists are reproduced here beyond those explicitly stated in the package header.

Tables Accessed

The package reads and writes a broad cross-section of GL, subledger, and CNAO localization tables through APPS synonyms. On the general ledger side it touches GL_JE_HEADERS, GL_JE_LINES, GL_IMPORT_REFERENCES, and XLA_AE_LINES, which together supply the journal header, line, import reference, and subledger accounting entry data being converted. Flexfield configuration is read from FND_DESCR_FLEX_COLUMN_USAGES and FND_SEGMENT_ATTRIBUTE_VALUES.

The CNAO localisation tables form the migration target set: JA_CN_CFS_ACTIVITIES_ALL, JA_CN_DFF_ASSIGNMENTS, JA_CN_JOURNAL_LINES, JA_CN_LEDGER_LE_BSV_GT, JA_CN_SUB_ACC_MAPPING, and JA_CN_SUB_ACC_SOURCES_ALL. JA_CN_LEDGER_LE_BSV_GT is a global temporary table used to stage ledger and legal-entity balance segment values, while JA_CN_SUB_ACC_MAPPING and JA_CN_SUB_ACC_SOURCES_ALL support the mapping of sub-account sources into the V2 model.

Usage Notes

Because the package is not referenced by any other database object, it is invoked directly rather than from within a larger call stack. Typical invocation is expected through a concurrent program, a one-off migration script, or bespoke upgrade code executed by a DBA or implementation consultant as part of the CNAO V1 to V2 transition. The period-name and ledger-name inputs on UpdateGLCashlines indicate that migrations are scoped to a specific ledger and accounting period, allowing the migration to be run in controlled increments rather than in a single bulk pass.

Given the AUTHID CURRENT_USER declaration, execute privileges must be granted to the invoking schema. The package is internal Oracle code and is not intended for general customer-facing use; any direct call should be validated against the specific 12.1.1 or 12.2.2 patch level in use.