Results for “ben_freq”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.BEN_SCHEDD_HRS_RT_D is a reporting view in the Oracle E-Business Suite Advanced Benefits (BEN) module, exposed under the APPS schema and available in releases 12.1.1 and 12.2.2. It presents scheduled hours rate definitions used by benefits plan configuration, specifically the rows held in the scheduled hours rate table joined to the descriptive meaning values required for end-user and interface readability. The "_D" suffix follows the EBS convention for a denormalized descriptive view: the underlying numeric identifiers and lookup codes are translated into user-facing names and meanings.
The view's role is to serve as a read-only projection for reporting, extracts, and integration where raw code values are unusable. In the context of a search for ben_freq, this view is the principal place where the BEN_FREQ lookup type is consumed within the scheduled hours rate structure: the frequency code stored on the rate row is resolved through HR_LOOKUPS into its displayed meaning.
Underlying Base Objects
The view is defined over the following documented base objects:
- BEN_SCHEDD_HRS_RT_F (SYNONYM) — the scheduled hours rate table, aliased
SHRin the view text. This is the driving table and supplies the ROWID, primary key, effective dates, order number, hours, and frequency code. - BEN_VRBL_RT_PRFL_F (SYNONYM) — the variable rate profile table, aliased
VRBL_RT_PRFL, providing the profile name. - FND_USER (SYNONYM) — the application user table, aliased
FUSER, resolving the last-updated-by identifier. - HR_LOOKUPS (VIEW) — joined twice, once as
FREQfor lookup typeBEN_FREQand once asEXCLDfor lookup typeYES_NO. - HR_API (PACKAGE) — documented as a referenced object, supporting the date-effective and lookup access patterns used by the BEN date-tracked entities.
All joins are outer joins, so a scheduled hours rate row is retained even when the profile, user, or lookup translation is missing. Note that the profile join is date-effective: the row's EFFECTIVE_START_DATE must fall between the profile's effective start and end dates.
Key Columns
- ROW_ID — the ROWID of the underlying
BEN_SCHEDD_HRS_RT_Frow. - SCHEDD_HRS_RT_ID — primary key of the scheduled hours rate record.
- EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range for the rate row.
- NAME — the variable rate profile name from
BEN_VRBL_RT_PRFL_F. - MEANING (from EXCLD) — the Yes/No meaning derived from
EXCLD_FLAGagainst lookup typeYES_NO. - ORDR_NUM — ordering sequence for the rate line.
- MEANING (from FREQ) — the display meaning of
FREQ_CDresolved from lookup typeBEN_FREQ, the column directly relevant toben_freq. - HRS_NUM — the number of scheduled hours.
- LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns, with the user identifier joined to
FND_USER.
Common Use Cases and Queries
Typical uses include validating scheduled hours rate configuration, producing benefits setup extracts, and auditing which frequency values are in use across plans.
- Listing all scheduled hours rates with their frequency meaning and profile name.
- Filtering by frequency meaning, for example only rates defined as weekly or monthly.
- Auditing recently changed rate records by user and date.
Sample query:
SELECT shr.row_id,
shr.schedd_hrs_rt_id,
shr.effective_start_date,
shr.effective_end_date,
shr.name,
shr.ordr_num,
shr.hrs_num,
freq.meaning AS frequency_meaning,
excld.meaning AS excluded_flag_meaning,
shr.last_update_date,
fuser.last_updated_by
FROM apps.ben_schedd_hrs_rt_d shr,
apps.fnd_user fuser,
apps.hr_lookups freq,
apps.hr_lookups excld
WHERE fuser.user_id (+) = shr.last_updated_by
AND freq.lookup_code (+) = shr.freq_cd
AND freq.lookup_type (+) = 'BEN_FREQ'
AND excld.lookup_code (+) = shr.excld_flag
AND excld.lookup_type (+) = 'YES_NO';
Because the view already performs lookup resolution, most reporting needs are met by selecting directly from APPS.BEN_SCHEDD_HRS_RT_D without re-joining the frequency lookups. Queries should nonetheless respect the date-effective columns and apply SYSDATE or a target date filter where only currently effective rates are required.
-
Lookup Type: BEN_FREQ 12.1.1
-
Lookup Type: BEN_FREQ 12.2.2
-
View: BEN_SCHEDD_HRS_RT_D 12.1.1
- Retrofitted
APPS.BEN_SCHEDD_HRS_RT_D·↳ BEN_SCHEDD_HRS_RT_F·↳ BEN_VRBL_RT_PRFL_F·↳ FND_GLOBAL·Explore BEN module →
-
View: BEN_SCHEDD_HRS_RT_D 12.2.2
- Retrofitted
APPS.BEN_SCHEDD_HRS_RT_D·↳ BEN_SCHEDD_HRS_RT_F·↳ BEN_VRBL_RT_PRFL_F·↳ FND_USER·Explore BEN module →
-
This view identifies how to calculate a person's hours worked in a period for such purposes as determining eligibility and calculating rates.
APPS.BENBV_HRS_WKD_IN_PERD_FCTR_V·↳ BEN_HRS_WKD_IN_PERD_FCTR·↳ HR_BIS·Explore BEN module →
-
This view identifies how to calculate a person's hours worked in a period for such purposes as determining eligibility and calculating rates.
APPS.BENBV_HRS_WKD_IN_PERD_FCTR_V·↳ BEN_HRS_WKD_IN_PERD_FCTR·↳ HR_BIS·Explore BEN module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - BEN Tables and Views 12.2.2
Start and End periods.
-
eTRM - BEN Tables and Views 12.1.1
Start and End periods.