More and more companies use selfservice funcionality. PeopleSoft deliveres some out-of-the-box selfservice functionality, but what if you want to develope some yourself?

Here are some pointers to get you on the right track:

Since some time now PeopleSoft’s support site Customer Connection has been replaces by Oracle Metalink. The Change Assistant is making use of Customer Connection (when searching for bundles / fixes) and other PeopleSoft servers (like update.peoplesoft.com).

Due to this migration to Customer Connection you might get some issues when using the Change Assistant. This post helps you in getting things working again.

In addition to my post of yesterday, I found out how to read PeopleSoft table definitions into the Topology manager of ODI.

After creating the SQL Server 2005 Data Server create a new Physical Schema specifying your PeopleSoft database (for instande HRMS9 for a HR 9.0 environment) and the owner of the schema (= dbo for SQL Server). In the Context tab give the Logical schema a logical name.

To actually load table definitions you can use furtheron for integration, start the ODI Designer.

I’ve been busy trying to get Oracle Data Integration to work. First step after installation is to connect one or more data sources using the Topology Manager. Although ODI is a fairly new product, it only comes with a SQL Server 2000 driver.

To install the SQL Server 2005 JDBC driver and use it to connect to the database you need to follow the following steps:

Within the new PeopleTools versions PeopleSoft often uses Component Interfaces in PeopleCode to adjust data. These constructions are sometimes very hard to understand. Especially if the update of data goes wrong, the error generated from the Component Interface is tucked away in an array which can only be read when debugging the proces.

There is a very simple way to get around this.