Understanding PeopleSoft eProcurement and HRMS Integration
PeopleSoft eProcurement enables you to use employee information that is stored in the PeopleSoft HRMS database to create requesters and automatically update PeopleSoft eProcurement, based on changes to the employee data. The integration is accomplished with PeopleSoft Integration Broker, which enables you to receive service operations sent by PeopleSoft HRMS. When changes are made to the record in HRMS, they are automatically received by eProcurement.
The service operations are delivered with a status of Inactive. You must activate each service operation before attempting to publish or subscribe. The service operations that are sent by PeopleSoft HRMS must be activated in that database, and the messages to which PeopleSoft eProcurement receives must be activated in the PeopleSoft FDM database.
The integration between PeopleSoft HRMS and PeopleSoft eProcurement enables you to preform these tasks:
Send new user data from HRMS to eProcurement.
Automatically create requesters if a user contains a role that is predefined in Supply Chain Management as having access to the component.
Automatically inactivate a requester when a user account is locked out.
When updating information between databases, PeopleSoft Integration Broker imposes these outbound and inbound rules:
Full Table Publish (outbound)
This rule erases all data from the target table and replaces it with data from the source table.
Incremental Table Publish (outbound)
This rule captures the addition, change, or deletion of data that is performed in the source database and either inserts a new row of data, or deletes, or updates the corresponding row of data in the target database.
Note: PeopleSoft eProcurement receives data changes from the PeopleSoft HRMS database. It does not send data to PeopleSoft HRMS (except for the USER_PROFILE service operation). Also, PeopleSoft eProcurement does not receive any full table user profile data changes. It only receives incremental data changes.