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

Similar Messages

Why do we need account key in SD revenue account determination?

Hi,
Why do we need account keys in SD pricing procedure and revenue account determination? If we dont use account keys wht will be the problem in priding procedure and revenue account determination?

hello, friend.
account keys allow you more flexibility in assigning revenues, costs and other financial data to different GL accounts.
let us take, for example, surcharges and discounts. surcharges are extras charged to the customer for maybe freight, penalties and other services. discounts could be header or item related, and can take many forms (volume discounts, customer discounts, customer group discounts, etc.).
in SAP standard, condition types in pricing procedures that are surcharges (i.e. freight) are assigned to account key ERF. discounts are assigned ERS. when you do account determination, it can look like this:
condition type KF00 (freight), account key ERF, post to GL account 600010.
condition type K007 (discount), account key ERS, post to GL account 700010.
however, your company might want the different surcharges to be posted to different GL accounts. let us say your company wants you to define additional freight surcharges KF01 and KF02. the company also wants you to post these to separate GL accounts. so now, you define additional account keys ZF1 and ZF2. you then assign these to the condition types in the pricing procedure, and then do account determination as follow:
condition type KF01, account key ZF1, post to GL account 600020.
condition type KF02, account key ZF2, post to GL account 600030.
these are just some impact of account keys.
hope this helped you.
regards.

Assignment of key for tax clearing account to tax clearing account

Hello,
I need a tax clearing account for gross display of down payments. In order to do so, I set a key for tax clearing account in OBL3 t-code but, afterwards, I am unable to link that key to the account that I need. Where can I assign the key to the clearing account?
Thanks,

HI,
Go to spro-> MM -> purchasng ->condition->define price determination process->define transaction and Event key
Reward if helpful,
Regards,
Chetan.

FAGLF101-Account determination for transaction V02 is missing for account

Morning
When I run the "faglf101" transaction, i get this error :
"Account determination for transaction V02 is missing for account 0000401142
Y1 PCG
Message no. FR005 "
I have tried to customize the adjustments accounts and postings keys in the IMG
"Financial accounting > Accounts Receivable and payable >
Business Transactions > Closing >Regrouping > Define adjustments
accounts for changes reconciliation accounts"., but i don't see the part "Regrouping" in the IMG.
I have tried to use the OBBW transaction, but his transaction code "A00-Transfer postings: changed recon. acct" don't correspond to mine (V02);
We are in ECC6.
Can somebody explain to me how can i correct this error please?
Best regards

This is meant for account determination for Receivables/payables sorting. Check your configuration in SPRO->General Ledger Accounting (New)->Periodic Processing->Reclassify->Transfer and Sort Receivables and Payables->Define Adjustment Accounts for Receivables/Payables by Maturity

Revenue Account Determination in MM

Hi all,
Can i know the path for configuring Revenue Account determination in MM.
Regards,
Ramaswamy.

Dear,
This is how Account determination done in MM,
Movement types have key role as central account determination in MM side.
This account determination is for MM settings u2013 group RMK.
Account determination is based for combination of valuation grouping code, general modifier/account modifier, valuation class in SAP MM.
This will be defined for particular transaction event key. Transaction event key will inturn be defined for each movement type of SAP MM.
Basically GL account are assigned for certain combination of above. To put down in flowchart format-
SAP RMK group (MM)
Movement type-
Transaction event key-
GL account determination (one debit and one credit)- based on below combination
Valuation Grouping code/ Valuation Modification -- Tcode: OMWD
Account modifier -- Tcode: OMSK
Valuation class -- Tcode: OMWN
SAP will see transaction is made in MM, it searches the transaction event key from movement types. Based on valuation grouping code, account modifier and valuation class, determination will be done for GL account for debit and credit.
and concern G/L Account assigned in TCODE- OBYC
Need further clarification revert back.
Dear atleast putup a thanks in responce to people efforts before closing the issue
Regards
AJIT K SINGH
HAPPY TO HELP U
Edited by: AJIT K SINGH on Jan 6, 2010 5:22 PM

Valuation string in account determination

Hi ,
Please explain me automatic account determination considering the Valuation strings,
Please explain me how the different factors( like valuation class, material type etc) comes in sequence in automatic account determination.
Regards, Deepika
Edited by: Deepika Pradhan on Dec 27, 2007 8:52 PM

Hello
All the Goods Receipt, Goods Issue movements and Invoice Postings are the events relevant to Accounting. These transactions or events effects the accounting and there is a need to post the value to certain GL Account.
Account Determination is a process to automatically identify the GL Account and post it when a relevant Transaction or events takes place.
The following is level for valuation and account determination in MM
Chart of accounts
Company code
Valuation area
Plant
Valuation type
A Chart of Account provides a framework for the recording of values to ensure an orderly rendering of accounting data This is used as a key for account determination, to enable a differentiation for the purposes of G/L account assignment. You must assign a chart of accounts to each company code.You must configure automatic account determination separately for each chart of accounts
The Valuation Area is the organizational level at which material is valuated. Plant and company code are two possible valuation areas in the R/3 System. When stock is valuated at plant level, a material in different plants can be valuated at different prices. When stock is valuated at company code level, the valuation price of a material is the same in all of a company's plants
Valuation Grouping code
By activating or deactivating the Valuation Grouping Codes, you can turn on or off the dependency of the Account determination function on the Valuation Area. You must configure automatic account determination separately for each valuation grouping code within a chart of accounts
Valuation Class
The Valuation Class is a key for grouping materials that have the same Account Determination
The relationship between Valuation class and Material Types is established by the Account Category reference. The Account Category reference is a compilation of valuation classes
A material type is assigned to only one account category reference
Account Category Reference
Account Category References link the valuation Classes with the material Types
The combination Material Type-Account Category Reference-Valuation Class determines the G/L accounts updated for a valuation relevant transaction
Business Transactions
In the R/3 System, posting transactions are defined for each transaction in Materials Management that is relevant for Accounting. General posting records are assigned to each transaction or event in a value string
Example of a transaction/ event is a goods mvt or an invoice receipt
Example of transaction/ event keys are BSX for stock posting & PRD for a price difference posting
Example of value strings are WE01 attached to transaction GR for std. PO & WA01 assigned to various GI & other goods receipts
Instead of definite G/L account numbers, this value string contains transaction keys for the relevant posting transaction. The first transaction key for a posting rule usually stands for the debit posting
The posting transactions for the transactions in Inventory Management and Invoice Verification that are relevant for accounting are fixed. Posting records are assigned to each relevant movement type in Inventory Management and to each transaction in Invoice Verification
The assignments of value strings to goods movements and the breakdown of the same into transaction keys can be seen in Customizing for Inventory Management and Physical Inventory, but they can not be changed
In Customizing for Valuation and Account Assignment, G/L accounts for the various posting transactions are mentioned
Regards

No G/L account found in Account determination type ZOFK

Hi Forum,
I have several inoices for which the acct. doc is not generated thru VFX3.
In the header the Posting status shows "Posting document not created (pricing Error)"
If I look in to the inovice's account determination analysis I find for two pricing condition types follwoing message is displayed *"No G/L account found in Account determination type ZOFK"*.
Also in VKOA transaction there is no mention of ZOFK acct. det. condition type. It has all the G/L a/cs are assigned to ZOFI.
Could some body help me how to know why in invoice the system is taking the ZOFK value and not posting it to account.
Thanks.

ZOFK is the copy of KOFK account determination type.................therefore whenever you are doing any costing related accounting entry system will required G/L account and Account Key combination for ZOFK account determination type...
go to VKOA and maintain the G/L account with combination of Account key and Account determination type ZOFK...
Regards,
Ratish
u2003

Account Determination

Hi friends
I got the error while releasing the billing document to accounting,
Posting keys for account determination for transaction EXD do not exist
Message no. F5598
Diagnosis
The posting keys necessary for account determination for transaction EXD have not been set.
System Response
Because the posting key is missing, the system cannot generate any automatic postings.
Procedure
Maintain the posting keys necessary for transaction EXD.
I have checked the Account determination in VKOA also, it is OK.
what could be the solution,
Thanx and Regards
srini

Hi srini,
In almost all customer cases with this error message it arose as a
result of missing customising settings in FI.
The help text on the error states that the posting keys necessary
for the account determination have not been set.
Please ensure that your customising is configured consistently. The
relevant transactions are VKOA and OVUR.
In addition, please review your configuration settings in transaction
OB40 and also the table settings in T007B for your posting keys, to
evaluate which posting indicator has been defined. You can do this
using transaction OBCN.
Hope that the iformation helpful.
regards
Claudia

Dual "Define Account Determination" under SAP Banking ??

Hi, all
There are two "Define Account Determination" transaction under IMG SAP Banking:
1) SAP Banking -> Loans Management -> Transaction Management -> Update Types -> Define Account Determination, which is the same as the one under FSCM/Treasury and Risk Management.
2) SAP Banking -> Loans Management -> Functions -> Accounting -> General Ledger Update -> Define Account Determination
By trial and error, it seems that the later one should be used in Loans Management. Could anyone tell me under which conditions should the former one be used?
Thanks.

We use product types under both SAP Banking->Loans and FSCM/Treasury and Risk, but I never realized that the Account determination for FSCM was included in the IMG path for SAP Banking->Loans.... When I learned Loans configuration, I was pointed in the direction of the Account determination under Functions, and never noticed it elsewhere.
I poked around the IMG a little and it looks like you would use the Account Determination under Update Types if you set up your Loans for parrallel valuation - that is if you need to maintain multiple valuations for Loans. It appears the Account Determination under Update Types appears to be needed for the postings to the parrallel valuation areas.
We don't use parrallel valuation for Loans, so that would be another reason I've not needed the Account Determination under Update Types.
From what I'm seeing in the IMG, I would say that if you only need one valuation for Loans, like we do, then you shouldn't need the Account determination under Update Types - just the one under Functions.
Regards,
Shannon

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.

Error in VF02 (Posting keys for account determination for transaction JTS)

Hi,
I have created new account key JTS and also assigned G/L account in VKOA, But at the time of releasing the billing document to accounting, I am getting the below error;
Posting keys for account determination for transaction JTS do not exist
Message no. F5598

Hi Amanulla,
once we create the Account key in revenue determination we have to assign that account key to respective procedure and condition types.
check that.
please award points.
ravikanth

Transaction key for account determination

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

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

Posting keys for account determination for transaction do not exist

Dear SAP Gurus,
While release to accounting service sale billing bellow error occurs while i made all necessary changes in VKOA.
Posting keys for account determination for transaction do not exist
Please guide me to coorect this error.
With Regards
MK

Dear IMUKUL,
Please search the forum before posting.
Check the following thread and see whether it helps you.
CIN Error
Kindly make it a point to search forum before posting
Thanks & Regards,
Hegal K Charles

Posting keys for account determination for transaction EXC do not exist

hi
i am doing Sales order for 1 month,no error i have got
but now i am getting error
Posting keys for account determination for transaction EXD do not exist
HELP

There will not be any such postings called FI side / SD Side.
Positng always done in Financial perspective only into Certain G/L accounts depends on configuration we did.
As we know,
To post Invoice Conditions in G/L accounts , we configure Account Determination . These tables will be communicated through Account keys maintained in Pricing procedure & in Account determination tables.
To account the stock in Inventory, will configure the same in OBYC - FI/MM Account Determination.- this will be triggered through Movement type - Transaction key / General modifier / Valuation calss / Valution group code n other factors.
In your issue,
Which Postings you are referring to?
In SO creation, Controlling documents will be created ( Ref: COPA - Controlling & Profitablity Analysis Customization)
After PGI in Delivery: Inventory will accounted through OBYC settings
After releasing invoice to Accounting, G/L accounts posted through VKOA settings.
Hope ,now you provide exact information related to your query

Posting keys for account determination for transaction EXD do not exist

hi
i am doing Sales order for 1 month,no error i have got
but now i am getting error
Posting keys for account determination for transaction EXD do not exist
HELP

Hello,
I have following suggestion to overcome this issue.
1. In the t-code "FTXP", check for assignment of the G/L account for the posting key.
2. Check out the SAP Note:200348.
3. In t-code "OBCN",for the account key EXD, make sure that the value of posting indicator is 2.
4. In t-code OBYZ, for the tax calculation procedures, change the key to EXD. The account keys in tax pricing procedures and SD pricing procedures Should be same.
Regards,
Sarthak

Transaction key / event key in account determination??

Similar Messages

Maybe you are looking for