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:
| Workflow | Internal Activity Name | Display Activity Name | Package |
|---|---|---|---|
| POAPPRV | APPROVE_AND_FORWARD_THE_PO | Approve And Forward The PO | PO_REQAPPROVAL_ACTION.APPROVE_AND_FORWARD_DOC |
| POAPPRV | APPROVE_PO | Approve The PO | PO_REQAPPROVAL_ACTION.APPROVE_DOC |
| POAPPRV | FORWARD_PO_INPROCESS | Forward PO With Status "In-Process" | PO_REQAPPROVAL_ACTION.FORWARD_DOC_INPROCESS |
| POAPPRV | FORWARD_PO_PREAPPROVED | Forward PO With Status "Pre-Approved" | PO_REQAPPROVAL_ACTION.FORWARD_DOC_PREAPPROVED |
| POAPPRV | OPEN_DOCUMENT_STATE | Open Document State | PO_REQAPPROVAL_ACTION.OPEN_DOC_STATE |
| POAPPRV | REJECT_PO | Reject The PO | PO_REQAPPROVAL_ACTION.REJECT_DOC |
| REQAPPRV | APPROVE_AND_FORWARD_THE_REQ | Approve And Forward The Req | PO_REQAPPROVAL_ACTION.APPROVE_AND_FORWARD_DOC |
| REQAPPRV | APPROVE_REQUISITION | Approve The Requisition | PO_REQAPPROVAL_ACTION.APPROVE_DOC |
| REQAPPRV | FORWARD_REQ_PREAPPROVED | Forward Requisition With Status "Pre-Approved" | PO_REQAPPROVAL_ACTION.FORWARD_DOC_PREAPPROVED |
| REQAPPRV | FORWARD_REQUISITION_INPROCESS | Forward Requisition With Status "In-Process" | PO_REQAPPROVAL_ACTION.FORWARD_DOC_INPROCESS |
| REQAPPRV | REJECT_REQUISITION | Reject The Requisition | PO_REQAPPROVAL_ACTION.REJECT_DOC |
| REQAPPRV/POAPPRV | RESERVE_DOCUMENT | Reserve Document | PO_REQAPPROVAL_ACTION.RESERVE_DOC |
| REQAPPRV/POAPPRV | SUBMISSION_CHECK | Is Document Complete? | PO_REQAPPROVAL_ACTION.DOC_COMPLETE_CHECK |
| REQAPPRV/POAPPRV | VERIFY_APPROVER_AUTHORITY | Does 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/Package | Comprenhensive list of known issues |
|---|---|---|
| Null (sysadmin error message is null) | Error might occur in any package that calls the document manager | Note 1310935.1 |
| POXDM-210: Subroutine poxdmaction() returned erro POACA-870: Subroutine poacasetup() returned error POACA-790: ORA-01403: no data found | VERIFY_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_LIST | Note 782911.1 |
| POXDM-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 found | OPEN_DOC_STATE (Open document state) PO_REQAPPROVAL_ACTION.OPEN_DOC_STATE | Note 1252697.1 |
| POXDM-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# 3 | OPEN_DOC_STATE (Open document state) PO_REQAPPROVAL_ACTION.OPEN_DOC_STATE | Note 1298629.1 |
| POXDM-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 found | OPEN_DOC_STATE (Open document state) PO_REQAPPROVAL_ACTION.OPEN_DOC_STATE | Note 316450.1 |
| POXDM-270: Subroutine poxdmact ion() returned error PODUS-090: Subroutine podus auths() returned error PODUS-270: Unknown code: PODUS-220: ORA-1403: no data found | APPROVE_DOC (Approve the PO) PO_REQAPPROVAL_ACTION.APPROVE_DOC | Note 754953.1 |
| POXDM-280: Subroutine poxdmaction() returned erro RVSRQ-025: Subroutine rvspoa_approve_po() returne RVSPO-000: ORA-01403: no data found | APPROVE_DOC (Approve the PO) PO_REQAPPROVAL_ACTION.APPROVE_DOC | Note 1318724.1 |
| POXDM-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 defined | APPROVE_DOC (Approve the PO) PO_REQAPPROVAL_ACTION.APPROVE_DOC | Note 374099.1 |
Most common issues for Release 12 and 12.1
| Message name (sysadmin error message) | Workflow activity/Package | Comprenhensive list of known issues |
|---|---|---|
| Null (sysadmin error message is null) | Error might occur in any package that calls the document manager | Note 1310935.1 |
| 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. | APPROVE_DOC (Approve the PO) APPROVE_REQ (Approve the Requisition) PO_REQAPPROVAL_ACTION.APPROVE_DOC | Note 1304639.1 |
| po.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 call | REJECT_DOC (Reject The PO) PO_REQAPPROVAL_ACTION.REJECT_DOC | Note 1116134.1 |
| po.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 call | VERIFY_APPROVER_AUTHORITY (Does Approver Have Authority?) PO_REQAPPROVAL_ACTION.VERIFY_AUTHORITY | Note 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.
'Approver Can Modify' option on Document Types form
Please check this option from Document Types form, in some cases it was reported that unchecking it , it solved the error:
FORWARD_PO_INPROCESS (Forward PO With Status "In-Process") #EXCEPTION 1 User-Defined Exception Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.FORWARD_DOC_INPROCESS, POAPPRV, 2852072-815193, 382782, RUN)
WFStat: Item Attribute Values
SYSADMIN_ERROR_MSG VARCHAR2 po.plsql.PO_DOCUMENT_ACTION_PVT.do_action:16:failed to lock document after 1000 tries
References
NOTE:1304639.1 - Document Manager Failed With Error Number 3 and "PO_DOCUMENT_ACTION_AUTH.approve:60:po_req_supply returned false....110:unexpected error in action call" Causing Purchase Orders or Requisitions to Get Stuck in Pre-Approved or in Process
NOTE:1252697.1 - Document Manager Failed With Error Number 3 and POXDM-250 POCUP-080 POCUP-395 RVSRQ-055 RVSPO-163 ORA-01403 Causing Purchase Orders to Get Stuck in Process
NOTE:1318724.1 - Document Manager Failed With Error Number 3 and POXDM-280 RVSRQ-025 RVSPO-000: ORA-01403
NOTE:374099.1 - Document Manager Failed With Error Number 3 and POXDM-280 RVSRQ-125 RVTUQ-83: Subroutine UomConvert Error
NOTE:1298629.1 - Document Manager Failed With Error Number 3 and POXDM-250: POCUP-080: POCUP-395: RVSRQ-055: RVSPO-161: ORA-08102 Causing Purchase Orders to Get Stuck in Process or Pre-Approved
NOTE:316450.1 - Document Manager Failed With Error Number 3 and POXDM-250: POCUP-080: POCUP-395: RVSUT-075:ORA-01403 Causing Purchase Orders to Get Stuck in Process or Pre-Approved
NOTE:754953.1 - Document Manager Failed With Error Number 3 and POXDM-270: PODUS-090: PODUS-270: PODUS-220: ORA-1403 Causing Purchase Orders to Get Stuck in Pre-Approved or In Process
NOTE:1310935.1 - Document Manager Error Number 3 and Unknown Error When Approving Purchase Orders or Requisitions
5万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
