Search Results ent_info25

Overview

APPS.PAY_WEBADI_BEE_CONTENT_V is a database view owned by the APPS schema in Oracle E-Business Suite. It is registered in FND Design Data as PAY.PAY_WEBADI_BEE_CONTENT_V and is flagged with the standard Oracle warning that it is for Oracle Internal Use Only. Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Its declared status is VALID, and its view type is characterized as internal.

Functionally, the view belongs to the Oracle Payroll / Oracle Payroll payment processing domain, specifically to the WebADI (Web Applications Desktop Integrator) infrastructure used to load and validate batch element entries and payment content. The name components — PAY (Payroll), WEBADI (desktop integration upload), BEE (Batch Element Entry), and CONTENT — indicate that the view exposes the content lines associated with batch element entry processing, including both attribute value sets and element entry information sets.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as a reporting and diagnostic surface over batch content data. Because batch element entry is a high-volume operation in payroll, the view is principally relevant to payroll administrators, technical consultants investigating load errors, and integration developers building extraction programs. The internal-use warning means it should be treated as a reference object rather than a supported public API; production interfaces should rely on documented concurrent programs and WebADI upload flows instead of querying the view directly.

Underlying Base Objects

The documented referenced base objects span several functional areas. Payroll batch structures are represented through the synonyms PAY_BATCH_LINES and PAY_MESSAGE_LINES, which supply the batch header/line identity and any processing messages. Payment-related configuration is drawn from PAY_ORG_PAYMENT_METHODS_F, PAY_ORG_PAYMENT_METHODS_F_TL, PAY_PAYMENT_TYPES, and PAY_PAYMENT_TYPES_TL, providing organization payment methods and payment type definitions with their translated descriptions. Personal payment method details come from PAY_PERSONAL_PAYMENT_METHODS_F.

Person and assignment information is resolved from PER_PEOPLE_F, HR_PERSON_NAME, HR_ORGANIZATION_UNITS, HR_LOOKUPS, and the packages HR_API, HR_GENERAL, and HR_SECURITY. Security and access control are therefore embedded in the view's resolution logic via HR_SECURITY. Batch element entry processing logic is encapsulated in the PAY_PAYWSQEE_PKG package, confirming the view's link to the web batch element entry process.

Key Columns

The view exposes identity and status columns: BATCH_ID and BATCH_LINE_ID are the numeric keys linking content to the underlying batch and batch line; BATCH_LINE_STATUS describes processing state; OBJECT_VERSION_NUMBER supports concurrent update detection; ASSIGNMENT_ID and ASSIGNMENT_NUMBER identify the payroll assignment in context.

Two large repeating groups carry the payload. ATTRIB_CATEGORY plus ATTRIB1 through ATTRIB20 hold attribute values, each an optional VARCHAR2(150). ENT_INFO_CATEGORY plus ENT_INFO1 through ENT_INFO30 hold element entry information values, likewise VARCHAR2(150). The column ENT_INFO25 is the twenty-fifth slot of this entry information group and is the specific item users search for when extracting or validating a particular informational field. DATE_EARNED indicates the earning date, and PERSONAL_PAYMENT_METHOD_ID links to the individual's payment method.

Common Use Cases and Queries

• Diagnosing batch element entry upload failures by inspecting BATCH_LINE_STATUS and any PAY_MESSAGE_LINES output.
• Extracting element entry information values, including ENT_INFO25, for reconciliation or data migration.
• Validating personal payment method assignment against the loaded batch content.
• Building read-only extracts constrained by HR security for authorized personnel.

A representative query filters batch content and returns the targeted information slot:

SELECT batch_id, batch_line_id, batch_line_status, assignment_id, assignment_number, ent_info25, date_earned FROM apps.pay_webadi_bee_content_v WHERE batch_id = :p_batch_id AND ent_info25 IS NOT NULL;

Joining to HR_ORGANIZATION_UNITS or PER_PEOPLE_F through the assignment columns allows reporting by organization or person. Because the object is internal and unsupported, any such query should be confined to diagnostic or read-only reporting use, and production integration should use Oracle's supported batch element entry and WebADI programs.