Results for “processing_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_KR_WG_REPORT_PKG is an Oracle E-Business Suite payroll package owned by the APPS schema and declared with AUTHID CURRENT_USER. It supports the Korean localization of wage garnishment (court order) processing within Oracle Payroll. The package encapsulates the business rules required to evaluate, report, and reconcile wage garnishment deductions against an employee's earnings for a given payroll run. It is classified as an OTHER API rather than a public or private payroll API, indicating that it is intended primarily for internal use by Oracle's Korean localization reporting and garnishment logic rather than as a general-purpose integration interface.

The central business concern of the package is determining how much of an employee's pay has been applied against an outstanding garnishment obligation within a payroll period. Several of its documented functions are dedicated to computing amounts that relate directly to the paid_amount concept: the amount already paid toward the garnishment, the amount paid in the current run, and the interest component of those payments. These values feed the Korean wage garnishment report, which provides the statutory reporting required under Korean labor and civil execution regulations.

Key Procedures and Functions

The package exposes 15 documented procedures and functions organized around courts orders, attachment sequencing, and financial computation.

• PROCESSING_TYPE — Returns the processing type associated with a court order element entry.
• OBLIGATION_EXISTS — Returns TRUE when an Obligation Release exists for a court order, allowing callers to short-circuit further evaluation.
• GET_ELEMENT_ENTRY_ID — Resolves an element entry identifier from an assignment and an attachment sequence number; the header notes Bug 2856663 added the assignment ID parameter.
• GET_ATTACH_SEQ_NO — Returns the attachment sequence number, the inverse of the lookup above.
• PREV_CASE_ATTACHMENT_SEQ_NO — Retrieves the attachment sequence number of the preceding case, supporting sequential case processing.
• WAGE_GARNISHMENT_EXISTS — Tests whether a wage garnishment is present for the subject assignment or element entry.
• PAID_AMOUNT_THIS_RUN — Determines the amount paid against the garnishment within the current payroll run.
• ATTACHMENT_TOTAL_BASE — Establishes the base figure against which attachment totals are computed.
• REAL_ATTACHMENT_TOTAL — Derives the actual attachment total after applicable adjustments.
• UNPAID_DEBT — Returns the outstanding balance remaining on the garnishment obligation.
• PAID_AMOUNT — Returns the cumulative amount paid toward the garnishment; this is the function most directly relevant to the paid_amount search term.
• PAID_INTEREST_THIS_RUN — Returns the interest portion paid during the current run.
• PAID_INTEREST — Returns cumulative interest paid on the garnishment obligation.

Tables Accessed

The package reads from core Oracle Payroll and HR tables through APPS synonyms. PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPES_F, and PAY_INPUT_VALUES_F supply the element entry context and input values that define a garnishment deduction. PAY_RUN_RESULTS and PAY_RUN_RESULT_VALUES hold the calculated results for a run. PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS provide assignment-level and payroll-action context. Balance information is sourced from PAY_BALANCE_DIMENSIONS, PAY_BALANCE_TYPES, and PAY_DEFINED_BALANCES, which are required to compute cumulative and run-specific paid amounts. FND_SESSIONS supplies session context, and DUAL is used for single-row expressions. The package appears to be read-only with respect to these tables, performing computations rather than modifications.

Usage Notes

PAY_KR_WG_REPORT_PKG is typically invoked from the Korean wage garnishment report and related payroll localization logic rather than being called directly by end users. Because it is classified as an OTHER API and depends on element entry and run result data, custom code should call it only within a payroll run context where assignment actions and run results have already been generated. It is referenced by one other package in the ETRM inventory, confirming that its functions are consumed programmatically. Developers extending Korean garnishment reporting should treat the paid-amount and interest functions as the authoritative source for statutory figures.