Results for “pay_run_types_f_vl”

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

Overview

PAY_RUN_TYPES_F_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite Payroll (PAY). In the ETRM object registry for 12.1.1 and 12.2.2 it carries the status VALID and is classified as a VIEW. The suffix "VL" identifies it as a "view language" construct: it joins the run-type base table to its translation table and returns the run type name and short name in the language of the current session. It is the standard presentation-layer access point for payroll run type definitions, shielding callers from the date-effective partitioning and multilingual storage used internally.

Its principal role is to expose the run types available in the current business group and legislation, resolved against the effective date and language of the user's session, together with a decoded run-method meaning. Because it is defined over synonyms and views rather than a private structure, it is safe to use in custom concurrent programs, BI Publisher data models, and integration queries in both the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The documented base objects are PAY_RUN_TYPES_F (SYNONYM), PAY_RUN_TYPES_F_TL (SYNONYM), HR_LOOKUPS (VIEW), FND_SESSIONS (SYNONYM), and the HR_API package. The view joins these as follows:

• PAY_RUN_TYPES_F supplies the run type identifier, run method, effective dates, business group, legislation code, audit columns, object version number, the SRS flag, run information category, and run information attribute slots.
• PAY_RUN_TYPES_F_TL supplies the translated RUN_TYPE_NAME and SHORTNAME, restricted by T.LANGUAGE = USERENV('LANG') so only the session language row is returned.
• HR_LOOKUPS is joined on LOOKUP_TYPE = 'RUN_METHOD' to translate RUN_METHOD into the RUN_METHOD_MEANING displayed to users.
• FND_SESSIONS is joined on the session id and effective date so that only rows effective for the user's session date are returned, resolving the date-effective (datetracked) nature of the base table.
• HR_API is listed as a referenced object, reflecting the business-group and datetrack security logic used by the underlying entity.

Key Columns

The view returns ROW_ID, RUN_TYPE_ID, RUN_METHOD, RUN_METHOD_MEANING, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, BUSINESS_GROUP_ID, LEGISLATION_CODE, the standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE), OBJECT_VERSION_NUMBER, RUN_TYPE_NAME, SHORTNAME, SRS_FLAG, RUN_INFORMATION_CATEGORY, and RUN_INFORMATION1 through RUN_INFORMATION30.

• RUN_TYPE_ID — primary key of the run type; the value stored on payroll action, assignment, and process parameters.
• RUN_TYPE_NAME / SHORTNAME — translated, user-facing name and abbreviated name of the run type.
• RUN_METHOD / RUN_METHOD_MEANING — the code stored in the base table and its decoded meaning from HR_LOOKUPS.
• LEGISLATION_CODE / BUSINESS_GROUP_ID — the legislative and business-group scope of the definition.
• SRS_FLAG — indicates whether the run type is processed by a concurrent (SRS) program.
• RUN_INFORMATION_CATEGORY and RUN_INFORMATION1..30 — the descriptive flexfield context and attribute values used to capture run-type-specific parameters.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective window honored by the session join.

Common Use Cases and Queries

The view is commonly used to populate LOVs and reports of run types, to validate a run type before submitting a payroll process, and to read descriptive flexfield values for integration. A typical listing query is:

• SELECT run_type_id, run_type_name, shortname, run_method_meaning, srs_flag, legislation_code FROM apps.pay_run_types_f_vl ORDER BY run_type_name;
• Filtering by legislation: SELECT run_type_id, run_type_name FROM apps.pay_run_types_f_vl WHERE legislation_code = :p_legislation;
• Reading flexfield data: SELECT run_type_id, run_information_category, run_information1, run_information2 FROM apps.pay_run_types_f_vl WHERE run_type_id = :p_run_type_id;
• Joining to payroll actions to enrich a report: SELECT pa.action_id, rt.run_type_name FROM apps.pay_run_types_f_vl rt, apps.pay_payroll_actions pa WHERE pa.run_type_id = rt.run_type_id;

Because the view is secured by session language and session effective date, queries must run in an initialized EBS session; direct SQL through a non-EBS connection returns no rows. Treat the object as read-only and reference run types by RUN_TYPE_ID in any custom logic.