Results for “oe_credit_wf”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OE_CREDIT_WF is an Oracle Applications (APPS) schema PL/SQL package classified under the OTHER API category within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2. Its primary business function is to integrate Order Management credit-checking logic with the Oracle Workflow engine. The package encapsulates the rules that determine whether an order should be blocked, held, or released based on available credit, customer credit exposure, and configured credit rules. Rather than acting as a standalone credit engine, OE_CREDIT_WF functions as the workflow-facing component that evaluates credit conditions and manipulates order holds programmatically, ensuring that the Order Management credit-checking process can be orchestrated as a workflow activity with proper state transitions and notifications.

Key Procedures and Functions

The package exposes nine documented procedures and functions. Each is listed below with its purpose:

• OE_CHECK_AVAILABLE_CREDIT — Evaluates whether the order or customer has sufficient available credit to proceed, forming the core credit validation routine.
• OE_CHECK_FOR_HOLDS — Inspects existing hold conditions applicable to the order, determining whether a credit hold should be applied.
• OE_APPLY_CREDIT_HOLD — Applies a credit hold to the order when credit validation fails or rules dictate a block.
• OE_RELEASE_CREDIT_HOLD — Releases an existing credit hold, allowing the order to proceed through fulfillment.
• OE_WAIT_HOLD_NTF — Handles the workflow wait and notification logic associated with hold processing, suspending or resuming the workflow based on hold status.
• CREDIT_BLOCK — Determines and enforces the credit block condition, centralizing the decision logic for blocking an order.
• GETHEADERID — Retrieves the order header identifier, typically used to resolve context within workflow activities.
• CHECKMANUALRELEASE — Determines whether a hold may be manually released, supporting user-driven release workflows.
• WHICHREDITRULE — Identifies which credit rule applies to the current order context, driving rule-based credit decisions.

Parameter lists are not documented in the available metadata and should be validated against the package specification before direct invocation.

Tables Accessed

OE_CREDIT_WF reads and writes a focused set of Order Management and Workflow tables, referenced through APPS synonyms:

• OE_ORDER_HEADERS, OE_ORDER_LINES, OE_ORDER_LINES_ALL — Provide order context; holds and credit decisions are anchored to specific headers and lines.
• OE_ORDER_HOLDS, OE_HOLD_SOURCES, OE_HOLD_SOURCES_ALL, OE_HOLD_RELEASES — Store the applied holds, their sources, and release history resulting from credit decisions.
• WF_ACTIVITY_TRANSITIONS, WF_ITEM_ACTIVITY_STATUSES, WF_PROCESS_ACTIVITIES — Manage workflow state, activity transitions, and status tracking for the credit-checking workflow process.

Usage Notes

OE_CREDIT_WF is typically invoked indirectly through the Oracle Workflow engine during Order Management credit checking, rather than called directly by end users. It is referenced by zero other documented packages, indicating it operates primarily as a workflow-invoked component. In practice, it is triggered by the seeded Order Management credit-checking workflow process and may be surfaced through Order Management forms when users apply or release credit holds, or through concurrent programs processing order holds. Custom code should exercise caution: because parameter signatures are not documented in the ETRM metadata, developers must reference the package specification before invoking any procedure directly. The package is marked VALID in the APPS schema, confirming it is an active, supported component of the Order Management credit infrastructure in both 12.1.1 and 12.2.2.