My Oracle Support Banner

12.1.3 Workflow Builder Client Error Occurs Saving Purchase Order Approval (POAPPRV) Workflow After Opening From the Database: 354: 'SAVE' Validation Failed For Activity 'POAPPRV/PO_AME_APPRV_TOP' (Doc ID 1522717.1)

Last updated on JANUARY 09, 2023

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On 12.1.3 version when attempting to open the Purchase Order (PO) Approval workflow from the database (internal name = POAPPRV) using the Workflow Builder Client software the following error occurs.

NOTE:   If the PO Approval Workflow file from the file system (the one located in $PO_TOP/patch/115/import/US/poxwfpoa.wft) is opened, the error does not happen.

ERROR
  382: Design Validation generated 1 warning(s). You may save invalid definitions but they should not be used in running process.
  354: 'SAVE' validation failed for activity 'POAPPRV/AME_ROUTING'.
  362: Validation failed for child activity 'POAPPRV/GET_NEXT_APPROVER_AME'.
  360: '&OPERATION' validation failed for 'NO_NEXT_APPROVER_ESIGNER' transition to activity 'WFSTD/END'.
  350: Invalid transition result code 'NO_NEXT_APPROVER_ESIGNER'. Transition codes must be valid lookup codes
          for the originating activity's result type.

Or 

ERROR

382: Design Validation generated 2 warning(s). You may save invalid definitions but they should not be used in running process.
354: 'SAVE' validation failed for activity 'POAPPRV/PO_AME_APPRV_TOP'.
362: Validation failed for child activity 'POAPPRV/AME_ROUTING'.
358: Activity result code 'TIMEDOUT' has no transition defined for it. All valid result codes must be modeled with specific transitions or a transition.
354: 'SAVE' validation failed for activity 'POAPPRV/AME_ROUTING'.
362: Validation failed for child activity 'WFSTD/END'.
356: Invalid end result code 'ESIGNER_APPROVE'. End activity result codes must be one of the valid codes for the parent process' result type.


STEPS
The issue can be reproduced at will with the following steps:
   1. Open WorkFlow Builder Client software
   2. Connect to the database and select the PO Approval item type
   3. Try to save, get errors, it does let the user continue with the Save

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
Cause
Solution


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