Business transaction key in account determination..?

Hi all
Can anybody explain me in simple form form, what is business transaction key in account determination , for eg, GBB,BSA,BSX,PRD,VBR,.WRX....etc (Approximately 60 transaction keys in std SAP)
If i want to do configuration the for new client, what are all the business transaction key,,, How the configuration wil happen..?
Pls giv me expaination,
Reply will be rewardable..
Thanks
sap-mm

Hi MM,
Please Search in SDN threads solution is given already in lot of threads.
Go to SAP Library
SPRO> Help> SAP Library
Or go to SPRO> IMG> MM>Valuation and Account Assignment>Account determination> Account det without wizard> configure Automatic postings
Click on IMG ACTIVITY DOCUMENTATION
These transactions are important for Accounts.
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a goods issue for a cost center:
Stock account
Consumption account
Agency business: income (AG1)
This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
Agency business: turnover (AG2)
This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
Agency business: expense (AG3)
This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
Supplementary entry for stock (BSD)
This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such postings are effected, for example:
In inventory management in the case of goods receipts to own stock and goods issues from own stock
In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.
Del credere (DEL)
Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
These transactions are used only if Purchase Account Management is active in the company code.
Note
Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
Before you use this function, check whether you need to use it in your country.
Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
You can also enter your own transactions for delivery costs in condition types.
External service (FRL)
The transaction is used for goods and invoice receipts in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
Exchange Rate Differences Materials Management(AVR) (KDG)
When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
Differences due to exchange rate rounding, Materials Management (KDR)
An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
Exchange Rate Differences from Lower Levels (KDV)
In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
None for consignment liabilities
PIP for pipeline liabilities
Offsetting entry for price differences in cost object hierarchies (KTR)
The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
Accruals and deferrals account (material ledger) (LKW)
If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).
Price Difference from Exploded WIP (Lar.) (PRA)
If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
Differences (AVR Price) (PRC)
In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
Price Differences (Material Ledger, AVR) (PRG)
When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
Price differences in cost object hierarchies (PRK)
In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
Price Difference from Exploded WIP (Mat.) (PRM)
If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
Price differences, product cost collector (PRP)
During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
This transaction is currently used in the following instances only:
Production cost collector in Release 4.0
Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
Offsetting entry: price differences, product cost collector (PRQ)
The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
This transaction is currently used in the following instances only:
Production cost collector in Release 4.0
Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
Price Differences from Lower Levels (PRV)
In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
Price differences for material ledger (PRY)
In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
Expense and revenue from revaluation (retroactive pricing, RAP)
This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.
Invoice reductions in Logistics Invoice Verification (RKA)
This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
Expenditure/income from revaluation (UMD)
This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
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.
Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
Inflation posting (WGB)
Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
WIP from Price Differences (Internal Activity) (WPA)
When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
WIP from Price Differences (Material) (WPM)
When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
Caution
You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
GR/IR clearing for material ledger (WRY)
This transaction/event key is not used from Release 4.0 onwards.
Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
Reg,
Ashok
assign points if useful.

Similar Messages

  • Transaction key for account determination

    Hi guru,
    i would like to add a new transaction key for account determination to fullfil a business process .
    Could you help me to find out the Transaction code in customizing?
    A prompt reply is appreciated.
    Thanks in advance
    Vir

    Dear Vir,
    The G/L account determination process in G/L Accounting mostly uses the
    transaction key technique to obtain the required G/L accounts for business transactions.
    For Foreign currency transactions:
    SPRO -> Financial Accounting -> General Ledger Accounting -> Periodic Processing -> Valuate -> Foreign Currency Valuation
    Other General Ledger Transactions
    SPRO -> Financial Accounting -> General Ledger Accounting -> Business Transactions -> Closing -> Carried Forward -> Define Retained Earning Account
    OBA1 G/L account determination for foreign currency valuation
    OBYA Maintain inter-company clearing G/L accounts
    OB53 Maintain retained earnings accounts
    OBBV Assign AR/AP adjustment accounts
    OBXD Maintain bad debt reserve accounts
    ACACAD Accrual account determination ( simple or extended )
    ACACADMETASGL Accrual account determination strategy
    ACACTREE01 Create accrual objects
    Pricing:
            V/09    Condition Types: Account Determin.
            V/10    Account Determination: Access Seqnc
            V/11    Conditions: Account Determin.Proced.
            V/12    Account Determination: Create Table
            V/13    Account Determination: Change Table
            V/14    Account Determination: Display Table
    G/L Accounts in MM Account Determination:
    The program RM07C030 check all the G/L account define in your Material Master valuation class.
    Search is via Company code and Valuation area.
    Visit the following link for more information:
    http://www.sapscene.com/sapscene/accassg.html#SD-FI%20Account%20Determination
    Reward points if this is helpful.
    Regards,
    Naveen.

  • Error in VF02 (Posting keys for account determination for transaction JTS)

    Hi,
    I have created new account key JTS and also assigned G/L account in VKOA, But at the time of releasing the billing document to accounting, I am getting the below error;
    Posting keys for account determination for transaction JTS do not exist
    Message no. F5598

    Hi Amanulla,
    once we create the Account key in revenue determination we have to assign that account key to respective procedure and condition types.
    check that.
    please award points.
    ravikanth

  • Posting keys for account determination for transaction do not exist

    Dear SAP Gurus,
    While release to accounting service sale billing bellow error occurs while i made all necessary changes in VKOA.
    Posting keys for account determination for transaction do not exist
    Please guide me to coorect this error.
    With Regards
    MK

    Dear IMUKUL,
    Please search the forum before posting.
    Check the following thread and see whether it helps you.
    CIN Error
    Kindly make it a point to search forum before posting
    Thanks & Regards,
    Hegal K Charles

  • Posting keys for account determination for transaction EXC do not exist

    hi
    i am doing Sales order for 1 month,no error i have got
    but now i am getting error
    Posting keys for account determination for transaction EXD do not exist
    HELP

    There will not be any such postings called FI side / SD Side.
    Positng always done in Financial perspective only into Certain G/L accounts depends on configuration we did.
    As we know,
    To post Invoice Conditions in G/L accounts , we configure Account Determination . These tables will be communicated through Account keys maintained in Pricing procedure & in Account determination tables.
    To account the stock in Inventory, will configure the same in OBYC - FI/MM Account Determination.- this will be triggered through Movement type - Transaction key / General modifier / Valuation calss / Valution group code n other factors.
    In your issue,
              Which Postings you are referring to?
    In SO creation, Controlling documents will be created ( Ref: COPA - Controlling & Profitablity Analysis Customization)
    After PGI in Delivery: Inventory will accounted through OBYC settings
    After releasing invoice to Accounting, G/L accounts posted through VKOA settings.
    Hope ,now you provide exact information related to your query

  • Posting keys for account determination for transaction EXD do not exist

    hi
    i am doing Sales order for 1 month,no error i have got
    but now i am getting error
    Posting keys for account determination for transaction EXD do not exist
    HELP

    Hello,
    I have following suggestion to overcome this issue.
    1. In the t-code "FTXP", check for assignment of the G/L account for the posting key.
    2. Check out the SAP Note:200348.
    3. In t-code "OBCN",for the account key EXD, make sure that the value of posting indicator is 2.
    4. In t-code OBYZ, for the tax calculation procedures, change the key to EXD. The account keys in tax pricing procedures and SD pricing procedures Should be same.
    Regards,
    Sarthak

  • Posting keys for account determination for transaction ERS do not exist

    Dear All,
    When I try to create an accounting document for a billing document, the below error happened:
    Posting keys for account determination for transaction ERS do not exist.
    Could any one of you meet the issue before and give me some advice? Thanks a lot.
    Ray

    Dear,
        In your pricing procedure check whether any sales deductions / discounts condition type is maintained and against that maintain ERS account key.
    and Go to VKOA and maintain gl account against your Kofi and KOFK for  account key ERS.
    try and let us know
    regards,
    SUdhir

  • Transaction key / event key in account determination??

    hii
    I want to know what is transaction key and event key in account determination??
    Thanks

    HI,
    Transaction/event key (internal processing key) Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers. You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction. Account grouping (only for offsetting entries, consignment liabilities, and price differences) Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code. An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting". Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts. If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key. Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities. Valuation class of material or (in case of split valuation) the valuation type The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials. You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class. If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
    Regards
    KK

  • Transaction type for Account Determination

    This doubt in STO scenario:
    STO - between 2 plants - different company codes under same client
    Created STO from Receiving Plant in ME21N with document type NB
    Based on that STO, Created Delivery in VL10B from supplying Plant
    Tried PGI in VL02N from supplying Plant.
    Received the Error Message as below:
    Posting keys for account determination for transaction BUV do not exist
    Message no. F5598
    Diagnosis
    The posting keys necessary for account determination for transaction BUV 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 BUV.
    After working thru OBYC found that the transaction type BUV is missing.
    How to create the transaction type?
    Thanks in advance
    Vaidee
    Edited by: Vaidee on Mar 11, 2009 10:08 AM

    Thanks for the effort.
    Executed TCode OBYA.
    Entered the company codes.
    For Company Code 1 u2013 Receivable u2013 Debit posting Key u2013 86
    For Company Code 1 u2013 Payable u2013 Credit posting key u2013 96
    For Company Code 1 u2013 Receivable u2013 Debit posting Key u2013 86
    For Company Code 1 u2013 Payable u2013 Credit posting key u2013 96
    Tried to change the posting key to 89 and 99.
    Error message is :
    Enter posting key with account type D, K or S
    Message no. F4809
    Diagnosis
    You have specified a posting key which is defined for neither customer, nor vendor, nor G/L account postings
    Thanks
    Vaidee

  • 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

  • Posting Keys for Account Determination do not exist

    This doubt in STO scenario:
    STO - between 2 plants - different company codes under same client
    Created STO from  Receiving Plant in ME21N with document type NB
    Based on that STO, Created Delivery in VL10B from supplying Plant
    Tried PGI in VL02N from supplying Plant.
    Received the Error Message as below:
    Posting keys for account determination for transaction BUV do not exist
    Message no. F5598
    Diagnosis
    The posting keys necessary for account determination for transaction BUV 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 BUV.
    kindly give the solution and advance thanks.
    Vaidee

    Hi Vadee,
    Account Determination for BUV has not been setup for PGI.
    So , go to transaction OBYC and assign the account by double clicking BUV  and give u r chart of accounts and check whether the account has been maintained. If not maintain.
    If account has been maintained , select your account/valuation class and select posting keys push button and maintain the posting keys.
    Regards,
    Nani

  • Posting keys for account determination

    Hi all
    I'll try to post an sales ticket from Retail modul to SD module.
    I have this message error : Posting keys for account determination for transaction ZST do not exist                                                                               
    Message no. F5598                                                                               
    Diagnosis                                                                               
    The posting keys necessary for account determination for transaction Z
        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 ZST. 
    In VKOA transaction, I check and for me the account determination has been set.
    So I was wondering what's goes wrong with this.
    Appreciate your expert advise..

    HI,
    Please check wther In the pricing procedure ZXXX some conditions have account key ZXX.
    But in table T030B there is not any record with KTOSL = ZXX.
    Check note 1273471,1128659
    Regards
    Ravinagh Boni

  • 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

  • No entry for account key 1002 in HRA transaction key in Account assignment

    Dear sap-gurus,
    the following problem occured. When posting a document (s-modelling), system displayed an error that there is no entry for account key 1002 in HRA transcation key in SPRO Account assignment.
    The document's size is very big, it considers many lime items in it.  May be this happened because of this?
    In F1 for SPRO Account assignment we have:
    In this step, you assign a document split account to an account key. This is a clearing acount (Transaction HRA) in Accounting.
    For various reasons, payroll data that is formatted for posting to accounting must be split into several documents per posting run. In Human Resources (HR), key 1001 is used for the breakdown of documents. A breakdown occurs if:
    There are several company codes
    There are different posting dates
    There are postings to G/L accounts, customer accounts, vendor accounts
    This is specified in the step Create Posting Variants (for example, document breakdown for expenses and payables)
    The document split account that is stored under the key 1001 is also used to clear the balance within a G/L account document for each business area.
    An additional split may be required depending on the size of the document in Financial Accounting. In this case, the clearing account specified under account key 1002 in transaction HRA, is used as the document split account.
    Further notes
    To avoid problems in current operations, it is advisable to set up a document split account even if a document breakdown is not necessary. In this way, you can avoid having to set up the system at short notice if changes are made to the settings or if there is an increased number of postings, or if cross-company code transactions occur.
    We have an entry 1001 and a clearing account for postings between several company codes. What are we supposed to do? How to avoid this error and post the documents to FI? Please, help!
    Best regards,
    Eldar

    Hello,
    How did you resolve this issue? Any inputs anyone.
    John

  • Transaction Key GBB/ Account grouping

    Dear all,
    I am configure intergation FI with MM.
    I don't know how to accounting entries generated in transaction key GBB.
    Please tell me accounting entries of AUA, AUF, AUI, BSA, INV, VAX, VAY, VBO, VKA, VKP, VNG, VQP, VQY, ZOB, ZOF
    and give me examples
    Thank in advance
    Minhtb

    Dear Tran Binh Minh ,
    Please find the explainations:
    AUA
    At the time of the manufacture of the Goods
    "Stock A/c Dr
    To Cost of Goods Manufactured"
    AUF
    At the time of the manufacture of the Goods
    "Stock A/c Dr
    To Cost of Goods Manufactured"
    BSA
    At the time of the initial upload of the stock into SAP during cutover vide t code MB1C (Movement Type 561)
    "Stock A/c Dr
    To Initial Clearing account"
    INV
    At the time of inventory differences, i.e in case the physical inventory is greater or lesser than the system stock
    "Stock A/c Dr / Cr
    To Inventory Difference Account Dr / Cr"
    VAX
    At the time of sales ( Delivery)
    "Cost of sales A/c Dr
    To Stock Account"
    VAY
    At the time of sales ( Delivery)
    "Cost of sales A/c Dr
    To Stock Account"
    VBO
    For the consumption of stock at the sub contractors place
    "Consumption of Goods with Sub-Contractor
    To Stock account"
    VNG
    For scrapping
    "Stock A/c Dr / Cr
    To Scrapping expense acount Dr / Cr"
    ZOB
    "For goods receipts without purchase orders (Movement type 501)
    "Stock A.c Dr
    To GR / IR account"
    ZOF
    "For goods receipts without Production orders (Movement type 521 / 531)
    "Stock A/c Dr
    To Cost of Goods Manufactured"
    Assign Points if useful.
    Regards
    Venkatesh

Maybe you are looking for

  • Problem using the tag validatorMessage on inputText

    In essence when there is an error i want as output what i write as string on validatorMessage. <h:inputText id="data_scadenza" value="#data_scadenza}"  validatorMessage="Data scadenza errata" > <f:convertDateTime pattern="dd/MM/yyyy" /> </h:inputText

  • External Wiki Security

    I am hosting a Wiki externally. It works fine, but I have a security concern. I have created a group for external Wiki access "only". So I thought. I created a virtual NIC with an IP of 192.168.10.9. I created a new "Site" in the Server admin under t

  • Pacman: sent interrupt and now thinks its up to date.

    Its a little long, so I've pastebin'd it. http://pastebin.com/m4465efec So, I understand stuff gets corrupted while downloading.  That's why one always checks the [md5,sha1,sha256]sum of what you are downloading.  But tell me.  Did I hit the interrup

  • Maintenance dialog

    Hi all,        While working with Tcode KES1 i got tthe following error message " The maintenace dialog for T2513 is incomplete or not defined" Help me to solve this issue, Thanks in advance, Charumathi.B

  • Can I create recovery disks using my laptop HD as external drive?

    My Thinkpad T420 hard drive crashed in a really bad way. I can't load windows (7) and windows repair says it can't help me. I removed my hard drive and put it in a usb enclosure and connected it to a different pc. I can see the recovery folder/drive