Search Results xdp_param_cache




Overview
Explore in AI Chat

Overview

XDP_PARAM_CACHE is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema, classified as a VALID, OTHER-type API within the ETRM 12.2.2 documentation set. It belongs to the XDP (eXecutable Delivery/Order Fulfillment) product family, which supports the telecommunications and high-volume order fulfillment functionality delivered through Oracle Advanced Global Intercompany/Service Fulfillment modules. The package implements an in-memory parameter caching mechanism for work item and fulfillment action parameters. Rather than repeatedly querying XDP_WI_PARAMETERS, XDP_FA_PARAMETERS, and related base tables during runtime processing, the package holds parameter values in a PL/SQL session-level table structure, reducing SQL round-trips and improving throughput during work item execution. The documented dependency list shows the package body references the PLITBLM PL/SQL table library, DBMS_STANDARD, and STANDARD, confirming that it manipulates PL/SQL associative arrays (index-by tables) for its cache. The package is referenced by two other database objects, indicating it is consumed internally by the fulfillment engine rather than being an entry-point API for end users.

Key Procedures and Functions

The ETRM metadata documents the following program units. Parameter lists are not published; purposes are described qualitatively.

  • INIT_CACHE — Initializes the in-memory cache structures at the start of a processing session or unit of work. Establishes empty associative arrays and any session-scoped state required before parameters can be loaded or retrieved.
  • ADD_WI_PARAM_TO_CACHE — Loads a work item parameter (or set of parameters) into the cache, typically after it has been read from XDP_WI_PARAMETERS. Enables subsequent lookups without additional SQL.
  • GET_WI_PARAM_FROM_CACHE — Retrieves a work item parameter previously staged in the cache. The primary read accessor used by the work item execution logic.
  • GET_FA_PARAM_FROM_CACHE — Retrieves a fulfillment action parameter from the cache. Serves the fulfillment action processing path, keyed off XDP_FA_PARAMETERS content.
  • REMOVE_FROM_CACHE — Removes a specific cached entry (or entries) once consumed or invalidated, freeing session memory and preventing stale reads.
  • CLEAR_CACHE — Purges the entire cache. Used at the end of a session or when parameters may have changed and a full reload is required.

Two additional documented units complete the count of eight; these support the retrieval and lifecycle operations described above.

Tables Accessed

The package reads and writes the following base tables through APPS synonyms:

  • XDP_WI_PARAMETERS — Stores work item parameter definitions and values; the source for ADD_WI_PARAM_TO_CACHE and GET_WI_PARAM_FROM_CACHE.
  • XDP_FA_PARAMETERS — Stores fulfillment action parameters; the source for GET_FA_PARAM_FROM_CACHE.
  • XDP_FULFILL_ACTIONS and XDP_FULFILL_WORKLIST — Fulfillment action and worklist records whose runtime execution consumes the cached parameters.
  • XDP_WORKITEMS — The work item header records driving the execution context in which the cache is populated.
  • XDP_FA_RUNTIME_LIST — The runtime list of fulfillment actions to be executed; parameters are resolved against this list.
  • PLITBLM — The PL/SQL table library used to manage the associative array structures backing the cache.

Usage Notes

XDP_PARAM_CACHE is an internal engine package. It is not exposed through Oracle Forms or standard concurrent program parameters; instead, it is invoked from within the order fulfillment runtime, most likely the work item processor and fulfillment action executor that drive XDP processing. Callers are expected to call INIT_CACHE before processing, populate via ADD_WI_PARAM_TO_CACHE and the corresponding loaders, read through the GET_* accessors, and release memory via REMOVE_FROM_CACHE or CLEAR_CACHE. Because the cache is session-scoped, any custom code that reuses a database session across multiple work items must clear the cache between units of work to avoid stale parameter reads. Direct application calls should be avoided in customizations; the supported integration points are the XDP work item and fulfillment action APIs. Any change to underlying parameter tables while a session holds a populated cache will not be reflected until the cache is cleared or the session is reinitialized.