Copy account determination

Hi,
In customzing you can create G/L accounts for new company codes with reference.
There is also an option "Copy account determination". What is exactly copied when you use this option?
Best Regards,
Eric.

**wrong area***

Similar Messages

  • Copy account determination (OB_GLACC01) and create G/L accounts

    Hi,
    In customzing you can create G/L accounts for new company codes with reference.
    There is also an option "Copy account determination". What is exactly copied when you use this option, and how can I check it?
    Second question In customizing you can create G/L accounts with refrence OB_GLACC01 or copy them OBY2.
    What is the best methode to use if you don't change the G/L accounts for the new companies?
    Best Regards,
    Eric.

    There are mainly links, sdn thread & message, sdn wiki & doc flowing around.
    Only thing required from your side is to put afford to search them.
    Thus, kindly put an afford to search for the topics search you want and if you find any problem in that then post your query on any of the respective forum.
    For instance, follow the following links:
    - [Account Determination|http://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=ERPLO&title=Account+Determination&decorator=printable]
    - Re: Account Determination
    - [Account Determination|http://wiki.sdn.sap.com/wiki/display/ERPLO/SD+FAQ#SDFAQ-2.AccountDetermination]
    Hope you are aware of rules & regulation of SDN forums.
    -Welcome and Rules of Engagement
    -Read this before posting
    Kindly corporate.
    Regards
    JP

  • 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

  • Error in :Posting keys for account determination

    Hi, Gurus,
          please suggest the solution for the following problem.
                we are selling two  types of materials, one is the  product material and the second one is the scrap material.Different type pricing procedures, sale order,delivery and billing types were configured for the same. For CST and VAT   same condition type  :"ZCST - for CST " and  ZVAT - for VAT" were used in both pricing procedure and the standard account keys : MW1 for ZCST and MWS for ZVAT  and  same G/L accounts configured .
    .                                                   key combination for the condition types as mentioned below:
    .                                                        ZCST:  Country/PlntRegion/Region/TaxCl2Cust/TaxCl.2Mat
                                                             ZVAT: Country/PlntRegion/Region/TaxCl1Cust/TaxCl.Mat
         Now we want to capture  CST and VAT seperately for both the materails.For that two new account keys created and incorporated the same in scrap pricing procedure and  and new  G/Ls created and assigned .Now the system is throwing  following error while while releasing the billing document to accounting document.
    Posting keys for account determination for transaction Z48 do not exist
    Message no. F5598
    here Z48 is the new accounting key created for  the  CST tax.We tried all the possibilities, but system is throwing the same error.
    with regards
    sam

    Thank u for ur response.Now it is solved when OB40 and OBCN maintained.Here I am facing a new problem.pl. provide the solution.we configured twoseperate  pricing procedures for our product and scrap material.We have configured same condition types for VAT(ie.condition type:ZVAT) and CST(cond type:ZCST), in both pricing procedures. Now We want to maintain  seperate condition types for VAT and CST for pricing procedure for Product material and Scrap material. I have created two new condition types for scrap sales ZSCT- cst for scrap and ZSVT-vat for scrap by copying the same from existing conditions ZCST & ZVAT, and the same is included in the scrap pricing procedure. And also maintained OB40,OBCN,OVK1,OVK3,OVK4, FTXP,FV11 and VK11.
    now I am facing the following problems.
    1. while creating the Material master & customer master, in tax category sub screen all conditions i.e. conditions defined for  product material( ZCST,ZVAT) and defined for scrap material (ZSCT, ZSVT) displaying and these are compulsory fields.
    2. While creating the sale order for scrap material, system is considering the TAX classes from ZVAT/ ZCST (defined for product material) and taking the condition value from the condition type ZSVT/ ZSCT with the TAX class values of  ZVAT/ZCST.
    Now I would like to know is there any procedure  to assign the Material type and Customer group to Tax category.
    Thanks & Regards
    sam

  • PR00 120 G/L account 0000785101 determined from Account determination type

    Hi all,
    I am getting the following error while saving sales order.
    PR00 120 G/L account 0000785101 determined from Account determination type
    I dont know why this error is occuring while creating sales order. Because of this issue, i am not able to save the sales order.
    How to solve this issue? Can anyone give me solution for this issue?
    Thanks in advance,
    Babu

    Hiii
    I hope you people are using COPA or Controlling in your process.
    This error is basically comes if you are not maintained the KOFK setting, same where u have done your KOFI setting, you have to do same with KOFK in Transaction VKOA.
    see what setting you have done for KOFI, copy that line and change KOFI to KOFK and save it.
    Hope it will solve your problem
    Regards
    Shambhu Sarkar

  • Cost of Goods Sold account determination by customer type (inter-company)

    We have a business need to separate the the cost of goods sold be customer type.  Specifically separating the inter-company cost of goods sold from the 3rd party cost of goods sold. 
    The standard COGS account determination in GBB/VAX only allows for differentiating between material valuation class. 
    Has anyone attempted this before and what method worked?

    For those who may need an answer to this, our solution was the following: 
    1)       Created new types for SO, SO Item, Sched. Line, Delivery, Delivery Item, Billing type  
    2)       Created new Pricing procedure
    3)       Created new movement type Y61/Y62 modeled after 601/602
    4)       Mapped Y61/Y62 to account modifier ZAX.
    5)       Mapped GBB/ZAX to the new account.
    Benefits, they now have better view of the orders going inter-company.  It is flexible enough to adjusting prices for intercompany separate from standard orders, even though for now it is a straight copy of cost.  They are able to remove the sales/use tax, from the calculations. They are able to plan with these orders separated out.  Plus, this will standardize their process for inter-company. 
    Hope this helps someone. 
    Cheers!
    Rick

  • Account determination in cancellation of billing document (VF11)

    Does anybody know if it's possible that a new account determination was carried out when cancelling a sd-billing document with VF11 transaction?
    Now, if we cancel a billing document the FI all relevant data is copied from the billing document to be cancelled. We'd like that a new account determination is carried out when cancelling the billing document.
    Thank you very much.
    Alberto.

    I'll try to explain in more detail the issue. Before January 2008, a society doesn't work with FI in SAP but only with logistics areas. Billing documents were created with an standard and not real account determination. Now, this society is working with FI in SAP and we have customized the correct and real account determination. Some times, an old billing document (posted before January 2008) has to be cancelled but the corresponding FI document takes the incorrect accounts.
    Thank you very much.
    Alberto

  • Error in account determination

    Dear All,
    I am getting error in account determination when iam trying to post the billing document from the automatically brought condition taxes in to the sales document.However i dont have problems when i am entering the same tax condition types manually in the sales order.these are copied to the billing documents and get posted as well.The automatiocally brought condition taxes(same one as the manually entered ones)
    in the sales order are copied in to the invoice but not able to post the same in accounting documents.
    Your immediate response is highly solicited.Reward points are assured for the timely support.
    Tahnking you,
    Best regards,
    R.Srinivasan

    hi,
    Thankyou very much for your kind reply.
    checked  the Tax Code and is maintained correctly in the condition record, and further G/L is maintained in the Tax Code.
    Also please note when i manually enter the conditions the billing document is getting posted in FI.
    Thanking you,
    Best regards
    R.Srinivasan

  • "Error in account determination:Table T030K key MWS"

    Hello Gurus,
    I would greatly appreciate some help on the following issues. The issue relates to tax on sales & purchases. The client charges a state tax for residents of certain states. In FTXP, I have used TAXUSJ and also tax code O1 (A/R Sales Tax, taxable). I have also put the state that charges the tax in the Tax Jurisdiction field in FTXP. In MW1 (Accrued: A/R Sales Tax 1) I have 6.500% for the state.
    On the SD side, the consultant is using the Acct Key of MWS for the Condition type UTX1 (hope that makes sense).
    When I try to release the billing document to accounting I get the following error:
    <b>Error in account determination:Table T030K key MWS</b>
    <b>Message no. FF709</b>
    <b>Diagnosis</b>
    In the chart of accounts to be posted to, no accounts are defined for the tax code you used.
    <b>Procedure</b>
    Contact your system administrator. Define the accounts to which a tax posting is to be made with the tax code entered in Customizing for taxes on sales/purchases. To do this, choose Maintain entries (F5).
    I went to OBYZ, double clicked on PROCEDURES, then selected TAXUSJ and double clicked on CONTROL. Once inside, I then <u>changed the account key for condition type JR1 from MW1 to MWS  and saved it.</u>
    But when I went back to release the billing document to accounting, I now get a new error:
    <b>System error in routine FI_TAX_GET_TXJCD_LEVELS error code 2 function builder TAX2</b>Message no. FF769
    <b>Diagnosis</b>
    A serious program error has occurred.
    <b>System Response</b>
    The current processing step cannot be carried out.
    <b>Procedure</b>
    If the program error occurred
    - In a standard SAP program, then create an OSS message
    - In a program you wrote yourself, then correct the program.
    I went back and changed MWS back to MW1 but still get this new error. Does anyone know what could be wrong?
    Thanks in advance!

    Hi United99
    To tell u in layman words, u r missing in Account determinatin. Tax determination is almost same as Pricing Procidur in SD for which we assign GL accounts to transaction key. As there are ERL, ERF, keys u have MWS (Output Tax)key assigned to Tax procidure TAXUS (check this at defining tax procidre.
    Now we assign GL accounts to this Transaction key MWS as OB40. U assign GL account at OB40. Your issue will be resolved. But..
    MWS is default Key, i suggest not to distrub it but copy it and assign it to your procidure and to this key assig GL account at OB40.
    Please assign points if useful
    Satish

  • Account determination for movement type 251

    Hi!
    While checking account determination for logistic movements, I find that according to standard customizing, movement type 251 is related to account modification VBR. You can easily see this: OMJJ --> Check movement type --> type "251" --> Select "Account Grouping".
    Now my question: what I don't understand is why VBR and not VAX. GBB-VBR is the transaction key + account modification for internal goods issues (such as consumptions of material) and it's accordingly associated to movements types 201, 261, etc. which seems logical to me since these are internal GI's.
    Now, 251 is IS-Retail movement type to reflect a POS sale, "GI for sales" as the short text indicates, so it is not an internal goods issue but rather an external one, not different from movement type 601, which is a normal sale and is associated to GBB-VAX. GBB-VAX is the transaction key + account modification for sales goods issue.
    I know I could easily copy 251 to create another movement type and assign any account modification to it, that's not the issue. The only problem is that I must explain to my client how account assignments work, and I cannot find a single reason why in standard SAP IS-R an external goods issue (251) is associated with an internal goods issue account modification (GBB-VBR).
    Any ideas? Thanks in advance.

    hi
    for inventory use
    gbb>inv
    umbfor inventory and material val
    prv for prise diffrence
    in 702   prv and inv is the postings
    for 309 vbr and pru is transaction in gbb
    1) one more thing u can do is go to OMWb then go to simulation there u can find gl accounts and grouping  keys note down that GL nos
    2) then come one step back
    and clik on  gl accounts  there u will find many gl accounts 
    find gl accont no which u have noted in step 1
    there u can find transaction keys
    by doing this u can find which are transaction keys for a perticular movement type
    reward if helpful
    regards
    kunal

  • Access Sequence Field not recognized in the Account Determination

    Hi All,
    we have created a new table for the account determination access sequence we are using as default.
    the new table contains the field MVGR2 (VBAP) which we added to the KOMPCV structure as ZZMVGR2.
    this goes fine in the sales order, however this is no longer recognized during billing. the field has no value in the Account determination analysis, hence there is no GL account determined for that.
    can anyone help?

    My guess is: you will have to modify the copy control routine, and populate the value of the new field accordingly.
    This routine needs to be assigned to the item category in copy control configuration (VTFL).
    Needless to say, the existing routine should be copied and then modified.
    Regards,
    Aroop

  • Account determination for cash sale

    Hi, sapcons
    please can any body can help me by sending  step by step notes on account determination for cash sales and rush orders
    my mail id is [email protected]
    thanks in advance
    regards
    srinivas

    Hi Srinivas,
    Account Determination for Cash Sale and Rush Order will be done in VKOA Transaction.
    Please find below the Process of Cash Sale and Rush Order
    CASH SALE:
    Cash sales is an order type for when the customer orders, picks up and pays for the goods immediately. The delivery is processed as soon as the order has been entered. A cash invoice can be printed immediately from the order and billing is related to the order. Receivables do not occur for the customer as they do for rush or standard orders, because the invoice amount is posted directly to a cash account.
    Process Flow
    In the standard system, sales document type BV is saved for cash sales with immediate delivery type BV.
    When the sales employee creates a cash sale, the system automatically proposes the current date as the date for delivery and billing. Once the order has been posted, a delivery with type BV is created immediately in the background and the system prints a document that is used as an invoice for the customer.
    The invoice papers are controlled with output type RD03, contained in the output determination procedure for order type BV.
    For Cash Sales the necessary Config Settings are,
    Copy the BV Standard Order and Copy to ZBV and in the functionality of ZBV check whether the field " Immediate Delivery" has the value "X" or not because that creates the Delivery immediately when the cash sale order saved. Do the same for item category BVN as ZBVN. And check whether credit active unchecked or not in ZBVN.
    Do the item category determination for cash sale for which u configured. And at the time of cash sale u will get the invoice. For that u use the output type Rd03.
    RUSH ORDERS:
    In a rush order transaction, the customer picks up the goods or you deliver the goods on the same day as the order is placed. In the standard system, when you save this sales document type, a delivery is automatically created and billing is related to the delivery.
    Process Flow
    In the standard system, sales document type SO is saved for rush orders with immediate delivery type LF. Once the goods have been removed from storage, the goods are picked, and goods issue is posted.
    Once the billing documents are created (for example, in collective processing), invoice papers are printed and sent to the customer.
    For Rush Order the necessary Config Settings are,
    Copy the RO Standard Order and Copy to ZRO and in the functionality of ZRO check whether the field " Immediate Delivery" has the value "X" or not because that creates the Delivery immediately when the cash sale order saved. Do the same for item category TAN as ZTAN. Do the item category determination for cash sale for which u configured. And check whether credit active checked or not in ZTAN.
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Intercompany Goods Movement Account Determination

    Hi,
    I'm wondering how to meet a business requirement relating to intercompany FI postings.
    We use the NB stock transport order to transfer materials between plants in different company codes. For this order type, SAP uses movement type 643 for the shipment and movement type 101 for the goods receipt.
    The requirements are:
    1) we would like to use the same FI account as offset for shipment as the receipt
    2) the account should not be the vendor Purchase Price Variance (PPV) account; otherwise it would be too difficult to analyze this account.
    The account determination for the 643 is determined in GBB VAX; and the account determination for the 101 is in PRD (no modifier). However this is the same account determination as Purchase Price Variance (PPV).
    Aside from creating a new movement type for the goods receipt, is there any way to achieve the required FI Postings?
    Thanks -- points to be awarded for a good solution.
    Dan

    Dear Dan
    Yes this is achievable.  But instead of changing the standard feature, you better copy the standard 643 and create a new movement type.
    For that go to OMJJ, select Movement Type, input 643 and execute.  You can see some tabs to your left screen where you double click on [Account Grouping]  so that a screen will open where you can modify the Account Grouping under the tab Account Modification.  Change it to required Account Group and save.
    Now try your process from begining and check the FI impact.  All these changes have to be tested thoroughly in development, get the concurrence from FI people and then transport to production.
    thanks
    G. Lakshmipathi

  • G/L account determination/change in confirmation

    Hello,
    How can we achieve G/L account determination and change while creating a confirmation in SRM?
    Is it possible using the CHANGE_DOC BADI.
    Ultimately we shoudl be able to modify the G/L account copied from PO in case the product category changes at item level.
    Please let me know if anyone has worked on similar issue.
    Regards.

    Dear Olyn,
    if it is showing in Account Determination analysis that "G/L account has been determined", but still in the incompletion log it shows "G/L account was not determined", then the most possible chance is that after creating the Sales Order the G/L account was determined for Customer or Material.
    You can be able to save the order even it is incomplete.
    Solution: you can delete the line item from the sales order & again add it
    Please let me know if this solution helps you or not.
    Thanks
    Bidhu

  • T030 - custom key for account determination

    Dear expert,
    according to your opinion would it be possibile to create a custom key for account determination.
    (f.i. ZGBB as a copy of GBB).
    Thank you in advance.
    Fuffo.

    Hi
    You can create new transaction keys for conditions (like delivery costs etc) but regular transaction keys like GBB - I  think not possible.
    Thanks
    Edited by: Praveen Raghavendra on Apr 3, 2009 7:26 AM

Maybe you are looking for