PeopleSoft Source-to-Settle Integrations
This document includes information common to the following Oracle's PeopleSoft applications:
Oracle's PeopleSoft Purchasing
Oracle's PeopleSoft Payables
Oracle's PeopleSoft eProcurement
Oracle's PeopleSoft Strategic Sourcing
Oracle's PeopleSoft Services Procurement
PeopleSoft Purchasing
Vouchers can be built from various sources in PeopleSoft Purchasing, including purchase order and receiver lines, evaluated receipt settlement (ERS) vouchers, return to supplier (RTV) transactions, and procurement card system vouchers. You can perform matching among vouchers, purchase orders, receivers, and inspection status to improve control and accuracy. You view related documents across the entire procure-to-pay process.
See Understanding Voucher Processing and the Voucher Life Cycle.
PeopleSoft Payables
The interaction of PeopleSoft Purchasing and PeopleSoft Payables data and processing enables you to match vouchers with all purchase order and receiver details, and to generate payments without waiting for invoices, using the Evaluated Receipt Settlement matching process. In addition, the PeopleSoft Payables voucher build process automatically generates invoices from Return to Supplier transactions and Procurement Card statements created in PeopleSoft Purchasing to streamline and centralize voucher creation. With instant access to all related current and historical procurement data, the procurement analysis tools enable you to view trends or track one item across all of procurement.
PeopleSoft Purchasing purchase order contracts and PeopleSoft Payables vouchers components are combined in one place within the system, providing full contract functionality through a single user interface.
Source-to-Settle Supplier Information
All applications in the source-to-settle business process use the Supplier component to create and maintain supplier information.
Field or Control |
Description |
|---|---|
Description |
Free-flow text up to 30 characters. |
Effective Date |
Date on which a table row becomes effective; the date that an action begins. For example, if you want to close out a ledger on June 30, the effective date for the ledger closing would be July 1. This date also determines when you can view and change the information. Pages or panels and batch processes that use the information use the current row. |
Language or Language Code |
The language in which you want the field labels and report headings of the reports to print. The field values appear as you enter them. Language also refers to the language spoken by an employee, applicant, or non-employee. |
Process Frequency (group box) |
Designates the appropriate frequency in the Process Frequency group box: Once executes the request the next time the batch process runs. After the batch process runs, the process frequency is automatically set to Don't Run. Always executes the request every time the batch process runs. Don't Run ignores the request when the batch process runs |
Process Monitor |
This link takes you to the Process List page, where you can view the status of submitted process requests. |
Report ID |
The report identifier. |
Report Manager |
This link takes you to the Report List page, where you can view report content, check the status of a report, and see content detail messages (which show you a description of the report and the distribution list). |
Recipient's |
Select to have a report print in the language defined for the recipient of the report. |
Request ID |
A request identification that represents a set of selection criteria for a report or process. |
Run |
This button takes you to the Process Scheduler request page, where you can specify the location where a process or job runs and the process output format. |
Run Control ID |
Each run control you create receives a unique run control ID. When you select a process from a menu, a search dialog box appears, asking for a run control ID. If you're in Add mode, enter a new ID for the run control you're about to define. If you're in Update/Display mode, enter an existing run control ID or press Enter and select from the list of available run control IDs. |
Short Description |
Free-flow text up to 15 characters. |
Specified |
Select to have a report print in the language that you specify in the Language field. |
Status |
Options include Active or Inactive. By linking status and effective date, you can retain historical information and plan future implementation. For auditing purposes, PeopleSoft encourages inactivating data that is no longer in use instead of deleting it. |
User ID |
The system identifier for the individual who generates a transaction. |