Working with Key Fields
Use the Definition Table component - Interface Definition Fields page, Key Field field to define a field as an occurrence (Occurrence) key or and effective-date(Effdt) key.
See Setting Up the Definition Table.
When you define a field as an occurrence key, multiple records (rows) are formatted for export. When you define a field as an effective-date key, the retrieved data is put through an extra process to eliminate redundant records (rows) from the PI_PARTIC_EXPT table.
For example, suppose the Job Data table contains the data shown in this table:
|
Effective Date |
Effective Sequence |
Comprate |
Department ID |
|---|---|---|---|
|
1999-01-15 |
0 |
100 |
00100 |
|
1998-12-12 |
0 |
100 |
00200 |
|
1998-12-10 |
0 |
85 |
00200 |
|
1997-06-10 |
0 |
85 |
00300 |
|
1997-05-31 |
0 |
75 |
00400 |
If you define the Effective Date field as an occurrence key, the following data is formatted for export:
|
Effective Date |
Comprate |
|---|---|
|
1999-01-15 |
100 |
|
1998-12-12 |
100 |
|
1998-12-10 |
85 |
|
1997-06-10 |
85 |
|
1997-05-31 |
75 |
If you define the Effective Date field as an effective-date key, the following data is formatted for export:
|
Effective Date |
Comprate |
|---|---|
|
1998-12-12 |
100 |
|
1997-06-10 |
85 |
|
1997-05-31 |
75 |
Warning! Accurate processing depends on the collate order that you specify for the effectived-dated field. On the PS Tables component - PS Tables page, Collate Order field, you must selectAsc (ascending). If you do not select the ascending collate order, you will eliminate all but the last row.