Components of a Data Model

The data model gets its inputs from the planning and analysis stage. Here the modeler, along with analysts, collects information about the requirements of the database by reviewing existing documentation and interviewing end-users.

The data model has two outputs:

1.) The first is an entity-relationship diagram which represents the data structures in a pictorial form. Because the diagram is easily learned, it is valuable tool to communicate the model to the end-user.

2.) The second component is a data document. This a document that describes in detail the data objects, relationships, and rules required by the database. The dictionary provides the detail required by the database developer to construct the physical database.

  • Data set: A data set contains the logic to retrieve data from a single data source. A data set 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 data sets from multiple sources.¬†
  • Data sources: Data sources are elements of the data model that represent real world sources of data in your environment.
  • Data types: Data types are elements of the data model that represent sets of data stored in a data source.
  • Data items: Data items are elements of the data model that represent actual units of data stored in a data source.
  • Links: Links are elements of the data model that define relationships between data types and data items.
  • Event sources: Event sources are special types of data sources. Each event source represents an application that stores and manages events.
  • 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 Oracle Applications. The data model editor supports retrieving data from flexfield structures defined in your Oracle Application 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 have 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.