Results for “filing_status_code”

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

Overview

The PAY_US_EMP_TIME_IN_STATE_V view is a Payroll (PAY) application database object owned by the APPS schema and shipped in a VALID state in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose within ETRM is to support the user interface; it is not a standalone business entity but a presentation-layer construct that consolidates state income tax configuration held against an assignment with the aggregated "time in state" value captured through the Vertex payroll element. The view joins assignment-level state tax rules to the element entries created by the payroll run, resolving the jurisdiction entry values that identify which state each entry belongs to, and then sums the numeric screen entry values that represent the days or periods the employee spent in that state during the pay period.

Because the view filters on PEF.CREATOR_TYPE = 'UT' and constrains the element type name to 'VERTEX', it returns only data produced by the Vertex tax calculation interface. Effective dating is enforced throughout by comparing each row to the session effective date obtained from FND_SESSIONS via USERENV('SESSIONID'), which aligns the output with the date-tracked context of the active EBS form session.

Underlying Base Objects

The view is defined over a join of eleven documented base objects:

• PAY_ELEMENT_ENTRIES_F — the element entry header, supplying ASSIGNMENT_ID and the effective start/end dates.
• PAY_US_EMP_STATE_TAX_RULES_F — assignment-level state tax rules, supplying STATE_CODE, JURISDICTION_CODE, FILING_STATUS_CODE, WITHHOLDING_ALLOWANCES, and the SIT override amount and rate.
• PAY_US_STATES — the state name lookup keyed by STATE_CODE.
• PAY_STATE_RULES — state-level rules, joined on STATE_CODE and STATE_ABBREV.
• PAY_ELEMENT_LINKS_F and PAY_ELEMENT_TYPES_F — used to confirm the entry belongs to the VERTEX element type.
• PAY_ELEMENT_ENTRY_VALUES_F (aliased PEV1 and PEV2) — the entry values that carry the jurisdiction and the time-in-state screen values.
• PAY_INPUT_VALUES_F (aliased PIV1 and PIV2) — the input value definitions that name the JURISDICTION input.
• FND_COMMON_LOOKUPS — resolves FILING_STATUS_CODE to its display meaning.
• FND_NUMBER — the CANONICAL_TO_NUMBER function converts the textual screen entry value into a numeric value for summation.
• FND_SESSIONS and FND_GLOBAL — supply the session effective date used in all date-range predicates.

Key Columns

• ASSIGNMENT_ID — the assignment to which the state tax rule and element entry belong.
• STATE_CODE / STATE_NAME — the two-character state code and its descriptive name.
• JURISDICTION_CODE — the taxing jurisdiction associated with the entry.
• FILING_STATUS_CODE / MEANING — the employee's state filing status and its lookup description.
• WITHHOLDING_ALLOWANCES — the number of state withholding allowances claimed.
• SIT_ADDITIONAL_TAX, SIT_OVERRIDE_AMOUNT, SIT_OVERRIDE_RATE — state income tax additional amount and override values.
• TIME_IN_STATE — the summed numeric value converted from the screen entry values, representing time worked in the state.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the effective dating window of the underlying element entry.

Common Use Cases and Queries

The view is typically consumed where a form or concurrent program must display the time an employee spent in a given state for withholding purposes. A representative query retrieves current rows for a single assignment:

• SELECT assignment_id, state_code, state_name, withholding_allowances, time_in_state FROM apps.pay_us_emp_time_in_state_v WHERE assignment_id = :p_assignment_id;
• SELECT state_code, SUM(time_in_state) FROM apps.pay_us_emp_time_in_state_v GROUP BY state_code; — used for period reporting across a population of employees.

Because effective dates are resolved from the session, queries executed outside a form session should rely on a controlled session context or expect the effective-date predicate to evaluate against the current session record. The view should be treated as read-only UI support rather than a data-entry surface.