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

Similar Messages

Restricting Transaction Keys while calling SAP Movement Types via MIGO

Hi Experts
I have a requirement which is stated below:
When ever I will call movement type 561 via MIGO, system will check if PRD transaction key is going to be hit & throw an error.How to achieve this.Plz advice.
Regards
Soumick

Hi Soumick Basak
Can you clarify us?
In sap standart , price difference is occured when you post a movement with differences in a standart price controled material master. If there is not a configuration in OBYC (automatic account assignment) , sap gives an error message which consists of like a PRD account not determinated for Valuation class XXXX ...
What you want to control ?
Regards.
M.Ozgur Unal

I am getting error messages when keying entries into SAP in transaction cod

I am getting error messages when keying entries into SAP in transaction code F-02. It will tell me that an asset doesn't exist in the company code I am posting to when the asset does exist. For example in the parked document 101079622 it tells me that asset WV0707711 doesnt' exist in CoCode . But what is keyed in the document is WV07077 1 1.
And when i look in Transaction AS03 for this asset number it does indeed exist in Co Code. Also if you take these assets out and park it and then go into Transaction FBV2 and add the asset back into the document it will add it and then post to it. This happens often and is very time consuming. I need to know how to fix this without all this additional effort

Hi,
it is urgent can any one help on this.
Thanks,
Sridhar Reddy.G

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

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

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

Transaction key FRL and FRN

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

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

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 - ZDI, what is it?

Dear SAP-team and specialists,
I was trying to look for information about ZDI - transaction key or BSEG-KTOSL.
...What is ZDI? Where can we get info about ZDI?
Thanks... my search is failed)
Best regards.
Eugene.

Hi,
Transaction Key is one of the processing keys for automatic posting which links two GL accounts or links tax codes
with the gl account to be posted. You see a list of these keys in OBCN where it is created. You can also create
a transaction key of your own. These keys are also called accounting keys to capture the amounts calculated through the pricing procedure or tax calculation procedure to post in the respective GL accounts. The accounts are assigned normally through OB40.
Regards,
Sadashivan

Transaction Key - bseg (KTOSL)

hi all,
can any one provide documetation on transaction key..
thanks
raj

Hi,
I think my reply meets some portion of your question:
T030 - for MM - the transaction key
T030A - transaction codes and transaction keys interlinked
T030B - transaction keys linked with posting keys.
There are many more tables involved. I think transaction keys are nerve system for all transactions in SAP.
I think SAP has hardcoded these transaction keys in all the programs.
You can check many more tables by using KTOSL data element where used list.
Hope this helps.
Rgds,
Sreeni

Posting transaction key PRD

Good morning,
I should do a little analysis about our G/L accounts definition for transaction key PRD. What I would like to understand is how SAP configures the automatic posting procedure or, in a better way, how SAP determines which transaction keys must be used in a particular situation.
I think that these tables should be involved in the procedure:
T156SC
T156SY
T156X
T156W
Does someone have more information?
Thank you in advance.
Francesco Alborghetti

Dear Francesco,
Go to T.code - OBYC.
Select the posting key - PRD.
Give the concern chart of Account and go inside.
You will see Valuation modification and Valuation class assigned to GL accounts.
If you want to include the movement types into this, you need the Account modifier. If so, click rules,
select the check box of Account modifier also and save the screen first.
Then go into the trasnaction, where you will find the Account modifier will also be included. You can select the correct account modifier which is in turn assigned with the movement type.
Hope this helps.
Reward points if satisfied.
Thanks.
Augustine Ponraj.

Transaction Keys Description in MM(BSX, GBB etc)

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

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

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

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.

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

SAP BW Transaction Key

Similar Messages

Maybe you are looking for