My Oracle Support Banner

Troubleshoot Performance Issues when Using Large Sections Rather than Using Clauses (Doc ID 1065043.1)

Last updated on OCTOBER 02, 2019

Applies to:

PeopleSoft Enterprise SCM Supplier Contract Management - Version 8.9 to 9.1 [Release 8.9 to 9]
Information in this document applies to any platform.

Purpose

Why are large Sections not viewable?  Our approach is to include all the document language in Sections and to not use Clauses.  For example, we have a Section that is 22 pages long.  When you try to preview these documents, it process for around 15 to 20 minutes and then you are signed out of the session.  This document is to help you workaround the performance issues.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

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


In this Document
Purpose
Troubleshooting Steps
 
The system, being architected around this concept, is designed to process smaller tokens (clauses) efficiently (for contract assembly, parsing, etc).  That said, using one large section can work, but depending on the complexity of the underlying xml (wordml) for the large section, the processing of the xml can perform slowly.  We have done some initial research in this area and it appears to be slow within some of our tools processing on larger xml segments as word paragraph styles from the word template are applied across the large document.

We would like to suggest the following options:

Option #1:   Break up the 22-page section into multiple sections or clauses; at least 3 different clause/sections for better performance.  Our system  will then apply Word styles (set up in Document Formats and Option)  that you have defined in the word template to all paragraph without styles.    This is done for paragraph styles and numbering (see documentation for more information).   It does require some up front effort to do this (as you are basically defining a library), but you should see significant performance gains in doing so.

Option #2:   If you really want/need to keep the 22-page section, you should create a new style within Word that is based on Normal, and use this style as the default for the content in the 22 page word document.  If you apply this new style to an existing document, you will need to re-apply other paragraph styles e.g. Body Text Indent.  Our system will not apply  the paragraph styles specified in supplier contracts setup to a clause that has a 'unique' style defined for it already.   In an initial test done here, we have found this to also significantly reduce the processing time.
 
 
 
To discuss this information further with industry peers and Oracle experts, we encourage you to review, join or start a discussion in
My Oracle Support - PeopleSoft Procure to Pay Community!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.