[HELP] OBYC Transaction Key - DIF

Hello Gurus,
Is there anyway to set another transaction key for small differences?
I have a customer requirement to set another transaction key for small differences in invoice. And i don't know if it's possible to set a different transaction key than DIF.
If there is a way to do it, can anyone show me the way?
Regards,
Rafael

Hi Rafael,
The transaction DIF(Materials management small differences) is triggered in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
For this you should define the G/L accounts against the key in OBYC settings.
Let us know why you want diff transaction other then DIF.

Similar Messages

Query on OBYC Transaction key

Dear Experts ,
I have a few queries regarding automatic postings :
1.What process triggers the transaction key AUM ? what type of account should be assigned here ?
2.What process triggers the transaction key BSV? what type of account should be assigned here ? Hw different is it from GBB-VBO ?
3. What is the difference between DIF , PRD & UMB ?
4. Is GBB-VKA relevant for make to stock scenario ?
Regards
Anis

Hi
1) AUM is triggered if the material iin supplying planrt is maintained either in MAP or Standard price and material in recieving plant is in stamdard price and there should be a price difference.The differencial amount will be posted to the Expense/Income account through AUM
2)BSV will be triggered during subcontracting GR.it is the Transaction event key which defines the Change in stock account .This is maintained to accomodate the credit side entry for the output material during GR.Whereas GBB-VBO is for input material consumtion during subcontracting GR.It provides the Debit side entry for Input material consumption
3)DIF is triggered during IV if there is balance and you still want to post it
PRD is triggered if the material is maintained as Standard Price and the value is differenet from the PO value .
UMB is triggered if you want to revaluate the material th MR21
4) GBB-VKA is for make to order scenario where you make a PO directly with reference to sales order
Regards
Sandeep

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

Transaction Key DIF

Dear All,
In which scenario the DIF account gets hit in SAP.... please guide
cheers

Hello,
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
Tolerance key - BD for defining small diff. tolerance
Also you can Configure Vendor-Specific Tolerances.
Regards,
Shailesh

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

OMR6 tolerance key and OBYC transaction

Dear All,
May I know how to know tolerance key in OMR6 is linked to which OBYC transaction. Where I can see the mapping of tolerance key in OMR6 to OBYC transaction.
Need your advice.
Thanks

hi
there is no link between OBY6 , OMR6.
OMR6 - Tolorence limits maitained in Company code leval.
OBY6- we are assign only G\L accounts. ( G\l Account tolarences maintained in Separetly)
satish

OBYC Delivery Costs Transaction Key

Hi,
I want to change the GL accounts that are impacted when i post for delivery costs in a Purchase Order. Can someone let me know in OBYC what is the 'Transaction' where i can configure for the same.
Please Advise.
Thanks,
Safi

Hi,
Please check transaction key UPF for Unplanned delivery costs or FRE for Purchase freight.
Assign points, if useful

OBYC - VKA transaction key

Please anybody clarify my following doubt:
I see that for cost of goods sold entry, in OBYC, we can use transaction key: VAX
Then what is the purpose of VKA key ? Is it also relating to Cost of Goods Sold ?

HI
this is obyc for integration between fi and mm where transaction key vkoa using for sales revenue account only
BEST
NASERK
Edited by: naserk on Dec 7, 2011 7:36 AM
Edited by: naserk on Dec 7, 2011 7:37 AM

OBYC - New Transaction Key

Hello Masters,
I would like to know how is the process to create a new Transaction Key in OBYC to assing a new account for a new delivery cost in the Good Receipt.
Thanks in advance.

Hello,
You can create a new Transaction Key in SPRO->Materials Management->Purchasing->Conditions->Define Price Determination Process->Define Transaction/Event Keys. Then assign this in to the Pricing Procedure (SPRO->Materials Management->Purchasing->Conditions->Define Price Determination Process->Define Calculation Schema). Now you can configure Account Determination using OBYC for the Transaction Key created by you.
Thanks,
Venu

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.

Movement type and obyc transaction and general modification

Dear All,
I would like to seek advice.
How to know from movement type, I can know that it is using what transaction and what general modification in OBYC?
I a bit surprise to know from forum that some even can tell movement type 201 is GBB-VBR.
May I know any where in IMG or table that got such linkage?
thanks

Hi,
The Movement type assigned to Transactions with the General Modifiers will post to the assigned G/L Accounts.
I am posting some explanation of Account Modifiers, which is Posted by one of SDN members :
(I am using it as my reference too)
OBYC Settings for Account Modifier
In standard SAP, only three transaction keys are having Account modifiers. The transaction keys are GBB, PRD, KON.
This account modifeirs helps to post to different G/L accounts for the same transaction event keys.
Account modifiers for 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)
Account Modifiers for KON
None for consignment liabilities
PIP for pipeline liabilities
Account modifiers for PRD
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)
Hope this helps,
Best Regards
Amit Bakshi

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

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.

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

[HELP] OBYC Transaction Key - DIF

Similar Messages

Maybe you are looking for