Transaction key FRL and FRN

hello all,
In case of goods recipt of subconracting po.the transaction event key FRL or FRN is hitted as sap standard process.
FRL External activity.
FRN Incidental costs of external activities.
IN OBYC SAME G/L IS assignes to both keys.i want to know that,the value goes to this g/l is loaded into inventory or goes anywhere?
What is the use of these transaction key and how it effect the inventory value?
thanx in advance.
regards
SIMRAN

Hi Sumit,
Kindly look into the note 108844 which explains the posting logic foe subcontracting with Purchase ACcounT Management
active
If the purchase account management is active, and if is GR or IR for the
subcontract order are concerned, the system uses posting keys FRL and
BSV instead of posting keys EIN and EKG.
>> If the purchase account management is active, and if is GR or IR for
>> the subcontract order are concerned, the system uses posting keys
>> FRL and BSV instead of posting keys EIN and EKG.
= no postings to EIN/EKG/FRE  -> EINEKGFRE = 0
regards,
Lalita

Similar Messages

  • Change GL account in OBYC for transaction keys GBB and BSV

    Dear Logistics Colleagues
    I would like to have your opinion on the following topic:
    I have an request to change an GL account in account determination (OBYC) for transactions:
    - GBB > Offsetting entry for inventory posting
    -BSV > Change in stock account
    What cutover should I consider or which actions should be executed before implementing the change?
    Many thanks in advance for your help?
    Regards,
    Mohamed

    Hi,
    Just check all the orders whose GR is done, there LIV also done, for the scenario where this key will be utilized,
    BSV - change in stock account, this will hit in subcontracting process. When you do GR against 101 mvt type this BSV will get credit, BSV is the balancing account to BSX for Finished goods, this amount goes to P&L accounts
    GBB - Most of the time this will be 0, because it is for offsetting entries, check there is no balance in this GL,
    If you want create OBYC for this 2 for some new valuation class then i do not think you need to look at cutover

  • Different GL for Transaction/Event Key FRL

    Hi expert,
    I hv an issue for subcontract processing.. as defined in SAP the GL for Subcontract is :
    Dr. [FRL] External Service Fee
    Cr. [WRX] GR/IR
    Dr. [GBB-VBO] Inventory
    Cr. [BSV] SP components for refurbishment
    but at the other requirement, the GL for subcontract need to define as the following :
    Dr. [FRL] External Service Material
    Cr. [WRX] GR/IR
    Dr. [GBB-VBO] Inventory
    Cr. [BSV] SP components for refurbishment
    So, how can i define the differences. As i know, SAP just give one transaction/key FRL with one GL account.
    Is there any solutions for this issue?
    i think that it can be changed by defining a new mov.type copy from 101 to combine with new transaction/event key to differ the GL account, but the matter is i can't find any acc.modification FRL assign in this mov.type so i can't change it with new transaction/event key on it....
    please help mee...
    Regards,
    AJ

    Dear Kumar,
    i ll explain it more details..
    the material is the same.. the business process is that the material can be repaired and can be buy by using procedure exchange parts program.
    when it is repaired.. the requirement for the GL is :
    Dr. FRL External Service Fee
    Cr. WRX GR/IR
    Dr. GBB-VBO Inventory
    Cr. BSV SP components for refurbishment
    and when it is exchanging parts program the GL is :
    Dr. FRL External Service Material
    Cr. WRX GR/IR
    Dr. GBB-VBO Inventory
    Cr. BSV SP components for refurbishment
    and certainly, the material can only be assigned with one valuation class.. logically one valuation class can't be assigned with more than one GL account in one trans/event key especially FRL..
    So how it can be solved? or is there any solution by creating a new movement type for Godds Receipt to move the GL to another one.. thanks

  • Transaction keys and debit/credit indicator.

    Hello Gurus,
    The transaction key '000' is a receipt. so it should have only 's' or 'h' for the 0dcindic(debit/credit indicator) field. but in one record i see transaction key '000' and dcindicator 's' and in some other record, i see transaction key '000' and dcindicator 'h'.
    Is this correct?
    please advice.
    Thanks,
    Kris.

    Look at the actual receipts.  Most probably some are credits and others debits...  Receipts can be both.

  • Transaction Key in F.19(Analyze GR/IR accounts)

    Hello,
    In the F.19 output, I see transaction key BNG and GNB. Can anyone tell me the difference between the two.
    In F.13(Automitic clearing without definition of clearing currency), how do I clear out the documents having transaction key GNB?
    If I run the F.13 giving the document number, the error log shows 'No clearing procedures were carried out'.
    Can anyone tell me if I am doing something wrong?
    Thanks,
    Rugmani
    Edited by: Rugmani Rajan on Sep 15, 2008 5:14 PM

    Let me explain my case a little better:
    We have POu2019s that were created for certain vendor purchases. I created GR and IR for these POu2019s. However, for some business reason the vendor clearing could not be done by the regular F-44 transaction. Instead I created vendor credit memo using F-41 and gave the invoice number as reference. This credit memo has no assignment reference (ZUONR). So now when the F.19 is run for the AP accrual account, this credit memo appears in the output. I am trying to clear this credit memo. As I saw the option of u2018Document Numberu2019 in F.13 selection screen, I assumed I could use the document number.
    Please let me know how to proceed in this case.
    Thanks,
    Rugmani

  • Transfer Posting 412 E triggers transaction key AUM

    Hi everybody,
    I'm trying to do a transfer posting ( 412 E) , every data ("dest" and "from" as material, plant, batch and storage location ) are the same. But the system is triggering the transaction key AUM, and I dont know why. I 've checked the material price (MAP) and it didn't change.
    Pls your help!!!

    The transfer posting made with the movement type 412 E is a reversal movement type (for the movement type 412, T156-XSTBW = X; so the movement type 412 is a reversal movement). The valuation logic for transfer postings made with reversal movements is explained in the note 180503.
    The material, valuation type and sales order item has an entry in   table EBEW . Table EBEW stores the valuated sales order   stock, similar to   MBEW, but this type of stock has its own pricing. All goods movements   with movement type 411/412 special stock E (valuated) will be done   the price determination of table EBEW.
    As explained in the attached note 180503 when you make transfer  posting with movement type 412 and special stock indicator E into the  sales order stock from the valuated stock the  goods movement is now  valuated with the price of the receiving valuation segment of the   of the sales order stock and not with the price of the issuing valuation segment.
    The difference between the valuation in issuing segment to stock account and the valuation in receiving segment to stock account will be posted to AUM account.

  • How to know debit and credit transaction key for movement type

    Hi,
    With T. code OMWB  account assignment simulation we can see all the accounts which are involve for debit and credit enties   but I want to know is there any T. code or method  with which we can know  which transaction key will be debit and which will be credited  like  for movement type  101 the transaction keys are GBB, BSX  WRX  etc.  i want o know whethere GBB a

    Hi,
      Thanks for your reply,  but with this we can see the for GBB which is the credit account and which account is use for debit entry,  like this for all transaction event key like WRX, BSX etc. we can see the G/L account use for Debit and credit,  but i want to know for particular selction of Plant, material , movement type,  my GBB account will have entry in debit account or credit account  How we can know this.
    regards,
    zafar

  • New transaction key with the posting key 24 and 34

    Hi,
    i want to create a new transaction key with the posting key 24 and 34.
    the corresponding table is T030B.
    but what is the Tcode/ IMG path to create it?
    Regards,
    Swetha

    Hi,
    Go to FBKP. Click on  Automatic Postings.
    Suppose you want to see the Exchange Rate diff. then click on it. You will see the transaction. Suppose KDB. Then double click on it. Now click on posting keys. The same will be defined in the table which is given by you.
    Regards,
    Jigar

  • Movement Type and Process/Transaction Key

    I have scoured SDN for a clear definition on this question but haven't found anything on this yet.
    I need to know, in Inventory, what is the difference between a Movement Type and Process Keys.
    Where can I see what Movement Types are associated with what Process/Transaction Keys.

    I have scoured SDN for a clear definition on this question but haven't found anything on this yet.
    I need to know, in Inventory, what is the difference between a Movement Type and Process Keys.
    Where can I see what Movement Types are associated with what Process/Transaction Keys.

  • Transaction Key and Acct Modifier Key

    In automatic account determination , whats is the difference between transaction key and account modifier key?
    When we need to define account modifier key?
    POINTS WILL BE REWARDED FOR ANSWERS.
    Thanks in advance.

    Hello Venugopal,
    Transaction / Event Key
    Key allowing the user to differentiate between the various transactions and events (such as physical inventory transactions and goods movements) that occur within the field of inventory management.
    The transaction/event type controls the filing/storage of documents and the assignment of document numbers.
    Account Modifier Key
    Account grouping code is only used with offsetting entries (GBB), consignment liabilities (KON), and price differences (PRD).
    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.
    Hope this helps.
    Regards
    Arif Mansuri

  • Transaction Keys Description in MM(BSX, GBB etc)

    Hi all,
    I was going through many documents for FI/MM Integration but i could not understand what exactly are these transaction keys used for. for ex if thr is a movement type 101, GR agnst PO. then we have two things to do go to BSX- give the debit account and go to GBB-AUM to credit, if i am not wrong. I appreciate if someone please explain the usage in normal terms quoting some examples.
    Thanks
    Shriya

    Hi,
    some of the key descriptions -
    Expense/revenue from consumption of consignment material (AKO)  
    •     Expenditure/income from transfer posting (AUM)                   
    •     Provisions for subsequent (end-of-period rebate) settlement (BO1)              
    •     Income from subsequent settlement (BO2)            
    •     Income from subsequent settlement after actual settlement (BO3)      
    •     Change in stock (BSV)                  
       Stock posting (BSX)  
      Revaluation of "other" consumptions (COC)     
       Small differences, Materials Management (DIF)     
       Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)                        
    External service (FRL)     
    External service, delivery costs (FRN)                            
    Offsetting entry for stock posting (GBB)      
    -   AUA:     for order settlement                                                 
    -   AUF:     for goods receipts for orders (without account assignment)  and for order settlement if AUA is not maintained                    
    -   AUI:     Subsequent adjustment of actual price from cost center  directly to material (with account assignment)  
    -   BSA:     for initial entry of stock balances      
    -   INV:     for expenditure/income from inventory differences  
    -   VAX:     for goods issues for sales orders without account assignment object (the account is not a cost   element) 
    -   VAY:     for goods issues for sales orders with   account assignment object (account is a cost element)
    -   VBO:     for consumption from stock of material provided to     vendor    
    -   VBR:     for internal goods issues (for example, for cost     center)  
    -   VKA:     for sales order account assignment       (for example, for individual purchase order)  
    -   VKP:     for project account assignment (for example, for individual PO)
    -   VNG:     for scrapping/destruction                                            
    -   VQP:     for sample withdrawals without account assignment
    -   VQY:     for sample withdrawals with account assignment   
    -   ZOB:     for goods receipts without purchase orders (mvt type 501)
    -   ZOF:     for goods receipts without production orders  (mvt types 521 and 531)                                                 
    Regards,
    Sridevi
    <i><b>* Pls. assign points, if useful</b></i>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/sridevi+pattabiraman">me!</a>

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

  • Key fields and non-key field of condition table

    Hello Gurus,
          what is key fields and non-key field of condition table?
    thanks very much!

    Key field
    Each condition table contains keys that can be used for creating dependent condition records.
    for example let take condition type PR00.
    PR00 uses access sequence PR02 .
    Access sequence PR02 has following tables associated with it namely 304, 305 & 306
    When you create a conditon record for PR00 with transaction VK11 or VK31, you have a button 'key combination' which is nothing but fields associated with tables 304, 305 & 306.
    In brief, Condition records are always created using specific keys. Condition tables are used to define the structure of the keys of a condition record.
    Non key field
    For example take condition table 144 - sales deal basic data.
    Table 144 is associated with access sequence PBUD.
    If you check the fields associated with this table (click technical view button), there are three fields at bottom which do not have 'key' check mark -KDATU, PLTYP, KSTAF
    So, when you create a condition record for PBUD, system does not propose these 3 fields in 'key combination' and hence are non key fields.
    Please reward points for good answers as this would help increase the total donation that SAP will make to the United Nations World Food Programme.

  • How to create Transaction keys.

    Hi All,
    I am MM consultnat
    I want to create a new Transaction keys in account determination.
    kindly let me know the steps to create....
    hope to hear back from you all.
    Thanks&Regards,
    Chand

    Hi,
    Use transaction OMGH and create a transaction key your want
    Regards,
    Chintan Joshi

  • Creation of new transaction keys

    hi
      experts this is ramakrishna new to this forum
      when i am performing inwards goods movement for the material it triggers bsx transaction key and it post to the respective G/L account. my client requirement is  create new trans key say yyy and it triggers my G/L account.
    CAN any on esuggest me how to do this

    HI,
    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.
    If you create it you have to make changes in Movement type level as well in following path which is not suggestible
    SPRO -> MM -> Valuation and Acct Assignment -> Acct Dtermination -> Define accoutn grouping for movement types.
    for more info check following link
    [http://help.sap.com/saphelp_46c/helpdata/en/12/1a39516e36d1118b3f0060b03ca329/content.htm]
    Regards
    Kailas Ugale

Maybe you are looking for