/ Copyright (c) Oracle Corporation 1989, 2004. All Rights Reserved.
/
/ File		:
/ Created	: 09/01/04
/ By		:
/ Language	: American
/ Character set : US7ASCII
/
/ CONTENTS:
/    Generic Base Messages for :
/  Default DESC: 6.1.0
/
/
/ NOTES:
/
/ MODIFIED:
/
/ 02000 .. 02299 Oracle Reports Generator - general error and warning mesgs
/
02000,0, "Failed in call to Oracle Reports API '%s'"
// *Cause :  A general fault has occurred between the Generator
//	     and the Oracle Reports engine.
// *Action : Contact your technical support representative.
02001,1, "Duplicate named routine %s found on the template has been overwritten"
// *Cause :  A named routine on the template used in
//	     generation was found to have the same name as a
//	     named routine defined on the module. The named
//	     routine on the module has taken precedence
//	     over the template logic.
// *Action : In order to prevent the template named routine from
//	     being overwritten, it will be necessary to remove
//	     the named routine with the same name from the
//	     module being generated.
02002,2, "Invalid data-link from across/down group of matrix "
// *Cause :  Oracle Reports does not allow a data-link for a
//	     master detail report (where the master is a
//	     matrix) to start in the cross-product group .
// *Action : Make sure the key column in the link is not in
//	     the across/down group of the matrix.
02003,1, "Datasource %s has unlinked table usages"
// *Cause :  The query contains tables that are not linked by a
//	     Where clause. This is a cartesian product which
//	     is not supported.
// *Action :
02004,1, "Invalid link on table : %s"
// *Cause :  The link on this table does not match a valid
//	     foreign key constraint.
// *Action : Check that the link is correct, and matches
//	     a foreign key constraint.
02005,8, "This module has been captured from a generated report with DOJOIN = 'Y'"
// *Cause :  The captured report has been generated with
//	     the DOJOIN preference set to 'Y'. The captured
//	     module has the same structure as the original
//	     module. However, the DOJOIN preference will
//	     be set to the default value.
// *Action : To generate from the captured module
//	     and get a report exactly like the one captured,
//	     manually set the DOJOIN preference to 'Y'.
02006,1, "The space chars in the routine named %s have been replaced with underscores"
// *Cause :  Oracle Reports does not allow space characters in
//	     program unit names.
//	     Report Generator has detected space characters
//	     in the name of a named routine in the module. These spaces
//	     have been replaced by underscores in order to
//	     produce a generatable report.
// *Action : Application logic items referencing a named
//	     routine whose name has had its spaces
//	     replaced by underscores will need updating
//	     to call the modified named routine correctly.
02007,2, "Failed to parse generated SQL statement %s"
// *Cause :  When Report Generator tried to build the query from
//	     the SQL statement that was being generated for the module,
//	     it failed to parse. This could be for a number of reasons:
//	     --- Tables referenced do not exist in the user that you are
//		 connected to
//	     --- An invalid expression has been added, for example against
//		 the Where clause on a table usage
// *Action : Since the most likely cause of this error is that the tables
//	     referred to in the SQL statement do not exist in the
//	     current user connection, then the best cause
//	     of action is to either:
//	     --- Create the tables in the user you are connecting with, for
//		 example by using the Server Generator.
//	     --- If the tables have been created in a different user,
//		 supply the connect string to this user from the Report
//		 Generator Options dialog.
//	     If the error persists, the best course of action is to cut and
//	     paste the generated statement into a SQL*Plus session to
//	     determine the exact error. You can then correct the module
//	     definition and re-generate the module.
02008,2, "Report window %s contains no valid module components and so is not valid"
// *Cause :  This error has occurred in attempting to process an
//	     Action Item for a Drill Down report.
//	     The Report module that you are attempting to generate
//	     is not valid for generation.  This is because the WINDOW
//	     in the module does not contain a valid  MODULE COMPONENT.
//	     The likey cause of this is that a window has been created
//	     with only an action inside it, or the Module Component in the
//	     window only contains an unbound item, such as a summary.
// *Action : In order to adjust this module and overcome this reason for
//	     invalidity either populate the MODULE COMPONENT
//	     property on the WINDOW with a MODULE COMPONENT
//	     that contains more than an unbound item, or remove the
//	     window from the module.
02009,1, "Unbound Item %s has been moved to the group of the bound item it references."
// *Cause :  The unbound item has been created referencing a bound item
//	     that is in a group above it. Oracle Reports does not allow
//	     a summary item based on a bound item
//	     that is not in the same group or in a group below the summary
//	     item. To create a valid report, Report Generator has moved the
//	     unbound item into the same group as that of the bound item
//	     referenced in the derivation text. To give the appearance of
//	     an unbound item referencing a bound item in the group
//	     above it, refer to the Action text for this message.
// *Action : To give the appearance of an unbound item referencing
//	     a bound item in the group above it:
//	     1. Create a second bound item based on the same
//	     column as the original bound item, but in the group containing
//	     the summary item.
//	     2. Set the Display property of the second bound item to No.
//	     3. Reference the non-displayed bound item in the summary item.
//	     The result will be a generated report in which the unbound item
//	     in the detail group appears to reference a bound item in the
//	     master group.
02010,1, "No database connection supplied for inclusion in key."
// *Cause :  A database connection to include in the generated key file has not
//	     been supplied.
// *Action : Either set the KEYCON preference to the required database
//	     connection, or modify the generated key file manually.
02011,1, "Key name '%s' already appears in key file, key left unchanged."
// *Cause :  An existing key with the same name was found in the destination
//	     key file.
// *Action : Either remove the existing key from the key file and generate again,
//	     or change the KEYNME generator preference so that the generated
//	     key has a different name.
02012,1, "Key file '%s' could not be written to - key not created"
// *Cause :  Report Generator was unable to open the key file for output.
// *Action : The file may be in use by another application, or it may have been
//	     write-protected.
//	     Make sure that:
//	     --- no other application is using the file
//	     --- the file allows write access
02013,1, "No virtual CGI directory specified, using 'cgi-bin' as default"
// *Cause :  When a report is generated for use over the Web via CGI,
//	     Report Generator looks for the path of the CGI application in the
//	     preference CGIPTH. If no path has been supplied,
//	     the default path 'cgi-bin' will be used instead.
// *Action : Set the CGIPTH preference to the CGI path.
02014,1, "No key name given - using module short name as default"
// *Cause :  When Web user authentication via a key has been chosen,
//	     Report Generator looks for a name for the key in the
//	     preference KEYNME.
// *Action : Set the KEYNME preference to the name of the key to be
//	     generated.
02015,1, "No reports server name specified - using 'report_server' as default"
// *Cause :  When drill-down reports are to be run over the Web,
//	     Report Generator looks in the REPSRV
//	     preference for the name of the Reports Server
//	     that the generated reports will be stored on.
// *Action : Set the REPSRV preference to the name of the
//	     Reports Server.
02016,1, "Cannot convert template report, %s already exists"
// *Cause :  The given RDF template cannot be converted
//	     to a TDF template because a template already
//	     exists with that name.
// *Action : Either update your preferences to use
//	     the TDF template, or delete the existing
//	     TDF template.
02017,2, "Unable to attach PL/SQL library %s to report"
// *Cause :  The generator was unable to find and attach
//	     the PL/SQL library to the report.
// *Action : Check one of the following :
//	     --- If generating a module that has a file-based library
//		 attached in a module network, check the Repository
//		 property 'Source Path' contains the name of the
//		 library including the full path.
//	     --- The destination path of the generated library is specified
//		 in the registry variable REPORT60_PATH or ORACLE_PATH.
02018,1, "Key-based links between modules not supported - reports will not be linked"
// *Cause :
// *Action :
02019,1, "Computed item cannot be used to summarise target-specific item, ignored"
// *Cause :  The derivation text of the computed item contains a reference
//	     to an unbound item of type Target Specific, which cannot be
//	     summarised.
// *Action : Alter the derivation text of the computed item.
02020,1, "Module argument has same name as item"
// *Cause :  The specified module argument has the
//	     same name as one of the items in the module. This can lead
//	     to ambiguity during design capture.
// *Action : Change the module argument name so that it is unique.
02021,1, "Master with two details will not be laid out correctly if DOJOIN=YES"
// *Cause :  When Reports Generator merges queries in a Report,
//	     it creates break groups in order to lay out each of the module
//	     components in the query. Break groups cannot be nested in
//	     the way required to produce the correct layout for a master
//	     module component with two detail module components.
// *Action : Either set the DOJOIN preference to N, or change the master-detail
//	     relationships in the module definition.
02022,1, "Filename derived from short name %s, '.' replaced by '_'"
// *Cause :
// *Action :
02023,1, "Argument format mask defaulted to '%s'"
// *Cause :  The 'Input Mask' property on the module argument is empty,
//	     and there is no format mask supplied in the DTEMSK generator
//	     preference. The Reports Generator has used the default format
//	     mask.
// *Action : Either enter an Input Mask on the argument, or set the
//	     DTEMSK generator preference to an appropriate mask.
02024,1, "Unbound item type set to server-side function"
// *Cause :  Capture identified the derivation text of the unbound item as
//	     a server-side function call.
// *Action : If the type of the unbound item is incorrect, navigate to the
//	     item and change it to the correct type.
02025,2, "Invalid group %s has no displayed items"
// *Cause :  This module contains a module component with no
//	     displayed items in it.
// *Action : Do one of the following:
//	     1. Make sure that at least one item in the module component
//	     is displayed.
//	     2. If you do not want any of the items in the module component
//	     displayed (e.g.because this module component is used simply
//	     to link to another module component), redesign the module
//	     so that all table usages are within one module component.
02030,1, "Failed to compile PL\SQL"
// *Cause :  The PL\SQL compilation failed.
// *Action : Open the generated report in Report Builder and compile it.
//	     This will allow you to
//	     determine the exact cause of the compilation failure.
//	     The most likely cause is an invalid PL\SQL unit
//	     entered under user application logic.
02032,2, "Computed item is based on '%s' which has a non numeric datatype"
// *Cause :  The datatype of the item referenced in the computed
//	     item is not valid for the function specified.
// *Action : Modify the datatype of the item referenced by
//	     the computed item or use a different item. The
//	     usual reason for this message is that a function
//	     such as SUM is used over a bound item with a
//	     datatype of CHAR.
02040,3, "Logon using %s failed. A system error will follow."
// *Cause :  The generator attempted to connect using the noted
//	     connect string but failed to establish a connection.
// *Action : Either correct the connect string or examine
//	     the system message that will follow.
02051,2, "System error: %s"
// *Cause :  No further information available.
// *Action :
02084,1, "Unable to access template report %s or registry variable REPORT60_PATH"
// *Cause :  The generator cannot access the given layout
//	     model template report. In order to generate a report
//	     the generator must be able to open the layout
//	     model template report.
// *Action : Ensure that the user generating the report
//	     can open the template layout model report,
//	     specified in the template preferences.
02092,4, "Unable to save report %s"
// *Cause :  The generated report could not be saved to the filesystem.
// *Action : Ensure that the user generating the report has
//	     write access to the filesystem.
02173,1, "Unable to layout report into given area"
// *Cause :  While trying to layout the given module, the
//	     Report Generator failed to fit the requested
//	     items into the given area as specified by
//	     the layout template (if specified). The report
//	     will still be saved, but no layout will be created.
// *Action : Since the Report Generator has attempted to reduce
//	     the font size of the items to fit the layout area, the only
//	     options remaining are the following:
//	     --- Increase the size of the layout area in the template report
//	     --- Decrease the number of displayed items
//	     --- Reduce the width of displayed items
02174,8, "%s - Edit definition"
// *Cause :
// *Action :
02175,8, "%s - View with the Live Previewer"
// *Cause :
// *Action :
02176,8, "%s - Run "
// *Cause :
// *Action :
02177,8, "%s - Convert "
// *Cause :
// *Action :
02178,2, "Journaling preference JNCOLS has invalid syntax, %s"
// *Cause :  The value for the preference JNCOLS has not been recognized.
// *Action : Consult the documentation for this preference
//	     and verify the syntax is correct
02179,2, "Journaling preference JNCOLS has invalid width for journal column %s"
// *Cause :  The displayed field specified for the journal column
//	     must be greater than zero.
// *Action : Check the displayed field width for the journal column
//	     specified in the value of preference JNCOLS.
02180,2, "Logon to validation user (%s) failed.  Using current connection."
// *Cause :  The generator attempted to connect using the noted
//	     connect string, but failed to establish a connection.
// *Action : Either correct the connect string or examine the system message
//	     that will follow.
02181,8, "Report %s"
// *Cause :
// *Action :
02182,8, "%s - View HTML report output"
// *Cause :  The command line used to auto-generate the HTM/PDF files
//	     has not executed correctly.
// *Action : To resolve the problem do one of the following:
//	     --- Check Reports Runtime has been installed correctly
//	     --- Check Reports Runtime runs on its own by double-clicking
//		the executable from the File Manager or Windows Explorer
02183,8, "%s - View PDF report output"
// *Cause :
// *Action :
02184,2, "%s has no displayed column usages or navigation action items"
// *Cause :  There must exist a module component that has at least one
//	     column usage that is marked as displayed, or a navigation
//	     action item.
// *Action : Do one of the following:
//	     --- Ensure that at least one of the column usages
//		 is marked as displayed
//	     --- Verify that there is at least one navigation action item
02185,1, "PL/SQL library %s does not exist"
// *Cause :  The PL/SQL library cannot be attached unless it exists
//	     at the specified location.
// *Action : Check that the library exists in the specified location.
//	     If a User PL/SQL library, check the Report-Level Objects
//	     preference MODLIB points to the correct location and name.
02186,1, "Unable to generate bookmark item due to invalid field type"
// *Cause :  Unable to generate bookmarks for the following types of fields:
//	     --- fields in a matrix group
//	     --- fields based on a item with IMAGE, BUTTON or OLE display
//		 datatype
//	     --- fields that include boilerplate text or other types of column
//		 text
// *Action : Check that the field is a valid type for generating bookmarks.
//	     If not, set the Context Flag on the item to 'No'.
02187,2, "Label style is incompatible with multiple groups "
// *Cause :  Only one group may exist if a label style report is to be generated.
// *Action : Delete all but one group.
02188,2, "Label style is incompatible with multiple module components"
// *Cause :  Only one zone and group may exist for a label style report.
// *Action : Delete all but one group.
02189,2, "Item cannot have a report level-summary function of % of Total"
// *Cause :  A report level-summary cannot have a function of % of Total,
//	     otherwise it would always compute to be 100%.
// *Action : Change the function of the report level summary,
//	     or move the computed item out of the module
//	     level module component.
02190,2, "Computed item is based on '%s' which must be in the same window"
// *Cause :  A computed item cannot reference a source item
//	     that is not in the same window as the computed item.
// *Action : Do one of the following:
//	     --- change the computed item to reference a source item
//		 that is in the same window as the computed item.
//	     --- move the module component containing the source item
//		 into the window that contains the computed item.
02191,2, "Parameter preference LOVTYP has invalid syntax, %s"
// *Cause :  The value for the preference LOVTYP has not been recognized.
// *Action : Consult the documentation for this preference
//	     and verify the syntax is correct.
02192,2, "Parameter preference VALTYP has invalid syntax, %s"
// *Cause :  The value for the preference VALTYP has not been recognized.
// *Action : Consult the documentation for this preference
//	     and check the syntax is correct.
02193,2, "%s is a matrix report with relating module components in different windows"
// *Cause :  This error is caused when a matrix layout format is
//	     chosen for a module that has more than one module
//	     component, and where these module components
//	     have table usages that are required by the matrix,
//	     yet have been placed in more than one window.
// *Action : Do either one of the following:
//	     --- move the offending module components into
//		 the same window
//	     --- change the display format of the module to one
//		 of a type that is not matrix
02194,1, "Computed item '%s' has reset level 'Page'  "
// *Cause :  A computed item that has a reset level of Page must be
//	     placed in a module-level module component, otherwise
//	     its reset level will default to Module.
// *Action : Either ignore the warning as the computed item will be created
//	     with reset level 'module', or move the computed item
//	     into a module-level module component.
02196,8, "Capturing module design and application logic from file  '%s'"
// *Cause :
// *Action :
02197,2, "The named routine \"%s\" has a name uniqueness conflict within this module"
// *Cause :  Oracle Reports does not allow two program units to
//	     have the same name, except in the case of a Package
//	     with its specification and body. This error has occurred
//	     because there is more than one function, procedure or
//	     package with the same name.
// *Action : Ensure that the named routine follows the Oracle Reports
//	     restriction stated in the Cause text. Make the name of
//	     the named routine concerned unique by editing
//	     the name of the offending package set/function/procedure
//	     in the application logic editor and saving the change.
//	     Note: If this named routine is referenced elsewhere within the
//	     module, update the reference to call the relevant named routine.
02198,2, "Computed item with invalid derivation text ignored"
// *Cause :  Either the derivation expression contains an invalid
//	     summary function or the source item is referenced
//	     out of scope. Valid summary functions for a computed
//	     item are :
//	     --- Average
//	     --- Count
//	     --- First
//	     --- Last
//	     --- Maximum
//	     --- Minimum
//	     --- % of Total
//	     --- Standard Deviation
//	     --- Sum
//	     --- Variance
// *Action : Check the derivation expression on the computed item
//	     contains a valid summary function.
02199,1, "Only navigation action items are supported; action item ignored"
// *Cause :  This drilldown module contains an action
//	     item that is not a navigation action item.
//	     Report Generator only supports navigation
//	     action items in drilldown modules.
// *Action : If you require an action item in a drilldown module,
//	     delete the existing action item and create a navigation
//	     action item.
02200,1, "Prompt for argument \"%s\" has been truncated to 20 characters"
// *Cause :  The allowable length of an argument prompt in
//	     Report Generator is restricted to 20 characters.
//	     In order to create a report that will run, this prompt
//	     has been truncated to 20 characters.
// *Action : You may wish to adjust the argument prompt text
//	     in order to take into account this restriction and
//	     have a more legible argument prompt.
02201,1, "Module layout style of %s is incompatible with structure of report"
// *Cause :  The style of the report has been derived
//	     from the structure of the report. This style
//	     is different from the module layout style.
// *Action : No action is necessary: The module layout style
//	     will default correctly.
02202,1, "Break group direction for all groups has been defaulted to %s"
// *Cause :  In a Group Left Report, all break group directions must
//	     be the same. All break group directions have defaulted
//	     to that of the first break group.
// *Action : Change the direction of the first break group to either
//	     Down or Across. All other break group directions
//	     will default to that of the first break group.
02203,1, "Layout style for master group defaulted to Form in Master Detail Report"
// *Cause :  In a master-detail-detail chain, all but the last group in the
//	     chain must have a layout style of Form.
// *Action : The group style will default to Form.
//	     You may set it to Form if you wish.
02204,1, "Module component layout style of ADDRESS is incompatible with report layout"
// *Cause :  The report has more than one break group, or more than
//	     one module component, so a module component layout
//	     style of Address is not valid. It will default to None.
// *Action : No action is necessary. You may reset the
//	     module component layout style to None.
02205,2, "Invalid break group design, no displayed item"
// *Cause :  Break group must have at least one item that is displayed
//	     and is not of unbound type Computed.
// *Action : Either add a displayed item to the break group
//	     or delete the break group.
02206,2, "Invalid break group design, item %s has invalid datatype"
// *Cause :  Break group cannot contain a single item that
//	     is of datatype LONG or LONG RAW.
// *Action : Either add a displayed item to the break group
//	     or delete the break group.
/
/ 02300 .. 02499 RESERVED: CGD utility - CASE Dictionary interface
/
/
/ 02500 .. 02699 Design Recovery error and warning messages
/
02500,2, "Report for design capture failed to load: %s"
// *Cause :  Unable to load the given report filename.
// *Action : The report may have failed to load for various reasons. Check the
//	     following and retry:
//	     --- the file is not being locked by another program or user
//	     --- the file can be opened in Report Builder
02501,1, "Bound Item Show Meaning property may have been captured incorrectly for %s"
// *Cause :  There may be more than one item in the select statement
//	     with the same name as the item that a show meaning
//	     property has been set against.
// *Action : In Report Builder, edit the select statement making
//	     sure that the item whose meaning is obtained from the
//	     CG_REF_CODE table is the only item with the same
//	     name as the relevant CG_REF_CODE column without
//	     the M character at the end of it.
02502,1, "Unable to recover some or all logic from Program Unit %s"
// *Cause :  An inconsistency has been detected by the
//	     Application Logic Capture tool, rendering some or
//	     all of the code in this Program Unit unrecoverable.
//	     This will generally be a result of incorrectly editing a
//	     tag that has been generated into the Program Unit
//	     whose logic has been edited.
// *Action : See the help section that covers how
//	     to use the Application Logic functionality.
//	     The most likely reason is that a tag specifying
//	     a Generated Code Group has been deleted.
02510,8, "Unable to Link SRSA table usage '%s'"
// *Cause :  During the analysis of the SQL statement that will
//	     form the module component, a sub-query construct
//	     was found in the statement.
// *Action : In order for the table usage to be incorporated into the module
//	     component design, the following actions need to be taken:
//	     --- set the table usage type to be Sub-query.
//	     --- link the table usage back to its parent base or lookup usage.
02511,8, "Capturing module design from file '%s'"
// *Cause :  A query in the report definition uses a column that is not defined
//	     in the table for this application system.
// *Action : Add column definition to table definition in the application system
//	     or specify the correct application system.
02513,8, "Unable to link Sub-query table usage '%s'"
// *Cause :  During the analysis of the SQL statement that will form
//	     the module component, a sub-query construct
//	     was found in the statement.
// *Action : In order for the table usage to be incorporated into the module
//	     component design, the following actions need to be taken:
//	     --- set the table usage type to be Sub-query.
//	     --- link the table usage back to its parent base or lookup usage.
02517,2, "No filename given for design capture"
// *Cause :  No filename was given to recover.
// *Action : This is an internal problem with the calling mechanism.
02518,2, "Parse error - the following SQL statement will be ignored\n{%s}"
// *Cause :  The generator has been unable to parse the displayed
//	     SQL statement. No usages will be reverse engineered
//	     for the statement and processing will continue.
// *Action : Modify the report to ensure that all the SQL statements within the
//	     report are syntactically correct.
02520,8, "No table usages captured for Data Source %s"
// *Cause :  During the recovery of a Reports Data Source (i.e. SQL
//	     statement), no table usages were found to be
//	     recovered.
// *Action : Use Report Builder to check the integrity of the
//	     application. The actions that can be taken are:
//	     --- Correct the SQL statement to include the
//		  appropriate table usages
//	     --- Ensure the SQL statement has the correct syntax
//	     --- Remove the Data Source object from the Report
//	     --- Ignore this message
//	     --- Create any required tables usages using the Design Editor
//		  or the Repository Object Navigator
02521,1, "Failed to capture routine %s due to routine of unknown type"
// *Cause :  Unable to capture this Program Unit because
//	     its type is unknown.
// *Action : Open the report in Report Developer and examine
//	     the Program Unit for abnormalities. If anything appears
//	     to be out of order correct it, then save the report
//	     and re-attempt application logic recovery.
//	     If problems persist either delete the program unit
//	     from the report or contact your support representative.
02522,1, "Failed to capture routine %s as no code segment was found "
// *Cause :  The code segment of the Report's Program Unit being
//	     captured by application logic recovery is empty,
//	     so there is nothing to recover back to the Repository.
// *Action : Open the report whose application logic you
//	     are attempting to recover and enter PL/SQL into
//	     the program unit that has no code. If this program
//	     unit is redundant (i.e. it has no code in it) then
//	     you can delete it.
/
/ 02700 .. 02999 RESERVED: CGD utility - CASE Dictionary interface (validate)
/
/
/ 05000 .. 05049 Oracle Reports Generator - messages displayed to user
/
05000,8, "Template %s converted successfully"
// *Cause :
// *Action :
05001,8, "Writing information to key file '%s'"
// *Cause :
// *Action :
05047,8, "Writing file '%s'"
// *Cause :
// *Action :
05048,6, "Validation of %s is complete"
// *Cause :
// *Action :
05049,8, "Capturing application logic from file '%s'"
// *Cause :
// *Action :
/
/ 05050 .. 05199 Oracle Reports Generator - prompts requiring user response
/
05050,6, "Generating attached libraries..."
// *Cause :
// *Action :