Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for Oracle E-Business Suite
  3. PowerExchange for Oracle E-Business Suite Configuration
  4. Oracle E-Business Suite Sources and Targets
  5. Application Source Qualifier Transformation
  6. Oracle E-Business Suite Mappings
  7. Oracle E-Business Suite Sessions
  8. Datatype Reference
  9. Error Messages
  10. Glossary

PowerExchange for Oracle E-Business Suite User Guide for PowerCenter

PowerExchange for Oracle E-Business Suite User Guide for PowerCenter

Key Relationships for Oracle E-Business Suite Targets

Key Relationships for Oracle E-Business Suite Targets

An open interface can contain multiple interface tables. These interface tables can have a primary key-foreign key relationship between them.
When you import an Oracle E-Business Suite target definition, the Designer creates a key relationship between each group in the target definition and its parent group. Each key uses the following naming convention:
GPK__<group_name> GFK__<primary_group_name>__<group_name>
The following table describes the key naming conventions:
Key Name Component
Description
GPK|GFK
Type of key. GPK represents a primary key. GFK represents a foreign key.
group_name
Name of the group to which the key belongs.
primary_group_name
Name of the master group with which you have established primary key relationship.
When you create mappings with the primary key-foreign key relationship, the Designer might not create the relationship for the tables. You need to manually set the primary key relationship in the foreign key table.
The PowerCenter Integration Service uses these keys to maintain the hierarchy of the Oracle E-Business Suite data. It does not load the input data to the interface tables. A foreign key field that does not match the primary key of its parent group results in an orphan row. A primary key field that is not unique results in a duplicate row.
If you insert null values in the primary key or foreign key fields, the PowerCenter Integration Service does not write any hierarchy to the Oracle E-Business Suite target.
If you do not select the Skip Hierarchy Validation session property, you must link the GPK and GFK ports in the mapping.
If you select the Skip Hierarchy Validation session property, the PowerCenter Integration Service ignores the data received on the GPK__<parent group> and GFK__<primary_group_name>__<group_name> ports of an Oracle E-Business Suite target.

0 COMMENTS

We’d like to hear from you!