Transaction Key Maintenance in BW logistics

Hello,
I am using the  DataSource  2LIS_13_VDITM for extracting invoice items from the R/3. There is a field name BWVORG that brings the processing key (Transaction Key maintenance). I tried to find out what kind of field it was, but I don't understand from where this field comes.
In SBIW, there is table with these codes, but i can't see the relation between theses codes and the type of movements in logistics.
Anyone could give me help about that?
Best regards
Sérgio Pinto

Hello,
Goto Transaction MCB0 in the Source System (R/3 or ECC). Here you can display the characteristics of the process key BWVORG.
R/3 field BWVORG
BW field 0PROCESSKEY
Also see,
SAP Note 353042 Howto: Activate transaction key (PROCESSKEY)
SAP Note 684465 BWVORG for purchasing data sources
Thanks
Chandran

Similar Messages

  • SAP BW Transaction Key

    Hi,
    There is a field called BWVORG (SAP-BW Transaction Key) in the data sources for Inventory namely 2LIS_03_BF and 2LIS_03_UM which gets mapped to 0PROCESSKEY in BW. I want to know in which transaction of R/3 I will be able to see all those available transaction keys and similarly with the keys available in BW.
    Thanks a lot in advance.

    HI Bobs,
    The tcode for the same is SBIW
    Navigation is as below
    SBIW --> Settings for Application-Specific DataSources (PI) --> Logistics -->Settings: Purchasing -->
    Transaction Key Maintenance for SAP BW
    Program name is SAPLMCRR
    Thanks and Regards
    PV

  • BW: Transaction Key  in 2LIS_02_ITM

    Hi ,
    In the datasource for Purchasing 2LIS_02_ITM and it is also there in the Schedule line item 2LIS_02_SCL, there is a field called BW: Transaction Key mapped to BWVORG in R/3. It looks to me, that it provides information about, whether it is a invoice, GR, and so on. Does anyone know, what are the different values and what do they mean. Thanks a bunch for helping me.

    Hi Sonali,
    Check oss 684465
    In the BW customizing is possible to maintain the description of the
    transaction key for transferring Logistics movement data to BW system,
    field BWVORG in purchasing data sources, but this will not change
    the BWVORG determination process.
    Customizing (transaction MCB0):
    Settings for application specific -> Logistics ->Purchasing settings ->
    Maintain Transaction Key for SAP BW.
    Here is a list of the values that BWVORG can assume, according with
    the purchasing item type, processed document and purchasing order type:
    1 - For non return items:
        a) Document type: Purchasing order
            - Normal purchasing order - BWVORG = 001
            - Stock transport order   - BWVORG = 011
            - Cross company order     - BWVORG = 021
        b) Document type: Goods receipt
            - Normal purchasing order - BWVORG = 002
            - Stock transport order   - BWVORG = 012
            - Cross company order     - BWVORG = 022
        c) Document type: Invoice receipt
            - Normal purchasing order - BWVORG = 003
    - Stock transport order - BWVORG = 013
            - Cross company order     - BWVORG = 023
        d) Document type: Scheduling agreement
            - Normal scheduling agreement - BWVORG = 004
            - Stock transport agreement   - BWVORG = 014
            - Cross company agreement     - BWVORG = 024
        e) Document type: Contract
            - Normal contract             - BWVORG = 008
            - Cross company contract      - BWVORG = 028
        f) Document type: Request of quotation
            - Request of quotation        - BWVORG = 009
            - Quotation                  - BWVORG = 040
    2 - For return items:
        a) Document type: Purchasing order
            - Normal purchasing order - BWVORG = 005
            - Stock transport order   - BWVORG = 015
            - Cross company order     - BWVORG = 025
        b) Document type: Goods receipt
            - Normal purchasing order - BWVORG = 006
            - Stock transport order   - BWVORG = 016
            - Cross company order     - BWVORG = 026
        c) Document type: Invoice receipt
            - Normal purchasing order - BWVORG = 007
            - Stock transport order   - BWVORG = 017
            - Cross company order     - BWVORG = 027
        d) Document type: Scheduling agreement
            - Normal scheduling agreement - BWVORG = 041
            - Stock transport agreement   - BWVORG = 051
            - Cross company agreement     - BWVORG = 061
    Jaya

  • OBYC- GBB- Transaction keys

    hi
    Can any one tell me what are these keys meant for
    In GBB: AUA,AUF,BSA,INV,VBR,VAX,VAY,ZOF,ZOP are some of the keys I have mentioned.
    I want to know to which key I have assign the inventory,scrap,consumption G/L codes ,etc for process industry in repetitive and discrete manufacturing scenario.

    Hi,
    Check this..
         Transactions     
         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.     
         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.     
         Account determination of valuated sales order stock and project stock     
         Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX andGBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.     
         During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.     
         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:
         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.
         Account determination of valuated sales order stock and project stock
         Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX andGBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.
         During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.
         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.
         Customers who used the transaction WRY prior to Release 4.0 must make a transfer posting from the WRY account to the WRX account in order to ensure that the final balance on the WRY account is zero.
    Thanks,
    Rau

  • Transaction Key values for MM

    Hi All,
    What entery's to be maintained in Transaction key (SBIW (Settings for application specific data source< Logistics< Transaction key maintenace for SAP BW) , will it contain all movement types defined in R/3 system for MM.
    For e.g.
    In SBIW -> Transaction key  641(Stock transfer) is not maintained where as its been defined and used in the R/3 system. So does this entry is mandatory to be maintained in SBIW before we extract MM data (Inventory).
    Thanks

    Hi Dipika,
    you could check the forum entry: Business Intelligence Old Forum (Read Only Archive)
    You could also check SAP notes 352344 and 492828.
    regards,
    Raymond Baggen

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

  • How to create Transaction keys.

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

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

  • Creation of new transaction keys

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

    HI,
    You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction.
    If you create it you have to make changes in Movement type level as well in following path which is not suggestible
    SPRO -> MM -> Valuation and Acct Assignment -> Acct Dtermination -> Define accoutn grouping for movement types.
    for more info check following link
    [http://help.sap.com/saphelp_46c/helpdata/en/12/1a39516e36d1118b3f0060b03ca329/content.htm]
    Regards
    Kailas Ugale

  • Transaction code for creation of  transaction keys in obyc

    Dear Experts,
    Can u tell me what is the transaction code for creation of transaction keys in obyc asap.
    Thanks & Regards,
    Radhika.

    Hi
    There is no TCode and the path is
    SPRO-Material Management-Purchasing-Conditions-Price Determination....
    Cheers
    Srinivas

  • Transaction Key for Movement Type 561

    Hello,
    For movement type 561, I know one of the Transaction Key is BSX.  I would like to ask what is the other Transaction Key as I would like to set the GL Account Determination.  Thanks.
    Thanks.

    Hi
    Transaction keys required for 561 movemnt type are
    BSX - For the inventory posting
    GBB - BSA - For initial entry of stock balances
    For performing the 561 movment G/L account needs to be assigned to both these transaction keys.
    Thanks & Regards
    Kishore

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

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

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

  • OMWB transaction key Issue

    Dear All,
    As per our customer's requirements we have created a new transaction/event key & assigned the same in existing Cal.Schema. The G/L A/C for the new trans key is also defined in OBYC.
    After all the these when we Checked in OMWB transaction - G/L accounts tab then both transaction key as well as the G/L which  we assigned to the new  transaction is not displayed..
    So can anyone provide some inputs on why the system is not displaying the newly created G/L & transaction key in OMWB - G/L Accounts tab ?
    Thanks in advance &  Have a Nice Day!
    Regards,

    Hi Kishore,
    Thanks a lot for the reply.
    As you suggested I have checked in T030 table & I can find a entry there with values for Chart of A/Cs, Trans Key & G/L A/C. (Since in OBYC I have specified my G/L A/C for trans key with ref to Posting key only)
    So the fields - Val grouping code, valuation class & Acct modifier are blank for the above entry.
    Now even if there is an entry in the above table the transaction key & G/L A/C is not displayed in OMWB - G/L A/C tab.
    Hope its clear.
    Awaiting your reply..
    Regards,

  • Change string value by adding a transaction key in T156

    Hello expert,
    My client want to add the transaction key BSX in the string value used for the code movement 261 k (good issue
    of supplier consignment stock).
    SAP Active Global Support respond that changes of value string for standard movement types are not supported.
    However we want if possible to change that : is there a way to do that?
    Thanks for your response.
    Céline Ouali

    Hi,
    If you just want to use new transaction or account modifier without changing value/quantity string, you can do that in T156X.
    Otherwise, i.e. to update value/quantity string -
    Create a custom value string with reference to SAP standard WA03. Update the Value/Quantity string for movement type 261 K in table T156S. Goto SE11 - Display Contents - Create/Maintain Entries.
    You need to add custom transaction keys/account modifiers for value strings in table T156W.
    Thanks
    Venkata Ganesh Perumalla

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

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

Maybe you are looking for

  • Displaying images at a fraction of the size

    This may not be a coldfusion question but I'm going to ask it here anyway because cfml developers are the smartest. :) I have a table that stores images paths and in my cfm file I pull the path and display the image. What I want to do is take that im

  • Phone Contact

    May I know how to set my default phone book as my SIM contact; May I know how can I backup my Contact to SIM; May I know how can transfer my contact from phone to SIM Please get back to me asap

  • Basic configuration of IDS

    i am having IDSM-2.can anyone give me the basic configuration setting of switch as well as IDSM-2.I donot know what to configure on IDSM-2. regadrs shivlu

  • Incompatibility of CC 2014 with CC

    Is there a way to downgrade? I have CC in my office, and my school offered me an opportunity to buy CC for my home computer, but it turned out to be CC-2014. Normally, I'd be happy to have the newer version, but I'm using InDesign, and the files I op

  • You have no Oracle clients installed: Windows XP client to Oracle Linux ser

    Hallo! I have Oracle 10g Db running on Redhat Enterprise Linux server.Moreover, I have a windows XP client having Toad 9.06 in the XP client. The client does not have any Oracle Db or Apps installed. I would like to connect to the Oracle Db sever via