Bookshelf Home | Contents | Index | Search | PDF

Siebel Connector for PeopleSoft > Prebuilt Integration Objects >

EAI Employee Integration Object

---

The EAI Employee integration object includes five integration components: Employee, Employee_ERM Employee Period Summary, Employee_Position, Employee_Responsibility, and Employee_StartHomeAddress. You can associate an Organization with the Employee object.

As you can see in Figure 30, Employee is the central entity. Using this integration object, you can insert, update, or delete information from the employee integration component. Employee is the primary integration component for this integration object.

Figure 30. Employee as Central Entity

The relationship between Employee/Start Home Address and Employee/ERM Employee Period Summary come through an MVG. New rows can be inserted or existing rows updated in the Start Home Address entities during the same time rows are inserted or updated in the Employee component. When an account is deleted, all the addresses associated with that account are also deleted. Insert, update or delete of ERM Employee Period Summary is not supported in this release. The information of ERM Employee Summary is available for read-only.

The relationship between Employee/Position and Employee/Responsibility come through MVG associations. Therefore, this integration object cannot be used to create, update, or delete positions or responsibilities. In other words, when you associate an employee with a position or a responsibility, that particular position or responsibility should already exist in Siebel database. As you can see from the ERD, these components are picked through Multi-Value Groups (MVGs). Hence, each employee can be associated with multiple positions or responsibilities.

Employee has a one-to-one relationship with Organization, which means a foreign key to Organization (named Employee Organization Id) exists in the Employee component. This relationship is implemented through a picklist. An existing organization can be identified by one of the following fields: Employee Organization Id (the foreign key) or Employee Organization Integration Id (the integration ID).

Similarly, as Figure 30 indicates, the relationship between position and division and the relationship between position and organization are implemented through a picklist.

An existing division can be identified by any one of the following three fields: Division Id (the foreign key), Division (the name), or Division Integration Id (the integration ID).

An existing organization can be identified by any one of the following three fields: Organization Id (the foreign key), Organization (the name), or Organization Integration Id (the integration ID).

Bookshelf Home | Contents | Index | Search | PDF