Search Results g_request_type

Overview

QP_RQT_UTIL is a utility PL/SQL package in the Oracle E-Business Suite Advanced Pricing (QP) module. Its name reflects its purpose: "RQT" denotes "Request Type," the pricing entity used to qualify or group pricing entities such as price lists, qualifiers, and modifiers. The package centralizes the low-level data manipulation logic required to create, maintain, and query request type records stored in the QP_PTE_REQUEST_TYPES tables. Rather than embedding this logic in individual forms or concurrent programs, Oracle exposes it through a single reusable package so that all callers apply consistent validation, attribute mapping, and multi-language handling.

The package is declared AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking schema rather than the package owner. The header also defines a large block of global constants — G_ATTRIBUTE1 through G_ATTRIBUTE15, G_CONTEXT, audit columns such as G_CREATED_BY and G_LAST_UPDATE_DATE, structural flags G_LINE_LEVEL_GLOBAL_STRUCT and G_ORDER_LEVEL_GLOBAL_STRUCT, and notably G_REQUEST_TYPE := 31 together with G_REQUEST_TYPE_DESC := 32. These constants provide stable numeric identifiers for the columns of the request type record, which is the field the user searched for via "g_request_type."

Key Procedures and Functions

The ETRM metadata documents twelve programmable units within the package:

• CLEAR_DEPENDENT_ATTR — Resets attributes that depend on a parent request type value so stale dependent data are not retained.
• APPLY_ATTRIBUTE_CHANGES — Applies a set of attribute-level changes to a request type record.
• COMPLETE_RECORD — Populates default or missing column values to produce a complete request type record.
• CONVERT_MISS_TO_NULL — Translates the FND_API "miss" sentinel values into database nulls.
• UPDATE_ROW — Updates an existing request type row.
• INSERT_ROW — Inserts a new request type row.
• DELETE_ROW — Removes a request type row.
• QUERY_ROW — Retrieves a single request type record.
• QUERY_ROWS — Retrieves a set of request type records.
• LOCK_ROW — Obtains a row-level lock prior to modification.
• GET_VALUES — Returns displayed or translated values for request type attributes.
• GET_IDS — Returns the internal identifiers associated with request type values.

The INSERT_ROW, UPDATE_ROW, DELETE_ROW, and QUERY_ROW/QUERY_ROWS procedures form a conventional CRUD layer, while LOCK_ROW and the attribute helpers support concurrency and validation.

Tables Accessed

The package references the following tables through APPS synonyms:

• QP_PTE_REQUEST_TYPES_B — the base table holding request type definitions; the primary target of insert, update, delete, and query operations.
• QP_PTE_REQUEST_TYPES_TL — the translation table supplying language-specific request type descriptions, used by GET_VALUES and related lookups.
• FND_LANGUAGES — the language registry, consulted to resolve the current session language for translated descriptions.
• PLITBLM — the PL/SQL integer table used for bulk processing.

Usage Notes

QP_RQT_UTIL is classified as a UTIL package and is referenced by four other packages in the pricing schema, indicating it acts as a shared foundation for higher-level business APIs. It is typically invoked from Advanced Pricing setup forms and from concurrent programs that maintain request type definitions, and it may be called from custom code that needs to manipulate request types without reimplementing validation and translation logic. Because the package uses AUTHID CURRENT_USER and relies on APPS synonyms, custom callers should be granted appropriate privileges and should treat the documented signatures as the supported interface. The global constant G_REQUEST_TYPE := 31 is the key reference point for developers mapping the request type column position during attribute processing.