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,

Similar Messages

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

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 Keys in Materials Management

Also known as u2018process keys,u2019 the u2018Transaction Keysu2019 are pre-defined in the system to enable transaction postings in Inventory Management and Accounting (Invoice Verification). For each of the movement types in MM, there is a value string that stores these possible transactions.
The pre-defined transaction keys are:
BSX (used in Inventory Postings)
WRX (used in GR/IR Clearing Postings)
PRD (used to post Cost/Price differences)
UMB (used to post Revenue/Expenses from revaluation)
GBB (used in offsetting entries in Stock postings)
BSX, WRX, and PRD are examples of transaction keys that are relevant for a GR with reference to a purchase order for a material with standard price control.
The transaction key UMB is used when the standard price has changed and the movement is posted to a previous period.
Likewise,GBB is used to identify the GL account to post to as the offsetting entry to the stock account (when not referencing a purchase order) such as miscellaneous goods receipts, goods issues for sales orders with no account assignment, and scrapping

Also known as u2018process keys,u2019 the u2018Transaction Keysu2019 are pre-defined in the system to enable transaction postings in Inventory Management and Accounting (Invoice Verification). For each of the movement types in MM, there is a value string that stores these possible transactions.
The pre-defined transaction keys are:
BSX (used in Inventory Postings)
WRX (used in GR/IR Clearing Postings)
PRD (used to post Cost/Price differences)
UMB (used to post Revenue/Expenses from revaluation)
GBB (used in offsetting entries in Stock postings)
BSX, WRX, and PRD are examples of transaction keys that are relevant for a GR with reference to a purchase order for a material with standard price control.
The transaction key UMB is used when the standard price has changed and the movement is posted to a previous period.
Likewise,GBB is used to identify the GL account to post to as the offsetting entry to the stock account (when not referencing a purchase order) such as miscellaneous goods receipts, goods issues for sales orders with no account assignment, and scrapping

Movement Types & Transaction Key/Posting Keys

Hi Friends,
Can any one explain How the Movement Types & Transaction Key are related/
where can we see the Movement types? I think we can see Transaction keys in OBYC but Movement types?
and is there any relation b/w condition types and Movement types?
Thank you ,
Paaarthu

Hi
In material master accounting view we will define Valuation class & in OBYC we will assing GL accounts for valuation class, under transaction key BSX (Inventory posting).
Go to T.code:OMWB here you can simulate the accounts.
I think this transaction gives a very clear picture on MM-FI integration.
It even specifies if there are any missing GL accounts.
Have a look at OMWB and let me know if you have any further questions.
Thanks
Kalyan

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>

PRD - PRA transaction Key

Dear All,
I hav one doubt regarding transaction key PRD - PRA.
When actually it hits . I think it is used while using goods issue and other movements.
But tell me the functionaly of it.
Also I found in OMJJ for movement type 201,221 posting like
PRD PRA and check box is unticked (a/c assignment)
Why is it so?
Pls clear my doubt.
Thanks in advance.
Regards,
Gitesh

Hi,
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 price),
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, then you can use this modification.
"PRA for goods issues and other movements "
thanks,
Prashant Rathore.

When use AG1,AG2,AG3 transaction key?

in the tcode:obyc configuration,when the transaction key of AG1,AG2,AG3,AKO,AUM will be used?
can you tell the business or the movetype?
Thank you in advance!

Hi Yulin
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.
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.
regards
Yogesh

Transaction Key PRD_PRA

HI All,
In which scenario OBYC Settings Transaction key PRD--PRA will be used. we did nt activated ML. Still the system is throwing a message at that time of cancellation of production order confirmation "Account determination for entry PRD_PRA valuation class XXXX not possible.
1.For PRD_PRA-- ML Need to activated or not??
2. how PRD-PRA is differ from the PRD
3. in which scenario PRD_PRA will be assigned with GL
Thanks

Hi
In PRD we assign accounts for price difference. It is independent of ML activation and has no relevance to ML.
PRD can be used with/without account modifier. If you use account modifier, you can assign separate account for price differences from purchase order or production order etc.
In particular PRD- PRA is for price difference in case of goods issue.
In your case, since you are cancelling Production confirmation, goods issue is happening for the finished good (presumed it is maintained with price control S and backflush is 'ON' for this)
This is the reason error is showing up.
In normal cases PRA will not picked because goods issue is generally done for raw materials which are maintained with price control V.
Generally PRA can be assigned with the same account as that for normal PPV (purchase price variance) account unless business specifically wants to assign something else.
Hope this helps
Regards
Abhinav

Transaction Key infoobject

Hi,
could any one tell me where i can find the Transaction Key infoobject "0PROCESSKEY" in 0ic_c03 cube?
i see the filed BWVORG in the 2lis_03_BX/BF/UM extraction structure, but i don't know where i can find corresponding infoobject in BW - in update rules or transfer rules?
please advice,
Ping

hi Ping,
you won't find 0PROCESSKEY in infocube 0ic_c03,
it has been translated to column, try to check the routine in update rules to infocube, you will find
code like attached, you can locate bvwvorg map to 0processkey in transfer rules, go to 'change transfer rules', tab 'tranfer rules', in right side 'assign infoobj-field', click 'position/other entry' button, choose field name and type bwvorg.
hope this helps.
IF ( COMM_STRUCTURE-PROCESSKEY = '100'   "Other Issues
   OR COMM_STRUCTURE-PROCESSKEY = '101'   "Returns / Vendor
   OR COMM_STRUCTURE-PROCESSKEY = '104'   "Material Transfer
   OR COMM_STRUCTURE-PROCESSKEY = '105'   "Stock Adjustment InvD -
   OR COMM_STRUCTURE-PROCESSKEY = '106'   "Stock Adjustment Other -
   OR COMM_STRUCTURE-PROCESSKEY = '110' ) "Issues from Stock Transfers
AND COMM_STRUCTURE-BWAPPLNM EQ 'MM'
Valuated Stock is considered
AND ( COMM_STRUCTURE-STOCKCAT IS INITIAL OR
        COMM_STRUCTURE-STOCKCAT = 'E' )
Only movements which are relevant for stock control
AND COMM_STRUCTURE-STOCKRELEV = '1'
AND COMM_STRUCTURE-CPQUABU <> 0.
result value of the routine
   RESULT = COMM_STRUCTURE-infoobjectname.
if the returncode is zero, the result will be updated
   RETURNCODE = 0.
ELSE.
if the returncode is not equal zero, the result will not be updated
   RETURNCODE = 4.
ENDIF.

Transaction Key AG1

Dear all,
I am configure intergation FI with MM.
I don't know how to accounting entries generated in transaction key AG1
Please tell me accounting entries of AG1
and give me examples
Thank in advance
Minhtb

Hi Yulin
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.
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.
regards
Yogesh

Transaction Key and Acct Modifier Key

In automatic account determination , whats is the difference between transaction key and account modifier key?
When we need to define account modifier key?
POINTS WILL BE REWARDED FOR ANSWERS.
Thanks in advance.

Hello Venugopal,
Transaction / Event Key
Key allowing the user to differentiate between the various transactions and events (such as physical inventory transactions and goods movements) that occur within the field of inventory management.
The transaction/event type controls the filing/storage of documents and the assignment of document numbers.
Account Modifier Key
Account grouping code is only used with offsetting entries (GBB), consignment liabilities (KON), and price differences (PRD).
Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
Hope this helps.
Regards
Arif Mansuri

Transaction key / event key in account determination??

hii
I want to know what is transaction key and event key in account determination??
Thanks

HI,
Transaction/event key (internal processing key) Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers. 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. Account grouping (only for offsetting entries, consignment liabilities, and price differences) Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code. An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting". Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts. If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key. Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities. Valuation class of material or (in case of split valuation) the valuation type The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials. You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class. If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
Regards
KK

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.

OMWB transaction key Issue

Similar Messages

Maybe you are looking for