Results for “relational_operator”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GHR_MASS_AWARD_CRITERIA_VALS is a transactional table owned by the HR schema in Oracle E-Business Suite, delivered as part of the GHR – US Federal Human Resources product family. The table stores the individual selection-criteria values that drive a Mass Awards process. In a federal HR context, a mass award is a single recognition action applied to a defined population of employees; the criteria values held in this table determine which employees qualify and how the award is scoped. Each row represents one criterion value bound to a specific mass award and to a specific criterion column definition.
From a Data Vault modeling perspective, the documented foreign-key structure suggests classifying this object heuristically as a link — it associates a mass award (GHR_MASS_AWARDS) with a criterion column definition (GHR_MASS_AWARD_CRITERIA_COLS) and carries its own descriptive payload. This classification is a modeling suggestion derived from the FK topology, not a statement of Oracle's internal design.
Key Information Stored
The table is documented in ETRM 12.2.2 with 11 physical columns. The most significant are:
- MASS_AWARD_CRITERIA_VAL_ID — the surrogate primary key, enforced by unique index GHR_MASS_AWARD_CRITERIA_VA_PK. It uniquely identifies each criterion value row.
- MASS_AWARD_ID — foreign key to GHR_MASS_AWARDS; identifies the parent mass award to which this criterion value belongs.
- MASS_AWARD_CRITERIA_COL_ID — foreign key to GHR_MASS_AWARD_CRITERIA_COLS; identifies the criterion column (the selection attribute) being valued.
- VALUE — the actual criterion value used for employee selection.
- DESCRIPTION — free-text explanation of the criterion value.
- RELATIONAL_OPERATOR — the comparison operator (for example, equals, greater than, less than) applied between the criterion attribute and the VALUE.
- CREATION_DATE, CREATED_BY — standard audit columns recording row creation.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification.
Only MASS_AWARD_CRITERIA_VAL_ID is documented as a unique-index business-key candidate; the remaining identifiers function as foreign keys rather than alternate keys. Together, MASS_AWARD_ID and MASS_AWARD_CRITERIA_COL_ID form the practical business grain of the table.
Common Use Cases and Queries
Typical usage centers on reproducing or auditing the criteria that scoped a mass award. Reporting queries join this table to both parent tables to resolve the award name and the criterion column label:
- Listing all criteria for a given award:
SELECT * FROM ghr_mass_award_criteria_vals WHERE mass_award_id = :award_id. - Resolving descriptors: join to GHR_MASS_AWARDS on MASS_AWARD_ID and to GHR_MASS_AWARD_CRITERIA_COLS on MASS_AWARD_CRITERIA_COL_ID.
- Audit and change tracking: filter on LAST_UPDATE_DATE to identify criteria modified after a given date.
- Validation extracts: isolate rows whose RELATIONAL_OPERATOR or VALUE fall outside expected patterns before reprocessing an award.
Related Objects
- GHR_MASS_AWARDS — parent table; joined via GHR_MASS_AWARD_CRITERIA_VALS.MASS_AWARD_ID.
- GHR_MASS_AWARD_CRITERIA_COLS — defines the criterion columns; joined via GHR_MASS_AWARD_CRITERIA_VALS.MASS_AWARD_CRITERIA_COL_ID.
- GHR_MASS_AWARD_CRITERIA_VA_PK — the unique index enforcing the primary key.
- Related mass-award processing tables and concurrent programs in the GHR module that consume these criteria during eligibility determination.
-
Used to store the values for the selection criteria in the Mass Awards
-
Filter conditions for Group operations
-
Holds the counter filters data
-
Used to store the values for the selection criteria in the Mass Awards
-
View: OKC_CNL_COUNTER_EXPR_V 12.1.1
View for table OKC_EVENT_DEF_LINES_B
APPS.OKC_CNL_COUNTER_EXPR_V·↳ OKC_CONDITION_LINES_B·↳ OKC_CONDITION_LINES_TL·Explore OKC module →
-
View: OKC_CONDITION_LINES_V 12.1.1
View for table OKC_EVENT_DEF_LINES_B
APPS.OKC_CONDITION_LINES_V·↳ OKC_CONDITION_LINES_B·↳ OKC_CONDITION_LINES_TL·Explore OKC module →
-
APPS.CSC_CONDITION_EXPRESSION_V·↳ OKC_ACTION_ATTRIBUTES_V·↳ OKC_CONDITION_LINES_V·Explore CSC module →
-
APPS.CSC_CONDITION_EXPRESSION_V·↳ OKC_ACTION_ATTRIBUTES_V·↳ OKC_CONDITION_LINES_V·Explore CSC module →
-
Each Condition Line expresses a Boolean condition. Multiple Condition Lines may be and'd or or'd together and nested using parenthesis.
APPS.CSC_CONDITION_LINE_DETAILS_V·↳ CSC_CORE_UTILS_PVT·↳ OKC_ACTION_ATTRIBUTES_V·↳ OKC_CONDITION_LINES_V·Explore CSC module →
-
Each Condition Line expresses a Boolean condition. Multiple Condition Lines may be and'd or or'd together and nested using parenthesis.
APPS.CSC_CONDITION_LINE_DETAILS_V·↳ CSC_CORE_UTILS_PVT·↳ OKC_ACTION_ATTRIBUTES_V·↳ OKC_CONDITION_LINES_V·Explore CSC module →
-
Stores boolean expression which further qualifies a Condition Header.
-
Stores boolean expressions which further qualify a Condition Header
-
History table for OKC_CONDITION_LINES_B.
-
View: OKC_CNL_GENERAL_EXPR_V 12.1.1
View for table OKC_EVENT_DEF_LINES_B
APPS.OKC_CNL_GENERAL_EXPR_V·↳ OKC_CONDITION_LINES_B·↳ OKC_CONDITION_LINES_TL·Explore OKC module →
-
CSC_PLAN_HEADERS_B table stores all the plan templates and customized plan templates.
-
View: CSC_PLAN_HEADERS_VL 12.2.2
This view is the MLSed view based on CSC_PLAN_HEADERS_B and CSC_PLAN_HEADERS_TL used in lock row event of server side API's
APPS.CSC_PLAN_HEADERS_VL·↳ CSC_PLAN_HEADERS_B·↳ CSC_PLAN_HEADERS_TL·Explore CSC module →
-
View: CSC_PLAN_HEADERS_VL 12.1.1
This view is the MLSed view based on CSC_PLAN_HEADERS_B and CSC_PLAN_HEADERS_TL used in lock row event of server side API's
APPS.CSC_PLAN_HEADERS_VL·↳ CSC_PLAN_HEADERS_B·↳ CSC_PLAN_HEADERS_TL·Explore CSC module →
-
View: OKC_CONDITION_LINES_HV 12.1.1
History view for OKC_CONDITION_LINES.
APPS.OKC_CONDITION_LINES_HV·↳ OKC_CONDITION_LINES_BH·↳ OKC_CONDITION_LINES_TLH·Explore OKC module →
-
View: CSC_PLAN_HEADERS_V 12.1.1
This view is based on CSC_PLAN_HEADRES_B & CSC_PLAN_HEADRES_TL used in the client code
APPS.CSC_PLAN_HEADERS_V·↳ CSC_CUSTOMIZED_PLANS·↳ CSC_LOOKUPS·↳ CSC_PLAN_HEADERS_B·Explore CSC module →
-
History table for OKC_CONDITION_LINES_B.
-
View: OKC_CNL_GENERAL_EXPR_V 12.2.2
View for table OKC_EVENT_DEF_LINES_B
APPS.OKC_CNL_GENERAL_EXPR_V·↳ OKC_CONDITION_LINES_B·↳ OKC_CONDITION_LINES_TL·Explore OKC module →
-
Counter derived filters view
APPS.CSI_COUNTER_DER_FILTERS_V·↳ CSI_COUNTER_DERIVED_FILTERS·↳ CSI_COUNTER_PROPERTIES_VL·Explore CSI module →
-
Counter derived filters view
APPS.CSI_COUNTER_DER_FILTERS_V·↳ CSI_COUNTER_DERIVED_FILTERS·↳ CSI_COUNTER_PROPERTIES_VL·Explore CSI module →
-
Filter conditions for Group operations
-
View: OKC_CONDITION_LINES_HV 12.2.2
History view for OKC_CONDITION_LINES.
APPS.OKC_CONDITION_LINES_HV·↳ OKC_CONDITION_LINES_BH·↳ OKC_CONDITION_LINES_TLH·Explore OKC module →
-
View: CSC_PLAN_HEADERS_V 12.2.2
This view is based on CSC_PLAN_HEADRES_B & CSC_PLAN_HEADRES_TL used in the client code
APPS.CSC_PLAN_HEADERS_V·↳ CSC_CUSTOMIZED_PLANS·↳ CSC_LOOKUPS·↳ CSC_PLAN_HEADERS_B·Explore CSC module →
-
View: OKC_CNL_COUNTER_EXPR_V 12.2.2
View for table OKC_EVENT_DEF_LINES_B
APPS.OKC_CNL_COUNTER_EXPR_V·↳ OKC_CONDITION_LINES_B·↳ OKC_CONDITION_LINES_TL·Explore OKC module →
-
View: OKC_CONDITION_LINES_V 12.2.2
View for table OKC_EVENT_DEF_LINES_B
APPS.OKC_CONDITION_LINES_V·↳ OKC_CONDITION_LINES_B·↳ OKC_CONDITION_LINES_TL·Explore OKC module →
-
Derive counter filters view
APPS.CS_COUNTER_DER_FILTERS_V·↳ CS_COUNTER_DER_FILTERS·↳ CS_COUNTER_PROPERTIES·Explore CS module →
-
Derive counter filters view
APPS.CS_COUNTER_DER_FILTERS_V·↳ CS_COUNTER_DER_FILTERS·↳ CS_COUNTER_PROPERTIES·Explore CS module →
-
Holds the counter filters data
-
CSC_PLAN_HEADERS_B table stores all the plan templates and customized plan templates.