Account Determination

Hi friends
I got the error while releasing the billing document to accounting,
Posting keys for account determination for transaction EXD do not exist
Message no. F5598
Diagnosis
The posting keys necessary for account determination for transaction EXD have not been set.
System Response
Because the posting key is missing, the system cannot generate any automatic postings.
Procedure
Maintain the posting keys necessary for transaction EXD.
I have checked the Account determination in VKOA also, it is OK.
what could be the solution,
Thanx and Regards
srini

Hi srini,
In almost all customer cases with this error message it arose as a      
result of missing customising settings in FI.                                                                               
The help text on the error states that the posting keys necessary       
for the account determination have not been set.                                                                               
Please ensure that your customising is configured consistently. The     
relevant transactions are VKOA and OVUR.                                                                               
In addition, please review your configuration settings in transaction   
OB40 and also the table settings in T007B for your posting keys, to     
evaluate which posting indicator has been defined. You can do this      
using transaction OBCN.                                                 
Hope that the iformation helpful.
regards
Claudia

Similar Messages

  • Account determination error - in creation of invoice

    Hello experts,
    i have an error in creation of invoice, after( pgi post goods issue)
    will you please help me out to solve this error.
    thanks & Regards,
    yogesh raina

    hello sir,
    After going throuth this path it shows no gl account in account determination chart
    as below
    Condition type     Message     Description
      ZPR0                                  123     Access KOFI not carried out (initialized field)
    Access     Message     Description
    10     123     Access KOFI not carried out (initialized field)
    20     121     No G/L account found in Account determination type KOFI
    30     123     Access KOFI not carried out (initialized field)
    40     121     No G/L account found in Account determination type KOFI
    50     121     No G/L account found in Account determination type KOFI
    60     123     Access KOFI not carried out (initialized field)

  • Account determination error in VF02

    Hai Guru,s
    In VF02 when i am going ton release the flag to accounting i am getting following error  "Posting keys for accounting determination for transaction EXD does not exist"
    I checked VKOA EXD a/c key availabele .This is Exise duty account key.....In pricing procedure also EXD assigned to respectine condition type.............
    where i did wrong.........which setting i missed........
    Thank u in advance
    Regards
    Anjan

    Dear Anjan,
    For Tax Conditions you have to maintain Account Determination in OB40
    Go to T-Code OB40
    Select the Transaction - EXD - & Double click on it...
    Mention required GL Account here...
    Your problem would definitely get solved.
    Hope this helps...
    Give Points if useful...
    Thanks,
    Jignesh Mehta
    Edited by: Jignesh Mehta on Sep 26, 2008 10:42 AM

  • Account determination error in Subcontract PO-MIGO.?

    Hi all
    While doing GR, i mgetting error i "Account determination for entry LDCA BSV 0001 ___ 5010 not possible".
    The above PO is subcontract PO .
    Thanks
    sap-m

    Hi,
    For subcontracting..maintain these keys..so that you will not get any problem..
    BSX, BSV, WRX, PRD, FRL
    Regards,
    Prasath

  • Account determination error in FI-MM

    Hi Gurus
    I trying to raise PO requisition in ME21N. Here I am facing couple of issues
    1) If I select the K in account assignment category I can't assign the raw material GL account in account assignment tab  as it falls under balance sheet item.
    2) I have saved the PO with out K in the account assignment category and proceeded to MIGO when the saving the document in MIGO the system showing the rejection as "account determination is missing for Valuation class and for COCD"
    and postings are not reflected.
    I want make sure that all the settings related to account determination are good in OBYC.
    Please advise here
    Kishore

    Hi,
    As you mentioned the below is the error message.
    "account determination is missing for Valuation class and for COCD"
    What is COCD ???
    Is it Chart of Account or else????
    Ravi Polampalli

  • Account determination error in FI doc during SD billing doc posting.

    hi,
    when I create one billing doc ref to s/o,
    I check account determination in condition type:
    G/L account no.: 110000
    Provision acc.   : 120000
    in FI doc,
    should debit 110000 and credit 120000
    but current status is credit 110000 and debit 120000
    Please help.
    Thanks.

    Hi,
    One of the following could be the reasons for the Account determination error.
    Please check.
    1.Incorrect account assignment group entered in the customer and material master
    Resolution:Maintain correct account assignment group in customer and material master,Eg.External Domestic,Z1 - External Foreign,Internal Foreign,etc,.
    2.GL account not extended to the respective company code.
    Resolution:Extend the required GL account to the company code.
    Regards,
    Sophia Xavier

  • Account Determination error in MIGO

    Hi Folks,
    I am getting the following Error while doing MIGO
    "Account determination for entry ABCD ___ 0001 ___ 3000 not possible"
    I have checked in OMWD and OBYC and all the setting looks ok .
    Kindly suggest..
    Thanks
    Sumit

    Check valuation class for material you are using.

  • Account determination error in sales order

    Dear all,
    Please help. Trying to release a billing document to accounting. Getting the error:
    Document 90000004 saved (error in account determination)
    Message no. VF051
    While analysing: going to Environment - Accnt determination analysis - Revenue accounts :- no condition types are coming under the procedure KOFI000. Checked settings in vkoa. All G/L accounts are mapped. There are invoices of the same document type, with the same condition types in production with correct account determination.
    On further analysis, found that  no condition types are coming  not determined in the sales orders. Yet there is no incompletion log. Quite baffled. The users are punching in cut over sales orders into production. Please help me rectify the situation.
    Thanks,
    Kasturi

    I hope you have incompletion log (OVA2) maintain for WBS element in your sales order.
    Like
    Table
    Fld Name
    Desc
    Screen
    Status
    VBAK
    PS_PSP_PNR
    WBS Element
    KKNT
    Based your requirement , say, 01
    VBAP
    PS_PSP_PNR
    WBS Element
    PKNT
    Based your requirement , say, 06
    Regards
    JP

  • Account determination error in Billing

    Dear Expert,
    I create one billing doc(1840000318) based on SO:1810000296. But in the posting status it is showing "Posting document not created(account determn error) in billing. I did not found any FI relavant docs for this billing in open item customer list.
    *Anyone can advice me why the FI docs not created automatically..???
    **Do you think there any missing configuration set?
    ***Or if I cancel the billing docs then it will okay or not ?
    Thanks & b.Rgds
    Bishnu

    Hi Bishnu,
    Check Points for Account Determination.
    1. Ensure Cutomer master (Xd02)Sales Area Data- Billing Tab-- Acc Assign Grp  ---Should be maintained
    2. Material Master -
    Sales Org-2----
    Acc Assign Grp..Should be maintained.
    3. In VKOA maintain
    Application- V Chart of Accounts--Sales Org ---Acc Assgn Gp Of Cust -Acc Assgn Gp of Material-Acc Keys (ERL,ERS,ERF)----& G/L Account.
    4. In ur Pricing Procedure i.e V/08... Maintain Reqt -2 corresponding to ERL,ERS,ERF. & Subtotal =9 in front of net total.
    Revert  for further clarification.
    Regards
    Amit Gupta

  • Account determination error in Invoice document posting

    Problem - When generating the invoice document to customer, an error is displayed - Document is saved (Account determination error). As a consequence of this step, the invoicing is not able to create FI document
    My Analysis-
    Account determination is done in G/L account assignment (VKOA screen)
    For my billing document, the system is not able to find the GL account (below are screenshots)
    In VKOA screen, I already defined the GL account determination using KOFI procedure.
    I initially defined in table 2 Cust.Grp/Account Key and it didnt work.
    So I defined in both the tables 1 as well - Cust.Grp/MaterialGrp/AcctKey
    But still system is not reading the tables and obtaining the GL account no
    Any advice on why its not working?

    Hi Nikhil,
    As per the screen shots i could observe that you didn't maintained acct asst grp of customer.
    check the acct asst grp of customer field in billing tab is maintained or not.
    other possible reason may be in your pricing procedure -check whether the accounting keys are maintained or not.
    This could solve your issue.

  • G/L account determination through material account assignment group

    Hi ,
           I would really appreciate any help on this . The scenario is .
    We changed the account assignment group of maetrial to 01 just 2 days back.
    We have old open sales order line up for this particular material . When I am trying to Bill these open orders , the system is not recognizing the account assignment grp change which happened 2 days back ,because of which I am getting a A/C determination error .
    This is a I/C order and we have PO linked to it. I am suggesting to back out everything (Do Invoice reversal,MIGO cancellation,PO cancellation , then cancel invoice ,delivery and sales order ) so that we can create a new cycle and  the system will recognize the account assignment grp change and determines  the G/L whwn it comes to acounting .
    1. Is this the right way
    2. Is there any other way by which I can make the accounting happen
    It was very obvoius that when I see the account determination analysis ,the system wasn't able to find the account assignment grp for the material .
    Thanks
    Sridhar

    Dear Sridhar
    First of all, I dont think, you will be able to change the Account Assignment Group of a material in sale order if any subsequent document is generated bcoz the said field will become uneditable.  Moreover, via MASS, this is not possible as the field name of Account Assignment Group for material (KTGRM) is not available in MASS.
    So the other option is via MASS, you can assign Reason for Rejection for existing orders.  To assign Reason for Rejection in bulk is run T.Code MASS, input [BUS2032]  as Object Type and execute.  There block he Sales Order Item Data and click on Fields and block the field MASSVBAP-ABGRU and execute.  Input the sale orders if possible otherwise leave it blank and once again execute.  Now you can assign Reason for Rejection in mass.
    Meanwhile, you have to create new orders for all those open items.
    thanks
    G. Lakshmipathi

  • FI-MM- Account determination questions

    Hello Gurus,
    I have posted this thread in FI forum but couldn't get the answer that I was looking for so posting this thread in CO forum.
    I have the following specific requirement from our business:
    Is there any specific table in SAP that will give us the correct GL accounts if I mention valuation class and movement type?
    I know table T030 for account determination and we can also simulate using OMWB if we have material and movement type.
    What I am trying to accomplish is the following:
    If I give a movement type and valuation class in my selection screen there should be a way to get all related GL accounts.
    Similarly, If I give GL account and valuation class, I need to understand what are the movement type configurations that are maintained in the system for this combination of GL and val class.
    Can standard SAP accomplish this task?
    If no, do we need a custom program (or) can this requirement be accomplished by writing a query and merging T030 with any other movement type configuration table?
    Any feedback will be helpful.
    Thanks,
    Ram

    You can try with SQVI where you can table join multiple tables.
    thanks
    G. Lakshmipathi

  • 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

  • No G/L account found in Account determination type ZOFK

    Hi Forum,
    I have several inoices for which the acct. doc is not generated thru VFX3.
    In the header the Posting status shows "Posting document not created (pricing Error)"
    If I look in to the inovice's account determination analysis I find for two pricing condition types follwoing message is displayed *"No G/L account found in Account determination type ZOFK"*.
    Also in VKOA transaction there is no mention of ZOFK acct. det. condition type. It has all the G/L a/cs are assigned to ZOFI.
    Could some body help me how to know why in invoice the system is taking the ZOFK value and not posting it to account.
    Thanks.

    ZOFK is the copy of KOFK account determination type.................therefore whenever you are doing any costing related accounting entry system will required G/L account and Account Key combination for ZOFK account determination type...
    go to VKOA and maintain the G/L account with combination of Account key and Account determination type ZOFK...
    Regards,
    Ratish
    u2003

  • No G/L account found in Account determination type KOFI

    Hello everyone,
    I have an issue with a billing document, it will not release to accounting. I think I know what the issue is, however I have no idea how to fix it.
    When I go into the billing document, and I run an "Account Determination Analysis" for Revenue Accounts, I am getting the following error...
    "Access Message Description
    70 121 No G/L account found in Account determination type KOFI"
    And I am seeing the following details...
    Access (complete) Description
    Field in condition table Field in document Value in doc.
    Chart of accounts Chart of accounts KHAA
    Sales organization Sales organization 0001
    AcctAssgGr AcctAssgGr 01
    Acct assignment grp Acct assignment grp 01
    Valuation type Valuation type 1110170001
    Account key Account key ERL
    The account assignment group matches in the customer master as well as the material master.
    The Valuation Type above is set to "1110170001". This is NOT a valid valuation type, it is not setup in OMWC or anywhere else that I can find. This valuation type should be "EPAS". if it were, then the information is setup in VKOA, and we would not get this error.
    I was wondering if anyone has had this issue before? What can I do to get rid of this invalid valuation type?
    Thanks in advance for all your help.
    Rhonda

    Hi Rhonda
    Check what is the Valuation type of the  Material Master Record. Also check in OMWC for the plant what is the Account category reference. Also check in OMWD wheather for the Valuation area ,properly Valuation grouping code has been assigned or not. Finally check in VKOA wheather all G/L accounts are assigned or not and what is the G/L accounts that have been assigned
    Regards
    Srinath
    Edited by: sri nath on Oct 27, 2011 5:50 PM

  • Abt account determination

    I want to know how does the automatic account determination takes place in MIRO,everytime how system picks
    Vendor account(credit)
    GR/IR(DEBIT)
    In MIGO it depends on movement type and all other things,
    but in MIRO there is no mvt type.
    pls let me know asap

    Unplanned delivery costs (UPF)                                      
    Unplanned delivery costs are delivery costs (incidental procurement 
    costs) that were not planned in a purchase order (e.g. freight,     
    customs duty). In the SAP posting transaction in Logistics Invoice  
    Verification, instead of distributing these unplanned delivery costs
    among all invoice items as hitherto, you have the option of posting 
    them to a special account. A separate tax code can be used for this 
    account.                                                            
    If the above setting is not done and you have std price than it will post to the price diff account and fi you hae MAP then based it will post the mateiral account

Maybe you are looking for

  • How do I prepare my iPad to give to a new owner?

    What are the steps I must take to transfer all my apps and info to my new iPad from my ipad2?  I want to give my iPad 2 to a family member and I want him to be able to have the iPad 2 to be like a brand new one so that he can set it up the way he wan

  • How to completely uninstall a downloaded program from my macbook pro

    I am trying to uninstall a program that I downloaded from the internet and do not use anymore. However the drag and drop into the trash bin does not do it because it is still in my applications folder. How do I completely uninstall it from my macbook

  • Hello alltogether! I use PSE 7 on my PC with windows XP and now want to change to a new Mac with the

    Hello alltogether! I use PSE 7 on my PC with windows XP and now want to change to a new Mac with the newest version PSE . Is it possible to move all my albums and tags to that new version? Thank you very much for your kind answers! Candyapple111

  • Partner Role wrong

    Hi My Scenario is like this. Sync HTTP -> XI BPM -> Async Idoc ->Async Idoc -> XI and back to HTTP client. When the Idoc is received in R/3 the Partner Role is 'CR' And not SP as expected. When looking in SXI_MONITOR the message is correct with <SNDP

  • Adobe Encore CS6 Licensing issues

    Adobe Encore CS6 licensing: Cannot be run in trial mode.  Please relaunch the application and provide a valid serial number. Uninstalled and reinstalled the application, ran the 6.0.2 update.  When the error comes up, it does not give me a window to