Siebel Connector for PeopleSoft > Prebuilt Integration Objects > Prebuilt Employee Workflows >

Employee - Receive PeopleSoft Customer Workflow


The Position - Receive PeopleSoft Customer workflow, shown in Figure 32, involves reading employee information from an XML file and upserting the data into the Siebel application.

Figure 32. Employee - Receive PeopleSoft Customer Workflow

Click for full size image

This workflow does the reverse of the workflow discussed in the previous section (Employee - Send PeopleSoft Employee). Here the goal is to read an XML file filled with employee(s) information, and upsert them into the Siebel database. Here the upsert stands for a combination of update and insert. Meaning, if the record already exists in Siebel database, then the record will be updated, using any changes supplied in the XML file. If no such record exists, then this record will be inserted as a brand new record. This determination is made by using the user keys in the integration object.

Process Properties

The Employee Inbound workflow has exactly the same set of process properties as Employee Outbound. Except for the process property XML File, all others come by default. The XML File process property is created. Of all these process properties, here, two have a higher significance—Siebel Message and XML File. Siebel Message is used to transfer the object related data between workflow steps, in a hierarchical format. And, XML File is the name and directory location of the XML file that contains account records to be loaded.

Workflow Steps

As shown in Figure 32, this integration workflow involves the following sequential processes:

  1. Read Employee from XML File.
  2. At first, the Read Siebel Message method of the EAI XML Read from File business service is used to read data from an external XML file. This is a standard business service shipped with the Siebel software.

    A value for a single parameter, XML location, is passed to this method. The XML data from the above file is converted into Siebel Message, and is kept in the output argument of the same name.

    This data will then be read by the next workflow step.

  3. Upsert Employee into Siebel.
  4. Next, the Insert or Update method is used to write the extracted Employee data to the Siebel database. As the name suggests, this method inserts or updates the record according to the need.

    All this needs is the Siebel Message output from the Read Employee from XML File workflow step. As discussed before, this step decides on whether to insert or update a record, based on the user keys.

    Finally, how would this workflow know which Integration Object it has to go against? This is neither listed in the process properties nor in the input arguments. This information comes from the input XML file itself. See Example below for details.

    This workflow step has no Output Arguments because once the data is written to Siebel database, the job of this workflow process is complete.

Example

The following sample XML file will be used to load the prebuilt Employee - Receive PeopleSoft Employee workflow.

<?xml version="1.0" encoding="UTF-8" ?>
<?Siebel-Property-Set EscapeNames="false"?>
<SiebelMessage MessageId="EmployeeInboundSample" MessageType="Integration Object"
IntObjectName="EAI Employee" IntObjectFormat="Siebel Hierarchical">
<ListOfEmployee>
<Employee>
<Alias>JohnLee</Alias>
<CellPhone>6504551234</CellPhone>
<Emp>111</Emp>
<EmployeeOrganization>Default Organization</ EmployeeOrganization>
<Fax>6504551999</Fax>
<FirstName>John</FirstName>
<HireDate>1/7/2000</HireDate>
<HomePhone>6504451111</HomePhone>
<JobTitle>Administrator</JobTitle>
<LastName>Lee</LastName>
<LoginName>JLEE</LoginName>
<LoginDomain>INTERNAL</LoginDomain>
<MF>M</MF>
<MaidenName>Chan</MaidenName>
<MiddleName>Paul</MiddleName>
<NextAnnualReviewDate>1/7/2002</NextAnnualReviewDate>
<NickName>Johnny</NickName>
<PagerPIN>PIN111</PagerPIN>
<PagerPhone>6505559898</PagerPhone>
<PagerType>Numeric</PagerType>
<PartyUId>EMP1234</PartyUId>
<PersonalTitle>Mr.</PersonalTitle>

<Phone>6505531335</Phone>
<ShareAddressFlag>Y</ShareAddressFlag>
<ShareHomePhoneFlag>Y</ShareHomePhoneFlag>
<TerminationDate>7/8/2001</TerminationDate>
<ListOfEmployee_Position>
<Employee_Position IsPrimaryMVG="Y">
<EmployeeEndDate />
<EmployeeStartDate>3/7/2001</EmployeeStartDate>
<EmployeeStartDate>7/8/2001</EmployeeStartDate>
<Position>Siebel Administrator</Position>
<Division>Siebel Administration</Division>
</Employee_Position>
<Employee_Position IsPrimaryMVG="N">
<EmployeeEndDate>3/6/2001</EmployeeEndDate>
<EmployeeStartDate>1/7/2000</EmployeeStartDate>
<Position>Compensation Administrator</Position>
<Division>Siebel Sales</Division>
</Employee_Position>
</ListOfEmployee_Position>
<ListOfEmployee_Responsibility>
<Employee_Responsibility IsPrimaryMVG="Y">
<Responsibility>ERM User</Responsibility>
</Employee_Responsibility>
<Employee_Responsibility IsPrimaryMVG="N">
<Responsibility>ePortal User</Responsibility>
</Employee_Responsibility>
</ListOfEmployee_Responsibility>
<ListOfEmployee_StartHomeAddress>
<Employee_StartHomeAddress IsPrimaryMVG="Y">
<StartHomeAddress>2000 College Ave,</StartHomeAddress>
<StartHomeCity>San Mateo</StartHomeCity>
<StartHomeCountry>USA</StartHomeCountry>
<StartHomeState>CA</StartHomeState>
<StartHomeZipcode>94401</StartHomeZipcode>
<StartHomeAddressName>2000 College Ave, Los Angeles, CA
94401</StartHomeAddressName>
</Employee_StartHomeAddress>
<Employee_StartHomeAddress IsPrimaryMVG="N">
<StartHomeAddress>1000 Phoebe Ct.,</StartHomeAddress>
<StartHomeCity>Foster City </StartHomeCity>
<StartHomeCountry>USA</StartHomeCountry>
<StartHomeState>CA</StartHomeState>
<StartHomeZipcode>94404</StartHomeZipcode>
<StartHomeAddressName>1000 Phoebe Ct., Foster City, CA
94404</StartHomeAddressName>
</Employee_StartHomeAddress>
</ListOfEmployee_StartHomeAddress>
</Employee>
</ListOfEmployee>
</SiebelMessage>


 Siebel Connector for PeopleSoft 
 Published: 18 April 2003