Account determination procedure

What is account determination procedure KOFI00.

It is used in FI and SD integration.
When you post an invoice, for example, the system uses account determination types to locate the G/L accounts to which amounts should be posted. You can define G/L accounts in account determination tables in SD Customizing through Acct determination -> Environment -> Maintain acct determ. The system checks these tables according to the specified access sequence until it finds a valid account.

Similar Messages

  • Account Determination Procedure in Sales Order

    Hi All,
    I have a problem regarding account determination procedure in sales order.
    When I create a new sales document, and go to menu Environment --> Analysis --> Account Determination, the information about the procedure is blank.
    For your information, I already assign this sales document type to a billing type.
    This billing type also already has an account determination procedure, which is KOFI00.
    The G/L Account in VKOA also already been set up for the combination of Condition Type - Chart of Acct - Sales Org - Account Assignment Category in Customer and Material - Account Key.
    But every time I create a new sales order, I cannot get the account determination procedure.
    Anyone can please help me to solve this problem?
    Thank you in advance

    Hi Surya,
    Have you assigned Billing type For Ex: F2 or F1 to respective Sales Order Type in Sales Document Type controls VOV8.
    Assign these F2 against Delivery Related billing and F1 is for Order Related billing.
    Assign KOFI0000 to respective Billing Types F2 and F1.
    And check, hope issue may resolve.
    Revert if u have any query.
    Regards
    Durga sana.

  • Account determination procedure for cash billing & payment cards

    HI experts
    i want to know know what are the configuration steps of account determination procedure for cash billing & payment cards

    Hi Surya,
    Have you assigned Billing type For Ex: F2 or F1 to respective Sales Order Type in Sales Document Type controls VOV8.
    Assign these F2 against Delivery Related billing and F1 is for Order Related billing.
    Assign KOFI0000 to respective Billing Types F2 and F1.
    And check, hope issue may resolve.
    Revert if u have any query.
    Regards
    Durga sana.

  • GR/IR clearing account determination (procedure WRX)- IR before GR

    Hello SAP gurus!
    For a normal PO, when we do IR first, then GR, the posting of GR/IR clearing accounts are different. However, if we do the other way around, the accounts are the same.
    <b>How can we clear these 2 accounts in PBS now?</b>
    <b>Do we have solution to post in the same GL?</b>
    Please advice.
    Many thanks
    Robert

    well u need to test this in u rsanbox first to check the pros and cons but yes it can be done
    and as i understand that u wish to have different g/l for particular plant then you need to have different valuation grouping code for that plant and in the wrx key u need to activate the valuation grouping code thing for this key and there u need to maintain the valuation grouping code of all the palnts
    bu i doubt how far this will work cause u need to check if wrx is getting hit at gr or not and also check if invoiceing is happening correctly or not just make sure every thing works fine and test different scenerios for that

  • Why do you need Account Det. Procedure in GL Account Determination ..?

    Guys, I need following clarification for GL Account Determination....
    While doing "Revenue Account Determination", one has to do "Define and Assign Account Determination Procedure". Now what I understand that in Acc. Determination Procedure, you can add more than one "Account Determination Types", which basically (if fully implemented) will bring back (via access seq) more than one GL Accounts. My question is, can you post one particular pricing condition type, in one billing line of a specific billing document, to more than one Revenue GL Account in FI. If yes, what that scenario would be?
    I do understand that one can maintain just one Determination Type in each Acc Det Procedure, where you can have just one GL Account, however, since Procedure can handle more than one Determination Types (and hence GL Account), I was wondering that in which scenario it would fit.
    Thanks
    Edited by: SR on Jan 8, 2009 5:17 PM

    HI SR
    The major difference between the KOFI & KOFK condition types are as follows
    In standard accounting procedure there we have 2 condition types .They are as follows :
    condition type                  Reqt
    KOFI                               3
    KOFK                             2
    Usage of KOFI condition type
    We will be using KOFK for generating controlling document
    We wil be using KOFK when we go for Make to Order (MTO) process.
    If you want to assign the KOFK to generate controlling document then you should assign the cost center , to your G/L accounts also
    When the controlling document generate then for FI consultants it will be helpful to generate the report as per the requirement
    Usage of KOFI condition type
    We will be using KOFI for normal sales cycle only .
    So the Stock whatever we deliver it will be a Make to stock (MTS)
    Regards
    Srinath

  • Cash sales using Pricing procedure for account determination cash settl

    Hi all ,
    we are customizing for cash sales , we have defined all steps as per "cash account determination" in basic functions.but , system is posting again to customer account, i.e account receivable account.
    if we assing "EVV" accounting key in the field "Account key for cash allocation" of billing type ( bv-cash sales),and assigning GL account for account key "EVV" in VKOA,  it is working fine.
    if we want to post cash account using cash account determination pricing procedure i.e by assining pricing procedure in billing document type, it is not working. Is there any additional cusotmizing has to be done in addition to steps involved in "cash account determination of basic functions?
    can any one help on this?
    regs,
    ramesh

    Hi,
    thanq for your reply.
    we have used same document types mentioned by you. for the same only cash account determination given.
    if we remove revenue account determination procedure, system will not post accounting document, system will give message, this billing is not relevant for accounting.
    our aim is to post sale account, but instead of accounts receivables, it has to post to cash clearing account.
    so, we have assigned revenue account determination procedure ( for sales posting) and cash account determination procedure ( for cash clearing posting).
    you may be right, some where i missed some thing, which is not tracked by me. If you can give steps, at least I can check, same thing was customized or not.
    regs,
    ramesh

  • SD tax G/L account determination

    First, I am not a Finance person nor do I know a lot about tax configuration.  My background (relevant for this issue) is in S/D pricing and associated account determination.  This is an S/D tax calculation and account determination issue for the United States.
    I am attempting to generate a “use” tax in an internal service order and then to populate the correct G/L account(s) with these tax values.  The service order, which is really just a sales order,  generates a statistical value for the basis and then I have pricing condition types (condition class = “D” (“taxes”), condition category = “D” (“Tax”)) specified in the pricing procedure.  These “tax” condition types are correctly calculating the tax amount.
    Normally, to point to the correct G/L account for a pricing condition type, you would configure Account Determination within S/D.  The simplest form would be the usage of the account key.  The account key would be specified in the “AccKey” column and account determination configuration would point this key to the correct G/L account.
    I understand (both from my own very recent experience and also from some of the information I have read on the internet) that things might be a little bit different when determining a G/L account for tax.  Originally I specified two different account keys in the pricing procedure for the tax condition types (normally I would have specified just one).  I specified MW1 through MW4 in the account key column for all 4 tax condition types and MWS in the accrual column.  My intent was to update the tax expense account from MW1 – 4 and the tax accrual account from MWS (I realize I might have this backward).
    When I created a billing document, SAP would not create the accounting document.  It indicated (from my recollection) that it was missing a tax code for the G/L account for the first tax condition type (“YTX1”).  Cutting through the history, it appears that SAP needs this code to point to the correct G/L account for S/D.  I also learned that there is a tax code field in the tax condition record (VK11) where you specify this code.
    I am actually familiar with the configuration and setup for use tax for A/P vendor invoices.  I had to perform this  setup very recently.  In short, I know that the tax code determines what the tax rates will be and also determines the G/L accounts.  I know how to setup a situation for tax accrual (this is setup found in tax code U1).
    My questions are the following:
    1) Is it true that I have to use the tax code to determine the G/L accounts for taxes generated in an S/D pricing procedure?  Is it possible I am doing something wrong in the S/D account determination (at the moment, not quite sure what this would have been)?
    2) Is it possible that I am adversely affecting account determination by specifying an account key in the accrual column of the pricing procedure for the tax pricing condition types?
    3) If we do have to specify a tax code in the tax pricing condition records in order to use the FI tax procedure to point to the correct G/L account, do we also specify the tax rates in this FI tax code or do we still specify them in the S/D tax pricing condition records?  It does not make sense to have to specify these rates twice.  In short, what does SAP actually use for tax calculation?
    Thanks a lot – Ed Seigler

    Hello Edward,
    The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
    Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
    SAP supplies a tax calculation procedure for each country. The procedure comprises a list of all common tax types with rules for tax calculation.
    You have to define a separate  tax on sales/purchases code for each country in which one of your company codes is located. Each code contains one or more tax rates for the different tax types.
    Tax codes are actually configured in FI, but they play a significant role while creating tax condition records for a particular condition type.
    Account keys in the account determination procedure connect the condition types to the relevant GL accounts. It doesnt have any impact on tax calculation. Its a procedure that is purely used to map GL accounts to the condition types.
    Finally, i would suggest you to check at the condition record level, whether you have assigned the correct tax code to the appropriate condition type to rectify the error.
    <b>REWARD POINTS IF HELPFUL.</b>
    Regards
    Sai

  • Purpose of account determination in Sales Order

    Hi
    My question is whether account determination happens at Sales Order level and if yes what is the purpose. Since I saw account determination procedure only to be assigned at billing document type but not in sales document type.

    Hi,
    Dear.. It is very basics of accounting. Unless there is a give and take complete process in sales process, the cycle is not completed. So there is no need of accounting entry.
    Billing is the final documentation with regards to accounts to register who has sold what to whom (Debits and credits). In practicality unless the transaction is complete, there is no accounting entry, when you raise the sale order, it does not affect your accounts, unless you completely process through delivery and billing.
    Regards
    DSR

  • Account determination analysis in sales order

    Hi there,
    in a sales order processing (VA02/VA03) I'd like to know which accounts will be determined prior to invoincing it.
    I find the "account determination analysis" tool through the menù path: "Environment" -> "Analysis" -> "Account Determination" (FCODE = 'KTPR'), but it shows an empty screen
    The same tool shows the desired data during an invoice processing (VF02/VF03).
    How can do to see the account determination analysis in sales order processing, and not in invoice processing ?
    This tool shows an empty screen even if the order is invoiced, or not.
    So I'm asking: which is the meaning of this tool inside sales order processing ?
    Hope I've explained correctly my problem.
    Thanks in advance.
    Andrea

    Hi Nagaraj,
    the sales order amount is > 0, but the account determination analysis tool still show me an empty screen
    It seems this tool runs only into invoice processing.
    I try to follow the ABAP debugger and at a certain point it uses the "account determination procedure" (KOFI00), that in the sales order is missing ... maybe this is the problem ...
    Best regards
    Andrea

  • Analysis Account Determination

    Dear all,
    I am getting error in account determination in VF01 screen. After I create billing document, I go to VF02 to check revenue accounts.
    In the Analysis Account Determanation>Procedure:ZOFI00 there are two price conditions (ZN01 and ZN01).
    But there must be one price condition.    
    As a result there is a problem.
    How can I put only one pricing condition (ZN01) in the pricing procedure.
    Regards,

    That is Revenue Account determination procedure not Pricing procedure , Please post the error you are getting.
    Regards,
    Ramesh

  • Error in account determination: table T030K key 1000 MW1 Message no. FF709

    Dear Gurus
    We have activate automatic release to account at VF01 level. For one billing doc system is giving us error
    Error in account determination: table T030K key 1000 MW1Message no. FF709
    At Environment -> Act determination analysis  here the system is not giving any error. But accounting entries are not there and Excise accounting entries are generated and showing there.
    When we check at header level Header tab Accounting data block Posting status system is showing Error in Accounting Interface.
    We have assign MW1 accounting key for CST condition Type.
    Assignment in VKOA is also done.
    In OB40 tax code and the GL is also done.
    Reetesh NIgam

    hello, friend.
    when you configure account determination, you assign not only account assignment groups (customer, material) to GL accounts, you also need to make assignments for taxes, represented in SAP default by the posting key MWS.
    an example assignment in account determination, procedure 5 (General) would be as follow:
    Applic/Ty/Chart of Accts/Sales Org/Act Asg Grp/Act Asg Grp/Account key/GL accounts 
    V   KOFI   INT   1000   01   01   ERL   xxxxxx
    V   KOFI   INT   1000   01   01   ERS   xxxxxx
    V   KOFI   INT   1000   01   01   ERF   xxxxxx
    V   KOFI   INT   1000   01   01   MWS   xxxxxx
    please check if your tax condition type/s are included in your pricing procedure and have been defined in FI.
    regards.

  • Run Time Error in Account Determination

    Dear Friends
    In my system using std one for account det then it posting to FI.
    Now I created my own Table, Access Seq, Condition Type and Procedures after all assignment when I assign my procedures to F2 .
        Then I done sales cycle upto billing, but when I am trying to save it it shows Run time Error. if assigning the Std Procedure KOFI00  to F2 then it is ok.
    give me solution
    Thanking You
    Arun

    Dear Arun,
    Can you provide in detail !!
    What is the error you are getting when you save the invoice
    Check the settings at all these steps with compare to the standard setings.
    SPRO>IMG>Sales and Distribution>Basic Functions>Account Assignment/Costing-->Revenue Account Determination.
    -->Check Master Data Relevant For Account Assignment
    -->Define Dependencies Of Revenue Account Determination
    -->Define Access Sequences And Account Determination Types
    -->Define And Assign Account Determination Procedures
    -->Define And Assign Account Keys
    -->Assign G/L Accounts.
    I hope this will help you,
    Regards,
    Murali.

  • Document 510008000 saved (error in account determination).

    When I am creating credit memo System through error message Document 510008000 saved (error in account determination).
    What could be the reason..

    Hi Murali,
    This is related to account determination issue
    You have been saved the document but that value not transfereed to the G/L accounts(i.e Account document not created.
    To overcome this go to VKOA transaction do the revenue account determintion.
    Assign the account determination procedure to your billing document type in VOFA transaction.
    I hope it will help you,
    Regards,
    Murali.
    Edited by: Murali Mohan.Tallapaneni on May 30, 2008 11:26 AM

  • Account  determination-urgent

    hi
    how the account will post in GL account    during intercompany billing transaction, third party order, and STO.  very urgent. 
    please give me the answer
    regards
    murali

    Hi,
    Apart from the above information,i would like to add one more point i.e.condition types KOFI/KOFK are controlled with the reqirement type given in the Account determination procedure.
    I hope this info will add up to your query.
    kiran,

  • Accounts determination error is coming while create billing.

    Hi Experts,
    Accounts determination error is coming while create billing for Account Assignment Group A4 . In some cases only this error is appearing . I m a ABAPer I got this case and I  m debugging the code  . Can anyone  suggest me what all the things i need to check to know the root cause . This error is coming very  rarely but I want to find the reasons.  I saw some of scn post bt it was not clear .
    Please suggest briefly what w'd be the probable cause of this error and how to correct it.
    Thanks in advance

    Hi Dharmkrit,
    In one of your earlier posts, you have mentioned that you have assigned G/L accounts by selecting table 1. This is probably where you might be going wrong.
    Please follow the below steps to cross check your entries and you should hopefully have a solution.
    (1) First of all, start from the account determination procedure and check which procedure is assigned to the billing type.
    (2) Check the account determination type that is maintained in the procedure.
    (3) Check which access sequence assigned in that condition type
    (4) Check which table/tables have been maintained in the access sequence
    * In most probability, you would have maintained a different table in the access sequence while you are trying to assign your G/L accounts to some other table
    * Also, since you say that this error is only for a particular account determination type, check if you have maintained the correct combination of application/chart of account/Customer account assignment group/material account assignment group/G/L account in the correct table. However, this combination of fields depends on the table that you have used in the condition technique.
    I suggest that you write your entries down while checking the flow. This will give you a clear picture if a connection is missing somewhere in the condition technique.
    The customer/material account assignment groups are just keys (two digit codes) and their determination has nothing to do with Z1/Z2/A1 or any other code that you have defined in the system. The main determination is purely based on the condition technique and how correctly you have maintained the connections between the tables, access sequences, types and procedures. Just recheck these entries and you should be able to resolve the issue.
    Hope this helps
    Regards,
    Sumita Mittra

Maybe you are looking for