Search Results create_and_start_flow

Overview

OE_BLANKET_WF_UTIL is an Oracle E-Business Suite PL/SQL utility package owned by APPS that provides the workflow integration layer for Oracle Order Management blanket sales agreements. Its principal responsibility is to initiate and drive the Oracle Workflow processes associated with blanket agreement life-cycle events, such as negotiation completion, customer acceptance or rejection, extension, release, closure, and termination. Within the ETRM classification scheme this package is designated as a UTIL object, meaning it is intended primarily for internal consumption by Order Management APIs and concurrent processes rather than as a formally published public API. In Oracle EBS 12.1.1 and 12.2.2 the package resides in the OEXUBWFB.pls source file, and source control records indicate a header revision of 120.1 dated November 2007.

Key Procedures and Functions

The package exposes eleven documented subprograms. CREATE_AND_START_FLOW is the central entry point: it selects the appropriate workflow item type based on the transaction phase code, sets the sales document type to blanket, and delegates to OE_ORDER_WF_UTIL.CREATESTART_HDRINTERNAL and START_ALL_FLOWS to launch the header-level flow. The remaining procedures correspond to discrete blanket agreement events, each of which raises or advances the relevant workflow activity:

• SUBMIT_DRAFT — initiates workflow processing when a blanket agreement is submitted in draft form.
• BLANKET_DATE_CHANGED — propagates effective or expiration date changes into the associated workflow.
• CUSTOMER_ACCEPTANCE / CUSTOMER_REJECTED — record the customer's response to a blanket agreement proposal and progress or halt the flow accordingly.
• CHECK_RELEASE — validates whether a release may proceed against the blanket agreement.
• EXTEND — handles extension of the blanket agreement's validity or terms.
• CLOSE — closes the blanket agreement and drives the corresponding workflow transition.
• TERMINATE — terminates the blanket agreement workflow.
• LOST — marks the blanket agreement opportunity as lost.
• COMPLETE_NEGOTIATION — signals completion of the negotiation phase and moves the agreement into its active state.

Tables Accessed

The package operates against the core Order Management blanket and order tables through APPS synonyms. OE_BLANKET_HEADERS and OE_BLANKET_LINES hold the blanket agreement header and line definitions that the flow operates upon. OE_ORDER_HEADERS and OE_ORDER_LINES are referenced because blanket releases materialize as order headers and lines, and the workflow utilities must resolve the related document context. WF_ITEMS is the Oracle Workflow runtime table, accessed as part of flow creation and progression. These accesses are consistent with the package's role as a bridge between blanket agreement data and the Workflow engine.

Usage Notes

OE_BLANKET_WF_UTIL is invoked indirectly rather than by end users. Typical invocation paths include the Blanket Sales Agreement and Sales Agreement forms in Order Management, Order Management concurrent programs that perform blanket-related batch processing, and the public OE_Blanket_Pub API layer, which maintains internal state such as header and control record types used by this utility. Because CREATE_AND_START_FLOW returns standard FND_API status values (x_return_status, x_msg_count, x_msg_data), callers should check the return status and use OE_MSG_PUB to retrieve error messages. The package is referenced by four other packages, confirming its role as a shared internal utility. Customizations should call the supported public API surface and avoid direct invocation of this utility unless the Workflow integration behavior is fully understood, since changes to item type derivation or sales document type constants could disrupt blanket agreement processing across releases. The metadata does not document explicit parameter lists for the remaining procedures, and their use should be validated against the deployed package specification in the target release.