Search Results pay_webadi_bee_content_v




Overview
Explore in AI Chat

Overview

PAY_WEBADI_BEE_CONTENT_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PAY (Payroll) product family and is primarily associated with the WebADI (Web Applications Desktop Integrator) Batch Element Entry (BEE) functionality. The view exposes batch line data together with associated assignment, entry information, and descriptive context, so it serves as a reporting and integration layer for payroll batch element entry content that originates from WebADI uploads.

The view is registered as VALID in the ETRM repository and is catalogued as a standard APPS-owned view. It abstracts the complexity of the underlying batch line tables and the HR lookup and security logic, presenting a consolidated, denormalised structure that is convenient for downstream reporting, data extraction, and interface building. Because the view relies on several HR and PAY packages and views, its output is dynamically resolved at runtime based on the caller's security profile and the prevailing payroll configuration.

Underlying Base Objects

The documented referenced base objects fall into several functional groups. Core batch data is sourced from the PAY_BATCH_LINES synonym and the PAY_MESSAGE_LINES synonym. Payment configuration and method data come from PAY_ORG_PAYMENT_METHODS_F, PAY_ORG_PAYMENT_METHODS_F_TL, PAY_PAYMENT_TYPES, PAY_PAYMENT_TYPES_TL, and PAY_PERSONAL_PAYMENT_METHODS_F. Person and assignment context is provided by PER_PEOPLE_F and related HR views and packages, including HR_API, HR_GENERAL, HR_LOOKUPS, HR_ORGANIZATION_UNITS, HR_PERSON_NAME, and HR_SECURITY. The packaged logic in PAY_PAYWSQEE_PKG supports the WebADI batch element entry processing that this view reflects.

Because the view draws on HR_SECURITY and related HR API packages, row visibility is governed by Data Security Group (DSG) and security profile rules applied to the requesting user, meaning the result set is not a naïve union of all batch lines.

Key Columns

The view projects BATCH_ID and BATCH_LINE_ID as the primary identifiers for the batch and the individual batch line. BATCH_LINE_STATUS is translated through a DECODE against HR_LOOKUPS (LOOKUP_TYPE = 'BATCH_STATUS'), replacing the code with its descriptive MEANING. OBJECT_VERSION_NUMBER supports optimistic locking and change tracking.

Assignment context is exposed through ASSIGNMENT_ID and ASSIGNMENT_NUMBER. The view also carries a full descriptive flexfield attribute block (ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE20, aliased ATTRIB1 to ATTRIB20) and a secondary descriptive block (ENTRY_INFORMATION_CATEGORY and ENTRY_INFORMATION1 through ENTRY_INFORMATION25, aliased ENT_INFO1 to ENT_INFO25). These two blocks provide the payload of the batch element entry and are the primary reason the view is used for reporting.

Additional columns are drawn from the referenced base objects to supply payment method, payment type, person name, and organisation context, although the view text excerpt truncates before the full column list is displayed.

Common Use Cases and Queries

Typical usage includes reporting on WebADI batch element entry loads, validating uploaded content before payroll processing, and feeding downstream interfaces that require batch line level detail. A simple query to inspect batch line statuses is:

  • SELECT batch_id, batch_line_id, batch_line_status, assignment_number FROM pay_webadi_bee_content_v WHERE batch_id = :batch_id;
  • SELECT batch_id, batch_line_id, assignment_id, ent_info1, ent_info2 FROM pay_webadi_bee_content_v WHERE assignment_number = :assignment_number;
  • SELECT batch_line_status, COUNT(* ) FROM pay_webadi_bee_content_v GROUP BY batch_line_status;

Because HR security is applied, queries should be executed under a responsibility whose security profile grants access to the relevant assignments. For performance, filter on BATCH_ID, BATCH_LINE_ID, or ASSIGNMENT_ID where possible, as unrestricted scans can invoke the underlying HR package calls repeatedly.