Search Results insert_session

Overview

APPS.PAY_JP_CREATE_CMA_PKG is a Japanese localization package within Oracle EBS Payroll (Oracle HRMS). Its name reflects its core purpose: the creation and management of CMA (Cost of Management Adjustment / statutory declaration) information specific to Japanese payroll processing. The package body header (pyjpcmap.pkb, version 120.2.12010000.4, dated 2008) shows it was shipped as part of the Japanese payroll legislative patches, which are typically driven by annual statutory changes to Japanese withholding tax and year-end adjustment (Nenmatsu Chousei) rules.

The package centers conceptually on the element SAL_CMA_PROC (Cost of Management Adjustment processing), along with supporting elements COM_ITX_INFO (income tax information) and COM_NRES_INFO (non-resident information). Constants defined in the package body, such as the non-resident input value flag NRES_FLAG, NRES_START_DATE, PROJECTED_RES_DATE, and a global value G_SAL_CMA_PUBLIC_TRANSPORT_NTXBL_ERN_MAX, confirm the package coordinates data used to calculate non-taxable commuter/public transport allowances and the projected residency date for non-resident employees. These are integral to correct Japanese tax withholding and year-end adjustment calculations.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents a single publicly classified procedure within this package:

• TRANSFER_FROM_CMA_INFO_TO_BEE — the primary documented procedure. It transfers CMA-related payroll information gathered by this package into the BEE (Balance Element Entry / BEE utility) structures maintained by PAY_JP_BEE_UTILITY_PKG. By moving values from CMA information to element entries, it ensures the derived CMA and tax data are available to downstream payroll processing and balance feeders.

Although only one procedure is classified as documented API, the source excerpt reveals an internal helper procedure, insert_session, which accepts an effective date and inserts a row into FND_SESSIONS with the current database session ID (USERENV('sessionid')). This establishes a session record for the payroll run before transfer logic executes, and clarifies why the package references FND_SESSIONS. The many constants, such as c_value_if_null_tbl and the BEE utility type t_varchar2_tbl, indicate that these helpers are used internally to supply default input values when transferring data.

Tables Accessed

The package reads and writes the following tables via APPS synonyms:

• FND_SESSIONS — written by insert_session to register the current session and effective date.
• PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL — used to resolve the element names COM_ITX_INFO, COM_NRES_INFO, and related types.
• PAY_INPUT_VALUES_F — used to resolve input value definitions such as NRES_FLAG, NRES_START_DATE, and PROJECTED_RES_DATE.
• FF_GLOBALS_F — used to look up the global value G_SAL_CMA_PUBLIC_TRANSPORT_NTXBL_ERN_MAX, which governs the non-taxable transport earnings maximum.
• HR_ASSIGNMENT_SETS — used to scope processing to relevant employee assignments.
• PAY_BATCH_HEADERS — consulted/updated to associate the transferred CMA information with the appropriate payroll batch.
• PLITBLM — the standard Oracle Payroll table used to hold resolved input values passed between package components, especially for element entry creation.

Usage Notes

PAY_JP_CREATE_CMA_PKG is not a general-purpose API; it is invoked as part of the Japanese payroll processing flow, typically during the year-end adjustment or monthly payroll cycle that handles CMA processing. It is called when CMA input data must be moved into the element-entry/BEE world so that balances and tax calculations can complete. The insert_session helper indicates it can be run in a session-bound context — for example, from a concurrent program or from a pay run action that establishes an FND_SESSIONS row.

Consistent with ETRM classification OTHER and the absence of any packages referencing it (0 referenced by), the package is not designed as an integration point for custom code. Customers and partners should normally call it indirectly through standard Japanese payroll processes and Oracle-supplied concurrent programs rather than invoking it directly. Any custom call should preserve the session-row insert semantics, honoring the effective date, and should run within a valid payroll session to avoid integrity issues.