Duplicate Rows On CS_DOC_PTXTBASE When Processing Multiple Amendments ABENDED at Step CS_DOC_MAIN.MAIN.Step06 (PeopleCode) --RC = 24 (108,524)

(Doc ID 2268885.1)

Last updated on JUNE 13, 2017

Applies to:

PeopleSoft Enterprise SCM Supplier Contract Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Contracts

Duplicate Rows on CS_DOC_PTXTBASE when Processing Multiple Amendments

When processing multiple amendments, getting duplicate rows on CS_DOC_PTXTBASE table that causes abend for the document generation process. See attachment for replication steps.

ERROR
-----------------------
A fatal PeopleCpode SQL error occurred. Please consult your system log for details.

SQL error in Exec. (2,280) SCM_CS_GEN_WORDML.Utilities.OnExecute Name:Create DocPtxtBase PCPC:3319 Statement:63
Called from:CS_DOC_MAIN.MAIN.GBL.default. 1900-01-01.Step06.OnExecute Statement:44

During the execution of SQL, an error occurred in the Exec subroutine. The preceding message should have described the SQL being executed.

process 92877 ABENDED at Step CS_DOC_MAIN.MAIN.Step06 (PeopleCode) --RC = 24 (108,524)

CallAppEngine: Applicatioin CS_DOC_MAIN:Appengine error. (2,653) SCM_CS_MGMT.Controller.Doc_Controller.OnExecute
Name:CreateAmendment PCPC:118319 Statement:1

During a CallAppEngine builtin function call, the Application Engine detected an error. The applicationi Engine Log may provide more information.




STEPS
-----------------------
The issue can be reproduced at will with the following steps:

There is an issue with duplicate rows on the CS_DOC_PTXTBASE table when processing multiple amendments, ultimately causing the document generation process to abend.

1. Setup – Create Clauses and Section for Amendment Configurator
2. 1. First clause, AMEND_TITLE:
a. Title field – Amendment to %%_CONTRACT_ID%% (this should be populated by checking out the clause and adding the information in Word).
  b. Not numbered (screenshot shows Numbered Clause flag set Clause ID = AMENDMENT_BODY
  c. Not protected
3. 2. Second clause, AMENDMENT_BODY:
  a. Title field – A dash (-) with the color white to be invisible. This is for the clause to number correctly.
  b. Full Text – Add provisions regarding scope, specifications, cost, time, etc.
NOTE: This information should be populated by checking out the clause and adding the information in Word.
  c. Numbered
  d. Not protected
4. 3. Third clause, AMENDMENT_END_CLS.
  a. Title field – A dash (-) with the color white to be invisible. This is for the clause to number correctly.
  b. Full Text – Except as modified herein, the terms of the Agreement shall remain in full force and effect.
NOTE: This information should be populated by checking out the clause and adding the information in Word.
  c. Numbered
  d. Protected
5. 4. Section, AMENDMENT_SECTION:
  a. Title – The parties agree to amend the Agreement as follows:
  b. Numbered
  c. Add the AMENDMENT_BODY clause to the section.
6. Create new amendment configurator using the new clauses and section.
7. Create and execute a new contract document or execute an existing document.

8. Click the Create Amendment button
9. Select Amendment Files Only in the Amendment Options field.
10. Select the new Amendment Configurator in the Amendment Configurator ID field.
11. Click OK.
12. Click the Edit Amendment File button to check out the amendment
13. Place the cursor after the 1 in the first clause.
14. Press the right arrow key, the cursor is now outside of the header clause. Add text to the document.
15. Complete the same steps for the section and main clause (adding text both within and outside of the clause/section.
16. Save and check in document.
First Amendment is checked in.
17. Complete the following for the amendment:
  a. Approve – Use Bypass Approvals
  b. Dispatch – Manual
  c. Execute
 Above screenshot is from the CS_DOC_PTXTBASE table. One row for each of the objects in the configurator.
18. Repeat steps 7 -16 for a second amendment. Make sure that text is added inside and outside of the clauses/section.
19. Repeat steps 7-16 again multiple times. Be sure to validate the CS_DOC_PTXT table for each executed amendment version.
20. After a given number of executed amendments (for most of my testing it typically occurs around the 4th or 5th amendment, a duplicate row is inserted on the CS_DOC_PTXTBASE table.
21. In this example, the duplicate row was inserted when the 4th amendment was created. Click the Create Amendment button.
22. See error above

Cause

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