Country India Version (C.I.N) TAXINN FI-CIN Configuration Document V.1.0

Country India Version [C.I.
N]
TAXINN FI-CIN Configuration Document V.1.0
Doc Code
Description
Subject
Book For
Language
SAP
:
:
:
:
:
:
FI_CIN
Country India Version (C.I.N)
TAXINN FI-CIN CONFIG
SAP FI-MM-SD CIN Consultants
English
ECC 6.0
Country India Version [FI-CIN]

Table of Content
CONFIGURING TAX PROCEDURE TAXINN
1) Define Tax Procedures
a)
b)
c)
d)
e)
TAXINN
TAXINJ only procedure
Assign Country to Calculation Procedure
Activate Country Version India for Specific Fiscal Years
Defining Tax Codes for Sales and Purchases
2) Define Access Sequence.

a) JTAX
b) JST1
3) Define Condition Types
a) MM Excise condition types
b) SD Condition Types
c) Service Tax Condition Types
4) Checking and Changing [Account Key] Settings for Tax Processing
5) Define Tax Accounts
Configuring Tax Procedures
Tax on Sales/Purchases
The taxes on sales/purchases include input tax, output tax, acquisition tax and
additional taxes.
In addition to tax codes, percentage rates and tax accounts, you have to specify whether
the cash discount amount reduces the tax base amount, depending on the company code.
This reduction is, for example, possible in Belgium but not in Germany.
The following sections describe the specifications you must make for calculating taxes on
sales/purchases.
1. Check Calculation Procedure /Defining Tax Procedures
Transaction code
OBQ3
IMG menu
Financial Accounting (New) Financial Accounting Global

Settings (New) Tax on Sales/Purchases Basic Settings
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.
Double Click on Define Procedures
Default values :
Usage : Usage of the condition table
Determines for which area the condition is used (for example, pricing or output).
Application
Subdivides the usage of a condition (for example, pricing) for use in different application
areas (for example, sales & distribution or purchasing).

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
TAXINJ PROCEDURE
Select the Procedure TAXINJ

Click on Control Data in Dialog Structure Window
TAXINJ PROCEDURE CONTROL VALUES

TAXINJ PROCEDURE
Fr
Ste Cnt
o
p r
CTyp m To
100
BASB
110
120
200
JMO1
205
JAO1
207
JSO1
210
JMO2
212
JAO2
214
JSO2
215
CONTROL VALUES
M
a Re SubT St AltCT AltCB ActK Accrl Pri Md
n. qt o
at y
V
y
s
nt t Description
362
10
0
11
0
12
0
12
0
12
0
12
0
12
0
12
0
10
0 214
Base Amount
352
Calculated Call
354
JI1
364
JI2
368
JI3
362
NVV
365
NVV
369
NVV
Sub total
IN: A/P BED
deductib
IN: A/P AED
deductib
IN: A/P SED
deductib
IN: A/P BED non
dedu
IN:A/P AED
nondeduct
IN:A/P SED non
deduc
BASE+all duties

217
JIP3
220
JIP1
230
JIP2
250
JSER
260
JSVD
510
JMOD
512
JAED
513
JSED
514
515
JCES
520
JIN1
530
JIN2
540
JIN4
550
JIN5
560
JMOP
561
JMOQ
562
JAOP
563
JAOQ
564
JSOP
565
JSOQ
570
JMIP
571
JMIQ
572
JAIP
573
JAIQ
21
5
21
5
21
5
10
0
25
0
12
0
12
0
12
0
12
0
51
5
51
5
52
0 520
53
0 530
12
0
12
0
12
0
12
0
12
0
12
0
12
0
12
0
12
0
12
0
370
371
363 VS5
IN: A/P ST setoff
363 NVV
IN:A/P CST
363 NVV
ESA
IN:A/P LST
Inp SrvTx (Not
used)
ESE
Inp SrvTx Cr
363
IN: A/R BED
366
IN: A/R AED
360
IN: A/R SED
X
X
367
IN: A/R Cess

sub total
MWS
IN: A/R CST
MW3
MW3
IN: AR LST
IN: A/R CST
Surcharg
IN: AR LST
Surcharg
JI1
Inp BED Cr %
JI1
IN: BED setoff Qty
JI2
IN: AED setoff %
JI2
IN: AED setoff Qty
JI3
IN: SED setoff %
JI3
IN: SED setoff Qty
NVV
Inp BED w/o Cr %

IN: BED inventory
Qt
IN AED inventory
%
IN AED inventory
Qty
MWS
NVV
NVV
NVV

574
JSIP
575
JSIQ
578
JMX1
579
JAX1
580
JSX1
581
JMX2
582
JAX2
583
JSX2
585
588
590
593
JIPS
595
JIPC
598
JIPL
600
700
JLS1
12
0
12
0
56
0
56
2
56
4
57
0
57
2
57
4
57
8
12
0
58
5
59
0
59
0
59
0
59
0
IN SED inventory
%
IN SED inventory
Qty
NVV
NVV
561
Inp BED Cr Total
563
IN: A/P AED setoff
565
571
573
575
IN: A/P SED setoff

IN: A/P BED
inventor
IN: A/P AED
inventor
IN: A/P SED
inventor
583
Total excise duty
120
Copy net price
588
Price + ED
590
VS5
IN Sales tax setoff
590
NVV
IN C Sales tax inv.
590
NVV
IN L Sales tax inv.

Net price + ED +
ST
IN A/P LST out
598
X
X

b) TAXINN PROCEDURE

TAXINN PROCEDURE CONTROL VALUES
TAXINN PROCEDURE CONTROL VALUES
Ste
p
Cnt
r
CTy
p
Fro
m
To
M
a
n.
R
e
qt
Su
bT
o
S
t
a
t
Alt
CT
y
Alt
CB
V
ActK
y
100
110
120
BASB
362
250
260
265
JSER
JSVD
JEC3
100
120
260
ESA
ESE
VS8
266
270
JSE1
JSV2
260
120
JI5
NVV
275
JEC4
270
NVV
276
280
560
JSE2
270
260
120
100
110
561
562
JMOP
JMO
Q
JAOP
563
564
X
X
NVV
276
VS1
120
120
VS1
VS2
JAOQ
JSOP
120
120
VS2
VS3
565
570
JSOQ
JMIP
120
120
VS3
NVV
571
JMIQ
120
NVV
572
JAIP
120
NVV
573
JAIQ
120
NVV
574
JSIP
120
NVV
575
578
JSIQ
JMX1
120
560
NVV
561
579
JAX1
562
563
580
581
JSX1
JMX2
564
570
565
571
X
X
Ac
crl
s
Pr
in
t
M
d
t
Description
Base Amount
Calculated Call
Sub total
Inp SrvTx (Not
used)
Inp SrvTx Cr
Inp SrvTxEces Cr
Inp SrvTxSEces
Cr
Inp SrvTx w/o Cr
Inp SrvTxEces
w/o Cr
Inp SrvTxSEces
w/oCr
Total SrvTx
Inp BED Cr %
IN: BED setoff
Qty
IN: AED setoff %
IN: AED setoff
Qty
IN: SED setoff %
IN: SED setoff
Qty
Inp BED w/o Cr %
IN: BED inventory
Qt
IN AED inventory
%
IN AED inventory
Qty
IN SED inventory
%
IN SED inventory
Qty
Inp BED Cr Total
IN: A/P AED
setoff
IN: A/P SED
setoff
IN: A/P BED
582
JAX2
572
573
583
585
JSX2
574
578
575
583
X
X
586
578
580
587
588
590
583
120
X
X
JEC1
581
120
586
592
593
JEC2
JSEP
587
586
NVV
JI6
594
595
JSEI
JEX1
587
590
NVV
X
596
597
JEX2
JHX1
592
593
X
X
598
JHX2
594
599
VS9
586
588
599
600
601
605
JIPS
JIPC
594
600
600
610
JVCS
600
371
JP4
615
JVRD
600
370
JP5
620
625
JVRN
JVCD
600
600
371
370
JP6
JP7
630
635
JVCN
JIPL
600
600
371
371
JP8
NVV
640
600 635
Field Explanations:
VS5
NVV
Step number
Number that determines the sequence of the conditions within a procedure.
Condition counter
inventor
IN: A/P AED
inventor
IN: A/P SED
inventor
Total excise duty
Sub Total for
Ecess Cr
Sub Total for
Ecess w/o Cr
Copy of Net Price
Inp Ecess Cr %
Inp Ecess w/o Cr
%
Inp SEcess Cr %
Inp SEcess w/o Cr
%
Inp Ecess Cr Tot
Inp Ecess w/o Cr
Tot
Inp SEcess Cr Tot
Inp SEcess w/o Cr
To
Price + Excise
Duty w/o Ecess
Sub Total for
Sales Tax
IN Sales tax setoff
IN C Sales tax inv.
Inp CST under
VAT
Inp VAT Cr NonCG
Inp VAT w/o Cr
Non-C
Inp VAT Cr CG
Inp VAT w/o Cr
CG
IN L Sales tax inv.
Total inclusive of
Taxes

Access number of the conditions within a step in the pricing procedure. During automatic
pricing, the system takes into account the sequence specified by the counter.
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.
Description
From Ref. Step for Percentage Conditions
Condition step, the value of which is the basis for percentage surcharges.
If you specify a to reference step at the same time, the condition values of the two steps
specified and the conditions values of the steps in between are totalled. In this case,
percentage surcharges are calculated on the basis of the total.
Example:
Level CType Description FromSt ToSt ActKy
10 A-B1 Wages
20 A-B2 Salaries
30 A-B3 Overtime/Wages
40 A-Z1 Vacation bonus 10 30 E11
The surcharge for step 40 is added to the total of steps 10 to 30.
To reference step (for percentages)
Condition step up to which the condition values of the previous steps are totalled.
Percentage surcharges are calculated on the basis of the total.
If you specify a from reference step at the same time, the condition values of the two steps
specified and the condition values of the steps in between are totaled.
Example:
Step CType Description FromSt ToStep AcctKey
10 A-B1 Wages

20 A-B2 Salaries
30 A-B3 Overtime/Wages
40 A-Z1 Vacation bonus 10 30 E11
The surcharge for step 40 is added to the total of steps 10 to 30.
Condition determined manually
Use
Conditions, that are given this indicator in the pricing procedure, are only included in
determination (price determination, output determination, batch determination) either if
they are entered manually, for example, on the condition overview screen in Pricing or if
they are transferred from an external process, such as costing.
Condition is mandatory
Indicates whether the condition is mandatory when the system carries out pricing using
this pricing procedure.
Example
If, for example, you always want to include a tax condition (VAT or sales tax) during pricing,
you can set this indicator for the appropriate tax condition type.
Definition: pricing procedure
Sales and Distribution (SD)
A rule type for pricing.
The pricing procedure defines the conditions permitted for a document and the sequence in
which the system takes these conditions into account during pricing.
A standard pricing procedure is defined in the standard SAP system. It contains conditions
most commonly used. These include material prices, discounts, and surcharges, such as
freight, or tax.
Profit Center Accounting (EC-PCA)
A pricing procedure defines how values posted in the SAP system are calculated.
A pricing procedure can consist of the following types of rows:
Base rows, which contain the amount or quantity to which overhead is applied
Calculation rows, which contain a percentage rate to be applied to the base lines
Totals rows, which contain a sum of base amounts and calculated amounts
Pricing procedures are used in Profit Center Accounting to calculate transfer prices.
Condition is used for statistics
This indicator causes a surchage or discount to be set in the document statistically (that is,
without altering the value).
Print ID for condition lines
Controls issue of condition lines when printing documents such as order confirmations or
invoices.
Use
In releases previous to 4.0, the following print indicators are available :
' ' : Condition line is not printed
'X' : Condition line is printed at item level
'S' : Condition line is printed in totals block
The following standard logic is set out for these printing indicators:
o
Item POS of the last condition line is determined with 'X'.
All condition lines that contain an item smaller than POS in the pricing
procedure are only printed if print indicators 'X' or 'S' are set.
All condition lines that contain an item larger than POS in the pricing
procedure, that come before the first tax condition line and which have a nonstatistical VAT condition, receive printing indicator 'S'. The same applies for
condition lines that contain an item larger than POS in the pricing procedure,
that come after the first tax condition line and an active non-statistical VAT
condition.
Condition lines that represent a tax condition type are always printed in totals
blocks with print indicator 'S' (set internally or externally).
Condition lines that represent a condition type that is not a tax condition type
are only printed with print indicator 'S' (set externally or internally) if the
condition value of the condition line is not zero. Condition lines that do not
represent a condition type (i.e. subtotals) are only printed with print indicator
'S' or 'X' (set externally or internally) if the condition value of the condition
line is different from the condition value of the previous condition line in the
pricing procedure.

To provide a better overview of this process, 8 more print parameters are available as of
Release 4.0. These print indicators cannot, however be mixed with the three previous print
indicators ' ', 'X' and 'S' in the pricing procedure. This means that the new indicators are
only taken into account if a no condition lines in the pricing procedure contain printing
indicators 'X' or 'S'.
The new printing indicators have the following settings, and corresponding influence on
processing.
o
'A' : in total: general
'B' : in total: if value <> zero
'C' : in total: if value <> value of predecessor
'D' : in total: if value <> zero and value <> value of predecessor
'a' : at item : general
'b' : at item : if value <> zero
'c' : at item : if value <> value of predecessor
'd' : at item : if value <> zero and value <> value of predecessor
Condition subtotal
Controls whether and in which fields condition amounts or subtotals (for example, a
customer discount or the cost of a material) are stored.
Use
If the same fields are used to store different condition amounts, the system totals the
individual amounts.
Example
These condition amounts or subtotals are used as a starting point for further calculations.
You may, for example, want a subtotal of all the discounts included in the pricing of a sales
order.
Requirement
If the requirement is fulfilled (SY-SUBRC = 0), then output determination also takes into
consideration output type or the access sequence, for which the requirement has been
specified.

Examples
A possible requirement would be, for example, that a difference should be made between
document currency and local currency .
Definition: message determination
Message Control (CA-GTF-BS-MC)
An object that checks whether the application data (for example, data determined in
Customizing) corresponds to the condition records.
If this is the case, one or several messages are "found," which can then be processed (for
example, sent electronically).
The condition records are searched for according to a predefined hierarchy in message
determination.
Condition formula for alternative calculation type
Alternative formula to the formula in the standard system that determines a condition.
Alternative formula for condition base value
Formula for determining the condition basis as an alternative to the standard.
Example
An absolute header discount is, for example, distributed in the standard system according to
the cumulative value of the items.
If the system, however, distributes the absolute header discount according to volume, a
header discount of $30 results in the following discounts:
Item
1
2
Value Volume
Discount
Stand. disc. Volume disc.
$1000 2 cbm
$20
$10
$500 4 cbm
$10
$20
Account key
Key that identifies different types of G/L account.
The account key enables the system to post amounts to certain types of revenue account.
For example, the system can post freight charges (generated by the freight pricing
condition) to the relevant freight revenue account.

Account key - accruals / provisions
Key which identifies various types of G/L accounts for accruals or provisions.
With the aid of the account key, the system can post amounts to certain types of accruals
accounts. For example, rebate accruals which are calculated from pricing conditions can be
posted to the corresponding account for rebate accruals.
c) Assigning Country to Calculation Procedure
Transaction code
SPRO
IMG menu
Financial Accounting (New) Financial Accounting

Global Settings (New) Tax on Sales/Purchases
Basic Settings Assign Country to Calculation
Procedure
Country Key
The country key contains information which the system uses to check entries such as the
length of the postal code or bank account number.
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a
default, is usually used.
It could also be the vehicle license plate country-code or a typical country key, for example,
in Germany the Federal statistics office key.
The country keys are determined at system installation in the global settings.
Since the country key does not have to correspond to the ISO code in all installations,
programs that differ according to certain values of the country key cannot query the country
key T005-LAND1, but have to program based on the ISO code T005 INTCA.
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.
d) Activating Country Version India for Specific Fiscal Years

Transaction code
SPRO
IMG menu

Basic Settings India Activate Country Version
India for Specific Fiscal Years
Component in ACC Interface

This field defines an SAP interface component that you can activate, deactivate, or delete in
the accounting interface.
To-year
Fiscal year up to and including which the transaction applies.
Indicator: Active
Use
Indicates whether a change status is active or not. If you mark this indicator, the
engineering change is relevant for requirements planning and delivery.
Procedure
If you enter both a delivery date and serial number here, the system automatically sets this
indicator to "active".
However, you may want to enter several material numbers for a certain delivery date, but
decide later which serial numbers to activate. In this case, simply unmark the indicator.
e) Defining Tax Codes for Sales and Purchases
Transaction code
SPRO
IMG menu

Calculation Define Tax Codes for Sales and
Purchases
Define Tax Codes for Sales and Purchases
Use
You have to define a separate tax on sales/purchases code for each country in which one
of your company codes is located.
Each code contains one or more tax rates for the different tax types.
If you have to report tax-exempt or non-taxable sales to the tax authorities, you need to
define a tax rate with the value 0.
Note
Do not delete or change any taxes on sales/purchases codes and their definitions as long as
items with these codes exist in the system.
Otherwise, the SAP system displays the tax amounts with incorrect tax rates in the
corresponding reports and determines incorrect amounts during a tax adjustment for
payment transactions.
Standard settings
SAP supplies a tax calculation procedure for each country. The procedure comprises a list of
all common tax types with rules for tax calculation. In addition, example tax codes are
defined for some countries.
Activities
1. Check the standard tax codes for your country. Add further tax codes, if
necessary.
2. Ensure that tax accounts are defined for the automatic posting of taxes.
Notes on transporting tax codes
When tax codes are transported, the tax rates of the tax codes are transported using
auxiliary table T007V. Logical transport object FTXP is used to transport the definition data
of the tax code from table T007A and the language-dependent name to table T007S.
The tax accounts for the tax codes (table T030K) are not transported.
The internal jurisdiction codes are also not transported.
The transport of tax codes between systems or clients consists of two steps:

1. Step:
Export tax codes from source system or source client
2. Step:
Import tax codes into target system or target client
Export
1. In the source system or client, in Customizing for the Financial Accounting Basic
Settings, choose Tax on Sales/Purchases -> Calculation -> Define Tax on Sales
and Purchases Code.
2. Choose Tax Code -> Transport -> Export.
3. Assign the export to the relevant transport request and make a note of the
request number.
4. Select and save the tax codes to be transported.
5. Make sure that the selected tax codes have the transport number in table T007V.
To check the table, in the SAP menu choose Tools -> ABAP Workbench -> Overview
-> Data Browser.
Enter the table name. The tax codes are in the MWSKZ fields, the tax jurisdiction
codes in the TXJCD fields.
6. Arrange the transport of the request to the target system.
To transport the request, in the SAP menu choose Tools -> ABAP Workbench ->
Overview -> Workbench Organizer -> Environment -> Customizing Organizer.
Import
1. Make sure that the transported tax codes are recorded in table T007V of the
target system or target client.
2. In the source system or client, in Customizing for the Financial Accounting Basic
Settings, choose Tax on Sales/Purchases -> Calculation -> Define Tax on Sales
and Purchases Code.
3. The tax codes should have been created in the target system without a tax
percentage rate by the import.
Otherwise you can do this manually:
In the target system, create the tax codes that do not exist there.
Create the tax codes completely, but without tax percentage rates.
If you use internal systems in company codes in the USA or Canada, the relevant tax
jurisdiction codes should also exist. You make the settings for the tax jurisdiction

code in Customizing for Financial Accounting Basic Settings under Tax on Sales and
Purchases -> Basic Settings -> Define Tax Jurisdiction Codes.
4. Choose Tax Code -> Transport -> Import.
5. Check the proposed values for the transport request and country.
6. Run the import.
Choose Country IN.
Tax codes as per Client / customer requirements be created.

One for Input nil tax code and another for Out put nil tax code.
Note: Dont maintain any % in any condition here.

Some Example Tax codes :
Tax
Code
Description
A0
Output VAT-0%
A1
Output VAT-1%
A4
Output VAT-4%
A8
Output VAT-8%
AC
Output VAT-12.5%
AD
Output VAT-13%
AF
Output VAT-15%
AG
Output VAT-16%
AK
Output VAT-20%
AP
Output VAT-25%
AQ
Output VAT-26%
AU
Output VAT-30%
AZ
Output VAT-35%
B0
Output VAT-0% on other sales
B3
Output VAT-38%
BB
Output VAT-46%
BP
Output VAT-60%
BV
Output VAT-25.3% special rate
BW
Output VAT-28.75% special rate
Output VAT-0% on consgt/branch trfer within
BX
state
Output VAT-0% on consgt/branch trfer within
BY
state
BZ
Output VAT-0% on sales to local agents
C0
Output CST-0% (C-form)
C1
C2
C3
C4
CA
Output CST-10%
Output CST-0% on sale to government (DCD
form)
CE
Output CST-0% on sale in-transit (E-I form)
Output CST-0% on interstate consgt/branch
CF
trfer
CG
Output CST-0% on sale in-transit (E-II form)
CH
Output CST-0% on deemed export (H form)
CI
Output CST-0% on sale to SEZ (I form)
CN
Output CST-0% (no form)
CX
Output CST-0% on export
E0
Output service tax-0%

EC
L0
L1
L2
L6
L7
L8
LC
LD
LE
LI
LJ
LK
LO
LP
LQ
LU
LV
LW
M0
M1
M2
M6
MC
MD
ME
MI
N0
N1
N2
N3
N4
N5
N6
N7
N8
N9
NA
NB
NC
ND
NE
Output service tax-12.36%

Input 0%Excise no-cr+0%CST(no form)
Input 8.24%Excise no-cr+0%CST(no form)
Input 16.48%Excise no-cr+0%CST(no form)
Input 0%Excise no-cr+0%CST(C-form)
Input 8.24%Excise no-cr+0%CST(C-form)
Input 0%Excise no-cr+0%CST(F-form)
Input 8.24%Excise no-cr+0%CST(F-form)
Input 16.48%Excise no-cr+0%CST(F-form)
Input 0%Excise no-cr+0%CST(H form)
Input 0%Excise no-cr+10%CST
Input 8.24%Excise no-cr+10%CST
Input 16.48%Excise no-cr+10%CST
Input taxes on imports
Input 0%Excise no-cr+0%VAT-NCG (RD)
Input 0%Excise no-cr+0%VAT-CG (RD)
Input 8.24%Excise no-cr+0%VAT-NCG
Input 8.24%Excise no-cr+0%VAT-CG
Input 16.48%Excise no-cr+0%VAT-NCG
Input 16.48%Excise no-cr+0%VAT-CG
Input 0%Excise no-cr+1%VAT credit-NCG
Input 0%Excise no-cr+1%VAT credit-CG
Input 8.24%Excise no-cr+1%VAT credit-NCG
Input 8.24%Excise no-cr+1%VAT credit-CG
Input 16.48%Excise no-cr+1%VAT credit-CG
Input 0%Excise no-cr+4%VAT credit-NCG
Input 0%Excise no-cr+4%VAT credit-CG

2. Defining /Maintaining Access Sequence Settings
Transaction code
OBQ2 / OBYZ
IMG menu

Double Click on Access Sequences

When we use OBYZ
DOUBLE CLICK ON ACCESS SEQUENCES
Enter
Caution: The table is cross-client
Message no. TB113
Diagnosis
You are in the process of maintaining a cross-client table. You are using the standard table
maintenance screen here, which is frequently used to maintain client-specific Customizing
entries. This message serves to warn you that each change you make will have an effect on
all other clients in the system.
System Response
You have the authorization required for cross-client maintenance.
Procedure
Think carefully about the effect of your changes. Due to logical dependencies between
client-specific Customizing and applications data on the one hand and cross-client
Customizing data on the other hand, changing or deleting cross-client data could result in
inconsistencies.
Therefore such changes should be carefully planned and coordinated, taking all the clients in
the system into consideration.
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
Description
Select the Access Sequence and double click on Accesses in Dialog structure
window.
JTAX ACCESS SEQUENCE
Access sequence - Access number

Indicates the number of the access within the access sequence.
Condition table
A combination of fields that defines the key of a condition record.
For each condition type in a pricing procedure, you define an access sequence. The
access sequence tells the system where to look for relevant condition records for a
particular condition type (a rebate for a specific customer, for example). Each access in the
access sequence refers to a condition table. The fields defined in the table (the key) help the
system to locate valid condition records.
Procedure
When you create a condition table, you specify one or more target fields as the table key.
You must also tell the system where to find the value for each target field. You do this by
specifying source fields. The source fields are usually the same as the target fields, but they
can differ. For example, if the target field "Customer" is part of the key, you can specify that
the system uses "Ship-to party" as the source field and takes the value from there.
Explanatory short text
This text is displayed when you generate reports or call documentation, for example
Requirement
If the requirement is fulfilled (SY-SUBRC = 0), then output determination also takes into
consideration output type or the access sequence, for which the requirement has been
specified.
Examples

A possible requirement would be, for example, that a difference should be made between
document currency and local currency .
Indicator: Exclusive condition access
Controls whether the system stops searching for a record after the first successful access for
a condition type within an access sequence.
Select the Access Number and Double click on Fields in Dialog Structure window.

JST1 ACCESS SEQUENCE [FIELD EXPLANATIONS REMAIN SAME]
Field for condition table

Name of the field from the condition record.
Definition: condition record
Sales and Distribution (SD)
Data record with input and output values for a task.
The condition record is created or changed with condition record maintenance and selected
in the determination process.
The output values are dependent on chosen input values (for example, customer, customer
group, product) and are valid for a certain time period.
A condition record can, for example, contain a specific free-goods discount for a particular
product quantity, or a specific discount for a particular business partner.
Message Control (CA-GTF-BS-MC)
A data record whose key fields display the requirement (condition) under which the
message is found.
The other fields describe the message. Therefore, if one of the data records transferred by
the application corresponds to these key fields, the message is found and can be processed
(for example, in print form or as an electronic message).
Definition
The symbols are used to display how the document data is used in the condition access and
how the data determined in the access is transferred back to the document.
Arrows indicate the direction of the data transfer, the equal sign stands for an access with a
direct value. The tools indicate that the data transfer must be ensured when setting up
pricing by adapting the system using formulas and requirements.
The green LED indicates automatic processing and a red LED marks a line, where data for
correct processing is missing.
Table name of the document structure
Specifies an internal table in which condition information about documents is stored.
Table field for document structure
Determines the data dictionary characteristics for new fields in data dictionary structures.

Use
Reference fields are necessary for the generation of data dictionary structures for conditions
and information structures. A reference structure and a reference field must always be
entered.
Long Field Label
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text
is displayed on the screen in the logon language of the user (if the text was translated into
this language).
A heading can be defined to output the field values in lists. This heading is automatically
included in the list header row, in the logon language.
Spec. Val. Source
Value which the system automatically assigns to a field when it accesses the condition
record.
Dependencies
A field can contain either the value of the source field or the value of a constant (a direct
value).
Characteristic: Initial value allowed
The initial inicator has two functions within Customizing for access sequences. Firstly, it
controls that the system does not access the condition if the field in the document
header/item is blank or 0. Secondly, during automatic return transfer of data that were
determined in the access, it allows an initial value to be returned.
Processing type in access
The processing type determines how the corresponding field is used for the condition
access. A field can be marked as belonging to the fixed/free key part or else as not relevant
for the access.
Fields that are defined as data fields for the definition of condition tables are automatically
marked with an access type.
Dependencies

The processing type influences processing for fields in an access
Characteristic Values
Definition
This valuation describes a priority for the characteristics which can be used as fields when
you create condition tables or document fields for pricing. You can enter values from 01
(very high) to 99 (very low).
The valuation controls how the system selects from the condition records determined from
an access with a free key part. The more fields that are filled with a high priority in the key
of a condition record, the more likely it is to be used for the document.
If no two fields have the same value, then the access is guaranteed to determine exactly
one condition record.
3. Defining condition Types
Transaction code
OBQ1
IMG menu

Double click on Define Condition Types
Condition Type
between different strategy types

Condition type Name
Condition Class Description
Enter text here that best describes the module.
Calculation type Description
Enter text here that best describes the module.
MM Excise Condition Types [ Access Sequence : JTAX]
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
JAIP
JAIQ
JAOP
JAOQ
JAX1
JAX2
JEC1
JEC2
JEX1
JEX2
JHX1
JHX2
JMIP
JMIQ
JMOP
JMOQ
JMX1
JMX2
JSEI
JSEP
JSIP
JSIQ
JSOP
JSOQ
JSX1
JSX2
JNIP
JNOP
JNX1
JNX2
IN AED inventory %
IN AED inventory
Qty
IN: AED setoff %
IN: AED setoff Qty
IN: A/P AED setoff
IN: A/P AED inventor
Inp Ecess Cr %
Inp Ecess w/o Cr %
Inp Ecess Cr Tot
Inp Ecess w/o Cr Tot
Inp SEcess Cr Tot
Inp SEcess w/o Cr To
Inp BED w/o Cr %
IN: BED inventory Qt
Inp BED Cr %
IN: BED setoff Qty
Inp BED Cr Total
IN: A/P BED inventor
Inp SEcess w/o Cr %
Inp SEcess Cr %
IN SED inventory %
IN SED inventory
Qty
IN: SED setoff %
IN: SED setoff Qty
IN: A/P SED setoff
IN: A/P SED inventor
Inp NCCD w/o Cr %
Inp NCCD Cr %
Inp NCCD Cr Total
Inp NCCD w/o Cr Tot

To see the Details of each condition Type
OBQ1:
Select the condition type and click on details icon on application tool bar.
1.
JAIP
IN AED inventory %
2.
JAIQ
IN AED inventory Qty

3.
JAOP
IN: AED setoff %
4.
JAOQ
IN: AED setoff Qty
5.
JAX1
IN: A/P AED setoff

6.
JAX2
IN: A/P AED inventor

7.
JEC1
Inp Ecess Cr %
8.
JEC2
Inp Ecess w/o Cr %
9.
JEX1
Inp Ecess Cr Tot

10.
JEX2
Inp Ecess w/o Cr Tot
11.
JHX1
Inp SEcess Cr Tot

12.
JHX2
Inp SEcess w/o Cr To

13.
JMIP
Inp BED w/o Cr %
14.
JMIQ
IN: BED inventory Qt
15.
JMOP
Inp BED Cr %
16.
JMOQ
IN: BED setoff Qty
17.
JMX1
Inp BED Cr Total
18.
JMX2
IN: A/P BED inventor
19.
JSEI
Inp SEcess w/o Cr %
20.
JSEP
Inp SEcess Cr %
21.
JSIP
IN SED inventory %

22.
JSIQ
IN SED inventory
Qty

23.
JSOP
IN: SED setoff %
24.
JSOQ
IN: SED setoff Qty
25.
JSX1
IN: A/P SED setoff
26.
JSX2
IN: A/P SED inventor
27.
JNIP
Inp NCCD w/o Cr %

28.
JNOP
Inp NCCD Cr %
29.
JNX1
Inp NCCD Cr Total

30.
JNX2
Inp NCCD w/o Cr Tot

Screen field values:
[ Explanation holds good for all categories of Conditions Types]
Condition Type
between different strategy types.
Name
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
Condition class
Preliminary structuring of condition types e.g. in surchages and discounts or prices.
Use
Allows standardised processing of individual condition classes within the system.
Plus/minus sign of the condition amount
Controls whether the condition results in an amount that is negative (a discount), positive
(a surcharge), or whether both positive and negative amounts are possible.
Procedure
If the condition amount can be either positive or negative, leave the field blank. Otherwise,
enter one of the indicators that specify plus or minus.
Calculation type for condition
Determines how the system calculates prices, discounts, or surcharges in a condition. For
example, the system can calculate a price as a fixed amount or as a percentage based on
quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not
happen, the calculation type maintained here is valid for the condition record.

Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all
conditions that relate to freight costs).
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last
digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business
standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:

10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:

1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira
does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated
condition.
This control is only helpful when you use bill of materials or configurable materials.
A duplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
Group condition
Indicates whether the system calculates the basis for the scale value from more than one
item in the document.
Use

For a group condition to be effective, the items must belong to a group. You can freely
define the group to meet the needs of your own organization. The items can, for example,
all belong to the same material group.
Example
A sales order contains two items. Both items belong to the material group 01.
Material
Quantity
Material group
150
01
100
01
The group condition indicator is set in the definition of the condition type for material group
discounts. The condition record for material group 01 includes the following pricing scale:
Scale quantity
Discount
from 1 pc
-1%
from 200 pc
-2%
Neither item alone qualifies for the 2% discount. However, when the items are combined as
part of a group condition, the combined quantity creates a basis of 250 pieces. This basis
then exceeds the scale value of 200 pieces, which is necessary to qualify for the higher
discount.
Routine number for creating group key
Identifies a routine that calculates the basis for the scale value when a group condition
occurs in pricing.
Example
You can specify a routine, for example, that totals the value of all items in a document in
order to determine the basis for a discount.
Rounding difference comparison
Indicator that controls whether rounding difference is settled for group conditions with a
group key routine.
If the indicator is set, the system compares the condition value at header level with the total
of the condition values at item level. The difference is then added to the largest item.
Making manual entries

Indicator which controls the priority within a condition type between a condition entered
manually and a condition automatically determined by the system.
&WHAT_TO_DO?
Make the following entries according to your requirements:
_: No limitations
A: Freely definable
B: The automatic entry has priority. If a condition record exists, the condition cannot be
entered manually.
C: The manual entry has priority. When you enter the condition
manually, the system does not check whether a condition record exists.
D: Cannot be processed manually
Condition applies to header
If this condition is marked as a header condition, it is possible to enter the condition type in
the header condition screen. Checks for changing the condition manually are unaffected by
this.
Condition rate of change for amount/percentage
Specifies whether the amout or percentage for the condition type can be changed during
document processing.
Scope for changing conversion factors
Specifies whether the conversion factors for the units of measure in conditions of this type
can be changed during document processing.
Condition applies to items
Procedure
Mark this field if the conditions of this type are allowed to be entered in the document
items. The condition is then only valid for the particular item in which it is entered.
Delete the scope for changing rate
Indicator that controls whether the condition type may be deleted from the document.
Scope for changing the value

Specifies whether the value of the condition type can be changed during document
processing.
Proposed starting date for the rebate validity period
Specifies the beginning validity date that the system automatically proposes when you
create a rebate agreement of this type.
Example
You can, for example, specify that the system proposes the first day of the current week,
month, or year.
Procedure
If you want the system to propose the current date, leave the field blank. Otherwise, enter
one of the values predefined for your system.
Sales and Distribution: Pricing Procedure in Pricing
Determines which condition types can be used in a document and in which sequence they
appear.
The system uses the pricing procedure that you enter here to control the use of condition
supplements in records of this condition type. You can apply the discounts that are defined
in the pricing procedure as condition supplements during pricing.
Procedure
Enter one of the predefined pricing procedures that control condition supplements. If you
leave the field blank, the condition supplement function in the screens where you maintain
the corresponding condition records is inactive.
Example
You define a pricing procedure to control a condition supplement for a material price. The
condition supplement specifies discounts that you want the system to apply every time the
system accesses a material price condition record. When you define the condition type for a
material price, you enter the pricing procedure that you defined for the condition
supplement.
Date proposed as valid-to date
Proposed value for how long a condition should remain valid.
The system proposes this value for the Valid to date when you create condition records.
Condition records should be deleted from the database

You can use this indicator to control how the system operates when deleting condition
records.
You have the following options:
SPACE: You can set an indicator so that the condition record is no longer used in
pricing. The condition record is then archived in the archiving run. This is how things
happened before Release 4.6A.
A: You can delete the condition records from the database. You then receive a
popup, asking whether the condition record should actually be deleted or whether
the deletion indicator should simply be set.
B: You delete the condition records from the database. You only receive a popup if
there are condition supplements available.
Reference condition type

A condition type which can be used as a reference so that you only have to create
condition records once for condition types that are very similar.
Use
You may need to use different condition types for the same condition. These can
differ in the access sequence, the description, the reference stage of the pricing
procedure or the calculation type, for example.
You can enter the condition type under which the condition records are created.
Example
Condition type MWSI only differs with condition type MWST in the calculation type.
For this reason an entry is made in field ReferenceCondTypeMWST for condition type
MWSI . Now, condition records only need be created for condition type MWST and
not additionally for MWSI.
Dependencies
Field RefApplication is used to refer to condition records from other applications.
Update condition index

Specifies whether the system updates one or more condition indices when maintaining
condition records.
This makes it possible to list or maintain condition records independently of condition type
and condition table, for example.
Dependencies
For source determination for services, service conditions for the vendor are taken into
consideration in the same way as info records, if the flag Condition Index is set for condition
type Total Price (PRS).
Reference application
Application, that can be used to refer to condition records from other applications.

You only have to create condition records once for condition types that are very similar. You
can also refer to condition records from other applications.
You will find further information on the Reference Cond Type field in the documentation.
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the
scale can be based on quantity, weight, or volume.
Formula for scale base value
Formula for determining the scale base value.
You can use this formula to specify calculation methods that are not provided in the
standard system.
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale unit
Unit of measure that the system uses to determine scales when you use group conditions.
The system proposes the unit of measure when you maintain records for group conditions
that are either weight or volume dependent.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the
condition type, that is, the scale type "interval scale" cannot be changed in the condition
record. The reason for this is technical restrictions resulting from the programming within
pricing.
Indicator: Currency Translation after Multiplication
Controls the currency conversion where the currency in the condition record varies with the
document currency.

To calculate a condition value in a document, the system multiplies the amount that results
from the condition record by the item quantity. This indicator controls whether the system
carries out currency conversion before or after the multiplication takes place.
Procedure
If you mark the field, the system converts the condition value into the document currency
after multiplication. If you leave the field blank, the system converts the condition value into
the document currency before multiplication.
Condition exclusion indicator
Indicates whether the system automatically excludes the discounts that are proposed during
pricing.
You can set this indicator in two ways:
For a particular condition record (the field appears on the Details screen)
For all records of a particular condition type (the field appears on the screen where
you define the condition type)
Note
If you set the indicator to exclude conditions, there are several things to consider:
The system will still take into account any condition supplements that are part of
the condition record for the price (condition type PR00, for example)
You can allow for exceptions where you want to include discounts in spite of the
condition exclusion indicator (for a particular discount condition you can specify a
requirement that applies the discount ONLY when the indicator is set)
Condition is Relevant for Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial
accounting as accruals.
If you mark this indicator, the condition appears in the document as a statistical
condition.
Condition for configuration
Before Release 4.0 variant conditions (VA00) had to be created with the condition
category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as
'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition
type:
* 'Variant condition' (KVARC)
* 'Internal costing condition' (KFKIV)

The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
Pricing date
Procedure
Enter the identification code for the date to which a condition of this type is to be
calculated in the sales document. If you do not enter an identification code, the
pricing date or the date of services rendered is used.
Example
It is a good idea to use the goods issue date as the calculation date for freight
surcharges. In this case, you enter 'A' as the identification code.
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is
different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stock
keeping unit. This means that the condition quantity is determined for planned
factors. This means that a change to the conversion factors in the delivery or the
order are not taken into account. Rounding errors can occur during quantity
conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the
quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before
Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as
'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set
up. You can use this to indicate a freight condition as an internal costing condition.
For more information, see note 93426.

Relevance for account assignment
Controls how account assignment is performed for conditions of this type.
Procedure
If you leave the field blank, account assignment is performed in the usual way.
If you enter the indicator B, the system includes the accounting indicator in the account
assignment process. The information from the condition record is forwarded to Controlling
with the classification "accounting indicator". The system links the condition record to the
underlying billing document item to find the accounting indicator that has been assigned to
a particular transaction.
In the standard system, the condition type KBM1 is set up for use in transactions involving
an accounting indicator.
Account assignment using an accounting indicator is often used in Service Management. It
enables you to identify how costs incurred by a particular service transaction arose (for
example, goodwill, under guarantee).
Text determination procedure
Identifies a group of text types that you can use in, for example, a sales document header.
The text procedure also determines the sequence in which the text types appear in the
document.
Example
The text procedure for a sales document header could include the following text types:
A standard header text that the system automatically includes in the document
Standard terms of delivery
Standard terms of payment
Text ID for text edit control
Specifies which text ID appears in Text Edit Control.

The text ID defines the different types of texts that belong to a text object.

SD Condition Types [Access Sequence: JST1]
JIPC
JIPL
JIPS
JVCD
JVCN
JVCS
JVRD
JVRN
IN C Sales tax inv.

IN L Sales tax inv.
IN Sales tax setoff
Inp VAT Cr CG
Inp VAT w/o Cr CG
Inp CST under VAT
Inp VAT Cr Non-CG
Inp VAT w/o Cr Non-C
To see the Details of each condition Type

OBQ1:
Click on details icon

JIPC
IN C Sales tax inv.
JIPL
IN L Sales tax inv.
JIPS
IN Sales tax setoff
JVCD
Inp VAT Cr CG

JVCN
Inp VAT w/o Cr CG

JVCS
Inp CST under VAT

JVRD
Inp VAT Cr Non-CG

JVRN
Inp VAT w/o Cr NonC

Service Tax Conditions (ACCESS SEQ: MWST):
AP - Accounts Payable SERVICE TAX
TCode: OBQ1
Condition Type
JSVD
JEC3
JSE1
JSER
JEC4
JSE2
JSV2
Description
Inp / AP Service Tax Cr
Inp / AP SerTx Ecess Cr
Inp / AP SerTx SEcess Cr
Inp SrvTx (Not used)
Inp SrvTxEces w/o Cr
Inp SrvTxSEces w/oCr
Inp SrvTx w/o Cr

JSVD
Inp / AP Service Tax Cr
TO CHANGE ACCESS
SEQ
JEC3
Inp / AP SerTx Ecess Cr
JSE1
Inp / AP SerTx SEcess Cr

JSER
Inp SrvTx (Not used)
JEC4
Inp SrvTxEces w/o Cr
JSE2
Inp SrvTxSEces w/oCr
JSV2
Inp SrvTx w/o Cr
4. Checking and Changing [Account Key]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.
Transaction code
OBCN
IMG menu

Basic Settings Check and change Settings for Tax
Processing
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.
Text (20 Characters)
Not
Posting disscnt
indic.
rel.
Process
Description
Non
Tax type deductible
ESA
Outp Srv Tx
ESE
Inp SrvTx Cr
JI5
Inp SrvTxSEces Cr
JI6
Inp SECess Cr
JN6
Outp VAT
JN7
Outp CST under VAT
JP4
Inp CST under VAT
JP5
Inp VAT Cr Non-CG
3
2

JP6
Inp VAT w/o Cr NonCG
JP7
Inp VAT Cr CG
JP8
Inp VAT w/o Cr CG
VS1
Inp BED Cr
VS2
Inp AED Cr
VS3
Inp SED Cr
VS5
Inp LST Setoff
VS8
Inp SrvTxEces Cr
VS9
Inp Ecess Cr
ZSE
Outp Ecess on Srv Tx
ZSS
Outp SEces on Srv Tx
2
X
5. Defining Tax Accounts

Transaction code
OB40
IMG menu

Posting Define Tax Accounts
In this activity, you specify the accounts to which the different tax types are to be posted.
The system determines these accounts for automatic postings.
Activities
Define the tax accounts.
Notes for the transport of tax accounts
When you transport tax codes between different systems or clients, no tax accounts are
transported.
Adjust the tax accounts in the source and target system (or source and target client)
manually.
Transaction Description
COA
ESA
Outp Srv Tx
BPIN
ESE
Inp SrvTx Cr
JI5
GL
Account
Posting Keys
Debit
Credit
18141101
40
50
BPIN
26364211
40
50
Inp SrvTxSEces Cr
BPIN
26364218
40
50
JI6
Inp SECess Cr
BPIN
18719000
40
50
JN6
Outp VAT
BPIN
16622111
40
50
JN7
Outp CST under VAT
BPIN
16622121
40
50
JP5
Inp VAT Cr Non-CG
BPIN
26372111
40
50
JP7
Inp VAT Cr CG
BPIN
26372112
40
50
VS1
Inp BED Cr
BPIN
18719000
40
50
VS2
Inp AED Cr
BPIN
18719000
40
50
VS3
Inp SED Cr
BPIN
18719000
40
50
VS8
Inp SrvTxEces Cr
BPIN
26364216
40
50
VS9
Inp Ecess Cr
BPIN
18719000
40
50

Country India Version (C.I.N) TAXINN FI-CIN Configuration Document V.1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Country India Version (C.I.N) TAXINN FI-CIN Configuration Document V.1.0

Uploaded by

Copyright:

Available Formats

Country India Version [C.I.

Country India Version [FI-CIN]

2) Define Access Sequence.

Financial Accounting (New) Financial Accounting Global

Country India Version [FI-CIN]

Double Click on Define Procedures

Country India Version [FI-CIN]

Usage : Usage of the condition table

Country India Version [FI-CIN]

Pricing in sales and distribution

Calculating accrued costs in Profitability Analysis

Output control (printed confirmations, EDI messages, electronic mail)

Calculating taxes on sales/purchases

Calculating accruals in Cost Center Accounting

Pricing for resource planning

Select the Procedure TAXINJ

Country India Version [FI-CIN]

TAXINJ PROCEDURE CONTROL VALUES

Country India Version [FI-CIN]

IN: A/P ST setoff

IN: A/R BED

IN: A/R AED

IN: A/R SED

IN: A/R Cess

IN: A/R CST

IN: BED setoff Qty

IN: AED setoff %

IN: AED setoff Qty

IN: SED setoff %

IN: SED setoff Qty

Inp BED w/o Cr %

Country India Version [FI-CIN]

Inp BED Cr Total

IN: A/P AED setoff

IN: A/P SED setoff

Total excise duty

Copy net price

IN Sales tax setoff

IN C Sales tax inv.

IN L Sales tax inv.

Country India Version [FI-CIN]

Country India Version [FI-CIN]

Country India Version [FI-CIN]

Country India Version [FI-CIN]

Country India Version [FI-CIN]

Country India Version [FI-CIN]

' ' : Condition line is not printed

'X' : Condition line is printed at item level

'S' : Condition line is printed in totals block

Item POS of the last condition line is determined with 'X'.

Country India Version [FI-CIN]

'A' : in total: general

'B' : in total: if value <> zero

'C' : in total: if value <> value of predecessor

'a' : at item : general

'b' : at item : if value <> zero

'c' : at item : if value <> value of predecessor

Country India Version [FI-CIN]

Country India Version [FI-CIN]

Financial Accounting (New) Financial Accounting

Country India Version [FI-CIN]

d) Activating Country Version India for Specific Fiscal Years

Financial Accounting (New) Financial Accounting