Issues with Documents generated by SCM for Events and Contracts (Doc ID 2198206.1)

Last updated on MAY 02, 2017

Applies to:

PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise SCM Strategic Sourcing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


Issue #1 -> A contract generated by strategic sourcing award errors out on document generation when SCM has more than one active SCM contract document types
Issue #2 -> When a contract document is generated by the multi-sourced document configurator shared between RFx and Contracts; the RFx document content is copied into the system generated contract documents

Steps to Reproduce the Issue:
1.Add a custom document type of "Purchasing Contract" source transaction
2.Make sure that the new added purchasing contract document is active
3.So, there should be more than ONE active purchasing contract document types
4.Copied an existing delivered contract document type
5.The contract document type must share the "multi-source" document configurator with RFx document type. This is not required to replicate issue #1 but is a requirement to reproduce issue# 2
6.Now add transactions
7.Create a sourcing event, add RFx document, follow the delivered RFx wizard,complete the document generation process and complete/approve the document Add document
8.The finish button will generate the document. Once the document is generated the document status is "Draft". Access the edit document button and open the solicitation document generated by SCM authoring system. Once the document is ready, modify the document by placing custom text in the document.
9.Save the document to your local drive and use the check-in document button the RFx document management page and check-in the edited document
10.Here¿s the screen capture of the edited first page of the SCM generated RFx document
11.Complete/approve the document. The option to either complete or approve depends on the document type configuration. As delivered by Oracle the document type configuration allows "Completing" the document.
12.Now, navigate to the strategic sourcing event and post the event
13.Enter/create bidder bids for the sourcing event
14.Analyze the sourcing event bid
15.Post the award to a "general contract"
16.Award a SS event to general contract produces a contract transaction. Once the contract transaction is established, "Add document" button is available.

The award event page is updated with the contract ID

17.Click on "Add document" on the contract entry screen (as shown above).Because the contract is awarded from a sourcing event that contains a RFx
wizard and that both the SS event document and the contract document were generated by a common multi-source document configurator; the wizard data
from the sourcing is available for use with the contracts
18.System asks users that event document is available and if you would like to copy from it?

a.Accepting an option to copy the event document; passes forward any sourcing event wizard collected data to the contract document wizard for common wizard bind variables
b.If the option is not accepted (click on NO) then the RFx wizard data is not available to the Contracts wizard
c.The RFx document was generated with Oracle delivered multi-source document configurator (MULTI_SOURCE_AUC)
d.Accepted the option to copy the event document into the contract document (clicked on YES in the prior screen capture); however, system produced a hard
error message because the document type was not populated and option to choose a document type was grayed out
19.Document types as available in the system - note that there are two available document types. However, availability of document types shouldn't
produce the above error message

20.This completes the error replication steps for Issue# 1.

Replication steps for Issue # 2

21.The next issue is to validate the contract document content when the contract document is generated by a multi-source configurator 

22.In order to complete the contract document process - seems that it becomes necessary to turn off one of the active contract document types - so that
there's only one active contract document type.

23.Now there's only ONE active contract document configurator - highly undesired but seems necessary to continue creating the contract document
24.Navigate to the sourcing event awarded contract and click on "Add a Document" button available on the contract entry screen
25.Because the contract was awarded from a strategic sourcing event containing an RFx document and that the option to copy forward the event
document was selected; the contract document generator references the event document; as shown in the above screen capture
26.Complete the contract document wizard process and review the produced document when generated

27.Review the generated contract document
a.Expected Behaviour -> contract document content and language to be controlled by active CLAUSES in the document configurator and that nothing from the event document is copied from to the contract document
b.Contract document wizard will contain the RFx wizard data

c.Observed Behaviour -> System generated and "unedited" version of the Contract document included manually edited text from the event document. A very severe issue since my customer will have fully generated and drafted/developed solicitation document. The majority of the event document content will be manual; from outside the SCM generated controlled clause
d.But the event wizard data came forward to the contract document wizard as expected




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms