Results for “open_order”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.AST_EVENT_ORDER_PKG is a private PL/SQL package belonging to the Oracle Advanced Sourcing / Event Management (AST) product family. Its business purpose is to bridge the event registration flow with Oracle Order Entry (OE). When a customer registers for a sourcing event or related activity that carries a financial consequence — such as a registration fee, subscription, or paid participation — the registration flow must produce a valid order that can be priced, validated, and posted through the standard Oracle Order Management pipeline. This package encapsulates that integration, allowing the AST registration logic to create and submit orders without directly embedding Order Entry API calls throughout the event code.
The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling schema rather than the package owner. This is consistent with Oracle EBS coding standards for shared application packages, and it requires that the invoking session have the appropriate privileges on the underlying OE and AST objects. The package is documented as Private API for every procedure, which indicates it is intended for internal use by other AST code rather than as a supported public interface for customer extensions.
Key Procedures and Functions
- OPEN_ORDER — Initializes the order entry process for the current event registration flow. It establishes the order header context, capturing the customer party and account, currency, source code, order type, price list, employee, invoice party information, and an optional quote header reference. This procedure must be called before lines can be added. The source code defaults to
'ASO'and the order type defaults to a seeded value (1000), which the documentation itself flags as needing confirmation againstOE_TRANSACTION_TYPES_ALL. - ADD_ORDER_LINE — Adds a new line item to the order currently being built for the event registration flow. It captures shipping party and site, inventory item, list price, quantity (default 1), discount and discount UOM, unit of measure (default
'Ea'), and price list line references. Each invocation appends a line to the in-progress order. - SUBMIT_ORDER — Submits the accumulated order to the Oracle Order Entry module for validation, processing, and posting. This final step hands the completed order to the standard OM workflow, where normal booking, pricing, and fulfillment rules apply. It should be invoked once the header (via OPEN_ORDER) and all desired lines (via ADD_ORDER_LINE) have been defined.
Tables Accessed
The documented metadata lists PLITBLM as a referenced table (via APPS synonyms). PLITBLM is a standard EBS temporary/interface table used in pricing and list-processing contexts; it is typically populated transiently during pricing calculations rather than treated as a permanent business table. Beyond this documented reference, the package logically interacts with Oracle Order Entry entities such as OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and OE_TRANSACTION_TYPES_ALL, since it initializes, populates, and submits orders through the OM APIs. The metadata confirms the OE_TRANSACTION_TYPES_ALL relationship explicitly through the open_order parameter comment, which identifies the order type as a foreign key to that view.
Usage Notes
Because all three procedures are classified as Private, AST_EVENT_ORDER_PKG is not a supported extension point and is not exposed for direct customer invocation. In practice it is called by the AST event registration code path — typically triggered when a user completes a paid registration through the Event Management or iProcurement/Sourcing registration interface. The package is referenced by zero other documented packages, reinforcing its role as a leaf-level implementation detail within the AST module rather than a shared utility.
When diagnosing issues involving an order that should have been generated from a sourcing event, technical consultants should trace execution through OPEN_ORDER, ADD_ORDER_LINE, and SUBMIT_ORDER in sequence, and verify that the source code, order type, and price list parameters supplied at header creation are valid. Because the package uses AUTHID CURRENT_USER, privilege errors on the OE objects will surface under the calling schema, and any customization that reuses these procedures must run under a schema with the requisite grants. This package is specific to the 12.1.1 and 12.2.2 code lines and should be reviewed against the current file version in each environment before troubleshooting.
-
PACKAGE: APPS.CRP_PLANNER_PK 12.2.2
-
PACKAGE: APPS.CRP_PLANNER_PK 12.1.1