Table of Contents

Search

  1. Preface
  2. Introduction
  3. Working with Enterprise Data Manager
  4. Enterprise Data Manager
  5. ILM Repository Constraints
  6. Partition Exchange Purging
  7. APIs
  8. Smart Partitioning
  9. Salesforce Accelerator
  10. SAP Application Retirement Entities
  11. Import Formats for Constraints
  12. Glossary

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Constraint Definition

Constraint Definition

Constraints may be included in the ILM repository when you import metadata for the source application. If the constraints are not included in the ILM repository, you can manually define the constraints. Or, use tools to help you discover the table relationships and use the suggested relationships to create constraints for the source metadata in the ILM repository.
You can use one of the following options to define constraints:
Manual Definition
You can manually create the constraints if you are familiar with the data model of the source and if the data model is not too large. You may want to manually create constraints if you have a small amount of tables to maintain constraints for.
Definition from Table Relationships
You can use tools to help discover table relationships. The tools help identify primary and foreign key relationships and column uniqueness. Then, create constraints from the suggested table relationships. You may want to define constraints from table relationships if you are not familiar with the data model of the source database. Or, if the data model is too large to manually create the constraints.
After you import or define the constraints for source metadata in the ILM repository, you can maintain the constraints if you need to change them. For example, you can create, delete, or change constraints. The constraints are changed for the source metadata in the ILM repository, not in the source database.
After you import or define the constraints, you can use the constraints to automatically create entities.

Pre-Packaged Applications

For pre-packaged applications, constraint definition is required only if you have custom tables or if you modified standard application tables. Constraints for standard application tables are included in the application accelerators. When you install the accelerators, the metadata and the constraints are imported to the ILM repository.

Custom Applications

For custom applications, constraint definition depends on how the source database stores constraints. If the source database maintains constraints at the database level, the constraints are automatically created in the ILM repository when you import metadata from the source database. If the source database maintains constraints other than at the database level, such as in the application logic, you must define the constraints. You must define constraints if constraint information is not included when you import metadata from the source application.

SAP Applications

For SAP applications, constraint definition is required. When you import metadata from SAP applications, only contraints that are defined at the database level are imported. Constraints that are defined in the SAP ABAP Dictionary are not imported. Constraints are not required to retire the SAP application. Constraints are required to create entities for Data Discovery portal searches. You may want to define the constraints after you retire the application.

0 COMMENTS

We’d like to hear from you!