Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Example of a Custom Validation Rule with a Join Between Tables

Example of a Custom Validation Rule with a Join Between Tables

You can create a condition for a custom validation rule that joins data from two tables. One table contains the parent record in the incoming data. The other table is a lookup table with a static list of values.
Use values in the parent record for conditions. If you create a condition that requires a value from a child record, the rule does not return results. You cannot join to child tables from the parent table in a custom validation rule.
You reference the incoming data as a table with the alias S. You reference the joined table with the alias I.
The following code shows a validation rule SQL statement for the join expressed by Put (BO - C_AAA_BO):
WHERE NOT EXISTS (SELECT 1 FROM C_B_LU_ADDR_TP T WHERE T.ADDR_TP = S.COL1)
The following code shows the generated SQL statement:
SELECT S.PKEY_SRC_OBJECT , (SELECT 'a' FROM dual WHERE NOT EXISTS (SELECT 1 FROM C_B_LU_ADDR_TP T WHERE T.ADDR_TP = S.COL1 ) AND ROWNUM <= 1 ) RULE1 FROM (SELECT NULL AS ROWID_OBJECT , 'SVR1.3GDX' AS PKEY_SRC_OBJECT , 'SYS0' AS ROWID_SYSTEM FROM dual) I CROSS JOIN (SELECT '1' AS COL2 , '1' AS COL1 , 'SVR1.3GDX' AS PKEY_SRC_OBJECT , 'SYS0' AS ROWID_SYSTEM FROM dual) S

0 COMMENTS

We’d like to hear from you!