INTEGRATION BETWEEN SUPPLIER

PORTAL AND PEOPLESOFT

Following design options for integration which were considered:

1. Synchronized Transfer

a. Supplier Portal

1. On click on Submit, a request to web service hosted at PeopleSoft server is

made. This request transfers vendor information to PeopleSoft hosted web
service.
2. A response from web service is sent to Supplier Portal Application server.
Along with the response, vendor id is sent as well.
3. Supplier portal, depending on response, stored the data into supplier portal
database. This will include PeopleSoft vendor id.
4. A nightly batch process running at PeopleSoft server ftps updated vendor
details to Supplier Portal SQL Server.
5. A batch process running at SQL server reads the received file and updates
the Supplier SQL database with vendor details.
 b. User Portal

User portal will provide registration and update points to Dow Jones employee.
Following registration takes place through User Portal:
1. Employee Vendor Registration
2. On Behalf Registration

Following are the steps:

1. On click on Submit, a request to web service hosted at PeopleSoft server is

made. This request transfers vendor information to PeopleSoft hosted web
service.
2. A response from web service is sent to User Portal SharePoint Server. Along
with the response, vendor id is sent as well.
3. User Portal, depending on response, stored the data into supplier portal
database. This will include PeopleSoft vendor id.
4. A nightly batch process running at PeopleSoft server ftps updated vendor
details to Supplier Portal SQL Server.
5. A batch process running at SQL server reads the received file and updates
the Supplier SQL database with vendor details.
Queries:
1. Synchronization will require communication between Supplier Portal
Application server (hosted on Internet) and PeopleSoft server. Will this create
any security issues?
2. On similar lines, a communication between SharePoint 2007 Server and
PeopleSoft server needs to be opened. Will this be provided and done?
3. The response from PeopleSoft needs to send the vendor id as Supplier Portal
Id will not be created by then and for any future updates, this vendor id will
be used between Supplier portal and PeopleSoft.
4. The current SOAP request contains Username and password. Why is this
required and what should be the values?
5. The SOAP request also contains a Vendor ID. While sending this request, we
won’t have the supplier id as well as vendor id with us. What should be done
in this case?
6. Supplier Portal needs to pass Requestor details to PeopleSoft for the vendors.
This needs to come in the SOAP request sent from Supplier portal to
PeopleSoft. Will the structure of request change in this scenario? Please
specify the structure.
7. In the request and response, how will we differentiate between Employee
Vendor and regular vendor? The employee vendor details are getting stored
in different table.
8. For Employee vendor, requestor details will not be sent to the PeopleSoft as
they won’t be present.
9. When vendor is is added directly through PeopleSoft, requestor details will
not be available in Supplier Portal as well as PeopleSoft.
10.How will an Update and an Add xml differ? How will the system differentiate
between update, add or delete?
11.What should be the schedule of batch job passing the data from PeopleSoft to
Supplier Portal database?
2. Asynch- Transfer

a. Supplier Portal

1. On click on Submit, an XML with vendor details is created and is sent to

PeopleSoft server through FTP.
2. Supplier Portal application stores the vendor data in Supplier portal database.
3. A process hosted at PeopleSoft server, pickups the ftp file.
4. The process parses the XML file and stores the vendor data in PeopleSoft
database.
5. For vendor updates/add through PeopleSoft, the process fetches the data
from PeopleSoft database on nightly basis.
6. This data is stored into XML file and stored in file system on PeopleSoft
Server
7. A job running on SQL server reads the file from the ftp location
8. The job parses the XML and stores the vendor detail in Supplier Portal
Content database.
 b. User Portal

1. On click on Submit, an XML with vendor details is created and is sent to

PeopleSoft server through FTP.
2. User Portal stores the vendor data in Supplier portal database.
3. A process hosted at PeopleSoft server, pickups the ftp file.
4. The process parses the XML file and stores the vendor data in PeopleSoft
database.
5. For vendor updates/add through PeopleSoft, the process fetches the data
from PeopleSoft database on nightly basis.
6. This data is stored into XML file and stored in file system on PeopleSoft
Server
7. A job running on SQL server reads the file from the ftp location
8. The job parses the XML and stores the vendor detail in Supplier Portal
Content database.
Queries:

1. Where should we FTP the file? Is it Supplier Portal database server or

PeopleSoft server? For above scenario, we assumed it to be PeopleSoft.
2. Jobs running to SQL server to access vendor XML file will need to have
access to PeopleSoft server location where the file is stored.
3. In this case we need to send Supplier Portal Id to PeopleSoft. PeopleSoft
needs to have a field to store Supplier Portal Id.
4. All the updates from Supplier Portal to PeopleSoft and PeopleSoft to
Supplier portal need to have Supplier Portal Id as well as Vendor id.
5. Employee vendor will have employee id as Vendor Id. Need to confirm if
this applies to PeopleSoft vendor creation as well.
6. What should be the schedule of batch job passing the data from
PeopleSoft to Supplier Portal database?