My Oracle Support Banner

ECA 9.2 : The Transaction Limits Are Not Processed Correctly When the Transaction Identifier Limits Are Added and Changed Multiple Times as Part of a Contract Amendment. (Doc ID 2894399.1)

Last updated on SEPTEMBER 13, 2022

Applies to:

PeopleSoft Enterprise FIN Contracts - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


The Transaction Limits are not processed correctly when the transaction identifier limits are added and changed multiple times as part of a contract amendment.

Replication steps:

  1. Customer Contracts > General Information - Create a new contract with a rate-based contract line and a Project and Contract associated with it.
  2. Go To The Contract Terms page.
  3. Click the Transaction Limits link and amend the contract to add “Additional Purchase”.
  4. Enter a new transaction limit (LABOR) and save.
  5. Now change the transaction Identifier (EQUIP) and save and proceed to complete the contract amendment. (changed from LABOR to Equip).
  6. When processing the amendment, the change is not shown correctly in the Amendment Components. The component is and the amendment ref #1 field is also showing LABOR which is incorrect. It should have been "EQUIP".
  7. Process amendment, the CA_LMT_TXN's CA_CHG_STATUS value is still 'P'. This is incorrect. The expectation is that it should be 'C'.
  8. Using Project Costing > Transaction Definition > Add Transactions, Create an ACT row that generates a billable row that exceeds the transaction limit amount. Notice that no OLT rows are generated in PS_PROJ_RESOURCE. This is incorrect.

Replication document



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

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