RFEULIST CZ - No. of tax-relevant docs

Hi all,
In TC RFEULIST (prg. RFASLD15, EU Sales & Purchases list for CZ, PL, HU) there is a column "No. Docs" in the report (field NO_OF_DOCUMENT). This is...
Number of Tax-Relevant Documents
Specifies the number of documents that the report has selected, in accordance with the entries on the report selection screen.
...and is required only for Czech Republic (obligation to report number of taxable events within EU). When we run the report with checkbox "Line item display" then the output lists every single invoice. Hence, I would anticipate that this column must always contain "1" since 1 invoice = 1 tax-relevant document. However, there are some lines with value "0". In the xml file we then have correct amounts per services and good deliveries but the number of documents is shortened.
Does anyone have an idea how this value is determined and why it is possible to have zero document count per line?
thanks to all,
John

I found that the problem is with multiline documents. These have only 1 line displayed, the column for item number displays the higgest item number, the amount is correctly displayed as a total of all items and the column "No. Docs" contains zero.
The generic EC Sales List TC S_ALR_87012400 shows correctly every single line for multiline docs.
I did not find any Note about this...

Similar Messages

  • Error in GR/IR - Tax relevancy

    We are implementing SAP ECC6 in a country where there is no tax.  But during the settings, settings requires to assign a tax procedure and for posting certain accounts like GR/IR clearing, tax relevant setting is required as a mandatory from the system.  How can we avoid this situation since we are in a country where no tax is there?
    Regars

    Hi Friends
    What you have suggested to this issue is to make posting with a zero percentage tax code by making the all tax allowed setting in the GL master.
    But, since we are operating in a country where there is no tax, is there any other way we can make setting so that system will not issue any message about the tax relevancy in postings ?

  • Error to Define Tax Relevancy Of Master Records

    Hi ,
    I created a condition type ( Y007)  with category as 'D' ( TAX) and  class as 'A'. and then i tried to  Define Tax Relevancy Of Master Records ( Customer taxes) but it gives the message "Condition type Y007 is not defined for taxes" . its fine when i use the class as 'D' or 'G' but the requirement is it should be 'A' as discount or surcharge.
    Any one can help on this if  this is possible??
    if not then the other situation is if i use class as 'D'  or 'G' then in the section"changes which can be made" the calculat. type disappears...is there any way to have it appear on the screen??
    thanks...

    Hi
    For tax condition types, condition class should also be D.
    Pls check the configuration for MWST condition type. If you have the need to create a new condition type, please copy MWST or some standard tax condition type and create a new one, instead of creating a new condition type itself. Also check for the access sequence. For tax condition types most of the times MWST access sequence will be the correct one.
    So, the tax c.type should have D both in condition category and condition class.
    You can have c.class as D (Not G) and then you can have the calculation type as A
    Rwd points if it helps.

  • Inter-Company accounts tax relevance

    Hi
    This is more a Finance question related to SAP. I am aware that Inter/Co trnasactions are not normally tax relevant (E.g. Company A sells products to Co B).
    However, we have a scenario, where one company pays (with tax ) for certain outside supplyon behalf of another I/Co. The I/Co accounts are created as "Not tax relevant" and hence the system is throwing an error message (I/C account does not allow P1).
    In my opinion, in this scenario, the I/Co accounts need to be tax relevant. I would like to know best practice approach.
    Thanks
    NW

    Hi,
    You can use the tax processing in the intercompany scenario.
    This is normal as the company paying to outsider pays the tax also and then recover the total amount from the other company.
    Regards,
    SDNer

  • Tax Relevancy of Mater Records

    Hi CIN Gurus
    We are implementing  my SAP ERP  ECC 6.0,we are using TAXINN procedure
    We are trying to maintain Tax relevancy for Master Records
    In the Customer master,Material master for tax LST ,CST tax category JLST,JCST
    is there,
    Now to introduce VAT conditions in Customer master ,material master which type of Tax Category has to be Adopted ,Kindly let me know the procedure for this
    Immediate response will be appreciated
    Regards
    Guruprasad

    Hi Guru,
    You will have only define Customer Tax classification and mAterial Tax classifications in Customer and material master. As tax gets detrmined based on 4 rules:
    1. Delivering Plant (country of shipping point)
    2. destination country
    3. customer tax classification &
    4. material tax classification
    You determine the procedure and deince the tax categories in IMG. and define the Tax codes also representing LST/CST /VAT etc. Against each tax code maintain the tax data.
    For Condition Type MWST maintain a tax code in condition record as per the access sequence what you want. system will read the Pricing procedure in the sales order and read MWST condition type. Against MWST system will read the access sequence what you have maintained and read the Tax code and against the tax code you have maintained in FTXP whether this tax code determines CST / LSt/VAt and what is the % .
    Hope this clarifies. pl go thr below links for more info:
    http://help.sap.com/saphelp_47x200/helpdata/en/09/ebf138cdd78a4be10000000a114084/frameset.htm
    http://help.sap.com/saphelp_47x200/helpdata/EN/40/a23c39129ffe2ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_47x200/helpdata/EN/40/a23c39129ffe2ee10000000a114084/frameset.htm
    http://sap-img.com/sd009.htm
    Incase you want any clarifications pl give revert back.
    REWARD IF IT HELPS
    regards
    Srini

  • Check issue account tax relevant field

    Friends,
    I have created a check issue account with selecting tax category * and posting without tax allowed fields in control data.  while posting F-48 if i am trying to give check issue account in bank account field then system is giving error message Tax relevant accounts not defined inthis are.  Then after correcting the GL master by removing the tax category and posting without tax fields as blank then system is accepting the postings.
    What is the logic.  and exactly for which accounts we have to select tax category and posting w/o tax fields in control data in gl master.

    hi,
    so you've to populate tax code (/ no tax code) for every line-item. You can determine whether tax code is nedded or not with field SKB1-MWSKZ
    A.
    Message was edited by: Andreas Mann

  • Tax Relevant Classification

    Hi,
    Refer to note 178824, I have to setup VK11 to the table 397.
    But It doesnu2019t allow me to put the code that I want. When I clicked u201CAnalysisu201D button in sales order, I got tax rel. classif. = SG. But I canu2019t set SG in VK11.
    In VK11, I can only put these codes:
    CP     Cofins Payment
    GP     General WHT payment
    IW     ISS WHT Invoice
    PP     PIS WHT Payment
    RP     IR WHT Payment
    SP     CSLL WHT payment
    What is it?
    Please kindly advise me how I can put u201CSGu201D in VK11. Thank you very much.
    Regards,
    Darin

    hi,
    what u can do is as the configuration i told was for direct taxes,bt ur issue is of withholding tax which is a indirect tax type.
    maintain  a condition type as normal sales tax with condition class as D
    and another condition as condition class w,
    now in the pricing procedure u can use from column to calculate the with holding tax,,
    i mean
    stepno     c.type     fr      to
    567         abcd      
    568         z123       567
    note:abcd is sales tax c.type with tax code(tax code appear in cond. record  because of c.class d)
            and z123 is your condition type(withholding tax) now the value can be generated .
    you can even use a relevant subtotal to calculate 568 value
    thanks
    revert if helpful
    mohit singh

  • Default profit centers Plant wise for Balance Sheet tax relevant Items.

    Dear All,
    We have an issue in profit center acccounting.
    In balance sheet accounts, Vat input tax payable, TDS payable, Cenvat clearing etc are picking profit center from 3KEH. When Exicse is getting captured cenvat clearing account having the profit center but while doing the MIRO cenvat clearing do not have profit center & plant.
    Why it is so?
    Basically we are doing the following steps.
    1. Purchase order creation ME21N.
    2.Goods received via migo
    3. invoice receipt via miro.
    At the time of miro posting, system creates automatically accounting document, with default profit center maintained in 3KEH, which are assigned to Vat input tax payable, TDS payable, other tax accounts. For GR/IR clearing account right profit center is picking without any mistake, while doing MIGO & MIRO.
    We need to extract the Balance Sheet profit center wise at plant level.
    Derivation rule is created for this balance sheet account along with Valuation area condition to post to correct profit center maintained under Tcode: 3KEI . But system is taking only default profit center (3KEH).
    I have checked configuration and the following areas like Material master costing view, tax code areas, and account group but did not find any mistake.
    Please advice and Guide us, how to get correct profit center at plant level for these balance sheet accounts instead of default. (I want to make default profit centers plant wise).
    It is urgent.
    Thanks,
    Shailendra Gupta.

    Hi!
    You can use following report :
    S_ALR_87013336 (Report for Balance sheet at Profit Center and Group Level).
    Hope this will help.
    Thanks & Regards,
    Taral Patel

  • Error account (GL a/c NO:)  has been set as not relevent for tax

    Hi,
    While posting MIRO  throughing error message " Error account (GL a/c NO:)  has been set as not relevent for tax "
    Kindly guide how to resolve the issue
    Thanks & Regards
    Lakshmi Kanth Reddy

    Hi Reddy,
    System throws up the message because the GL account you have entered has not made Tax relevant in the Control tab.  2 things I would like to point out -
    a)  Should you need the tax code for the particular GL account, then change the GL account master and make it relevant for tax.
    b)  If the tax code is not needed, then delete from the MIRO transaction and then post the document.
    Important point -  Mostly for all the MIRO transactions, tax code is made relevant for tax in the GL master.
    Hope this helps.
    Vikas.

  • How to find paricular GL ACCOUNT is relevant to tax or not.

    Hi ,
    Actually i am abaper working on FI MODULE.
    How to find paricular GL ACCOUNT is relevant to tax or not.
    Please provide the tcodes and necessary information..where to check .
    Thanks & Regards,
    Hari priya

    Hi Dianne,
    i checked in FS00 for my gl accounts.
    1. 60004100 : Tax category is Only input tax allowed
                          posting without tax allowed is ticked .
    The following message is displaying.. 
    G/L account 60004100 is relevant to tax; check code
    Message no. FS219
    Diagnosis
    You are posting to a tax-relevant account which does not, however,
    require the entry of a tax code.
    Procedure
    Check to see whether the transaction you are currently processing is
    actually not tax-relevant, and enter a valid tax code, if necessary.
    Effects on Customizing
    You can define when this system message is to be issued in accordance
    with your requirements.
    You do this in Customizing as follows: Cross-Application Components ->
    Bank Directory -> Change Message Control.
    The application area and message number can be taken from the technical
    documentation.
    please help me to solve this issue.
    thanks & regards,
    Hari priya

  • Withholding Tax all Condtion table not appearing in Rebate Credit memo

    Hi
    I am finding issue in rebate credit memo.
    Issue: In Acces sequence I have table 397 and extended 397 with additional fields.
    In normel credit memo I am able to find all these table in sales order Pricing Analysis tab.
    But in rebate credit memo, I am not able to find all table. Credit memo is showing 397 table but not showing ztable.
    Please check below screen shot for details
    1. 397 and 988 are identical and its appearing in rebate credit memo.
    I created 988 just to verify if any thing wrong in ztable generation or any thing missing to map.
    987 is extended table with addtional field sales doc. Type, Item category and its not appearing in Rebate credit memo.
    2. Rebate credit memo showing 988 and 397 table
    3. Normel credit memo showing all three table
    Question : How to get all three table in Rebate Credit memo?
    If 988 is appearing than why 987 is not populating.
    Both are Ztable and created together.
    I tried many combination but extended ztable not coming in rebate credit memo
    Regards
    Neeraj

    Hi JP,
    Thanks
    Routine 923 created as per SAP note 178824. And I am finding this issue only for rebate credit memo request.
    This condtion type (withholding tax ) is not part of rebate condtion. It is part of standard pricing procedure same like MWST.
    In Normel credit Memo (CR) all access assigned to this access sequnce is visible in sales order pricing analysis.
    But rebate credit memo request (B3) not showing all access (as in above screen shot). It shows only 2 access out of 3 access.
    One more addition
    If I am maintaining condtion record for visible access in rebate Credt memo request i.e. country / Tax relevant classifcation.
    SAP disble it in rebate credit memo request order.
    But normel Tax (MWST) is appearing in rebate credim memo request.
    I am not sure if this is due to standard sap.
    For Thailand we require withholding tax for Rebate credit memo.
    Please advice if any one can give some input on this.
    Regads
    Neeraj

  • Where to configure Tax categories for tax related Condition types

    Hi all,
    Could you pls let me know Where to configure Tax categories for tax relevant Condition types. (any tcode for this)
    When we are creating condition records for tax relevant condition types then you have to assign tax classification for customer and tax classification for material....i am providing 1 and 1 for customer and material as well.....then assigning tax code....when trying to save this doc.... system throwing this error....Tax indicator 1 is not defined for use with condition type O012. This means for 1 we can't find tax categories maintained.
    Please look into this and your help would be appreciable.....
    Thanks in advance....regards.....Diwakaran......

    Hi,
    1. First you need to create condition type eg : ZCST in V/06 by copying standard condition type for taxes MWST for output taxes.
    2. you need to assign this condition type to country eg:IN in OVK1 T-Code.
    3. Next you need to define Tax classification for customer eg : 1 in OVK3 T-Code and assign it to tax category (condition type : ZCST)
    4. Next you need to define Tax classification for material eg : 1 in OVK4 T-Code and assign it to tax category (condition type : ZCST)
    5. Maintain this tax classification in XD01 & MM01 T-Codes.
    Regards,
    Dippy

  • EFFECT OF TAX PROCEDURE

    HI
    First we configured CIN settings (TAXINN procedure) in our 650 client (DEV clinet) later we changed to TAXINJ in DEV itself and again we changed to TAXINN only. Now the tax codes are not working while doing the MM transaction is coming stating that Tax code is not assigned to TAXINN procedure. Now i want to know is there any effect by chaning the tax procedure like this manner will effect the tax codes or not? Please help me in solving this issue.

    hi sravani,
    the following are the SAP Tax Procedures to configure
    OBBG - Assign Country to calculation procedure.
    OBCO - Specify structure for Tax Jurisdiction code. For country like U.S.A.
    LG -> character length of first level of hierarchy within your tax jurisdiction code structure.
    LG -> Second level of hierarchy as above.
    LG -> Third level of hierarchy as above.
    LG -> Fourth level of hierarchy as above.
    TX -> Tick if you want the system to determine taxes on a line by line basis instead of determining them on a cumulative basis
               per tax jurisdiction code.
    OBCP - Define Tax Jurisdiction code
    Dil -> Tick if you do not want tax amounts included in the based amount used for calculating cash discounts.
    Txl -> Tick if you want the cash discount amount deducted from the base amount that is used to calculate taxes.
    FTXP - Define Taxes on Sales/Purchases Code.
    OBCL - Allow Tax codes for non-taxable transactions.
         External Tax Determination U.S.
    SAP AG
    Neurottstr. 16
    69190 Walldorf
    Germany     Configuration Guide
    Copyright
    © Copyright 2006 SAP AG. All rights reserved.
    No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
    Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
    Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
    IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.
    Oracle is a registered trademark of Oracle Corporation.
    UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
    Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
    HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
    Java is a registered trademark of Sun Microsystems, Inc.
    JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
    MaxDB is a trademark of MySQL AB, Sweden.
    SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
    These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
    Icons
    Icon     Meaning
         Caution
         Example
         Note
         Recommendation
         Syntax
    Typographic Conventions
    Type Style     Description
    Example text     Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
    Cross-references to other documentation.
    Example text     Emphasized words or phrases in body text, titles of graphics and tables.
    EXAMPLE TEXT     Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
    Example text     Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
    EXAMPLE TEXT     Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
    Example text     Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
         Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
    External Tax Determination
    1.1     Prerequisites
    Before using this configuration guide, you need to install the following building blocks in the order shown:
    Building Block     Description
    B32     Best Practices R/3 Installation
    V32     Best Practices Technical Objects (Manual DDIC, Tables, User Exit, Routine) + Install Transport
    J02     Organizational Structures
    V03     Financial Accounting
    V08     Basic Controlling
    V05     Delta Materials Management
    J04     Sales and Distribution
    V04     Delta Sales and Distribution
    1.2     Configuration
    1.2.1     Defining Physical Destination
    Use
    This activity defines an RFC destination.
    Procedure
    1.     Run the following activity:
    SAP R/3 Menu     Logistics  Central Functions   Supply Chain Planning Interface  Core Interface Advanced Planner  Settings   RFC Destination for Application
    Transaction Code     SM59
    2.     On the Display and Maintain RFC destinations screen, click TCP/IP connections.
    3.     Choose the Create button.
    4.     In the RFC Destination screen, enter the following:
    RFC destination     VERTEX_MAXTAX
    Connection type     T
    Description 1     Connection to Vertex
    5.     On the Technical settings tab, enter the following:
    Gateway host     Vertex server’s name
    Gateway service     Your gateway service for Vertex server
    6.     Choose the Save button.
    1.2.2     Define Logical System
    Use
    This activity defines the logical destination for external tax determination.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)   Financial Accounting Global Settings  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Define Logical Destination
    Transaction Code     SPRO
    2.     Enter the following values:
    N     Ex     Event for ext. taxation proc.     Function Module     RFC Destination
    1     V     JUR     RFC_DETERMINE_JURISDICTION     VERTEX_MAXTAX
    2     V     TAX     RFC_CALCULATE_TAXES1     VERTEX_MAXTAX
    3     V     UPD     RFC_CALCULATE_TAXES1     VERTEX_MAXTAX
    3.     Choose Save.
    1.2.3     Maintain Pricing Procedures
    Use
    This activity maintains pricing procedures.
    Procedure
    1.     Start the following activity:
    IMG Menu     Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define and Assign Pricing Procedures
    Transaction Code     SPRO
    2.     Enter the following values:
    Table VV_T683_VA
    N     Cl     U     App     Proc     LA     Destination     TSPP     PrTy
    1     030     A     V     ZVAXUD     EN     BU SMB with ext. Jurisd.NEW          
    2     030     A     V     ZCAX01     EN     Intercompany Billing US Ext.     X     
    3     030     A     V     ZDPJXD     EN     myPCC US DownPaym/Tax per doc.          
    4     030     A     V     ZSER02     EN     Service BP Exp Settlement Ext.          
    5     030     A     V     ZSPUS1     EN     SP:Resource Related Bill Ext.          
    6     030     A     V     ZSPUS2     EN     SP: Res Rel Bill Down Pay Ext.          
    7     030     A     V     ZSPUS3     EN     SP: Res Rel Bill CrossComp Ext          
    8     030     A     V     ZU0030     EN     Credit memo (US) Ext.          
    3.     Choose Save.
    1.2.4     Define Pricing Procedure Determination
    Use
    This activity defines pricing procedures.
    Procedure
    1.     Start the following activity:
    IMG Menu     Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define and Assign Pricing Procedures
    Transaction Code     OVKK
    2.     Enter the following values:
    Table V_T683V
    N     SOrg     DChl     Dv     DoPr     Cupp     PriPr     CTyp
    1     BP01     01     01     A     1     ZVAXUD     PR00
    2     BP01     02     01     A     1     ZVAXUD     PR00
    3     BP01     01     01     I     1     ZCAX01     
    4     BP01     01     01     V     1     ZSPUS1     RB00
    5     BP01     01     01     W     1     ZSER02     
    6     BP01     01     01     W     2     ZSER02     
    7     BP01     01     01     Z     1     ZU0030     
    8     BP01     02     01     Z     1     ZU0030     
    9     BP01     03     01     I     1     ZCAX01     
    10     BP01     03     01     I     1     ZCAX01     
    3.     Choose Save.
    1.2.5     Activate External Tax Interface
    Use
    This activity activates external tax interface.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Activate External Tax Calculation
    Transaction Code     SPRO
    2.     Enter the following values:
    Table V_TXD_E
    N     Reference     Ex     version of the tax interface     TC     RFC Destination
    1     TAXUSX     V     TAXDOC00          VERTEX_MAXTAX
    3.     Choose Save.
    1.2.6     Assign Country to Tax Calculation Procedure
    Use
    This activity assigns a country to tax calculation procedure.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings   Assign Country to  Calculation Procedure
    Transaction Code     SPRO
    2.     Enter the following values:
    Table V_005_E
    N     Cty     Proc     Name
    1     US     TAXUSX     
    4.     Choose Save.
    1.2.7     Allocate Company Code to Non-Taxable Transactions
    Use
    This activity allocates company code to non-taxable transactions.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)   Asset Accounting  Asset Accounting(Lean Implementation)  Organizational Structures  Assign Input Tax Indicator for Non-Taxable Acquisitions
    Transaction Code     OBCL
    2.     Enter the following values:
    Table V_001_J
    N     CoCd     Company Name     City     Input tax code     Output tax code     Jurisdict. code
    1     BP01     SAP Best Practices     Palo Alto     I0     O0     XX00000000
    3.     Choose Save.
    1.2.8     Create Number Range for External Tax Document
    Use
    This activity creates a number range for the external tax document.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Define Number Ranges for External Tax Returns
    Transaction Code     OBETX
    2.     Enter the following values:
    Table NRIV
    N     Object Name     Subobject value     Number range number     To year     From number     To number     Curr. Number     External
    1     ETXDC_NR          01     0000     000000000001     999999999999          
    3.     Choose Save.
    1.2.9     Activate External Updating
    Use
    This activity activates external updating.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Activate External Updating
    Transaction Code     SPRO
    2.     Enter the following values:
    Table V_TRWCA
    N     Comp     To year     Activ
    1     EXTX     2999     X
    3.     Choose Save.
    1.2.10     Creating Tax Codes for External Tax Calculation
    Use
    This activity creates tax codes for external tax calculation.
    Procedure
    1.     Start the following activity:
    Transaction Code     FTXP
    2.     The following five tax codes were created for the tax procedure TAXUSX and country US.
    Tax Code     Description     Condition types      Tax Type     Relevant to Tax     Tax  Category
    O0     A/R Sales Tax Exempt     Condition types XR1–XR6 are maintained with a 100% rate.      A
    (Output tax)     2     
    O1     A/R Sales Tax     Condition types XR1–XR6 are maintained with a 100% rate.     A
    (Output tax)     0     
    I0     A/P Tax Exempt     Condition types XP1I–XP6I are maintained with a 100% rate.      V
    (Input tax)     2     
    I1     A/P Sales Tax     Condition types XP1I–XP6I are maintained with a 100% rate.     V
    (Input tax)     0     
    U1     A/P Self Assessment Use Tax     Condition types XP1I–XP6I are maintained with a 100% rate. Negative 100% is entered for condition types XP1U–ZP6U to force the credit entry to the tax liability accounts.     V
    (Input tax)     0     1 (Consumer Use Tax)
    The values in the Relevant to Tax column can be interpreted as follows:
    •     Setting the Relevant to tax indicator to 2 will bypass the call to the external tax system, which saves processing time. If handling exemptions within Vertex or Taxware, then this indicator must be set to 0 or space, because the call must be made to Vertex or Taxware to access their exemption handling.
    •     Leaving the Relevant to tax indicator blank means that the tax code is relevant to tax and a call will be made to Vertex or Taxware to decide the tax rate.
    You can verify the settings using transaction FTXP.
    1.2.11     Change Jurisdiction Codes for SAP Best Practices Cost Centers
    This activity removes the standard jurisdiction codes from cost centers in order for Vertex to determine a valid jurisdiction code. The jurisdiction code found by Vertex is based on our default Palo Alto address.
    If you want to create different addresses for each cost center, choose Accounting  Controlling  Cost Centers  Master Data  Cost Center  Individual or Collective Processing.
    1.2.12     Change Jurisdiction Codes for SAP Best Practices Company Code and Plants
    This activity goes through the organizational elements of the SAP Best Practices — company code BP01 and plants BP01 and BP02 — and remove the standard-delivered jurisdiction code from the related addresses in order for Vertex to determine a valid jurisdiction code. The jurisdiction code found by Vertex is based on our default Palo Alto address.
    If you want to create a different address for each of the organizational elements, use transaction OBY6 to change the company code address, and transaction OX10 to change the plant addresses.
    dont forget to reward me points if it helps you
    regards
    karthik

  • Tax categoy in the Customer and material master

    Hi Friends,
    I have defined tax categories for Country "IN" as JTX1,JTX2 to capture VAT and CST and maintained one tax code for VAT and one for CST.
    Do i need to maintain the JTX1,JTX2 in the JINFAC pricing procedure to capture the VAT and CST or do i need to maintain separate condition types for VAT and CST.(Like ZVAT /ZCST).........if so how is JTX1 and JTX2 linked with VAT and CST condition types.
    Thanks
    Ivy

    Dear
    Wht Rajam told is right.
    I want to add sme points in the same.
    like when u put tax relevancy in cmr & mmr for ZCST & ZLST.
    then while maintaining access seq to ZCST & ZLST u have to take care to add the fields like cust tax 1, mat tax 1 from field catlog. even in std access seq there is table 40 i m not sure bt in that table u will get those fields to see. so when u will maintain the cond record u have to maintain those fields like cust tax 1 & mat tax 1.
    so plz take care while definig access seq. bcoz that is imp thing while taking tax relevancy in consideration while retriving condition record in sales doc.
    like when u maintain tax relevancy 1 in both cmr & mmr then only system will pick up full tax. bcoz while maintaing cond record u m ention like when u will get values like 1 in cmr & mmr u have to pivk up X percentage.
    hope this will help u.
    for any further assistance please feel free to ask.
    what region u are asking abt is from customer master.
    regards
    nitin
    Edited by: nitin chavan on May 27, 2008 2:21 PM

  • Asset US Taxes

    Hi ,
    Can any one provide me us tax configuration steps or any document related to asset for US. My email is [email protected]
    Thanks in advance

    Hello Aj,
    see the below configuration of US TAX ( Vertex)
    External Tax Determination
    1.1 Prerequisites
    Before using this configuration guide, you need to install the following building blocks in the order shown:
    Building Block Description
    B32 Best Practices R/3 Installation
    V32 Best Practices Technical Objects (Manual DDIC, Tables, User Exit, Routine) + Install Transport
    J02 Organizational Structures
    V03 Financial Accounting
    V08 Basic Controlling
    V05 Delta Materials Management
    J04 Sales and Distribution
    V04 Delta Sales and Distribution
    1.2 Configuration
    1.2.1 Defining Physical Destination
    Use
    This activity defines an RFC destination.
    Procedure
    1. Run the following activity:
    Supply Chain Planning Central Functions SAP R/3 Menu Logistics   RFC Destination for Settings  Core Interface Advanced Planner Interface  Application
    Transaction Code SM59
    2. On the Display and Maintain RFC destinations screen, click TCP/IP connections.
    3. Choose the Create button.
    4. In the RFC Destination screen, enter the following:
    RFC destination VERTEX_MAXTAX
    Connection type T
    Description 1 Connection to Vertex
    5. On the Technical settings tab, enter the following:
    Gateway host Vertex server’s name
    Gateway service Your gateway service for Vertex server
    6. Choose the Save button.
    1.2.2 Define Logical System
    Use
    This activity defines the logical destination for external tax determination.
    Procedure
    1. Start the following activity:
    IMG Menu  Tax on Financial Accounting Global Settings Financial Accounting (New)   Define Logical External Tax Calculation  Basic Settings Sales/Purchases  Destination
    Transaction Code SPRO
    2. Enter the following values:
    N Ex Event for ext. taxation proc. Function Module RFC Destination
    1 V JUR RFC_DETERMINE_JURISDICTION VERTEX_MAXTAX
    2 V TAX RFC_CALCULATE_TAXES1 VERTEX_MAXTAX
    3 V UPD RFC_CALCULATE_TAXES1 VERTEX_MAXTAX
    3. Choose Save.
    1.2.3 Maintain Pricing Procedures
    Use
    This activity maintains pricing procedures.
    Procedure
    1. Start the following activity:
    IMG Menu  Define Pricing Control  Pricing  Basic Functions Sales and Distribution  and Assign Pricing Procedures
    Transaction Code SPRO
    2. Enter the following values:
    Table VV_T683_VA
    N Cl U App Proc LA Destination TSPP PrTy
    1 030 A V ZVAXUD EN BU SMB with ext. Jurisd.NEW
    2 030 A V ZCAX01 EN Intercompany Billing US Ext. X
    3 030 A V ZDPJXD EN myPCC US DownPaym/Tax per doc.
    4 030 A V ZSER02 EN Service BP Exp Settlement Ext.
    5 030 A V ZSPUS1 EN SP:Resource Related Bill Ext.
    6 030 A V ZSPUS2 EN SP: Res Rel Bill Down Pay Ext.
    7 030 A V ZSPUS3 EN SP: Res Rel Bill CrossComp Ext
    8 030 A V ZU0030 EN Credit memo (US) Ext.
    3. Choose Save.
    1.2.4 Define Pricing Procedure Determination
    Use
    This activity defines pricing procedures.
    Procedure
    1. Start the following activity:
    IMG Menu Sales  Define and Pricing Control  Pricing  Basic Functions and Distribution  Assign Pricing Procedures
    Transaction Code OVKK
    2. Enter the following values:
    Table V_T683V
    N SOrg DChl Dv DoPr Cupp PriPr CTyp
    1 BP01 01 01 A 1 ZVAXUD PR00
    2 BP01 02 01 A 1 ZVAXUD PR00
    3 BP01 01 01 I 1 ZCAX01
    4 BP01 01 01 V 1 ZSPUS1 RB00
    5 BP01 01 01 W 1 ZSER02
    6 BP01 01 01 W 2 ZSER02
    7 BP01 01 01 Z 1 ZU0030
    8 BP01 02 01 Z 1 ZU0030
    9 BP01 03 01 I 1 ZCAX01
    10 BP01 03 01 I 1 ZCAX01
    3. Choose Save.
    1.2.5 Activate External Tax Interface
    Use
    This activity activates external tax interface.
    Procedure
    1. Start the following activity:
    IMG Menu  Tax on Financial Accounting Basic Settings (New) Financial Accounting (New)   Activate External External Tax Calculation  Basic Settings Sales/Purchases  Tax Calculation
    Transaction Code SPRO
    2. Enter the following values:
    Table V_TXD_E
    N Reference Ex version of the tax interface TC RFC Destination
    1 TAXUSX V TAXDOC00 VERTEX_MAXTAX
    3. Choose Save.
    1.2.6 Assign Country to Tax Calculation Procedure
    Use
    This activity assigns a country to tax calculation procedure.
    Procedure
    1. Start the following activity:
    Financial Accounting BasicIMG Menu Financial Accounting (New)   Assign Country to Basic Settings  Tax on Sales/Purchases Settings (New)  Calculation Procedure
    Transaction Code SPRO
    2. Enter the following values:
    Table V_005_E
    N Cty Proc Name
    1 US TAXUSX
    4. Choose Save.
    1.2.7 Allocate Company Code to Non-Taxable Transactions
    Use
    This activity allocates company code to non-taxable transactions.
    Procedure
    1. Start the following activity:
    IMG Menu Financia Asset Accounting(Lean Asset Accounting l Accounting (New)   Assign Input Tax Indicator for Organizational Structures Implementation)  Non-Taxable Acquisitions
    Transaction Code OBCL
    2. Enter the following values:
    Table V_001_J
    N CoCd Company Name City Input tax code Output tax code Jurisdict. code
    1 BP01 SAP Best Practices Palo Alto I0 O0 XX00000000
    3. Choose Save.
    1.2.8 Create Number Range for External Tax Document
    Use
    This activity creates a number range for the external tax document.
    Procedure
    1. Start the following activity:
    IMG Menu Financial  Tax on Financial Accounting Basic Settings (New) Accounting (New)   Define Number External Tax Calculation  Basic Settings Sales/Purchases  Ranges for External Tax Returns
    Transaction Code OBETX
    2. Enter the following values:
    Table NRIV
    N Object Name Subobject value Number range number To year From number To number Curr. Number External
    1 ETXDC_NR 01 0000 000000000001 999999999999
    3. Choose Save.
    1.2.9 Activate External Updating
    Use
    This activity activates external updating.
    Procedure
    1. Start the following activity:
    IMG Menu Financial  Tax on Financial Accounting Basic Settings (New) Accounting (New)   Activate External External Tax Calculation  Basic Settings Sales/Purchases  Updating
    Transaction Code SPRO
    2. Enter the following values:
    Table V_TRWCA
    N Comp To year Activ
    1 EXTX 2999 X
    3. Choose Save.
    1.2.10 Creating Tax Codes for External Tax Calculation
    Use
    This activity creates tax codes for external tax calculation.
    Procedure
    1. Start the following activity:
    Transaction Code FTXP
    2. The following five tax codes were created for the tax procedure TAXUSX and country US.
    Tax Code Description Condition types Tax Type Relevant to Tax Tax Category
    O0 A/R Sales Tax Exempt Condition types XR1–XR6 are maintained with a 100% rate. A
    (Output tax) 2
    O1 A/R Sales Tax Condition types XR1–XR6 are maintained with a 100% rate. A
    (Output tax) 0
    I0 A/P Tax Exempt Condition types XP1I–XP6I are maintained with a 100% rate. V
    (Input tax) 2
    I1 A/P Sales Tax Condition types XP1I–XP6I are maintained with a 100% rate. V
    (Input tax) 0
    U1 A/P Self Assessment Use Tax Condition types XP1I–XP6I are maintained with a 100% rate. Negative 100% is entered for condition types XP1U–ZP6U to force the credit entry to the tax liability accounts. V
    (Input tax) 0 1 (Consumer Use Tax)
    The values in the Relevant to Tax column can be interpreted as follows:
    • Setting the Relevant to tax indicator to 2 will bypass the call to the external tax system, which saves processing time. If handling exemptions within Vertex or Taxware, then this indicator must be set to 0 or space, because the call must be made to Vertex or Taxware to access their exemption handling.
    • Leaving the Relevant to tax indicator blank means that the tax code is relevant to tax and a call will be made to Vertex or Taxware to decide the tax rate.
    You can verify the settings using transaction FTXP.
    1.2.11 Change Jurisdiction Codes for SAP Best Practices Cost Centers
    This activity removes the standard jurisdiction codes from cost centers in order for Vertex to determine a valid jurisdiction code. The jurisdiction code found by Vertex is based on our default Palo Alto address.
    If you want to create different addresses for each cost center,  Cost Center  Master Data  Cost Centers  Controlling choose Accounting  Individual or Collective Processing.
    1.2.12 Change Jurisdiction Codes for SAP Best Practices Company Code and Plants
    This activity goes through the organizational elements of the SAP Best Practices — company code BP01 and plants BP01 and BP02 — and remove the standard-delivered jurisdiction code from the related addresses in order for Vertex to determine a valid jurisdiction code. The jurisdiction code found by Vertex is based on our default Palo Alto address.
    If you want to create a different address for each of the organizational elements, use transaction OBY6 to change the company code address, and transaction OX10 to change the plant addresses.
    Hope this will help you.
    Regards,
    shashikanth
    Assign points if usefull

Maybe you are looking for