28.01.2013 Views

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

● In the Activate dialog, you can select the Bypass validation checkbox in order to skip validation before<br />

activation to improve the activation time. For example, if you have imported a number of objects and<br />

want to activate them without spending time on validation.<br />

Note: During delivery unit import, full server side activation is enabled, activation of objects after import is<br />

done. In this case all the imported objects are activated (moved to active table), even if there are errors in<br />

activated or impacted objects. But the objects for which activation results in error are considered as<br />

broken or inconsistent objects which means that the current runtime representation of these objects is<br />

not in sync with the active design time version. The broken objects are shown in the Navigator with an ‘x’<br />

along side.<br />

Note: The behavior of activation job is as follows:<br />

● The status (completed, completed with warnings, and completed with errors) of the activation job<br />

indicates whether the activation of the objects is successful or failed.<br />

● In case of failure that is when the status is completed with errors, the process is rolled back. This<br />

means, even if there are individual objects successfully activated, since the activation job is rolled<br />

back, none of the objects are activated.<br />

● Even in case of failure, the job log shows success in the summary part. This is to help the user to<br />

indicate that those objects were successfully activated without any issues. But because the entire job<br />

is a failure, none of the objects are activated and all of them are rolled back.<br />

● When you open the job log, the summary list shows only those objects that are submitted for<br />

activation. It does not list all the affected objects. They are listed only in detail section.<br />

6.3 Creating Decision Tables<br />

You use this procedure to create a decision table to model related business rules in a tabular format for decision<br />

automation. Using decision tables you can manage business rules, data validation, data quality rules without any<br />

IT knowledge on technical languages like, SQL Script, MDX . A data architect or a developer creates the decision<br />

table and activates it. The active version of the decision table can be used in applications.<br />

Procedure<br />

1. Set Parameters<br />

1. In the Modeler perspective, expand Content .<br />

2. In the context menu of the package, choose New Decision Table .<br />

3. In the New Decision Table dialog box, enter a name and description for the decision table.<br />

4. To create data foundation for the decision table, perform substeps of the required scenario given in the table<br />

below:<br />

Scenario Substeps<br />

Create a decision table from scratch. 1. Choose Create New.<br />

<strong>SAP</strong> <strong>HANA</strong> <strong>Developer</strong> <strong>Guide</strong><br />

Setting Up the Analytic Model<br />

2. Choose Next.<br />

P U B L I C<br />

© 2012 <strong>SAP</strong> AG. All rights reserved. 133

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!