Tuesday, June 7, 2016

APP-SQLAP-10000: ORA-01403: no data found occurred in with parameters (Terms id = Seqiemce num =1)

Issue:

Unable to validate invoice where the item line has a withholding tax group due to:

APP-SQLAP-10000: ORA-01403: no data found occurred in
with parameters (Term id = Sequence num = 1) while performing the following operation: &DEBUG_INFO the following error occurs.



Solution:-

This error is caused because when the invoice is validated the system tries to create the automatic withholding invoice yet there is no Payment Term associated with the Supplier (Tax Authority) site. Since the invoice could not be created without this, the validation fails.

1. Navigate to Supplier form
Payables > Suppliers > Entry

2. Query the Supplier/Tax Authority linked to the withholding group on the problematic invoice
Click Update
Select the Key Payment Setup tab

3. Scroll to the Payment terms section and add a Payment Term to the Tax Authority for that Vendor Site.

4. Retest the issue


Wednesday, June 1, 2016

Check the opening and closing balances in the control totals

Issue: 

Check the opening and closing balances in the control totals.



Solution:


The Bank Statement Import program checks if the Control end balance matches:
(Control begin balance) + (Control cr amount) - (Control dr amount)

If not, it shows the warning, "Check the opening and closing balances in the control totals."

Here's the steps to address the warning:

Case 1:
Bank statement file does not provide the opening and closing balances and these optional fields are not populated.
So CONTROL_TOTAL_DR and CONTROL_TOTAL_CR are populated but not the begin and end balance.

Workaround:
Either null out the CONTROL TOTAL DR and CONTROL TOTAL CR, or populate begin and end balance for the Bank Statement Import Parameters.

Case 2:
CONTROL_BEGIN_BALANCE and CONTROL_END_BALANCE is populated but not CONTROL_TOTAL_DR and CONTROL_TOTAL_CR

The issue can occurr when there is a missing transaction code setup.

1 - With the Bank Statement in the Interface tables , navigate to the Bank Statement Interface form.

2 - Check the Bank Transaction Codes assigned to the Bank Statement Lines.

3 - Ensure Bank Transaction Codes identified on the Bank Statement are correctly setup in the system prior to importing the bank statement.

Please check the information from bank statement loader TDD:
-----------------------------------------------------------
After you load SWIFT940 bank statement files into the open interface tables,
you may need to define new bank transaction codes in Cash Management.
SWIFT940 transaction codes represent the type of transaction. For example,
TRF represents transfers. SWIFT940 transaction codes do not, however, contain
information about the debit or credit nature of the transaction. Instead,
the Debit/Credit Mark field is used to differentiate debit and credit
entries, where D means debit and C means credit. When the Bank Statement
Loader program populates the TRX_CODE column in the Bank Statement Lines
Interface table, it appends the Debit/Credit Mark to the transaction code to
form a new code. For example, debit transfers are identified as TRFD and
credit transfers as TRFC. You must set up these new transaction codes before
you can import the bank statement information.


4 - Once this is checked and corrected ( if required ), make a change to the Bank Statement in the Interface form and save.

5 - Now, try to import the Bank Statement.