Search Results create_county_record

Overview

PAY_US_EMP_TAX_RULES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Payroll (Oracle Payroll, US localization). It encapsulates the business rules that govern how employee-level United States tax rules are created, validated, and applied when Payroll processes element entries for tax-related earnings and deductions. The package sits between the user-facing maintenance forms and the underlying payroll data model, providing the row-level DML handling and defaulting logic required to keep US employee tax records consistent. In the ETRM classification it is registered as an OTHER API, meaning it is not part of the public, supported API surface, but is a supporting database object used primarily by forms and internal payroll logic. Its central responsibility is the interpretation of state, county, city, and school district tax rules and their translation into payroll element entries that drive withholding calculations.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions, which fall into three functional groups.

• Row maintenance and validation: INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW provide the standard transactional operations on the employee tax rules record, including concurrency control through LOCK_ROW. CHECK_UNIQUE enforces that no duplicate tax rule record exists for the same employee and jurisdiction combination. ON_INSERT is the trigger-style hook invoked during row creation to apply insertion-time business logic. UPDATE_ATTRIBUTE supports targeted modification of individual attributes without rewriting the whole record.
• Defaulting and derivation: DEFAULT_TAX and DEFAULT_TAX_WITH_VALIDATION populate tax-related attributes automatically, the latter adding validation of the derived values before they are committed. ZERO_OUT_TIME is used to suppress or zero time-related tax treatment where the employee's jurisdiction or rule configuration does not permit it.
• Jurisdiction and element integration: CREATE_VERTEX_ENTRY and CREATE_WC_ELE_ENTRY build the payroll element entries required for tax processing, including the entries consumed by third-party tax engine integration. CREATE_COUNTY_RECORD generates the county-level record used when an employee's residence or work location falls within a taxing county.

Detailed parameter lists are not reproduced here; the procedures should be referenced through their package specification in the APPS schema.

Tables Accessed

The package reads and writes a defined set of Payroll and HR tables through APPS synonyms. Employee and assignment context is drawn from PER_ASSIGNMENT_EXTRA_INFO, PER_ASSIGNMENT_EXTRA_INFO_S, and PER_ADDRESSES. Payroll element structures are accessed via PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, and PAY_INPUT_VALUES_F, which together form the element entry chain created by CREATE_VERTEX_ENTRY and CREATE_WC_ELE_ENTRY. Jurisdiction definition data comes from PAY_US_STATES, PAY_US_COUNTIES, PAY_US_CITY_SCHOOL_DSTS, PAY_US_COUNTY_SCHOOL_DSTS, and PAY_STATE_RULES. HR_ORGANIZATION_INFORMATION and HR_SOFT_CODING_KEYFLEX supply organization and costing context for derived records.

Usage Notes

PAY_US_EMP_TAX_RULES_PKG is typically invoked indirectly rather than by custom code. Its principal consumers are the Oracle Payroll US employee tax maintenance forms, which call INSERT_ROW, UPDATE_ROW, DELETE_ROW, and the defaulting routines when a user adds or changes an employee's state, county, or school district tax rule. CREATE_VERTEX_ENTRY and CREATE_WC_ELE_ENTRY are invoked during payroll run preparation to materialize the element entries required by the tax calculation process. Because the package is classified as OTHER and is not documented as a public API, direct calls from custom code are not supported and may break across patches or upgrades. The ETRM metadata records no packages referencing this package, confirming it is a leaf-level implementation object used by forms and concurrent processes rather than a reusable API layer.