This chapter provides an overview of PeopleSoft Supplier Contract Management reports, lists common definitions, and discusses how to:
Create reports.
Access other procurement contract reports.
Understanding PeopleSoft Supplier Contract Management ReportsPeopleSoft Supplier Contract Management provides document reports that you can use or tailor to meet organizational needs. The reports provide summary and detailed document information along with where clauses and sections are used, if they have been changed, or if they have not been used since a date that you specify. The reporting system makes it easy to access, tailor, run, and view the reports.
You can run the reports from the run control pages of the PeopleSoft Supplier Contracts Reports menu. The system builds the reports using XML Publisher. To create the reports you do not need to use PeopleCode, and there are not any custom pages required to run the reports.
Note. To enable users access to Supplier Contract Management reports, you need to define users and roles as SCMTUSER users on the Report Category page. To access the page, select Reporting Tools, XML Publisher, Setup, Report Category and then search for the SCMTUSER report category. After accessing the Report Category page, you can specify the roles or users that you want to run and have access to report pages. If the SCMTUSER report category is not available, you can add the value.
Common Elements Used in This Section|
As Of Date |
Select a date. This is the date for the template layout. Typically, you leave the date as the current date so that you use the latest version of the report. The field is required, and the system displays an error message if the template is not active as of the As Of Date field value. |
|
Created Date From and To Date |
Select a date from which you want to create a report for when documents were created. All documents that were created within the date range that you enter, and that meet other criteria, are included in the report. You cannot enter dates in the future and the date that you select in the Created Date From field must be earlier than or equal to the to date. |
|
Department |
Select a department on which to base a contract document search. |
|
Document Administrator |
Select a document administrator on which to base a contact document report. The system retrieves information about those documents for which the administrator is responsible. |
|
Document Status |
Select a document status on which to base a report. The status represents the life-cycle state of the document. Only documents that are in the status you select are included in the report. |
|
Document Type |
Select a document type on which to base a report. Document types help you define specific settings, defaults, and security for fine-tuning the use of each type of document. Only documents that were created using the document type that you select appear in the report. |
|
Last Modified Date From andTo Date |
Select a date from which you want to create a report for changed documents. The date cannot be in the future and must be less than or equal to the to date. The last modified date to must be greater than or equal to the last modified date from. |
|
Library SetID |
Select a library setID. The setID is used in conjunction with a document type. The document type is setID controlled. So, you need to enter a library setID before you can enter a document type, which is a library element. |
|
Sponsor |
Select a sponsor on which to base the report. |
|
Source Transaction |
Select the source transaction type on which to base the contract document report. The source transaction indicates the transaction from which the document originated. If you do not make a selection, all source transaction types are included in the report. If you select a source transaction, the system provides additional entry fields based on the source transaction. Valid values include: Ad hoc: A stand-alone document that is not associated with a transaction. When you select this value, the system displays the Ad Hoc ID field and ad hoc ID from and to fields. Purchasing Contract: A document that is based on transactional purchasing contract information. When you select this value, the system displays the Contract SetID field and contract ID from and to fields. Purchase Order: A contract document generated from a purchase order. When you select this value, the system displays fields that relate to a purchase order, such as the Business Unit and Purchase Order ID From and Purchase Order ID To fields. Also, if you select Purchase Order, the system displays the Vendor SetID and Vendor ID fields for you to define specific vendors. |
|
Template ID |
Select the template that you want to use to run the contract document report. PeopleSoft Supplier Contract Management provides basic templates that you can use or tailor to meet organizational needs. This list provides the report followed by the default template provided for the report:
|
Creating Reports This section provides an overview of PeopleSoft Supplier Contract Management reports, lists common definitions, and discusses how to:
Create Document Status Summary reports.
Create Document Status Detail reports.
Create Contract Content Deviations reports.
Create Unused Contract Content reports.
Create Contract Content Usage reports.
Access procurement contract reports.

Pages Used to Create Supplier Contract Management Reports|
Page Name |
Definition Name |
Navigation |
Usage |
|
CS_RPT_DSTAT1 |
Supplier Contracts, Reports, Document Status Summary |
Create Document Status Summary reports. |
|
|
CS_RPT_DSTAT2 |
Supplier Contracts, Reports, Document Status Detail |
Create Document Status Detail reports. |
|
|
CS_RPT_OBJDEV |
Supplier Contracts, Reports, Contract Content Deviations |
Create Contract Content Deviations reports. Three versions exists for this report. The first version is the Contract Content Deviations report (CS_OBJ_DEV_1) The second is the Contract Content Deviation Summary report (CS_OBJ_DEV_2). This report is the same as CS_OBJ_DEV but does not include object text. The final version is the Contract Content Deviation by Contract (CS_OBJ_DEV_3) This version is the same as CS_OBJ_DEV_1 but is sorted by contract and then library object within the contract. This report includes the modified object text. |
|
|
CS_RPT_OBJUNUSE |
Supplier Contracts, Reports, Unused Contract Content |
Create Unused Contract Content reports. |
|
|
CS_RPT_OBJUSE |
Supplier Contracts, Reports, Contract Content Usage |
Create Contract Content Usage reports. |

Creating Document Status Summary ReportsAccess the Document Status Summary page (Supplier Contracts, Reports, Document Status Summary).
You use this page to run the Document Status Summary report process (CS_DOC_STAT1). This report provides basic document status information for the documents that you select to include in the report. When the system does not locate report data, the report contains a No Data Found line. The last page of a report also has a End of Report line.
The report is sorted by library setID, then source transaction, document type, administrator, ad hoc setID/ad hoc ID, contract setID, contract ID, and purchase order business unit/purchase order ID.
See Also
Document Status Summary (CS_DOC_STAT1)

Creating Document Status Detail ReportsAccess the Document Status Detail page (Supplier Contracts, Reports, Document Status Detail).
You use this page to run the Document Status Detail report (CS_DOC_STAT2) process. The report is similar to the summary report, but provides more detailed information in a different format about document statuses. Among the additional features, the report contains provides the collaboration status, as of date, and version. If a document is in Dispatched status the report provides dispatched as of date and version. If the document is in an Amended status, the report provides the amendment, amendment option, and as of date.
Also if user-defined fields are enabled on the PeopleSoft Supplier Contract Management setup page, and if the fields are also enabled for the document type used for the document (or if document types are not in use), then those user fields that are enabled appear in the report.
The report is sorted by library setID, then source transaction, document type, administrator, ad hoc setID/ad hoc ID, and contract setID.
For more information about fields on this page, see the common elements section.
See Also
Document Status Detail (CS_DOC_STAT2)

Creating Contract Content Deviations ReportsAccess the Contract Content Deviations page (Supplier Contracts, Reports, Contract Content Deviations).
You use this page to run the Contract Content Deviation report (CS_OBJ_DEV_1) process. The report provides a listing of documents having deviations based on the document objects selected, and that have been manually modified within documents as of the date that you specify. So, this report enables you to identify which contracts have deviations against the type of content for which you want to search, such as highly sensitive terms and conditions.
The system tracks changes made to documents for all objects within that document based on when the document was last checked in, not when each individual change was made. For example, if you update an object one day and check it in, and then a different object in the same document is changed later in the day, and checked in, both objects will show the same last modified date. The last modified date always reflects the last time the entire document was checked in.
Note. Documents will only appear in this report if they have manual changes that were made directly to the newly created or copied document. So, for example if users update a document, and then you create a new document using the Copy From Contract link of the first document, the newly created document will not appear in the Contract Content Deviations report. This is because those changes were not made directly to the new document but were instead made by copying in the entire document.
Report Template
Use this group box to define template information for the report.
|
Template ID |
Select a template for use with the report. The Contract Content Deviations report has three different template views. They are:
|
Library Object Selection Criteria
Use this group box to define objects from the contract library on which to build the Contract Content Deviations report. To define document-level values for the report use the Document Selection Criteria group box.
|
Library SetID |
Select a library setID. |
|
Incl Add/Del Library Content (include additions and deletions to library content) |
Click to include library content that has been manually added or deleted for documents in the report. When this check box is deselected, the system only includes changes that have been manually made to existing document objects. |
|
Clause or Section |
Select to build the report for clauses or for sections. If you leave the field blank, both clauses and sections are included in the report. If you select Section, the Class Name and Approval Type fields are not available. |
|
Class Name |
Select a clause class name to which you want to limit the report. You use classes that require workflow approvals for the clause definition or within documents. When you select a class, the system only includes modified documents in the report that include clauses that have been updated within that class. |
|
Approval Type |
Select an approval type to which you want to limit the report. An approval type is a part of the workflow process and controls approvers for the clause approval process and document approval process. When you select an approval type, the system only includes modified documents that include clauses that have been updated within that approval type. |
Document Selection Criteria
Use this group box to define document report criteria. The system uses these values along with the library object selections to create the Contract Content Deviation report. Depending on the source transaction that you select, the system provides additional fields on which to base the search.
|
Include Only In-Process Docs |
Click to exclude documents in an Executed or Complete status from the report. When the check box is deselected, documents will be included in the report regardless of the Executed or Complete status. |
See Also
Contract Content Deviations (CS_OBJ_DEV)

Creating Unused Contract Content ReportsAccess the Unused Content page (Supplier Contracts, Reports, Unused Contract Content).
You use this page to run the Unused Contract Content report (CS_OBJ_UNUSE) process. This report provides information about contract library objects that are not used in documents. This information helps you determine outdated or dormant objects in the contract library. The report lists the objects by setID, content type, and content ID and provides details about each document in which the object is used.
Fields on this page are similar to those on previous report pages. See those page details and the common elements section for more information about the Unused Contract Content report.
See Also
Unused Contract Content CS_OBJ_UNUSE

Creating Contract Content Usage ReportsAccess the Content Usage page (Supplier Contracts, Reports, Contract Content Usage).
You use this page to run the Contract Content Usage report (CS_OBJ_USAGE) process. This report provides information about where contract library objects have been used in documents. The report lists the objects by setID, content type, and content ID.
This page is similar to previous report pages. See those page details and the common elements section for more information about the Contract Content Usage report.
See Also
Contract Content Usage (CS_OBJ_USAGE)
Accessing Other Procurement Contract ReportsYou can access a variety of procurement contract reports from within PeopleSoft Supplier Contract Management by using the Procurement Contract Reports component (Supplier Contract, Procurement Contract Reports).
These reports include:
Master Contracts (POY1050): Lists all the master voucher contracts for a specified setID.
Recurring Voucher Contracts (POY1051): Lists all the voucher contracts for a specified setID with contract header and distribution information.
Recurring Voucher Contract Details (POY1052): Lists recurring voucher contract details by setID and contract ID.
Order Contracts (POCNT100): Lists all the vendor contracts based on selection criteria you enter on the Order Contracts page.
Internal Order Contracts (POCNT200): Lists all internal contracts based on selection criteria you enter on the Internal Contract Report page. You can view item usage by category, by vendor, and by contract.
Order Contract Releases (POY3010 – business unit) (POY3020 – setID): Lists order contract releases based business unit or setID.
Non-Contracted Items (POCNT300): Lists use and monetary value of items not under contract. Additionally, you can identify items being used that should be substituted for items currently under contract.
Contract Expiration (POCNT400): Lists, by vendor/category or category/vendor, contracts that are scheduled to expire within a selected date range.
Activities Report (POY3031): Lists activities against contracts within a specified setID.