1 – Introduction
The OBIEE writeback functionality allows the end-user to write informations in the database with some limitations.
Often the writeback functionality is used to allow the users to apply a comment to certain data in the report or to input values for a caluclation.
This option can be integrated only in Table Views; Gauge, Pivot and other views do not support the writeback.
2 – Best Practice
The best practice is to do not allow the user to directly modify the datamart structure; is always useful to provide a table that will store the data inserted via writeback. That table is usually imported in the repository and linked with the other tables in order to be used in the reports.
3 – Setup the writeback functionality
3.1 The SQL statement that are executed by the server to complete a writeback operation are stored in xml template that need to be create in the following folder: <OBIEE_HOME>\OracleBI\web\msgdb\customMessages\
3.2 Give whatever name to the file and write the followin xml code inside it:
<?xml version=”1.0″ encoding=”utf-8″ ?>
<WebMessageTables xmlns:sawm=”com.siebel.analytics.web/message/v1″>
<WebMessageTable lang=”en-us” system=”WriteBack” table=”Messages”>
<WebMessage name=”<Message Name that will be used in the presentation later [case sensitive!!!]>“>
<XML>
<writeBack connectionPool=”<Connection Pool Name used in the repository [case sensitive!!!]>“>
<insert> <Insert statement> </insert>
<update> <update statement> </update>
</writeBack>
</XML>
</WebMessage>
</WebMessageTable>
</WebMessageTables>
Remember: The <insert> and <update> tags need to be defined in the xml file even if there is no statement defined for that particular operation. In this case, a blank has to be inserted between the open/close tags; e.g. <insert> </insert>
Read the rest of this entry »