Search Results get_seq_num

Overview

APPS.BEN_BENXAUDT_XMLP_PKG is a PL/SQL package that supports the Oracle EBS Benefits audit reporting infrastructure. In the Oracle E-Business Suite 12.1.1 and 12.2.2 releases, packages named with the _XMLP_PKG suffix act as the PL/SQL backing for XML Publisher (BI Publisher) concurrent program report definitions. The name segment BENXAUDT identifies this package as belonging to the Benefits (BEN) product family and specifically to an audit-trail style report, while XMLP confirms its role in the XML Publisher report execution model.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer. This is the standard convention for APPS-owned report packages and ensures that any data queries performed during report execution are subject to the caller's security context, including any Benefits security profiles or row-level restrictions in force. The package declares a small set of package-level globals (P_REQUEST_ID, P_RECORD_FROM, P_RECORD_TO, P_CONC_REQUEST_ID, and g_counter) that carry concurrent request context and a running counter across report phases.

Key Procedures and Functions

• GET_SEQ_NUM — A procedure that generates or retrieves a sequence number used to order or identify audit records within the report output. Given the presence of the g_counter global, this procedure is the likely mechanism that increments and maintains that counter across the record set processed by the report. Users searching "get_seq_num" are typically looking for the source of a sequence or line-numbering value that appears in the report layout.
• VALUEFORMULA — A function that returns a VARCHAR2 value for a given record. Its parameters relate to an external record identifier, an external result detail identifier, and a sequence number, indicating it derives a display value for each detail row of the audit report.
• BUSINESS_NAMEFORMULA — A function returning a VARCHAR2 business name, parameterized by business group ID. In Benefits, the business group determines the legislation and configuration context, so this function resolves an organization or business-group display name for the report header or row output.
• BETWEENPAGE — A Boolean function invoked by the XML Publisher report engine at page boundaries, typically used to control page-level logic such as repeating headers or suppressing content between pages.
• BEFOREREPORT — The standard report trigger executed once before the report data is fetched. It is used to initialize package globals, validate concurrent program parameters such as the record range, and prepare the report environment.
• AFTERREPORT — The complementary report trigger executed once after data retrieval completes, used for cleanup or final status handling.

Tables Accessed

The documented table reference for this package is HR_ALL_ORGANIZATION_UNITS, accessed through an APPS synonym. This table stores organization definitions, including the business group and organization hierarchy records. The report uses it most plausibly to resolve organization or business group names for the audit output, consistent with the BUSINESS_NAMEFORMULA function's parameter. No other base tables are documented, and the package neither stores nor updates persistent data of its own; its role is read-only with respect to the database.

Usage Notes

BEN_BENXAUDT_XMLP_PKG is not intended for direct invocation from Forms or custom PL/SQL. It is bound to an XML Publisher concurrent program definition and is executed by the Oracle Reports/BI Publisher runtime when that concurrent program is submitted. The BEFORE/BETWEEN/AFTER report triggers are called automatically by the report engine, while the formula functions are invoked from the report data model and layout templates. The package is referenced by zero other packages in the documented metadata, confirming it is a terminal, report-dedicated component. Because it is AUTHID CURRENT_USER and owned by APPS, it should be treated as an Oracle-supplied object; modifications are not supported. Support personnel investigating "get_seq_num" behavior should expect the sequence value to be governed by g_counter and reset per report run through BEFOREREPORT.