Siebel Connector for PeopleSoft > Prebuilt Integration Objects >

EAI Position Integration Object


The EAI Position integration object involves only one integration component, Position. You can associate parent position, billing product, business address, division, and organization to Position.

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

Figure 27. EAI Position Integration Associations (Relationships)

Click for full size image

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

During position inbound integration, the administrator can sort the positions records in order such that all the parent positions are inserted into Siebel database before their corresponding child positions. For example, the administrator can choose to define the Chief Executive Officer (CEO) of the company first, define its reporting Vice Presidents second, and define the corresponding managers and staff last. Alternatively, the administrator can choose to leave the positions records in random order (for example, the parent positions may be defined after the child positions) and run the whole position inbound process twice. By running the process twice, it makes sure that all child positions are able to associate their parent positions which are not defined by the time the child positions are created.

Similarly, as Figure 27 indicates, the relationship between position and division, the relationship between position and organization, and the relationship between position and business 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). Note that upon picking a division, if the division is already associated with an organization, the associating info of the organization with the position will be filled in automatically.

Alternatively, 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).

The business addresses of a position are automatically retrieved from the business addresses, if they exist, of the corresponding division. During a position integration, only primary business address of the position can be specified from the list and it can be identified by any one of the following fields: Primary Position Address Id (the foreign key) and Primary Position Address Integration Id (the integration ID).


 Siebel Connector for PeopleSoft 
 Published: 18 April 2003