Search Results submit_efile

Overview

The APPS.PAY_KR_YEA_DON_EFILE_CONC_PKG package body implements the concurrent-program driver logic for the Korean Year-End Adjustment (YEA) Donation electronic filing process in Oracle E-Business Suite. Its principal responsibility is to accept a set of run-time parameters from a concurrent program submission, resolve the internal business-group identifier associated with the supplied business place, and then submit an indirect request to the internal Oracle Payroll e-file reporting engine (PYKRYEAM_DON_I). This package is part of the Oracle Payroll localization layer for Korea and supports regulatory reporting of donation deductions as required by Korean tax authorities. It is classified under Oracle ETRM as an "OTHER" API and is not intended as a general-purpose public interface. The header comment (pykrydcon.pkb 120.1, dated 2006/10/20) confirms its lineage within the Korean payroll statutory reporting family.

Key Procedures and Functions

The package exposes three documented procedures:

• SUBMIT_EFILE — The primary entry point invoked by the concurrent program. It receives the business place, report-for context, magnetic file name, report file name, payroll action, assignment set, report type, reported date, target year, character set, home tax identifier, and organization structure version. Its internal logic first calls GET_BG_ID to derive the business group, then calls FND_REQUEST.SUBMIT_REQUEST to launch the internal concurrent program PYKRYEAM_DON_I ("KR Year End Adjustment Donation eFile (Internal)"), passing the parameters as positional arguments including MAGTAPE_REPORT_ID=KR_YEA_DON_EFILE, PRIMARY_BP_ID, REPORTED_DATE, PAYROLL_ACTION_ID, ASSIGNMENT_SET_ID, REPORT_TYPE, REPORT_DATE, TARGET_YEAR, CHARACTER_SET, and HOME_TAX_ID. It returns the standard errbuf/retcode concurrent-program completion pair. The internal variable l_bg_id holds the resolved business group.
• GET_BG_ID — A helper routine that resolves the business group identifier for a given business place. This is the procedure most frequently referenced in searches for "get_bg_id" and is called at the start of SUBMIT_EFILE to populate the l_bg_id variable before the request submission. Its purpose is to translate the user-selected business place into the internal organization identifier required by the payroll reporting engine.
• RECORD_COUNT — A utility procedure that returns record counts, presumably used to validate or report on the volume of data captured for the e-file extract prior to submission or during diagnostic reporting.

Tables Accessed

Per the ETRM 12.2.2 metadata, the package references the following tables via APPS synonyms:

• HR_ORGANIZATION_INFORMATION — read to resolve organization-level attributes such as the business place and business group classification used by GET_BG_ID.
• PAY_PAYROLL_ACTIONS — consulted to validate the payroll action supplied to SUBMIT_EFILE and to derive action context for the report.
• PAY_ASSIGNMENT_ACTIONS — used to determine the assignments falling within the selected payroll action, supporting the record count and extract scope.
• PER_ASSIGNMENT_EXTRA_INFO — read for assignment-level statutory or tax attributes relevant to donation reporting, such as home tax identifiers.

Usage Notes

This package is invoked indirectly through the Korean Payroll Year-End Adjustment Donation eFile concurrent program rather than from a form. The standard invocation pattern is: the user submits the concurrent program with business place, payroll action, assignment set, target year, and related parameters; the concurrent manager then executes SUBMIT_EFILE, which resolves the business group via GET_BG_ID and spawns the internal reporting request PYKRYEAM_DON_I. Because the package relies on FND_REQUEST.SUBMIT_REQUEST, the submitting user must hold execute privileges on the target program. It is referenced by one other package within EBS, indicating reuse of its helper routines. Custom code should not call these procedures directly without replicating the concurrent-program parameter validation performed by the standard submission flow.