Search Results launch_resubmission_fas

Overview

XDPCORE_ORU is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM metadata as an "OTHER" API type. It forms part of the Oracle Telecommunications/Order Fulfillment infrastructure associated with the XDP (eXtensible Data Platform / provisioning) product family. The package is declared with AUTHID CURRENT_USER, meaning its stored procedures execute with the privileges of the invoking user rather than the package owner, which is consistent with EBS workflow-enabled utility packages that must respect invoker security for downstream DML against APPS synonyms.

The name suffix "ORU" denotes Order Review and Update processing. The package encapsulates the orchestration logic that drives an ORU workflow process — initialization of the process instance, status transitions, and the relaunch of Failed Activity Streams (FAS) when a work item must be resubmitted. It is designed to be called from Oracle Workflow activity functions, where each procedure returns a result string (RESULTOUT) consumed by the workflow engine to determine the next node.

Key Procedures and Functions

The package exposes three documented procedures, all following the standard Oracle Workflow activity signature pattern (itemtype, itemkey, actid, funcmode, resultout):

• INITIALIZE_ORU_PROCESS — The entry point targeted by the user's search. This procedure initializes an ORU process instance within the workflow engine. It performs the setup work required before any ORU processing activity can proceed, such as seeding runtime state, validating the item context, and returning a completion result to the workflow.
• LAUNCH_RESUBMISSION_FAS — Invoked when a failed activity stream must be relaunched. It re-drives the failed fulfillment activities associated with the current item, writing trace information to the resubmission log so the retry attempt can be audited.
• SET_ORU_STATUS — Transitions the ORU process to a specified status. This procedure is typically the terminal or intermediate activity in the ORU workflow, recording the outcome of the preceding activities against the runtime work list. The single documented worklist table, XDP_FULFILL_WORKLIST, is the natural target of this write.
• e_NullValueException is a package-level exception declaration used for nil-value validation; x_ErrMsg and x_DebugMsg are package globals that capture error and debug text for downstream logging.

Tables Accessed

Three APPS synonyms are referenced:

• XDP_FA_RESUBMISSION_LOG — records each resubmission attempt, including the item key and the reason the prior Failed Activity Stream could not complete. Written by LAUNCH_RESUBMISSION_FAS.
• XDP_FA_RUNTIME_LIST — the live list of Failed Activity Streams, read to determine which activities are still outstanding for the work item.
• XDP_FULFILL_WORKLIST — the fulfillment worklist that holds items in flight; updated by SET_ORU_STATUS when the ORU process reaches a terminal state.

Usage Notes

XDPCORE_ORU is not invoked directly by end users. Its procedures are expected to be wired as Oracle Workflow function activities: INITIALIZE_ORU_PROCESS on the start node, LAUNCH_RESUBMISSION_FAS on the retry node, and SET_ORU_STATUS on the completion node. In 12.1.1 and 12.2.2 the package sits in the standard APPS deployment, so custom code should call it via APPS.XDPCORE_ORU.procedure_name. Because the package is compiled with AUTHID CURRENT_USER, direct calls from a custom schema require the caller to hold EXECUTE on the package and appropriate privileges on the underlying XDP tables. The ETRM metadata records zero dependent packages, indicating this is a top-level orchestration utility rather than a shared library.