C.3 PL/SQL Batch Registering Function

The SQL script that rwconverter generates for you to batch register reports in Oracle Fusion Middleware consists mainly of calls to the RWWWVREG.REGISTER_REPORT function. The syntax of RWWWVREG.REGISTER_REPORT is as follows:

Function Rwwwvreg.register_report(
  p_owner varchar2,
  p_name varchar2,
  p_servers varchar2,
  p_filename varchar2,
  p_description varchar2,
  p_privileges varchar2,
  p_availability varchar2,
  p_types varchar2,
  p_formats varchar2,
  p_printers varchar2,
  p_pdformTemplate varchar2,
  p_parameters varchar2,
  p_trigger varchar2)
  return number;
    --  =0 : succeeded;
    --  !=0 : failed;

The table below describes each of the parameters taken by RWWWVREG.REGISTER_REPORT.

Table C-1 RWWWVREG.REGISTER_REPORT parameters

Parameter	Description
`P_OWNER`	Is the DB Provider name. The default is the current Oracle Fusion Middleware DB Provider that you are connected to when you start the SQL*PLUS script. For example: `P_OWNER=>'PORTAL_APP'`
`P_NAME`	Is the name used to identify the report in Oracle Portal. `P_NAME` corresponds to the Name field in the Create Report Definition File Access wizard. For example: `P_NAME=>'Earnings'`
`P_SERVERS`	Is the names of the Reports Servers on which the report definition files defined in the `P_SERVERS` parameter have access privileges. The list of Reports Servers is comma delimited. `P_SERVERS` corresponds to the Reports Servers field in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_SERVERS=>'repserver,acct'` Note: The Reports Servers you list for `P_SERVERS` must already be registered in Oracle Portal. For more information, refer to Chapter 16, "Deploying Reports in Oracle Portal".
`P_FILENAME`	Is the name of the report definition file that is being registered. `P_FILENAME` corresponds to the Oracle Reports File Name in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_FILENAME=>'earnings.rdf'`
`P_DESCRIPTION`	Is a description of the report. `P_DESCRIPTION` corresponds to the Description field in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_DESCRIPTION=>'restricted report'`
`P_PRIVILEGE`	Is the users or roles given privileges to run the report definition file defined in `P_FILENAME`. This list is comma delimited. `P_PRIVILEGE` corresponds to the Grantee list on the Access tab of the Manage Component page for the report. Note that you must uncheck Inherit Privileges from Portal DB Provider in order to see the Grantee list. For example: `P_PRIVILEGE=>'SCOTT,JABERS,PORTAL90'`
`P_AVAILABILITY`	Is the name of the availability calendar that determines when the report definition file defined in the `P_FILENAME` parameter will be available for processing. `P_AVAILABILITY` corresponds to the Availability Calendar Name field in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_AVAILABILITY=>'production'` Note: The availability calendar must already exist in Oracle Portal. For more information on creating an availability calendar, see Chapter 16, "Deploying Reports in Oracle Portal".
`P_TYPES`	Is the destination types to which the report definition file defined in the `P_FILENAME` parameter can be sent (for example, cache, printer). This list is comma delimited. `P_TYPES` corresponds to the Types multiple select box in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_TYPES=>'CACHE,printer'`
`P_FORMATS`	The destination formats to which the report definition file defined in the `P_FILENAME` parameter can be sent (for example, HTML, PDF). This list is comma delimited. `P_FORMATS` corresponds to the Formats multiple select box in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_FORMATS=>'HTMLCSS,PDF'` Note: If the destination format for the report is `DELIMITEDDATA`, it may not be possible to batch register the report. As a workaround, you can define a different destination format, then batch register the report, and later manually edit the report to `DESFORMAT=DELIMITEDDATA`.
`P_PRINTERS`	The printers to which the report definition file defined in the `P_FILENAME` parameter can print. This list is comma delimited. `P_PRINTERS` corresponds to the Printers multiple select box in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_PRINTERS=>'sales_printer,acct_printer'` Note: The printers you list for `P_PRINTERS` must already be registered in Oracle Portal. For more information, refer to Chapter 16, "Deploying Reports in Oracle Portal".
`P_PFORMTEMPLATE`	Is the parameter form template that determines the page style of the Runtime Parameter Form. `P_PFORMTEMPLATE` corresponds to the Parameter Form Template field in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_PFORMTEMPLATE=>'public.finance_template'`
`P_PARAMETERS`	Is the user and system parameters' default, high, and low values, or list of values name. Note: The `P_PARAMETERS` parameter does not have a corresponding `rwconverter` option. Hence, if you want to batch import user parameter values, ranges, or lists of values, you must manually edit the SQL script generated by `rwconverter`. `P_PARAMETERS` corresponds to the (parameter) Name, LOV, Low Value, and High Value fields in the Create Report Definition File Access wizard and the Edit Report Definition File page. The default corresponds to the value set in the Runtime Parameter Form for the specified parameter. For example: `P_PARAMETERS=>'(P_LASTNAME, LOV=LASTNAME_LOV) (P_SSN)(COPIES, DEFAULT=1,LOW=1,HIGH=2)'` where: `P_LASTNAME`, `P_SSN`, and `COPIES` are parameter names. `LOV` is the name of the list of values. `DEFAULT` is the default value. `LOW` is the low value in a range of values. `HIGH` is the high value in a range of values.
`P_TRIGGER`	Is the validation trigger written in PL/SQL that returns a boolean statement (for example, true (succeeded) or false (failed)). `P_TRIGGER` corresponds to the text box in the Create Report Definition File Access wizard and the Edit Report Definition File page. For example: `P_TRIGGER=>'Is begin` `IF UPPER(DESTYPE) = ''PRINTER'' AND` `EMPNAME = ''SMITH''` `THEN` `RETURN(TRUE);` `ELSE` `RETURN(FALSE);` `END IF;` `end;'`