Understanding Joining Records



  1. Record-hierarchy joins use records that are related through a parent-child relationship.


    You define this join in the record properties and key structure when you create the record in PeopleSoft Application Designer.


    This diagram illustrates an example of record-hierarchy joins.

    Step 1
  2. Related-record joins combine nonhierarchical records that share common fields. This relationship is defined in Oracle PeopleSoft Application Designer.


    Related records are specific to a field in the current record. If you use Application Designer to set field edit properties so that the field validates against a prompt table, the related record link appears to the right of the field.


    This diagram illustrates an example of related-record joins.

    Step 2
  3. Any joins are manually linked to tables to retrieve the correct output. The tables are linked using common keys.


    You can create queries based on multiple tables, even when a table is not in the parent hierarchy or related-record hierarchy.


    This diagram illustrates an example of any joins.

    Step 3
  4. In a left outer join, all rows of data are included from the master table. Matching rows from the subordinate table are also included.


    This diagram illustrates an example of left outer join.


    In this example, all rows from table 1—the Course table (PSU_COURSE_TBL)—appear in the result, even if no match is in table 2—no course IDs are in the Course Session table (PSU_CRS_SESSN).

    Step 4

You have successfully reviewed the Joining Records topic.

Table of Contents  Start Topic