Account determination EIN key

Hi Folks,
While doing Goods Receipt against Purchase Order, I am getting following error:
"Account determination for entry ABBS EIN not possible"
The problem is that I don't want to make posting in EIN rather I want to post in BSX which is already configured.
Please advise how to remove this error.
Regards

Hi,
The purchase account is posted at the time goods receipts and incoming invoices are posted, with the same amount as the stock account. The offsetting entry is posted to a purchase offsetting account. The purchase account is generally not posted upon goods receipts for purchase orders with account assignment.
A freight purchase account also exists. This is used to document delivery costs posted for externally procured materials.
EIN Purchase account
EKG Purchase offsetting account
FRE Freight purchase account
You can change the settings at the following location
SPRO->Materials Management->Valuation and Account Assignment->Account Determination->Account Determination Without Wizard-> Purchase Account Management-> Activate Purchase Account in Company Code
Thanks,
Sandeep

Similar Messages

MM - account determination error

Hi MM Experts,
We have a vendor with currency in USD.After G/R,document has been parked successfully using MR41.But when we tried to post the parked document it gives the error message.
"Account determination for key BIV1KDR is not possible"
Here BIV1 - Chart of Accounts and KDR - Account key for MM exchange rate differences.
Whereas for a different PO raised against the same vendor we were able to successfully post the parked document without any error.(Both the POs were raised on the same date)
Can you pls provide ur valuable inputs to resolve this issue?
Rgds,
Aram K.

for this transaction to pass u will have to put gl account in that key in obyc.
before transaction may be posted as there might be no diffrence in exchange rate
and now for this transaction there might be a diffrence in exchange rate.
so to post this transaction u will have to give gl account in obyc for that key
reward if usefull

Account determination for MM (Valuation)

I get an Error when I do a goods movement (Transaction: MB1B) from plant to plant: Account determination for key entry TELC BSX___ ___ 4100 (Valuation) is not mainatained in MM Customizing, where exactly do I maintain these settings, becasue it is a new plant & storage location that I created.
Thank you.

Hello,
System is finding difficulty in finding the G/L s via Automatic account determination.
Goto T.Code OBYC
Select the transaction type BSX
It will ask for your Chart of Accounts TELC
Then maintain G/L accounts for your Valuation class (4100) against valuained.grouping code if maintained.
Regards

Account determination for entry 1000 AUM

Hello Everybody,
While doing the stock transfer (MB1B) from unrestricted stock to sales order stock system is giving the below error.
"Account determination for entry 1000 AUM 1000 ___ 3100 not possible
    Message no. M8147
Diagnosis
    The system did not find an account for this transaction. This means that
    the account determination for key 1000 AUM 1000 ___ 3100 is not
    maintained in MM Customizing (Valuation). The key is made up of:
    o   Chart of account
    o   Transaction key (= Posting transaction)
    o   Valuation grouping code
    o   Account grouping code
    o   Valuation class
System Response
    The system cannot update a G/L account for this transaction. You cannot
    post the transaction."
*The total quantity of the Material is 600.but if i transfer up to 599 qty system is not giving any error.for 1 qty only its asking    AUM assignment.*
**why system is behaving like this..? where its finding the price difference...?
   Please help me..
Regards,
Srinivas Putty
Edited by: srinu putty on Apr 21, 2010 7:44 AM

hi
goto OBYC here dbl click on AUM and then here give the accounts for the valuation class 3100
SAP help for understanding AUM
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.
regards
kunal

Error M8147 Account determination for entry CPES PRD not possible

Hi all
Im getting this error when a try to make a goods receipt whit trx migo and materials whitout material number and GR goods receip: 101. I try with the trx omjj whith movement type 101 and account grouping and then I don´t know how to do, I read I need a new entry here, but I don´t know how to do this. Some one could tell me if I´m doing the things right or exist any other way to solve this problem?
Here´s the exactly message error.
Account determination for entry CPES PRD not possible
Message no. M8147
Diagnosis
The system did not find an account for this transaction. This means that the account determination for key CPES PRD is not maintained in MM Customizing (Valuation). The key is made up of:
Chart of account
Transaction key (= Posting transaction)
Valuation grouping code
Account grouping code
Valuation class
System Response
The system cannot update a G/L account for this transaction. You cannot post the transaction.
Procedure
Contact your system administrator.
If you have the authorization, check the Account determination in Customizing for Valuation.
Proceed
Note
The relevant posting transaction can be found in Table T030A.
Best regards
Edited by: Alvaro Olmos on Aug 21, 2010 2:36 PM
Edited by: Alvaro Olmos on Aug 21, 2010 2:40 PM

Hi,
Use t.code: OBYC, Double click PRD, Enter Chart of Account.In next screen ,click RULES in application tool bar & then in next screen select check box of Debit/Credit but do not select check boxes valuation class, valuation Modifier & account modifier & save.( not required as price difference will goto one generic G/L).
Now come back & again use t.code: OBYC, Enter Chart of Account, Double click PRD & enter your G/L account for Debit/Credit& save.
Now try your transaction doing MIGO, you would not have any error now.
Better involve FICO consultant for the above steps.
For more check the link:
http://www.scribd.com/doc/2531210/SAP-FI-GL-CONFIGURATION
Regards,
Biju K

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 :Posting keys for account determination

Hi, Gurus,
      please suggest the solution for the following problem.
            we are selling two types of materials, one is the product material and the second one is the scrap material.Different type pricing procedures, sale order,delivery and billing types were configured for the same. For CST and VAT   same condition type :"ZCST - for CST " and ZVAT - for VAT" were used in both pricing procedure and the standard account keys : MW1 for ZCST and MWS for ZVAT and same G/L accounts configured .
.                                                   key combination for the condition types as mentioned below:
.                                                        ZCST: Country/PlntRegion/Region/TaxCl2Cust/TaxCl.2Mat
                                                         ZVAT: Country/PlntRegion/Region/TaxCl1Cust/TaxCl.Mat
     Now we want to capture CST and VAT seperately for both the materails.For that two new account keys created and incorporated the same in scrap pricing procedure and and new G/Ls created and assigned .Now the system is throwing following error while while releasing the billing document to accounting document.
Posting keys for account determination for transaction Z48 do not exist
Message no. F5598
here Z48 is the new accounting key created for the CST tax.We tried all the possibilities, but system is throwing the same error.
with regards
sam

Thank u for ur response.Now it is solved when OB40 and OBCN maintained.Here I am facing a new problem.pl. provide the solution.we configured twoseperate pricing procedures for our product and scrap material.We have configured same condition types for VAT(ie.condition type:ZVAT) and CST(cond type:ZCST), in both pricing procedures. Now We want to maintain seperate condition types for VAT and CST for pricing procedure for Product material and Scrap material. I have created two new condition types for scrap sales ZSCT- cst for scrap and ZSVT-vat for scrap by copying the same from existing conditions ZCST & ZVAT, and the same is included in the scrap pricing procedure. And also maintained OB40,OBCN,OVK1,OVK3,OVK4, FTXP,FV11 and VK11.
now I am facing the following problems.
1. while creating the Material master & customer master, in tax category sub screen all conditions i.e. conditions defined for product material( ZCST,ZVAT) and defined for scrap material (ZSCT, ZSVT) displaying and these are compulsory fields.
2. While creating the sale order for scrap material, system is considering the TAX classes from ZVAT/ ZCST (defined for product material) and taking the condition value from the condition type ZSVT/ ZSCT with the TAX class values of ZVAT/ZCST.
Now I would like to know is there any procedure to assign the Material type and Customer group to Tax category.
Thanks & Regards
sam

Account determination not possible for key 3000

Hi gurus,
While generating invoice iam getting the error like
"Account determination not possible for key 3000"
3000 is comapny code.
it shows the Diagnosis
"The system could find no entry for the following key combinations in the entries for account determination:"
"Chart of accounts
Posting area Billing Default Values: Repayment Method (R401)
Key 3000
Field names BUKRS "

Hi,
For the error, go to details, and check the main/sub transaction. From there you can navigate thru error analysis and it will take you to the configuration details in SPRO. Check for the key specified in the error log, if the entry is present or not. If not maintain the entries accordingly.
Alternatively
Please check the configuration for Automatic GL account determination.
Please check if the GL determination is made for the main transaction and sub transaction for which it is giving the error.
Path -: SPRO -> Financial accounting -> Contract Account receivable and payable -> basic functions -> Postings and documents -> document -> define account assignments for automatic postings -> Automatic GL determination.
Check for ISU : Define account assigment data related to main transaction and data relevant to transaction.
Alternatively check tcodes EK01 / EK02.
Hope this helps!!
Regards,
Rajesh Popat

Maintain account determination (table T030B) for posting key IRX (M8395)

Dear Guru,
I am testing IS-OIL - Exchanges.
Created Exchange Agreement and Purchase Contract and Sales Contract, Purchase Contract and Sales Contract are assigned to the Exchange Contract.
A PO is created with reference to the Purchase Contract.
Upon post goods receipt in MIGO, encountered error message "Maintain account determination (table T030B) for posting key IRX (Message no. M8395)" that does not allow PGR to get through.
A call-off is created with reference to the Sales Contract.
Similarly, when PGI is performed in VL01N, encountered error message "Maintain account determination (table T030B) for posting key IGX (Message no. M8395)" that does not allow PGI to get through.
Checked in OBYC, there is no transaction key for IRX and IGX.
Please advise. Thank you.
Regards,
WL

Hi WL,
In an Exchange scenario, the account determination entry would have to go added through tcode O54E for this purpose. You would see both the IRX and IGX entry in the above mentioned tcode.
Menu path: IS-OIL Downstream --> EXG --> Account Assignment
You would not be able to see the IRX or IGX transaction key in OBYC.
Hope the above helps.
Thanks.
Edited by: Kok Wai Phang on Jul 10, 2011 7:58 AM

Reg.Error in account determination: table T030K key NCCA EXD

Dear Friends
we are doing domestic sales for that I am doing pricing procedure, I create 5 condition types without access sequence,and I manualy enter all the mrp price,mrp discount,bed,eces,shec and cst in billing, during the billing release I am getting the error
" Error in account determination: table T030K key NCCA EXD" Diagnosis In the chart of accounts to be posted to, no accounts are defined for the tax code you used. " in VKOA I maintained the account key ERL,MWS and EXD,and also in OBCN and OB40 but I am getting the same error.
do I need to create separate procure for pricing ? or can I use the same procedure which in SD.
do I need to change the TAXINJ and put the EXD there ? I am unable to solve this problem. Please help me .
Thanks
Rajakumar.K

FYI, as per SD pricing for tax condition type is concern, it doesn't require tax procedures to be maintain.
Tax % with correspondingly tax codes are maintain & determine from Condition record in to the pricing of sales doc.
These kind of error occurs due to non determination or missing tax code in sales doc pricing.
In turn, raises error due to accounting interface.
So, as per best practices, tax condition type are determined through condition record in sales document.
Thus, you ought to have access sequence for tax condition type & should create condition record with respective TAX % & Tax code. By, manually processing tax values into pricing, you will be able to maintain tax %, but without TAX CODE.
I hope this can assist you.
Thanks & Regards
JP

FI-SD integration issue Error in account determination: table T030K key NECA EXD Message no. FF709

Dear expert.
Thank you for adding me at your professinal network Linkedin. I am getting some issue related to FI-SD integration.
IT's coming while releasing billing document in Tcode VF02.
Error in account determination: table T030K key XXXX EXD
Message no. FF709
I look into Tcode VKOA- Acct determination for Cust Grp Mat Grp for sales organization for EXD, OB40 - EXD AcctKey, V/08- checked procedure Zneac.
And also maintained the taxcode in Vk11.
But i am not able to understand the issue.
Please reply with valuable suggestion.
Thanks in advance.
Regards Mani.
manibhushanchoubey8 at the rate gmail dot com

Hi
Please check below links
Error in account determination:T030K
Msg no.FF709 Error in account determination: table T030K key INT VS1 I0
Note: Please search in the forum before posting the issue
Thanks
Dasaradha

Error in account determination: table T030K key 1000 MW1 Message no. FF709

Dear Gurus
We have activate automatic release to account at VF01 level. For one billing doc system is giving us error
Error in account determination: table T030K key 1000 MW1Message no. FF709
At Environment -> Act determination analysis here the system is not giving any error. But accounting entries are not there and Excise accounting entries are generated and showing there.
When we check at header level Header tab Accounting data block Posting status system is showing Error in Accounting Interface.
We have assign MW1 accounting key for CST condition Type.
Assignment in VKOA is also done.
In OB40 tax code and the GL is also done.
Reetesh NIgam

hello, friend.
when you configure account determination, you assign not only account assignment groups (customer, material) to GL accounts, you also need to make assignments for taxes, represented in SAP default by the posting key MWS.
an example assignment in account determination, procedure 5 (General) would be as follow:
Applic/Ty/Chart of Accts/Sales Org/Act Asg Grp/Act Asg Grp/Account key/GL accounts
V   KOFI   INT   1000   01   01   ERL   xxxxxx
V   KOFI   INT   1000   01   01   ERS   xxxxxx
V   KOFI   INT   1000   01   01   ERF   xxxxxx
V   KOFI   INT   1000   01   01   MWS   xxxxxx
please check if your tax condition type/s are included in your pricing procedure and have been defined in FI.
regards.

VF02 - Error in account determination: table T030K key HCL ZAT

Hi,
I am getting following problem, while releasing my billing for accounting (VF02):
"Error in account determination: table T030K key HCL ZAT" Message no. FF709
System is giving this message, However account is already there in table T030K.
Please help.
Regards,
Sandeep

Hi,
I have already checked and entry is there.
Sandeep

Error in account determination: table T030K key CNFX MWS

Hi,
     i have a issue when releasing the billing document .i have a issue like "Error in account determination: table T030K key CNFX
     MWS". Actually iam trying to map the scrap process. User requirement is , when upload the non valuated material Stock, that
     material should be selling to the customer . User's wants to GL account (other revenue) should update the value only .
    i created new material account assignment group. i did GL assignment with combination of customer and material account
    assignment group and sales organisation.
     where i made mistake?
    can you help me for configuration.
WIith regards
dinesh
Edited by: code acess on Jul 26, 2011 8:09 AM

Hi,
Maintain account determination for tax in VKOA
Select last combination ACCOUNT KEY
maintain entries for combination of CNFX + Sales orgz.+ MWS = your tax account
Kapil

Error in account determination: table T030K key SCOA JN6 A5

Hi,
While posting the billing dicument Iam getting the error like .Error in account determination: table T030K key SCOA JN6 A5.
(Here SCOA : Chart of Accounts.)
Plz let me know the Answer.
thanking u.

hi,
go to transaction code SE11 and enter the data base table=T030k
and then click on the display button
then go to utilites in the menu bar from there go to table contents go to new entries
and enter
KTOPL= your chart of accounts
KTOSL=jn6
MWSKZ=A5
and save it
hope this will resolve your problem
reward points if the answer is helpful
REgards,
Murali

Account determination EIN key

Similar Messages

Maybe you are looking for