BSX / WRX transaction key in OMWN (Account grouping)

Hi There,
I'm trying to understand AAD.
My confusion is, I do not see BSX / WRX transaction key for MVT 101 (considering all permutations and combinations) in OMWN .
As we know, when we perform 101, below accounts come to picture.  So where this MVT 101 will be linked to BSX & WRX.
Goods Receipt Against Purchase Order:101
Movement Type: 101
Accounting Entry:
Inventory of Raw Material Debit [BSX]
GR/IR (Goods Receipt/Invoice Receipt) Credit[WRX]
Thanks,
Udaya

Hi,
   Account grouping is not available for BSX and WRX. It available for GBB, PRD, and KON only. Refer the help doc:  Define Account Grouping for Movement Types - Valuation and Account  and
Assignment - SAP LibraryConfigure Automatic Postings - Valuation and Account Assignment - SAP Library
Regards,
AKPT

Similar Messages

  • Transaction Key for Purchase Account

    Hi Dear All,
    I want ti define another Purchase account key for frieght like FRE.
    How to creat it?
    Regards
    Gitesh

    Hi Gitesh,
    We won't assign Purchase A/C keys in Pricing Procedure.
    Normally we activate Purchase A/C posting @ company code level under the following settings.
    SPRO - MM - Valuation and Account Assignment - Account Determination - Account Determination Without Wizard - Purchase Account Management.
    As I have already mentioned above system uses the Standard transaction key EIN & EKG for Purchase A/C postings.
    I dont think we have the option to change this standard one.
    Now if your requirement is to use a different transaction key instead of FRE then create a new trans.key & assign the same to the freight condition type in Pricing Procedure.
    Hope its clear.
    Thanks & Regards,

  • Assigning more than one G/L account to transaction key WRX

    Can any one tell me where we can create General Modification keys in  MM-FI integration
    As i need to assign more than one GL account for transaction key WRX (GR-IR)Clearing account.
    There may be one valuation grouping code with different General modifications thereby we can assign more than one G/L account to WRX transaction key.
    Example:
    Valuation grouping code or valuation modification = IN
    General Modifications: I01,I02,I03,I04..
    General Ledger Accounts: 240940000,240940001,240940002,240940003
    IN I01 240940000
    IN I02 240940001
    IN I03 240940002
    IN I04 240940003
    But , I am unable to find, where we can define these general modifications ( I01,I02,I03)....
    If any one knew please let me know...
    Ramesh B

    Hi
    Tcode: obyc, double clickon WRX event key, slect Rules ....you can find General Modification option>
    REgards
    ss
    Assing the points if useful

  • Clarification on Account grouping -OMWN for 101 movement type

    Hi SAP MM gurus,
    In OMWN - Account grouping , I am not able to find any entry for 101 (Goods receipt for Purchase order B and with no consumption posting ) with Value and Quantity updates . There are entries for 101 movement type with special stock indicator but not able to find any entry for standard good receipt for Purchase orders ( No Special stock Indicator , Value and Quantity update checked , Movement type indicator B and No Consumption posting ). There are no issues with the accounting posting for goods receipt with standard purchase order with BSX being debited and WRX being credited. I am trying to understand the logic for this posting and I am not able to understand from where (customization settings) this posting is derived from. May I request your valuable inputs in understanding this logic.
    Thanks in advance for your immediate response.
    with regards,
    Anandj

    Hi there,
    Not sure where you want to go... but here is a tip
    Would it make sense to have value and qty update and no consumption ? it can either one or the other but not both.
    Now in prg there are further checks that makes other option possible like a GR for PO that is not valuated.
    Remember that these key determination behind the account grp / TE key is a kind of black box where the prg is hardcoded to sort out what keys to take.
    I hope this helps... Cheers

  • MIRO TRANSACTION - BSX TRANSACTION KEY TAKE PLACE

    Dear Consultants,
    While posting MIRO document, the BSX transaction key is taking place & posting key is 89 apart from WRX transaction key, the figure of (MIRO )WRX transaction key ie the automatic G/L a/c assign in OBYC is matching with WRX transaction key in MIGO.
    pls note that BSX transaction key i.e automatic G/L posting is taking effect in MIGO.( 120000Rs)
    My question is why BSX transaction key ( hardly 200 Rs ) is taking place in MIRO posting, wht was the reason & further there is no invoice condition difference from PO & MIRO.
    Anticipating your advices.

    Hello
    Posting key 89 is for debit and BSX transaction gets debited at the time of MIGO as stock account is getting debited at the time of MIGO.
    WRX is GR/IR clearing and it gets credited at the time of GR.
    In normal cases the debit and credit entry will be for the same amount unless configured otherwise.
    At the time of MIRO WRX gets debited and vendor account gets credited. As you are saying BSX is also coming into play at the time of MIRO, that means some amount is getting into the material accounts in the line item.
    It can happen if you have given unplanned delivery costs (should be Rs.200) and is configured to be distributed among the material account.
    Hope it is clear.
    Regards
    Gregory Mathews

  • Miro posting - BSX transaction key take place

    Dear Consultants,
    While posting MIRO document, the BSX transaction key is taking place & posting key is 89 apart from WRX transaction key, the figure of (MIRO )WRX transaction key ie the automatic G/L a/c assign in OBYC is matching with WRX transaction key in MIGO.
    pls note that BSX transaction key i.e automatic G/L posting is taking effect in MIGO.( 120000Rs)
    My question is why BSX transaction key ( hardly 200 Rs ) is taking place in MIRO posting, wht was the reason & further there is no invoice condition difference from PO & MIRO.
    Anticipating your advices.
    Edited by: vivek tripathi on Sep 26, 2008 6:55 AM

    Hi
    There must be some difference in the PO Value and the Actual invoice received from the Vendor. This difference can be due to various reasons, e.g. difference in Basic Value, or difference in Sales Tax, or even difference in amount of excise duty as that as per the PO condition and as captured in J1IEX
    regards
    Parag Bhargava

  • Define Account Group for Matetial Types

    Hi All,
    I am trying to understand how Movement types are linked to account assignment.
    In IMG - MM - Valuation and account assignment - Account determination - Account determination without wizard (OMWN)
    In this transaction or setting i do not see my movement type 101 linked to BSX and WRX transaction key, however when i do Goods receipt with 101 mvt type it is hitting inventory accounts in BSX,
    However i see 101 mvt type linked to Transaction key KBS.
    How is this linkage working.
    Let me know your inouts here.
    Thanks,
    Regards
    Raghavendra

    Hi,
    When Goods movement (101) is posted, accounts in BSX is hit.
    However in OMJJ setting i do not see 101 movement type being linked to BSX.
    Can you let me know is there any relationship here.
    Thanks,
    Regards
    Raghavendra

  • How many transaction key used for Service PO

    Hi,
    Please let me know, how many transaction key used for Service PO...
    In OBYC, we have maintained GBB & WRX Transaction key's for Service PO, Is there any other Transaction key skip???
    Please guide...

    Hi,
    GBB is used for Offsetting entry for inventory posting but for Service procurement WRX Transaction key is used for GR/IR clearing-service.
    NOTE: You may use WRX with new account modifier ZZZ  to triggers GR/IR clearing-service only for service procurement where you need to post all separate GR/IR clearing- material , GR/IR clearing-asset and GR/IR clearing-service and can done with user exit.
    #But in special case GBB can be used with VBR key or copy of VBR as ZBR for default G/L account foe service PO.
    For more check the link:
    http://www.bluemarlinsys.com/ns/0603-03.asp
    Regards,
    Biju K

  • Transaction keys in material document

    Hi,
    While Displaying the material document, i am seeing accounting entries.
    There i am unable to see the Transaction keys for each account.
    How to view Transaction keys here.
    Utsav...

    Hi,
    Re:
    "Above the entries, you can choose the columns to be included in layout. Choose Transaction from the layout which shows the transaction keys for FI entries"
    I have selected option for change layout....But there i can not find field for transaction keys ...
    These are the fields which i can add in the current layout:
    Clearing Document
    G/L Account
    Account Type
    Debit/Credit Ind.
    Business Area
    Trading part.BA
    Withholding Tax Code
    Tax Jurisdiction
    Amount in LC
    Value date
    Assignment
    Text
    Trading Partner
    Cost Center
    Order
    Billing Document
    Sales Document
    Sales Document Item
    Schedule Line Number
    W/o cash disc.
    Payment transaction
    G/L Account
    Branch account
    Terms of Payment
    Baseline Payment Dte
    Days 1
    Days 2
    Days net
    Discount Percent 1
    Discount Percent 2
    Payment Method
    Payment Block
    Fixed
    Invoice reference
    Fiscal year
    Line item
    Collective invoice
    B/e payment request
    Dunning key
    Dunning block
    Dunning level
    Dunning Area
    Plant
    Purchasing Document
    Item
    Blocking reas. price
    Blocking reason: qty
    Block. Reason: Date
    Blocking reason:OPQ
    Blocking reas: proj.
    Manual Block. Reason
    Reason code
    Profit Center
    Joint Venture
    Equity group
    Billing indicator
    Recovery Indicator
    Partner
    Contract Type
    Contract Number
    Real Estate Key
    Reference Date
    Commitment Item
    Network
    Task list number operations
    Counter
    Pmt meth. supplement
    Funds Center
    Fund
    Tax company code
    Reference key 1
    Reference key 2
    Payee/er
    Reference key 3
    Pmnt currency
    Pmnt curr. amnt
    Business Place
    Section Code
    Credit control area
    Grant
    Earmarked Funds
    Document item
    Partner Profit Ctr
    Transaction Type
    Planning level
    Planning Group
    Asset value date
    Personnel Number
    Investment ID
    Sp. G/L assignment
    Discount base
    House Bank
    Partner Bank Type
    SCB Indicator
    Supplying Cntry
    Settlmnt period
    Insurance ind.
    Insurance date
    ISR Number
    ISR Reference Number
    Check Digit
    Exemption number
    Withholding tax amnt
    Wthld.tax-exempt amt
    Material
    Quantity
    Base Unit of Measure
    VAT Registration No.
    Country of destination
    Supplying country
    Flow Type
    Negative posting
    Activity Code GI Tax
    Region
    Distribution Type
    Payment reference
    Functional Area
    Local Currency
    Currency
    Tax Amount
    G/L account name
    General ledger amount
    Operation/Activity
    General ledger currency
    Correct Item
    Alternative account no.
    Usage document
    WBS element
    Segment
    Partner Segment
    Partner Func. Area
    Sender cost center
    Partner Fund
    Partner Grant
    Produktionsmonat
    I I tried all the fields , but none is showing the Transaction keys.
    Utsav...

  • 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

  • Account grouping/Transaction keys PRD/DIF

    Hello Gurus
    I have a situation that some MIRO posting are using PRD and some are using DIF transaction keys. For some reason  The postings with DIF are not picking up the material thus resulting in putting dummy profit center.
    Please advise the difference between PRD and DIF and how  these are triggered during MIRO transactions.
    Many thanks
    MSJ

    HI Jayaram/Surabhi
    The see what you are saying and it make sense after I read your reply.
    The reason that I say that few MIRO postings are using DIF is because the posting key 83 debit and 93 credit are defined in the OBYC for DIF.
    So when I looked at the document in the Vendor acct (after I post MIRO), I see the profict center and material missing for posting keys 83 and 93  for some postings.
    Wheras I can see the profict center and material for posting keys 86 and 96 for some othe MIRo postings which use these posting keys.
    Of course  all these postings are generated automatically
    So my question is where do I make a setting to have the material and profict center generated for posting keys 83 and 93.
    I appreciate your help on this critical issue for me.
    Please advise.

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

  • Assign GL account in two transaction keys

    Hi!  In OBYC,  is it possible for us to assign the GL account twice?  We would like to use a specific GL account in two Transaction Keys.. Is that possible?
    Thanks so much!
    Regards,
    Paula

    Hi,
    BSX- Account is Balanc sheet account.
    PRD is P& L Account-- the same varient G/; account only can assign to twice.
    Check in FS00. the G|L account  account group.
    SAM

  • Transaction Key/ Account modifier Key

    Hi
    Can any body explain relation :
    NEW material group( Type is ROH)-> new valuation class-> GBB( TRANSACTION KEY)-> VBR( ACCOUNT MODIFIER KEY)-> G/L account
    Significance of them wrt each other and config steps necessary.
    Which transaction key we should select for posting related to newly created material group.
    Say for ROH, Consumables, services etc.
    Regards Komal

    hi,
    1. In Material master, Accounting view we will assign the valuation class,  For material type ( IN OMS2 transaction), we will give Account category referance.
    2. for STock account it is BSX transaction key.
    follow this link:
    http://help.sap.com/saphelp_erp2005/helpdata/en/93/744148546011d1a7020000e829fd11/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/93/744148546011d1a7020000e829fd11/frameset.htm
    hope this may help you,
    Regards,
    Srinivas

  • Account grouping for account key PRD

    Hello Gurus,
    Is it possible to add new account grouping or modifier ( standard SAP provides Blank, PRA,PRF) to account key for Price difference account  PRD in  OBYC (automatic account determination) transaction.
    The requirement is we are using PO condition type for freight and surcharge which is to be paid to a different vendor . In purchasing pricing procedure condition types can be mapped to freight and surchage account keys, in turn mapped to different accounts in OBYC
    In the case of invoicing if  difference in freight and surchage value occurs, system post both balance to PRD account through account modifier blank.So its difficult to identify what caused the account price difference.
    If we can add new account grouping to how to attach to the invoice verification procedure?
    Any help is appreciated
    regards
    Megha

    Hi,
    Group Modifier Key which has a different meaning depending on the procedure. It is used   to differentiate account determination. The key's meaning is predefined in the SAP system and cannot be changed.                               
    For offsetting entries for inventory postings, you enter the key which 
    is assigned to the movement type and posting string.                   
    So the meaning here is you can define your own keys but it should be assigned to the Movement type and posting string which is very difficult as these two affects all types of businesses.
    Thanks
    Krishna.

Maybe you are looking for

  • Problem with ojdbc14.jar (oracle10g Rel. 2 driver) in updating a BLOB field

    Hello All, Our web application uses oracle10g Release 2 jdbc driver with websphere 5.1.1.4 and oracle 9i. When it tries to update a BLOB field in the database updation is successful but it is updating that field with a null value. So rest of our appl

  • Urgent :ORACLE.FDK.UnexpectedError --how to rectify this error

    Hello, I am getting the following error when I am running a standalone java program, where I am trying to list the folders in a container. =========================== log created on console =========================== FdkException: Error Code: ORACLE

  • CROSS TAB PRINTING IN PDF PROBLEM

    Post Author: peachpx CA Forum: General Hi, My report uses a Cross Tab query with multiple lines for each value. Originally, I only get one line for Total In.  I modified Total In to include three lines Total Into Final, Total Into Initial and Total O

  • Socket in Palm OS with MIDP

    Hallo, Has anyone create a Socket with MIDP ? If I execute Connector.open("socket://MyServer:32123"); I receive a IOException without any message. What make I wrong? Volker

  • Creative Clouds App won't work!

    Everything else works for me except the app when it says "download error" and then choose "get help" or "try again" which I have printed about 1000 times. I can not update my adobe programs which I have to do. There is no help available in Swedish an