## Creating Parent-Child Relationships

This chapter provides an overview of parent-child relationships and discusses how to create parent-child relationships by employee.

### Understanding Parent-Child Relationships

You can define an organizational structure to provide executives and managers with a summary of the reporting relationships in your organization. An organizational structure shows the flow of information in an organization. The organizational structure that you define can vary from business to business, or even from department to department within a business.

You can use an organizational structure to show reporting relationships among employees and supervisors. These relationships are called parent-child relationships.

You can define two types of parent-child relationships:

- A relationship in which an employee address can appear multiple times.

- A relationship in which an employee address can appear only once.

After you define a parent-child relationship, you can periodically review and revise that relationship to reflect staff additions or turnover.

### Creating Parent-Child Relationships by Employee

This section provides an overview of parent-child relationships by employee, lists prerequisites, and discusses how to:

- Set processing options for the A/B - Org Structure Browse program (P0150).

- Set processing options for distribution list control (P02150).

- Create parent-child relationships by employee.

#### Understanding Parent-Child Relationships by Employee

When you define organizational structures, you create hierarchies of relationships between parents and children. For example, a large business might have headquarters in one city and several regional offices that are subsidiaries of the headquarters. You can define an organizational structure in which you set up the regional offices as children, or subsidiary business units, of the headquarters. The regional offices can in turn be parents, or higher-level business units, of local offices. For each office, you can set up an organizational structure by employee, with upper-level managers as parents of mid-level managers, and mid-level managers as parents of employees.

Each employee can have only one immediate supervisor. The system prevents you from entering a manager as a subordinate of an employee.

You use one of these modes to define an organizational structure by employee:

- Enter child positions for a higher-level parent.

- Enter a parent position for subordinate child positions.

After you create parent-child relationships, you can revise these relationships as necessary to reflect changes in the organization.

#### Prerequisite

Set up parent-child structure types in user-defined code (UDC) 01/TS.

See User-Defined Codes for Human Capital Management Systems.

#### Form Used to Create Parent-Child Relationships by Employee

Form Name | FormID | Navigation | Usage
Address Parent/Child Revisions | W0150A | Employee Management (G05BE1), Employee/Supervisor Relationships Click Add on the Work With Distribution Lists form. | Create parent-child relationships by employee.

#### Setting Processing Options for the A/B - Org Structure Browse Program (P0150)

Processing options enable you to specify the default processing for programs and reports.

Note. To access the processing options for the A/B - Org Structure Browse program (P0150), you must use the Work With Interactive Versions program (P983051).

Process

These processing options specify whether the system displays workflow information for parent-child relationships and controls whether multiple parents in tier relationships can have overlapping effective dates.

1. Workflow Information | Specify whether the system displays workflow processing information. Values are: Blank: Do not display 1: Display
2. Tier Descriptions | Specify whether a tier structure can be defined based on effective dates for a root parent address. The root parent in a structure is the highest level of a parent-child structure, and it can have no parent. Values are: Blank: Do not allow. 1: Allow.

Defaults

These processing options specify whether the system automatically provides effective dates and provides the option to select an organization structure from a predefined list in UDC 01/TS.

1. Date Defaults | Specify whether the system supplies default dates on the Address Parent/Child Revisions form (W0150A) when the beginning and ending effective dates are blank. Values are: Blank: Does not supply default dates. 1: Supplies default dates.
Beginning Effective Date - Julian | Specify the default beginning effective date. The system supplies this date on the Address Parent/Child revisions form if you leave the beginning effective date on that form blank and if you specify a 1 in the Date Defaults processing option.
Ending Effective Date - Julian | Specify the default ending effective date. The system supplies this date on the Address Parent/Child revisions form if you leave the ending effective date on that form blank and if you specify a 1 in the Date Defaults processing option.
2. Default Organization Structure Type | Specify the value that the system enters in the Organizational Structure field when the A/B Org Structure Browse program (P0150) is first run.

#### Setting Processing Options for Employee/Supervisor Relationships (P02150)

Processing options enable you to specify the default processing for programs and reports.

Defaults

These processing options specify an organizational structure type and designate the program version number that the system uses.

1. Enter the default Structure Type | Specify the default structure type. For employee/supervisor relationships, specify ES.
2. Enter the Version of Organizational Structure Revisions to call. | Specify the version of the A/B - Org Structure Browse program (P0150) to call. If this processing option is left blank, the system uses version ZJDE0001.

#### Creating Parent-Child Relationships by Employee

Access the Address Parent/Child Revisions form.

Parent Number | Enter the Address Book number of the primary level in a hierarchy (or reporting) relationship. A parent in one hierarchy can be a child in another hierarchy. A hierarchy can be organized by business unit, employee, or position. For example, you can create a hierarchy that shows the reporting relationships between employees and supervisors.
Structure Type | Enter a code from UDC 01/TS that identifies a type of organizational structure that has its own hierarchy in the JD Edwards EnterpriseOne Address Book system (for example, E-mail). This value identifies the type of distribution list, such as ES for employee/supervisor, ORG for group, and EML for E-mail.
Address Number | Enter a number that identifies an entry in the JD Edwards EnterpriseOne Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or location.
End Eff Date (end effective date) | Enter the date on which the address book record will cease to exist in the structure.