Overview
How Blitz Report is built into Oracle E-Business Suite, and which of its objects you can build on.
Where things are
| Object | Schema | Use |
|---|---|---|
Tables (xxen_*) | Custom schema chosen at installation, XXEN by default, with synonyms in APPS | Read for your own reports and checks. Change content only through the APIs and the XML import. |
PL/SQL packages (xxen_api, xxen_util, ...) | APPS, definer rights | Call from APPS, or grant execute to the schema of your integration. |
| Webservices | ORDS and the EBS Integrated SOA Gateway | Call from applications outside the database, see Calling Blitz Report over REST. |
Supported interfaces
The routines, tables and webservice operations described in this reference are the supported interfaces. Other routines in the same package specifications are internal to Blitz Report and may change in any release.
Start with xxen_api for running reports and maintaining content, and xxen_util for functions to use in report SQL. The engine packages (xxen_report, xxen_report_ebs, xxen_xdo, xxen_upload) document only the routines that report SQL, upload packages and integrations call directly.
Session context
Blitz Report runs with the security of an EBS user and responsibility: organization access, ledger and data access set, flexfield value security and the report assignments. Initialize the database session with fnd_global.apps_initialize before calling an API that runs a report; the webservices do this from the user and responsibility of the request.
Ids and names
Report, parameter and template ids are generated per instance and differ between your development, test and production instances. Identify reports and parameters by name in integrations (xxen_api.create_run_id_, set_parameter_value_), and move definitions between instances with the XML export and import, which match them by GUID.
Generated from Blitz Report 3.3.7 on .