App-po-14288 [upd] Jun 2026

If you encounter APP-PO-14288, follow this rigorous diagnostic workflow. It is designed for Oracle EBS functional users, system administrators, and support analysts.

For detailed troubleshooting, consulting the is recommended to find specific solutions for stuck documents.

Demystifying APP-PO-14288: Troubleshooting Stuck Procurement Workflows in Oracle EBS

Automate this via PL/SQL stored procedure on insertion to the AP_SUPPLIERS table. app-po-14288

Have you encountered a unique cause for APP-PO-14288? Share your experience in the comments or contact your Oracle user group for peer support.

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"].

Update the employee's approval limits or the position hierarchy in HR. I've been assigned/appointed to investigate and resolve the

This suggests that the requisition or order lacks essential information required for it to be valid in the system, such as a default buyer, a valid list price for an item, or an approved supplier list (ASL) assignment.

This is an extremely common root cause, especially in newly configured or recently modified environments. The error occurs because the person creating or submitting the requisition does not have a valid position in the Human Resources (HR) module.

: Ensure that whenever new document types are added, the correct Oracle Approvals Management (AME) or standard Document Type attributes are bound correctly. If you need more help resolving this error, please tell me: in some cases

Locate the specific document type (e.g., Purchase Requisition). Ensure the Approval Transaction Type

The error most commonly appears when a user tries to view the of a Purchase Order (PO) or Requisition. It serves as a defensive wall for the system, triggered by two primary scenarios:

Disclaimer: Oracle troubleshooting often requires system administrator access and, in some cases, running scripts that should be approved by Oracle Support. If you'd like, I can:

While less common than a workflow break, it can also signify that the current user does not have the necessary security profile access to view the document. Causes of the Error