Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for Siebel
  3. PowerExchange for Siebel Configuration
  4. Siebel Sources
  5. Application Source Qualifier for Siebel Sources
  6. Siebel Targets
  7. Siebel Business Service Transformation
  8. Siebel EIM Read Transformation
  9. Siebel EIM Load Transformation
  10. Siebel EIM Invoker Transformation
  11. Siebel Sessions
  12. Datatype Reference
  13. Error Messages
  14. Glossary

PowerExchange for Siebel User Guide for PowerCenter

PowerExchange for Siebel User Guide for PowerCenter

Generating Key Values

Generating Key Values

When you import a Siebel 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__<parentgroup_name>__<group_name>
The following table describes the key naming conventions:
Key Name Component
Description
GPK|GFK
Type of key. The key name begins with GPK when it is a primary key. The key name begins with GFK when it is a foreign key.
group_name
Name of the group to which the key belongs.
parentgroup_name
Name of the parent group with which you have established primary key relationship.
For the Account business component, the Designer generates primary keys, GPK__Account and GPK__Business_Address. It generates the GFK__Account__Business_Address foreign key for the child group.
Provide the values for the GPK and GFK fields in the source that define the relationship between the parent group and child group rows. Choose values for the GFK field from the GPK field in the parent group.
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.

0 COMMENTS

We’d like to hear from you!
Hi, I'm Bolo!
What would you like to know?
Please to access Bolo.