Search Results ap_web_parent_pkg




Overview
Explore in AI Chat

Overview

AP_WEB_PARENT_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Payables family of self-service web applications, specifically the Internet Expenses and Web Expenses module, and is classified in ETRM as an OTHER API type rather than a formal public API. Its principal business function is to construct and manage the hierarchical "parent" data structures that drive the web-based expense report entry pages rendered through Oracle Application Framework (OAF) and related HTML interfaces. This includes assembling structured PL/SQL source fragments and mapping custom array constructs into bindable columns so that dynamic regions of the expense entry flow can be populated correctly at runtime.

The documented metadata confirms the package is VALID in the ETRM repository and that it is not referenced by any other database object, although it itself depends on a substantial set of APPS packages, tables, and views. It therefore acts as an internal helper layer within the Web Expenses stack rather than as an integration surface for external callers.

Key Procedures and Functions

ETRM documents four procedures and functions within this package body:

  • STRING2PLSQL — The core utility that converts a delimited or formatted string into a PL/SQL code fragment. It is used to translate stored or user-supplied configuration strings into executable dynamic SQL/PLSQL blocks consumed by the web expense pages.
  • STRING2PLSQL_HEADER — A variant specialised for building header-level PL/SQL fragments, typically associated with the top section of an expense report template or parent record. It follows the same string-to-code pattern as the core routine but targets header attribute generation.
  • STRING2PLSQL_RECEIPTS — A variant specialised for receipts-related constructs. It generates the PL/SQL fragments needed to represent and validate receipt information within the parent structure.
  • MAPCUSTOMARRAYTOCOLUMN — Maps entries from a custom PL/SQL array (associative array, nested table, or varray) into named columns suitable for binding into a query, cursor, or web region. This supports flexible, template-driven column layouts in the expense entry UI.

No parameter lists are documented in the ETRM metadata; callers must consult the package specification source for exact signatures.

Tables Accessed

The package accesses the following database objects, primarily through APPS synonyms:

  • AP_EXPENSE_REPORT_PARAMS — Stores configuration parameters controlling expense report behaviour (policy, template, and processing options). The package reads these to determine which parent structures and dynamic fragments to build.
  • PA_PROJECTS — Provides project definitions used when expense lines are charged to projects. It supplies project context needed to construct project-related parent attributes and validation.

Additional dependencies documented by ETRM include the views PA_PROJECTS_EXPEND_V, PA_TASKS, PA_TASKS_EXPEND_V, and HR_EMPLOYEES_CURRENT_V, along with sibling packages AP_WEB_DB_AP_INT_PKG, AP_WEB_DB_EXPTEMPLATE_PKG, AP_WEB_DB_HR_INT_PKG, AP_WEB_DFLEX_PKG, AP_WEB_PROJECT_PKG, and AP_WEB_UTILITIES_PKG. Standard facilities such as FND_MESSAGE, FND_PROFILE, GL_CURRENCY_API, ICX_SEC, and APP_EXCEPTION are also referenced, indicating the package raises user-facing messages, reads profile options, and performs currency and security handling.

Usage Notes

AP_WEB_PARENT_PKG is invoked internally by the Oracle Internet Expenses / Web Expenses UI layer, principally when an OAF page or HTML region needs to assemble parent-level expense data. It is not intended for direct invocation by customer code, and ETRM records no database objects referencing it, confirming its position as a leaf dependency in the call graph.

Typical invocation contexts include:

  • Expense report entry and template rendering in the self-service Web Expenses responsibility.
  • Concurrent or online processing where dynamic PL/SQL fragments must be generated from template strings.
  • Custom extensions that require header, receipt, or parent-array mapping behaviour can reference the documented procedures, but must do so through the supported public specification and with awareness that the object is classified as OTHER, not as a supported public API.

Because the package is not documented as a public API and is referenced by no other database object, extensions should avoid direct dependencies and instead rely on the AP_WEB utility packages documented as its peers. Any modification to its logic falls under Oracle's standard support policy for internal Web Expenses objects.