My Oracle Support Banner

REP-1401:'Beforereport': Fatal PL/SQL error occured. (Doc ID 296374.1)

Last updated on OCTOBER 17, 2023

Applies to:

Oracle Reports Developer - Version 12.2.1.4.0 and later
Oracle Forms for OCI - Version 12.2.1.4.0 and later
Information in this document applies to any platform.
- Oracle Reports: Oracle Internet Developer Suite - Version: 9i, 10g
- Oracle Application Server 9i, 10g

Symptoms:
---------
Problems with PL/SQL Code in Report Triggers, random PL/SQL Error: REP-1401:'
Beforereport': Fatal PL/SQL error occured or no value for parameter available

Cause:
--------
There is a Before Report trigger with PL/SQL in your application that
should influence the query and/or includes DML or DDL.

Fix:
-----
Use an After Parameter Form Trigger.

From this trigger, you can access parameters and check their values.
This trigger can also be used to change parameter values or, if an
error occurs, return to the Runtime Parameter Form. Consistency is
guaranteed if you do DML and DDL or influence the query in (or before)
the After Parameter Form trigger. Be cautious in these cases using a
Before Report trigger because queries are parsed BEFORE the Before
Report trigger will fire. By checking these circumstances carefully
you can avoid problems with parameter values or PL/SQL.
Nevertheless the data is fetched and the Report is executed after the
Before Report trigger fires.

Reference:
----------
<Note 273777.1> Reports Order of execution, with trigger order,
cautions and trigger restrictions






Symptoms

 

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!

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