Results for “get_concurrent_request_ids”

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

Overview

The APPS.XDO_CP_DATA_SECURITY_PKG package body is an Oracle E-Business Suite security utility belonging to the XML Publisher (XDO) product family. Its documented filename, XDODSCRB.pls, and package header comment establish its purpose unambiguously: the package is used to retrieve concurrent requests based on the data security profile of the requesting user. In the EBS concurrent processing architecture, users are restricted to viewing only those concurrent requests that their responsibility and security profile permit. This package encapsulates the logic that evaluates those restrictions and materializes the resulting set of permissible request identifiers so that other XML Publisher components can filter their queries accordingly.

The package was created in 2006 and carries a header revision of 120.4, last modified in December 2010. It is classified as an OTHER API type rather than a public or private API in the ETRM catalog, indicating that it is intended primarily for internal consumption by Oracle-delivered code rather than as a supported customer-facing extension point.

Key Procedures and Functions

The ETRM metadata documents a single callable program unit:

• GET_CONCURRENT_REQUEST_IDS — a public function that returns a VARCHAR2 status indicator. Its documented purpose is to determine which request IDs the current user is authorized to view and to store that set in a global temporary table for downstream use. The function is declared with PRAGMA AUTONOMOUS_TRANSACTION, meaning its database operations commit or roll back independently of the caller's transaction — an appropriate design for a read-and-populate utility that must not interfere with the calling session's transactional state.

The package also declares several module-level constants that govern its behavior. The user search term g_success_status refers to the package global g_success_status VARCHAR2(1) := 'T', which holds the success return value used by GET_CONCURRENT_REQUEST_IDS. This constant is paired with g_result_yes := 'Y' and g_result_no := 'N', and with g_package_name := 'oracle.apps.xdo.xdo_cp_data_security.', which supplies the logger module prefix. Internally, the function builds a security predicate, applies it against the concurrent requests data source, and assigns the outcome to a local return status that is compared against g_success_status before the caller proceeds.

Tables Accessed

The package interacts with two documented database objects, both referenced through APPS synonyms:

• XDO_CONCURRENT_REQUESTS_GT — a global temporary table specific to XML Publisher. This is the target of the function's inserts: GET_CONCURRENT_REQUEST_IDS populates it with the request IDs the current user is permitted to view. Because it is a GTT, the rows are session-scoped, so each session receives its own isolated result set. Downstream XDO queries join to this table to enforce the data security filter efficiently, rather than reevaluating the security predicate for every row.
• PLITBLM — a standard Oracle Applications internal table, typically used to store and manipulate long VARCHAR2 values. It is referenced as a working area for assembling or tokenizing the generated security predicate, whose length may exceed ordinary PL/SQL VARCHAR2 limits before being applied.

Usage Notes

This package is invoked internally by Oracle XML Publisher concurrent processing components, generally before displaying a list of concurrent requests or before executing queries that enumerate request output. A typical invocation pattern is a call to GET_CONCURRENT_REQUEST_IDS, followed by a check of the returned status against g_success_status; on success, the caller queries XDO_CONCURRENT_REQUESTS_GT for the authorized request IDs.

Because the procedure runs under an autonomous transaction, callers cannot roll back its effects as part of their own transaction, and the populated GTT data persists for the duration of the session regardless of the caller's commit behavior. The ETRM catalog records that this package is referenced by one other package in the application, confirming its role as a supporting dependency rather than a top-level entry point.

Given its OTHER classification and the 120.4 revision level, customers and partners should not treat GET_CONCURRENT_REQUEST_IDS as a stable public API. Customizations that must apply additional data security to XML Publisher concurrent request listings should be implemented as extensions to the surrounding framework rather than by direct calls into this package, since Oracle may alter its internal predicate construction and global constants — including g_success_status — without notice in future patch levels.