Concurrent Process XLAACCUP:PRC: Create Accounting Error "The subledger journal entry does not balance in the entered currency"
(Doc ID 2871534.1)
Last updated on SEPTEMBER 22, 2023
Applies to:
Oracle Project Billing - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
Concurrent Process PRC: Create Accounting showing the below exception for revenue transactions,
Error
The subledger journal entry does not balance in the entered currency. Please verify the entered amounts on the journal entry lines.
Steps to reproduce the issue
1.Go into the Project Responsibility
2. Navigate to View-> Request
3. Run the PRC: Create Accounting
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 |
| Cause |
| Solution |
| Possible Cause : Setup issue |
| Case 1 :Inter company Balancing rules not defined |
| Case 2 : Customer associated with the project was different from customer id on the agreement |
| Case 3:Expenditure item dates do not fall between the effective start and end date of the incurred by person. |
| Possible Cause :Code fix ,Issue is caused due to lower Version of accounting related files |
| Case 2: Join condition is failing for the events in PA_XLA_REVENUE_LINES_V view. |
| Case 3 : The procedure RTC_UBR_UER_CALC,P_REVTRANS_UBR calculated 'prior' to rounding of the uer amount. |
| Case 4 : Expenditure item dates do not fall between the effective start and end date of the incurred by person. |
| Case 5: Realized gain account is created in GL for the a revenue journal even when realized gains or losses is not enabled. |
| Case 6 : In Revenue generation, during rounding of amount using 'oarrou' DPLACE variable is used to round amount.DPLACE is defined as 2 irrespective of currency precision. |
| Possible Cause : Data Corruption |
| Case 2 : Draft revenue number credited is wrongly updated |
| Case 3: Data corruption due to incorrect UBR/UER values in PA tables |
| Case 4: Conversion rate and rounding issue with project id<project ID>, DRAFT_REVENUE_NUM<draft revenue num>, and EVENT_ID<event_id>. |
| Case 5: The cause of the issue is invalid / incorrect data in PA_CUST_REV_DIST_LINES_ALL |
| Case 6 : Revenue amounts are populated up to 4 decimals where as currency has a precision of 2 |
| Case 7: Revenue status is showing as transferred to GL but corresponding expenditure item id is missing in pa_cust_rev_dist_lines_all |
| Cause 8 : Data corruption in pa_expenditure_items_all |
| Cause 9: Data corruption in table pa_Cust_rev_dist_lines_all and pa_Draft_Revenues_all |
| Cause 10: Issue was caused by reversal script as it didn't reverse the changes completely. |
| Cause 11: PRC: Generate Accounting Event is rounding the entered amount using the transaction currency |
| References |