Bookshelf Home | Contents | Index | Search | PDF

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

Account - Receive PeopleSoft Customer

---

The prebuilt Account - Receive PeopleSoft Customer workflow involves reading accounts from an XML file and making upserts into the Siebel application. This workflow is shown in Figure 21.

Figure 21. Account - Receive PeopleSoft Customer Workflow

This workflow is the functional reverse of the workflow discussed in the previous section (Account - Send PeopleSoft Customer). Here, the goal is to read an XML file filled with account information and upsert the data into the Siebel database. Upsert involves both updating and inserting data.

If the record already exists in Siebel database, it is updated with any changes supplied in the XML file. If the record does not exist, it is inserted as a new record. This determination is made by using the user keys in the integration object.

Process Properties

The Account Inbound workflow has exactly the same set of process properties as Account Outbound. Except for the process property XML File, all others come by default.

The process property XML File was 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. Also, XML File is the name and directory location of the XML file that contains account records to be loaded.

Workflow Steps

This integration workflow involves the following sequential processes:

Read Account from XML File.

In the first step in the workflow in Figure 21, 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 only one parameter is passed to this method, the XML file location.

XML data from the XML file is converted into Siebel Message, and is kept in the output argument of the same name, as shown below.

This data is read in the next workflow step.

Upsert Account into Siebel

In the next step, an Insert or Update method is used to write data to the Siebel database. This needs the Siebel Message output from the previous workflow step. As before, this step decides 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 requirement is not listed in the process properties or in the input arguments. The information comes from the input XML file itself.

Looking at the header of the input XML file, notice the following:

At the top of the Account_Inbound.xml file, there is an envelope for Siebel Message. That envelope includes IntObjectName=EAI Account. This is the same integration object that was used for the outbound workflow.

This workflow step has no Output Arguments because the workflow is complete once data is written to Siebel database.

Bookshelf Home | Contents | Index | Search | PDF