Transaction -FTXP - Tax Accounts

Hi ,
In transaction FTXP i have given a output tax.
When i click Tax Accounts(in application tool bar) ,there is no value in G/l Account & it is disabled.
how to enable that field? to give G/L account.

In OB40 for each combination of Chart of accounts - Transaction Key - Tax code, GL accounts are maintained.

Similar Messages

Tax accounts set up in FTXP

Can anyone please tell me of How I can have Tax accounts set up for a 'Transaction'(Ex:NVV for A/P Sales Tax1) in FTXP, Or Assign Tax Procedure to 'NVV' Trans. in OB40. I am not even able to see the Transaction NVV assigned to the Tax Procedure when I view the screen(FTXP).

Hi,
You can check it from T-code OBCN. Here you can find NAV and NVV.
Following is setting from my system :
NAV : Non-deduct.input tax > Posting indic. 2 Separate line item
NVV : Non-deduct.input tax > Posting indic. 3 Distribute to relev
Posting indic. 2 let you can see from t-code : OB40.
If you change NAV Posting indic. from 2 to 3, then you can't find NAV from tcode OB40.
Please. review following note for NVV and for further information on settings, pls. refer Online documentation.
SAP Note No. 425193 Account assignment with non-deductible tax
Please assign points if it useful.
Regards
Ravinagh Boni

What's the difference between tax account in FTXP and OB40

Hi all,
There are two tax accounts link to same tax code in FTXP for different company codes, but in OB40 I only can assign one account to tax code. What's the difference between tax account in FTXP and OB40?
Thanks in advance.
babyyw
Edited by: babyyw on May 5, 2010 8:21 AM

Hi,
FTXP no need to create a request and it is easy but in OB40 system will ask you create request. and another thing is in FTXP it is at country level but in OB40 it is at chart of accounts level.

Transaction for tax code

transaction for tax code

T.Code: FTXP
Difference between TAXINJ & TAXINN is in TAXINJ, Tax rate is picked based on rates maintained in Tax Code, whereas in TAXINN, Tax rate will be picked from condition record, but if Tax code is missing in condition record, Transaction will flow upto billing, but not release to accounting.
Regards,
Rajesh Banka

Ftxp tax code

Hi,
1 I have the below list of tax category to choose from in FS00. May I know why only A0 and V0 exist in FTXP?
- Only input tax allowed
+ Only output tax allowed
All tax types allowed
< Input Tax Account
> Output Tax Account
A0 Output Tax - 0 %
V0 Input Tax - 0 %
2 what is procedure in FTXP?
Thanks
Rgds

Hi,
A0 and V0 are two Zero tax % codes means they dont have any Tax rate (0%) . These Tax codes are codes for certain GL accounts where Tax category is preesent but if the transaction is not attracting any tax but if the tax field is required then these two tax codes will be used based on the business transaction (input or output).
In FTXP you will define tax codes with the tax rate and GL account to which VAT will be posted.
Regards
Srikanth
Edited by: boddupalli srikanth on Sep 15, 2009 6:44 PM

Action canceled for transaction ftxp

I'm trying to understand the difference of behavior for transaction ftxp between my quality and production system.
If I execute FTXP on QAS, the action is canceled (message tk495).
There is nothing in ST22, SM21, SU53...
I need to open the client in transaction SCC4, and then it works...
But if I execute FTXP on PRD, it works directly. I don't even have to open the client.
My user has sapall permission in both systems...
Do you have any idea or suggestion ?
Maybe this is a customizing configuration...I don't know...
Eduardo

This is allowed in production because the client has a role "production", which does allow you to execute.
Whereas in the Quality, you need to open the client inorder to copy or transport.
This is the expected behavior because you are trying to do client specific changes.
By the way, you can do it in your dev and transport it to your quality.
Any tax account adjustment you have to manually do it quality by opening your client.
Also message tk495 may be due to your authorization or client setting.
Link: [https://service.sap.com/sap/support/notes/356483]

Error in Tax account determination

Hi experts,
When i am trying to release by billing document by using t-code VF02 i am getting error:
"Error in account determination table T030K Key xxx MWS"
I checked config but could not find any thing
Can anyone help me to resolve this?
thanks,
Vani

DEFINE TAX ACCOUNTS
PATH: SPRO  FINANCIAL ACCTG  FIN ACCTG GLOBAL SETTINGS       TAX ON SALES/PURCHASES  POSTING  DEFINE TAX      ACCOUNTS
TRANSACTION CODE     -     OB40
DOUBLE CLICK ON VST INPUT TAX
GIVE THE CHART OF ACCTS          -     GES
PRESS ENTER & SAVE
GIVE THE ACCOUNT NO.          -     200155 (VAT POOL A/C)
 SAVE & SAVE IN YOUR REQUEST
SELECT BACK ARROW
DOUBLE CLICK ON MWS OUTPUT TAX
PRESS ENTER & SAVE
GIVE THE ACCOUNT NO.          -     200155 (VAT POOL A/C)
 SAVE & SAVE IN YOUR REQUEST

Assign Project Code to Tax account automatically

Hi Everyone:
When I assigned a Project code in a Marketing document, why in the Journal Entry the tax account does not assign automatically the project code the way the others accounts does?. Is there any way to achive this?
Thanks
Claudia

Hi,
Check this thread...
[Re: Project code is not tagged against service tax in transactional J.E.|Re: Project code is not tagged against service tax in transactional J.E.]
Thanks
Sachin

BAPI_ACC_DOCUMENT_POST. Why tax account is replaced ?

The code as follow:
REPORT YC_BAPI_ACC_DOCUMENT_POST.
* bapi
CLEAR:BAPI_HEADER,
      BAPI_ACCOUNTGL,
      BAPI_ACCOUNTRECEIVABLE,
      BAPI_ACCOUNTPAYABLE,
      BAPI_ACCOUNTTAX,
      BAPI_CURRENCYAMOUNT,
      BAPI_RETURN,
      BAPI_EXTENSION2,
      LS_ACCOUNTGL,
      LS_RECEIVABLE,
      LS_ACCOUNTPAYABLE,
      LS_ACCOUNTTAX,
      LS_CURRENCYAMOUNT,
      LS_EXTENSION,
      LS_EXTENSION_BAPI.
* set header
CLEAR BAPI_HEADER.
BAPI_HEADER-DOC_TYPE    = 'SA'.   "u51EDu8BC1u7C7Bu578B
BAPI_HEADER-COMP_CODE   = '1000'.   "u516Cu53F8u4EE3u7801
BAPI_HEADER-BUS_ACT     = 'RFBU'.           "u4E1Au52A1u8303u56F4
BAPI_HEADER-DOC_DATE    = SY-DATUM.   "u51EDu8BC1u65E5u671F
BAPI_HEADER-PSTNG_DATE = SY-DATUM.   "u8FC7u8D26u65E5u671F
BAPI_HEADER-HEADER_TXT = SY-DATUM.   "u9879u76EEu62ACu5934u6587u672C
BAPI_HEADER-FISC_YEAR   = SY-DATUM+0(4)."u5E74u5EA6
BAPI_HEADER-FIS_PERIOD = SY-DATUM+4(2).   "u671Fu95F4
BAPI_HEADER-REF_DOC_NO = ''.   "u53C2u8003u51EDu8BC1u7F16u53F7
BAPI_HEADER-HEADER_TXT = ''.   "u51EDu8BC1u62ACu5934u6587u672C
BAPI_HEADER-USERNAME    = SY-UNAME.             "u8BB0u8D26u7528u6237
* set items
CLEAR LS_ACCOUNTGL.
LS_ACCOUNTGL-ITEMNO_ACC = 1."u884Cu9879u76EEu53F7
LS_ACCOUNTGL-GL_ACCOUNT = '0000154001'.
LS_ACCOUNTGL-TAX_CODE    = 'V2'."u7A0Eu7801
*LS_ACCOUNTGL-ACCT_KEY    = 'VST'.
*LS_ACCOUNTGL-ACCT_TYPE   = 'S'.
*LS_ACCOUNTGL-COND_CATEGORY = 'D'.
APPEND LS_ACCOUNTGL TO BAPI_ACCOUNTGL.
CLEAR LS_ACCOUNTGL.
LS_ACCOUNTGL-ITEMNO_ACC = 2."u884Cu9879u76EEu53F7
LS_ACCOUNTGL-GL_ACCOUNT = '0000078200'.
APPEND LS_ACCOUNTGL TO BAPI_ACCOUNTGL.
* set currency
LS_CURRENCYAMOUNT-ITEMNO_ACC   = 1. "u884Cu9879u76EEu53F7
LS_CURRENCYAMOUNT-CURRENCY     = 'EUR'. "u8D27u5E01u7801
LS_CURRENCYAMOUNT-CURR_TYPE    = '00'.               "u91D1u989Du7C7Bu578B
*LS_CURRENCYAMOUNT-EXCH_RATE    = ''. "u6C47u7387
*LS_CURRENCYAMOUNT-AMT_DOCCUR   = 100. "u51EDu8BC1u8D27u5E01u91D1u989D
*LS_CURRENCYAMOUNT-AMT_BASE     = 1427.
APPEND LS_CURRENCYAMOUNT TO BAPI_CURRENCYAMOUNT.
CLEAR LS_CURRENCYAMOUNT.
LS_CURRENCYAMOUNT-ITEMNO_ACC   = 2. "u884Cu9879u76EEu53F7
LS_CURRENCYAMOUNT-CURRENCY     = 'EUR'. "u8D27u5E01u7801
LS_CURRENCYAMOUNT-CURR_TYPE    = '00'.               "u91D1u989Du7C7Bu578B
*LS_CURRENCYAMOUNT-EXCH_RATE    = ''. "u6C47u7387
LS_CURRENCYAMOUNT-AMT_DOCCUR   = -100. "u51EDu8BC1u8D27u5E01u91D1u989D
APPEND LS_CURRENCYAMOUNT TO BAPI_CURRENCYAMOUNT.
* tax items currence
CLEAR LS_ACCOUNTTAX.
LS_ACCOUNTTAX-ITEMNO_ACC = 3.     "u884Cu9879u76EEu53F7
*LS_ACCOUNTTAX-GL_ACCOUNT = '0000154001'.
LS_ACCOUNTTAX-TAX_CODE   = 'V2'."u9500u552Eu7A0Eu4EE3u7801
*LS_ACCOUNTTAX-TAX_RATE   = LV_FWSTE.        "u9500u552Eu7A0Eu7387
*LS_ACCOUNTTAX-DIRECT_TAX = 'X'.
*LS_ACCOUNTTAX-ITEMNO_TAX = 1. "u7A0Eu76F8u5173u884Cu9879u76EE
*LS_ACCOUNTTAX-ACCT_KEY = 'VST'.
*LS_ACCOUNTTAX-COND_KEY = 'MWS'.
APPEND LS_ACCOUNTTAX TO BAPI_ACCOUNTTAX.
CLEAR LS_CURRENCYAMOUNT.
LS_CURRENCYAMOUNT-ITEMNO_ACC   = 3.    "u884Cu9879u76EEu53F7
LS_CURRENCYAMOUNT-CURRENCY     = 'EUR'."u8D27u5E01u7801
*LS_CURRENCYAMOUNT-EXCH_RATE    = LS_ZCNTPDM01-KURSF."u6C47u7387u7801
LS_CURRENCYAMOUNT-AMT_DOCCUR   = 100."u7A0Eu91D1
LS_CURRENCYAMOUNT-AMT_BASE     = '1427.1'."u7A0Eu57FA
*LS_CURRENCYAMOUNT-TAX_AMT       = 100.
APPEND LS_CURRENCYAMOUNT TO BAPI_CURRENCYAMOUNT.
*   extend the reason code
CLEAR LS_EXTENSION.
LS_EXTENSION-POSNR = 1. "u884Cu9879u76EEu53F7
LS_EXTENSION-BSCHL = '40'. "u8BB0u8D26u7801
LS_EXTENSION_BAPI-STRUCTURE = 'ZEXCEL'."u81EAu5B9Au4E49u6269u5C55u7ED3u6784
LS_EXTENSION_BAPI-VALUEPART1 = LS_EXTENSION. "u6269u5C55u7ED3u6784
APPEND LS_EXTENSION_BAPI TO BAPI_EXTENSION2.
CLEAR LS_EXTENSION.
LS_EXTENSION-POSNR = 2. "u884Cu9879u76EEu53F7
LS_EXTENSION-BSCHL = '50'. "u8BB0u8D26u7801
LS_EXTENSION_BAPI-STRUCTURE = 'ZEXCEL'."u81EAu5B9Au4E49u6269u5C55u7ED3u6784
LS_EXTENSION_BAPI-VALUEPART1 = LS_EXTENSION. "u6269u5C55u7ED3u6784
APPEND LS_EXTENSION_BAPI TO BAPI_EXTENSION2.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
      EXPORTING
        DOCUMENTHEADER    = BAPI_HEADER
      TABLES
        ACCOUNTGL          = BAPI_ACCOUNTGL
        ACCOUNTRECEIVABLE = BAPI_ACCOUNTRECEIVABLE
        ACCOUNTPAYABLE     = BAPI_ACCOUNTPAYABLE
        ACCOUNTTAX         = BAPI_ACCOUNTTAX
        CURRENCYAMOUNT     = BAPI_CURRENCYAMOUNT
        RETURN             = BAPI_RETURN
        EXTENSION2         = BAPI_EXTENSION2.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
LOOP AT BAPI_RETURN INTO LS_RETURN.
WRITE:/ LS_RETURN-MESSAGE.
ENDLOOP.
In FB03, The generated document as follow:
1000     1     50          78200     Transfer of reserves     100.00-     EUR
1000     2     40          154000     Input tax     100.00     EUR     V2
=========================================================
If i create a document in FB01 with the above data, the generated document as follow:
1000     1     50          78200     Transfer of reserves     100.00-     EUR
1000     2     40          154001     Input tax     100.00     EUR     V2
So, what i should do if i want '154001' in generated document by BAPI.
Please help me.
Thanks.
Edited by: y_ch_19 on Sep 28, 2011 11:09 AM
Edited by: Thomas Zloch on Sep 28, 2011 11:22 AM

Hi Vijaymadhur,
Thank you very much.
I check the reason is not enhancement or exit.
In t-code: FTXP, i see the tax code 'V2' corresponding the tax account '154000',
when execute the BAPI, the system determine the tax account by the tax code,
but i have no idear how to set the parameters in BAPI with no tax account replaced.
CLEAR LS_ACCOUNTTAX.
LS_ACCOUNTTAX-ITEMNO_ACC = 3.     "u884Cu9879u76EEu53F7
*LS_ACCOUNTTAX-GL_ACCOUNT = '0000154001'.
LS_ACCOUNTTAX-TAX_CODE   = 'V2'."u9500u552Eu7A0Eu4EE3u7801
*LS_ACCOUNTTAX-TAX_RATE   = LV_FWSTE.        "u9500u552Eu7A0Eu7387
*LS_ACCOUNTTAX-DIRECT_TAX = 'X'.
*LS_ACCOUNTTAX-ITEMNO_TAX = 1. "u7A0Eu76F8u5173u884Cu9879u76EE
*LS_ACCOUNTTAX-ACCT_KEY = 'VST'.
*LS_ACCOUNTTAX-COND_KEY = 'MWS'.
APPEND LS_ACCOUNTTAX TO BAPI_ACCOUNTTAX.

FP04 : Write off and debiting Tax accounts

Dear All,
I have an issue with debiting tax account on write off.
Scenario: Invoice posted $1000 including tax of $100. i.e $900 consumption (revenue) + $100 tax.
GL Postings:
Customer account 1000 Dr
Revenue Account   900 Cr
Sales tax                 100 Cr.
Write off( FP04 any reason codes).
System posts the Following:
Customer account 1000 Cr
Expense Account 1000 Dr
I need it to be like:
Customer account 1000 Cr
Expense Account   900 Dr
Sales tax                 100 Dr.
I've tried everything I can, but I think I'm missing something very obvious and silly.
1) Maintained posting areas:
0120 : Expense Account (No tax code specified and tried with tax code too)
0121 : Expense Account for non tax related items (same expense account)
0122 : Tax Adjustment Flag (Tested with both flag on and off)
2) Define Act Assignments ReLU to Main Transactions
Company     Division     Act Deter        Main       Acct
1000     10          01-10               0090       Expense account
1000     10          01-10               0095       Expense account
3) ISU u2013 Define Acct Assignment Relv to Transactions
Set Main receivable account (Customer account) for all combination of 0090 and 0095. i.e. 0010 and 0020.
Company     Division     Act Deter              Main/Sub      Acct
So what am I doing wrong?
Thank you very much.
Edited by: JayUtility on Jan 31, 2012 2:53 PM

Thank you Ivor. Tried that too.
I'm still stuck at:
Customer (AR) Account 1000 Cr
Expense           Account 1000 Dr
The entire invoice amount is debiting against the Expense / bad debt account.
I need that only the consumption portion should debit Expense account and the Tax portion should debit the Tax account.
Customer account 1000 Cr
Expense Account    900 Dr
Sales tax                 100 Dr.
It seems like an easy enough thing. I must be missing something.

Tax account different currency than document

Experts,
I have a client who need to create a US Dollar AR Invoice but track the Tax on that Invoice in Euro on the accoutn level.
I have created a Sales Tax Account that only allows Euro currency, but when I enter this Invoice, I get an error on the currency in that account.
Is there no way to have 2 currencies in one document?
Thanks,
Marli

Hi Marli.......
Transactions in Two different currencies are not possible at a time. If you want it to be happened then go for Multicurrency transaction. Here at the time of transaction put the Ex rate for US Dollar as well as for EURO.
When you run the ex rate report hope this will give you correct effect.
I would suggest you to do it in Demo version.....
Regards,
Rahul

Transaction FTXP and BDC recording

We need to maintain TAX Code and TAX JURISDICTION/RATE data. For the same we are using transaction FTXP.
When we tried to update values manually, it was successful. But I created BDC (tcode: SHDB) for it, and but this BDC wasn't able to update above mentioned data.
I believe the problem is SCROLLING on RATE screen, because BDC is giving an error "Field L_KBETR (7) is not an input field" (to update this field we need to do page down, it is at the bottom).
Could you please help me with this issue? also is there any other way to update TAX Code and TAX JURISDICTION/RATE data i.e. substitute to TCode: FTXP?
Kind Regards,
Nikhil J

There is not a simple solution, and sometimes the scrolling may not be handled at all in BDC mode (then it needs a modification of standard if you really want to make it work).
For a detailed explanation, look at [the BDC FAQ wiki about table control scrolling|http://wiki.sdn.sap.com/wiki/display/ABAP/BatchInputFAQ#BatchInputFAQ-Howtoscrollatablecontrol%3F].

Credit Memo Error AR-RAXTRX: TAXACT ERROR- Others Exception in Tax accounti

Hi All,
We are getting the following error when we interface Credit Memo record to AR using Auto Invoice
Error Message: AR-RAXTRX: TAXACT ERROR- Others Exception in Tax accounting routine
This is not the actual error
Following is the setup
Transaction Type for Credit Memo and Invoice ( Creation Sign: Allow any Sign )
Now first create a Invoice with following line amounts ( Using Auto Invoice )
Line 1 : 100
Line 2 : 500
Line 3 : - 300
Now Create a Credit Memo using LIFO rule having following line amount
Line 1 : -100
Line 2 : -500
Line 3 : 300
On submitting the Auto Invoice import program, the Concurrent program error out.
Following is the Snippet from CP
AR-RAXTRX: TAXACT ERROR- Others Exception in Tax accounting routine
Error calling raacae()
Error calling raapic()
Following the above example if we have a invoice
Invoice Amount 300
Line 1 : 300
Line 2 : 200
Line 3 : -200
Now create a credit memo using LIFO rule using following line type
Line 2: -200
Line 3: 200
The credit memo gets created but with no distribution on the credit memo.
This lead me to think there is some issue with the distribution.
Note we have no tax on the invoice neither we have any tax distribution records on the invoice.
Any suggestion/advice/ solution on the above error. Btw on account Credit Memo works okay.
Thanks.

What is the complete error message? Please post it here.
Please see if these docs help.
Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 [ID 1075757.1]
AutoInvoice Setup for Release 12: A Case Study Using a Simple Script [ID 1067402.1]
If none of the above helps, please log a SR.
Thanks,
Hussein

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.

State wise tax accounts

Hi,
My client requirment is to create the tax ( VAT and CST) accounts state wise.
How can i configure this.
what are the steps involved in to set up the scenario.
Thanks and regards

Hi Kuldeep,
You can do this by using State Jurisdiction code. You will have to create Jurisdiction code for each state & one for the country as a whole . Generally CST is not maintained Statewise. Path
Financial Accounting Global Settings (New)> Tax on Sales/Purchases>Basic Settings......
Maintain the following
Check Calculation Procedure
Assign Country to Calculation Procedure
Check and Change Settings for Tax Processing
Specify Structure for Tax Jurisdiction Code
Define Tax Jurisdictions
--> Calculation
Define Tax Codes for Sales and Purchases
Assign Company Code to Document Date for Tax Determination
Specify Base Amount
--> Posting
Define Tax Accounts
Define Account for Exchange Rate Difference Posting
Assign Tax Codes for Non-Taxable Transactions
Transfer Posting of Tax for Cross-Company Code Transactions
Thank You.

Transaction -FTXP - Tax Accounts

Similar Messages

Maybe you are looking for