Error- while depositeing incomming payment.

Dear Friends,
Problem :
1)We have done Incomming payment.
2)We have deposited check thriugh deposite window upto 1/12/2009.
3)But 2/12/2009 onwards, if we are going to deposite checks which
are made through incomming payment. We are facing following error.
"This entry all ready done in table deposite ODPS"
Bur if we ckeck that incomming payment amount is still 'Db' at
Advance payment adjustment account ,means not deposited to Bank.
Why this happened? what is its solution.?
BR,
Mahesh.

Hi
I think u should not use The Restoring option,if u want to use that then u have to raise the ticket to SAP then after their reply only u have to use that option... .
Whether it was hapeening to all customers r only to particular customers, then check  whether the customer ref no is more than 39character in invoice.
Restore you db in demo db and test whether it was happening same or not... Also what is PL? & Version of SAP...
Giri

Similar Messages

  • Error while posting Incoming Payment.

    Hi
    I Got this error while posting Incoming Payment. What do this Error Mean. How to solve it.
    Error:
    SBO_Application_ItemEventAP Object reference not set to an instance of an object
    Thank You

    Hi Gayathri,
    Try to disconnect the add-ons if any and then add the incoming payment.
    Regards,
    Vijay kumar

  • Error while posting Incoming payments from customers

    Hi Experts,
                      when i am trying to post Incoming payments from customers in F-28,The payment difference amount is Rs 5.
    while simulating the following error 
    "TAX CODE C2 FOR COUNTRY IN HAS BEEN DELETED OR INCORRECTLY CHANGED"
    MESSAGE NO.FS201

    Hi,
    OBZT just controls the display of the various tax codes in the drop down list if MIRO/ FB60 etc.
    You need to maintain the atx coe correctly in FBZP. Go to FBZP and in this tax code and check whether the tax rates etc. have been defined correctly for it.
    Regards,
    SDNer

  • Error while posting Incoming payment Cancellation entry in Current date

    Hi Experts
    Scenario
    Incoming payenet created on 31-05-2009
    Cancellation to be done on current date - 02-06-2009
    Current period selected as 010609 to 300609 in general settings
    When Incoming payment is cancelled - The system shows message ' The selected period is locked, Posting will be created in Current period', Continue - ?
    When YES is clicked - 'Date deviates from permissible range - (Journal Entry - posting date) Msg - (173-11)
    Document Numbering Journal entry is for Current period. (All the Journal entries are getting posted in current date, hence Document numbering is correct for Journal entry)
    PLEASE NOTE - The cancellation entry is needed to be passed on system date (02-06-2009) and NOT original document date of incoming payment (31-05-2009)

    Hi Sundaraja
    In 2007 B this issue does not arise, working FINE
    In 2005 B, there is option to set period as Current which I have done. and Active 'YES' & Locked 'NO'. Infact I have done this for all the periods of yr 2009-10.
    Still getting the error.
    Regards,
    Sid

  • Error while opening Incoming Payments

    Dear all,
    I'm getting error called 'Linking Primary Sales Accounts has not been completed' when I open Incoming Payments.  Please advise how to rectify this error.
    Regards,
    Balaji

    Hiii Balji
        check this out , exact solution for ur question
    Error: Linking primary sales accounts has not been completed
                                                                               Good Luck
                                                                                    RIYAZ

  • Error while posting Down Payment

    Hi,
    I got error while posting down payment in F-48. the error was "Special G/L Indicator P is not defined for down payment".
    Thanks,

    Hello,
    "Special G/L Indicator P is not defined for down payment" because you have not maintained this indicator in your system. For maintain this you go to TC: OBYR, dbl down payment indicator P, , give your chart of accounts and press enter. Here you have to give normal Recon A/c and Alternative Recon A/c and save it. Now, go to TC: F-48 and you will able to post it now.
    Thanks
    Para

  • Encountered error while updating the payment document

    Hi Guys,
    I encountered an error while updating the payment document of one of our bank account. See below error message:
    Error: Unable to lock the record. Cause: The record is being modified by another user
    thanks,
    gracie

    Hi Vikas,
    Repeat the changes you are trying to make one step at a time and make sure you click on update in both the series screen and the document numbers screen every time.
    I've faced this issue and doing this helped.
    Regards,
    Hamsa

  • Error -2028 : No matching Record found while adding Incoming payment

    Hi all,
             I was trying  to add an Incoming Payment using DI API, checked both DocEntry and ChequeSum property..and all other properties and seems set as well, it would be better if you can give any solution.Thank you
    Regards
    Sijimon Sidharthan
    oPay.CardCode = oInvoice.CardCode;
                                       string sCardName=oInvoice.CardName;
                                  oPay.CardName = oInvoice.CardName;
                                  oPay.JournalRemarks = "820 Import Test" +  oInvoice.CardCode;
                                  oPay.ApplyVAT = SAPbobsCOM.BoYesNoEnum.tYES;
                                  oPay.CashSum = 189.77;
                                       int conP=oInvoice.ContactPersonCode;
                                  oPay.ContactPersonCode = oInvoice.ContactPersonCode;
                                       string cur =oInvoice.DocCurrency;
                                  oPay.DocCurrency = oInvoice.DocCurrency;
                                  oPay.DocDate = now;
                                  oPay.TaxDate = now;
                                  oPay.DocRate = 0;
                                  oPay.LocalCurrency = SAPbobsCOM.BoYesNoEnum.tYES;
                                  oPay.DocType = SAPbobsCOM.BoRcptTypes.rCustomer;//rAccount;
                                  oPay.HandWritten = SAPbobsCOM.BoYesNoEnum.tNO;
                                  oPay.Remarks = "remarks";
                                  oPay.Reference1 =iBaseRef.ToString();//"R";
    //                              oPay.TransferAccount = "10100";//OTRC doesn't contain any code
    //                              oPay.TransferDate = now;
    //                              oPay.TransferSum = 0;
                                  #region Invoice
                                  oPay.Invoices.AppliedFC = 0;
                                  oPay.Invoices.DocEntry = iBaseRef;//baseEntry;
                                       int ln=oPay.Invoices.LineNum ;
                                  oPay.Invoices.DocLine = 0;
                                  oPay.Invoices.InvoiceType = SAPbobsCOM.BoRcptInvTypes.it_Invoice;
                                  //oPay.Invoices.InvoiceType = SAPbobsCOM.BoRcptInvTypes.it_ChequesForPayment;
                                  oPay.Invoices.SumApplied = 189.77;//amount;
                                  oPay.Invoices.Add();
                                  #endregion Invoice
                                  #region Cheque
                                  oPay.Checks.BankCode ="026008866"; //"026002794";//"Leumi";
                                  oPay.Checks.CheckAccount="10200-00";//"10203";//-00";//"1HD";10203-00
                                  oPay.Checks.DueDate=Convert.ToDateTime("04/03/2007");
                                  oPay.Checks.CheckSum =189.77;
                                  oPay.Checks.CheckNumber = 12345678;
                                  oPay.Checks.Add();
                                  #endregion Cheque
    int ret=oPay.Add();
                                  if(ret!=0)
                                       int lErrCode; string sErrCode;
                                       oCompany.GetLastError(out lErrCode, out sErrCode);
                                       MessageBox.Show(ret.ToString ()+ sErrCode);

    Hi Lan,
              I tried to add IncomingPayment with another Database works fine with all these properties..think some extra settings may be there in the database now I'm working , do you have any idea regarding to solve this issue ..Thank you
    Regards
    Sijimon Sidharthan

  • Error while adding Incoming Excise Invoice

    Hi Experts,
    I am facing 1 problem while adding Incoming Excise Invoice & A/P invoice.
    The error msg is:-
    No matching records found  'G/L Accounts' (OACT) (ODBC -2028)  [Message 131-183]
    What might be reasons Vendor account is correctly defined.
    Regards-
    Mona

    Please check the following threads:
    GL Account missing in AR Credit Memo
    'No matching records found ' G/L account' (OACT) (ODBC - 2028) [Message 131
    Re: g/l account missing
    Re: G/L account is missing
    Thanks,
    Gordon

  • Document Split for Currency Exchange while posting Incoming payment

    Hi Experts,
    Scenario:
    > Post incoming Customer payments using F-28
    > posting entered today (14 Jan 2009), but posting date is 30 Dec 2008)
    > Tested in Clients 001 and 005 (same setup in terms of GLs, Customers, Vendors, etc)
    I was able to post the incoming payment in Client 005.  However, in Client 001, I got error message:
    *Ex.rate diff.accts are incomplete for account 0000140000 (Trade Debtors/Customers) currency SGD
    Message no. F5063
    Diagnosis
    The accounts for posting exchange rate differences could not be determined. For the specified G/L account and the specified currency key, the accounts are only specified incompletely. Either the accounts for the implemented exchange rate difference, the accounts for the valuation differences or the balance sheet adjustment account are missing.
    System Response
    The system cannot generate the exchange rate difference posting.
    Procedure
    By pressing ENTER, you achieve that the document is reset to a status without automatic posting. In another window, you can complete default settings for exchange rate differences and post the document afterwards.
    Proceed*
    When I clicked Proceed, the system took me to OBA1, with "Document Split for Currency Exchange" option highlighted in blue.
    Does this mean that I need to create a new GL account to post Document Split for Currency Exchange?
    Note: Setup for OBA1 both 001 and 005 are the same. But I only encountered the error in 001.
    Hope someone can help me.
    Thanks...

    problem solved: add relevant Open Item GLs in OBA1 (Account Determination for OI Exchange Rate Differences)

  • F-04 Section code error while full Down Payment Clearing

    Hi,
    I am facing a situation wherein suppose I have given an advance of INR 10,000 to an employee as Travel advance but due to some reason his trip got cancelled and the employee is refunding me the full advance. I am trying to clear that down payment of INR 10,000 through transaction code F-04 but I am getting an error and the system is asking to input Section code to proceed further but the Section code field is greyed out; I can see only Business Place coming automatically but not Section code. In this case ofcourse no invoice will be raised on the employee.
    I am facing the same problem if try to clear through F-54 without any invoice reference. But when I try to do a partial/residual clearing the system allows me to enter Section code and proceed with the clearing. I have created a validation for making Section code mandatory and am using Sets (t-code GS01) in my validaiton but i have not inputted clearing transaction codes in there.
    What I am unable to understand is why I am getting this error only while doing full clearing and without invoice reference. If there is something wrong with the validation I should get the same error while doing partial/residual clearing.
    Please help me out on this one.
    Thanks

    Hi
    In validation , you have to give TCODs in which both the field required to make mandatory. Otherwise it is applicable for every transaction of vendor.
    Make necessary changes in prequisits in validation.
    Thannks
    GG

  • Problem while making incoming  payment entries

    I am making check incoming payment entries in SAP-B1. As we receive check payment entries, it is crediting clearing check account & debiting account receivables.
    Please let us know how do  bank account will be credited & clearing check account will be debited.

    Hi........
    The entries are goming perfect. Actully in Incoming Payment there are two stage of entries.
    1. Incoming Payment from Customer where cheque receive
    2. Deposit in which check wil be deposited.
    So in first option Cheque will be debited and customer Account will be settled.
    in second step you have to deposit this cheque where Cheque account will be credited and deposit Bank will be  debited.
    This way your accounting happens and accounts for cheque will be settled.
    Hope this will clear the concept.
    Regards,
    Rahul

  • Error on creating Incoming Payment that links to another Incoming Payment

    Hi Experts,
    I am trying to create an Incoming Payment to pay an Invoice, as well as to use another Incoming Payment with an open balance (with Payment On Account box checked) to offset part of this payment.
    Conceptually...
    Incoming Payment A (-$75)
       --- link to Invoice B   ($85)
       --- link to Incoming Payment C  (-$10)
    This can be done manually, but by using DI API, I am facing this error:
    "-10: Base document card and target document card do not match.  (RCT2.DocLine)(line: 2)"
    Here is the source code:
    Dim oPayments As Payments = DirectCast(oCompany.GetBusinessObject(BoObjectTypes.oIncomingPayments), Payments)
    ' [HEADER]
    oPayments.CardCode = "C0001"
    oPayments.DocDate = Today
    oPayments.DocType = BoRcptTypes.rCustomer
    oPayments.CashSum = 0
    oPayments.BankChargeAmount = 0
    oPayments.TransferAccount = "12180208"
    oPayments.TransferDate = Today
    oPayments.TransferSum = 75
    oPayments.LocalCurrency = BoYesNoEnum.tYES
    ' [LINE 1 - AR Invoice B.]
    oPayments.Invoices.InvoiceType = BoRcptInvTypes.it_Invoice
    oPayments.Invoices.DocEntry = 16949
    oPayments.Invoices.SumApplied = 85
    ' [LINE 2 - Incoming Payment C with Open Balance.]
    oPayments.Invoices.Add()
    oPayments.Invoices.InvoiceType = BoRcptInvTypes.it_Receipt
    oPayments.Invoices.DocEntry = 20338           ' Journal Entry Number of the Incoming Payment
    oPayments.Invoices.SumApplied = -10
    If oPayments.Add() <> 0 Then
        oCompany.GetLastError(errCode, errMessage)
        BarError(String.Format("{0}: {1}", errCode, errMessage))
    Else
        BarSuccess("Success.")
    End If
    Initially I tried to set
    oPayments.Invoices.DocEntry
    with the Incoming Payment's DocEntry, but after trial and error, I realized I should be using the Incoming Payment's Journal Entry's Number instead. So this field should be correct. (If I were to use the Incoming Payment's DocEntry for this field, I get the "-2028: No matching records found (ODBC -2028)" error.)
    I have ensured that the Incoming Payment C's CardCode is the same as the one I set in
    oPayments.CardCode
    , so I'm not sure why it gives an error saying the document cards do not match. I would appreciate any form of help on this! Thanks!

    Hi,
    I am not trying to Pay to Account (you are referring to the top left radio button of the Incoming Payment right?). I am trying to create an Incoming Payment that uses another over-paid Incoming Payment (i.e. Open Balance > 0) to offset its Amount Due.
    Anyway I have found the solution to my problem. It seems that I need to also set the
    oPayments.Invoices.DocLine
    value to the over-paid Incoming Payment's Journal Entry's document line which contains the same business partner as my Incoming Payments. This DocLine value is usually 1 (0-based), as SAP usually creates the Journal Entry with the BP row in the second row.

  • DTW Error when importing Incoming Payments-Invoices (RCT2).

    Hi Experts,
    I have imported invoices through DTW and they currently have the status 'Open'. I have tried importing Incoming Payment records but DTW gives me the following error: 'Base document card and target document card do not match'.
    After importing the invoices i ran the query for OINV and used the Internal Number / DocEntry for these invoices, in the RCT 2 table. (I read some where that its this DocEntry that will link Invoices and Incoming Payments). I have filled the DocEntry field in both ORCT and RCT 2 templates but am still getting the same error.
    Kindly assist.
    David.

    Hi, any luck fixing this issue?
    Im dealing with the same problem here.
    Thanks,

  • Error message: Banking - Incoming Payments - Incoming Payments

    Hi, Experts,
    When I was trying to post a deposit (for an A/R Invoice) to the bank account. I click  'Banking - Incoming Payments - Incoming Payments'. But there is a error message saying 'Linking primary sales accounts has not been completed'.
    How to fix this problems? Thanks!
    Lorrie

    Hi,
    Check Note No. 871509 if the same applies to your case.
    Request you to kindly check the following :
    1. First define revenue account under administration->setup- >financial   ->G/L account determination -> sales tab and check whether the issue was solved or not.
    2. if the error still exists after step 1, you have to define all the
       other accounts that you have not defined previously. Then your
       issue might be resolved.
    Even if there are no bookings to go on a primary sales or purchase account, an account must be defined for SBO to work. Ideally, ALL sales, purchase and tax accounts should be defined. Once the account code is entered, the error message disappears and SBO works normally.
    Other possibility is that one of your primary accounts is defined
    as "confidential". (sales/purchase/Cash etc..)
    Hope it helps.
    Regards,
    Jitin

Maybe you are looking for