| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Connector for PeopleSoft > Prebuilt Integration Objects >
Overview
The integration objects and workflows that are provided with the Siebel Connector for PeopleSoft can be used for receiving and sending accounts, employees, and positions from Siebel applications.
Siebel eBusiness Applications includes three prebuilt integration objects to support integration with PeopleSoft: EAI Account, EAI Employee, and EAI Position. The most frequently integrated components of each object are included in the corresponding integration object.
Every integrated component has multiple fields. For example, the Account integration component of the EAI Account integration object has 182 fields. In theory, all of these fields can be used for the outbound integration. This means that values for each of these fields may be written to an XML file for transportation to a PeopleSoft. However, several fields in the integration components are inactive because they are either unlikely to be required or useful in integrating with a PeopleSoft ERP system or not required by Siebel applications. You may activate these fields using Siebel Tools.
User keys uniquely identify the rows in an integration object. A user key may be a single field or a combination of fields. For example, one Account integration component user key combines two fields, Location and Name. If the user key is selected, all account records inserted or updated through this integration component are identified by these two fields. Each integration component can have multiple user keys. And, as the following discussion indicates, user keys are important in sequencing.
In Figure 13, a sample Account integration component has four user keys. When a new record based on this integration component is inserted or updated, the uniqueness of that record is checked first against User Key:1 (Key Sequence Number 1). If the fields that make up this user key are not present in the record under consideration, the next user key is considered (Key Sequence Number 2). If those fields are absent too, then the uniqueness is checked using User Key:3, and so on, until fields for a particular user key are present.
As Figure 13 indicates, the second user key has an Integration Id field. This field is typically used to store a unique external reference, often from the external system. Using this field, you can enforce the uniqueness of records in two different databases and systems.
If you decide not to input values into the Integration Id, User Key:3 is considered to check the record's uniqueness. This user key contains the fields that you will normally use to uniquely identify an account record. In fact, Name is the required field in the Account Business Component. You can see this in Figure 14.
If you pass an XML file that looks like the example in Figure 15 for an upsert method of Siebel Adapter, User Key 3 will be considered. Because this file contains neither Id nor Integration Id fields, the first two user keys are not used. If you are using the upsert method with the above record, Siebel Adapter will look into the Siebel database and first find out if an account record with name A.K. Parker and Location San Mateo exists. If such a record exists, then that record in Siebel database will be updated. If no such record (Name: A.K. Parker Location: San Mateo) exists, then a new account record will be inserted into the Siebel database.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Connector for PeopleSoft Published: 18 April 2003 |
