Unable to Post accounting document(URGENT)

I am unable to push to accounting from the billing document. I created oreder with one line item and in delivery I entered text item, then I did billing but it is not posting to accounting by giving error message "Field Bus. Area is a required field for G/L account xyz 121000. Neither it is allowing to delete the particular text item in deliver nor it is allowing me to cancel the billing document in VF11 it is giving error message that Data inconsistency during processing of document and another error message is Cancellation document is not the same as the original billing doc. I checked everything is fine. How to rectify the error.

Hi
This problem can be solved in two way.
1. Go to T-Code FS00 Enter the G/L 121000 and enter the Company Code  Then Click on Display Mode..then In Create and Bank interest Tab find the Field Status Group.. Aftet that Go TO T-Code Select Field Status Variant as 0001 and click on Field status  Gropus and You will find field status group here.. then Double click on that Field status group.. There in Select Group you have Businees area which made and Mandatory entry .. Make that entry as optional and save it.. then do the billing .. 
OR
2. Go to T-Code OBY6 and double click on your company code .. in that screen you have business area financial statement screen which is checked.. you uncheck this one and save it.. then do the billing
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).
Enjoy Buddy...
Regards
MBS

Similar Messages

  • Unable to create Accounting document for my Outgoing excise Invoice

    Dear All,
    I am implementing sales from Factory. I am unable to creat accounting document for my Outgoing excise invoice.  When I click the Utilization button, The excise invoice type is selected Deemed.
    1. How to control which Which Excise invoice type should be selected in J1IIN.
    2. For Deemed exports will system not genererate Accounting document for Excise Invoice?
    3. Where to view the excise invoice document types (Like Billing and order types)
    Thanks & Regards

    For deemed export sales,
    -Accounting documents will not get generated. (ref: Excise Acct Determination in CIN settings, you will not find Excise Tranraction type:ARE3 for which G/L account will not be assigned)
    -Excise Invoice type will be automatically triggered based on configuration : Excise Group / Series Group detetermination.
    - For Deemed Exports , only Quantity will get updated in RG1, but not the value. thats the reason, accounting document will not get generated.
    - This excise invoice is created, for - to update the RG1 registry / ARE3 creation.
    hope it clears
    regards,

  • Not able to post accounting document from CRM to ECC.

    I am tring to post accounting document through BDOC but it is not posting . Can any one have idea how we can post accounting document to ECC from CRM with out use of Bdoc .  Thanks

    Hi,
    Check if any of the condition types which has the account is having a tax code.. That tax code shouldn't have defined as EC tax code.
    When you double click on the line item condition type which will be posted to accounts, you could see the G/L account and tax code. Ask you FI consultant to check how that tax code has been defined.
    Btw, it is always good if you open a new thread.. But you can refer the old thread inside your post.
    Regards, Sai Krishna.

  • Posting accounting documents into G/L accounts

    HI friends,
    what are the tables involved in posting accounting documents in G/L accounts.
    Please let me know.
    Thanks in advance.
    Roberts.K

    <b>Do check this out</b>
    http://www.erpgenie.com/abap/tables_fi.htm

  • Posting accounting documents in G/L accounts.

    HI friends,
    what are the tables involved in posting accounting documents in G/L accounts.
    Please let me know.
    Thanks in advance.
    Roberts.K

    Hi Roberts,
    BKPF and BSEG are your tables for the accounting documents.
    Regards,
    Srinivas

  • BTE while posting accounting document through MIRO

    Hi All,
    I am doing MIRO posting with PO,while MIRO posting accounting document is getting created for it.  I need a BTE while posting accounting document through MIRO to trigger workflow(through event).
    For direct accounting document posting I found the BTE 1030 to trigger workflow.
    Thanks
    Sree

    Hello !
          The BTE required is "00001120     DOCUMENT POSTING:  Field substitution header/items".
          Double click on this entry at FIBF transaction and you will find the function module SAMPLE_PROCESS_00001120
          Take a copy of this function module and go ahead.It is not possible to change the tables T_BKPF and T_BSEG. So, use the tables T_BKPFSUB and T_BSEGSUB.
    Regards,
    S.Suresh

  • Profit center change in posted accounting document

    Hello,
    please, is it possible to change the profit center in already posted accounting document?
    We DTO'd open customer balance with wrong profit center. PC document has been created as well. Please, what is the proper way to change the PC?? Or how to proceed?
    Thanks a lot
    Kind regards
    Marcela

    It is not possible to change profit center, for that matter any other CO assignment cannot be changed. You can try transfering to correct profit center through 9ke0

  • After post accounting document user cannot change Reference Field

    Hi,
    I have a issue. After post accounting document user cannot change Reference field value. Please suggest .     
    Thanks & Regards,
    Hemant Maurya

    Hi Hemanth,
    Mr. ajay's solution solve your issue.
    If you activate it will applicable to entaire client (it is not comp code specific)
    For Activation USe T.Code: OB32 maintain Field (BKPF-XBLNR), Account Type & Transaction Type Blank
    Remove Field Can be change Check Box
    Regards
    Viswa

  • Error in Posting Accounting Document from invoice

    Hi,
    When i create invoice, the system gives error while creating accounting document as,
    "Tax code Y1 does not appear in any G/L account item".
    In my pricing procedure. i have two tax condition types. MWST and ZSED (copy of mwst). when i delete ZSED from my pricing procedure and then i create a sales order/delivery & finally invoice...then it works fine (Accuonting document is created successfully).
    i have assigned the gl accounts in vkoa. and MWST & ZSED goes to same gl account via MWS accounting key.
    although i have searched the forum for this issue, but that didnt resolved my issue.
    seeking your guidance.

    Dear Robert,
    I'm having same issue as yours.
    The requirement for us is if return sales in some order reason codes, then tax should be posted to different G/L other than the G/L defined in OB40(transaction MWS).
    After several test, found the system only recognize the G/L in OB40, won't touch setting in VKOA. As if I delete the GL in table T030R, SAP will issue an error requesting GL assignment.
    Please let me know if you have solved your issue! If yes, please share your solution! 
    Thanks in advance!

  • Movement type 941 is not posting accounting document

    While postig post goods issue for replacement order no accounting document is being created, only PCA document is being created. Numbers are zero on PCAdocument, thats probably the reson whuy accounting document is not being generated. Is there any configuration that drives the passing of cost to FI?  I see that material is valued at 100 ncurrency units.

    Hello Pankaj,
    In OMJJ transaction, you can set customizing for movement type 941.
    If you want to create FI document when you post metarial document, you must set valuation update check in Account Grouping node on OMJJ customizing.
    Regards,
    Burak

  • BAPI_ACC_DOCUMENT_POST - Unable to create accounting document

    Hi All,
    I am trying to post a document using BAPI "BAPI_ACC_DOCUMENT_POST" and "BAPI_TRANSACTION_COMMIT " . On execution the following message is being displayed "                                                                   
    S RW  605 Document posted successfully: FKKSU $ I00CLT030 " .  But, I could not able to see the accounting document number generated in BKPF / BSEG table.
    Can any one of you help me in creating the accounting document number in BSEG / BKPF table using the above said BAPI. Is there any thing which needs to be maintained in customization?
    Thanks in advance.
    Sunil.K

    May be this is little late to answer .. but still it will be better for clarity.
    First of all accouting document will be generated only after commit of the BAPI i.e. call BAPI_TRANSACTION_COMMIT after  BAPI_ACC_DOCUMENT_POST.
    Second to check the accounting document number  generated from BAPI
    When filling the BAPI interface, leave the following fields empty if  the FI document number is to be the reference document number for  the posting:                                                                               
    o  DOCUMENTHEADER:                                OBJ_TYPE, OBJ_KEY and OBJ_SYS       
    o  DOCUMENTHEADER and ACCOUNTGL:   AC_DOC_NO                           
    o  ACCOUNT_GL:                                         STAT_CON, AC_DOC_NO 
    In the importing paramters
         IMPORTING
           obj_type          = l_type
           obj_key           = l_key
           obj_sys           = l_sys
    The first 10 character of l_key will contain the FI document number

  • Error in accounting document-urgent

    hi
    gurus
    iam working on ECC 6.0
    i have createe sales order , delivery and billing without taking tax conditions
    in this case accounting document is generated
    but when iam taking tax  conditions in my sale order and do the delivery and billing
    at the time of billing(in vfo1) , No accounting docuemnt is generated
    system show "error in accounting documents"
    pleae help
    thank in advance

    To resolve the error, you can analyze account determination in the billing document. Process:
    Goto T.Code: VF02 & Enter Invoice number
    Next (On the top most strip) goto Environment
    Next (Select Environment) go to Account determination
    Next (In Account Determination) select Revenue Account Determination (first option)
    This will list all the condition types in the Billing document & analyze each condition & check for which G/L accounts is not determined.
    Possible errors:
    1. VKOA not maintained for required combination
    Solution: Maintain the combination in VKOA.
    2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA).
    Solution:
    Option 1 (Standard solution):
    step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order
    step 2: Maintain Customer master / Material Master correctly.
    step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.
    Option 2:
    Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting.
    3. Account Key not maintained in Pricing Procedure:
    Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account.
    From FI Side, you require to check that all the G/L account has been maintained through T.Code: FS00. G/L account being Master data has to be created in each client ot uploaded through LSMW / SCATT / BDC.
    In Billing Document in change mode (in the first screen where we enter Billing Document number), on the top most left hand corner, take a dropdown on Billing Document & select Release to accounting. Here you can get the under mentioned possible message:
    1. G/L account not found
    2. Cost Element not maintained for G/L account.
    In both the above cases, FI consultant requires to take corrective action.
    Regards,
    Rajesh Banka
    Reward suitable points.
    How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

  • T. Code to view Purchase Order and posted Accounting Document

    Hi,
    Is there any single SAP standard T.Code from which I can get  Accounting Document(posted) and its Purchase Order No.
    Dont sent any Table name plz.
    Regards,
    Vivek Kumar

    Run Standard Reports with Scope of List : ALLES
    ME2M  Material Wise report
    ME2N  PO Number wise Report
    ME2L  Vendor Wise report
    You can also Check MB51 / MR51 Reports.
    Regards,
    Ashok

  • Example program - posting accounting document,  Idoc ( ACC_DOCUMENT )

    Hi fellows developers,
    here is an example of  usage of the IDOC, directly in program for an accounting document
    (ALE message type ACC_DOCUMENT, bapi BAPI_ACC_DOCUMENT_POST )).
    It was inspired  by the lack of a flexible usage of this IDOC in LSMW
    (f.e. booking of Gl and Vendor from the same file).
    Both cases inbound and outbound are covered, although the outbound idoc was delivered in state
    for furthere dispatching and was further not tested.
    You can adapt this example to any idoc type (bapi type) and load data from anywhere ( file, table, etc.).
    If you have question please ask.
    On my system works !!!:)))
    I hope it will help you in your daily work.
    Regards,
    Miroslaw
    *& Report  Z_MKPR87
    *& Version 1.0 - creates idoc for accounting document with status
    *&  64 - inbound and 30 - outbound.
    *& Then you need to execute program RBDAPP01 for this message type (inbound),
    *& for outbound further dispatching with appropriate tool is required (not tested here).
    *& For inbound, complete booking of document was tested. For outbound
    *& only to the stage 30 - 'Idoc ready for dispatch'.
    *& Program does not require any additional DDIC objects.
    *& The solution gives you possibility for example to book document G/L + Vendor items,
    *& strictly speaking the whole power of this bapi in IDOC can be used. Unfortunately
    *& in LSMW its not the case.:)
    *& Data for idoc is takken from internal table, but can be loaded from anywhere.
    REPORT  Z_MKPR87.
    INCLUDE Z_MKPPR87_TOP.
    INCLUDE Z_MKPPR87_SEL.
    INCLUDE Z_MKPPR87_EVN.
    INCLUDE Z_MKPPR87_IDOC.
    *&  Include           Z_MKPPR87_TOP
    CONSTANTS:
    input structure for idoc ***
    Achtung! don't use BAPI input structures
    they are similar but not flat ( the casting cannot occure, since idoc
    needs flat data - see 'sdata' field in edidd )
    gc_idoc_structure1(27) TYPE c VALUE 'E1BPACHE09',
    gc_idoc_structure2(27) TYPE c VALUE 'E1BPACGL09',
    gc_idoc_structure3(27) TYPE c VALUE 'E1BPACCR09'.
    Structrures for IDOC : ALE message type - ACC_DOCUMENT
                         BAPI - BAPI_ACC_DOCUMENT_POST
    NOTE!  The E1BPXXXXXX structures are flat (char type), opposite to
    BAPI structures (BAPIACHE09. etc. )
    DATA:      gs_DOCUMENTHEADER  TYPE E1BPACHE09,
                    gt_ACCOUNTGL  TYPE TABLE OF E1BPACGL09,
               gt_CURRENCYAMOUNT  TYPE TABLE OF E1BPACCR09,
                gt_idoc_str_names TYPE TABLE OF char15,
                     gs_edidc     LIKE edidc,
               gt_idoc_data TYPE  TABLE OF       edidd,
               gt_comm_idoc_control TYPE TABLE OF edidc.
    *&  Include           Z_MKPPR87_SEL
    SELECTION-SCREEN BEGIN OF BLOCK bk2 WITH FRAME TITLE text-002.
    PARAMETERS:
              p_itype TYPE char15 DEFAULT 'ACC_DOCUMENT03',
    *'CREMAS04',
              p_mtype TYPE EDIDC-mestyp  DEFAULT 'ACC_DOCUMENT',
              p_rport TYPE EDIDC-rcvpor DEFAULT 'LSMW',
              p_rtype TYPE EDIDC-rcvprt DEFAULT 'US',
              p_rname TYPE EDIDC-rcvprn  DEFAULT 'Z_MKARAS',
              p_inbd    TYPE c DEFAULT 'X'.  " C - inbound (2), space - outbound (1)
    SELECTION-SCREEN END OF BLOCK bk2.
    *&  Include           Z_MKPPR87_EVN
    INITIALIZATION.
    PERFORM initialize_idoc_const.
    START-OF-SELECTION.
    PERFORM create_idoc.
    *&  Include           Z_MKPPR87_IDOC
    *&      Form  create_idoc
          text
    FORM create_idoc.
      PERFORM set_bussines_data
                  USING
                     gs_documentheader
                     gt_accountgl
                     gt_currencyamount.
      PERFORM build_idoc_from_bus_dat
                  USING
                     gs_documentheader
                     gt_accountgl
                     gt_currencyamount
                  CHANGING
                     gt_idoc_data.
    CASE p_inbd.
    WHEN 'X'.
       PERFORM create_inbound_idoc.
    WHEN space.
       PERFORM create_outbound_idoc.
    ENDCASE.
    ENDFORM.                    "create_idoc
    *&      Form  create_inbound_idoc
          text
    FORM create_inbound_idoc.
      PERFORM set_idoc_control_inbound CHANGING gs_edidc.
      CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND'
        EXPORTING
          i_edidc = gs_edidc
        TABLES
          i_edidd = gt_idoc_data.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ELSE.
       MESSAGE 'Inbound idoc(s) created, check in TAC WE02' TYPE 'I'.
      ENDIF.
    ENDFORM.                    "create_inbound_idoc
    *&      Form  create_outbound_idoc
          text
    FORM create_outbound_idoc.
      PERFORM set_idoc_control_outbound   CHANGING   gs_edidc.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
          master_idoc_control        = gs_edidc
        TABLES
          communication_idoc_control = gt_comm_idoc_control
          master_idoc_data           = gt_idoc_data.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ELSE.
       MESSAGE 'Outbound idoc(s) created, check in TAC WE02' TYPE 'I'.
      ENDIF.
    ENDFORM.                    "create_outbound_idoc
    *&      Form  set_idoc_control_inbound
          text
         -->CT_EDIDC   text
    FORM set_idoc_control_inbound CHANGING cs_edidc LIKE gs_edidc.
      DATA: ls_edidc TYPE  edidc.
      cs_edidc-direct = '2'.
      cs_edidc-idoctp = p_itype.
      cs_edidc-mestyp = p_mtype.
      cs_edidc-rcvpor = 'SAPECI'.
      cs_edidc-rcvprt = p_rtype.
      cs_edidc-rcvprn = p_rname.
      cs_edidc-sndpor = p_rport.
      cs_edidc-sndprt = p_rtype.
      cs_edidc-sndprn = p_rname.
      cs_edidc-credat = sy-datum.
      cs_edidc-cretim = sy-uzeit.
    ENDFORM.                    "set_idoc_control
    *&      Form  set_idoc_control_outbound
          text
         -->CS_EDIDC   text
    FORM set_idoc_control_outbound CHANGING cs_edidc LIKE gs_edidc.
      DATA: ls_edidc TYPE  edidc.
      cs_edidc-direct = '1'.
      cs_edidc-idoctp = p_itype.
      cs_edidc-mestyp = p_mtype.
      cs_edidc-rcvpor = p_rport.
      cs_edidc-rcvprt = p_rtype.
      cs_edidc-rcvprn = p_rname.
      cs_edidc-sndpor = 'SAPECI'.
      cs_edidc-sndprt = p_rtype.
      cs_edidc-sndprn = p_rname.
      cs_edidc-credat = sy-datum.
      cs_edidc-cretim = sy-uzeit.
    ENDFORM.                    "set_idoc_control_outbound
    *&      Form  set_bussines_data
          text
         -->CS_DOCUMENTHEADER  text
         -->CT_ACCOUNTGL       text
         -->CT_CURRENCYAMOUNT  text
    FORM set_bussines_data USING cs_documentheader LIKE gs_documentheader
                                 ct_accountgl      LIKE gt_accountgl
                                 ct_currencyamount LIKE gt_currencyamount.
                            CHANGING ct_idoc_data LIKE edidd.
      DATA:
             ls_documentheader TYPE e1bpache09,
             ls_accountgl      LIKE LINE OF  gt_accountgl,
             ls_currencyamount LIKE LINE OF gt_currencyamount.
    HEADER **
      cs_documentheader-bus_act =  'RFBU'.
      cs_documentheader-username = 'RNOWAK'.
      cs_documentheader-comp_code = '1000'.
      cs_documentheader-doc_date = '20071205'.
      cs_documentheader-pstng_date = '20071205'.
      cs_documentheader-fisc_year =  '2007'.
      cs_documentheader-fis_period = '12'.
      cs_documentheader-doc_type = 'JE'.
    POSITIONS ***
    111111111 ****
      ls_accountgl-itemno_acc = '0000000001'.
      ls_accountgl-gl_account = '0000473110'.
      ls_accountgl-item_text = 'MIK test dokumentu GL z programu IUE'.
      ls_accountgl-comp_code = '1000'.
      ls_accountgl-tax_code = '0I'.
      ls_accountgl-costcenter = '0000001000'.
      ls_currencyamount-itemno_acc = '0000000001'.
      ls_currencyamount-currency = 'PLN'.
      ls_currencyamount-amt_doccur = '496'.
      APPEND ls_accountgl TO ct_accountgl.
      APPEND ls_currencyamount TO ct_currencyamount.
    2222222222 ****
      ls_accountgl-itemno_acc = '0000000002'.
      ls_accountgl-gl_account = '0000113302'.
      ls_accountgl-item_text = 'MIK test dokumentu GL z programu IUE'.
      ls_accountgl-comp_code = '1000'.
      ls_accountgl-tax_code = ''.
      ls_accountgl-costcenter = ''.
      ls_currencyamount-itemno_acc = '0000000002'.
      ls_currencyamount-currency = 'PLN'.
      ls_currencyamount-amt_doccur = '-496'.
      APPEND ls_accountgl TO ct_accountgl.
      APPEND ls_currencyamount TO ct_currencyamount.
    ENDFORM.                    "set_bussines_data
    *&      Form  build_idoc_from_bus_dat
          text
         -->IS_DOCUMENTHEADER  text
         -->IT_ACCOUNTGL       text
         -->IT_CURRENCYAMOUNT  text
         -->CT_IDOC_DATA       text
    FORM build_idoc_from_bus_dat USING is_documentheader LIKE gs_documentheader
                                            it_accountgl LIKE gt_accountgl
                                       it_currencyamount LIKE gt_currencyamount
                                   CHANGING ct_idoc_data LIKE gt_idoc_data.
      DATA:
      ls_documentheader LIKE is_documentheader,
      ls_accountgl     LIKE LINE OF it_accountgl ,
      ls_currencyamount LIKE LINE OF  it_currencyamount,
      ls_idoc_data LIKE LINE OF ct_idoc_data.
    Document header *****
      ls_documentheader = is_documentheader.
      ls_idoc_data-segnam = gc_idoc_structure1.
      ls_idoc_data-sdata = ls_documentheader.
      APPEND ls_idoc_data TO ct_idoc_data.
    Positions G/L part ************
      LOOP AT it_accountgl INTO ls_accountgl.
        ls_idoc_data-segnam = gc_idoc_structure2.
        ls_idoc_data-sdata = ls_accountgl.
        APPEND ls_idoc_data TO ct_idoc_data.
      ENDLOOP.
    Currency Items part ******
      LOOP AT  it_currencyamount INTO  ls_currencyamount.
        ls_idoc_data-segnam = gc_idoc_structure3.
        ls_idoc_data-sdata = ls_currencyamount.
        APPEND ls_idoc_data TO ct_idoc_data.
      ENDLOOP.
    ENDFORM.                    "build_idoc_from_bus_dat
    *&      Form  initialize_idoc_const
          text
    FORM initialize_idoc_const.
      APPEND gc_idoc_structure1 TO gt_idoc_str_names.
      APPEND gc_idoc_structure2 TO gt_idoc_str_names.
      APPEND gc_idoc_structure3 TO gt_idoc_str_names.
    ENDFORM.                    "initialize_idoc_const

    I summarized postings and posted again into the same system.  Yes, you can save an IDOC in your own system...There's an IDOC FM that will do just that...  In my case, I did:
    after receipt of IDOC and posting,
    process the idoc tables, rebuilding the input into tables.
    Summarize the tables, as needed.
    Create a new IDOC with a specific function code.
    Save the IDOC in my own system, using IDOC_INBOUND_ASYNCHRONOUS, as I recall.
    I had a custom process code that fired off the standard FM to process the JE posting.  I don't remember all the variables, but I have this stored as my example:
    DATA : p_sndprn TYPE edi_sndpn3.
    * Control Record Build.
      CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
        IMPORTING
          own_logical_system = p_sndprn
        EXCEPTIONS
          OTHERS             = 0.
      iedidc-direct   =  '2'.
      iedidc-idoctyp  =  'FIDCCP02'.
      iedidc-mestyp   =  'FIDCC2'.
      iedidc-mesfct   =  'ACC'.  <customer made up....used to control which process codes fire off when for standard message.
      iedidc-sndprt   =  'LS'.
      iedidc-sndprn   =   p_sndprn.
      iedidc-rcvprn   =   wa-rcvprn.
      iedidc-rcvprt   =  'LS'.
      iedidc-sndpor   =  'SAP_EDI_SC'.
      iedidc-credat   =  sy-datum.
      iedidc-cretim   =  sy-uzeit.
      APPEND iedidc.
    * IDOC store routine...must commit work
    * to get IDOC transferred to the IDOC processor.
      CALL FUNCTION 'IDOC_INBOUND_ASYNCHRONOUS'
        TABLES
          idoc_control_rec_40 = iedidc
          idoc_data_rec_40    = iedidd.
    ENDFORM.                    " send_idoc
    Edited by: DaveL on Oct 25, 2011 8:15 PM

  • Unable to Post FI Document through Billing Document in SD(For Credit Card)

    Hi Experts,
    I was able to successfully post FI document through Billing document in SD.
    The Problem is encountered when a Sales Order is created
    for Credit Card customers.
    When the sales order is created the credit card information we are prompted with an error message Payment terms is a required field for G/L Acc so and so...
    The payment terms field in the posting key 01 is marked required and the same field for the reconcilation account is optional. However this config has not created any problem for the Non credit card sales orders.
    If any one has faced the same problem. Please help me out in this issue. I have been working on this for a long time.
    Thanks for your help...
    Thanks,
    Chaitanya

    Hi Folks,
    Please refer SAP OSS Note 119047.
    In the OSS Note they have mentioned..
    Pass the payment terms to the field
    xaccit-zterm = '0001'. in the User Exit.
    Program : LV60BF0C,
    Customer Function ]002'.
    Include File ZXVVFU02.
    Still I don't understand why SAP doesn't support payment terms for Credit Card. But when a Sales Order is  created without credit card the field xaccit-zterm  has a value.
    Thanks,
    Chaitanya K

Maybe you are looking for