Account determination error for Account key

Hi Everyone,
I have maintain one condition manual pricing e.g ZMRG where i m manually putting the margin of sales price
this condition is only for calculation and i dont want to post it to account. But at the time of bill it is giving me account determination error. In VF02 i check it is showing error due to not assigning the account key for that condition but here i dont want to post that condition to accounts.
Please suggest me the best possible way.
Regards
Shambhu

Hi,
You said that the condition is manual.
Now you saying:
i maintained the condition for it instead of only text in PP
Have you got the solution? Then please update.
Thanks,
Ravi

Similar Messages

  • Account determination error for EK02

    Hi,
    I am using EK02 for unit costing in quotation used specially for PS.
    I have assigned EK02 in the quotation doc type and have added the same to the pricing procedure (marked it manual & ststistical) and assigned it SubTotal-B.
    It is working perfectly in the quotation but while in Sales Order it is giving account determination error for EK02.
    I am unable to understand when there is no account key assigned to it, how is this error ?
    Please advise immediately.
    Regards,
    Rajesh

    Check the Requirement class in order - in procurement tab.
    when you use the EK02 cost estimation condition type, Controlling documents get generated once you save the sales order.
    i.e. the reason, in VKOA for the all the access keys maintained in order pricing procedure, should have valid record with Costing conditon type:KOFK.
    maitain entries in table:005- Account key for all the account keys maitained
    such as;
    Application / Condition type-KOFK/ chart of accounts/ Acct key - G/L account ( here maintain same G/L account which have you assigned with Condition type KOFI)
    it will solve your issue.

  • Account Determination Error for Rebate Settlements

    I have question on Account Determination for rebates
    Here are the entries that I have made in VKOA
    ERB - R201051
    ERU - R201051 / R120201
    ERS - R120201
    ERL - R559001
    I am able to accrue the money to right accounts, but I am getting an Account Determination error when processing rebate settlements
    Any input on this would be really helpful.
    Thank you!

    Hi Shailesh
    When you are getting the error in rebate settlements it means you carefully check
    all the combinations for VKOA settings. Whether the Account assignment
    group in all the Materials used in settlement document along with the customer account assignment group
    is maintained or not. Also check in the pricing procedure the account key used.
    For all these account key the settings are made in VKOA or not. Hope it will help you
    Thanks
    sushant

  • Accounting Determination Error

    Hi,
    I am getting the below error message in VF02.
    "Account determination error".
    Accounting document has not been released yet though SAP billing documentcreated.
    Please let me know where the configuration happens.
    Thanks
    Venkatesh

    Hi Venkatesh,
    We can determine the GL accounts through access sequence.
    Access sequence is nothing but SAP terminology of determing the GL accounts.
    Basically the FI- SD integration is for picking up the revenue accounts or the discounts and surcharges.
    The account key determines whether it is a revenue or a surcharge or discount.
    Actually Goods issue and billing generate account entries.
    Goods issue:
    Cost of goods sold account                          Dr
    Inventary finished goods account                 Cr
    Billing:
    Customer               Dr
    Sales                     Cr
    Please check configuration GL account determinations.at VKOA
    ERL               Sales revenue
    ERS               Sales deductions
    MWS             Sales Tax    etc.....
    and also please check automatic account determination in OBYC. In OBYC need to maintain offsetting entry.
    GBB       -
    >              Inventary stock account
    I hope you are understand.
    Thanks & Regards,
    Haribabu Bodapudi

  • Report on Account determination errors

    Normally, when billing sometimes you get the account determination errors and then users have to investigate and find solutions.  My user wants to run a report prior to billing to detect any possible errors that prevent the posting to accounting document.  If it is, does anyone know of such report.
    Thanks.

    Hi,
    There is no standard report for checking SD account determination, as there is no specific reason for account determination error, possible Account determination error reasons are account group is not maintain in customer master, new condition is not mapped in COPA. Finished product Sales, Account view is not maintain properly, Account key is not assigned properly to condition in pricing etc. If you need a report better you can develop based on above checks.
    Regards,
    Santosh

  • Account Determination error while goods receipt

    I am trying to receive a Purchase order thru MIGO transaction. I got an error message saying "Account Determination for entry IPGL FR1 0040 not possible".
    This error message came only when i had "FRB1" condition type in Purchase Order Conditions. Without FRB1 condition type in conditions i am able to receive the Purchase Order thru MIGO.
    IPGL is the chart of accounts in our company.
    What is FR1 in the error message ?
    What is 0040 ?
    What is the connection between condition type FRB1 and Account determination?
    What do i need to do to fix the issue?
    I greatly appreciate any help from you guys.

    Prashanth,
    I would encourage you to search the forum before posting any question (if you have the time, interest etc). It is likely that youu question (or a similar question) would have been answered previously.
    Please search the forum with 'account determination error' for instance. I get 11 hits. You can try searching with other similar terms. Read the hits and then come back if you still have questions.
    I don't intend to be unhelpful but I felt the need to point this out (although most people don't seem to care).
    H Narayan

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

  • Account determination error

    hi
    when i a creating a billing document for third patry sales with refernce to sales order
    while saving the doc i am facing error called account determination error
    can i now where i am wrong
    do i have to amitained ant record in VKOA
    if yes what
    Screen shot
    http://www.4shared.com/file/59857963/f56431d5/fico.html
    Regards
    Vini

    The access you are using for maintaining the condition record. The screen shows the first two accesses which means that there is something wrong with that.
    If your acct determination is not carried out then it will say acct. det has not been done . \
    Looks like your condition records and the acct. determination seems to be a problem.
    GO to acct. det. in BAsic functions- revenue acct detemination I think its VKOA and check your account determnation to see if your account keys and accounts have been correctly maintianed.
    Check your pricing procedure to see if all the relevant condition types have been assigned to the account keys.
    check if your condition records have been maintianed in the correct accesses. It will solce your problem.
    regds
    Jude

  • Account Determination Error - Discounts - ERS

    Dear All,
    When I am releasing my Billing Document, I am getting the "Account Determination Error".
    My Requirement: Sales Discounts should not post to ERS Account Key.
    Price          -     PR00 - 10000 ERL GL Account (10000)
    Discount    -     K004 - 10%
                                         900
    Base Price                   9, 100 INR  
    In the Accounting ENtry - it has to show only Customer Account 9100 Dr to Sales Revenue A/c 9100.
    I don't want to show Sales Discount 900 Rs.
    For this in pricing procedure configuration - i have removed ERS Act key (for not posting), becoz of this - I am getting the Account Determination Error.
    Any Idea on How to Configure the above scenario?
    Ganesh Varma G.

    In pricing procedure
    MAINTAIN SUBTOTAL CONDITION AFTER DISCOUNT IN PRICING. MAINTAIN THE DISCOUNT CONDITION AS STATISTICAL.
    MAINTAIN ACCOUNT KEY ERL FOR SUBTOTAL.
    STEP  COND TYPE                FROM             TO         STAT     ACCT KEY
    10       PR00                                                                             -
    20       K004                                                                 X          -
             price after discount      10                  20                        ERL

  • MM - account determination error

    Hi MM Experts,
        We have a vendor with currency in USD.After G/R,document has been parked successfully using MR41.But when we tried to post the parked document it gives the error message.
    "Account determination for key BIV1KDR is not possible"
    Here BIV1 - Chart of Accounts and KDR - Account key for MM exchange rate differences.
    Whereas for a different PO raised against the same vendor we were able to successfully post the parked document without any error.(Both the POs were raised on the same date)
    Can you pls provide ur valuable inputs to resolve this issue?
    Rgds,
    Aram K.

    for this transaction to pass u will have to put gl account in that key in obyc.
    before transaction may be posted as there might be no diffrence in exchange rate
    and now for this transaction there might be a diffrence in exchange rate.
    so to post this transaction u will have to give gl account in obyc for that key
    reward if usefull

  • Unable to determine domain for account  Uninstall ecc6 on domain

    Hello All,
    I am trying to uninstall sap ecc6 from a server on a domain . While proceeding with uninstallation, it got stuck with following error details after entering the database details on sapinst.exe
    FSL-01018  Unable to determine domain for account S-1-5-21-705529515-409054649-1020538192-1108. The group name could not be found.
    ERROR 2008-01-02 10:29:35
    MUT-03025  Caught ESyException in Modulecall: ESAPinstException: error text undefined.
    I am trying to uninstall by logging to that server as administrator of domain . Can you guys give me some clue to fix this.
    Thank you in advance

    Hello All,
    Here are the other log details
    INFO 2008-01-29 11:02:05
    An error occured and the user decided to retry the current step: "|NW_Uninstall|ind|ind|ind|ind|0|0|NW_System_Uninstall|ind|ind|ind|ind|3|0|NW_uninstallDB|ind|ind|ind|ind|1|0|NW_OraDBCheck|ind|ind|ind|ind|2|0|checkForExistingDatabase".
    ERROR 2008-01-29 11:02:10
    FSL-01015  Unable to determine whether account TESTSAP\Administrator is member of account wicomp05\ORA_C30_DBA. The group name could not be found.
    ERROR 2008-01-29 11:02:10
    MUT-03025  Caught ESyException in Modulecall: ESAPinstException: error text undefined.
    ERROR 2008-01-29 11:02:10
    FCO-00011  The step checkForExistingDatabase with step key |NW_Uninstall|ind|ind|ind|ind|0|0|NW_System_Uninstall|ind|ind|ind|ind|3|0|NW_uninstallDB|ind|ind|ind|ind|1|0|NW_OraDBCheck|ind|ind|ind|ind|2|0|checkForExistingDatabase was executed with status ERROR .
    INFO 2008-01-29 11:02:17
    An error occured and the user decided to retry the current step: "|NW_Uninstall|ind|ind|ind|ind|0|0|NW_System_Uninstall|ind|ind|ind|ind|3|0|NW_uninstallDB|ind|ind|ind|ind|1|0|NW_OraDBCheck|ind|ind|ind|ind|2|0|checkForExistingDatabase".
    ERROR 2008-01-29 11:02:21
    Here TESTSAP\Administrator is the administrator of domain TESTSAP on which  sap is installed and wicomp05\ORA_C30_DBA is hostname and oracle dbsid and the group dba,
    When I check on the the group ORA_C30_DBA,  TESTSAP\Administrator is the member of group
    I tried to change the name of the group to
    ORA_C30_DBA1 and it successfully passed the phase of error. However the drop  database phase seems like disabled and it tells to manually drop the database.
    Can I proceed with this method and finally drop the database manually ?. Have any one done like this.
    Please help.

  • 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

  • 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 at billing level

    Hi,
    for Account determination error at billing level
    i checked the line item level for the material by highlighting the item, then GO TO > ITEM > ITEM DETAILS. here 5 line items are there , 4 line items have same "Acct asgnmt grp" and 1 line item is different at order level. i gess this is the problem if am wrong please correct me.
    thanks
    Edited by: pandu123 on May 26, 2011 2:24 AM
    Edited by: pandu123 on May 26, 2011 2:32 AM

    Hi Pandu
    A/c deterimation error. 1st you check in customer master sales area data billing tab page with account assingment and go to material master u select particular material see in sales organization 2 tab with account assignment. and go to T.Code VKOA check the combination which is assiged A/c assingmnet group of customer and matrial account assingment group. If it is not come goto VFX3 and specify the customer execute and click on RELEASE FLAG. If it is error go to log see the digonsis.
    Kind Regards
    Chandra Mouli A

  • Account Determination Error:  How to properly cancel the invoice/ cr memo

    Hello SAP Guru's,
    What is the correct procedure in cancelling an invoice with Account Determination errors and subsequent credit memo?  The error is a result of the user entering line items that are not permitted for the order type thus we suspect caused the Account Determination error.  We were however unable to verify or correct that.
    We now want to cancel the invoice and all the subsequent credit memos.  What is the correct procedure in doing so?
    I think we start off by VF03 then select the billing and select Display Document then Cancel?  Is this correct?
    Thank you.

    Hi,
    If you want to block specific line items in the sales order then you could enter a u201Creason for rejectionu201D in those line items and save the sales order. This can be done by going to the tab "Reason for Rejection".
    If you want to stop delivery creation for the entire sales order then you could enter a delivery block in the sales order. Delivery block field can be found on the main "Sales" tab.
    Cheers,
    Shailabh

Maybe you are looking for

  • Since downloading firefox, I can no longer open a PDF file? How do I get my computer to open PDF files?

    I am enrolled in college and have to down load graph paper. The teacher posted a link to her copies of graph that we can download at home. The graph paper link is a PDF file and when I click on the link the page opens but it's only a white page. I al

  • Vaults No Longer Show Up in Aperture

    I opened Aperture today and my two rotating backup vaults (on two external HDs) do not show up in the "Show Vaults" pane. Each of these HD Vaults is almost 2TB of Aperture files, so I could wipe the drives and do a fresh backup, but that would probab

  • Does Time Machine work?

    I see lots of posts from people with the same problem I have: TM worked correctly for a while, now I get "error creating backup directory" messages. The answers mention a lot of possible problems/solutions, but really: this software is painful to use

  • XSLT with XDK (Using C libs, Oracle 8.1.7)

    Hi,I am currently tring to use the XSLT mechanism available within Oracle 8.1.7 XDK C libs. In the file called "XSLSample.c", a function :"void printres(xmlctx*, xmlnode*)" is used to display the result of the tranformation to the standard output. Wh

  • How to put data from database into array

    I need to answer hot to put data from database directly into array. I tried like the code below but the error message said: java.lang.ArrayIndexOutOfBoundsException: 0, and it points to this line: numbers [row][0]= rs.getString("ID"); Hope you can he