Results for “lar_attribute1”

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

Overview

BEN_LOA_RSN_RT_V is a reporting and integration view owned by the APPS schema within the Oracle Advanced Benefits (BEN) module. In the Oracle EBS 12.1.1 and 12.2.2 data models, it exposes the definition of absence or leave-of-absence reason rates (LOA_RSN_RT) held in the underlying base table BEN_LOA_RSN_RT_F. The view is documented as a "Retrofitted" object, a designation that reflects the OAF-style retrofit of the original forms-based BEN schema during the transition to Release 12, adding multi-org and object versioning infrastructure while retaining backward compatibility.

The view is not a simple column projection. Its defining characteristic is a DATE_TRACK-style effective-date filter implemented against FND_SESSIONS: only rows whose effective date range brackets the session's effective date are returned, and the current session is resolved through USERENV('SESSIONID'). This means the view presents the currently effective configuration of leave-of-absence reason rates as of the user's session date, which is precisely why it is preferred over querying the base table directly in reporting and integration scenarios. In Release 12, DATE_TRACK views of this family are commonly used by date-tracked flexfield or descriptive-flexfield reporting.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both resolved as APPS synonyms:

• BEN_LOA_RSN_RT_F — the single base table containing LOA reason rate rows, including the surrogate primary key LOA_RSN_RT_ID, the effective date range columns, the descriptive flexfield columns LAR_ATTRIBUTE_CATEGORY and LAR_ATTRIBUTE1 through LAR_ATTRIBUTE30, and the foreign key references to absence attendance types and reasons.
• FND_SESSIONS — the standard EBS concurrent/session table supplying SESSION_ID and EFFECTIVE_DATE, joined to enforce the effective-date window.

Because the view is defined over BEN_LOA_RSN_RT_F directly and is a Retrofit view, it remains updateable only in the sense of the base row identity (ROW_ID is exposed); however, in practice it is used for read-only retrieval rather than DML.

Key Columns

• ROW_ID — the ROWID of the base BEN_LOA_RSN_RT_F row.
• LOA_RSN_RT_ID — surrogate primary key identifying each LOA reason rate.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity range of the row.
• BUSINESS_GROUP_ID — the business group owning the row; in Release 12 this is the multi-org discriminator.
• ORDR_NUM, EXCLD_FLAG, VRBL_RT_PRFL_ID, LOA_RSN_CD — ordering sequence, inclusion/exclusion indicator, variable rate profile reference, and the leave-of-absence reason code.
• LAR_ATTRIBUTE_CATEGORY and LAR_ATTRIBUTE1..30 — the descriptive flexfield context and segment columns. Users searching for lar_attribute1 are targeting this DFF structure; LAR_ATTRIBUTE1 corresponds to the first DFF segment of the LOA reason rate entity.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard OAF audit columns added during retrofit.
• ABSENCE_ATTENDANCE_TYPE_ID, ABS_ATTENDANCE_REASON_ID — references linking the reason rate to absence attendance configuration.

Common Use Cases and Queries

The most common use is retrieving currently effective leave-of-absence reason rates for a reporting extract, particularly when DFF attributes drive downstream processing. A typical query is:

SELECT lar.LOA_RSN_RT_ID,
       lar.LOA_RSN_CD,
       lar.ORDR_NUM,
       lar.EXCLD_FLAG,
       lar.LAR_ATTRIBUTE_CATEGORY,
       lar.LAR_ATTRIBUTE1
FROM   APPS.BEN_LOA_RSN_RT_V lar
WHERE  lar.BUSINESS_GROUP_ID = :p_business_group_id
ORDER  BY lar.LOA_RSN_CD;

Because the view already applies the effective-date filter against the current session date, callers do not need to add date-predicate logic. When a caller must resolve rows as of an arbitrary date rather than the session date, the base table BEN_LOA_RSN_RT_F should be queried directly with explicit date bounds; the view is otherwise the recommended access path, since querying the base table alone may return multiple date-tracked versions of the same key. In integration contexts, the view is convenient for extracting lar_attribute1 and related DFF segments when mapping LOA reason rates into absence management or payroll-facing interfaces.