Typical Workflow to Model Data for Pixel-Perfect Reports
A data model used for pixel-perfect reports can be simple with one data set retrieved from a single data source (for example, the data returned from the columns in the employees table) or can be complex with parameters, triggers, and bursting definitions and using multiple data sets.
Task | User | More Information |
---|---|---|
Launch the data model editor. |
Report Data Modeler | |
Set properties for the data model. (Optional) |
Report Data Modeler | |
Create the data sets for the data model. |
Report Data Modeler | |
Define the data output structure. (Optional) |
Report Data Modeler | |
Define the parameters to pass to the query, and define lists of values for users to select parameter values. (Optional) |
Report Data Modeler | |
Define Event Triggers. (Optional) |
Report Data Modeler | |
(Oracle Applications Only) Define Flexfields. (Optional) |
Report Data Modeler | |
Test your data model and add sample data. |
Report Data Modeler | |
Add a bursting definition. (Optional) |
Report Data Modeler | |
Map Custom Metadata for documents to be delivered to Web Content Servers (Optional) |
Report Data Modeler |