Search Results assign_id

Overview

PAY_KR_YEA_DON_EFILE_PKG is a Korean localization package in Oracle E-Business Suite that supports the generation of Year-End Adjustment (YEA) electronic filing data for the National Tax Service (NTS) of South Korea. The package is owned by APPS and is classified under the ETRM taxonomy as OTHER. Its header, source comments, and cursor definitions indicate that it assembles the header and control records required by the Korean year-end tax settlement electronic file format, commonly referred to as the "Don" e-file layout. The package reads configuration parameters through PAY_MAGTAPE_GENERIC and derives business place, tax office, and corporate registration values from HR organization information, then formats them as positional name-value pairs expected by the downstream e-file writer. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling user rather than as its definer, which is relevant when invoked from concurrent programs running under a restricted responsibility.

Key Procedures and Functions

The documented ETRM metadata for this package lists no public procedures or functions, and the excerpt provided exposes only package-level declarations and cursor definitions rather than a callable API surface. The visible declarations include module-level variables such as LEVEL_CNT, G_BUSINESS_PLACE_ID, G_TARGET_YEAR, G_B_RECORDS, and the year-type flags G_NORMAL_YEA, G_INTERIM_YEA, and G_RE_YEA, all of which act as global state for a single execution. G_PAYROLL_ACTION_ID and G_ASSIGNMENT_SET_ID identify the payroll action and assignment set scoped for the run, while G_REP_PERIOD_CODE defaults to '2' following the correction noted in Bug 9251570. Cursor CSR_A produces the top-level "A" record header, concatenating the business place organization name, tax office code, primary business place number, corporate name, and the A record count from G_B_RECORDS. Cursor CSR_B produces the per-business-place "B" record header, combining business place number and name, tax office code, and a C record count obtained by invoking PAY_KR_YEA_DON_EFILE_CONC_PKG.RECORD_COUNT. Because no procedures are formally documented, consumers should treat the package as an internal component of the Korean YEA concurrent program family rather than as a supported integration API.

Tables Accessed

The package queries HR_ALL_ORGANIZATION_UNITS_TL and HR_ORGANIZATION_INFORMATION to resolve the legal employer, business place, tax office, and corporate registration attributes stored in descriptive flexfield contexts such as KR_INCOME_TAX_OFFICE, KR_BUSINESS_PLACE_REGISTRATION, and KR_CORPORATE_INFORMATION. The ETRM metadata additionally records references to PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS, which supply the payroll action context used to scope the population of assignments included in the filing, and to PER_ASSIGNMENT_EXTRA_INFO, which holds assignment-level Korean tax attributes consumed when building detail records. PER_ORG_STRUCTURE_ELEMENTS is referenced to resolve organizational hierarchy relationships, particularly the linkage between a business place and its parent corporate entity. These tables are accessed through APPS synonyms, and all reads are filtered by the language environment and by organization identifiers passed through the magtape parameter mechanism.

Usage Notes

PAY_KR_YEA_DON_EFILE_PKG is invoked in the context of the Korean year-end adjustment e-file concurrent program, normally after a payroll action has been created and an assignment set has been selected so that G_PAYROLL_ACTION_ID and G_ASSIGNMENT_SET_ID are populated. The ETRM metadata records that the package is referenced by one other package, indicating a narrow call graph and confirming that it is a subordinate module rather than an entry point. The presence of the ASSIGN_ID search term in user queries reflects the fact that assignment identifiers flow into this package indirectly through the assignment set and payroll action, not through a directly documented parameter. Customizations should avoid calling this package directly; instead, use the delivered concurrent program and, where extension is required, wrap the delivered logic or use supported payroll action and assignment set configuration. Because method signatures are not exposed in the documentation, any direct invocation risks breakage across patch levels.