Search Results icx_req_submit




Overview
Explore in AI Chat

Overview

APPS.ICX_REQ_SUBMIT is a PL/SQL package in the Oracle E-Business Suite that supports the final submission processing of shopping carts and requisitions within the iProcurement and Internet Procurement (ICX) application stack. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references resolve against the privileges of the invoking schema rather than the package owner, which is significant because the package is executed from within Web-based requisition flows where the session user is typically a self-service application user.

The package header header comment ($Header: ICXRQSMS.pls 115.4 99/07/17) places its origin in the early Internet Procurement generation, and the same interface has been carried forward into Oracle EBS 12.1.1 and 12.2.2 with minimal structural change. Its role is to bridge the interactive shopping-cart user interface with the requisition submission logic, including the collection of header-level descriptive and assignment attributes, delivery and destination information, requestor and approver detail, and the handling of submission errors.

Key Procedures and Functions

The ETRM metadata documents three procedures for this package:

  • SHOW_END — Terminates or finalizes the display phase of the requisition submission flow. It accepts the shopping cart identifier, an emergency indicator, and a user action indicator, and is responsible for rendering the closing state of the submission page.
  • FINALSUBMIT — The principal submission entry point. It drives the actual submission of a shopping cart identified by icx_cart_id, accepting the user action together with a broad set of optional header attributes. These include the approver identifier and name, deliver-to location and requestor identifiers, destination organization, shopper, need-by date, notes to approver and buyer, header description, requisition organization and location, and ten generic descriptive flexfield header attributes (attribute1 through attribute10). Most of these default to FND_API.G_MISS_CHAR, following standard EBS API convention so that the caller may leave values unset.
  • STOREERROR — Persists error information generated during cart submission, allowing validation or processing failures to be recorded and subsequently surfaced to the user.

The package also declares a PL/SQL associative array type, defaultParamType (a table of VARCHAR2(250) indexed by BINARY_INTEGER), and a package-level instance named empty_table. The empty_table constant is the object most directly associated with the search term "empty_table": it is an unpopulated collection used as a neutral default argument, typically where a parameterized routine must receive a collection but the caller has no data to supply.

Tables Accessed

The package operates against the core iProcurement cart and requisition structures. ICX_SHOPPING_CARTS and ICX_SHOPPING_CART_LINES hold the cart header and line data being submitted, while ICX_CART_DISTRIBUTIONS and ICX_CART_LINE_DISTRIBUTIONS carry the accounting and delivery distributions applied at header and line level. Errors are written to and read from ICX_REQ_CART_ERRORS and its sequence-backed sibling ICX_REQ_CART_ERRORS_S, which are the persistence targets of STOREERROR. Item validation and description enrichment draw on MTL_SYSTEM_ITEMS and the key flexfield view MTL_SYSTEM_ITEMS_KFV. Currency handling references FND_CURRENCIES, and organization-level defaults are taken from FINANCIALS_SYSTEM_PARAMETERS. PO_UNIQUE_IDENTIFIER_CONTROL is consulted in connection with unique identifier assignment for the resulting requisition. Utility references include DUAL, the HTP and OWA_UTIL packages for HTML output generation during the submission flow, and PLITBLM for PL/SQL table-to-buffer manipulation.

Usage Notes

ICX_REQ_SUBMIT is invoked as part of the online iProcurement requisition submission path rather than through standalone concurrent programs. The typical caller is the Web-based shopping cart submission flow, with the procedures exposed to the middle tier so that the final submission page and subsequent processing execute server-side. The package is referenced by three other packages within the EBS code set, indicating that other ICX components depend on its submission and error-handling routines. Because the header interface is attribute-rich and defaults to FND_API.G_MISS_CHAR, custom code integrating with the package should populate only the attributes relevant to the requirement header and leave the remainder unset, relying on the standard EBS convention that missing-character defaults are ignored during processing. Error handling should be anticipated through the ICX_REQ_CART_ERRORS tables, which provide the diagnostic record for any submission rejected by the flow.