Results for “pay_element_types_f_pk”

50+ results




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

Overview

APPS.PAY_EMEA_PAYMNTS_ACTION_INFO_V is a reporting view in the Oracle E-Business Suite Payroll (PAY) module that exposes EMEA-specific payment action information by joining payroll action interlocks to EMEA element definition context stored in PAY_ACTION_INFORMATION. The view is defined with an extensive set of optimizer hints, added expressly to resolve performance bug 2421978, and therefore represents a performance-tuned query rather than a simple single-table projection. Its principal role is to present, for a given locking action, the element input values and EMEA payment attributes associated with the locked payroll action and its contributing assignment actions. Organizations use it in payment reconciliation, third-party payment file generation, and EMEA statutory reporting where the relationship between locking and locked actions must be resolved alongside element-level result values. Because the view references PAY_EMEA_PAYMENT_VALUES_V, it is EMEA-localized and is not intended as a global payments view.

Underlying Base Objects

The view is defined over six documented base objects: PAY_ACTION_INTERLOCKS, PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, PAY_ACTION_INFORMATION, PAY_EMEA_PAYMENT_VALUES_V, and FND_NUMBER. The first four are accessed through public synonyms owned by the PAY schema. The driving table is PAY_ACTION_INTERLOCKS (aliased LCK), which supplies the locking_action_id and locked_action_id pair that governs the join. PAY_ASSIGNMENT_ACTIONS is joined twice: once as PAA1 on lck.locked_action_id and once as PAA2 on lck.locking_action_id, allowing the view to correlate both sides of an interlock. PAY_PAYROLL_ACTIONS (PPA) is joined on paa1.payroll_action_id and is filtered to action_type values of 'P' (payment) and 'U' (unlock or related processing). PAY_ACTION_INFORMATION (PAI) is joined where the action context is of type 'PA' and the category is 'EMEA ELEMENT DEFINITION', with a NVL relationship to the payroll action. PAY_EMEA_PAYMENT_VALUES_V (PET) is then joined on assignment_action_id, element_type_id, and input_value_id to retrieve the actual result values. The FND_NUMBER package reference supports numeric formatting or conversion within the supporting view layer.

Key Columns

  • locking_action_id — Identifier of the action holding the interlock, sourced from PAY_ACTION_INTERLOCKS and used to reach PAA2 and the EMEA action context.
  • action_information4 — EMEA element definition attribute retrieved from PAY_ACTION_INFORMATION, typically carrying a payment or element descriptor.
  • action_information5 — A second EMEA element definition attribute from PAY_ACTION_INFORMATION, used alongside action_information4.
  • value — The element input result value returned from PAY_EMEA_PAYMENT_VALUES_V, aliased as result_value in the view text and selected twice in the projection.

The view projects only these four columns, making it a narrow, purpose-built interface suitable for joining back to element or assignment-level reports.

Common Use Cases and Queries

Typical usage includes identifying the payment values associated with a locking action during EMEA payroll runs and reconciling locks against element definitions. Because the view is small, it is normally joined to PAY_PAYROLL_ACTIONS or PAY_ASSIGNMENT_ACTIONS for context.

  • Retrieve EMEA payment values for a specific locking action: SELECT locking_action_id, action_information4, action_information5, value FROM apps.pay_emea_paymnts_action_info_v WHERE locking_action_id = :p_locking_action_id;
  • Join to payroll actions to filter by action type: SELECT v.* FROM apps.pay_emea_paymnts_action_info_v v, apps.pay_payroll_actions ppa WHERE v.locking_action_id = ppa.payroll_action_id AND ppa.action_type = 'P';
  • Aggregate values for reconciliation: SELECT locking_action_id, SUM(value) FROM apps.pay_emea_paymnts_action_info_v GROUP BY locking_action_id;

Performance is heavily dependent on the embedded hints, particularly the ORDERED and USE_NL directives and the INDEX hint on PAY_ACTION_INTERLOCKS_PK, the primary key index referenced in the user's search. Queries that bypass the hinted join order may degrade significantly; retaining the view as supplied is strongly recommended.