My Oracle Support Banner

In Oracle Contract Lifecycle Management For PARS, Notification Generation To Approvers Through Parallel Approval Subprocess Failed Due To Exception In PO Output For Communication Program (Doc ID 2745101.1)

Last updated on JANUARY 19, 2021

Applies to:

Oracle Contract Lifecycle Management for Public Sector - Version 12.2.7 and later
Information in this document applies to any platform.

Symptoms

In Oracle Contract Lifecycle Management for PARs, Notification generation to approvers through Parallel approval subprocess failed due to exception in PO Output for Communication program.


The following 4 issues are identified and resolved with this patch:

 1. When PAR is submitted for approval without any approvers and if there is an exception/error in PO Output for Communication program then the following happens in poappame.wft.
 "PO CLM AME Top Approval Process" --> "Post Routing" --> if PAR then "Post Award Request Post Approval Process" --> "Wait for Concurrent Program" (which is POXPOPDF) --> If this errors/warning then "Notify PDF error to Buyer" in Post Process  --> Return back to main approval process and END in normal state, meaning "Approve" the PAR.

 But when a PAR is submitted for approval with any approvers and if there is an exception/error in PO Output for Communication program of the "Parallel approval subprocess"(to send notification to Approver) then the following happens in poappame.wft.
 "PO CLM AME Top Approval Process" --> "Routing" --> "AME Approval Routing" --> "Parallel approval subprocess" --> "Wait  for Concurrent Program" (which is POXPOPDF) --> If this errors/warning then Return to "AME Approval Routing", which sends "Notify PDF error to Buyer" and then ends with ERROR.
 The behavior is different in Child workflow notification flow.

 2. In generateDoc method of PoGenCLMDoc.java, the java object conPgOS is used again without resetting/erasing the previous data.

 3. There is not proper debug messages in generateDoc method of PoGenCLMDoc.java to track the progress/exception in PDF generation.

 4. Several variable 'ACCOUNT_ID' is missing errors when PO Output for Communication program is executed to generate SGD or PAR PDF(using PO_MOD.xml).

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.