PeopleSoft Supplier Contract Management Integrations

Supplier Contract Management integrates with the following PeopleSoft applications:

PeopleSoft Purchasing.
PeopleSoft eProcurement.
PeopleSoft Strategic Sourcing.

Purchasing

Supplier Contract Management includes a transactional contract definition entry page that is fully integrated to Purchasing for purchase order creation, integration to requests for quotes, and accounts payable. In addition, using the transactional contract definition, you have access to Supplier Contract Management's electronic contract repository, document authoring capabilities, and contract compliance monitoring features. Within the transactional contract component, you can generate an authored contract. Using the authoring system, you can create document clauses that link to transactional information, such as supplier and item IDs included on the contract, and then use that information to create the contract document.

In environments where the transactional purchasing contract is not used, and instead the transactional purchase order alone is used on the transaction side, you can optionally configure the system to author contract documents based on the purchase order transactional data.

Note: The Supplier Contract Management authoring capability is not indented to be a replacement for the Purchase Order Dispatch report and its calculations. Instead, Supplier Contract Management's authoring is intended for Microsoft Word-based contract documents that have terms and conditions along with transactional information that you can bind to the document. The authoring does not provide the specific layout, and coding within it to present data to match the Purchase Order Dispatch report

Purchasing also provides you the capability to generate contract request type documents within Supplier Contract Management documents through the Add/Update Requisition page. You can either create a document for use with a requisition or maintain a document that exists for the requisition. This feature enables you to collect user responses related to contract requests that the system can later provide to contract specialists when they are authoring the contract document itself. When the requisition is approved, and the system creates the corresponding transactional contract through the request for quote or through the Strategic Sourcing award process, the system can carry forward responses to wizard requisition questions for the contract specialist to use to generate the formal contract document.

PeopleSoft eProcurement

PeopleSoft eProcurement provides you the capability to generate contract request type documents within Supplier Contract Management documents through the eProcurement requisition page. You can either create a document for use with a requisition or maintain a document that exists for the requisition. This feature enables you to collect user responses related to contract requests that the system can later provide to the contract specialist when authoring the contract document itself. When the requisition is approved and the system creates the corresponding transactional contract through the request for quote or through the Strategic Sourcing award process, the system can carry forward the responses to wizard requisition questions for the contract specialist to use to generate the formal contract document.

Strategic Sourcing

The Strategic Sourcing application provides integration for agreements. These are deliverables that are included in the event (request for proposals). Agreements can reference the Supplier Contract Management clause library for content, which the system includes on event header or line bid factors. When you award an event to a contract, the system transfers agreement information to the transactional contract, including contract-specific agreement clauses that you can include in the final contract document.

Note: Since Supplier Contract Management provides an additional ad hoc source transaction along with user-defined document types, it is often possible to create additional authored document types using the system for various purposes. While not integrated specifically with other system sources, document types that use ad hoc source transactions can contain user-defined fields, wizards, and role-level security to model various types of documents that you might require.