My Oracle Support Banner

Defaulting Generator Fails With Error PLS-00375: illegal GOTO statement; this GOTO cannot branch to label 'RETURN_VALUE' (Doc ID 2776552.1)

Last updated on JULY 07, 2021

Applies to:

Oracle Order Management - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, Transaction Payment

In order Management define new Defaulting Rule for entity Order Payments for attribute Payment Type

and Credit Card number in order to default payment type and other credit card information on Payments window .
Defaulting Generator concurrent program Fails to compile Seeded defaulting Conditions
For e.g Defaulting Generator Log file shows below error
Create defaulting handler for attribute: FREIGHT_TERMS_CODE
Call AD_DDL to create SPEC of package ONT_D1_FREIGHT_TERMS_CODE
Call AD_DDL to create BODY of package ONT_D1_FREIGHT_TERMS_CODE
ERROR in creating PACKAGE BODY :ONT_D1_FREIGHT_TERMS_CODE
LINE :71 PLS-00703: multiple instances of named argument in list
LINE :71 PL/SQL: Statement ignored
LINE :68 PLS-00375: illegal GOTO statement; this GOTO cannot branch to label 'RETURN_VALUE'
LINE :31 PL/SQL: Statement ignored
Error :User-Defined Exception
Error in creating entity def hdlr User-Defined Exception

When this seeded condition is disabled and run defaulting generator ,it fails for some other attribute with same error as above.
The user defined conditions work fine for the same attribute.
Due to this error unable to open sales order form below error occurs

ERROR
-----------------------
ORA-06508: PL/SQL: could not find program unit being called in Package ONT_HEADER_Def_Hdlr Procedure Default_Record

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Order management super user
2. Setup >Rules >defaulting >Define defaulting Rule for Order Payments
3. Payment Type > Always condition >Source Type : Constant > Default Value :Credit Card
4.Save and run Defaulting Generator concurrent program for Entity Order Payments
5.Define Defaulting condition for Credit card number >first disable the seeded condition then use Always >with constant value of some valid credit card number
6.Save >Run Defaulting Generator for Entity Order Header  >error occurs

Changes

 After Defining Defaulting Rule for Entity 'Order Payments'

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.