Input tax - from 4.6 to ECC 6.0 calculates differently

Hello all, little issue here. Now i don't know if now it is working as designed and 4.6 was incorrect or if ECC6 is incorrect. We just upgraded from $.6C to ECC 6.
In 4.6 Acct would post an accrual for use tax and it would post fine with out posting use tax automatically., they would just post it to a manual use tax account. They would post Db to Expense, Cr to Sales use Tax Manual - both would have U1 tax code - Self Assessed tax. Exp line had differnt Tax Jurisd. Code then the Sales Use Tax manual account had, but still in the same state. When i look at the Tax data, i would have base amounts, i would have Percentages, but i would not have any tax amount values, so there would be no additional postings to the entry, which is what they wanted and have been getting.
Now in ECC6 - same scenario, but however what the system is now doing is, it is increasing the expense line, along with the manual Sales and Use tax account, then there would be the Auto posting to the Sales and use tax account in OB40. So now our accounts are overstated. The only way to get ECC6 to react the same,is to make sure the two jurisdiction codes are the same, and it won't calculate additional lines.
Now i would think ECC 6 is working as designed, but if the amounts posting to the Auto post Sales and Use tax accounts are a wash, why is it posting and why does it increase the amount of the Expense account and B/S account first? i need help in figuring if our 4.6 system was incorrect or correct, and if correct, how do i fix ECC6?
PS- We are using Vertex.
Thanks
Sean Dwyer

One other thing that might be of interest. When io click on the button for tax data, in 4.6, you would see a debit for one jurisdiction code(Federal), and a credit for the same code, then you would see a debit for the next code (State) and a credit for the same code, and so on for all the different areas. But in ECC6, i see a debit for all codes (Fed, state, locl..) then i see the group of Credits for all codes. now i am not sure if that has anything to do with the issue, but i am just grasping at straws.
Thanks,
Sean

Similar Messages

When creating a travel expense, an incorrect input tax code is defaulted

Dear experts,
I'm new with SAP customizing in Travel Management. I have an issue that I cannot solve and I've tried almost all possibilities.When an employee tries to create a travel expense in PR05, him being from Belgium, the default input tax code for any expense type is, for example V3. This code exists in FI and will be transferred correct into accounting. But, if the employee wants to change the the country key in the field Country of Receipt (found in additional info section), anything other than the domestic country (BE) will automatically change the input tax from V3 to V0, which we don't even have in FI.
I tried the following:
- checked under global settings and for Belgian trip provision variant there was always Input Tax per Travel Expense Type flagged and V3 with cocd BE;
- checked each and every expense type for the default input tax and all have V3.
I had to create a country grouping EU for all European Countries. All maximum rates for different expense types have been defined using this EU code. Might it be this grouping?
Any new expense type, similar to any of the ones I have problems with, will keep the default V3 tax code no matter if I change the country of receipt.
Thank you in advance guys,

No need anymore for an answer, I found out what I was looking for under Define Country-Dependent Default Values for Expense Types

Asset acqisition input tax ECC

I'm using an special input tax condition. It is an Asset acqisition input tax ECC.
I need that the system does an special post, I need post in the debit and in the credit.
Anybody know how I can try it?
Thank you very much

query solved.

Vendor down payment with input tax

Dear Expert
My client receieves down payment with input tax, to meet their legal requirement for VAT filing, they have to book entries as below;
When receieving down payment with input tax:
Dr. Down payment
Input tax
Cr. Bank
When receiveing vendor invoice for remaining AP amount:
Dr. Expense
Input tax
Cr. AP (remaining amount)
Then clear down payment by expense
Dr. Expense
Cr. Down payment
They do in this way, because input tax in down payment and input tax in remaining AP invoice should be listed as two items in their VAT report. And intput tax in down payment document is with reference field which is different from reference field in remaining AP invoice, and reference field is also one mandatory field in VAT report.
In this case, I can not use SAP standard T-code F-54 to clear down payment. But when I tried to create a manual JV to post entry with Dr. Expense and Cr. Down payment, it's OK, but then when I used F-44 to manully clear down payment doc by manual JV, I got problem because the amount in down payment is down payment amount + input tax amount, but the amount in manual JV is only down payment.
Does someone have a solution?
Thanks,
Nicole

Nicole,
Which country is this requirement for? As far as I know, there is no tax incidence on downpayment. Input tax arises only when you receive the invoice, right? Not when you receive a downpayment.

Self billing invoice with input tax code

Hello experts,
we are currently trying to implement a billing procedure with credit memos within the module SD. In this set-up the recipient of a service (company using the SAP) creates a credit memo for the renderer of a service (a debitor in SAP) showing the amount the recipient of the service/product has to pay. The credit memo will also show VAT (we currently only try to implement a process for transaction within Germany, no cross-border transactions yet). For the recipient of the service (= issuer of the credit memo) the credit memo is similar to an incoming invoice (self billing invoice). Hence, the shown VAT on this credit memo - if all other requirements are met - can be treated as deductible input tax.
In order to automatically process the credit memo correctly as incoming invoice it has to be linked to a tax code (Steuerkennzeichen) with tax type "V" (=input tax) (Vorsteuerkennzeichen). To achieve that we have created a new condition record (Konditionssatz) that performs that task.
So currently we create a credit memo request (Gutschriftsanforderung) which is linked to an input tax code (Vorsteuerkennzeichen) via mentioned condition record. We then create the billing document. During creating the billing document an accounting document should also be created. But that is where our approach does not work properly. The system creates a billing document (credit memo) but does not create the corresponding accounting document. We receive the error message:
Document .... saved (no accounting document generated)
Message no. VF050
When trying to release the document to FI via Transaction VF02 we receive the following, more detailed error message:
Only output tax is allowed for account 480000 1000, VZ is not allowed
Message no. FS215
This problem has to be somehow linked to the usage of an input tax code. If we perform the same procedure with an output tax code (Ausgangsteuerkennzeichen) we will not receive the error message and an accounting document is created.
It seems that the account determination is responsible for the described problem: Although an input tax code is assigned, the account key (as shown in the overview to the applied conditions on the items within the credit memo request (Item - Condition - Detail)) does not change from "MWS" to "VST" and therefore an output tax account (Account Number 480000) is determined for the tax amount. And for that output tax account the usage of an input tax code is not allowed.
Has anyone an idea how to solve the described problem or how to implement the billing procedure another way?
We are aware that there is such a functionality within the module MM called "Evaluated Receipt Settlement (ERS)" but this is not suitable for our purposes since we want to implement this within SD and without the need to create an order first which seems to be necessary for ERS.
Thanks for your help,
Bernd

Hi
Please check in FS00, of that G/L account in control data tab what is the Tax Category that has been maintained.Check wheather input tax/output tax has been maintaind or not
In FS00 in the control tab check the box Posting without tax allowed
Regards
Srinath
Edited by: sri nath on Sep 30, 2011 4:55 PM

Runtime Error in MIGO after upgrade from 4.6c to ECC 6.0

hi,
    We are doing a upgrade project from 4.6c to ECC 6.0 and when we are posting the MIGO a runtime error is occuring from the method
"IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE" which is
in the class "ZCL_IM_MMIM_STK_TRANSFER".
The error is as follows :
method IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE
>>>>>CALL FUNCTION 'Z_MM_STK_TSFR'
TABLES
T_XMKPF = XMKPF
T_XMSEG = XMSEG.
END METHOD.
the errror is showing at function 'Z_MM_STK_TSFR'   .
I would be happy if anyone could give any inputs i hav also put chek in unicode in attributes in main program however still the error is arising.
thanks in advance

hi,
     thanks for the inputs i have done the syntax check on the main program and the FM the error which is coming is Field "ENJPREVIEW" is unknown. its neither in one of the specified tables nor defined by a DATA 'statement' . THis error is showing in the include LMEDRUCKF1K.
Thanks in advance

Technical upgrade from 4.7 to ECC 6.0

Experts,
1.We need to make Technical upgrade in HR from 4.7 to ECC 6.0 with OM,PA, -ve Time,Payroll, Recruitment (other Modules also upgraded).Kindly let us know what will haeepen for the following .
A.Configrations in SPRO
B.Previous database (Cluster table for previous Time and payroll run)
C.Master data of employees which is stored in Infotypes
2.Also Kindly let us know is there anything we need to take care after moving from 4.7 to 6.0

Hi Kumar,
Basically there needs to be a Transport established between 4.7 and ECC6.00 Version . You can create Transport request for those tables whose value remain same in 4.7 nad ECC6.00 But for tables having changes you need to create the Configuration.
1 more method applied by organization is a client copy of tables.
My suggestion would be like this :
1. Compare and Update Tables (from Configuration Handbook)
Pay Frequency
Define Period Modifiers
V_T549R
Define Date Modifiers
V_T549L
Check Payroll Accounting Area
V_T549A
Pay Scale Structure
Define EE Subgroup Grouping for PCR and Collective Agreement Provision (CAP)
V_503_B
Check Pay Scale Type
V_T510A
Check Pay Scale Area
V_T510G
Check Assignment of Payscale Structure to Enterprise Structure
V_001P_C
Define Default for Pay Scale Data
Feature - TARIF
Setup payroll period for Collective Agreement Provision
V_T510W
Revise Pay Scale Groups and Levels
V_T510
Enterprise Structure for Wage Type Model
T539A
Feature - LGMST
Revise Default Wage Types
V_T539A - already tested
Define Valuation of Base Wage Types
V_T539J
Legacy Data Transfer
T558B
T558D
Define Periods for import
T558B - already tested
Rates of Pay
T512W
Pay Scale Allowance Group
V_T7INA1
Assign Pay Scale Groupings for Allowances
V_T7INA3
Define Basic Codes
V_T7INB4
Statutory
Define Trust Details for Provident Fund
V_T7INF1
Assign Company Rates for Provident Fund
V_T7INF5
Define PF Trust Validity Period
V_T7INF7
Maintain Contribution Details for Provident Fund
Feature: 40EPF
V_T7INF3
Define Contribution Type for Statutory rates for Provident Fund
V_T7INF3 - already tested
Employees' State Insurance
V_511P_B
V_T511P
Maintain Number of Working Days in a Month
V_511K_B
V_T511K
Define Personnel Area and Subarea Groupings for ESI
V_T7INE1
Assign ESI Groupings for Personnel Area and Subarea
V_7IN0P_ESI
Maintain Contribution Rates for ESI
V_T7INE3
Assign Universal Contribution Groupings for Universal Contribution Type
V_T7INOP_ALL
Assign slab code for Universal Contribution Grouping
V_T7INU1
Assign Slab code and other parameters for each state of a universal type
V_T7INU3
Assign contribution Value for each slab
V_T7INU5
Maintain Eligibility Details for Superannuation
Feature - 40SAN
Tax and Professional Tax
Define Professional Tax Grouping Details
V_T7INP1
Maintain Method and Form Layout for Ptax Groupings
T596F
Maintain Re-Computation Behaviour of Tax related
Feature - 40MWT
Maintain Schema for Exemption on Medical Reimbursement / Insurance
V_T7INT9
Maintain Schema for Exemption of Child education and hostel allowance
V_T511K - already tested
V_T7INT9 - already tested
Bonus Act
T511K - already tested
T511P - already tested
One Time Bonus Tax
Copy Wage Types
V_T7INT9 - already tested
V_T7INA9
Define Compensation Area Feature
Feature - CAREA
Assign organizational assignment to Compensation Groups
Feature - CMGRP
Maintain Variant for Payroll Simulation
Feature - 16CVA
Maintain Payslip Variant
Feature - 16EVA
HRA/CLA/LTA
Define Accomodation Types
V_T7INT7
Company Loans
Maintain Loans Grouping
Feature - 40LGR
Mantain Loans Eligibility Checks and Limits
Feature - 40 LGR - already tested
Banking
Setup House Banks
V_T012
Bank Account
V_T012K
Define Sending Banks
Feature - DTAKT
Check Text Keys for Payment Transactions
V_T520S
General Ledger
Define Employee Grouping Account Determination
Feature - PPMOD
Define Symbolic Accounts
V_T52EK
V_T52EZ
2. Compare and Update Genaral Tables
1     T512W
2     T511K
3     T511P
4     TCURR
5     T030
2a. Compare and Update Additioanl PY-IN Tables
1     T7INTN TAN Number Maintainence
2     T7INA1 Pay scale grouping for allowances
3     T7INA3 Associating pay parameters to pay scale grouping
4     T7INA5 Wage type model for pay scale grouping for allowances
5     T7INA7 Reimbursements Allowances and Perks - base slabs
6     T7INA9 Reimbursement allowances perks - eligibility and calculation
7     T7INAA Salary year for pay scale grouping for allowances
8     T7INB1 Basic Wages
9     T7INB4 Basic Codes
10     T7INB5 Basic Codes for Allowance Groups
11     T7INB7 Basic slabs
12     T7INB8 Appraisal Criteria
13     T7INB9 Increment criteria
14     T7INC1 Car types master
15     T7INC3 Type and age eligibility for car schemes(COCS/OYCS)
16     T7INC5 Perk valuation for cars
17     T7INC7 Amount and number eligibility for car schemes(COCS/OYCS)
18     T7INC9 Conveyance allowance eligibilty
19     T7INCA Codes for Conveyance types
20     T7IND1 Dearness allowance consumer price index master
21     T7IND3 Dearness allowance consumer price index value
22     T7IND5 Dearness allowance basic slab details
23     T7IND7 Dearness allowance calculation rules
24     T7IND9 Dearness allowance consumer price index slabs
25     T7INE1 Personnel area / subarea grouping for employees' state ins.
26     T7INE3 Employees' state insurance contribution rates
27     T7INF1 Trust Master
28     T7INF3 Statutory rates for Provident fund
29     T7INF5 Company rates for Provident Fund
30     T7INF7 Trust details
31     T7ING1 Gratuity Details Maintenance
32     T7ING3 Gratuity ID Maintenance
33     T7ING5 Gratuity ID and Related Wage Types
34     T7INI0 Investment category limits
35     T7INI2 Investment technical description and text
36     T7INI4 Investment details
37     T7INI5 Sub section description
38     T7INI7 Sub section limit
39     T7INI8 Sub division description
40     T7INI9 Sub division details
41     T7INIA Deduction wage type for Sec 88
42     T7INIC Deduction wage type for Sec 80
43     T7INJ1 Section 24 Deduction Details Maintenance
44     T7INJ3 HR-IN: Loans Eligibility checks and limits
45     T7INJ5 HR-IN: Loans Dusbursement Schedule
46     T7INJ6 HR-IN : Loan Tranche Disbursement: Text for Events Code
47     T7INL1 Leave validation for LTA
48     T7INO1 One day salary deduction
49     T7INP1 Professional tax grouping details
50     T7INP3 Method and form layout for states
51     T7INP4 Professional tax slab amounts
52     T7INR1 Housing code for taxation
53     T7INR3 Percentage/amount for housing related constant
54     T7INR5 Housing related statutory constants for taxation
55     T7INR7 Codes for Housing Types
56     T7INR9 City category for housing type
57     T7INS1 Superannuation Details Maintenance
58     T7INS3 Superannuation ID
59     T7INS5 Superannuation-Wagetype Details
60     T7INT1 Slab codes for taxation
61     T7INT3 Taxation slabs
62     T7INT5 Personnel subarea grouping for Tax
63     T7INT7 Tax codes for tax exemptions
64     T7INT9 Taxability of wage types
65     T7INU1 State for Universal Grouping
66     T7INU3 Slab Codes for States
67     T7INU5 Contribution Value for Each Slab
68     T7INW1 Personnel area/subarea grouping for LWF
69     T7INW3 Labour welfare fund rates
70     T7INY1 Recovery of rounding off amounts
71     T7INZ1 Factor for retiral benefits
72     T7INZ3 Period of notice codes
3. Compare Payroll Schemas
1     Compare ECC5- to ECC6 standard schemas
2     Compare ECC5- to ECC6 customised schemas
4. Compare Personnel Calculation Rules (PCR)
1     Compare ECC5- to ECC6 standard PCR's
2     Compare ECC5- to ECC6 customised PCR's
B. Payroll Process
1     Generic Payroll Process
1.1     Simulate Payroll
1.2     Release Payroll
1.3     Start Payroll
1.4     Check result
1.5     Corrections
1.6     Remuneration statement
1.7     Simulate and test FI/CO postings
1.8     Simulate and Test Preliminary DME
1.9     Run Preliminary DME Program
2     Create a live posting run and create FI documents
C. Regression Testing (Variance Monitor)
1     Compare Payroll Results
Create a Excel with these contents and fill them up by saying the percentage of similarity and completetion.
Please let me know if this is usefull
Regards,
Prabha

Expense Types with Input Tax (GST) - mapping to GL Account for reporting

We are in the process of implementing Expenses for countries like Australia & New Zealand, which have GST.
Expense Types were created and different Tax Codes were defaulted to the expense types, as per the requirement. Some Expense Types have no GST while some do have a Tax Code to 10% Input Tax
The issue is, I cannot find a config step to map the Expense Types to Tax GL accounts so that the Finance office in Australia / New Zealand can submit their claims end of the year by pulling up a report from this GL. I can do the regular mapping of Expense Types to specific GLs. I can even settle & post the expenses to FI and reimburse the employees but there is no way I can record the receipts which have taxes on them into the tax GLs for reporting purposes.
Any inputs on how this can be mapped or addressed is much appreciated. We went live with a bunch of countries but, the GST quotient is holding us off from going ahead with AU and NZ.
Here's an example - Expense Type is Dinner. This is mapped to GL 123456. When an employee submits an Expense with the Dinner, it is settled and posted to FI against the GL 123456. The reimbursement is done. But, the Dinner expense receipt has 10% GST which the Finance team wants to submit and claim the tax breaks end of the year. We want all the expenses with 10% tax be mapped to GL 800900. But this is only for reporting reasons. No postings done against the GL 800900.
So, we are looking to map all the Expense Types with Input Tax 10% to GL 800900 and all Expense Types with Input Tax 15% to GL 700600
Here's some of the Tax Config that was done ...
1). SPRO -> Financial Accounting -> Travel Management -> Travel Expenses -> Master Data -> Control Parameters for Travel Expenses -> Define Global Settings ... Input Tax is set to "Input Tax per Travel Expense Type"
2). SPRO -> Financial Accounting -> Travel Management -> Travel Expenses -> Master Data -> Control Parameters for Travel Expenses -> Travel Expense Types -> Create Travel Expense Types for Individual Receipts ... in the Expense Type, "Tax Code" field is set the either 0% or 10% Tax Codes

Issue is resolved ... I misunderstood the logic. Tax Code is linked to a GL account. And when I run PRRW, I see the relevant Tax amount in against the trip

Travel management: Input tax for each travel expense

Dear forumers,
I've got the following problem with input tax.
I activated input tax for my country variant in Customizing IMG Global settings for each trip provision variant, second option "Input tax per trip expense type".
I also put the tax code to each travel expense which should be taxed.
But still amounts are not posted in FI with input tax codes.
When I tested the situation in Testing system, everything worked fine. Then I did the same customizing in Development in order to transfer to Production system and copied requests to Testing. And from that moment, amounts are posted to FI without taxation even in Testing system. Don't know, what went wrong 'cause everywhere I did the same manipulations.
Can anyone help me to solve the problem?
Best regards,
Eldar.

Hi
what is the rule in schema?
i had similiar problem, i.e. the tax code is not updated in the FI document.
can you advice what might go wrong?
thanks in advance!

Input Tax configuration (FTXP)

Dear Experts,
I have a US client having SAP 4.7 . Currently they are using Vertex for Tax calculation, but need to change to TAXUS or TAXUSJ. I need to know how can I configure an Input Tax code to Accrue the tax. The entry should be as follows;
Scenario : Suppose Vendor Invoice is $ 1000, State tax is 4 % and City tax is 4.5%( both these taxes are arrued)
Dr   Exp                   1085       (posting key    40)
Cr   Vendor             1000-     (posting key   31)
Cr   State Tax             40-      (posting key   50)
Cr   City Tax                45-      (posting key   50)
Can you please let me know how can I configure to get this? Really appreciate your help.
Thanks, Reji Cherian
Edited by: Reji PC on Oct 21, 2011 8:16 AM

Hi,
Our FTXP screen is the replica of Tax Procedure which has been activated at your end. If the condition types have been added in the Taxing Procedure then only those will get reflected automatically in FTXP.
First confirm the Tax code requirement clearly since you will have to maintain the percentage (%) against the displaying Tax condition types.
Account key, condition type, Level to and from Lvl as I said, are the reflectiions of Taxing procedure in FTXP.
You have maintained the period of condition types for which those are valid.
Regards,
Shridhar

Incorrect field KNA1-STCEG in output list for input tax Line items-RFUMSV00

Hi all,
I found the incorrect field in RFUMSV00 - Advance Return for Tax on Sales/Purchases. If you want to configure the output list for Input tax: Line items, there is the field VAT Registration No. which has to be LFA1-STCEG, but there is incorrect field KNA1-STCEG. After that I cannot find the values for this field in my output.
In the output list for Output tax: Line items there is correct field in configuration /LFA1-STCEG/.
I tried to find some SAP notes but without avail.
Thanks for help.
Miroslav

Hi,
Please check the following OSS note:-
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=736203
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=640269
It is picked up from bseg-stceg and not from lfa1-stceg or kna1-stceg
Regards,
Gaurav

Table Enhancement Category during upgrade from 4.7 to ECC 6.0

When our sandbox was upgraded from 4.7 to ECC 6.0, Basis had the ABAP developers change the Enhancement Category on about 400 tables, some of which were custom tables. The enhancement category was previously u2018not classifiedu2019 on these tables.
Is this really necessary? Has anyone not changed the enhancement categories on tables that were flagged during the upgrade? Also, what happens if we select the wrong enhancement category?

Jane,
This is what SAP says,
Short Text
Enhancement Category Selection
Definition
Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
Cannot be enhanced
The structure must not be enhanced.
Can be enhanced or character type
All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
Can be enhanced or character-type or numeric
The structure and its enhancement must not contain any deep data types (tables, references, strings).
Can be enhanced in any way
The structure and its enhancement may contain components whose data type can be of any type.
Not classified
This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

Business area as a req..field for vat input tax g/l

in fs00 . we set the additional account assignment for field like suppress req. entry,opt. entry..i want to know for which general ledger it will be required...?
actually in our system for (vat input tax ) gl business area it is not mandatory field ...or when i check the line items for this general ledger business area wise ...it displaying for all business area...
so tell me if i set it as req. field,then will it be right or not?
Thanks & Regards
Rekha Sharma

Hi,
To my understanding taxes are always posted without a business area. System makes transfer postings from tax account to business areas for the income and expense account. A balance sheet adjustment is carried out according to business area if 'Business Area Balance sheets' has been activated in company code global parameters(OBY6).
When you post a document the system determines this document and notes for the adjustment. Documents noted during posting are calculated for the adjustment. The system calculates the adjustment according to the account assignments. Execute F.5D(programSAPF180A) reads the marked documents, calculates the necessary adjustment postings, and updates these in its own database tables. After that execute F.5E(program SAP F180) reads the adjustment posting tables and on this basis posts the accounting documents required.
For example you posted on customer invoice:
Customer A/c Dr 1150(Accts Receivables)
Revenue A/c1 Cr         600 (BA-1)
Revenue A/c2 Cr         400 (BA-2)
Tax A/c Cr                   150
During the Balance Sheet Adjustment the system divides this tax entry by business area wise
Tax A/c 90(BA-1)
Tax A/c 60(BA-2)
You cannot run balance sheet adjustment without activating the 'Business Area Balance Sheets' at company code global parameters.
Hope it will clear your query.
Regards,
Krishna Kishore

Copying variants & Layouts from 4.7 to ECC 6.0

Hi All,
Upgrading Client system from 4.7 to ECC 6.0. The 4.7 server would have its own variants and layout for different objects.
How do I copy those variants and layouts to my ECC 6.0 server?
Thanks for your valuable inputs.
Rajesh

Hello prashant,
SPDA_GET_STACK_INFO will check wether all PATCH prerequisites are met or not your ST related level is not up to the required level.
Please check this requirement up the level of STand run it agin.
Thank you,
Shyam

Documents related to upgrade from 4.6C TO ECC 6.0

Hi all,
can anyone send some documents related to upgrade from 4.6C TO ECC 6.0
my emil id is
[email protected]
THANKS
VENKI

Hi Venki,
Please check for the following links for the information on Upgradation from 4.6C to ECC6.0
Upgrade Procedure/Support Packages:
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
SAP Upgrade guide:
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
Upgrade information centre:
Upgrade Information Center [original link is broken]
For Functionality Differences pls refer to the below site - http://solutionbrowser.erp.sap.fmpmedia.com/
From ABAP's perspective, the link below helps you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
For technical upgrade inputs, check:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
I am sending you a mail too.Please check it.
Reward if found useful.
Regards
Sayee

Input tax - from 4.6 to ECC 6.0 calculates differently

Similar Messages

Maybe you are looking for