Troubleshooting Guide

Troubleshooting Guide - Document Manager Error Failed With Error Number 3 (DOC_MGR_ERROR) for Purchasing Workflows (文档 ID 462695.1)转到底部

---

In this Document

Purpose Troubleshooting Steps Introduction Affected workflow activities How to find additional error messages Most common issues for Release 11.5.10 Most common issues for Release 12 and 12.1 How to retry the workflow for documents Stuck in Pre-Approved or In Process Status References

---

APPLIES TO:

Oracle Purchasing - Version 11.5.1 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
POXCON

PURPOSE

This note is intended to facilitate troubleshooting Document Manager Number (Doc Mgr Error) 3 issues in releases 11.5 through 12.1.

TROUBLESHOOTING STEPS

Introduction

Document Manager failures are classified as Doc Mgr Error 1 (Document Approval Manager timeout) or Doc Mgr Error 2 (Document Approval Manager Not Active). Any other document manager exception is considered a Doc Mgr Error 3 and the cause can be related to setup issues or a code fix. 

The Doc Mgr Error 3 is a generic message but for most cases it is possible to get more detailed error messages, which helps to identify the root cause of the problem.

Affected workflow activities

Before Release 12, Purchase Order (PO)/Requisition approval workflow used to initiate a call to the 'PO Document Approval Manager' using fnd_transaction.sync() API. In Release 12, fnd_transaction call has been replaced with direct calls to pl/sql code. The document manager errors are exceptions that occur during the call or execution of the approval manager code and is isolated to certain workflow activities, as shown here below:

WorkflowInternal Activity NameDisplay Activity NamePackagePOAPPRVAPPROVE_AND_FORWARD_THE_POApprove And Forward The POPO_REQAPPROVAL_ACTION.APPROVE_AND_FORWARD_DOCPOAPPRVAPPROVE_POApprove The POPO_REQAPPROVAL_ACTION.APPROVE_DOCPOAPPRVFORWARD_PO_INPROCESSForward PO With Status "In-Process"PO_REQAPPROVAL_ACTION.FORWARD_DOC_INPROCESSPOAPPRVFORWARD_PO_PREAPPROVEDForward PO With Status "Pre-Approved"PO_REQAPPROVAL_ACTION.FORWARD_DOC_PREAPPROVEDPOAPPRVOPEN_DOCUMENT_STATEOpen Document StatePO_REQAPPROVAL_ACTION.OPEN_DOC_STATEPOAPPRVREJECT_POReject The POPO_REQAPPROVAL_ACTION.REJECT_DOCREQAPPRVAPPROVE_AND_FORWARD_THE_REQApprove And Forward The ReqPO_REQAPPROVAL_ACTION.APPROVE_AND_FORWARD_DOCREQAPPRVAPPROVE_REQUISITIONApprove The RequisitionPO_REQAPPROVAL_ACTION.APPROVE_DOCREQAPPRVFORWARD_REQ_PREAPPROVEDForward Requisition With Status "Pre-Approved"PO_REQAPPROVAL_ACTION.FORWARD_DOC_PREAPPROVEDREQAPPRVFORWARD_REQUISITION_INPROCESSForward Requisition With Status "In-Process"PO_REQAPPROVAL_ACTION.FORWARD_DOC_INPROCESSREQAPPRVREJECT_REQUISITIONReject The RequisitionPO_REQAPPROVAL_ACTION.REJECT_DOCREQAPPRV/POAPPRVRESERVE_DOCUMENTReserve DocumentPO_REQAPPROVAL_ACTION.RESERVE_DOCREQAPPRV/POAPPRVSUBMISSION_CHECKIs Document Complete?PO_REQAPPROVAL_ACTION.DOC_COMPLETE_CHECKREQAPPRV/POAPPRVVERIFY_APPROVER_AUTHORITYDoes Approver Have Authority?PO_REQAPPROVAL_ACTION.VERIFY_AUTHORITY

How to find additional error messages

When the purchase order or requisition approval workflow fails with a Doc Mgr Error 3 exception, the POERROR workflow will send a notification to the preparer or owner of the document. This notification will display additional error messages. These messages come from the SYSADMIN_ERROR_MSG workflow attribute that is populated by the purchase order or requisition approval workflow during its execution.

1. In order to see the errors via the application, log in as the preparer or document owner and go to the worklist to review the 'Document manager failed' notification. This is an example of one notification sent to the preparer after a document manager exception, with the additional error message highlighted.

      

If needed, use this script to identify the owner of the document manager notification for a specific document:

     select recipient_role, subject from wf_notifications
     where status = 'OPEN'
     and message_type = 'POERROR'
     and message_name = 'DOC_MANAGER_FAILED'
     and subject like '%&document_number%';


2. In order to see the errors via SQL*Plus, follow these instructions to obtain the value of the SYSADMIN_ERROR_MSG error message for a specific workflow:

2.1. Identify the workflow item type and item key for the document.

Requisition:

     SQL > select hr.name, prh.segment1, prh.wf_item_type, prh.wf_item_key
     from po_requisition_headers_all prh,
     hr_all_organization_units hr
     where prh.org_id = hr.organization_id and
     prh.segment1 = '&Enter_Req_Number';

Purchase Order:

     SQL > select hr.name, poh.segment1, poh.wf_item_type, poh.wf_item_key
     from po_headers_all poh,
     hr_all_organization_units hr
     where poh.org_id = hr.organization_id and
     poh.segment1 = '&Enter_PO_Number';

Purchase Order Release:

     SQL > select hr.name, poh.segment1, por.release_num, por.wf_item_type, por.wf_item_key
     from po_headers_all poh,
     po_releases_all por,
     hr_all_organization_units hr
     where poh.org_id = hr.organization_id and
     por.org_id = poh.org_id and
     poh.po_header_id = por.po_header_id and
     poh.segment1 = '&Enter_PO_Number' and
     por.release_num = '&Enter_Release_Num';

2.2. Run this script using the values retrieved from step 2.1 to see the SYSADMIN_ERROR_MSG value:

     select wiav.name attr_name,
     substr(nvl(wiav.text_value, nvl(to_char(wiav.number_value),to_char(wiav.date_value,'DD- MON-YYYY hh24:mi:ss'))),1,300) value
     from wf_item_attribute_values wiav,
     wf_item_attributes wia
     where wiav.item_type = '&item_type'
     and wiav.item_key = '&item_key'
     and wia.item_type = wiav.item_type
     and wia.name = wiav.name
     and wiav.name = 'SYSADMIN_ERROR_MSG'
     and wia.type <> 'EVENT';

The second column will display additional error messages. For the previous example, the result is as follows:

SYSADMIN_ERROR_MSG 
po.plsql.PO_DOCUMENT_ACTION_AUTH.approve:60:po_req_supply returned false - po.plsql.PO_DOCUMENT_ACTION_PVT.do_action:110:unexpected error in action call

3. Use the error messages to find possible solutions in this next table for your application release.

Most common issues for Release 11.5.10

Message name (sysadmin error message)Workflow activity/PackageComprenhensive list of known issuesNull (sysadmin error message is null)Error might occur in any package that calls the document managerNote 1310935.1POXDM-210: Subroutine poxdmaction() returned erro
POACA-870: Subroutine poacasetup() returned error
POACA-790: ORA-01403: no data foundVERIFY_APPROVER_AUTHORITY (Does Approver Have Authority?)
PO_REQAPPROVAL_ACTION.VERIFY_AUTHORITY

BUILD_DEFAULT_APPROVAL_LIST (Build Default Approval List)
PO_APPROVAL_LIST_WF1S.BUILD_DEFAULT_APPROVAL_LISTNote 782911.1POXDM-250: Subroutine poxdmaction() returned erro
POCUP-080: Subroutine pocupsupply() returned erro
POCUP-395: Subroutine rvsrq_po_req_supply() retur
RVSRQ-055: Subroutine rvspos_create_po_ship_suppl
RVSPO-163: ORA-01403: no data foundOPEN_DOC_STATE (Open document state)
PO_REQAPPROVAL_ACTION.OPEN_DOC_STATENote 1252697.1POXDM-250: Subroutine poxdmaction() returned erro
POCUP-080: Subroutine pocupsupply() returned erro
POCUP-395: Subroutine rvsrq_po_req_supply() retur
RVSRQ-055: Subroutine rvspos_create_po_ship_suppl
RVSPO-161: ORA-08102: indexkey not found, obj# 3OPEN_DOC_STATE (Open document state)
PO_REQAPPROVAL_ACTION.OPEN_DOC_STATENote 1298629.1POXDM-250: Subroutine poxdmaction() returned erro
POCUP-080: Subroutine pocupsupply() returned erro
POCUP-395: Subroutine rvsrq_po_req_supply() retur
RVSRQ-125: Subroutine rvsutg_maintain_mtl_supply(
RVSUT-075: ORA-01403: no data foundOPEN_DOC_STATE (Open document state)
PO_REQAPPROVAL_ACTION.OPEN_DOC_STATENote 316450.1POXDM-270: Subroutine poxdmact ion() returned error
PODUS-090: Subroutine podus auths() returned error
PODUS-270: Unknown code:
PODUS-220: ORA-1403: no data foundAPPROVE_DOC (Approve the PO)
PO_REQAPPROVAL_ACTION.APPROVE_DOCNote 754953.1POXDM-280: Subroutine poxdmaction() returned erro
RVSRQ-025: Subroutine rvspoa_approve_po() returne
RVSPO-000: ORA-01403: no data foundAPPROVE_DOC (Approve the PO)
PO_REQAPPROVAL_ACTION.APPROVE_DOCNote 1318724.1POXDM-280: Subroutine poxdmaction() returned error
RVSRQ-125: Subroutine rvsutg_maintain_mtl_supply()
RVTUQ-83: Subroutine UomConvert() returned error
Interclass conversion between UOM-1 and UOM-2 is not definedAPPROVE_DOC (Approve the PO)
PO_REQAPPROVAL_ACTION.APPROVE_DOCNote 374099.1

 

Most common issues for Release 12 and 12.1

Message name (sysadmin error message)Workflow activity/PackageComprenhensive list of known issuesNull (sysadmin error message is null)Error might occur in any package that calls the document managerNote 1310935.1po.plsql.PO_DOCUMENT_ACTION_AUTH.approve:60:po_req_supply returned false - 
po.plsql.PO_DOCUMENT_ACTION_PVT.do_action:110:unexpected error in action call.
APPROVE_DOC (Approve the PO)
APPROVE_REQ (Approve the Requisition)
PO_REQAPPROVAL_ACTION.APPROVE_DOCNote 1304639.1po.plsql.PO_DOCUMENT_ACTION_AUTH.reject:210:po_req_supply returned false -
po.plsql.PO_DOCUMENT_ACTION_PVT.do_action:110:unexpected error in action callREJECT_DOC (Reject The PO)
PO_REQAPPROVAL_ACTION.REJECT_DOCNote 1116134.1
po.plsql.PO_DOCUMENT_ACTION_CLOSE.auto_update_close_status:30:100 ORA-01403: no data found
po.plsql.PO_DOCUMENT_ACTION_CLOSE.auto_close_po:120:unexpected error in updating closed status -
po.plsql.PO_DOCUMENT_ACTION_PVT.do_action:110:unexpected error in action callOPEN_DOC_STATE (Open document state)
PO_REQAPPROVAL_ACTION.OPEN_DOC_STATENote 867855.1po.plsql.DOCUMENT_ACTION_CHECK.authority_checks_setup:40:100ORA-01403: no data found - po.plsql.PO_DOCUMENT_ACTION_CHECK.authority_check:20:unexpected error in authority_checks_setup -
po.plsql.PO_DOCUMENT_ACTION_PVT.do_action:110:unexpected error in action callVERIFY_APPROVER_AUTHORITY (Does Approver Have Authority?)
PO_REQAPPROVAL_ACTION.VERIFY_AUTHORITYNote 1073703.1

 

 

How to retry the workflow for documents Stuck in Pre-Approved or In Process Status

Follow instructions in Note 312582.1 'How To Resubmit a Document For Approval When the Document is IN PROCESS Due To PO Document Approval Manager Errors' to retry affected workflows.