MM role in Account determination

hii
What are major MM consultant roles in account determination.??
Explain in detail...?
Thanks

Hi MM Group,
SAP MM Role in Account Determination :
This account determination is for MM settings u2013 Rajgeetha
Account determination is based for combination of valuation grouping code, general modifier/account modifier, valuation class in SAP MM.
This will be defined for particular transaction event key. Transaction event key will inturn be defined for each movement type of SAP MM.
Basically GL account are assigned for certain combination of above.
To put down in flowchart format-
- Movement type-
- Transaction event key
- GL account determination (one debit and one credit)- based on below combination
- Valuation grouping code (see definition below)
- Account modifier (see definition below)
- Valuation class (see definition below)
SAP will see transaction is made in MM, it searches the transaction event key from movement types. Based on valuation grouping code, account modifier and valuation class, determination will be done for GL account for debit and credit.
                                                    Some definitions and assignments
1) SAP MM Valuation grouping code: It is maintained as part of plant configuration same for all plants within company code having same chart of account.
This will be applicable only if valuation control is active for organization
2) SAP MM Account modifier: This is defined in each movement type. There may be more than one account modifier per movement type based on combinations of different special stock, movement indicator, consumption type.
3) SAP MM valuation class: This is maintained in material master. Material type is taken from material master. Account category reference is taken from material type which in turn is assigned to valuation class. GL account are assigned to valuation class
Example:
Material 1016101 is received in stock for plant SEPC by movement 101 in SAP MM.
1) Valuation class determination from material master of 1016101.
2) Valuation grouping code determination based on plant SEPC
3) Account modifier will be taken from movement type 101
4) Transaction event key will be always BSX for inventory posting. (that is programmed) and also defined in movement type
5) In account assignment, for combination of above GL account determination as we saw in above hierarchy.
Hope, it is useful for you,
Regards,
K.Rajendran

Similar Messages

  • SD tax G/L account determination

    First, I am not a Finance person nor do I know a lot about tax configuration.  My background (relevant for this issue) is in S/D pricing and associated account determination.  This is an S/D tax calculation and account determination issue for the United States.
    I am attempting to generate a “use” tax in an internal service order and then to populate the correct G/L account(s) with these tax values.  The service order, which is really just a sales order,  generates a statistical value for the basis and then I have pricing condition types (condition class = “D” (“taxes”), condition category = “D” (“Tax”)) specified in the pricing procedure.  These “tax” condition types are correctly calculating the tax amount.
    Normally, to point to the correct G/L account for a pricing condition type, you would configure Account Determination within S/D.  The simplest form would be the usage of the account key.  The account key would be specified in the “AccKey” column and account determination configuration would point this key to the correct G/L account.
    I understand (both from my own very recent experience and also from some of the information I have read on the internet) that things might be a little bit different when determining a G/L account for tax.  Originally I specified two different account keys in the pricing procedure for the tax condition types (normally I would have specified just one).  I specified MW1 through MW4 in the account key column for all 4 tax condition types and MWS in the accrual column.  My intent was to update the tax expense account from MW1 – 4 and the tax accrual account from MWS (I realize I might have this backward).
    When I created a billing document, SAP would not create the accounting document.  It indicated (from my recollection) that it was missing a tax code for the G/L account for the first tax condition type (“YTX1”).  Cutting through the history, it appears that SAP needs this code to point to the correct G/L account for S/D.  I also learned that there is a tax code field in the tax condition record (VK11) where you specify this code.
    I am actually familiar with the configuration and setup for use tax for A/P vendor invoices.  I had to perform this  setup very recently.  In short, I know that the tax code determines what the tax rates will be and also determines the G/L accounts.  I know how to setup a situation for tax accrual (this is setup found in tax code U1).
    My questions are the following:
    1) Is it true that I have to use the tax code to determine the G/L accounts for taxes generated in an S/D pricing procedure?  Is it possible I am doing something wrong in the S/D account determination (at the moment, not quite sure what this would have been)?
    2) Is it possible that I am adversely affecting account determination by specifying an account key in the accrual column of the pricing procedure for the tax pricing condition types?
    3) If we do have to specify a tax code in the tax pricing condition records in order to use the FI tax procedure to point to the correct G/L account, do we also specify the tax rates in this FI tax code or do we still specify them in the S/D tax pricing condition records?  It does not make sense to have to specify these rates twice.  In short, what does SAP actually use for tax calculation?
    Thanks a lot – Ed Seigler

    Hello Edward,
    The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
    Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
    SAP supplies a tax calculation procedure for each country. The procedure comprises a list of all common tax types with rules for tax calculation.
    You have to define a separate  tax on sales/purchases code for each country in which one of your company codes is located. Each code contains one or more tax rates for the different tax types.
    Tax codes are actually configured in FI, but they play a significant role while creating tax condition records for a particular condition type.
    Account keys in the account determination procedure connect the condition types to the relevant GL accounts. It doesnt have any impact on tax calculation. Its a procedure that is purely used to map GL accounts to the condition types.
    Finally, i would suggest you to check at the condition record level, whether you have assigned the correct tax code to the appropriate condition type to rectify the error.
    <b>REWARD POINTS IF HELPFUL.</b>
    Regards
    Sai

  • Valuation and Account Determination...

    Hello,
              Can anyone help me to get some of the functional implementing questions on "Valuation and Account Determinationa" ....
    Thanks
    Priyanka

    Hi,
    In SAP every movement of goods is followed by one movement type and movement type trigged transaction event keys. G/L account assignment and G/L account assigned to transaction event key (OBYC). GR & IR will updated by movement of goods only. In Account Determination, respective G/L accounts assigned to your chart of account,relevant to business transactions keys(Example:BSX,PRD,FRE,GBB),Account modifier(Example:BSA,VBR) and Valaution Calsss.If all are assigned then you would not face any problems during your posting of GR,IR etc..........
    Configuration of Automatic Account Determination with T.Code are as follow:
    1.OMSK: valuation Class with Account category reference,
    2.OMWM: Active Valuation Grouping Code,
    3.OMWN: Active Movement type with G/L account,
    4.OMWD: Active Valuation Area,
    5.OMWB: Active Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
    In OMWB or OBYC
    Click TE key and enter Chart of account and then save the Roles 1st for
    1.Debit/Credit
    2.General modification
    3.Valuation Modif
    4.Vakuation class
    And then enter respective critetia for that TE key and save.
    If assignment(Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts are correct and u would not face any problems in G/GI/IV.
    For more check the links:
    http://www.sap-img.com/materials/general-test-of-sap-mm-knowledge.htm
    http://www.saptechies.com/category/financial-accounting/page/0
    http://e-mory.blogspot.com/2007/06/sap-mm-and-fi-doc-number-verification.html
    http://www.sap-img.com/materials/sap-mm-configuration-tips.htm
    http://moryhanry.com/sapmmfidocverify.html
    http://www.sapcustomization.com/document/fi_mm_integration.pdf
    Regards,
    Biju K

  • Revenue Account Determination in MM

    Hi all,
    Can i know the path for configuring Revenue Account determination in MM.
    Regards,
    Ramaswamy.

    Dear,
    This is how Account determination done in MM,
    Movement types have key role as central account determination in MM side.
    This account determination is for MM settings u2013 group RMK.
    Account determination is based for combination of valuation grouping code, general modifier/account modifier, valuation class in SAP MM.
    This will be defined for particular transaction event key. Transaction event key will inturn be defined for each movement type of SAP MM.
    Basically GL account are assigned for certain combination of above. To put down in flowchart format-
    SAP RMK group (MM)
    Movement type-
    Transaction event key-
    GL account determination (one debit and one credit)- based on below combination
      Valuation Grouping code/ Valuation Modification -- Tcode: OMWD
      Account modifier -- Tcode: OMSK
      Valuation class -- Tcode: OMWN
    SAP will see transaction is made in MM, it searches the transaction event key from movement types. Based on valuation grouping code, account modifier and valuation class, determination will be done for GL account for debit and credit.
    and concern G/L Account assigned in TCODE- OBYC
    Need further clarification revert back.
    Dear atleast putup a thanks in responce to  people efforts before closing the issue
    Regards
    AJIT K SINGH
    HAPPY TO HELP U
    Edited by: AJIT K SINGH on Jan 6, 2010 5:22 PM

  • Account Determination and Movement type

    Hello Experts,
    From SD course, we know that account determination is Account Key + Account assignment groups for customer and material respectively + Sorg + COA.
    So, what does it mean by this definition of Movement type:
    "The movement type is a three-digit key used to differentiate between goods movements in the R/3 System. Examples of these goods movements are goods receipts, goods issues or transfer postings It plays a central role in Automatic Account determination"
    regards
    Pascal

    From SD course, we know that account determination is Account Key + Account assignment groups for customer and material respectively + Sorg + COA.
    This is related to revenue account determination. Normally carried out by SD personal using t.code VKOA.
    The movement type is a three-digit key used to differentiate between goods movements in the R/3 System. Examples of these goods movements are goods receipts, goods issues or transfer postings It plays a central role in Automatic Account determination
    This is related to inventory account update (quantity/value]. For example, when a goods issue is made, the value and quantity in the stock account needs to be reduced. The G/L account assignment is configured by MM personnel using t.code OBYC.
    Regards,

  • MM subcontracting Account determination

    Hi All,
    Any one knows MM subcontracting Account determination in OBYC?
    any help is appreciated..
    Thanks,
    Rau

    Hi,
    Hi,
    For Account Determination 5 major characteru2019s are as follow:
    1.Chart of Account,
    2.Valuation Class,
    3.Transaction Event Key,
    4.Valuation Grouping Code,
    5.Account Grouping Code/Account Modifier.
    Configuration of Automatic Account Determination with T.Code are as follow:
    1.OMSK: valuation Class with Account category reference,
    2.OMWM: Active Valuation Grouping Code,
    3.OMWN: Active Movement type with G/L account,
    4.OMWD: Active Valuation Area,
    5.OMWB: Active Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
    In OMWB or OBYC
    Click TE key and enter Chart of account and then save the Roles 1st for
    1.Debit/Credit
    2.General modification
    3.Valuation Modif
    4.Vakuation class
    And then enter respective critetia for that TE key and save.
    If assignment(Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
    are correct and u would not face any problems in G/GI/IV.
    The TE keys are:
    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.
    u2022 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.
    u2022 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.
    u2022 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.
    u2022 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.
    u2022 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.
    Caution :
    Take care to ensure that:
    A stock account is not used for any transaction other than BSX
    Postings are not made to the account manually
    The account is not changed in the productive system before all
    stock has been booked out of it
    Otherwise differences would arise between the total stock value of
    the material master records and the balance on the stock account.
    Revaluation of "other" consumptions (COC)
    This transaction/event key is only relevant to Brazil. It is used if
    a revaluation report is used for company codes in Brazil.
    The revaluation report uses the actual prices determined by the
    material ledger/actual costing to:
    Revaluate costs on the basis of actual prices
    Post the price differences arising from "other" consumptions
    (e.g. consumption to cost center) to a collective account
    This transaction/event key is needed to post the price differences.
    The account specified here is posted with the price differences for
    "other" consumptions.
    o documentation currently available.
    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.
    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
    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:
    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)
    You can also define your own account groupings. If you intend to
    post goods issues for cost centers (mvt type 201) and goods issues
    for orders (mvt type 261) to separate consumption accounts, you can
    assign the account grouping ZZZ to movement type 201 and account
    grouping YYY to movement type 261.
    Caution
    If you use goods receipts without a purchase order in your system
    (movement type 501), you have to check to which accounts the account
    groupings are assigned ZOB
    If you expect invoices for the goods receipts, and these invoices
    can only be posted in Accounting, you can enter a clearing account
    (similar to a GR/IR clearing account though without open item
    management), which is cleared in Accounting when you post the vendor
    invoice.
    Note that the goods movement is valuated with the valuation price of
    the material if no external amount has been entered.
    As no account assignment has been entered in the standard system,
    the assigned account is not defined as a cost element. If you assign
    a cost element, you have to enter an account assignment via the
    field selection or maintain an automatic account assignment for the
    cost element.
    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 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.
    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.
    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)
    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).
    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.
    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.
    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.
    Thanks,
    Raja

  • MM Account Determination

    Hi,
               Can anybody explain total how many G/l Accounts, we will generally assign and please give the list including TE Key.. The reply will be highly appreciated...

    Hi,
    For Account Determination 5 major characteru2019s are as follow:
    1.Chart of Account,
    2.Valuation Class,
    3.Transaction Event Key,
    4.Valuation Grouping Code,
    5.Account Grouping Code/Account Modifier.
    Configuration of  Automatic Account Determination with T.Code are as follow:
    1.OMSK: valuation Class with Account category reference,
    2.OMWM: Active Valuation Grouping Code,
    3.OMWN: Active Movement type with G/L account,
    4.OMWD: Active Valuation Area,
    5.OMWB: Active Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
    In OMWB or OBYC
    Click TE key and enter Chart of account and then save the Roles 1st for
    1.Debit/Credit
    2.General modification
    3.Valuation Modif
    4.Vakuation class
    And then enter respective critetia for that TE key and save.
    If assignment(Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
    are correct and u would not face any problems in G/GI/IV.
    The TE keys are:
    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.
    u2022 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.
    u2022 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.
    u2022 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.
    u2022 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.
    u2022 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.
    Caution :
    Take care to ensure that:
    - A stock account is not used for any transaction other than BSX
    - Postings are not made to the account manually
    - The account is not changed in the productive system before all
    stock has been booked out of it
    Otherwise differences would arise between the total stock value of
    the material master records and the balance on the stock account.
    Revaluation of "other" consumptions (COC)
    This transaction/event key is only relevant to Brazil. It is used if
    a revaluation report is used for company codes in Brazil.
    The revaluation report uses the actual prices determined by the
    material ledger/actual costing to:
    - Revaluate costs on the basis of actual prices
    - Post the price differences arising from "other" consumptions
    (e.g. consumption to cost center) to a collective account
    This transaction/event key is needed to post the price differences.
    The account specified here is posted with the price differences for
    "other" consumptions.
    o documentation currently available.
    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.
    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
    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:
    - 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)
    You can also define your own account groupings. If you intend to
    post goods issues for cost centers (mvt type 201) and goods issues
    for orders (mvt type 261) to separate consumption accounts, you can
    assign the account grouping ZZZ to movement type 201 and account
    grouping YYY to movement type 261.
    Caution
    If you use goods receipts without a purchase order in your system
    (movement type 501), you have to check to which accounts the account
    groupings are assigned ZOB
    If you expect invoices for the goods receipts, and these invoices
    can only be posted in Accounting, you can enter a clearing account
    (similar to a GR/IR clearing account though without open item
    management), which is cleared in Accounting when you post the vendor
    invoice.
    Note that the goods movement is valuated with the valuation price of
    the material if no external amount has been entered.
    As no account assignment has been entered in the standard system,
    the assigned account is not defined as a cost element. If you assign
    a cost element, you have to enter an account assignment via the
    field selection or maintain an automatic account assignment for the
    cost element.
    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 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.
    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.
    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)
    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).
    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.
    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.
    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.
    Regards,
    Biju K

  • Asking account determination while posting to MB1A

    hi friends,
    while posting goods issue to cost center(MB1A). i am getting the following error
    ACCOUNT DETERMINATION FOR ENTRY (CHART OF ACCOUNTS) GBB _________VBR 3000 NOT POSSIBLE, and
    ACCOUNT DETERMINATION FOR ENTRY (CHART OF ACCOUNTS) BSX _________VBR 3000 NOT POSSIBLE
    actually i assigned all the required GL acounts in obyc( i assigned GL accounts for BSX and GBB too). i dont know what to do.can anybody please help me out from this problem

    OMWB is the right tool to detect the error. Go to this transaction code and enter the plant and material number. Select the movement type (201?). Double click on the GI to cost center. Then click on Account Assignment icon. The resultant output will show what is missing.
    Valuation grouping code (Valuation modifier) also plays a majore role, as it groups plant together, to be used in maintaining account determination. of GBB for ZOB

  • Account determination error - in creation of invoice

    Hello experts,
    i have an error in creation of invoice, after( pgi post goods issue)
    will you please help me out to solve this error.
    thanks & Regards,
    yogesh raina

    hello sir,
    After going throuth this path it shows no gl account in account determination chart
    as below
    Condition type     Message     Description
      ZPR0                                  123     Access KOFI not carried out (initialized field)
    Access     Message     Description
    10     123     Access KOFI not carried out (initialized field)
    20     121     No G/L account found in Account determination type KOFI
    30     123     Access KOFI not carried out (initialized field)
    40     121     No G/L account found in Account determination type KOFI
    50     121     No G/L account found in Account determination type KOFI
    60     123     Access KOFI not carried out (initialized field)

  • Account determination error in VF02

    Hai Guru,s
    In VF02 when i am going ton release the flag to accounting i am getting following error  "Posting keys for accounting determination for transaction EXD does not exist"
    I checked VKOA EXD a/c key availabele .This is Exise duty account key.....In pricing procedure also EXD assigned to respectine condition type.............
    where i did wrong.........which setting i missed........
    Thank u in advance
    Regards
    Anjan

    Dear Anjan,
    For Tax Conditions you have to maintain Account Determination in OB40
    Go to T-Code OB40
    Select the Transaction - EXD - & Double click on it...
    Mention required GL Account here...
    Your problem would definitely get solved.
    Hope this helps...
    Give Points if useful...
    Thanks,
    Jignesh Mehta
    Edited by: Jignesh Mehta on Sep 26, 2008 10:42 AM

  • Account determination error in Subcontract PO-MIGO.?

    Hi all
    While doing GR, i mgetting error i "Account determination for entry LDCA BSV 0001 ___ 5010 not possible".
    The above PO is subcontract PO .
    Thanks
    sap-m

    Hi,
    For subcontracting..maintain these keys..so that you will not get any problem..
    BSX, BSV, WRX, PRD, FRL
    Regards,
    Prasath

  • Account determination error in FI-MM

    Hi Gurus
    I trying to raise PO requisition in ME21N. Here I am facing couple of issues
    1) If I select the K in account assignment category I can't assign the raw material GL account in account assignment tab  as it falls under balance sheet item.
    2) I have saved the PO with out K in the account assignment category and proceeded to MIGO when the saving the document in MIGO the system showing the rejection as "account determination is missing for Valuation class and for COCD"
    and postings are not reflected.
    I want make sure that all the settings related to account determination are good in OBYC.
    Please advise here
    Kishore

    Hi,
    As you mentioned the below is the error message.
    "account determination is missing for Valuation class and for COCD"
    What is COCD ???
    Is it Chart of Account or else????
    Ravi Polampalli

  • Account determination error in FI doc during SD billing doc posting.

    hi,
    when I create one billing doc ref to s/o,
    I check account determination in condition type:
    G/L account no.: 110000
    Provision acc.   : 120000
    in FI doc,
    should debit 110000 and credit 120000
    but current status is credit 110000 and debit 120000
    Please help.
    Thanks.

    Hi,
    One of the following could be the reasons for the Account determination error.
    Please check.
    1.Incorrect account assignment group entered in the customer and material master
    Resolution:Maintain correct account assignment group in customer and material master,Eg.External Domestic,Z1 - External Foreign,Internal Foreign,etc,.
    2.GL account not extended to the respective company code.
    Resolution:Extend the required GL account to the company code.
    Regards,
    Sophia Xavier

  • Account Determination error in MIGO

    Hi Folks,
    I am getting the following Error while doing MIGO
    "Account determination for entry ABCD ___ 0001 ___ 3000 not possible"
    I have checked in OMWD and OBYC and all the setting looks ok .
    Kindly suggest..
    Thanks
    Sumit

    Check valuation class for material you are using.

  • Account determination error in sales order

    Dear all,
    Please help. Trying to release a billing document to accounting. Getting the error:
    Document 90000004 saved (error in account determination)
    Message no. VF051
    While analysing: going to Environment - Accnt determination analysis - Revenue accounts :- no condition types are coming under the procedure KOFI000. Checked settings in vkoa. All G/L accounts are mapped. There are invoices of the same document type, with the same condition types in production with correct account determination.
    On further analysis, found that  no condition types are coming  not determined in the sales orders. Yet there is no incompletion log. Quite baffled. The users are punching in cut over sales orders into production. Please help me rectify the situation.
    Thanks,
    Kasturi

    I hope you have incompletion log (OVA2) maintain for WBS element in your sales order.
    Like
    Table
    Fld Name
    Desc
    Screen
    Status
    VBAK
    PS_PSP_PNR
    WBS Element
    KKNT
    Based your requirement , say, 01
    VBAP
    PS_PSP_PNR
    WBS Element
    PKNT
    Based your requirement , say, 06
    Regards
    JP

Maybe you are looking for