Error: BAPI_ACC_DOCUMENT_POST in down payment

Hi,
I am using the BAPI_ACC_DOCUMENT_POST in down payment  for creating an down payment document.(Similar to F-47 transaction).
Here i am only filling the header and the vendor(ACCOUNTPAYABLE), currency(CURRENCYAMOUNT) structures...(With only one line item)..
I am getting an error: balance in transaction currency..
Can you help?
Regards
Shiva

Use this code might help you
    LOOP AT gt_data INTO gw_data.
      MOVE gw_data TO lw_data.
      AT NEW posnr.
        MOVE sy-tabix TO from_row.
        gw_header-comp_code = lw_data-bukrs.
        gw_header-doc_type  = lw_data-blart.
        gw_header-pstng_date = lw_data-budat.
        gw_header-doc_date = lw_data-bldat.
        gw_header-username = sy-uname.
        gw_header-bus_act  = 'RFBU'.
        gw_header-ref_doc_no = lw_data-xblnr.
        gw_header-header_txt = lw_data-bktxt.
      ENDAT.
      MOVE sy-tabix TO to_row.
      APPEND lw_data TO lt_errdata.
      gw_acgl-itemno_acc = gw_acgl-itemno_acc + 1.
      IF gw_data-koart = 'C'.
        gw_acre-itemno_acc = gw_acgl-itemno_acc.
        WRITE gw_data-hkont TO gw_acre-customer.
        gw_acre-comp_code = lw_data-bukrs.
        gw_acre-bus_area    = gw_data-gsber.
        gw_acre-item_text  = gw_data-sgtxt.
        gw_acre-alloc_nmbr  = gw_data-zuonr.
        gw_acre-tax_code    = gw_data-mwskz.
        APPEND gw_acre TO gt_acre.
      ELSEIF gw_data-koart = 'V'.
        gw_acpa-itemno_acc = gw_acgl-itemno_acc.
        WRITE gw_data-hkont TO gw_acpa-vendor_no.
        gw_acpa-comp_code = lw_data-bukrs.
        gw_acpa-bus_area    = gw_data-gsber.
        gw_acpa-item_text  = gw_data-sgtxt.
        gw_acpa-alloc_nmbr  = gw_data-zuonr.
        gw_acpa-tax_code    = gw_data-mwskz.
        APPEND gw_acpa TO gt_acpa.
      ELSEIF gw_data-koart = 'G'.
        WRITE gw_data-hkont TO gw_acgl-gl_account.
        gw_acgl-bus_area    = gw_data-gsber.
        IF gw_data-kostl IS INITIAL.
          CLEAR gw_acgl-costcenter.
        ELSE.
          WRITE gw_data-kostl TO gw_acgl-costcenter.
        ENDIF.
        gw_acgl-tax_code    = gw_data-mwskz.
        gw_acgl-orderid     = gw_data-vbel2.
        IF gw_data-projk IS INITIAL.
          CLEAR gw_acgl-wbs_element.
        ELSE.
          gw_acgl-wbs_element = gw_data-projk.
        ENDIF.
        gw_acgl-item_text  = gw_data-sgtxt.
        gw_acgl-alloc_nmbr  = gw_data-zuonr.
        APPEND gw_acgl TO gt_acgl.
      ENDIF.
      gw_amt-itemno_acc = gw_acgl-itemno_acc.
      gw_amt-currency   = gw_data-waers.
      gw_amt-amt_doccur = gw_data-wrbtr.
      gw_amt-amt_base   = gw_data-wmwst.
      APPEND gw_amt TO gt_amt.
        CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
          EXPORTING
            documentheader    = gw_header
          TABLES
            accountgl         = gt_acgl
            accountreceivable = gt_acre
            accountpayable    = gt_acpa
            currencyamount    = gt_amt
            return            = gt_ret.

Similar Messages

  • 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

  • Error when posting Down payment with reference to down payment request

    Hi Experts,
    In October of 2010 we upgraded from version SAP 4.7 to version 604 SAPKH60406.  
    With this upgrade we decided to select the following FM setting:
    "Flag to activate down payment request update to PO history"
    If this flag is set, down payment requests are updated to the purchase order history. In addition, when you create a down payment referencing this down payment request , the down payment request is cleared by the down payment.
    Use- Set this flag if you want to see the down payment requests  in the purchase order history.
    So, since October 2010, the Down payment requests have been updated to the PO history (note - no update of the down payment request was made to the PO status tab) and the down payments (made with reference to the down payment request) have been clearing the DP requests.
    Today we have applied packages SAPKH60407 - SAPKH60409 and we are in the process of testing. 
    Now we are experiencing errors when processing down payments:
    1. create the down payment request (F-47) - this is OK
    2. create the down payment (F-48) with reference to the down payment request - ERROR MESSAGE F5373 - "Order value will be exceeded"
    Can anyone please explain why this is happening?  We would like to keep the "Flag to activate DPR update to PO history" ON
    as it has been since October 2010.
    Thanks,
    Michelle

    Hi,
    Please find the below link it will help full for you,........
    Order Value will be exceeded Msg No. F5373
    Naresh

  • BAPI_ACC_DOCUMENT_POST in down payment

    Hi!
      When i create a Purchase order i have to make an automatic down payment request (F-47), i'm working with an user exit that calls the BAPI_ACC_DOCUMENT_POST bapi from the PO transaction. Anybody have a code example on how to use this bapi with this scenario?. I made a local program to test the bapi with this call:
          CALL FUNCTION 'BAPI_ACC_DOCUMENT_CHECK'
            EXPORTING
              DOCUMENTHEADER          = WA_DOCHEAD
            CUSTOMERCPD             =
            CONTRACTHEADER          =
            TABLES
            ACCOUNTGL               =
            ACCOUNTRECEIVABLE       =
              ACCOUNTPAYABLE          = IT_VENDOR
            ACCOUNTTAX              =
              CURRENCYAMOUNT          = IT_CURRENCY
            CRITERIA                =
            VALUEFIELD              =
            EXTENSION1              =
              RETURN                  = IT_RETURN
            PAYMENTCARD             =
            CONTRACTITEM            =
            EXTENSION2              =
            REALESTATE              =
    The IT_RETURN itab from BAPI_ACC_DOCUMENT_CHECK returns "Document check - no errors" .
    the IT_RETURN itab from BAPI_ACC_DOCUMENT_POST returns
    "Document posted successfully"
    But no document had been posted! i look at the BKPF itab and nothing was created.
    Please help.
    Thanks in advance.
    John.

    Hi Rishi !
       I am using the bapi commit. here's the test code:
    *& Report  YPRUEBA_BAPI_DOCUMENT_POST                                  *
    REPORT  YPRUEBA_BAPI_DOCUMENT_POST              .
    *     ************* LLENAR ESTRUCTURAS BAPI ****************************
          DATA: WA_DOCHEAD      TYPE BAPIACHE09,
                IT_ACCOUNT      TYPE TABLE OF BAPIACGL09,
                WA_ACCOUNT      TYPE BAPIACGL09,
                IT_CURRENCY     TYPE TABLE OF BAPIACCR09,
                WA_CURRENCY     TYPE BAPIACCR09,
                IT_VENDOR       TYPE TABLE OF BAPIACAP09,
                WA_VENDOR       TYPE BAPIACAP09,
                IT_RETURN       TYPE TABLE OF BAPIRET2,
                WA_RETURN       TYPE BAPIRET2,
                WA_CRITERIA     TYPE BAPIACKEC9,
                WA_CURRENCY_EXT TYPE P DECIMALS 2.
          DATA: KEY(19)         TYPE C.
          DATA: COMMIT_RET      TYPE BAPIRET2.
          REFRESH: IT_ACCOUNT,
                   IT_CURRENCY,
                   IT_RETURN.
          CLEAR:   WA_DOCHEAD,
                   WA_ACCOUNT,
                   WA_CURRENCY,
                   WA_RETURN,
                   WA_CRITERIA,
                   WA_CURRENCY_EXT.
    *     FILL KEY FIELD
          KEY = '0000000000'.
          KEY+11(4) = '2000'.
          KEY+15(4) = '2005'.
          WA_DOCHEAD-USERNAME   = SY-UNAME.
          WA_DOCHEAD-OBJ_TYPE   = 'IDOC'.
          WA_DOCHEAD-OBJ_KEY    = KEY.
          WA_DOCHEAD-OBJ_SYS    = 'Z220'.
          WA_DOCHEAD-COMP_CODE  = '2000'. "SOCIEDAD
          WA_DOCHEAD-DOC_DATE   = SY-DATUM.
          WA_DOCHEAD-PSTNG_DATE = SY-DATUM.
          WA_DOCHEAD-TRANS_DATE = SY-DATUM.
          WA_DOCHEAD-DOC_TYPE   = 'KA'.
          WA_DOCHEAD-BUS_ACT    = 'RFBU'.
          CONCATENATE 'Solicitud de anticipo. Fecha:' SY-DATUM
                                              INTO WA_DOCHEAD-HEADER_TXT.
    *      WA_ACCOUNT-TAX_CODE   = 'C3'.
    *      WA_ACCOUNT-ACCT_TYPE  = 'K'.
    *      WA_ACCOUNT-ITEMNO_ACC = '0000000010'.
    *      WA_ACCOUNT-GL_ACCOUNT = '1121501001'.
    *      WA_ACCOUNT-VALUE_DATE = SY-DATUM.
    *      WA_ACCOUNT-CUSTOMER   = '2000015'.
    *      WA_ACCOUNT-ITEM_TEXT  = 'Posición anticipo'.
    *      WA_ACCOUNT-DOC_TYPE   = 'KA'.
    *      WA_ACCOUNT-COMP_CODE  = '2000'.
    *      WA_ACCOUNT-PSTNG_DATE = SY-DATUM.
    *      WA_ACCOUNT-COSTCENTER = SPACE.
    *      WA_ACCOUNT-ALLOC_NMBR = 'Nº asignación'.
    *      WA_ACCOUNT-PROFIT_CTR = SPACE.
    *      WA_ACCOUNT-ORDERID    = SPACE.
    *      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    *           EXPORTING
    *             INPUT  = WA_ACCOUNT-CUSTOMER
    *           IMPORTING
    *             OUTPUT = WA_ACCOUNT-CUSTOMER.
    *      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    *           EXPORTING
    *             INPUT  = WA_ACCOUNT-GL_ACCOUNT
    *           IMPORTING
    *             OUTPUT = WA_ACCOUNT-GL_ACCOUNT.
    *      APPEND WA_ACCOUNT TO IT_ACCOUNT.
    *      CLEAR  WA_ACCOUNT.
          WA_CURRENCY-ITEMNO_ACC   = '0000000010'.
          WA_CURRENCY-CURR_TYPE    = '00'.
          WA_CURRENCY-CURRENCY     = 'USD'.
    *     WA_CURRENCY-AMT_DOCCUR   = '150000.00'.
          WA_CURRENCY-AMT_BASE     = '15000.00'.
          APPEND WA_CURRENCY TO IT_CURRENCY.
          CLEAR WA_CURRENCY.
          WA_VENDOR-ITEMNO_ACC   = '0000000010'.
          WA_VENDOR-VENDOR_NO    = '2000015'.
          WA_VENDOR-SP_GL_IND    = 'A'.
    *      WA_VENDOR-TAX_CODE     = 'C3'.
          WA_VENDOR-COMP_CODE    = '2000'.
          WA_VENDOR-GL_ACCOUNT   = '1121501001'.
          WA_VENDOR-BLINE_DATE   = '20050510'.
          WA_VENDOR-PYMT_AMT     = '150000.00'.
          WA_VENDOR-PYMT_CUR     = 'VEB'.
    *      WA_VENDOR-PYMT_CUR_ISO = 'VEB'.
          WA_VENDOR-PMNTTRMS     = 'Z001'.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
               EXPORTING
                 INPUT  = WA_VENDOR-GL_ACCOUNT
               IMPORTING
                 OUTPUT = WA_VENDOR-GL_ACCOUNT.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
               EXPORTING
                 INPUT  = WA_VENDOR-VENDOR_NO
               IMPORTING
                 OUTPUT = WA_VENDOR-VENDOR_NO.
          APPEND WA_VENDOR TO IT_VENDOR.
          CLEAR WA_VENDOR.
    *     PROBAMOS LA BAPI
          REFRESH IT_RETURN.
          CLEAR   WA_RETURN.
          CALL FUNCTION 'BAPI_ACC_DOCUMENT_CHECK'
            EXPORTING
              DOCUMENTHEADER          = WA_DOCHEAD
    *         CUSTOMERCPD             =
    *         CONTRACTHEADER          =
            TABLES
    *         ACCOUNTGL               =
    *         ACCOUNTRECEIVABLE       =
              ACCOUNTPAYABLE          = IT_VENDOR
    *         ACCOUNTTAX              =
              CURRENCYAMOUNT          = IT_CURRENCY
    *         CRITERIA                =
    *         VALUEFIELD              =
    *         EXTENSION1              =
              RETURN                  = IT_RETURN
    *         PAYMENTCARD             =
    *         CONTRACTITEM            =
    *         EXTENSION2              =
    *         REALESTATE              =
    *     Se leen los resultados del posteo
    *     el mensaje S RW 614 indica que el chequeo fue exitoso
          READ TABLE it_return INTO wa_return WITH KEY type    = 'S'
                                                         id      = 'RW'
                                                         number  = '614'.
          IF SY-SUBRC = 0.
             REFRESH IT_RETURN.
             CLEAR   WA_RETURN.
             CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
               EXPORTING
                 DOCUMENTHEADER          =  WA_DOCHEAD
    *            CUSTOMERCPD             =
    *            CONTRACTHEADER          =
    *          IMPORTING
    *            OBJ_TYPE                =
    *            OBJ_KEY                 =
    *            OBJ_SYS                 =
               TABLES
    *            ACCOUNTGL               =
    *            ACCOUNTRECEIVABLE       =
                 ACCOUNTPAYABLE          =  IT_VENDOR
    *            ACCOUNTTAX              =
                 CURRENCYAMOUNT          =  IT_CURRENCY
    *            CRITERIA                =
    *            VALUEFIELD              =
    *            EXTENSION1              =
                 RETURN                  =  IT_RETURN
    *            PAYMENTCARD             =
    *            CONTRACTITEM            =
    *            EXTENSION2              =
    *            REALESTATE              =
    *        Se leen los resultados del posteo
    *        el mensaje S RW 605 indica que el POST fue exitoso
             READ TABLE it_return INTO wa_return WITH KEY type      = 'S'
                                                            id      = 'RW'
                                                            number  = '605'.
             IF SY-SUBRC = 0.
                CLEAR COMMIT_RET.
                CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
                 EXPORTING
                   WAIT          = 'X'
                 IMPORTING
                   RETURN        =  COMMIT_RET
             ELSE.
                MESSAGE S162(00) WITH 'Error en el Posteo'.
             ENDIF.
          ELSE.
             MESSAGE S162(00) WITH 'Error en el chequeo'.
          ENDIF.
    Code Formatted by: Alvaro Tejada Galindo on Jan 8, 2009 10:24 AM

  • CO Object Assignment Error while posting Down Payment Request

    User is raising a Down Payment Request for the purchase of an Asset  through a Purchasing Document. This Asset Master has got the cost center and WBS Element assigned in it.
    System while saving the DP Request is throwing an error that “CO Account Assignments has different Profit Centers”
    I have also checked the cost center master but the profit center assigned there is correct only. Should I check the OKB9 settings ? If yes, for which GL Account do I need to check ? Where else can I check the CO Object Assignments for profit centers ?
    Requirement is critical. Please help.
    Thank you
    Ravi
    9849393564

    Hi,
    Good evening and greetings,
    Please have a look in GGB1 (Profit Centre Substitution), there may be some rule which is overriding the OKB9.
    Please reward points if found useful.
    Thanking you,
    With kindest regards,
    Ramesh Padmanabhan

  • Error message in down payment on asset purchase order

    Hello,,
    While i am trying to make down payment request with reference to PO have asset number it is return an error message
    *Store a cost element for credit down payments
        Message no. KI165
    Diagnosis
        You posted a payment to a CO-relevant object (cost center, order, and so
        on). The payment is therefore recorded in CO.
        If a payment has no order reference, no consumption account can be
        derived. Therefore, CO posts the payment under a default cost element
        created and stored during Customizing.
        You have not yet maintained this default in the system.
    Procedure
        Maintain the default cost and revenue elements in the Implementation
        Guide under "Project System" for controlling area CA00.*
    I don`t know what is the reason for using this cost element and which type of cost elements that i can use in this issue....
    We are not use Down payment clearing account, because Our customer don`t need this account..
    Please help me ASAP
    Thanks for your cooperation
    Hussein

    Hello Hussein,
    For error message KI165,please maintanin default cost  element in OKEP.Down payments have to be posted in CO with cost   elements. In case of purchase orders (or open items in CO), the cost  element for consumption can be derived from the purchase order. Thus the  down payment in CO is posted with the consumption cost element.                                                                               
    If the  down payment does not have any reference to a purchase order, then the cost element for which the consumption will be posted is not known.  In this case, the cost element maintained with OKEP is used.                     
    The error message KI165 will occur if no cost element is maintained with  OKEP - not regarding whether the actual down payment has a reference to  a purchase order and thus will update in CO under the consumption cost element derived from the purchase order.  This is always a  source of  misunderstanding - but I hope it is clear now.                                                                               
    OKEP configuration is absolutely necessary if you do not have  a cost element assigned at the time of downpayment request creation.                                                                               
    If after maintaining the default cost element you get some other error  then please note that you would need to check the following :                                                                               
    1.Compare the configuration settings for the GL accounts that are  used for posting the cash call in EHP4 system with the system without the EHP4 support pack.               
    2.Check the controlling area settings in both the systems.        
    Regards Bernhard

  • 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

  • Payment run error:Only clear down payment requests individually :DEFTAX 012

    Hi ,
    In the payment run, I get the error as "Only clear down payment requests individually"
    The error code is DEFTAX 012 . What is the reason and solution. It seems to be a downpayment.
    Please suggest the needful.
    Regards
    Rudra

    Check any of the following notes whether it helps you.
    1)  Note 1127049 - New deferred tax: DEFTAX025 when posting down payment clr.
    2)  Note 1154793 - Def.Tax: No Amounts in Local Currency; Wrong Amount Diff.
    3)  Note 1160939 - Deferred Tax: Error DEFTAX(023) for Payment of 2 DP Requests
    thanks
    G. Lakshmipathi

  • Error in Vendor Down payment F-48

    Hello,
    I got an error message during posting Vendor down payment in F-48:
    " Balancing field "Profit Center" in line item 003 not filled. The field Profit Center marked as balancing is not filled with any value in line item 003, even after document splitting. "
    I'm using vendor down payment using VAT code.
    I think it's related to document splitting customizing.
    Can someone help me on this ?
    Thanks in advance
    Tarek

    Hi
    The Concept of Document Splitting is that you must use same Profit Center in all the line items of an Document.
    Not only in Down Payments , in Invoices also or in any document entry.
    i will give you 1 example, suppose an Invoice is there,
    31 Vendor 10000
    40 expense g/l a/c 5000 x1(x1 iscost center , profit center in x1 is x)
    40 expense g/l a/c 2000 x2(x2 is cost center , profit center in x2 is x)
    40 expense g/l a/c 3000 x3(x3 is cost center , profit center in x3 is x)
    If you give different cost centers , but they are also having different profit centers , then the total amount should be written on which profit center? this is logic , which profit center it will pick?
    Regards
    venkat

  • Error in Customer down payment clearing

    Hello Friends,
    I am trying to clear the customer down payment through transaction f-39.
    We have also created one validation rule that reference 3 field is mandatory so i am  getting error that reference field is mandatory.
    But reference field becomes gray so i cannot enter anything and cannot deactivate validation rule.
    I can enter value in reference field of remaining line item but not able to enter only in one line item i.e. customer lint item.
    Please tel me the solution to overcome this problem.
    Thanks In advance
    Regards,
    Reva Naik

    Hi ,
    If the reference field is gray,then the value fetch automatically.
    check the validation and down payment document if any reference field is there...
    If it is fill and save the document.
    Regards
    Surya

  • Withholding Tax Error during Vendor Down Payment

    Hi,
    We have created some new Withholding Tax Types and codes and have assigned them to a Vendor. Now when we try to make a down payment on this Vendor, at the time of posting the system gives the error:
    "WCT Code not allowed in Down Payment. Remove the WCT Code."
    We are using the newly created Withholding Tax code, so how and why is the system taking it as WCT?
    Please help.
    Thanks!
    Regards,
    Angad Nagpal

    Hi
    First create withholding tax types for Payment Posting and withholding tax codes and while assigning withholding tax types and codes in Vendor Master Data , only assign withholding tax types and select Liable checkbox and do not assign withholding tax codes.
    while doing Down payments or Invoices system will prompt a pop-up box and you can select the relevant tax codes.
    Then you can check whether it is calculating the taxes or not.
    Regards
    Venkat

  • Budget exceeded error when reversing down payment request via FB08

    Hi Experts,
          I am trying to reverse a down payment request via FB08 but unfortunately its throwing a budget exceeded error, is this normal behaviour?
    Regards,
    Lewis

    Hi,
    Please find the below link it will help full for you,........
    Order Value will be exceeded Msg No. F5373
    Naresh

  • Withholding Tax Calculation Error for Vendor Down Payment Clearing:Oct '09

    Hi,
    We are trying to incorporate the new Withholding Tax Structure w.e.f. 01-Oct-09.
    There were 3 scenarios possible:
    a. Invoice = Down Payment
    b. Invoice < Down Payment
    c. Invoice > Down Payment
    While 1 & 2 were taken care of effectively, the third scenario did not work as expected. The scenario is as follows:
    1. Down Payment (Date : 30/09/09)
    Amt : Rs. 40000/-;
    Withholding Tax @ 15% : Rs. 6000/- (40000 * 15%)
    Surcharge @ 10% : Rs. 600/- (6000 * 10%)
    Edu Cess @ 2% : Rs. 132 (Rs. 6600*2%)
    Higher Edu Cess @ 1% : Rs. 66 (Rs. 6600*2%)
    2. Invoice (Date : 02/09/09) - As per new TDS Rates
    Amt : Rs. 50000/-
    Withholding Tax @ 10% : Rs. 5000/- (50000 * 10%)
    Surcharge : NIL
    Edu Cess : NIL
    Higher Edu Cess : NIL
    3. DPC (Date : 02/09/09) - Reversal of TDS calculated in Down Payment (Step 1) above.
    Issue:
    While making J1INCHLN, amount is adjusted as Rs. -1000/- (hence zero) not payable.
    Also, the Surcharge, Edu Cess & Higher Edu Cess are also getting reversed in DPC.
    As suggested by SAP Note No. 1372734 - Handling of downpayment clearing scenarios after budget '09, the scenario does not seem to work.
    Actual payable should be worked out as under:
    Invoice : Rs. 50,000/-
    DP : Rs. 40,000/-
    Bal : Rs. 10,000/-
    TDS @ 10% : Rs. 1,000/-
    All TDS Challans, Certificates & Returns must reflect Rs. 1000/- in the Challan.
    Require assistance.
    Regards,
    Kapil Tilwani

    Hi Kapil,
    The following needs to be taken care of  -
    The message controls settings as the note suggests must be set as W.
    When entering the details the logic is Vendor Debit amount is Tax amount + 1
    The Vendor credit line, the tax code has to be assigned with the advance amount (amount for which the challan has been created) as the tax base amount and the tax amount will be the extra liability that needs to be created.
    In your example -
    The tax amount will be - 2000 ( the debit at the time of downpayment clearing should have been 4000 instead of 6000)
    Tax base amount -  40000 (Challan for this amount has already been made at the time of downpayment made)
    The vendor Debit - 2001 (2000 + 1)
    The vendor credit - 1
    Note - Tax amount and base amount has to be made manually in the withholding Tax tab for the credit entry.
    Please revert for any clarification.
    Thanks and Regards,
    Anit

  • Error during Vendor down payment f-48

    hi
    When i doing vendor down payment by F-48 and i enter bank services charges than this msg display.Can anybody telll me what the solution for it?
    Acct determination not defined for trans. BSP   in chart of accts CHPL
    Thanks
    Rekha

    Hi Rekha,
    Please check the following customizing
    1. Go to FBKP
    2. Click on Automatic Posting
    3. Now click on Bank transaction
    4. Double click on BSP and assign the GL Account for Bank Charges
    Hope above should work
    Regards,
    Jigar

  • Making Down Payment Request using BAPI_ACC_DOCUMENT_POST

    Hi, all...
    I faced a problem while I'm testing BAPI_ACC_DOCUMENT_POST to make down payment request(F-47), so I need some help.
    I've found a BAPI_ACC_DOCUMENT_POST in down payment about this topic and followed its parameter settings except for currency settings.
    In that posting, the accountpayable-pymt_cur and currencyamount-currency are set different currency.
    While I set the two fields with same currency(USD). Belows are my source codes.
      DOCUMENTHEADER-OBJ_TYPE   = 'IDOC'.
      DOCUMENTHEADER-OBJ_KEY    = '$'.
      DOCUMENTHEADER-OBJ_SYS    = 'D10CLNT200'.
      DOCUMENTHEADER-BUS_ACT    = 'RFBU'.
      DOCUMENTHEADER-USERNAME   = SY-UNAME.
      DOCUMENTHEADER-HEADER_TXT = 'DOWN PAYMENT REQUEST'.
      DOCUMENTHEADER-COMP_CODE  = '1000'.
      DOCUMENTHEADER-DOC_DATE   = '2006.09.01'.
      DOCUMENTHEADER-PSTNG_DATE = '2006.09.01'.
      DOCUMENTHEADER-DOC_TYPE   = 'KG'.
      ACCOUNTPAYABLE-ITEMNO_ACC    = '0000000001'.
      ACCOUNTPAYABLE-VENDOR_NO     = '0002314908'.
      ACCOUNTPAYABLE-GL_ACCOUNT    = '0091120100'.
      ACCOUNTPAYABLE-COMP_CODE     = '1000'.
      ACCOUNTPAYABLE-PYMT_METH     = 'L'.
      ACCOUNTPAYABLE-PMNT_BLOCK    = 'A'.
      ACCOUNTPAYABLE-BUSINESSPLACE = '1001'.
      ACCOUNTPAYABLE-PYMT_CUR      = 'USD'.
      ACCOUNTPAYABLE-PYMT_AMT      = '123,438.0000'.
      ACCOUNTPAYABLE-SP_GL_IND     = '2'.
      ACCOUNTPAYABLE-TAX_CODE      = 'RR'.
      CURRENCYAMOUNT-ITEMNO_ACC = '0000000001'.
      CURRENCYAMOUNT-CURRENCY   = 'USD'.
      CURRENCYAMOUNT-AMT_DOCCUR = '123,438.0000'.
    But the function returns an error:
    'Enter a payment currency different to USD'
    But if I would set with different currencies, it returns an error:
    'Balance in transaction currency'
    If the ACCOUNTPAYABLE-PYMT_CUR and ACCOUNTPAYABLE-PYMT_AMT were remained empty, it returns
    'Balance in transaction currency'
    What should I do about this currency setting.
    Someone please let me know about doing this right way.
    Thank you.
    Message was edited by: Jong-woon Lee

    Hi,
    Just in case you found this thread with the same problem.
    At least in my case what was happening is that I wanted to leave the currency fields blank (the same currency as payment value) but I was filling in ACCOUNTPAYABLE-PYMT_AMT, so was receiving error telling me that currency fields could not be empty. And if I set them to the same as payment, I would receive a message telling me that currency must be different.
    If you want to use only one currency you don't need to fill in these 3 fields:
    ACCOUNTPAYABLE-PYMT_AMT
    ACCOUNTPAYABLE-PYMT_CUR
    ACCOUNTPAYABLE-PYMT_CUR_ISO
    The same probably applies for the ACCOUNTRECEIVABLE table.
    Cheers,
    Erick
    Ps.
    Some extra text so you can find this thread by searching for error messages:
    Required field CURRENCY was not transferred in parameter ACCOUNTPAYABLE
    For the ISO code  there is no unique SAP currency code for ALE
    For the ISO code  there is no unique SAP currency code for ALE
        Message no. B1888
    Diagnosis
        There are several entries in TCURC for this ISO code, but none with the
        primary flag set.
    Procedure
        In table TCURC set the primary flag for ISO codes used multiple times.
    Required field CURRENCY was not transferred in parameter ACCOUNTPAYABLE
        Message no. RW602
    Diagnosis
        Field CURRENCY is required in parameter ACCOUNTPAYABLE for processing
        the document. The document is incomplete without this field.
    System Response
        The document cannot be processed.
    Procedure
        Enter a valid value in field CURRENCY in parameter ACCOUNTPAYABLE.

Maybe you are looking for