Results for “additional_wa_amount”

50+ results




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

Overview

HR_H2PI_FEDERAL_TAX_RULES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered under the PER (Human Resources) product family. The view exposes United States federal tax rule data used by the Oracle HR to Oracle Payroll Interface, commonly abbreviated as H2PI. Its documented status is VALID in both ETRM 12.1.1 and 12.2.2, and it is classified as a VIEW object type.

The view serves as a consolidation layer that joins assignment information to the underlying federal tax rule records, producing a person-centric projection of US federal withholding and exemption attributes. It is typically referenced by H2PI extraction and integration logic, and by reporting queries that must reconcile HR assignment data with the federal tax configuration maintained in the payroll tax model. Because the view filters tax rules by the effective date range of the associated assignment, it returns only tax rows that are valid for the assignment at a given point in time — a behavior that simplifies downstream reporting and reduces the risk of returning stale or out-of-period tax records.

Underlying Base Objects

According to the documented view text, HR_H2PI_FEDERAL_TAX_RULES_V is defined over two referenced objects:

The join condition links FED.ASSIGNMENT_ID to ASG.ASSIGNMENT_ID and further restricts the result so that FED.EFFECTIVE_START_DATE falls BETWEEN ASG.EFFECTIVE_START_DATE and ASG.EFFECTIVE_END_DATE. The additional PERSON_ID and BUSINESS_GROUP_ID columns are carried through from the tax rules record and the assignment context, respectively.

Key Columns

  • PERSON_ID — unique identifier of the person associated with the assignment and federal tax rule.
  • EMP_FED_TAX_RULE_ID — surrogate key of the underlying federal tax rule row.
  • ASSIGNMENT_ID — assignment to which the tax rule applies.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective bounds of the tax rule.
  • SUI_STATE_CODE — the state code used for State Unemployment Insurance; this is the column most directly relevant to the search term "sui_state_code" that led to this object.
  • SUI_JURISDICTION_CODE — the SUI jurisdiction associated with the rule.
  • BUSINESS_GROUP_ID — the business group owning the tax rule record.
  • FILING_STATUS_CODE — federal filing status used to determine withholding.
  • WITHHOLDING_ALLOWANCES — number of federal withholding allowances claimed.
  • FIT_OVERRIDE_AMOUNT, FIT_OVERRIDE_RATE, SUPP_TAX_OVERRIDE_RATE — overrides for federal income tax and supplemental withholding.
  • FIT_ADDITIONAL_TAX — additional federal income tax to be withheld.
  • FIT_EXEMPT, FUTA_TAX_EXEMPT, MEDICARE_TAX_EXEMPT, SS_TAX_EXEMPT — exemption indicators for federal income tax, FUTA, Medicare, and Social Security.
  • EIC_FILING_STATUS_CODE — earned income credit filing status.
  • CUMULATIVE_TAXATION — indicates whether cumulative taxation applies.
  • ADDITIONAL_WA_AMOUNT, EXCESSIVE_WA_REJECT_DATE — additional withholding allowance amount and the date on which an excessive withholding allowance was rejected.
  • STATUTORY_EMPLOYEE, W2_FILED_YEAR — statutory employee indicator and the W-2 filing year.
  • LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER — standard audit and optimistic locking columns.

Common Use Cases and Queries

Typical uses include verifying SUI state assignment for a person, auditing federal exemption elections, and feeding H2PI extraction routines that need person-level federal tax attributes aligned to assignment effective dates. A representative query to retrieve SUI state information for a person is:

SELECT person_id, assignment_id, sui_state_code, sui_jurisdiction_code
FROM   apps.hr_h2pi_federal_tax_rules_v
WHERE  person_id = :p_person_id;

To review exemption and filing attributes for a business group:

SELECT person_id, filing_status_code, withholding_allowances,
       fit_exempt, fut_a_tax_exempt
FROM   apps.hr_h2pi_federal_tax_rules_v
WHERE  business_group_id = :p_business_group_id
ORDER BY person_id;

Because the view is date-effective and joins through HR_H2PI_ASSIGNMENTS_V, queries should always filter by PERSON_ID or ASSIGNMENT_ID to avoid returning multiple effective-dated rows per person. The view is read-only and should be treated as an integration and reporting surface rather than a maintenance path.