1. Designing and Publishing Pixel-Perfect Reports in Oracle Analytics Server
  2. Model Data for Pixel-Perfect Reports
  3. Use the Data Model Editor
  4. Components of a Data Model

Components of a Data Model

A data model supports the following components:

  • Dataset

    A dataset contains the logic to retrieve data from a single data source. A dataset can retrieve data from a variety of data sources (for example, a database, an existing data file, a web service call to another application, or a URL/URI to an external data provider). A data model can have multiple datasets from multiple sources.

  • Event triggers

    A trigger checks for an event. When the event occurs the trigger runs the PL/SQL code associated with it. The data model editor supports before data and after data triggers as well as schedule triggers. Before data and after data triggers consist of a call to execute a set of functions defined in a PL/SQL package stored in an Oracle database. A schedule trigger is executed for scheduled reports and tests for a condition that determines whether or not to run a scheduled report job.

  • Flexfields

    A flexfield is a structure specific to Fusion Applications Suite. The data model editor supports retrieving data from flexfield structures defined in your Fusion Applications Suite database tables.

  • Lists of values

    A list of values is a menu of values from which report consumers can select parameter values to pass to the report.

  • Parameters

    A parameter is a variable whose value can be set at runtime. The data model editor supports several parameter types.

  • Bursting Definitions

    Bursting is a process of splitting data into blocks, generating documents for each data block, and delivering the documents to one or more destinations. A single bursting definition provides the instructions for splitting the report data, generating the document, and delivering the output to its specified destinations.

  • Custom Metadata (for Web Content Servers)

    If you've configured a web content server as a delivery destination and enabled custom metadata, the custom metadata component displays in the data model editor. Use this component to map data fields from your data model to the custom metadata fields set up for a set of rules defined in a Content Profile.