If you want, paste a redacted server log (timestamp, correlation ID, stack trace) or the sanitized request payload and I’ll analyze it and propose a targeted fix.
Scenario 1: Workflow Stuck If the document is stuck in the workflow:
Scenario 2: Data Corruption (Missing/Invalid Data) app-po-14160 document action not completed successfully
Scenario 3: Custom Code Conflict If recent customizations were deployed to the PO forms:
Before applying a fix, perform the following steps to isolate the issue: If you want, paste a redacted server log
Step A: Check Backend Logs
If the application allows, have a System Administrator check the PO Debug/Trace logs. Look for the specific SQL statement failing immediately before error APP-PO-14160 is raised. Common SQL errors include ORA-01403 (No data found) or ORA-00054 (Resource busy).
Step B: Verify Workflow Status Run the following query to check the workflow status of the document: Scenario 1: Workflow Stuck If the document is
SELECT item_key, activity_status, activity_result
FROM wf_item_activity_statuses_v
WHERE item_key = '<DOCUMENT_ID>'
ORDER BY begin_date DESC;
Look for activities with a status of 'ERROR'.
Step C: Check for Locks Ask the DBA to check for database locks on the PO headers or lines tables while the user is attempting the action.