App-po-14288 !!top!! -

App-po-14288 !!top!! -

APP-PO-14288 is a common error code encountered in Oracle E-Business Suite (EBS) Purchasing. It typically appears when a user attempts to "View Action History" for a Purchase Order (PO) or Requisition and the system cannot retrieve the requested data.

The standard error message text is: "This document is either incomplete or you do not have access to it or there is no action history". Common Causes

Workflow Breakdown: If a document has a status of "In Process" but shows this error, it usually indicates a workflow failure occurred after the document was submitted but before the action history could be updated.

Missing Action History: Newly imported documents or those that have not yet undergone any approval actions may naturally lack an action history record.

Insufficient Access: The user may not have the necessary security permissions or responsibilities to view the specific document's history.

Background Process Issues: The "Workflow Background Process" or "PO Document Approval Manager" may not be running correctly, causing documents to get stuck in a "Pre-Approved" or "In Process" state. Troubleshooting Steps app-po-14288

To resolve this issue, Oracle users often follow these steps:

Check Document Status: Verify if the document is stuck in "In Process" or "Pre-Approved".

Restart Services: Ensure the PO Document Approval Manager is active and restart it if necessary.

Run Background Processes: Verify that the Workflow Background Process is scheduled and running correctly.

Review Security: Confirm the user has the correct functional access for the Operating Unit or document type. APP-PO-14288 is a common error code encountered in

Use Diagnostic Scripts: Run standard Oracle diagnostic scripts (e.g., poreqer.sql or po_approval_error.sql) to identify where the workflow stalled.

Detailed troubleshooting guides can be found on community platforms like Spiceworks or through documentation on Scribd and Oracle Community. Unable to approve Requisitions - Spiceworks Community


Step 6: Review Supplier Site Assignments

When to Escalate to Oracle Support

If you have exhausted the troubleshooting steps above and APP-PO-14288 persists, request an Oracle Support SR. Provide the following to fast-track resolution:

  1. Screenshot of the exact error dialog box.
  2. Workflow Status Monitor output (XML or HTML).
  3. Debug log from FND_LOG with level set to STATEMENT for the PO module.
  4. The PO_HEADER_ID of the offending document.
  5. A complete list of recent changes (e.g., new jobs, responsibilities, or patches).

Oracle’s development team has a known bug fix for certain releases regarding APP-PO-14288 when using multi-org access control (MOAC). Reference Bug 21345678 (hypothetical example) if your system is on R12.1.3.

Expected Result:

[Describe what was expected to happen]

2. Run the "Workflow Validity Report" Weekly

Oracle provides a concurrent program: Workflow Validity Report (under Purchasing > Reports > Workflow). Run this on all pending documents. It identifies documents that will fail approval before a user even tries.

Writing Tips

2. Decoding the Structure: APP-PO-14288

Let's dissect the identifier:

Thus, APP-PO-14288 could be interpreted as: Application-associated Purchase Order #14288.