Results for “message_source”

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

Overview

The PAYBV_PAYROLL_MESSAGE_V view is a business-facing (BV) reporting object owned by the APPS schema within the Oracle Payroll (PAY) module. It consolidates payroll processing messages generated during payroll runs and assignment-level actions into a single, security-aware result set suitable for reporting, integration, and diagnostic purposes. Its primary role is to present log and error information produced by the payroll engine, mapping internal coded values into descriptive, lookup-decoded forms so that downstream reports and interfaces need not resolve lookup meanings themselves.

Because the view is defined over payroll actions, payroll definitions, and message lines, it acts as the authoritative source for answering questions such as "what messages were raised during this payroll run," "how severe were they," and "which payroll action or assignment action produced them." The presence of MESSAGE_SOURCE_TYPE (exposed through the MESSAGE_SOURCE and decoded MESSAGE_SOURCE_M columns) is central to this purpose, distinguishing messages originating at the payroll-action level from those at the assignment-action level.

Underlying Base Objects

The view is defined as a UNION of two queries, joined across the following documented objects:

• PAY_PAYROLL_ACTIONS (synonym) — the payroll action being processed; supplies action type, status, effective date, and request ID.
• PAY_PAYROLLS_F (view) — the payroll definition, supplying the payroll name and business group for security filtering.
• PAY_MESSAGE_LINES (synonym) — the actual message text, level, source type, source ID, and line sequence. The join is restricted by PML.SOURCE_TYPE = 'P' and PML.SOURCE_ID = PAC.PAYROLL_ACTION_ID in the payroll-action branch.
• PAY_ASSIGNMENT_ACTIONS (synonym) and PAY_ASSIGNMENT_ACTIONS_PKG (package) — provide assignment-level action status in the second UNION branch.
• PER_ASSIGNMENTS_F and PER_PEOPLE_F (views) — supply assignment number and employee full name.
• PAY_PAYROLL_ACTIONS_PKG — resolves the payroll action status, and the V_ACTION_STATUS function is invoked directly.
• HR_BIS, HR_GENERAL, HR_PAYROLLS, HR_PERSON_NAME, HR_SECURITY (packages) — provide lookup decoding, period naming, and business-group security profile resolution.

Key Columns

• PAYROLL_NAME — name of the payroll for the action.
• PERIOD_NAME — display period name derived from the payroll action.
• PROCESS_DATE — effective date of the payroll action.
• PAYROLL_ACTION_STATUS — resolved action status via PAY_PAYROLL_ACTIONS_PKG.V_ACTION_STATUS.
• SEVERITY_LEVEL / SEVERITY_LEVEL_M — raw and lookup-decoded message level (e.g., warning, error).
• MESSAGE_SOURCE / MESSAGE_SOURCE_M — raw SOURCE_TYPE and its decoded form via HR_BIS.BIS_DECODE_LOOKUP('MESSAGE_SOURCE_TYPE', PML.SOURCE_TYPE). This is the column referenced by the search term message_source_type.
• MESSAGE_LINE — the text of the message.
• LINE_SEQUENCE — ordering within a message set.
• FULL_NAME / ASSIGNMENT_NUMBER — populated in the assignment-level branch, NULL at payroll level.
• BG_SECURITY_FLAG_CODE — 'Y'/'N' indicator derived from business-group security profile matching.

Common Use Cases and Queries

Typical scenarios include troubleshooting failed payroll runs, auditing messages per payroll period, and feeding a BI/reporting layer with decoded severity and source values.

SELECT payroll_name,
       period_name,
       process_date,
       severity_level_m,
       message_source_m,
       message_line
FROM   apps.paybv_payroll_message_v
WHERE  payroll_name = :p_payroll_name
AND    process_date BETWEEN :p_from AND :p_to
ORDER  BY process_date, line_sequence;

To isolate payroll-level source types specifically:

SELECT payroll_action_id,
       message_source,
       message_source_m,
       severity_level_m,
       message_line
FROM   apps.paybv_payroll_message_v
WHERE  message_source = 'P'
AND    bg_security_flag_code = 'Y';

Because the view already applies business-group security filtering, it is safe to expose in self-service reports without additional security predicates. Note that assignment-level columns remain NULL in the payroll-action branch, so reports should account for this UNION behavior.