Search Results get_activity_result

Overview

The APPS.OE_LINE_FULLFILL package provides the fulfillment-set processing engine for Oracle Order Management in Oracle E-Business Suite 12.1.1 and 12.2.2. A fulfillment set is a configuration of order lines whose fulfillment activities must be coordinated so that the lines are fulfilled (or cancelled) as a unit rather than independently. The package encapsulates the business rules that determine whether a line belongs to a fulfillment set, executes the fulfillment workflow for a single line or set, retrieves the current fulfillment activity associated with a line, and supports cancellation of in-progress fulfillment. It is classified under the ETRM API classification of OTHER, indicating that it is an internal, Oracle-owned processing package rather than a published integration API. The package is part of the Oracle Order Management fulfillment infrastructure and reflects the header stamp OEXVFULS.pls, version 120.0.12010000.1, dated 2008/07/25.

Key Procedures and Functions

• IS_PART_OF_FULFILLMENT_SET — A function that determines whether a given order line participates in a fulfillment set, returning the indicator value used by callers to decide whether set-level processing is required.
• FULFILL_LINE — The primary fulfillment routine. It accepts a line record and line table in the OE_ORDER_PUB structures, a processing mode, a fulfillment type, and a fulfillment activity, and returns a status. It drives fulfillment of the line, including the requirement that other members of the same fulfillment set be fulfilled consistently.
• PROCESS_FULFILLMENT — Wraps fulfillment processing for a line and activity combination, returning a result flag and the standard FND error-handling outputs (return status, message count, message data). It is the entry point most often invoked where full error propagation is required.
• GET_FULFILLMENT_ACTIVITY — Returns the fulfillment activity name for a line identified by item key and activity identifier.
• GET_ACTIVITY_RESULT — Retrieves the result, status code, and activity identifier for a named workflow activity on an item, allowing callers to inspect the outcome of a previously executed fulfillment step.
• CANCEL_LINE — Cancels fulfillment for a line. A later revision added the p_fulfill_operation parameter (referenced in the source as Bug2068310) to distinguish the cancellation context.
• GET_FULFILLMENT_SET — Returns the set of lines that constitute the fulfillment set for a given line, using the Line_Set_Tbl_Type collection defined in the package.
• FULFILL_SERVICE_LINES — Extends fulfillment processing to service lines associated with the fulfillment set, ensuring that service and goods lines are handled together.

The package also declares the record type Line_Set_Rec_Type with line_id, set_id, type, fulfilled_flag, and ordered_quantity attributes, plus the Line_Set_Tbl_Type and processed_set collection types used to pass and track set membership.

Tables Accessed

• OE_ORDER_HEADERS / OE_ORDER_HEADERS_ALL — Header context for the order being fulfilled.
• OE_ORDER_LINES / OE_ORDER_LINES_ALL — Line attributes, fulfillment flags, and quantity data updated or read during processing.
• OE_SETS and OE_LINE_SETS — Define fulfillment set membership and the relationship between a line and its set.
• OE_BLANKET_HEADERS, OE_BLANKET_HEADERS_EXT, OE_BLANKET_LINES, OE_BLANKET_LINES_EXT — Blanket agreement context referenced when fulfillment applies to blanket-sourced lines.
• RA_RULES — Accounting rule data consulted for line processing.
• WF_ITEM_ACTIVITY_STATUSES and WF_PROCESS_ACTIVITIES — Oracle Workflow activity status and definition tables used to determine the current fulfillment activity and its result.
• PLITBLM — The PL/SQL table used by the Oracle Forms infrastructure, indicating form-driven invocation.

Usage Notes

OE_LINE_FULLFILL is an internal Oracle Order Management package invoked by the Order Management forms and by the fulfillment workflow rather than by customer-facing integration APIs. It is referenced by seven other packages, which confirms its role as a shared utility within the OM fulfillment stack. Custom code should generally avoid calling it directly, preferring OE_ORDER_PUB procedures; where direct invocation is unavoidable, callers must supply the OE_ORDER_PUB line record and table types, handle the FND-style x_return_status, x_msg_count, and x_msg_data outputs, and respect the fulfillment set semantics enforced by IS_PART_OF_FULFILLMENT_SET and GET_FULFILLMENT_SET. The package is present with the same documented procedure set in both 12.1.1 and 12.2.2. The search term "Fill me fly" does not correspond to any documented object or parameter; it is best understood as a colloquial spelling of "fulfill."