Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  21. Using Multiple Engines in an ILM Environment
  22. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  23. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Business Rule Types

Business Rule Types

When using EDM business rules can be constructed using one of five methods:
  • WHERE
  • SET
  • INLINE
  • LOOP
  • FULL
In this section we will describe how to create a business rule using each type, and why one type would be used versus another.
To implement business rules you must first determine what the functional business requirement is, and then identify what the technical representation of that requirement is. The technical representation of the requirement is a SQL statement.
In our example the business rule is INVOICE IS NOT CLOSED. The technical representation of this requirement may be:
select invoice_header_id from ap_invoice_header where invoice_status <> ‘ CLOSED’;
Our sample interim table would have the following columns:
INVOICE_HEADER_ID
PURGEABLE_FLAGINVOICE_IS_NOT_CLOSED
We will use this example to describe how to use the different condition types.