gst configuration- 2015 tax inj and tax inn

7/25/2019 Gst Configuration- 2015 Tax Inj and Tax Inn

http://slidepdf.com/reader/full/gst-configuration-2015-tax-inj-and-tax-inn 1/35

1 | P a g e

Goods & Service Tax 2015

Contents

Requirement: .......................................................................................................................................... 2

What is GST? ........................................................................................................................................... 2

Impact in the Business transaction: ......................................................................................................... 2

Changes in SAP ........................................................................................................................................ 2

For Taxinn customers: ............................................................................................................................. 2

Configuration in detail: ............................................................................................................................ 3

1 Material Management: ......................... ........................ ......................... .......................... ................ 3

1.1 Sales and Distribution ..................... ......................... ......................... ......................... ............ 12

SAP Oss Note: .................................................................................................................................... 15

Tax Procedure Migration-Taxinj to Taxinn ....................................................................................... 16

1 Executive Summary..................................................................................................................... 16

1.1 Business Context .................................................................................................................. 16

1.2 Solution Overview ................................................................................................................. 16

1.3 Approach and Risk Management ........................................................................................ 17

2 Process Descriptions & Solution Proposal ....................................................................................... 17

2.1 Procurement Process & Solution Proposal ........................ ......................... ......................... ...... 17

2.1.1 Proposed Solution ................................................................................................................. 18

2.2 Sales Process & Solution Proposal ................................................................................................ 23

2.2.1 Proposed Solution ................................................................................................................. 24

How To transport the Taxcodes to production system. ..................... ......................... ......................... ... 30

Procedure ...................................................................................................................................... 30

Diagnosis ....................................................................................................................................... 30

Action : Source System where the tax codes are created: ........................ ......................... ............ 30

1. Step: Export tax codes from source system or source client...................................................... 31

2. Step: Import tax codes into target system or target client ........................................................ 33

Action: Target System where you want to receive the tax codes: ..................... ......................... ... 33

Notes for the transport of tax accounts ........................................................................................ 35



2 | P a g e


Requirement:

Goods and Service Tax changes expected from 1st April 2016, there are two levels

of GST applicable in India. The finance ministry released its first discussionpaper only and SAP is waiting for the complete picture. This document is

prepared for the purpose of immediate solution providing to the TechM

customers. Once final Law announced and SAP’s solution will be informed.

What is GST?

Present Sales Tax, Central Excise duties are combined to one tax slab. The total

tax structure is called Goods and Service Tax. It is two kinds in nature.

Local GST – Sales & purchase within the State

Central GST – Sales & purchase Between the state

Impact in the Business transaction:

0.1 All domestic Sales

0.2 All Domestic Purchase

0.3 All Export

0.4 All Imports

0.5 All Stock Transfers

0.6 All inter state sales & purchase

Changes in SAP

For Taxinn customers:

0.1 Taxinn condition types creations – T. Code OBQ1

0.2 Country pricing procedure changes – T.Code OBQ3

0.3 GL Code Creation – T. Code FS000.4 Excice default updation - SPRO

0.5 Master Data tax % updation with condition types – T. Code FV11

0.6 SD condition type creations – T. Code V/06

0.7 SD pricing procedure changes – T. Code V/08

0.8 SD master data tax % updation with condition types – T. Code VK11

0.9 Excise default updation - SPRO

0.10 Utilization program (j2iun) changes – abap

0.11 Register format changes – abap



3 | P a g e


0.12 Tax code validation- New report- update Tax codes in Purchase

Order(report J_1I_TAXUPDATE_PO) and Contracts (report

J_1I_TAXUPDATE_CNTRCT).0.13 All Purchase orders closed and new Pos to be created

0.14 All Sales orders closed and new SOs to be created

Configuration in detail:

1 Material Management:

1) OBQ1 – Create condition types

For Purchase:

Copy the condition type JMOP - Inp BED Cr % and name it as CGTP - Inp CENT GST Cr %

Copy the condition type JMX1 - Inp BED Cr Total and name it as CGTT - Inp CENT CGST

TOT

Likewise for Sales:

Copy the condition type JAOP - IN: AED setoff % and name it as SGTP - IN: STATE GST %

Copy the condition type JAX1 - IN: A/P AED setoff and name it as SGTT - IN: STATE GST

TOT

Likewise for Inter-state transaction:

Copy the condition type JSOP - IN: SED setoff % and name it as ISTP – IN: INTST GST %

Copy the condition type JSX1 - IN: A/P SED setoff and name it as ISTT – IN INTST GST

TOT



4 | P a g e


2) Define Procedure:

Copy TAXINN procedure and name it as TAXGST - IN; India taxes GST and inserts the

necessary condition and removes the other: (new implementation only).

Assign the procedure against the Country:



5 | P a g e


3) Create Account Keys: - OBCN

Copy the account Keys of VS1, VS2 & VS3 and create and name it as GS1, GS2 and GS3 respectively.

4) Define TAX Accounts:

For GS1 - 18719005



6 | P a g e




7 | P a g e


GS2 - 18719006

GS3 - 18719007



8 | P a g e


5) Create TAX Code: FTXP

V0 – Input NIL TAX

A0 – Output NIL TAX

6) Create Condition record for Tax percentage:



9 | P a g e


1) CGTP – 12%

2) CGTT – 100%

3) SGTP – 10%

4) SGTT – 100%

Vendors – 300000 & 300001

Material – F1000

7) Maintain Excise Defaults: India Localization



10 | P a g e


Classify Condition types for the Procedure TAXGST:

Raw Material Number – 1 & 2



11 | P a g e


Finished Good Material – 4 & 5.

Vendor Number – 300015 & 300016

Customer Number – 100015 & 100016

PO – 4500000016



13 | P a g e


c) Copy the condition JEXT and name it as JCGT:

d) Likewise copy the condition type JEST and name it as JSGT:

Assign these condition type in the Pricing procedure:



14 | P a g e


These conditions are inserted in the row 203, 351, 411 & 415 respectively.

And after executing the transactions, the Invoice and Excise invoice are created.



15 | P a g e


SAP Oss Note:

2014164

2153807

The above are sample config. Please use and change it as per the project based requirement. In

case if the customer is not in taxinn, the taxinj to taxinn migration is needed.



16 | P a g e


Tax Procedure Migration-Taxinj to Taxinn

1 Executive Summary

This solution gives a proposal to migrate the tax procedure and SD Pricing procedure toease out steps to move the open documents with minimal cut over time. Cut over timefor Materials Management (MM) is more compared to Sales and Distribution (SD).

1.1 Business Context

Customers who have implemented Country Version India (CIN) in the initial stages areusing a formula-based tax procedure named 'TAXINJ' which was the initial taxprocedure released for India. In TAXINJ, tax codes are used to derive tax rates. Due tomultiple Excise duty, Service tax, VAT and CST rates and many variations/exemptionsin central/state taxes, TAXINJ customers need to use many tax codes in MM and SD,and customers are running out of tax codes as they have reached the maximum limit oftax codes (2 digits possible). Many tax codes create problems for users, as they need tokeep track of several tax codes at master data level as well as transaction level.

There is another tax procedure, TAXINN, which is based on the pricing conditiontechniques. In TAXINN, tax codes do not play a vital role in rate determination, whereother logistics entities such as plant, material, chapter id, vendor, customer, regions andso on are used for tax rate derivation. A seamless migration from TAXINJ to TAXINNwas not possible and customers need to foreclose open purchase orders in TAXINJ,and start with a new line item in TAXINN tax codes which is a difficult approach,considering the volume ofdocuments.

1.2 Solution Overview

Tax procedure migration covers CIN-relevant MM and SD processes in SAP which havetaxes and tax code implications. With this solution, SAP would like to propose a feasiblemigration from TAXINJ to TAXINN. The proposed solution will have an impact on

processes such as procurement, sales, job work, stock transfers, returns, excise dutyposting transactions, in logistics and financials for goods and services. Non-taxablescenarios would continue without any impact in TAXINN set up also.

The solution is supported for the SAP_APPL software component and valid for releaseECC 6.0 and above via consulting.



17 | P a g e


1.3 Approach and Risk Management

This solution is a consulting service to customers and should be thoroughly tested in theproduction copy environment for all processes with production configuration and data.

This requires down time in customer production system and needs to be evaluated inconsulting.

2 Process Descriptions & Solution Proposal

2.1 Procurement Process & Solution Proposal

Goods and Services procurement process in India has tax implications. Goodsprocurement in India is levied excise duties which are goods movement tax, and servicereceipts in India are levied service tax which is at the time of invoice. There are state-specific sales taxes such as VAT and CST which are calculated on top of the exciseduty for goods. All taxes are defined in tax procedures and migration has an impact onthe procure-to-pay process.

Tax code triggers a taxable scenario in procurement transactions. A tax code is enteredat the time of a purchase order and/or an accounts payable invoice (vendor invoice) andis associated with a tax procedure. Based on the tax configuration, relevant taxes arecalculated in the procurement transactions. Major tax relevant procurement processes

in India are the following.

. Domestic procurement

. Imports procurement

. Dealers procurement

. Job work receipt

. Stock transfer receipt

. Debit and credit memos

. Service receipt

. Vendor returns

The documents involved which have a tax impact for the above process are thefollowing:

. Purchase order/contract

. Goods receipt

. Incoming excise/challan postings

. Invoice verification

. Direct accounts payable (A/P) FI transactions with taxes



18 | P a g e


2.1.1 Proposed Solution

Following steps need to be carried out in the customers' test/sandbox system (thatcontains a copy of the production configuration/data)

1. Configure TAXINN procedure as per customers' business scenario along with OB40settings and relevant CIN settings. If you use COPA or custom specific reports dependon condition types, use TAXINJ procedure's condition types itself in TAXINN also, sothat customer's mapping to COPA valuation fields and customs reports impacts can bereduced. If you are using existing condition types, you need to change the accesssequence for the condition types, based on your business requirement (e.g. MWST to

JTAX).



19 | P a g e


2. In transaction OBBG, change the tax procedure from TAXINJ to TAXINN for countryIN.



20 | P a g e


3. Create TAXINN tax codes as per the customers' requirement for TAXINN proceduresin FTXP.

4. Verify/change input and output tax codes for Indian company codes level in SPRO asshown in the screenshot below, in case customers use different zero tax codes inTAXINN. Otherwise, incorrect tax codes will be posted in excise relevant accounting(PART2). This can affect the customers COPA and other accounting reports which workbased on tax codes.



21 | P a g e


5. Map the TAXINJ and TAXINN tax codes for table J_1ITCJCMAP via transaction code'J1ITCMAP' (For more information, refer to SAP Note 827268). Leave the jurisdictioncodes blank. This tax code mapping is used by the transactions J1IMGPO andJ1IMGCN while updating open purchase orders and contracts.

6. Execute transaction J1IMGPO and Extract open purchase orders/schedulingagreements. This step helps reduce downtime as the open purchase orders andscheduling agreements are downloaded into intermediate SAP tables.



22 | P a g e


7. Execute the transaction J1IMGCN and extract contracts to the intermediate SAPtables. The steps (6&7) can be performed before cut over time.

8. Update TAXINN tax codes at PO, scheduling agreement, service order, STO (if taxcode used) lines by executing the transaction J1IMGPO. This will help avoid foreclosingpurchase order items.



23 | P a g e


9. In the same way, use transaction code J1IMGCN to update tax codes for contractsfrom the intermediate tables. This will help avoid foreclosing contract items. The steps(8&9) need to be performed in the cut over time.

Note

The above programs take care of basic master data validation by considering only openPO items. It also handles basic tax relevant errors, updates the tableJ_1ITCJCUPDATE to keep log of processed documents, avoids PO items which arealready updated with the program, application error logs and basic exceptions handling.Tax calculation in Direct A/P FI transactions are managed with tax codes only.

2.1.2 TAXINJ PO Line Display and A/P Invoice Reversal Refer to SAP Note 2161911for the details.

Note:Do not delete TAXINJ set up from the system (J1ID, tax codes…) as systemneeds the same for displaying TAXINJ PO lines and A/P invoice reversals(MM

side).

2.2 Sales Process & Solution Proposal

Order to cash process in India has tax implications. Sale of goods in India is leviedexcise duty which is a goods movement tax and service provision in India is leviedservice taxes which are at the time of invoice. All taxes are defined in pricingprocedures but unlike procurement, tax code has a minimal role on the SD side. Thereare state-specific sales taxes such as VAT and CST which are calculated on top of theexcise duty for goods.



24 | P a g e


A tax code is required in condition record of tax condition types'. So in general, exciseduties condition records do not have tax codes as they are discount/surcharge in

nature, whereas VAT/CST condition types require a tax code.

Major tax relevant sales processes in India are the following:

. Domestic sales

. Sale to external Customer (EXP)

. Dispatch from a plant (STO)

. Sale from a depot (STO)

. Service provision

. Customer Returns

. Dispatch for job work (sub-contract)

. Credit and debit note to customer scenarios

The documents involved which have a tax impact for the above process are thefollowing:

. Sales order

. Goods issues/deliveries

. Outgoing excise/challan postings

. Customer invoices

. Direct A/R FI transactions with taxes

2.2.1 Proposed Solution

Prerequisites: Ensure that you have performed the following settings:

. Configured TAXINN (with A/R condition types)

. Defined OB40 settings according to customers' requirement

. Changed the tax procedure in OBBG

Since all your pricing procedure's condition types are not changed, the pricing

procedure determination and condition types mapping to valuation fields of COPA is notimpacted. Configure SD Pricing procedure with access sequences for all set ofcondition types.

1. Excise Conditions: If customers are also using pricing formula/routine for exciserelevant conditions in SD pricing procedure (Control via J1ID), remove the formulas inpricing procedure and configure customers' SD pricing procedures as per the businessrequirement.



25 | P a g e


2. Remove condition type 'UTXJ' which is used for various base value determinations,and tax code based rate determination for VAT, CST and Service Tax condition types.These have to be done according to TAXINN set up in SD Procedure, as percustomers' business requirement.



26 | P a g e


3. Maintain required SD relevant access sequence for all (excise, VAT, CST, Service…)tax conditions.



27 | P a g e


4. Maintain condition records with appropriate tax rates at required access levels in theVK11 transaction for all required (Old & present items) cases for relevant taxes (Excise,Services, VAT, CST...), as per customers' business requirements.

5. Sales tax/Service taxes: In SD, tax codes are required for all output tax conditionrecords (transaction VK11) for respective tax condition types (non-excise).



28 | P a g e


6. If G/L accounts are maintained based on the tax code in OB40, customers have toverify/update the same with the new TAXINN tax codes (for tax conditions VAT, CST,Service Taxes and so on) as shown in the screenshot below. Customers' need to take acall in this regard based on the requirement.

7. If customers are using alternate VAT G/L account determination functionality, where

G/L accounts are maintained based on tax codes in the J_1IT030K_V view, they haveto update the same with new TAXINN tax code as shown in the screenshot below. Thisneeds to be done based on customers' requirement.



29 | P a g e


8. If the billing document was created in TAXINJ and not released to accounting,customers need to carry out the New Pricing Run in billing, so that the TAXINN tax codeis considered. Else, they will encounter tax code error 'FICORE 704' during release toaccounting.



30 | P a g e


9. If customers cancel a billing document posted in TAXINJ, they need to carry out theNew Pricing Run so that tax code error FICORE 704 will not come up during release toaccounting.

Note:Tax calculation in Direct A/R FI transactions are managed with tax codes onlyUsage of tax codes or condition record for old Sales Order/Invoice to be decided atcustomers' end based on the requirement.

How To transport the Taxcodes to production system.

Procedure

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.

Diagnosis

Transporting tax codes requires manual post processing. This post processing is also necessary

if tax codes have to be transported from one client to another within the system.

Action : Source System where the tax codes are created:



31 | P a g e


1. Step:

Export tax codes from source system or source client

A. Run Transaction FTXP (Maintain Tax Code). Or in Customizing for the Financial

Accounting Basic Settings, choose Tax on Sales/Purchases -> Calculation -> Define Tax on

Sales and Purchases Code.

B. Enter the COUNTRY you want to work with -> Press ENTER. If the country does not

have jurisdiction codes, screen 101 will be displayed with the country entered.

Otherwise, screen 102 will be displayed with the country entered and a validity date. In

both cases, all other fields are blank.C. Execute Tax code -> Transport -> Export.

D. Assign the export to the relevant transport request or new transport request and make

a note of the request number



32 | P a g e


E. Select and save the tax codes to be transported

F. Save your entries.



33 | P a g e


In your source system, search table T007V for the number of the tranport request

generated in step ‘D’ to ensure that the marked tax codes have been loaded. To check

the table, in the SAP menu choose Tools -> ABAP Workbench -> Overview -> DataBrowser.Enter the table name. The tax codes are in the MWSKZ fields, the tax

jurisdiction codes in the TXJCD fields

G. Release the transport request created in step ‘D’ using transaction SE10 and transport

the tax codes and tax rates into your target system using program r3trans to transport

the request, in the SAP menu choose Tools -> ABAP Workbench -> Overview ->

Workbench Organizer -> Environment -> Customizing Organizer.

2. Step:

Import tax codes into target system or target client

Action: Target System where you want to receive the tax codes:

In your target system, run program RFTAXIMP with the correct transportnumber. Or

you can also start RFTAXIMP from Transaction FTXP -> Tax code -> Transport -> Import.

Or in Customizing for the Financial Accounting Basic Settings, choose Tax on

Sales/Purchases -> Calculation -> Define Tax on Sales and Purchases Code . Choose Tax

Code -> Transport -> Import.

Check the proposed values for the transport request and country and Run the import



34 | P a g e


Give the transport no and select f8 or execute button. The success of the transporting process

can be verified using Transaction FTXA or reviewing tables A003



35 | P a g e


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.

gst configuration- 2015 tax inj and tax inn

Documents