Skip to main content

Dear All,

Expect your valuable advice on this.

I have come across this error in the cash box payment. The below mentioned error appears when we try to approve the cash box payment.

As we investigate the issue further, the basic data were set accordingly and the there were no functional error with regards to the relevant transaction ID. And no customization done & this is standard IFS. Transaction Type -Direct Cash Payment

As we checked from the backend /sql  we found there is link with the mixed payment table. Hence, we had to do small data repair and proceed with the transaction. 

Refer the below sql query for further understanding. Expect your inputs whether this is bug or whether we can eliminate this error through functionally. 

 

CURSOR get_zero_payment_line IS
         SELECT t.party_type,t.lump_sum_trans_id,t.mixed_payment_ledger_trans_id
         FROM   MIXED_PAYMENT_LEDGER_TRANS_TAB t
         WHERE  t.company                          = '***'
         AND    t.mixed_payment_id                 = '29641'
         AND    NVL(t.curr_amount,0)               = 0
         AND    NVL(t.disc_curr_amount,0)          = 0
         AND    NVL(t.withheld_tax_curr_amount,0)  = 0
         AND    NVL(t.write_off_curr_amount,0)     = 0
         AND    NVL(Mixed_Payment_Deduct_Det_API.Get_Deduction_Amount(company,
                                                                      mixed_payment_id,
                                                                      lump_sum_trans_id,
                                                                      mixed_payment_ledger_trans_id),0) = 0
         AND   ( NVL(t.new_diff_item,'FALSE')      = 'TRUE'
                 OR NVL(Ledger_Item_API.Is_Invoice_Str(company,
                                                       t.identity,
                                                       Party_Type_API.Decode(t.party_type),
                                                       t.ledger_item_series_id,
                                                       t.ledger_item_id,
                                                       t.ledger_item_version),'FALSE') = 'TRUE');

 

 

Please advise.

Regards

Naadira

 

 

What is the transaction you are trying to process? In your screenshot there seems to be supplier payments as well. Cashbox does not allow 0 value transactions.

What is the transaction you are trying to process? In your screenshot there seems to be supplier payments as well. Cashbox does not allow 0 value transactions.

Dear Pamith,

Thank you for your response.

The transaction line is 21 & it has a value of 3800. It is a direct cash payment to the supplier petty cash payable. The petty cash reimbursement is done as a SUPOA through MSI and the expenses recorded in the cash box. The process is functionally correct. Our problem is this error appears when we approve the cash box. Which is linked to the mixed payment table.

 

 

 

Regards

Naadira

Okay, I am still confused here. So you created a SUPOA then matched it with an MSI which had the actual expense accounts, is this matching also in the cash box?

Since you are recording a direct cash payment, there cannot be any invoice involved, only the manual accounts, is that in balance?

Okay, I am still confused here. So you created a SUPOA then matched it with an MSI which had the actual expense accounts, is this matching also in the cash box?

Since you are recording a direct cash payment, there cannot be any invoice involved, only the manual accounts, is that in balance?

Dear Pamith,

 

Thank you for your reply.

I have explained about the business scenario. The supplier details and MSI details we retrieved from the debugging the error message. Which is not relevant for line 21. Line 21 error comes from the mixed payment table. which we had to do a data repair.

Yes direct cash payment method was manually matched against a GL a/c not with an MSI. You are correct. 

Our concern is why cash box generate an error while approving & when there is a cancelled mixed payment for the same date. Because from the back end we can see both there is a validation. You can refer the SQL query for more details.

 

Regards

Naadira

Reply


Terms & ConditionsCookie settings