My Oracle Support Banner

PAXTRAPE Duplicate Record Resulting from Splitting Expenditure with null Quantity or Raw Cost or Denom Burden Cost (Doc ID 2885098.1)

Last updated on JULY 26, 2022

Applies to:

Oracle Project Costing - Version 12.2.10 and later
Information in this document applies to any platform.

Symptoms

When the user attempt to split an expenditure with null quantity or raw cost or denom burden cost, the system create three additional records: one record reverse the original transaction value and two records, each with the transaction value. Resulting in duplicate expenditures.

Steps to reproduce:

  1. Using custom source, upload expenditure to pa_transaction_interface_all with zero quantity and no value for denom burden cost.
  2. Login into the application.
  3. From project responsibility, select View >  Requests > Submit a New Request.
  4. Submit request 'PRC: Transaction Import'.
  5. Without submitting PRC: Distribute Cost request,  navigate to Expenditures > Expenditure Inquiry > Project
  6. Query the newly created expenditure
  7. Select Tools > Split to open split screen
  8. Enter 50 in first field
  9. Enter 50 in second field
  10. Then press ok
  11. Three more records are created. One record is the reverse for original one and two records identical to the original record. Resulting in duplicate raw cost.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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