OSS for TAXINN and CIN in ECC6

Hi ..
Can you pls advice the OSS notes that i have to apply,to get all my condition types in TAXINN procedures.
In addition to this what are the OSS notes that i have to apply for CIN in various areas.
looking forward of earliest responses.
Thanks
R.Kannan.

TAXINN is avialble from ECC 5.0 onwards. It is standard tax procedure by SAP. So no need to go for any OSS Note. TAXINN has to be copied from '000' client to our cleint.TAXINJ was in use upto 4.7 Verson
Also check :
http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/taxinnjex1jhx1cond-record-1568253
Edited by: m_n_novice on Aug 17, 2009 4:00 PM

Similar Messages

Is Oracle 11g released for NW04s and ECC6.0?

Is Oracle 11g released for NW04s and ECC6.0?
Please help. Thanks!

Plain and simple: No, it isn't.
Check the SAP on Oracle homepage [here|SAP on Oracle] in SDN and read the latest development news on this topic including a rough schedule.
regards,
Lars

CIN - TAXINN and TAXINJ

Why should we go for TAXINN, what are the advantagous of TAXINN over TAXINN
Thanks in Advance

Hi,
TAXINJ is Routine based based PRICING PROCEDURE and we have to define the Routine/Requirement for our requirement and assign to each condition type in that pricing procedure
Here we have to define Routines with the Help of ABAPers. Till 4.7 version this pricing procedure is used
From 4.7 Onwards, SAP came with TAXINN pricing procedure which is condition records based pricing procedure for whcih we can just maintain the condition records which are very flexible.
Here we can have condition records based on the access sequence which are flexible and can be used in different scenarios.
This is the Main Advantage of TAXINN over TAXINJ.
Hope you got it.
regards,
santosh

Pricing procedure and CIN master

Hi MM Gurus,
I need one simple procedure for creating Pricing Procedure.........and ......creating Excise details and relating and can anybody show how the pricing procedure and excise (CIN) is related .
Regards,
Girish.C.M

Hi,
CIN Setting:
Check Calculation Procedure
In this activity, you can check and, if necessary, change existing procedures for tax calculation.
Standard settings
Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it.
The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
Note
In this activity, the condition types for the check and the possible change provided in the standard system are also displayed. Here, for example, the condition calculation rule, or for which base amount the tax is calculated is determined (= condition type).
Recommendation
If possible, do not change the condition types and calculation procedures provided in the standard system. Only check the standard condition types and calculation procedures regarding whether you can use them for your requirements. If necessary, make changes.
Activities
If you cannot use the standard settings, change the condition types and calculation procedures delivered to meet your requirements.
Procedure (pricing, output control, acct. det., costing,...)
Specifies the conditions that are allowed for a document and defines the sequence in which they are used.
Example
Procedures are used, for example, in the following applications:
· Pricing in sales and distribution
· Applying overhead in Product Costing (costing sheets) and for CO internal orders
· Calculating accrued costs in Profitability Analysis
· Output control (printed confirmations, EDI messages, electronic mail)
· Account determination
· Calculating taxes on sales/purchases
· Calculating accruals in Cost Center Accounting
· Pricing for resource planning
Definition: condition type
Controlling (CO)
A distinction, in overhead calculation, is made between:
· Base condition types, which determine the object for which the overhead is to be calculated
· Overhead condition types, which define the percentage overhead to be applied
In resource planning, a condition type determines the types of resource prices that are stored in the SAP System. These can be absolute or percentage values, for example.
Real Estate Management (RE)
An exact definition of a condition that specifies the amount paid for a specific service.
Condition types include:
· Basic rent
· Advance payment for operating costs
· Pest control
Sales and Distribution (SD)
A characteristic of a condition.
For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Treasury (TR)
A characteristic of a condition used to classify financial transactions.
Typical examples of condition types are interest, dividends, or full repayment upon maturity. The various parameters specified for the individual condition types determine how the flows are calculated in the cash flow.
Return ->
Definition: condition_type
Condition type
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Access sequence
With the access sequence you define
· the condition tables used to access the condition records
· the sequence of the condition tables
· which field contents are the criteria for reading the tables
Assign Country to Calculation Procedure
In this activity, you enter the key for the calculation procedure which determines the conditions which are allowed per document and which defines the sequence of the conditions in the document for each country.
Requirements
Each calculation procedure which you enter must contain the necessary specifications for calculating and posting the taxes on sales/purchases. For more information on this, read the chapter "Create calculation procedure".
Activities
1. Assign a procedure for tax calculation to every country with which your company has business dealings.
2. Make sure that the corresponding data for calculating taxes is stored for each calculation procedure which you enter here.
Check and Change Settings for Tax Processing
In this activity you make the necessary specifications for posting taxes. In doing this you specify under a process key the following indicators:
· Tax type
Output tax, input tax, additional taxes, or "not tax-relevant" can be specified as the tax type.
· Nondeductibility of tax amounts
For this, tax amounts are marked as not deductible.
· Posting indicator
Here you specify whether the tax amount is posted separately or distributed to expense or revenue items.
· Tax not relevant to cash discount (Not discount relevant)
This indicator is set only for Canada. If you select it, the system does not take into account the corresponding tax amount when determining the tax base.
Standard settings
Process keys with the most important characteristics for tax amounts have already been set in the standard SAP system.
Recommendation
Do not change the standard settings. Check whether you can use these process keys for your company, making changes only if necessary.
Activities
If you cannot use the standard settings, use new process keys and enter them in your calculation procedure. Do not change the standard SAP process keys.
Note
You must make enhancements to the standard settings if you want to specify a new account key in the "Create calculation procedure" activity. You must create and maintain this key beforehand in the "Settings for tax processing" activity.
Internal processing key
The internal processing keys are used by the system to determine accounts or posting keys for line items which are created automatically.
The processing keys are defined in the system and cannot be changed by the user.
Definition: posting key
Financial Accounting (FI)
A two-digit numerical key that determines the way line items are posted.
This key determines several factors including the:
· Account type
· Type of posting (debit or credit)
· Layout of entry screens
Return ->
Definition: posting_key
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each.
Definition: excise registration
Financial Accounting (FI)
An entity in India that is entitled by law to produce any goods liable to excise.
Each entity is assigned its own excise registration number.
Every factory that manufactures excisable goods is required to register separately, so that a business with seven factories requires seven registrations.
Return ->
Definition: excise registration
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Maintain Excise Groups
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Definition: excise group
Financial Accounting (FI)
A unit within an excise registration, in India, which keeps its own set of excise records.
Whereas the excise registration reports to the excise authorities, the excise group is a purely internal organizational unit. Each excise group keeps records of all transactions that have to be reported to the excise authorities. When the time comes to present these records to the authorities, the excise registration compiles the information from all of its excise groups.
Return ->
Definition: excise group
Maintain Series Groups
Use
In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
Activities
· Define excise series groups based on type of outgoing document
· Assign series group to excise registration ID
· If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
· If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
Maintain Postal Addresses
Use
In this IMG activity, you maintain the addresses of various customs and excise organizations that your company deals with.
You use these addresses in the ARE Documents functions. When you create an ARE-1 or ARE-3, you enter the address of the excise department and the customs department involved in the export process. The system then prints their names and addresses on the AREs.
You can then define a default local excise department for each excise group and a default customs department for each series group.
Definition: ARE-1 document
Logistics - General (LO)
A form, in India, that companies have to fill out when they remove excisable goods from their manufacturing plants for export.
The form exempts them from paying excise duty when they remove the goods from their premises.
Return ->
Definition: ARE-1 document
Definition: ARE-3 document
Logistics - General (LO)
A form, in India, that allows companies to sell otherwise excisable goods from their premises without paying basic excise duty. The buyer of the goods must be in possession of a deemed export license.
The ARE-3 states what goods are being removed and which deemed excise license covers it.
Return ->
Definition: ARE-3 document
Maintain Subtransaction Type with Text
Sub Transaction Type
Sub transaction type is used for multiple purposes
Subcontracting:
It determines the subcontracting attributes and determines the accounts for the posting while doing a sub contracting transaction.
Excise removals
Sub transaction type is also used for determining the accounts while doing excise removals.
With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
Select Tax Calculation Procedure
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
· If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
· If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Definition: condition-based excise determination
Logistics - General (LO
A method that the system uses of determining excise duty in India.
This method requires you to create condition records for each combination of vendor or customer and material (and possibly other conditions).
When you create a purchasing document, the system calls the tax procedure assigned to India. The tax procedure finds all of the condition records that you have created for that combination of vendor and material.
When you create a sales document, the excise duties and sales taxes are determined by the pricing procedure (not the tax procedure).
Return ->
Definition: condition-based excise determination
Definition: formula-based excise determination
Logistics - General (LO)
A method that the system uses of determining excise duty in India.
This method was used in the Country Version India Add-On and requires you to maintain additional data in the Excise Rate Maintenance transaction, J1ID.
When you create a purchasing document, the system calls the tax procedure assigned to India. Each of the excise duties in the tax procedure has its own condition types, and each condition type is assigned to a formula. This formula instructs the system to calculate the excise duty using the data that you have maintained in the Excise Rate Maintenance transaction.
When you create a sales document, the system determines the excise duties and sales taxes using the pricing procedure (not the tax procedure).
Return ->
Definition: formula-based excise determination
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
· Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
· Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
· Specify the conditions in the sales order that are used for excise rates.
· Specify the countervailing duty condition type used for import purchase orders.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
Definition: basic excise duty
Financial Accounting (FI)
The main type of excise duty in India.
It is levied on a wide range of products, for example, foodstuffs, metals, jewellery, leather goods, and machinery.
Return ->
Definition: basic excise duty
Definition: additional excise duty
Financial Accounting (FI)
A form of excise duty, in India, levied on a select range of products, for the most part, textiles.
Return ->
Definition: additional excise duty
Definition: special excise duty
Financial Accounting (FI)
A form of excise duty in India on a limited number of goods, mostly luxury goods, including pan masala, sparkling waters, furs, and yachts.
Return ->
Definition: special excise duty
Definition: cess
Financial Accounting (FI)
In India, a tax on the manufacture of certain products, mostly foodstuffs.
Return ->
Definition: cess
Definition: countervailing duty
Financial Accounting (FI)
A form of excise duty imposed on imports that are subsidized by the country in which they were manufactured.
Countervailing duty (also known as CVD) is intended to make the imports more expensive, thereby redressing any competitive advantage they might have over goods produced locally.
Return ->
Definition: countervailing duty
Define Tax Code for Purchasing Documents
Use
In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities
Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Deter
Sales Tax Code
The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
Procedure
For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.
Note
You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
Definition: tax code
Financial Accounting (FI)
A two-digit code that represents the specifications used for calculating and displaying tax.
Examples of the specifications defined under the tax code are:
· Tax rate
· Type of tax (input tax or output tax)
· Calculation method (percentage included or percentage separate)
Return ->
Definition: tax_code
Definition: tax rate
Financial Accounting (FI)
The percentage rate used to calculate the tax amount.
Return ->
Definition: tax_rate
Assign Tax Code to Company Codes
Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination
Classify Condition Types
Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
· For taxes on purchases, use the condition types contained in the tax procedure.
· For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
Maintain Chapter IDs
Use
In this IMG activity, you maintain the chapter IDs and the corresponding descriptions as per the schedules published by the Central Board of Excise and Customs.
Definition: chapter ID
Logistics - General (LO)
The number given to a material in the schedules of materials published by the government of India.
The schedule lists all materials involved in manufacturing, input materials and output materials alike. It shows how much excise duty is levied on each material.
Each material in the schedule is assigned its own identification code, called "chapter ID."
Example
The schedule contains an entry for ceramic roofing tiles, which are liable to basic excise duty at 16%. The chapter ID associated with these tiles is 6903.10.
Return ->
Definition: chapter ID
Assign Users to Material Master Screen Sequence for Excise D
Use
In this IMG activity, you customize the material master data so that it shows the information relating to excise duty.
Standard settings
Country Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.
Activities
1. Double-click User Screen Reference.
2. Assign all users who need to see the excise duty information to the screen reference IN.
Example
Name Screen Reference
MISHRA IN
Screen Sequence Number
Alphanumeric key identifying the screen sequence. The screen sequence defines the sequence of information units in the material master dialog. A screen sequence is made up of data screens. For information on the screen sequences defined in the standard R/3 system, see the IMG documentation Configuring the Material Master.
Note
When creating a screen sequence, use an alphanumeric key beginning with the letter Y or Z (customer name range). This key cannot subsequently be changed.
Dependencies
You can assign screen sequences to users in the IMG activity Assign Screen Sequences to Users/Material Types/Transactions/Industry Sectors.
Screen reference depending on the user
Grouping of users that determines what screens are displayed in accordance with the user master record when you maintain material master records. It also determines the order in which the screens appear.
Definition: user master record
User and Authorization Management (BC-SEC-USR)
Record that contains important master data for a user in the SAP System.
The user master record contains the assignment of one or more roles to the user. This is how a user menu and the corresponding authorizations for the activities contained in the user menu are assigned to the user. Only users who have a user master record can log on to the system.
Return ->
Definition: user_master_record
Define Form Types
Use
In this IMG activity, you define which form types you want to record in the system. You can only use form tracking for the form types that you enter here.
Example
· Form type: CT3
· Form description: Concessional tax form
· Status: Receive
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
· VS1 (basic excise duty)
· VS2 (additional excise duty)
· VS3 (special excise duty)
· VS5 (sales tax setoff)
· MWS (central sales tax)
· MW3 (local sales tax)
· ESA (service tax)
· ESE (service tax expense)
Specify Excise Accounts per Excise Transaction
Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
If you use subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example
Excise TT DC ind Account name
GRPO CR CENVAT clearing account
GRPO CR RG 23 BED account
GRPO DR CENVAT on hold account
Specify G/L Accounts per Excise Transaction
Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
· Excise group
· Company code
· Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
· Defined the G/L accounts
· Defined the excise groups
· Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
Define Processing Modes Per Transaction
Use
In this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice transactions.
This way, you can tailor the transaction to what your users have to do.
Standard settings
The system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:
· J1IEX_C
This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.
· J1IEX_P
This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.
· J1IEX
In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling them.
Activities
If the standard settings meet your requirements, do not do anything.
Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:
1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.
2. In this activity, enter data as follows:
o Tcode: The transaction code that you have just created.
o Proc. mode: Specify what the users of the transaction will do with the excise invoices.
o Active: Select this indicator to activate the setting.
Example
You might want to create a transaction that only allows users to display excise invoices.
Define Reference Documents Per Transaction
Use
In this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.
Activities
If the standard settings meet your requirements, you do not have to do anything.
Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work.
Definition: excise invoice reference document
Logistics - General (LO)
A document, in India, that you refer to when you enter an incoming excise invoice.
If you have already posted the goods receipt, you can use the goods receipt document as the reference document. Otherwise, you can use the purchase order (or another purchasing document, such as a be a contract or a scheduling agreement).
Example
In the SAP System, you create a purchase order for 100 bags of sand and send the order to your vendor. Two weeks later, the vendor delivers the sand, accompanied by an excise invoice.
When you enter the excise invoice in the system, you specify the number of the original purchase order: this is the reference document.
Return ->
Definition: excise invoice reference document
Maintain Rejection Codes
Use
In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
Activities
For each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.
Specify Which Movement Types Involve Excise InvoicesUse
In this IMG activity, you specify which movement types relating to goods receipts involve excise invoices.
The system uses this information during the goods receipt procedure. When you post a goods receipt using one of the moevement types that you have specified here, the system prompts you to enter the excise invoice number.
Note
This option cannot be used for processing goods receipts without purchase orders.
Maintain Default Excise Groups and Series Groups
Use
In this IMG activity, you specify which excise group and series group you want to appear in these fields by default. You can make separate settings for different combinations of sales organization, distribution channel, division, and shipping point.
Activities
This activity is optional, unless you want the system to automatically create outgoing excise invoices when you create a customer invoice.
In this case, you must also make the appropriate setting in Customizing for Excise Duty, by choosing Basic Subcontracting Attributes
Use
The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
Requirements
Before you continue with this activity, work through the following activities:
· Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Maintain OutputTypes.
Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Assign Forms andPrograms.
Maintain the Program, FORM routine, and the form for the output type.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Printer Determination -> Printer Determination by Plant / Storage Location.
Enter the output device that you use.
Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).
Maintain Movement Type Groups
Use
In this IMG activity, you group movement types together to form movement type groups.
Definition: movement type
Inventory Management (MM-IM)
A classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
Return ->
Definition: movement type
Utilization Determination
Use
In this IMG activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report: When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts the duty should be debited to. Here, you specify those defaults.
You can either:
· Debit all the excise duty to one account
· Debit the excise duty to more than one account, in which case you specify which percentage is to be debited to each account
Example
If you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG 23C account, you would make the following settings:
Acct name BED perc.
RG 23A BED account 50
RG 23C BED account 50
Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the RG 23A account, you would make the following settings:
Acct name BED perc. +
RG 23A BED account X
RG 23C BED account X
When you come to run the report, the system takes the RG 23A account because it is the first one you have entered. If this account does not cover the BED, the system takes the RG 23C account instead.
Maintain Minimum Balances for Excise Accounts
Use
In this IMG activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts during utilization falls below this level, the system automatically utilizes funds in the PLA account.
Activities
Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.
Specify SAPscript Forms
Use
In this IMG activity, for each of your company codes, you specify which SAPscript forms the system prints the excise registers with.
Standard settings
Country Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:
Reg. name Lay. no. Form Tcode/Prog
RG 23A Part I 1 J_2IRG23A_PART1 J_2IRAP1
RG 23C Part I 1 J_2IRG23C_PART1 J_2IRCP1
RG 23A Part II 1 J_2IRG23A_PART2 J_2IRAP2
RG 23C Part II 1 J_2IRG23C_PART2 J_2IRCP2
PLA 1 J_2I_PLA J_2IPLA
RG 23 D 1 J_2I_RG23D J_2IRG23
RG 1 1 J_2I_RG1 J_2IRRG1
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_3 J_2IRT12
The layout description can be left blank or an appropriate description maybe filled in. You may not change the register name. You can have your own layouts and maintain the name here. If the output device and number of copies are maintained it is automatically picked up for printing.
Number Ranges
You can maintain the number ranges for all CIN Number range objects using this transaction
Activities
Please maintain the number ranges for the folllowing objects The no nr has to be '01' for all
1. j_1iintnum
At an Excise group
1. j_1irg23a1
2. j_1irg23a2
3. j_1iRG1
4. j_1irg23c1
5. j_1irg23c2
6. j_1ipla2
7. j_1iintpr2
8. j_1irg23d
9. j_1irg1_t ( material level)
10. j_1iconpla ( if Consolidated PLA is used )
At Series group
1. j_1iexcloc
2. j_1iexcexp
3. j_1idepinv
4. j_1i57Fc ( 57F Challans )
Rewards if Helpful
regards
rb

CIN in ECC6.0

As per my understanding,In SAP R/3 version 4.6 we have to install CIN
patches seperately...how is it in ECC 6.0...does in come in the
standard package or do we have to install seperately...
secondly...what are modules wise components of CIN i.e. what is in cin
...like what report, taxes etc...in FI,SD,MM...where can i find
them...do you have any details...
How do we know that in an SAP system CIN is working or not...i can see
the tax procedures like TAXINN & TAXINJ...does that mean CIN is
installed...
your feedback please...

hi John,
JEXP Basic Excise Duty
JECP Higher Education Cess (2%)
JA1X Secondary and Higher Education Cess (1%)
Pl refer,
http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
Also Pl. follow the link for difference between ECC 6 & ECC 5.0
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
ECC 5.0:
http://help.sap.com/saphelp_erp2004/helpdata/en/c6/feda40ebccb533e10000000a155106/frameset.htm
http://solutionbrowser.erp.sap.fmpmedia.com/
CIN customising missing in the development/test/production client
Additional key words
Cause and prerequisites
CIN related entries missing in the desired client after CIN installation
Solution
Please follow the steps mentioned below.
For copying customizing entries from Client 000 to the target client
In the target client execute the report program RSAVGL00
1. To copy all the condition types use tables T685, T685T & T685A
For the entries to be copied please refer page 146 (Appendix D) & 147
(Appendix E) of user manual, apart from the entries mentioned there,
the following condition types have to be copied :
JEXC, JOCM
2. To copy the tax procedure TAXINJ use tables T683 & T683U & T683S
3. To copy the pricing procedures JFACT, JDEPOT, JEXPORT, JSTKTR
use tables T683 & T683U
4. create tax codes for the various tax rates
5. To copy the accounting keys VS1, VS2, VS3, VS5, NAV use table T007B
6. To copy the Tax Jurisdiction codes IN00, IN01, IN02, 9900, 9999 use
tables TTXJ & TTXJT
7. To copy the Billing type JEX use tables TVFK & TVFKT
8. To copy the Delivery type JF use tables TVLK & TVLKT
Link the Tax procedure TAXINJ to the Country IN
Link the Tax jurisdiction code to the Tax procedure TAXINJ
Set the Pricing procedure determination for Sales and Calculation schema
for Purchasing
Regards,
Ranjit

Diff in TAXINN and TAXINJ

Hii All...
I am new in CIN can anyone please tell me what is the difference in these two procedure ?
Which one is generally used and why ?
And is there any difference in accounts to be maintained in both procedure.
Can any one please tell me both Tax procedure methods in details..
Do the needful help,
Thanks
Abhinay Waikar.

Hi Abinay,
ref the blw detailed info reg cin..
If SAP is implemented for any company in INDIA and the company is in EXCISABLE range then
in SAP ,CIN is implemented ( Country India Version) then
you have to implement the SAP by either of the one type of CIN
1. TAX INN - Condition based CIN implementation
2.TAX INJ -Formula Based CIN implementation
1. If you are using TAXINN then system will pick rate from condition record maintained using tcode FV11.
2. If you are using TAXINJ then rates are to be entered while creating tax code in FTXP & J1ID.
===============================
and ref the blw links which will give the complete details abt cin - tax procedure diff and config.
Cin config. Links
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/207dd2ad-bf92-2b10-a88b-e3a4a01ca7fc?overridelayout=true
http://www.scribd.com/doc/7216701/MMCIN-Customization-Document
http://help.sap.com/saphelp_erp2005/helpdata/en/09/ebf138cdd78a4be10000000a114084/frameset.htm
Diff between TAXINJ and TAXINN
Diff between TAXINJ and TAXINN
diff betwn TAXINN &TAXINJ
Re: Diff in TAXINN and TAXINJ
diff.between Taxinn& taxinj

Pricing procedure for Depot Sales(CIN Version)

HI,
Can anyone explain me TAXINJ and
The Pricing procedure for Depot Sales(CIN Version)
alongwith the Condition Types like JMOD,JECS,JECX etc.
Points will be given
Regrds,
Binayak

Hi Binayak.
JMOD is a FI Tax condition which gets the Basic Excise duty from calculation formula 352. JEX2 is a copy of JMOD and is a Sales pricing condition. The value of JEX2 gets posted for Excise account key. This ensures that the cost accounting of excise value paid is done correctly. In cases where commercial invoice is created after utilization the condition value formula 353 ensures that the actual MODVAT utilized is accounted as excise.
Similarly JAED is a FI Tax condition which gets the Additional Excise duty from calculation formula 352. JEXA is a copy of JAED and is a Sales pricing condition. The accounting is done for the value of JEXA.
JSED is a FI Tax condition which gets the Special Excise duty from calculation formula 352. JEXS is a copy of JSED and is a Sales pricing condition. The accounting is done for the value of JEXS.
JCES is a FI Tax condition which gets the CESS from calculation formula 352. JCED is a copy of JCES and is a Sales pricing condition. The accounting is done for the value of JCED.
So, Conclusion :---->
JMOD -- > Basic Excise duty condition for FI side.
corresponding to it,
JEX2 is the Basic Excise duty condition for SD side.
That's why
account key to JMOD is linkes in TAXINJ.
and
account key to JEX2 is linkes in JDEPOT.
Hope this certainly helps you.
Please reward points if found useful to you.
Let me know if you have any other doubt.
Regards,
Gaurav Raghav.

Function Module for Excise and VAT Calculation

Dear All,
I required one Function module for calculation of Excise % and amount of Invoice Verification Document.
We are use TAXINN tax procedure. I am try to make Purchases Register where we required the Break up of Full tax amount as basic excise duty, Education Cess, S&H Education Cess and VAT Amount.
Thanks
Mukesh

Hi,
Locks are usually appliend on Tables. So you could find the table names affecting.
Then you could goto SE11 and n Lock objects search for table name
Once you identify the lock object. Display. Goto->Lock Modules.
You will get 2 module names one for enqueue and 1 for dequeue.
e.g. Lock object EBKK_ACCNT.
and FMs are DEQUEUE_EBKK_ACCNT and ENQUEUE_EBKK_ACCNT
Hope this helps.
Regards
Megha

Screen configs for DFP and TV

Does anyone know how I can get Gnome to recognise my DFP as the primary screen and the TV out as the secondary?
At the moment my login and mounted drives are showing up on my TV.
Here is my xorg.conf.
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# Files section. This allows default font and rgb paths to be set
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
# FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# Server flags section.
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
Option "DefaultServerLayout" "MonitorTV"
Option "AllowMouseOpenFail" "true"
Option "BlankTime" "0" # I don't like it
Option "NoPM" "true" # I don't like it too :-)
EndSection
# Input devices
# Core keyboard's InputDevice section
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "microsoft"
Option "XkbLayout" "us"
EndSection
# Core Pointer's InputDevice section
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Hitachi CML174"
HorizSync 24-80
VertRefresh 56-75
EndSection
Section "Monitor"
Identifier "Teac TV"
HorizSync 30-50
VertRefresh 60
EndSection
# Graphics device section
Section "Device"
Identifier "Nvidia Ti4400"
Driver "nvidia"
Option "NoLogo" "true"
Screen 0
BusID "PCI:01:05:0"
EndSection
Section "Device"
Identifier "Nvidia Ti4400TvOut"
Driver "nvidia"
Option "NoLogo" "true"
Screen 1
BusID "PCI:01:05:0"
EndSection
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "DFP"
Device "Nvidia Ti4400"
Monitor "Hitachi CML174"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Identifier "TV"
Device "Nvidia Ti4400TvOut"
Monitor "Teac TV"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
EndSection
# ServerLayout sections.
Section "ServerLayout"
Identifier "MonitorTV"
Screen 0 "TV"
Screen 1 "DFP" LeftOf "TV"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
I have TVout and DFP running but need to get the screens around the other way and am stuck on how. Wish Nvidia would get a nice version of Nview going with their Linux Driver. :cry:

Thanks for the reply dp but alas, no go on swaping the server config around. As per you instructions I still get the DFP as the 0.1 display device but with the resolution of the tv. I have tried a few combinations but no go.
Is there a way I can tell gnome to use the other screen instead? The screens aside work fine other than the TV being my primary.

Taxinn and Pricing procedure

Dear MM Experts,
I am working on ECC 6.0 and decided to implement taxinn procedure. I have made both procedures and it is working for service tax is ok. But It is not working with VAT/CST taxes.
It is highly appreciable If any one provide step by step procedure for settings (both Taxinn and MM Pricing procedure) Please send to [email protected]
My TAXinn reqmt incl taxes CST or VAT or Service tax+ Edcess+ H Ed Cess
Regards,

Hi
for Pricing peocedure
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
http://www.sap-img.com/sap-sd/creating-new-pricing-procedure.htm
http://www.sap-basis-abap.com/sapsdlog.htm
For VAT
help.sap.com/bp_bblibrary/500/documentation/U40_BB_ConfigGuide_EN_IN.doc
http://help.sap.com/saphelp_erp2005vp/helpdata/en/dd/ab17adedc9438fb548a8d86efbb187/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/93/75663ca0a9272ae10000000a11405a/frameset.htm
nagesh

Difference between TAXINN and TAXINJ

Dear Friend,
Any one tell me the what are the difference between TAXINN and TAXINJ.
regards
Joseph

Hello,
The only difference between TAXINJ & TAXINN is that TAXINJ is formula based tax calculation procedure for India and TAXINN is that condition based tax calculation procedure. Now a dayu2019s most of the companies are using TAXINJ procedure.
In formula based we are using the formula like (excisecessvat/cst etc.,) but in condition based we just maintain the tax codes which are relevant to taxes and these tax codes has been assign to condition records which we are maintained in MM and SD configuration.
Thanks
Para

TAXINN and TAXINJ -difference

Dear all ,
would you please tell me whether TAXINN can be applied to SAP release 4.6C.As I understand that the TAXINJ is formula based taxprocedure and was most commonly used till version 4.7 what was the reason not to use TAXINN before that ?
Would you please explain is detail .
Thanks in advance.
Sunil

TaxINJ was the procedure which was used earlier to 4.7. This was based on the formula based approach even though the condition technique was introduced in the 4.6C version I think.
The condition based approach until ecc 5.0 did not work perfectly. Thats the reason why it was not popular. Also there was some inconsistency in the way the system determined the tax vaues. In the TAXINJ based on the formula based approach the records for excise and tax was maintianed though tax codes in finance transaction FTXP. This had little flexibility in that the number of combinations for excise and ST/CST was very large and a large number of tax codes need to be maintianed which was cumbersome. It was also very complex and should you wish to change the basis for the values it was difficult.It was totally a tax code based approach.
But it worked O.K though on the export side there are still a lot of things not yet ironed out by SAP even now.
When it came to condition technique it was a refreshing change. It was simple bold and flexible in that you could maintain your your condition using a variety of criteria i.e sales org, country, plant, chapter id , material .....
This offered the company a great flexibility. But the condition value still references to the tax code here which is a dummy tax condition which is required for maintian condition values. each of this condition values is unique unlike the previous where all the taxes are maintained in a single code.
If you want to change the tax rate basis its pretty simple. Just use a different access.
Thats the basic difference. There are other differences too but this is the essential.
regards
Jude

TAXINN AND TAXINJ difference ? AND Which is better ?

HI,
Could u please explain difference between TAXINN AND TAXINJ ? AND Which is better ? And in which scenario they are used ?
Regrds,
Binayak

TAXINJ & TAXINN are Tax Procedures in India. TAXINJ is old version & TAX INN is new version. Both has its own advantage & disadvantage.
Upto 4.6C & partially 4.7 version of SAP, TAXINJ was used. TAXINJ is formula based calculation, in which we maintain the tax rate in Tax Code itself. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST & permutation & combination of these, we require that many Tax Codes. For example:
Tax Code: A1
Taxes: 16% Excise Duty + 2% Education Cess + 12% VAT
Tax Code: A2
Taxes: 16% Excise Duty + 2% Education Cess + 8% VAT
Tax Code: A3
Taxes: 12% Excise Duty + 2% Education Cess + 12% VAT
Tax Code: A3
Taxes: 12% Excise Duty + 2% Education Cess + 8% VAT
From 4.7 version onwards of SAP, TAXINN is being recommended & used. TAXINN is more user friendly & condition record based. In TAXINN, Tax Codes are statistical & of not much relevance, but are required to be maintained in condition record for taxes condition type. This makes Tax Codes simpler. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST, we need not have the tax codes to that combination. For example:
Tax Code: A1
Can be used for any rate of excise duty, as tax code is only required to be maintained statistically in condition record.
Tax Code: A2
Can be used for any rate of VAT, as tax code is only required to be maintained statistically in condition record
Regards,
Rajesh Banka
Reward points if helpful.

VAT reporting for Spain and Italy

Hi,
we have a problem getting VAT report for spain and Italy. Trying to get the report RFUMSV20 for current month but it is giving an error saying " There is no data record for RFUMSV20 Ccode 2008 in Table TRVOR" Can I anyone help me with this?
Thank you
Priti
Edited by: Priti Singh on Mar 13, 2008 7:06 PM

Hello,
If your tax config is correct and the GL accounts are updated, then check for some OSS notes. Probably, you need to apply one of those.
Reg
assign points if useful

Enterprise Hotfix Rollup for Win7 and Server 2008 R2 via WSUS

I stumbled across the fact that Microsoft released a hotfix rollup for Win7 and Server 2008 R2 that contains 90 hotfixes
http://support.microsoft.com/kb/2775511/en-us
The articled I linked above talks about after installing 2775511 (the big hotfix rollup containing 90 hotfixes) it is also necessary to install three more hotfixes:
After this update is installed, you must install update 2732673 to fix a regression issue in the Rdbss.sys file
After this update is installed, you must install update 2728738 to fix a regression issue in the Profsvc.dll file
After this update is installed, you must install update 2878378 re-released on November 11, 2013 to fix a regression issue in the Advapi32.dll file
I have imported all four of these hotfixes into my WSUS server. Do I need to install 277551 first and then install the other three or can all four be approved and go out at once? I guess I am hung up on the language of "After this update is installed
.... ". I want to put all 4 of these on our Win7 machines as well as my 40+ WinServer 2008 R2 machines

I read somewhere that over half of the updates included in Win7 SP1 and WinServer 2008 R2 SP1 were originally released as hotfixes. This means Microsoft made the decision that a large number of hotfixes would benefit every user of these two OSs
I think your conclusion is flawed. The only thing that you can draw from the presented statistic, is that Microsoft determined that a significant percentage of updates originally released as hotfixes warranted the additional investment in regression testing
to subsequently release those hotfixes as updates.
The fact that they bundled these 90 hotfixes together leads me to the same conclusion.
In fact, exactly the opposite conclusion applies: What you have in this package is all the rest of the stuff that didn't make that cut. What you have in this package are still NOT-regression tested hotfixes, they've just been bundled up for easy deployment
(and note that three of them got further broken in the process of bundling), causing yet three more hotfixes to have to be released.
In fact I read the MS Team Blog about this big hotfix release and they say the same thing, all users of these OSs would benefit from the installation of this hotfix rollup, not just a subset of users.
I suspect there are a notable number of patch administrators and systems administrators who would disagree with that self-serving promotion. If, in fact, it's true that "all users" would benefit, then the product team should have invested the effort in properly
regression testing those hotfixes, and releasing them as REAL updates. They did not; ergo the *actual* value is less than claimed.
Of course the bugaboo here is the fact that three other individual hotfixes need to be installed after the big hotfix rollup is installed.
Exactly! (And those are just the attempted fixes that broke something. Who knows how many other "fixes" may still result in newly discovered "broken stuff" that was never broken in the first place.)
The second part of this question should revolve around an itemized review of the hotfixes contained in this rollup with one simple question asked for each:
Have we actually *experienced* the issue addressed by this hotfix.
Where hotfixes are concerned one very simple but important rule applies:
If it ain't broken, don't try to fix it!
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

OSS for TAXINN and CIN in ECC6

Similar Messages

Maybe you are looking for