Document Manager Error Number 3 and Unknown Error When Approving PO or PR-1310935.1

摘自：文档 1310935.1 (oracle.com)

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

Document Manager Error Number 3 and Unknown Error When Approving Purchase Orders or Requisitions (文档 ID 1310935.1)

In this Document

Symptoms

Cause

Solution

1. Context issue

2. Sequence reached max value (Release 11.5.x)

3. Terms and conditions file exceeds 32KB size limitation (Release 11.5.x)

4. Custom data group (Release 11.5.x)

5. Incorrect RAC configuration (Release 11.5.x)

6. Logging

References

---

Applies to:

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

Symptoms

Listing of Document Manager Error Number 3 Issues and Troubleshooting Tips > 1310935.1

Requisitions or purchase orders fail during approval with document manager error number 3, causing documents to get stuck in an in process or pre-approved status. These are examples of some of the errors in the workflow:

Failed activity: Approve The PO (APPROVE_PO)
Error Stack: Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.APPROVE_DOC,
POAPPRV, 133890-113857, 196532, RUN)
Error Message: User-Defined Exception

Failed activity: Approve The Requisition (APPROVE_REQUISITION)
Error Stack: Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.APPROVE_DOC,
REQAPPRV, 133890-113857, 196532, RUN)
Error Message: User-Defined Exception

Failed activity: Does Approver Have Authority? (VERIFY_APPROVER_AUTHORITY)
Error Stack: Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.VERIFY_AUTHORITY,
POAPPRV, 133890-113857, 196532, RUN)
Error Message: User-Defined Exception

Failed activity: Forward PO With Status "In-Process" (FORWARD_DOC_INPROCESS)
Error Stack: Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.FORWARD_DOC_INPROCESS,
REQAPPRV, 133890-113857, 196532, RUN)
Error Message: User-Defined Exception

Failed activity: Open document state (OPEN_DOCUMENT_STATE)
Error Stack: Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.OPEN_DOC_STATE, POAPPRV, 61-800,204955, RUN)
Error Message: User-Defined Exception

Failed activity: Build Default Approval List (BUILD_DEFAULT_APPROVAL_LIST)
Error Stack:Wf_Engine_Util.Function_Call
(PO_APPROVAL_LIST_WF1S.BUILD_DEFAULT_APPROVAL_LIST,
REQAPPRV, 24164-182234, 166001, RUN)
Error Message: User-Defined Exception

The sysadmin error workflow attribute does not display additional error messages. Run this query to confirm that the value is null:
 

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,30) value
from wf_item_attribute_values wiav,
wf_item_attributes wia
where wiav.item_type = '&1'
and wiav.item_key = '&2'
and wia.item_type = wiav.item_type
and wia.name = wiav.name
and wiav.name = 'SYSADMIN_ERROR_MSG'
and wia.type <> 'EVENT';

Cause

Multiple

Solution

1. Context issue

Cause:
The responder workflow attributes are incorrectly set, causing the workflow to fail when identifying the approver. In order to check if responder attributes were incorrectly set to -1 or 0 for a specific workflow item type and item key, run this query:

 

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,15) value
from wf_item_attribute_values wiav,
wf_item_attributes wia
where wiav.item_type = '&1'
and wiav.item_key = '&2'
and wia.item_type = wiav.item_type
and wia.name = wiav.name
and wiav.name in ('RESPONDER_APPL_ID', 'RESPONDER_RESP_ID')
and wia.type <> 'EVENT';

The result will display any of these two combinations:

     RESPONDER_APPL_ID/Responder Application ID...............-1
     RESPONDER_RESP_ID/Responder Responsibility ID............-1
or
     RESPONDER_APPL_ID/Responder Application ID...............0
     RESPONDER_RESP_ID/Responder Responsibility ID............20420

Fix:
For release 11.5.10, apply patch: 8339900 and patch: 5389914 to upgrade files to these versions or higher:

POXWPA1B.pls 115.206.11510.42
POXWPA4B.pls 115.50.11510.8
POXWPA5B.pls 115.7.11510.12
POXWPA6B.pls 115.68.11510.12
POXWPA7B.pls 115.38.11510.13
poxwfpoa.wft 115.127.11510.16
poxwfrqa.wft 115.80.11510.4


Use this query to confirm the package versions:
 

select text
from dba_source
where line = 2
and name in ('PO_REQAPPROVAL_INIT1','PO_REQAPPROVAL_ACTION'
, 'PO_REQAPPROVAL_LAUNCH','PO_WF_REQ_NOTIFICATION'
, 'PO_WF_PO_NOTIFICATION');

If using a custom workflow, follow instructions from Note 763086.1 if the problem is not resolved.
 

Note: After application of patch 8339900, whenever the notifications are approved from the default worklist/full list or homepage, they will move to DEFERRED status. Therefore, the Workflow Background Process will need to be run to approve these notifications. Reference Note 967325.1 for details.

For release 12, apply patch: 9362974 to upgrade files to these versions or higher:

Release 12.0 : poxwfpoa.wft - 120.20.12000000.3
Release 12.1:

POXAPL1B.pls 120.12.12010000.9  
POXWAL1B.pls 120.3.12010000.3

 

2. Sequence reached max value (Release 11.5.x)

Cause: Sequence FND_TRN_REQUEST_ID_S.NEXTVAL needed for the concurrent manager activity reached the max value causing the error.

Fix: Review the solution in Note 1225135.1 to verify if this is the cause and find steps to recreate the sequence.
 

3. Terms and conditions file exceeds 32KB size limitation (Release 11.5.x)

Cause: Purchase Orders are only failing when appending terms and conditions file to the PO email to Supplier and the file exceeded the 32k size limitation.

Fix: Review solution in Note 1126684.1 to find suggestions to avoid the error when attaching the terms and conditions file.
 

4. Custom data group (Release 11.5.x)

Cause: Responsibilities used to create and approve PO's had a different data group than the data group assigned to the PO Document Approval Manager.

Fix: Review solution in Note 365792.1 to tie the data group to the PO Document Approval Manager to prevent the error.
 

5. Incorrect RAC configuration (Release 11.5.x)

Cause: The Transaction Manager is not active on each instance for all RAC nodes, in the cluster which caused the error on Approval.

Fix: Review solution in Note 309578.1 with recommendations to fix the RAC setup.
 

6. Logging

If the problem is not resolved with above solutions, please log a service request with My Oracle Support and provide the following:

a. Provide the debug and trace as documented in Note 409155.1 ‘How to Capture Debug / Log / Trace Files During the Purchase Order / Requisition Approval Process?’

b. Provide the Purchasing Approval Diagnostic on one of the documents stuck in process:

From the responsibility "Oracle Diagnostics Tool" click on the hyperlink next to Purchasing.
Choose the + next to 'Data Collectors'.
Choose the hyperlink to PO Approval.
In the 'Responsibility ID' field from the list of values choose the responsibility name used for Purchasing.
Under Document Type choose the correct document type from the list of values.
In the number field enter the document number.
Then choose the Run Test button.

c. Zip all the files together and upload the data collection to the Service Request
 

Another possible solution for such errors and confirmed by several customer is : rebooting the system.

References

NOTE:1225135.1 - Document Manager Failed With Error Number 3 At Open Document State for all Requisitions and Purchase Orders (any type)
NOTE:309578.1 - 11.5.10 - Document Approval Manager Error #3 in OPEN_DOC_STATE for All Documents Under RAC Instance
NOTE:1126684.1 - Document Manager Failed With Error Number 3 at OPEN_DOCUMENT_STATE When Terms and Conditions file Exceeded 32KB Size Limitation
NOTE:462695.1 - Troubleshooting Guide - Document Manager Error Failed With Error Number 3 (DOC_MGR_ERROR) for Purchasing Workflows
NOTE:763086.1 - Even After Applying Patch To Fix Context Issue Requisitions and Purchase Orders Continue To Fail With Document Manager Error Number 3
NOTE:967325.1 - Intermittently Document Manager Failed With Error Number 3 While Attempting To Approve Purchase Orders And Requisitions
NOTE:365792.1 - Document Manager Error 3 due to Custom Data Group Setups in Purchase Order or Requisition Approval Processes
NOTE:409155.1 - How to Capture Debug Files During the Purchase Order / Requisition Approval Process?