Results for “message_source_type”

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

Overview

APPS.PAYBV_PAYROLL_MESSAGE_V is a payroll diagnostic view within Oracle E-Business Suite, delivered as part of the HRMS payroll schema and typically associated with the "Payroll Batch Viewer" (PAYBV) functionality. The view consolidates payroll processing messages generated during payroll runs and other payroll actions, exposing them in a denormalized form suitable for user-facing inquiry screens, concurrent program output, and integration extracts. A single row represents one message line attached either to a payroll action (process-level message) or to a specific assignment action (assignment-level message). Because it joins payroll action data to person and assignment attributes, the view answers the practical question of "what messages did this payroll run or this employee's assignment produce?" The MESSAGE_SOURCE_M column, which the user searched on, is the decoded (translated) form of the internal SOURCE_TYPE code, distinguishing messages that originate from payroll processes ('P') and related sources. Defining the view in the APPS schema, with the same definition available in both 12.1.1 and 12.2.2, allows customers to build custom reports, OAF pages, or extracts upon a stable interface rather than against the underlying base tables directly.

Underlying Base Objects

The documented view metadata references a mix of base objects, each serving a distinct purpose:

• PAY_PAYROLL_ACTIONS (synonym) — the driving table; each row identifies a payroll action, its action type, status, effective date, and request ID.
• PAY_MESSAGE_LINES (synonym) — stores the individual message lines, keyed by source type and source ID, message level, line sequence, and line text.
• PAY_PAYROLLS_F (view) — the date-tracked payroll definition; joined by PAYROLL_ID and the action's effective date range to obtain the payroll name and business group.
• PAY_ASSIGNMENT_ACTIONS (synonym) — provides assignment-level action rows and their status codes.
• PER_PEOPLE_F and PER_ASSIGNMENTS_F (views) — date-tracked person and assignment data supplying FULL_NAME and ASSIGNMENT_NUMBER.
• HR_BIS and HR_GENERAL (packages) — supply BIS_DECODE_LOOKUP and DECODE_LOOKUP for translating lookup codes into MESSAGE_SOURCE_M, SEVERITY_LEVEL_M, and PROCESS_TYPE_M, plus GET_SEC_PROFILE_BG_ID for business-group security.
• HR_PAYROLLS (package) — DISPLAY_PERIOD_NAME yields the period name for the action.
• PAY_PAYROLL_ACTIONS_PKG and PAY_ASSIGNMENT_ACTIONS_PKG (packages) — V_ACTION_STATUS and GET_ACTION_STATUS return the derived payroll action and assignment action statuses.
• HR_SECURITY and HR_PERSON_NAME (packages) — support security enforcement and name formatting.

Key Columns

• PAYROLL_NAME / PERIOD_NAME — the payroll and its display period for the action.
• PROCESS_TYPE / PROCESS_TYPE_M — the action type code and its decoded description.
• PROCESS_DATE — the effective date of the payroll action.
• PAYROLL_ACTION_STATUS — the derived status of the payroll action.
• FULL_NAME / ASSIGNMENT_NUMBER / ASSIGNMENT_ACTION_STATUS — populated for assignment-level messages, NOT NULL only for the assignment branch.
• SEVERITY_LEVEL / SEVERITY_LEVEL_M — the message level code and decoded severity (e.g., warning, error).
• MESSAGE_LINE / LINE_SEQUENCE — the message text and its ordering within the message set.
• MESSAGE_SOURCE / MESSAGE_SOURCE_M — the source type code and its decoded description; the searched column.
• PAYROLL_ACTION_ID / PAYROLL_ID / REQUEST_ID / ASSIGNMENT_ACTION_ID — surrogate keys for drilling into detail.
• BG_SECURITY_FLAG_CODE — 'Y'/'N' indicating whether the row passes business-group security.

Common Use Cases and Queries

The principal use case is presenting payroll messages for a given payroll action, period, or employee. Filtering by MESSAGE_SOURCE_M allows users to isolate messages from a particular source. For example:

SELECT payroll_name, period_name, process_type_m, process_date, severity_level_m, message_line FROM apps.paybv_payroll_message_v WHERE payroll_action_id = :p_action_id ORDER BY line_sequence;

To inspect messages from a specific source:

SELECT payroll_name, full_name, assignment_number, severity_level_m, message_line FROM apps.paybv_payroll_message_v WHERE payroll_id = :p_payroll_id AND message_source_m = :p_source AND bg_security_flag_code = 'Y';

Because the view enforces business-group security inline and decodes lookup codes, it is well suited to custom OAF pages, XML Publisher reports, and interface extracts where decoded, security-filtered payroll diagnostics are required.