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

Similar Messages

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

  • Transaction key for account determination

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

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

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

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

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

  • 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

  • Transaction key in Accounting document

    Dear gurus,
    I want to see the transaction/event keys (such as: BPX, GBB,...) for each relevant account in Accounting document but cannot.
    I remember that just to change layout of the document OR see the detail of the account in that document. But right now, I cannot see the transaction/events key there.
    Pls tell me how can I display it. Thanks

    Hello,
    Got o accounting document,  go to "S elect layout "option  , Besides Graphic.
    Click on that, You will get slect layout, Change lyaout....you should select "Change layout" 
    Change layout will open  One screen "dsipalyed coloumn" and "coloumn set"  In coloumn set you will find "transaction field select that .....
    you will get the accounting entries
    Mahesh Naik

  • 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

  • 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

  • To add new transaction key

    All SAP Gurus,
    We want  to add new transaction key in account determination (OBYC).
    How to add it?
    Regards,

    Hi Rajan,
    If you are talking about the transaction key at Materials Management postings (MM) group (RMK),
    it is merely not advisable to create a transaction key.
    You have General modification like BSA, INV etc for differentiating the postings.
    The transation key mentioned in the earlier mail is for below purpose:
    To enable the system to find the relevant account for provisions (
    accrued delivery costs or miscellaneous provisions, for example),
    must assign a transaction/event (internal processing) key to each
    condition type that is relevant to provisions in the step Define 
    Calculation Schema.                                              
    Cheers
    Arun.

  • 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

  • Different field groups in the different account groups

    Dear IT Experts,
    I´m working on restructuring authorization in roles concerning the IC and TP customers.
    The goal of this changes is be able to have different field groups in the different account groups (TP and IC), for give you some more detail a good example can be, the same AMS user should be able to change general data and sales views for TP customers  but for IC he should only be allowed to change the sales views, however when the changes are made in the roles they are being ignored because as far as I could check the system does not have as a rule that the field groups are or can be dependent from the account group...
    I can give you a clear example:
    Role A
    F_KNA1_AEN -> VGRUP = 10-16
    F_KNA1_GRP -> ACTVT = 01, 02, 03
    F_KNA1_GRP -> KTOKD = INTR
    Role B
    F_KNA1_AEN -> VGRUP = 16
    F_KNA1_GRP -> ACTVT = 01, 02, 03
    F_KNA1_GRP -> KTOKD = THIR
    Despite it looks fine, the system is not validating the account group with the correspondent field group in each role, so the field groups that the system use is unique, it means it the content of the object F_KNA1_AEN in total independently of used account group!
    So my question is, can we apply any other object that makes the field group being directly depending of the account group, as we can see for example activities for each account group having something similar for field group and account group?
    Can someone please explain me step-by-step how I can do this work even if by another method?
    I´m quite new on this issues and I really need your wisdom to find a solution for this.
    Many thanks
    Katjia

    Hi Manoj
    The debate is each inidividual business unit has defined different account groups for the same vendor in their respective systems.
    The question is : What is the best practice-- Should we keep Vendor account group as main table field and define Vendors with one unique account groups OR we maintain the account group in qualified table each pointing to different business unit.
    In my opinion this is going to be very complex solution. Ideally we need to define all the Harmonization rules before syndicating data to different target systems.
    Is this possibel that the same vendor record which is existing as vendor of different account groups in different systems have same set of attributes. If yes then enabling the remote key for Account group Lookup field is one option and defining a unique Account group 'AG" (which is mapped to say AG1 from remote system1, AG2 from remote system2 and so on..)..
    Managing this via Qualified table will be very complex and not advisabel. As Rajesh also mentioned Account Group in MDM should be considered as Global attribute and all such harmonization rules should be defined in your project. AG1=AG2=AG in above exmaple.
    Hope this clarifies.
    Thanks-Ravi

  • Define Account Grouping for Movement Types??

    hi
    In account determination the setting in transaction  OMWM - Define Account Grouping for Movement Types
    The above transaction needs any setting or its standard SAP settings??
    Can somebody explain me about this transaction in detail.
    Thanks

    OMWM is to decide account determination should happen via valuation grouping code or not. SAP standard is with valuation grouping code. I had never seen singe time anywhere it is deactivated.
    Account grouping for movemement you can see in OMJJ. (Inside movement type left side). It is also predefined by SAP. You see only account modifier and check acct. assignment is editable. Others cannot be edited.
    In case for same transaction if you want 2 different GL account needs to be triggered for same material in same plant, we copy a movemen type and create a new and assign a different account modifier.
    Then in OBYC against it we will maintain different GL account.
    Hope you are clear
    Regards
    Antony

  • OBYC - Transaction key FR1

    Dear All,
    I want to add general modified in rules of transaction key FR1? as per standard SAP, we have debit/credit, valuation modifier and valuation classes are there.
    is there any possibility to add, because as per our client i have to assign different Freight clearing accounts based on Geographical area. by using general modifier i want to assign different Freight clearing accounts.
    Can any one suggest me - how we can meet the requirement?
    thanks & regards,
    Ramesh B

    hi,
    i didn't find any option to add new rules for transaction keys.
    For example for transaction key "WRX" - accounts are determined based on : debit/credit, general modificaiton,valuation modifier,valuation class.
    For FR1 - we have only debit/credit, valuation modifier,valuation class. But here i want to add general modificaiton.
    is it possible. if yes, how can we add.
    I don't want to create any new transaction keys, because we are using only one MM pricing schema and one condition type.
    thanks & regards,
    Ramesh B

  • 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

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

Maybe you are looking for

  • Is there an easy way to reimport all songs in my itunes folder?

    This may sound like a weird question but here goes... When I bring up my iTunes I have 8731 files (mostly music) that come to about 41.33G's but when I right click on my iTunes Music folder and select properties there are 8809 files and a total of 48

  • Imac 27" 2012 Mountain Lion running very hot

    Please help. My 27" IMac running very hot, especially top left corner. Is there a fix. Tony R

  • Inconsistent display of events..

    So...this is a layout thing that is just driving me crazy.  I have just noticed that sometimes my events/calendars will over lap, which is they way I prefer iCal to work.  (The blocked off sections are the width of each day)  But other times, the eve

  • DDP 2.0 and DDP 2.1... what difference?

    I use DLT to create master. I usually use 2.0 but not understand why I need to use 2.0 instead of 2.1. Can you explain what difference? I wonder if I can use DVD-R with ddp as master. Is that good idea instead of using DLT due to high costly on DLT?

  • Intervals, synchronize the data between two oracle tables located in diffe

    Hi Experts, Is there any way I can, at set intervals, synchronize the data between two oracle tables located in different servers? What is the software, if there is any? If there are steps I can follow, so much the better. Thanks!