Results for “hot_default_flag”

50+ results




Overview
Explore in AI Chat

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

Overview

PAY_KR_SEP_RESULT_RRV_V is a valid view in the APPS schema of Oracle E-Business Suite 12.1.1 and 12.2.2, delivered as part of the PAY (Payroll) product. It exposes run-result values produced by the Korean Separation Pay process for a given payroll run. The view is a reporting and integration object: it joins assignment action, payroll action, run result, and run result value data so that a consumer can retrieve the calculated separation pay result for an assignment without navigating the underlying payroll calculation tables directly.

The view is parameterized implicitly by two identifiers — ASSIGNMENT_ACTION_ID and RUN_RESULT_ID. As stated in the ETRM documentation, it returns the result value of the Separation Pay process based on both of these keys. This makes it a targeted lookup rather than a broad transaction register; queries should normally constrain on at least one of these columns to remain efficient.

Underlying Base Objects

The view is defined over six synonym-backed base objects in the APPS schema:

Joins are made on PAYROLL_ACTION_ID, ASSIGNMENT_ACTION_ID, RUN_RESULT_ID, and INPUT_VALUE_ID. The date join PPA.DATE_EARNED BETWEEN PIV.EFFECTIVE_START_DATE AND PIV.EFFECTIVE_END_DATE resolves the correct dated input value definition, and the translation join restricts UNAME to USERENV('LANG').

Key Columns

  • ASSIGNMENT_ACTION_ID — the assignment action that produced the result; a primary filter key.
  • ASSIGNMENT_ID — the assignment (employee) associated with the action.
  • EFFECTIVE_DATE, DATE_EARNED — payroll action dates used for temporal context and for resolving the dated input value.
  • RUN_TYPE_ID, RUN_RESULT_ID — the run type and the run result header; RUN_RESULT_ID is the second primary filter key.
  • INPUT_VALUE_ID, NAME, UNAME — the input value identifier, its base name, and its language-specific display name.
  • DISPLAY_SEQUENCE — ordering sequence for the input value.
  • HOT_DEFAULT_FLAG, IDEFAULT_VALUE — the hot default indicator and default value carried from the input value definition; the search term "hot_default_flag" maps directly to this column, which indicates whether the input value is a "hot default" (prompted at run time) in the element definition.
  • ELEMENT_TYPE_ID — the element type the input value belongs to.
  • RESULT_VALUE — the calculated value produced by the Separation Pay process for that input value.

Common Use Cases and Queries

Typical uses include extracting separation pay results for a specific assignment action, auditing a particular run result, or reporting result values alongside their input value names and default flags. A representative query is:

  • SELECT ASSIGNMENT_ACTION_ID, RUN_RESULT_ID, NAME, UNAME, HOT_DEFAULT_FLAG, RESULT_VALUE FROM APPS.PAY_KR_SEP_RESULT_RRV_V WHERE ASSIGNMENT_ACTION_ID = :p_assignment_action_id ORDER BY DISPLAY_SEQUENCE;
  • SELECT ASSIGNMENT_ACTION_ID, INPUT_VALUE_ID, RESULT_VALUE FROM APPS.PAY_KR_SEP_RESULT_RRV_V WHERE RUN_RESULT_ID = :p_run_result_id;
  • SELECT ASSIGNMENT_ID, DATE_EARNED, UNAME, RESULT_VALUE FROM APPS.PAY_KR_SEP_RESULT_RRV_V WHERE HOT_DEFAULT_FLAG = 'Y' AND DATE_EARNED BETWEEN :p_start AND :p_end;

Because the view performs several joins, including a date-bounded lookup against the input value definition, callers should constrain on ASSIGNMENT_ACTION_ID or RUN_RESULT_ID wherever possible to avoid scanning the full run result population.