App-po-14288 !!top!! Jun 2026

First, check the exact status of the Purchase Order or Requisition.

Over time, workflow item attributes (like DOCUMENT_TOTAL_AMOUNT or APPROVAL_STATUS ) can desync from the actual document version. When the approval process queries these stale attributes, the workflow engine throws APP-PO-14288 as a generic fail-safe.

: Ensure the Workflow Background Process is scheduled and running via the System Administrator responsibility.

Look for blocks marked with an or "Suspended" status. This will call out whether the failure relates to missing supervisors, invalid approval limits, or syntax exceptions. Database Validation (For DBAs and Technical Analysts) app-po-14288

: Navigate to Administer Concurrent Managers and verify that the PO Document Approval Manager is active.

Is this happening on a or a Purchase Requisition ?

To help isolate your specific instance of this error, could you tell me whether you are seeing this on a or a Requisition ? Additionally, sharing your current PO: Workflow Processing Mode profile setting will help pinpoint the exact system fix. AI responses may include mistakes. Learn more Share public link First, check the exact status of the Purchase

In the world of enterprise resource planning (ERP), supply chain management, and software asset management, alphanumeric codes like serve as critical identifiers. Although specific references to "APP-PO-14288" are rare in public documentation, this article provides a detailed framework for understanding, validating, and troubleshooting such codes.

When a document (like a PO) is submitted for approval, Oracle Workflow takes over, directing the document through the approval hierarchy. If the workflow breaks down—due to system issues, incorrect setup, or missing data—the document remains "In Process," but the action history becomes unviewable.

I've been assigned/appointed to investigate and resolve the issue identified as "app-po-14288". This issue seems to be related to [briefly mention the area of the application or system it pertains to, e.g., "the login functionality"]. : Ensure the Workflow Background Process is scheduled

Oracle EBS requires clear instructions on how to route documents. This error regularly occurs if the is missing its designated Approval Transaction Type (e.g., PURCHASE_REQ for standard requisitions or INTERNAL_REQ for internal requests). If you route routing rules through the Approval Management Engine (AME) , a missing or broken transaction configuration in AME will yield the same result. 3. Stalled Workflow Background Processes

: The document is stuck "In Process" due to a breakdown after submission but before the history update Manager Inactivity PO Document Approval Manager is not running or has failed Troubleshooting Guide 1. Check the Document Approval Manager