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

Similar Messages

  • 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.

  • 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.

  • Down payment & BAPI_ACC_DOCUMENT_POST

    May be someone knows the decision of the problem:
    At dialogue creation down payment (F-48), the system creates communications between the purchasing order and the accounting document.
    I.e. in history of a position of the purchasing order there is a record with number accounting the document.
    And in the accounting document down payment there is a reference to number of the purchasing order in a browser of relations (look FB03 it is cluck in the menu: Environment-> Document Environment-> relationship Browser).
    I use ' BAPI_ACC_DOCUMENT_POST ' for creation down payment:
    As a result I receive the normal document of down payment, but links on the purchasing order it was not created, i.e. there is no record with number of the accounting document in history of a position of the purchasing order, and there is no reference to the purchasing order in a browser of relations of the accounting document.
    Is it possible to create the high-grade document down payment with all references what is at dialogue work of transaction F-48? What I for this purpose should make?
    Edited by: Soloviev Ivan on Apr 1, 2008 1:46 AM

    Hi,
    Just wait for a moment(10 to 15  mins) since you have given WAIT in BAPI_TRANSACTION_COMMIT.
    Check again, and hope it updates the values.
    or else, Just give BAPI_TRANSACTION_COMMIT after the BAPI with no parameters.
    Regards,
    Anbalagan

  • Down payment request: posting using BAPI_ACC_DOCUMENT_POST

    Hello, Gurus!
    We have a problem with posting DPR using BAPI.
    We can't carry out DPR for a Vendor.
    The following parametrs were set:
    1) BSTAT = 'S'
    2) ZUMSK = 'A'
    3) BSCHL = '39' 
    4) SHKZG = 'H' 
    5) WRBTR (negative sum is written)
    6) GLVOR (business transaction) - RFBU
    7) we also set assignment to a Funds reservation document.
    When we try to execute BAPI it returns an error RE 041 "Amount in document &1 &2 may not be exceeded".
    Perhaps, FM-PSM thinks that we try post a credit memo...
    We used F-47 before, but we need to use the BAPI.

    Hi,
    I had the same problem with posting a down payment request using BAPI. Actually, it seems SAP does not allow to post this kind of document "natively". Therefore, you have to implement a BADI (ACC_DOCUMENT) in order to make it work.
    1. Be sure you have the latest notes applied for BAPI_ACC_DOCUMENT_POST (especially note 561175)
    2. As for as DP request, call BAPI with DOCUMENTHEADER, ACCOUNTRECEIVABLE and CURRENCYAMOUNT filled with your needed lines.
    In my case, I set SP_GL_IND to 'F'.
    3. In your implementation of BADI, in method CHANGE, set ACCIT-BSTAT to 'S' (noted items) so that balance check will not take it into account. You may customize your line if needed.
    This should be enough to have your document posted. I can give you more details should you need help.

  • Down payment request for assets using bapi_acc_document_post

    Hi guys(girls)!,
    I<< priority reduced >>
    I'm posting a down payment request to an asset with a z program using bapi_acc_document_post. Everything is fine, but, when i go to fb03 to check the generated document i don't see the asset number associated to the purchase doc. When i go to bseg to check, i don't see the asset number and the subnumber. I lack just these to fields even i'm passing the values to correct fields in bapiacgl09.
    This is the values i'm passing:
    wa_acctgl-itemno_acc  =  iterator.
    wa_acctgl-gl_account  =  lv_skont.
    wa_acctgl-vendor_no   =  p_vendor.
    wa_acctgl-doc_type    =  p_tipdoc.
    wa_acctgl-item_text   =  p_txtcab.
    wa_acctgl-po_number   =  p_ponum.
    wa_acctgl-po_item     =  s_ekpo-ebelp.
    wa_acctgl-serial_no   =  imp_no.
    wa_acctgl-asset_no    =  wa_ekkn-anln1.
    wa_acctgl-sub_number  =  wa_ekkn-anln2.
    wa_acctgl-acct_type   =  'A'.
    wa_acctgl-CS_TRANS_T  =  '100'.
    wa_acctgl-asval_date  =  sy-datum.
    APPEND wa_acctgl      TO gt_acctgl.
    CLEAR wa_acctgl.
    Please help!.
    Edited by: Rob Burbank on Oct 24, 2011 9:44 AM
    Edited by: ramvargash on Oct 25, 2011 2:54 PM

    Hi Eduardo, what i'm trying to do is a down payment request for an asset. Indeed, i do the post. My problem is that the asset main number and the asset subnumber are not getting saved in bseg, so when i go to fb03 and double click on a line item, i got prompt to fb03 in visualize mode, and the fixed asset field is blank.
    I have now a week trying to get the asset main number and the asset subnumber getting saved in bseg. I note that i have other field that are not getting saved 'cause i'm not passing the value thru the bapi. This field is LNRAN.
    If you or anybody have a clue how to solve this, i would appreciate the help.
    Ramón Vargas

  • Creating Down Payment Request using BAPI_ACC_DOCUMENT_POST (URGENT!!)

    Hi...
    I have a posting unanswered.
    Please take some care about it... ^^
    Making Down Payment Request using BAPI_ACC_DOCUMENT_POST

    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.

  • Idoc for Down payment - SAP FI

    HI Experts,
    I need to create Customer/Vendor down payments in SAP FI through an Inbound Idoc. Data would be comming from theLegacy.
    Could you please suggest the Idoc or any BAPI available to post the Downpayment.
    <<text removed - do not offer points>>
    Thanks.
    Ramana
    Edited by: Matt on Nov 11, 2008 4:47 PM

    Ramana,
              You can used the Bapi 'BAPI_ACC_DOCUMENT_POST' or IDOC type FIDCMT01 to post your vendor documents.
    Sojan

  • BAPI or Function Module for F-47 (Down payment request)

    Hi All, I would like to know if there is a BAPI or FM to create F-47(Down payment request).
    I checked and noticed that BAPI_ACC_DOCUMENT_POST  is NOT working for this.
    We have BDC way of doing this but it is causing issues with COMMIT sometimes.
    Please advice.

    Hi Eswar,
    BAPI_ACC_DOCUMENT_POST  works only for 2 line postings. But we can make it work for one line by implementing BTERWBAPI01.
    Here you will be passing ACCHD-GLVOR = RFST
    ACCIT-BSTAT = S
    ACCIT-BSCHL = 39
    ACCIT-UMSKZ = F
    ACCIT-ZUMSK = Z
    could you please share the code that you have implemented in BTE?
    please share the sample code that you have done for BAPI.Because I also have the same requirement for f-47.
    Regards,
    xavier.P

  • Bapi for  'post customer down payment (t-code F-29)'

    hi all
    can any one tell which bapi is used to 'post customer down payment:header data (t-code F-29)'.
    thanks in advance,
    lokesh

    Hi,
    this one :
    BAPI_ACC_DOCUMENT_POST
    Best regards,
    Erwan

  • Vendor Down Payment Clearing: F-54 or F-44

    Hi
    I have made a down payment (with Spl. GL indicator) to a vendor, using F-48. Then I book an invoice using FB60. I kept the two amounts same and ignored WT to keep things simple.
    Now i want to clear the down payment against the invoice. I use F-54. The clearing transaction is getting posted. However, the Invoice is lying open (credit entry) along with the Clearing document (debit entry). On the other hand the down payment document (debit) is getting cleared with the Clearing document (credit entry). This means I have two open line items and two cleared line items. I can clear the two open items again using F-44.
    I have two questions:
    1. What is the use of F-54 here since I have to use F-44 eventually?
    2. While doing F-54, Posting Key for the debit line item is 26 : Payment Difference. This is could not understand.
    Can anyone please help me out on this?
    Thanks in advance
    Aninda

    Dear Aninda ,
    I will explain you with following example.
    Recon account(Vendor)---3000000
    Advance to Vendor----
    4005000
    Exp a/c----
    7575100
    Bank a/c----
    5000100
    1. Advance to Vendor (spl gl -A)(F-48)
    Vendor a/c    (SPL-A)( GL- 4005000)        DR   1000
                      T0  Bank a/c (GL-5000100)                  1000
    2. Invoice posting
    Expenditure a/c ( GL-7575100) Dr      1000
         To  Vendor Account(GL-3000000)     1000
    3. Clear Vendor Down Payment (F-54)     
    Vendor  a/c (GL-3000000) DR                1000 (Posting key-26)
         To Vendor a/c (SPL-A)( GL- 4005000)          1000
    It means  Credited spl GL-A has converted from advance to Normal open item. Amount has been transferred from Advance to Vendor GL to Normal Recon account.By this way Advance account shows Nil  Balance with debit(F-48) and Credit (F-54)
    The remaining 2 line items i.e., Credit (F-43) and Debit (F-54) shows as open items. In the next step we need to knock off those line items by manual clearing or automatic clearing.
    4. Normal Clearing (F-44)
    It will be posted without line items.
    I hope i am able to help you out to understand process

  • 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 While Posting the Asset Down Payment

    Dear Members,
    When I am doing Asset down payment through F-48, I am getting the following error.
    Before that I would like to inform you that I created 2 GL Accounts. i.e. Down Payments on Assets ( Recon A/c Assets )  and Second GL A/c is Asset Clearing A/c ( With out Recon A/c ).
    Further I assigned in T. Code -   AO90, I assigned the Down Payments on Assets GL A/c and In Clearing column I assigned the Asset Clearing A/c.
    Even though it is giving the following error.
    Item category 07000 not allowed in accounting transaction 1000/0001
    Message no. GLT2001
    Diagnosis
    The online document splitting is active in your system. Here, each document is assigned to a accounting transaction variant and each document row to an item category.
    You determine for each business transaction variant which item categories can or must be posted here.
    The following error occurred for the document you entered:
    Item category 07000 in accounting transaction 1000, variant 0001 is not allowed.
    System Response
    The document cannot be posted.
    Procedure
    Check the document entered, the derivation of the business transaction variant, the derivation of the item category, and the assignment of the item categories to the business transaction variant.
    do the needful at the earliest.
    Thanking You
    Regards
    K. S. Kumar

    Hi Sai Kumar,
    Go to Document splitting node..
    And check against the doc type that you are using in F-48, what business transaction variant is assigned in Classify document types for Document Splitting.
    next go to the following node....
    Doc Splitting->Extended Doc Splitting-> Define Business Transaction variants
    and select your business transaction variant as defined above and copy that and give it a name Z001,
    now select Z001 and double click on Assigned Item categories.., then select new entries and add 07000 Asset there and save.. it will give a warning message but just go on saving.
    next go to the node Classify document types for Document Splitting again and enter this Business transaction variant againt the document type that u r using in F-48. AND it will work.
    Regards,
    SAPFICO

  • Error -Account 'Down-payments clearing account' could not be found for area

    When I am trying to pass a down payment entry by debiting vedor and crediting bank with asset it is giving an error as follows.
    Account 'Down-payments clearing account' could not be found for area 01
    Message no. AU133
    Please help me to rectify the same.
    Thanks in advance
    Deepak

    HI
    Please pay attention at  the possible causes of message AU133:
    1. Error AU133:
       a) You have not defined a contra account for acquisition value postings in the Asset Accounting Customizing settings (Transaction AO90).However, this is required as of Release 4.6C because, as is the case for all other integration postings in Asset Accounting, invoice receipt postings have to be displayed in Asset Accounting via the new posting kernel to ensure an identical document
    structure.
       b) You have defined the account in Asset Accounting, however, it is not created in the affected company code.Check whether the account is correct and create it for the company code, if necessary.
    2. You have entered an asset reconciliation account for the "Contra account: Acquisition value posting" (for example, the same account as for   "Acquisition:Acquis. and production costs" account).This is not  permitted.Check whether your account determination is correct               
       (Transaction AO90) in Asset Accounting Customizing. The same applies
       for the 'Contra account: Down payment posting'.
    3. As "Contra account: Acquisition value posting" you entered an asset G/L account. If necessary change the automatic posting indicator in the G/L account master record.
    4.Check if you need  revaluation accounts in depreciation areas involved   (AO90):
      -Revaluation acquis. and production costs
      -Offsetting account: Revaluation APC
    Please run also programm RACKONTO where missing or wrong customizing
    the accoutn determinations per company code is displayed
    Also have a look at note 7595 in this regard.
    Please assign points if it useful.
    Regards
    Ravinagh Boni

  • Creation of A/R Down Payment Invoice  based on Sales Order not logical

    When creating a A/R Down Payment Invoice based on a Sales Order you
    have the option to create multible ones. Which by itself could be
    usefull to create one of 50 % for a certain day and decide they need to
    pay another 25 % at a later date.
    But SBO does not track what already have been posted. Therefore you can
    create a sum more then a 100% without warning or blockage.
    Tested this in SBO 2007 A SP:00 PL:00
    Scenario:
    Sales - AR>Sales Order
    Create and post a Sales Order
    Sales - AR>A/R Down Payment Invoice
    Create an A/R Down Payment
    Select the BP and copy the Sales Order
    Set DPM to 40%
    Post the A/R Down Payment
    Sales - AR>A/R Down Payment Invoice
    Create an A/R Down Payment
    Select the BP and copy the Sales Order
    Set DPM to 100%
    Post the A/R Down Payment
    Sales - AR>A/R Down Payment Invoice
    Create an A/R Down Payment
    Select the BP and copy the Sales Order
    Set DPM to 70%
    Post the A/R Down Payment
    Making the total for the Sales Order 210% worth of Down Payment
    Invoices without warning/blocking. I would expected that you would only
    be able to set the rest sum %. For instance first scenario I entered
    60% therefore setting the second Down Payment Invoice to a max of 40%
    Untill you have used up the 100% and you cannot select the Sales Order
    in question..
    If multible users do the same work, SBO doesn't show that it has
    already been done. Same if you forgot you already created it you can
    still create one. Plus sometimes it will happenyou create the Down
    Payment Invoice and not paying attention you create the first one with
    a 100% and later with the intended percentage..

    Hello Petronella,
    you are right that B1 is not checking the total value of DP created from the Sales Order.
    The logic and checking procedure here is only between Sales Order -> Delivery/Invoice.
    DP Invoice is considered as transaction related to document the receipt of the money (parallel to the sales process). Between the moment of basing of DP to Sales Order it is still possibility to adjust Sales Order as there is no posting behind Sales Order.
    The question is what would be a checking  procedure in case that on Sales Order there is based Delivery and DP? What would be the system priority to take into a consideration?
    Regards,
    Martin Slavik
    Regional Solution Manager

Maybe you are looking for