Blocking Analyses Based on Formula

Configuring and Managing Analyses and Dashboards 18-21 ■ You can use the template mechanism only with table views and only for single-value data. The template mechanism is not supported for pivot table views or any type of view or for multiple-value data. ■ All values in write-back columns are editable. When displayed in non printer friendly context, editable fields are displayed as if the user has the Write Back to Database privilege. However, when a logical column is mapped to a physical column that can change, the logical column returns values for multiple level intersections. This scenario can cause problems. ■ Any field in an analysis can be flagged as a write-back field, even if it is not derived from the write-back table that you created. However you cannot successfully execute the write-back operation if the table is not write-back enabled. The responsibility for correctly tagging fields lies with the content designer. ■ A template can contain SQL statements other than insert and update. The write-back function passes these statements to the database. However, Oracle does not support or recommend the use of any statements other than insert or update. ■ Presentation Services performs only minimal validation of data input. If the field is numeric and the user enters text data, then Presentation Services detects that and prevents the invalid data from going to the database. However, it does not detect other forms of invalid data input values out of range, mixed text and numeric, and so on. When the user clicks the write-back button and an insert or update is executed, invalid data results in an error message from the database. The user can then correct the faulty input. Content designers can include text in the write-back analysis to aid the user, for example, Entering mixed alphanumeric values into a numeric data field is not allowed. ■ The template mechanism is not suitable for entering arbitrary new records. In other words, do not use it as a data input tool. ■ Write-back analyses do not support drill-down. Because drilling down modifies the table structure, the write-back template does not work.

18.7.2 Configuring for Write Back

Complete the following steps to configure for users to write back values to the data source. To configure for write back: 1. Create a physical table in the database that has a column for each write-back field needed. In the table create statement, make the write-back fields nonnullable. 2. Use the Oracle BI Administration Tool to configure the new table, as described in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition. Caution: The template mechanism takes user input and writes it directly to the database. The security of the physical database is your own responsibility. For optimum security, store write-back database tables in a unique database instance. Note: For optimum security, store write-back database tables in a unique database instance. 18-22 System Administrators Guide for Oracle Business Intelligence Enterprise Edition 3. Create a write-back template that specifies the SQL statements that are necessary to both insert and update values into the table that you created. For more information, see Section 18.7.3, About the Write-Back Template. 4. Add the LightWriteback element in the instanceconfig.xml file, as described in Section 18.7.2.1, Setting the LightWriteback Element. 5. In Oracle BI Presentation Services, grant the following write-back privileges to the appropriate users: Manage Write Back and Write Back to Database. For information, see Managing Presentation Services Privileges in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition. 6. Configure a write-back analysis, as described in Process for Write Back in Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition.

18.7.2.1 Setting the LightWriteback Element

For users to write back values, you must manually add the LightWriteback element in the instanceconfig.xml file. Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, Using a Text Editor to Update Configuration Settings. To manually set the element for write back: 1. Open the instanceconfig.xml file for editing, as described in Section 3.6, Where Are Configuration Files Located?

2. Locate the ServerInstance section in which you must add the LightWriteback

element.

3. Include the element and its ancestor elements as appropriate, as shown in the

following example. WebConfig ServerInstance LightWritebacktrueLightWriteback ServerInstance WebConfig Note that this example does not include parameters that might exist in the file, but that are centrally managed by Fusion Middleware Control and cannot be changed manually. 4. Save your changes and close the file. 5. Restart Oracle Business Intelligence.

18.7.3 About the Write-Back Template

The write-back template is an XML-formatted file that contains SQL statements that are needed to insert and update records in the write-back table and columns that you have created. You can create multiple write-back templates, customizing each one for the fields that are used in each specific analysis. In the table view properties, you specify the name of the write-back template to use.

18.7.3.1 How Write Back Works

If a user has the Write Back to Database privilege, then the write-back fields in their analyses can display as editable fields if properly configured. If the user does not have this privilege, then the write-back fields display as normal fields. If the user types a value in an editable field and clicks the appropriate write-back button, then the