R12: AP/XLA: Payments Cannot Be Posted
(Doc ID 3051352.1)
Last updated on OCTOBER 08, 2024
Applies to:
Oracle Payables - Version 12.2.4 and laterInformation in this document applies to any platform.
Symptoms
Payments cannot be accounted for and their associated invoices are partially accounted.
Output of the Create Accounting program shows the following error for the problem payment
The total debits and the total credits do not balance for this subledger journal entry. Please ensure that the
application accounting definition PAS En Base a Devengado owned by &OWNER contains journal line types for the event class
Payments and event type Payment Cancelled that can create a balanced entry. Also verify that any conditions
associated with a journal line type are correct.
Automatic Withholding Tax is set to calculate at Invoice Validation and Invoice Payment Time.
All invoice lines have been discarded.
Invoice amount is currently zero (0.00) correctly. SUM of Invoice Lines amounts s zero (0.00) and SUM of Invoice Distributions amounts per Line is zero (0.00).
Invoice was paid and payment was Voided correctly.
All AWT Lines and distributions of the invoice net to zero(0.00).
All Invoice Distributions are Validated OK, except for the AWT ones.
All Invoice Distributions are Accounted OK, except for the AWT ones.
All AWT Invoice Distributions are linked to an Accounting event (accounting_event_ID)
Steps to reproduce:
- Log into Oracle Applications using a Payavbles responsibility.
- Open the Standard Request Submission screen
(N) Other > Requests > Run - Query/Submit "Create Accounting" process to try to account the voided payment.
- Wait until completed and review the output.
FND Debug Log of attempting Create Accounting for Check ID 1682559 and Invoice ID 1420394, shows the following messages:
LOG_SEQ. MODULE LVL MESSAGE_TEXT --------- ----------------------------------------------------------- --- ------------------------------------------------------------------
306513220 xla.plsql.xla_accounting_err_pkg.build_message 2 BEGIN of procedure BUILD_MESSAGE 306513217 xla.plsql.xla_je_validation_pkg.balance_by_ledger_currency 3 g_sla_bal_by_ledger_curr_flag = N 306513218 xla.plsql.xla_je_validation_pkg.balance_by_ledger_currency 3 BEGIN LOOP - balance by ledger currency 306513219 xla.plsql.xla_je_validation_pkg.balance_by_ledger_currency 3 LOOP - balance by ledger currency: ae_header_id = 41326656 306513221 xla.plsql.xla_accounting_err_pkg.build_message 2 p_appli_s_name = XLA 306513222 xla.plsql.xla_accounting_err_pkg.build_message 2 p_msg_name = XLA_AP_UNBAL_BASE_AMT 306513223 xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_1 = PROD_RULE_NAME 306513224 xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_1 = PAS En Base a Devengado 306513225 xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_2 = OWNER 306513226 xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_2 = User 306513227 xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_3 = EVENT_CLASS_NAME 306513228 xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_3 = Payments 306513229 xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_4 = EVENT_TYPE_NAME 306513230 xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_4 = Payment Created 306513231 xla.plsql.xla_accounting_err_pkg.build_message 2 p_entity_id = 10195721 306513232 xla.plsql.xla_accounting_err_pkg.build_message 2 p_event_id = 10300044 306513233 xla.plsql.xla_accounting_err_pkg.build_message 2 p_ledger_id = 2205 306513234 xla.plsql.xla_accounting_err_pkg.build_message 2 p_ae_header_id = 41326656 306513235 xla.plsql.xla_accounting_err_pkg.build_message 2 p_ae_line_num = 306513236 xla.plsql.xla_accounting_err_pkg.build_message 2 p_accounting_batch_id = 306513237 xla.plsql.xla_accounting_err_pkg.stack_error 2 BEGIN of procedure STACK_ERROR 306513238 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_appli_s_name = XLA 306513239 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_msg_name = XLA_AP_UNBAL_BASE_AMT 306513240 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_entity_id = 10195721 306513241 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_event_id = 10300044 306513242 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ledger_id = 2205 306513243 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ae_header_id = 41326656 306513244 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ae_line_num = 306513245 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_accounting_batch_id = 306513246 xla.plsql.xla_accounting_err_pkg.stack_error 1 l_msg_number = 95340 306513247 xla.plsql.xla_accounting_err_pkg.stack_error 2 END of procedure STACK_ERROR 306513248 xla.plsql.xla_accounting_err_pkg.build_message 2 END of procedure BUILD_MESSAGE 306513249 xla.plsql.xla_je_validation_pkg.balance_by_ledger_currency 3 LOOP - balance by ledger currency: ae_header_id = 41326665 306513250 xla.plsql.xla_accounting_err_pkg.build_message 2 BEGIN of procedure BUILD_MESSAGE 306513251 xla.plsql.xla_accounting_err_pkg.build_message 2 p_appli_s_name = XLA 306513252 xla.plsql.xla_accounting_err_pkg.build_message 2 p_msg_name = XLA_AP_UNBAL_BASE_AMT 306513253 xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_1 = PROD_RULE_NAME 306513254 xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_1 = PAS En Base a Devengado 306513255 xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_2 = OWNER 306513256 xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_2 = User 306513257 xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_3 = EVENT_CLASS_NAME 306513258 xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_3 = Payments 306513259 xla.plsql.xla_accounting_err_pkg.build_message 2 p_token_4 = EVENT_TYPE_NAME 306513260 xla.plsql.xla_accounting_err_pkg.build_message 2 p_value_4 = Payment Cancelled 306513264 xla.plsql.xla_accounting_err_pkg.build_message 2 p_ae_header_id = 41326665 306513261 xla.plsql.xla_accounting_err_pkg.build_message 2 p_entity_id = 10195721 306513262 xla.plsql.xla_accounting_err_pkg.build_message 2 p_event_id = 10336129 306513263 xla.plsql.xla_accounting_err_pkg.build_message 2 p_ledger_id = 2205 306513265 xla.plsql.xla_accounting_err_pkg.build_message 2 p_ae_line_num = 306513266 xla.plsql.xla_accounting_err_pkg.build_message 2 p_accounting_batch_id = 306513267 xla.plsql.xla_accounting_err_pkg.stack_error 2 BEGIN of procedure STACK_ERROR 306513268 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_appli_s_name = XLA 306513269 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_msg_name = XLA_AP_UNBAL_BASE_AMT 306513270 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_entity_id = 10195721 306513271 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_event_id = 10336129 306513272 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ledger_id = 2205 306513273 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ae_header_id = 41326665 306513274 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_ae_line_num = 306513275 xla.plsql.xla_accounting_err_pkg.stack_error 2 p_accounting_batch_id = 306513276 xla.plsql.xla_accounting_err_pkg.stack_error 1 l_msg_number = 95340 306513277 xla.plsql.xla_accounting_err_pkg.stack_error 2 END of procedure STACK_ERROR 306513278 xla.plsql.xla_accounting_err_pkg.build_message 2 END of procedure BUILD_MESSAGE 306513279 xla.plsql.xla_je_validation_pkg.balance_by_ledger_currency 3 END LOOP - balance by ledger currency 306513280 xla.plsql.xla_je_validation_pkg.balance_by_ledger_currency 2 End of function balance_by_ledger_curr 306513281 xla.plsql.xla_je_validation_pkg.balance_by_ledger 2 Value of profile XLA_CUSTOM_BAL_JOURNALS
Notice the XLA_AP_UNBAL_BASE_AMT accounting Error for ae_header_id = 41326665. The same appears for ae_header_ids = 41326656 , 41326662, 41326667
ALL four(4) linked to the same Entity ID 10195721, and two(2) DISTINCT Ledgers 2208 and 2205, as follow:
* Event_id 10336129 - Ledger_id 2208 :: AE_Header_ID = 41326667
* Event_id 10336129 - Ledger_id 2205 :: AE_Header_ID = 41326665
* Event_id 10300044 - Ledger_id 2208 :: AE_Header_ID = 41326662
* Event_id 10300044 - Ledger_id 2205 :: AE_Header_ID = 41326656
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 |
Data-Corruption |
Code-Bug |
Solution |
Code-Fix |
Data-Fix |
References |