GST India

Implement at ion St eps and Guidlines

Page 1 of 97
Table of Contents
Int roduct ion Funct ional Design ................................................................................................................................ 3

Scope and references ............................................................................................................................................ 3

Scope / Reference ............................................................................................................................................. 3

Prerequisites..................................................................................................................................................... 3

Assumpt ions ..................................................................................................................................................... 4

Funct ional Requirements....................................................................................................................................... 5

Underst anding for India GST.............................................................................................................................. 5

St eps for GST India Implement at ions. ................................................................................................................ 6

GST Implement at ion Pre – Requisit e St eps............................................................................................................. 6

St ep 1 : M inimum Support Package(SP) level ..................................................................................................... 6

St ep 2 : Validat ion of exist ing Tax procedure is TAXINN or TAXINJ....................................................................... 7

St ep 3 TAXINJ t o TAXINN M igrat ion Process................................................................................................. 7

St ep 4 FAQ on Tax procedure migrat ion .................................................................................................... 19

St ep 5 This SAP Not e is prerequisit e for SAP Not e 2153807 t o apply DDIC change. ..................................... 20

St ep 6 Tax code updat e programs for PO / SLA and cont ract s. .................................................................... 20

St ep 7 PO and Invoice Display / Cancel Issue .............................................................................................. 35

St ep 8 Errors in report J_1I_TAXUPDATE_PO - J1IM GPO GST ........................................................................... 58

GST Implement at ion Solutioning St eps - Screen changes ...................................................................................... 58

St ep 1 : Badi Definit ion for screen enhancement in enjoy t ransact ions of FI and M M ........................................ 58

St ep 2 : Changes t o t ransaction dat a ................................................................................................................ 59

St ep 3 : Changes t o t ransaction dat a ................................................................................................................ 60

St ep 4 : Changes t o M IRO Invoice it em level screen. ......................................................................................... 61

St ep 5 : GST in Changes for FI Invoice it em level screen. ................................................................................... 66

GST Implement at ion Solutioning St eps - Process changes..................................................................................... 72

St ep 1 : Changes t o Tax Procedure and Pricing Procedure................................................................................. 72

St ep 2 : Badi definit ion for Screen enhancement in Enjoy t ransaction in FI and M M . ......................................... 83

St ep 3 : Tax Calculation based on Vendor region and Vendor GST Classificat ion. ............................................... 84

St ep 4 : Tax Calculation based on Vendor region and Vendor GST Classificat ion. ............................................... 84

St ep 5 : Line it em wise Tax calculat ion for sales invoices................................................................................... 90

St ep 6 : GST India - St ock Transafer Scenarios. ................................................................................................. 90

Page 2 of 97
Int roduct ion

Funct ional Design

Scope and references
Scope / Reference
The Const it ut ion (One Hundred and Tw ent y Second Am endm ent) Bill, 2014, or t he Goods and Service Tax
(GST) bill in India has been passed by t he lower and upper house of t he Parliament on August 03, 2016.

At present,
As you m ust be aw are t hat t he Governm ent of India is planning t o roll out GST from 1st of July, 2017 as
per the lat est updat e. Current ly based on the Draft GST Law , SAP has st art ed releasing solution not es for
DDIC changes, Screen Changes, M ast er Dat a and Transactional dat a.
The next steps:

Legislat ions for CGST, SGST, and IGST act s

Final det ails of t he law need t o be published

The m odel GST law is current ly available for public consum pt ion and we are expect ing t he det ails of t he
law t o be available soon, along wit h t he det ails of GSTN. SAP has st arted releasing solution design based
on t he M odel GST law. However, Once t he final GST law is available, SAP will keep informed regarding t he
det ails of t he final solut ion.

This cont ains inform ation about t he legal change of The Goods and Service Tax for India

This inform at ion is based on legislat ion and regulat ions w hich is subject t o change at any t im e by t he
respective aut horit ies and are t herefore not binding. The inform ation w ill be updat ed if necessary.

Prerequisit es

As t he GST Bill is passed, SAP is current ly w orking on t he solut ion/ proposals part of it. Once t he solution
is ready, it will be available on the service market place. Now t ill t he solution is rolled out t o t he
cust om ers, t he only below pre-requisites needs t o be followed by t hem as m ent ioned.

1. Cust om ers are recom mended t o be at m inim um support pack levels as per not e 1175384
(Com ponent is SAP_APPL) t o obt ain furt her support for legal changes in India Logistics and
Indirect Taxes.

2. It is m andat ory for all t he cust om ers t o have TAXINN as t ax procedure not TAXINJ, as GST will be
based on TAXINN. Cust om ers w ho are st ill using TAXINJ t hey w ould have t o m igrat e t o TAXINN.

Page 3 of 97
Not e: Please not e t hat Tax M igrat ion from TAXINJ t o TAXINN Solution has been delivered by SAP as a
CONSULTING SOLUTION. Kindly check/ plan wit h your consult ing t eam s accordingly. Refer t o all the not es
m entioned in <See Also>.

Refer t o t he below link for SAP's readiness on GST.

ht t ps:/ / launchpad.support.sap.com / #/ legalchangenotificat ion/ det ail/ GSCBIN-348

SAP w ill keep updat ing t his Note as soon as SAP have any relevant inform ation about GST.

Refer t o below not es for Tax M igrat ion Activt ies.

1. 2252781 - FAQ on Tax procedure migrat ion from TAXINJ t o TAXINN
2. 2014164 - TAXINJ t o TAXINN M igration
3. 2167294 - Prerequisite Note for SAP Not e 2153807
4. 2153807 - Im provem ent s in Tax code updat e program s for Purchase Order/ Scheduling
Agreement 2161911 - Purchase order display and Invoice display/ cancel issue

Assum ptions

References

Legal change is current ly not yet published. However, a m odel law is available in t he following link.
http://www.cbec.gov.in/htdocs-cbec/deptt_offcr/model-gst-law.pdf

Page 4 of 97
Funct ional Requirement s

Understanding for India GST

The high level t hings you w ould probably need t o do for a cust om er:

1. Ensure a condit ion based t ax procedure is used. SAP's proposed roadm ap is for TAXINN.

2. The Govt has said t hat the Out going invoice w ill be validat ed by GST Net w ork, so t he sam e w ould
probably be an interface t o GST Net w ork, som et hing like a Golden t ax in China

3. The GST in india w ill be a dual struct ure t ax regim e, so you w ill need t o set up t he requisit e
condition t ypes in your t ax procedure and in your sales schem a.

4. If w e are not on TAXINN, you will need t o m igrate t o TAXINN given as per roadm ap by SAP.

5. Every GST No will be at st at e level, so configurat ion change w ill be required for t he sam e t o be
set up as Business Place in SAP.

6. We w ill have t o be on the required SP Level as per t he det ails w hich will be provided by SAP.

7. There w ill be som e am ount of overlap for VAT and GST Regim e expect ed, so w e need t o plan for
a t ransition t im e for t he t ax applicabilit y and how t o m igrat e t he open docum ent s from VAT t o
GST. Of course, t his w ill also depend on legal guidance on GST from t he Govt and it is still under
w orks.

8. The GST w ill have t hree com ponent s: CGST, SGST and IGST. The t ransact ion w ithin a st at e will
at t ract CGST+SGST. The t ransact ion betw een t w o st at es will have IGST. For Im port s int o India,
Cust om Dut y+IGST will be applicable.

9. Every st at e will have a unique GST Regist erat ion No and that w ill be t he basis for t aking t he GST
credit .

10. All other indirect t axat ion like Excise, Service Tax, Ent ry Tax, Oct roi et c w ill be subsum ed by GST

11. There are eight returns w hich are proposed as part of GST right from GSTR -1 uptill GSTR-8. GSTR
-1 w ill cont ain det ails of Sales from Com mercial Invoices and GSTR -2 w ill cont ain det ails from
Purchases m ade. GSTR-3 w ill provide det ails for m ont hly credit or liabilit y.

12. There are st ill lot of open point s from a functional perspective w here Supplier and seller are
list ed in St at e A and St at e B, but t he goods are supplied in Stat e C, so how t he credit m echanism
w ill w ork. Addit ionally, cert ain product s like Pet roleum Product s are out side t he scope of GST, so
how t o t rack such goods in GST ret urns. Addit ionally, t here is no clarit y on t he det ails of invoices
if t hey can be sent from SAP t o GSTN Net w ork t hrough an aut om at ed utility. Some of t he st at es
are also cont em plating rem oval of SGST component for certain indust ries which in m y view
negat es the purpose of one t ax and brings back t he sam e old t ax struct ure w it h a new nam e, but
again t hese are nit t i grit i we will have t o w ait and see.

Page 5 of 97
Steps for GST India Im plem entations.

Below are t he at t ached OSS not e w hich w e need t o im plement in t he Syst em w it h t he below specific
st eps.

GST Implement at ion Pre – Requisit e St eps

St ep 1 : M inimum Support Package(SP) level

SAP_APPL Release Support Pack

SAP ERP 6.0 (600) SP 26

EHP2 FOR SAP ERP 6.0 (602) SP 16

EHP3 FOR SAP ERP 6.0 (603) SP 15

EHP4 FOR SAP ERP 6.0 (604) SP 16

EHP5 FOR SAP ERP 6.0 (605) SP 13

EHP6 FOR SAP ERP 6.0 (606) SP 14

EHP6 FOR SAP ERP 6.0 for HANA (616 - SAP SP 08

HANA)

EHP7 FOR SAP ERP 6.0(617) SP 07

EHP8 FOR SAP ERP 6.0(618) SP 02

SAP S/ 4HANA ON-PREM ISE 1511 SP 02

Page 6 of 97
Step 2 : Validation of existing Tax procedure is TAXINN or TAXINJ

t o validat e use t he below checks t o verify w het her t he t ax procedure used for Count ry India in your
syst em is TAXINJ or TAXINN.

1) Check in t he transaction code OBQ3 w het her t he field " Condit ion form ula for alternative
calculat ion t ype" has been m aint ained for t he excise condition t ypes or not . If t he sam e has been
m aint ained for t he excise condit ions, t hen t he t ax procedure used in t he syst em is TAXINJ as it
uses alt ernat ive form ula t hat determ ines a condit ion. Where as in t he TAXINN condit ions are
det erm ined using condit ion records m aint ained via transaction code FV11. Similarly you can check
on t he SD pricing procedure as w ell, t here should be no form ula used for t he excise relevant
conditions.
2) Check t hat t he condition value/ rat e w hich is get t ing fetched in t he PO should be from J1ID (Excise
M at er / FTXP for TAXINJ w hereas for TAXINN it should be direct ly from t he condition records
m aint ained via transact ion code FV11.
3) Procedure is TAXINJ, if t he st andard access sequence M WST (or copy of t he sam e) w hich cont ains
only one st andard condit ion t able A003 for condit ion access has been assigned t o the excise
condition t ypes. For TAXINN, excise condition types m ust be having the st andard access sequence
JTAX (or copy of t he same) w hich cont ains m ultiple st andard condit ion for condition accesses. You
can verify t he access sequence and condition t able in t he transact ion code OBQ2.
4) In case of condition based technique i.e. usage of t he TAXINN procedure, com pany code and t ax
code for purchasing docum ent s should be m aint ained in the t able J_1ICONDTAX.
5) For TAXINN procedure all t he excise/ VAT/ CST/ service condition t ypes should have been classified
in t he t able J_1IEXCDEFN w it h t he unique condit ion nam es.
6) There should be no condition t ype UTXJ in the TAXINN set of SD pricing procedure, as t his is only
used in case of TAXINJ for t he base and rat e determ inat ion for condition types.

St ep 3 TAXINJ to TAXINN M igration Process

To follow t he migration process st ep by st ep process m ent ion as below w it h t he help of consulting.

Business Context
Cust om ers w ho have im plement ed Count ry Version India (CIN) in t he initial st ages are using a form ula-
based t ax procedure nam ed 'TAXINJ' w hich w as t he initial t ax procedure released for India. In TAXINJ, t ax
codes are used t o derive t ax rates. Due t o m ult iple Excise dut y, Service t ax, VAT and CST rat es and m any
variations/ exem pt ions in cent ral/ st at e t axes, TAXINJ cust omers need t o use m any t ax codes in M M and
SD, and cust omers are running out of t ax codes as t hey have reached t he m axim um lim it of t ax codes (2
digit s possible). M any t ax codes creat e problem s for users, as t hey need t o keep t rack of several t ax codes
at m ast er dat a level as w ell as transact ion level.

Page 7 of 97
There is anot her t ax procedure, TAXINN, w hich is based on the pricing condit ion techniques. In TAXINN,
t ax codes do not play a vit al role in rate det erminat ion, w here other logist ics entit ies such as plant ,
m at erial, chapter id, vendor, cust om er, regions and so on are used for t ax rat e derivat ion. A seamless
m igration from TAXINJ t o TAXINN w as not possible and custom ers need t o foreclose open purchase
orders in TAXINJ, and st art wit h a new line it em in TAXINN tax codes w hich is a difficult approach,
considering t he volum e of docum ent s.

Solution Overview
Tax procedure m igration covers CIN-relevant M M and SD processes in SAP w hich have t axes and t ax code
im plicat ions. With t his solution, SAP w ould like t o propose a feasible migrat ion from TAXINJ t o TAXINN.
The proposed solution w ill have an im pact on processes such as procurem ent , sales, job w ork, st ock
t ransfers, ret urns, excise dut y posting t ransact ions, in logistics and financials for goods and services. Non-
t axable scenarios w ould continue w it hout any impact in TAXINN set up also

The solut ion is supported for t he SAP_APPL soft w are com ponent and valid for release ECC 6.0 and above
via consulting

Process Descriptions & Solution Proposal

1) Procurement Process
Goods and Services procurem ent process in India has tax implications. Goods procurem ent in India is
levied excise duties which are goods m ovem ent t ax, and service receipt s in India are levied service t ax
w hich is at t he time of invoice. There are st at e-specific sales t axes such as VAT and CST w hich are
calculat ed on t op of t he excise dut y for goods. All t axes are defined in t ax procedures and m igration has
an im pact on t he procure-t o-pay process.

Tax code t riggers a t axable scenario in procurement transact ions. A t ax code is ent ered at the tim e of a
purchase order and/ or an account s payable invoice (vendor invoice) and is associat ed w ith a t ax
procedure. Based on t he t ax configurat ion, relevant t axes are calculat ed in t he procurement transactions.
M ajor t ax relevant procurem ent processes in India are t he following

1. Dom estic procurem ent

2. Im port s procurem ent

3. Dealers procurem ent

4. Job w ork receipt

5. St ock t ransfer receipt

6. Debit and credit m em os

7. Service receipt

8. Vendor ret urns

Page 8 of 97
The docum ent s involved w hich have a t ax im pact for t he above process are t he following:

1. Purchase order/ cont ract

2. Goods receipt

3. Incom ing excise/ challan post ings

4. Invoice verification

5. Direct account s payable (A/ P) FI transactions wit h t axes

Proposed Solution
Follow ing st eps need t o be carried out in t he cust om ers' t est / sandbox syst em (t hat cont ains a copy of t he
production configurat ion/ dat a) Configure TAXINN procedure as per cust om ers' business scenario along
w it h OB40 set t ings and relevant CIN set tings. If you use COPA or cust om specific report s depend on
condition t ypes, use TAXINJ procedure's condit ion t ypes it self in TAXINN also, so that cust omer's m apping
t o COPA valuat ion fields and cust om s report s im pact s can be reduced. If you are using exist ing condit ion
t ypes, you need t o change t he access sequence for t he condit ion t ypes, based on your business
requirem ent (e.g. M WST t o JTAX).

Page 9 of 97
In transact ion OBBG, change t he t ax procedure from TAXINJ t o TAXINN for count ry IN.

Creat e TAXINN t ax codes as per t he cust omers' requirem ent for TAXINN procedures in FTXP

Page 10 of 97
Verify/ change input and out put t ax codes for Indian com pany codes level in SPRO as show n in t he
screenshot below , in case cust om ers use different zero t ax codes in TAXINN. Ot herwise, incorrect t ax
codes will be post ed in excise relevant accounting (PART2). This can affect t he cust om ers COPA and ot her
accounting report s w hich w ork based on t ax codes.

Page 11 of 97
M ap t he TAXINJ and TAXINN t ax codes for t able J_1ITCJCM AP via transaction code 'J1ITCM AP' (For m ore
inform ation, refer t o SAP Not e 827268). Leave the jurisdiction codes blank. This t ax code m apping is used
by t he t ransact ions J1IM GPO and J1IM GCN w hile updating open purchase orders and cont ract s.

Execute transaction J1IM GPO and Extract open purchase orders/ scheduling agreement s. This st ep helps
reduce dow nt im e as t he open purchase orders and scheduling agreement s are dow nloaded int o
int erm ediat e SAP t ables

Page 12 of 97
Execute t he transaction J1IM GCN and extract contract s t o the int erm ediat e SAP t ables. The st eps (6& 7)
can be performed before cut over time

Updat e TAXINN t ax codes at PO, scheduling agreem ent , service order, STO (if t ax code used) lines by
execut ing t he t ransaction J1IM GPO. This w ill help avoid foreclosing purchase order item s

Page 13 of 97
In t he sam e w ay, use t ransact ion code J1IM GCN t o updat e tax codes for cont ract s from t he int erm ediat e
t ables. This will help avoid foreclosing cont ract it em s. The steps (8& 9) need t o be perform ed in t he cut
over t im e

The above program s take care of basic m ast er dat a validation by considering only open PO it em s. It also
handles basic t ax relevant errors, updat es t he t able J_1ITCJCUPDATE t o keep log of processed document s,
avoids PO it em s w hich are already updat ed wit h t he program , applicat ion error logs and basic exceptions
handling.

Tax calculation in Direct A/ P FI t ransact ions are m anaged wit h t ax codes only

A/P Invoice Reversal

Refer t o SAP Not e 2161911 for t he det ails

Note :

Do not delet e TAXINJ set up from t he syst em (J1ID, t ax codes…) as syst em needs t he sam e for displaying
TAXINJ PO lines and A/ P invoice reversals(M M side).

Page 14 of 97
Sales Process

Order t o cash process in India has t ax im plicat ions. Sale of goods in India is levied excise dut y w hich is a
goods m ovem ent t ax and service provision in India is levied service t axes w hich are at t he t im e of invoice.
All t axes are defined in pricing procedures but unlike procurem ent , t ax code has a minim al role on t he SD
side. There are st at e-specific sales t axes such as VAT and CST w hich are calculated on t op of t he excise
dut y for goods.

A t ax code is required in condition record of t ax condition t ypes'. So in general, excise dut ies condit ion
records do not have t ax codes as t hey are discount / surcharge in nat ure, whereas VAT/ CST condit ion t ypes
require a t ax code.

M ajor t ax relevant sales processes in India are t he following

1. Dom estic sales

2. Sale t o ext ernal Cust omer (EXP)

3. Dispat ch from a plant (STO)

4. Sale from a depot (STO)

5. Service provision

6. Cust om er Returns

7. Dispat ch for job w ork (sub-contract)

8. Credit and debit note t o cust om er scenarios

The docum ent s involved w hich have a t ax im pact for t he above process are t he following

1. Sales order

2. Goods issues/ deliveries

3. Out going excise/ challan post ings

4. Cust om er invoices

5. Direct A/ R FI transactions wit h t axes

Proposed Solution

Ensure t hat you have perform ed t he follow ing set tings:

1. Configured TAXINN (wit h A/ R condit ion t ypes)

2. Defined OB40 set t ings according t o cust omers' requirem ent

3. Changed the tax procedure in OBBG

Page 15 of 97
Since all your pricing procedure's condit ion t ypes are not changed, t he pricing procedure determ ination
and condit ion t ypes m apping t o valuat ion fields of COPA is not im pacted. Configure SD Pricing procedure
w it h access sequences for all set of condit ion t ypes.

Excise Condit ions: If cust om ers are also using pricing form ula/ rout ine for excise relevant condit ions in SD
pricing procedure (Control via J1ID), rem ove the form ulas in pricing procedure and configure cust omers'
SD pricing procedures as per t he business requirem ent.

Rem ove condit ion t ype 'UTXJ' w hich is used for various base value det erminat ions, and t ax code based
rat e det erminat ion for VAT, CST and Service Tax condition types. These have t o be done according t o
TAXINN set up in SD Procedure, as per cust om ers' business requirement

Page 16 of 97
M aint ain required SD relevant access sequence for all (excise, VAT, CST, Service…) t ax condit ions

M aint ain condition records w it h appropriat e t ax rat es at required access levels in t he VK11 transact ion for
all required (Old & present it em s) cases for relevant t axes (Excise, Services, VAT, CST...), as per cust om ers'
business requirem ent s

Page 17 of 97
Sales t ax/ Service t axes: In SD, t ax codes are required for all out put t ax condit ion records (transaction
VK11) for respective t ax condition t ypes (non-excise).

If G/ L account s are m aint ained based on t he t ax code in OB40, cust om ers have t o verify/ updat e t he same
w it h the new TAXINN t ax codes (for t ax conditions VAT, CST, Service Taxes and so on) as show n in t he
screenshot below . Cust omers' need to t ake a call in t his regard based on t he requirem ent.

If cust omers are using alt ernat e VAT G/ L account det erminat ion functionalit y, w here G/ L account s are
m aint ained based on t ax codes in t he J_1IT030K_V view , t hey have t o updat e t he same wit h new TAXINN
t ax code as shown in t he screenshot below. This needs t o be done based on cust omers' requirem ent

Page 18 of 97
If the billing docum ent w as created in TAXINJ and not released t o account ing, cust om ers need t o carry out
t he New Pricing Run in billing, so t hat t he TAXINN t ax code is considered. Else, t hey w ill encount er t ax
code error 'FICORE 704' during release t o account ing.

If cust omers cancel a billing docum ent post ed in TAXINJ, t hey need t o carry out t he New Pricing Run so
t hat t ax code error FICORE 704 w ill not com e up during release t o accounting.

Note
Tax calculation in Direct A/ R FI t ransact ions are m anaged wit h t ax codes only

Usage of t ax codes or condition record for old Sales Order/ Invoice t o be decided at cust om ers' end based
on t he requirem ent

St ep 4 FAQ on Tax procedure m igration

This SAP Not e answ ers frequently asked quest ions for Indian t ax procedure migration from TAXINJ t o TAXINN

Refer OSS Note : 2252781

Page 19 of 97
St ep 5 This SAP Note is prerequisite for SAP Note 2153807 to apply DDIC change.

You have t o execute report 'NOTE_2153807'present in t his not e as a prerequisite t o apply SAP Note
2153807 t o updat e Tax codes in Purchase Order(report J_1I_TAXUPDATE_PO) and Cont ract s (report
J_1I_TAXUPDATE_CNTRCT)

Refer OSS Note 2167294

St ep 6 Tax code update program s for PO / SLA and contracts.

To updat e t he Program w e need t o follow t he below few St eps

1. M anual st eps for adding Error log in PO update program

Go t o transact ion SLG0 and click ‘New ent ry t ab’ –

Ent er Object as J1ITAXUPDLOG and Object Text as ‘ India Localization: Tax M igration Log’

Press Ent er and select t he entered object

Page 20 of 97
Double click on Sub-object s and again press ‘New Entries’ t ab –

Now enter

I. ‘J1ITAXUPDPO’ under Object colum n and ‘Tax M igration Log for Purchase Orders’ in Sub-Object
t ext

II. ‘ J1ITAXUPDCNTRCT’ under Object colum n and ‘Tax M igrat ion Log for Cont ract s’ in Sub-Object
t ext .

Press Ent er and save.

Page 21 of 97
 2. M anual St eps for adding Text Elem ent s

In Program J_1I_TAXUPDATE_PO

Go t o Transact ion SE38 –

Ent er Program Nam e as ‘ J_1I_TAXUPDATE_PO’ and select Text Element radio but t on

Click on change but t on and ent er following det ails as show n below in ‘Text Symbol’ Tab –

001 Organizat ional Element s 23 25

002 Tax code & Jurisdiction code 28 28

003 Purchasing Organization 23 23

004 Open Inbound Order Type 23 25

005 Processing Options 18 18

S01 Ext ract Docum ent s 17 20

S02 Updat e Docum ent s 16 22

S03 Test Run 8 18

S04 Docum ent Dat e 13 23

S05 Plant 5 15

Page 22 of 97
Refer t he screenshot below –

Next , Go t o Select ion Text s t ab and Ent er details as show n –

BEDAT

BUKRS Com pany Code

EBELN Purchasing Document No.

EKORG Purchasing Organization

FETCH

M WSKZ Tax Code

PO Purchase Orders

SH Scheduling Agreem ent

TESTRUN

UPDATE

WERKS Plant

WERKS1

Page 23 of 97
Refer t he screenshot show n below

In Program ‘J_1I_TAXUPDATE_CNTRCT’ –

Go t o Transact ion SE38 –

Ent er Program Nam e as ‘ J_1I_TAXUPDATE_PO’ and select Text Element radio but t on and enter t he
following det ails in Text Sym bols t ab –

001 Organizat ional Element s

002 Tax code

003 Purchasing Organization

004 Processing Options

S01 Ext ract Docum ent s

S02 Updat e Docum ent s

S03 Test Run

S04 Docum ent Dat e

S05 Plant

Page 24 of 97
Refer t he screenshot below

In Selection Texts t ab ent er follow ing ent ries –

BEDAT

BUKRS Com pany Code

EBELN Purchasing Document No.

EKORG Purchasing Organization

FETCH

M WSKZ Tax Code

TESTRUN

UPDATE

WERKS Plant

WERKS1

Page 25 of 97
Refer t he screenshot below

Page 26 of 97
 3. Go t o SE93 and Ent er Transaction code nam e as ‘J1ITCM AP’

Click on creat e but t on –

Ent er Short text as ‘M ap Tax Codes’ and select Radio but t on ‘ Transaction with parameters (parameter
transaction) ’ and ent er

Page 27 of 97
Fill t he subsequent fields as show n in below screenshot –

Save t he t ransact ion code.

Aft er saving you can you use t his transaction code t o updat e m apping t able J_1ITCJCM AP.

Page 28 of 97
 4. M anual st eps t o edit colum n nam es of Tax Codes in J_1ITCJCM AP view

Go t o transact ion SE80 and ent er Funct ion Group nam e J1I5

Navigate t o screen num ber 40 and double click on it. On t he right side of t he screen click on ‘Elem ent list ’
t ab followed by ‘Text s/ I/ O tem plat es’ t ab

Page 29 of 97
Now change t he t ext of t he field J_1ITCJCM AP-M WSKZ, J_1ITCJCM AP-M WSKZN t o Taxcode1 and
Taxcode2, respect ively.

Act ivat e.

Page 30 of 97
 5. M anual st eps t o updat e t able J_1ITCJCUPDATE

Go t o transact ion SE11 and ent er t able nam e as J_1ITCJCUPDATE and click on change but t on

Ent er follow ing fields and activat e –

Field Data Element

CPUDT CPUDT

CPUTM CPUTM

Page 31 of 97
 6. St eps for Transaction code creation

Transact ion Code creat ion for program ‘J_1I_TAXUPDATE_PO’.

Go t o transact ion SE38 and ent er program nam e as ‘J_1I_TAXUPDATE_PO’. Right click on program
nam e and navigat e t o ‘Transaction’ option as show n below -

Select ‘Program and select ion screen (report t ransact ion)’ –

Ent er transact ion code name as ‘ J1IM GPO’ and short t ext as ‘ Update Tax code in Purchase Orders’.

Save t he t ransact ion code.

Page 32 of 97
 7. Transaction code creation for program ‘ J_1I_TAXUPDATE_CNTRCT’–

Go t o transact ion SE38 and ent er program nam e as ‘ J_1I_TAXUPDATE_CNTRCT’. Right click on program
nam e and navigat e t o ‘Transaction’ option -

Page 33 of 97
Select ‘ Program and selection screen (report transaction) ’ –

Ent er transact ion code name as ‘ J1IM GCN ’ and short t ext as ‘ Update Tax code in Contracts’.

Save t he t ransact ion.

Im plem ent t he correct ions relevant for your release.

Page 34 of 97
  Report s J_1I_TAXUPDATE_PO and J_1I_TAXUPDATE_CNTRCT w orks in t w o st eps -

o When you select radio but t on " Extract Document s" in 'Processing Opt ion' section at t he selection
screen, report w ill ext ract all t he Inbound Order docum ent s(Purchase order, scheduling
agreem ent , contract s) int o SAP t ables J_1ITCPOUPD, J_1ITCSAUPD, and J_1ITCCNUPD,
respectively.

o To updat e t hese ext ract ed docum ent s wit h new tax code you need t o select radio but t on "
Updat e docum ent s" in 'Processing Opt ion' section at t he select ion screen and t hen execut e t he
report.

o Plant and Docum ent Dat e are provided as a selection opt ion for selective updat e of ext ract ed
document .

 'Test run' option w hen checked gives you t he list of line it em s of t he respective Purchase
Orders/ Scheduling Agreem ent / Cont ract , w hich w ill be updat ed in t he normal run. M ark t he
checkbox TESTRUN, t o enable preview.
 Tax code, plant field has been m ade optional now , if it is filled, line it em s containing ent ered
t ax code and plant will only be picked. If these are kept em pt y all t he lines of Purchase
Orders/ Scheduling Agreem ent / Cont ract will get updat ed with new t ax codes based on ent ries
m aint ained in t able/ view J_1ITCJCM AP.

St ep 7 PO and Invoice Display / Cancel Issue

When we have the tax procedure change from TAXINJ to INN. There will be the below cases.

1. Close purchase order which has all the line items in TAXINJ
2. Purchase order contain both line item TAXINJ and TAXINN
3. New Purchase order which have all line item in TAXINN.

Now when we try to display the taxes for the PO line item which are in TAXINJ, system does not take to Taxes
screen and we are not able to disply the taxes.
Also, when we migrating and try to reverse vendor invoice using the MR8M, we will have a error massage
“FICORE704: Tax code XX in procedure is invalid' is displayed”

When we execute the transaction F.12 for Advance Return for tax on sales / purchase. This report result in error ”
Com bination of calculation procedure and t ax code m issing”

To avoid such issue we need to follow below correction steps in system.

Page 35 of 97
 Apply Manual Changes in Function Module : J_1I4_KALSM_CHANGE

1. Execute transaction SE37 and enter ‘ J_1I4_KALSM_CHANGE’ and select create

2. Select import tab and enter the following parameters, and select ‘optional’ checkbox.

3. Select export tab and enter the following parameters.

4. Save and activate.

Page 36 of 97
  Formulate the Own code based on business requirement in given below enhancement spot or user exits.

Enhancement 1

1. Execute transaction SE37 and enter the following FM: MRM_INVOICE_CANCEL_PERFORM and
select Display.
2. Select the spiral icon, and place the cursor on the
ENHANCEMENT-POINT MRM_INVOICE_CANCEL_PERFORM_01 SPOTS
ES_SAPLMR1M.
Select right click and select the following options.

3. In the following pop-up Select new implementation and give your desired name and short text. Eg:
Z_KALSM_CHANGE.

Page 37 of 97
 4. Now enter the code as per your logic, to store the invoice date of the current invoice in the FM
J_1I4_KALSM_CHANGE.

Sample code:

ENHANCEMENT 105 Z_KALSM_CHANGE. "active version

*Z_kalsm_change

DATA: lv_mgdat TYPE DATS VALUE '20150429', “Enter the date of

migration yyyymmdd) format lv_bukrs TYPE BUKRS.

lv_bukrs
= rbkpv-bukrs.
CALL FUNCTION
'J_1BSA_COMPONENT_ACTIVE'
EXPORTING bukrs
= lv_bukrs component
= 'IN'
* COUNTRY =
* IMPORTING
* ACTIVE_COMPONENT =
EXCEPTIONS
component_not_active =
1 OTHERS
= 2.

IF sy-subrc EQ 0.

IF rbkpv-bldat LT lv_mgdat.
CALL FUNCTION 'J_1I4_KALSM_CHANGE'
EXPORTING
I_BLDAT = rbkpv-bldat.
ENDIF.
ENDIF.

Page 38 of 97
Enhancement 2
1. Execute transaction se37 and enter ‘TAX_INDICATOR_CHECK’ and select display 2. Select the spiral icon,
and perform the following operations

3. Select edit - > Enhancement operations -> Show Implicit…

4. Place the cursor and select the line indicated by the black arrow

Page 39 of 97
5. Select edit -> Enhancement operations -> Create…

6. Select code in the pop-up.

Page 40 of 97
 7. Enter desired name and short text

8. Enter the logic as per your requirement to skip the tax indicator check for the required
doc.

Sample code

ENHANCEMENT 1 Z_KALSM_CHANGE2. "active version

*Kalsm_change
DATA: lv_bldat TYPE DATS, lv_mgdat TYPE DATS VALUE
'20150429'. "Enter migration date lv_kalsm TYPE kalsm
VALUE 'TAXINN'. " TAXINN tax procedure
IF steuerschema EQ lv_kalsm.
IF sy-tcode EQ 'ME23N' OR sy-tcode EQ 'ME23' OR
sy-tcode EQ 'ME33K' OR sy-tcode EQ 'ME33L'.
SELECT SINGLE cpudt FROM J_1ITCJCUPDATE INTO lv_bldat.
CALL FUNCTION 'J_1I4_KALSM_CHANGE'
EXPORTING
I_BLDAT = lv_bldat .

EXIT.

ELSE.
CALL FUNCTION 'J_1I4_KALSM_CHANGE'
IMPORTING
E_BLDAT = lv_bldat.

Page 41 of 97
 IF lv_bldat IS NOT INITIAL AND lv_bldat LT lv_mgdat.
EXIT.
ENDIF.
ENDIF.
ENDIF.
ENDENHANCEMENT.

Enhancement 3

1. Execute transaction SE37 and enter the follow ing FM : PRICING and select Display.

2. Select the spiral icon, and place the cursor on the

ENHANCEMENT-SECTION PRICING_14 SPOTS ES_SAPLV61A.

Select right click and select the follow ing options.

3. Enter desired name and short text

Page 42 of 97
 4. Enter the required logic to pass TAXINJ to T005-KALSM

DATA: lv_bldat TYPE DATS, lv_mgdat TYPE DATS VALUE

'20150429',Migration date lv_poidt TYPE DATS,
lv_kalsm TYPE KALSM_D VALUE 'TAXINJ', -Enter your TAXINJ based tax
procedure lv_bukrs TYPE BUKRS.

lv_bukrs = komk-bukrs.
CALL FUNCTION
'J_1BSA_COMPONENT_ACTIVE'
EXPORTING bukrs
= lv_bukrs component
= 'IN'
* COUNTRY
= * IMPORTING
* ACTIVE_COMPONENT
= EXCEPTIONS
component_not_active =
1 OTHERS
= 2.

IF sy-subrc EQ 0.

CALL FUNCTION 'J_1I4_KALSM _CHANGE'

IMPORTING
E_BLDAT = lv_bldat.

IF lv_bldat IS NOT INITIAL.

IF sy-tcode EQ 'ME23N' OR sy-tcode EQ 'ME23' OR

sy-tcode EQ 'ME33K' OR sy-tcode EQ

'ME33L'.
SELECT SINGLE AEDAT FROM ekpo INTO
lv_poidt

WHERE ebeln = komp-evrtn AND ebelp = komp-evrtp.

IF lv_poidt LT lv_bldat. " Change date of PO line item is <
than

Migration date then TAXINJ

T005-KALSM = lv_kalsm.
ENDIF.
ELSE.
IF T005-KALSM IS NOT INITIAL AND lv_bldat LT lv_mgdat.
T005-KALSM = lv_kalsm.

Page 43 of 97
 ENDIF.
ENDIF.
ENDIF.
perform konv_einlesen
using yes. ENDIF.

USER EXIT
1. Execute transaction SE37 and enter J_1I7_USEREXIT_FILL_KOM K_KOM P

2. Enter the logic as per your requirement to overw rite XKOM K-KALSM as TAXINJ SAM PLE
CODE:

DATA: lv_bldat TYPE DATS, lv_mgdat TYPE DATS VALUE

'20150429', “Enter migration date lv_poidt TYPE DATS,
lv_kalsm TYPE KALSM_D VALUE 'TAXINJ', --Enter the your
TAXINJ based tax procedure lv_bukrs TYPE BUKRS.
lv_bukrs =
xkomk-bukrs.
CALL FUNCTION
'J_1BSA_COMPONENT_ACTIVE'
EXPORTING bukrs
= lv_bukrs component
= 'IN'
* COUNTRY
=
* IMPORTING
* ACTIVE_COMPONENT
= EXCEPTIONS
component_not_active =
1 OTHERS
= 2.

IF sy-subrc EQ 0.
CALL FUNCTION 'J_1I4_KALSM _CHANGE'
IMPORTING
E_BLDAT =
lv_bldat. IF lv_bldat IS
NOT INITIAL.
IF sy-tcode EQ 'ME23N' OR sy-tcode EQ 'ME23' OR
sy-tcode EQ 'ME33K' OR sy-tcode EQ 'ME33L'.

SELECT SINGLE AEDAT FROM ekpo INTO lv_poidt

WHERE ebeln = xkomp-evrtn AND ebelp = xkomp-evrtp.

Page 44 of 97
 IF lv_poidt LT lv_bldat. " Change date of PO line item is <
than Migration date then TAXINJ
XKOMK-KALSM = lv_kalsm.
ENDIF.

ELSE.
IF lv_bldat LT lv_mgdat.
XKOMK-KALSM = lv_kalsm.
ENDIF.
ENDIF.
ENDIF.
ENDIF.

Enhancement 4

This enhancement is valid for the case w here the customer is reusing the conditions that w ere

originally created for TAXINJ based tax procedure.

1. Execute transaction SE38 and enter LV61AA30 and select display

2. Select the spiral icon, and perform the follow ing operations
3. Select edit - > Enhancement operations -> Show Implicit…

Page 45 of 97
4. Place the cursor and select the line indicated by the black arrow 5. Select edit ->
Enhancement operations -> Create…

5. Select code in the pop-up.

6. Enter desired name and short text
7. Enter the required logic to overw rite access sequence.

Sample Code

ENHANCEMENT 325 Z_KALSM_CHANGE4.

*access sequence change
DATA: lv_kalsm TYPE kalsm VALUE 'TAXINJ', -- Enter your
TAXINJ based procedure lv_kozgf TYPE kozgf VALUE 'MWST',
- Enter the required access sequence of the TAXINJ based
procedure lv_bukrs TYPE BUKRS. lv_bukrs = komk-bukrs.
CALL FUNCTION
'J_1BSA_COMPONENT_ACTIVE'
EXPORTING bukrs
= lv_bukrs component
= 'IN'
* COUNTRY
= * IMPORTING
* ACTIVE_COMPONENT
= EXCEPTIONS
component_not_active =
1 OTHERS
= 2.

IF sy-subrc EQ 0.
IF sy-tcode EQ 'ME23N' OR sy-tcode EQ 'ME23'

Page 46 of 97
 OR sy-tcode EQ 'ME33K' OR sy-tcode EQ 'ME33L' OR sy-tcode EQ
‘MR8M’.
IF KOMK-KALSM EQ lv_kalsm.
komt1-kozgf = lv_kozgf.
ENDIF.
ENDIF.
ENDIF.

For cases w here cust omer has defined a separate access sequence for vat conditions:
You may validate the same using the variable KOM T1-KSCHL = ‘cond_name’ and can
pass the required access sequence in the above enhancement.

Enhancement 5

This enhancement is for the displaying tax code description w hile displaying invoices using
transaction M IR4.

1. Execute transaction SE38 and enter LFDCBF4F and select ‘Display’.

2. Place cursor on t he FORM hlp_tax_alternative USING stbuk.

3. Select the spiral icon, and perform the follow ing operations
4. Select edit - > Enhancement operations -> Show Implicit…

Page 47 of 97
5. Place the cursor and select the line indicated by the black arrow
6. Select edit -> Enhancement operations -> Create…

7. Select code in the pop-up.

8. Enter desired name and short text.
9. Enter the required logic.

Page 48 of 97
Sample code:

ENHANCEMENT 3 Z_KALSM_CHANGE5. "active version

*tax description change DATA: lv_budat TYPE DATS,
lv_mgdat TYPE DATS VALUE '20150429', "Enter migration date
lv_kalsm TYPE KALSM_D VALUE 'TAXINJ', "-Enter your TAXINJ
based tax procedure lv_bukrs TYPE BUKRS.
lv_bukrs =
i_stbuk.
CALL FUNCTION
'J_1BSA_COMPONENT_ACTIVE'
EXPORTING bukrs
= lv_bukrs component
= 'IN'
* COUNTRY
= * IMPORTING
* ACTIVE_COMPONENT
= EXCEPTIONS
component_not_active =
1 OTHERS
= 2.

IF sy-subrc EQ 0.

IF BKPF-BUDAT LT lv_mgdat.
lv_budat = BKPF-BUDAT.

CALL FUNCTION
'J_1I4_KALSM_CHANGE'
EXPORTING i_bldat
= lv_budat.
ENDIF.

ENDIF.

ENDENHANCEMENT.

Page 49 of 97
Enhancement 6

This enhancement is for the displaying tax code description, continuation of above
enhancement logic.

1. Execute transaction SE37, enter ‘FI_F4_M WSKZ’ and select display.

2. Select the spiral icon, and then select Enhancement point ‘KALSM _CHANGE’ and create
an implementation

3. Select code in the pop-up.

4. Enter desired name and short text.
5. Enter the required logic.

Sample Code:
ENHANCEMENT 1 Z_KALSM_CHANGE6. "active version
*Tax code description change DATA: lv_budat TYPE DATS,
lv_mgdat TYPE DATS VALUE '20150429', "Enter migration date
lv_kalsm TYPE KALSM_D VALUE 'TAXINJ'. "-Enter your TAXINJ
based tax procedure lv_bukrs TYPE BUKRS.
lv_bukrs =
i_stbuk.
CALL FUNCTION
'J_1BSA_COMPONENT_ACTIVE'

Page 50 of 97
 EXPORTING bukrs
= lv_bukrs component
= 'IN'
* COUNTRY
=
* IMPORTING
* ACTIVE_COMPONENT
= EXCEPTIONS
component_not_active =
1 OTHERS
= 2.
IF sy-subrc EQ 0.

CALL FUNCTION
'J_1I4_KALSM_CHANGE'
IMPORTING e_bldat
= lv_budat.

IF lv_budat LT lv_mgdat.
i_kalsm = lv_kalsm.

ENDIF.

ENDIF.

ENDENHANCEMENT.

Enhancement 7

This enhancement is for the displaying tax code description for FI transactions: FB03

1. Execute transaction SE38 and enter M F05LO00 and select ‘Display’.

2. Customers on EHP5 (SAP_APPL 605) and below :
a.) Select PBO module “ get_bset_zeile”

Page 51 of 97
b.) Then select the enhancement point kalsm_change2 and create an implementation

c.) Select code in the pop-up.

d.) Enter desired name and short text.
e.) Enter the required logic.

3. Customers on release EHP6 ( SAP_APPL 606) and above:

a.) select the sub routine pbo_get_bset_zeile

b.) Place cursor on the FORM pbo_get_bset_zeile USING i_loopc TYPE syloopc.
c.) Select the spiral icon, and perform t he follow ing operat ions
d.) Select edit - > Enhancement operations -> Show Implicit…
e.) Place the cursor and select the line indicated by the black arrow
f.) Select edit -> Enhancement operations -> Create…
g.) Select code in the pop-up.
h.) Enter desired name and short text.
i.) Enter the required logic.

Page 52 of 97
Sample code:

*Tax code description change DATA: lv_budat TYPE DATS,

lv_mgdat TYPE DATS VALUE '20150429', "Enter migration date
lv_kalsm TYPE KALSM_D VALUE 'TAXINJ', "-Enter your TAXINJ
based tax procedure lv_bukrs TYPE BUKRS.
lv_bukrs =
bseg-bukrs.

CALL FUNCTION
'J_1BSA_COMPONENT_ACTIVE'
EXPORTING bukrs
= lv_bukrs component
= 'IN'
* COUNTRY
=
* IMPORTING
* ACTIVE_COMPONENT
= EXCEPTIONS
component_not_active =
1 OTHERS
= 2.
IF sy-subrc EQ 0.
IF bkpf-budat LT lv_mgdat.
SELECT SINGLE * FROM t007s
WHERE spras = sy-langu
AND kalsm =
lv_kalsm AND mwskz
= bset-mwskz.
IF sy-subrc NE
0. CLEAR
t007s.
ENDIF.

ENDIF.
ENDIF.

Page 53 of 97
Enhancement 8

* Implement enhancement if error 713 still occurs, aft er implementation of all the above
enhancements

1. Execute transaction “ SE37” and enter “ FI_TAX_CHK_JURISDICTION_ACTIVE” and

select ‘Display’.
2. Select the spiral icon, and perform the follow ing operations.
3. Select edit - > Enhancement operations -> Show Implicit…
4. Place the cursor and select the line indicated by the black arrow
5. Select edit -> Enhancement operations -> Create…

6. Select code in the pop-up.

7. Enter desired name and short text.
8. Enter the required logic.

Sample Logic:

*kalsm change 8
DATA: lv_bldat TYPE DATS, lv_mgdat TYPE DATS
VALUE '20150429', "Enter migration date lv_kalsm
TYPE kalsm VALUE 'TAXINN'. " TAXINN tax procedure

CALL FUNCTION 'J_1I4_KALSM _CHANGE'

IMPORTING
E_BLDAT = lv_bldat.
IF lv_bldat IS NOT INITIAL AND lv_bldat LT lv_mgdat.
EXIT.
ENDIF. .

Page 54 of 97
  This enhancement is for the displaying tax code description w hile displaying invoices
using transaction M IR4

1. Execute transaction SE38 and enter RFUM SV00 and select ‘Display’.
2. Place cursor on t he FORM READ_T007A.

3. Select the spiral icon from the application toolbar.

4. From the menu bar, Select Edit - > Enhancement operations -> Show Implicit Enhancement
Options

5. Place the cursor on the highlighted row as show n below .

Page 55 of 97
6. From the menu bar, Select Edit -> Enhancement Operations -> Create

7. Select Code in the pop-up w indow .

8. Enter desired name and short text for your enhancem ent implementation.

9. Enter the required logic w ithin the implementation. You can refer t he follow ing sample code.
This code needs t o be enhanced/ adjusted according to your needs.

Sample code:

ENHANCEMENT 1 ZTAX_MIGRATION. "active version

DATA: lv_kalsm TYPE kalsm VALUE 'TAXINJ', "Enter TAXINJ
based ta x procedure lv_mgdat TYPE dats VALUE
'20151029', "Enter the migration date wa_tax_item
TYPE rfums_tax_item.

CALL FUNCTION
'J_1BSA_COMPONENT_ACTIVE'
EXPORTING bukrs
= t001-bukrs component
= 'IN'
* COUNTRY =

Page 56 of 97
* IMPORTING
* ACTIVE_COMPONENT =
* OUT_COUNTRY =
EXCEPTIONS
COMPONENT_NOT_ACTIVE = 1
OTHERS = 2
.

IF sy-subrc = 0.
* Initial data selection
IF gt_alv IS INITIAL.
IF bkpf-budat LT lv_mgdat OR
( bkpf-budat GE lv_mgdat AND bkpf-awtyp = 'RMRP'
AND bkpf-stgrd IS NOT INITIAL ).
kalsm = lv_kalsm.
ENDIF.

ELSE.
* Input Tax Line Item Information
IF gt_alv-t_voste_ep IS NOT
INITIAL. LOOP AT gt_alv-
t_voste_ep INTO wa_tax_item WHERE budat LT lv_mgdat
AND
mwskz = mwskz.
kalsm = lv_kalsm.
EXIT.
ENDLOOP.
*Output Tax Line Item Information
ELSE.
LOOP AT gt_alv-
t_auste_ep INTO wa_tax_item WHERE budat LT lv_mgdat
AND
mwskz = mwskz. kalsm = lv_kalsm.
EXIT.
ENDLOOP.
ENDIF.
ENDIF.
ENDIF.

Page 57 of 97
St ep 8 Errors in report J_1I_TAXUPDATE_PO - J1IM GPO GST

When we execut e t he Transact ion J1IM GPO or report program J_1I_TAXUPDATE_PO

1. You get runtim e error as "LOAD_COM M ON_PART". This happens w hen you are on EHP 7 SP04 or
above.

2. You do extraction of Scheduling Agreement s, you also get Purchase Orders ext ract ed.

3. You require M ultiple Purchase Organizat ion, Docum ent t ype, Docum ent dat e as input for
ext raction.

4. Back ground job fails for Scheduling agreem ent

To Im plem ent t o correct ion Please Im plem ent t he S Not e - 2200639

GST Implement at ion Solut ioning St eps - Screen changes

St ep 1 : Badi Definit ion for screen enhancement in enjoy t ransact ions of FI and M M

A new BAdI im plem ent ation 'GST_INV_SCREEN_ENH' has been int roduced for t he BAdI definition
'BADI_FDCB_SUBBAS08' w it h t his SAP Not e only for GST India specific requirem ent s. This BAdI
im plem ent ation is used for subscreen enhancem ent in function group FDCB, basic dat a screen 010 for
vendors and screen 0510 for cust om er. This screen is accessed in t he Enjoy t ransact ions for FI docum ent
ent ry or M M invoice receipt .

Screen 0010 is accessed in 'Basic dat a' t ab in below t ransact ions:

A. In FI, t ransact ions FB60, FB65, FV60 and FV65.
B. In M M , transact ion M IRO.
Screen 0510 is accessed in 'Basic dat a' t ab in below t ransact ions:
A. In FI, t ransact ions FB70, FB75, FV70 and FV75.
As part of t he GST India solution t w o new fields have been int roduced in the above screens
A. GST Part ner.
B. Place of Supply.
These fields w ill be visible only w hen:
A. Count ry of com pany code is IN.

 Steps to create the BAdI Implementation “GST_INV_SCREEN_ENH” in package

“J1I_GST_LO”
1. Execute transaction SE18 and select radio but t on 'Enhancem ent Spot '.
2. Ent er t he Enhancem ent Spot wit h t he name as ‘BADI_FDCB_SUBBAS’ and select display.

Page 58 of 97
 3. Under t he “ BAdI Definit ions” select “ BADI_FDCB_SUBBAS08” and select right click, from t he
cont ext m enu select ‘Creat e Im plem ent ation” .
4. Select “ Creat e Enhancement Im plem ent at ion” but t on.
In t he pop-up ent er Enhancem ent Im plement at ion “ GST_INV_SCREEN_ENH” and short t ext
“ GST Invoice Screen Enhancement ” . Ent er package as “ J1I_GST_LO”
5. Save and activat e.

 Creation of Function Group J_1IG_CUSTOM ER_SUBSCR

1. Execute transaction code SE80 and select " Funct ion Group" from t he drop dow n m enu.
2. Provide t he name " J_1IG_CUSTOM ER_SUBSCR" and press Ent er.
3. Syst em w ould prom pt for creation. Select " YES" .
4. Provide t he Short Text as " Cust omer Invoice Subscreen Enhancement ".
5. Save t he object under t he package " J1I_GST_LO".
6. Act ivat e t he funct ion group.

Follow t he above st eps for creat ing the below Funct ion Groups-
Funct ion Group: J_1IG_ITEM _SCR_VALIDATE
Descript ion : FSKB Screen field validat ion

Funct ion Group: J_1IG_IV_ITEM

Descript ion : M R1M validations

Funct ion Group: J_1IG_VENDOR_SUBSCR

Descript ion : Vendor Invoice Subscreen Enhancem ent

St ep 2 : Changes to t ransact ion dat a

Implement the corrections relevant for your release.

a.) If your SAP BASIS release is 702 or above execute 'NOTE_2415115' t o apply Dat a Dict ionary
object s.
b.) If your SAP BASIS release is 701 or below you have t o perform t he m anual changes as per t he
at t ached docum ent s of t his SAP Note.

Page 59 of 97
Below Steps need to follow manually for Point 2.

1. Execute transaction code SE11.

2. Select radio but t on 'View ' and enter 'RBKP_V'.
3. Select 'Change'.
4. Select 'Table Fields' but t on.
5. Select t he t able RBKP and select 'Choose' but ton.
6. Select check box for fields: 'GST_PART' & 'PLC_SUP'.
7. Select 'Copy'.
8. Save and Activat e.

Aft er im plement at ion and activat ion of Dat a Dictionary, perform m anual activity as described in t he
m anual post im plement at ion st ep need t o im plement the OSS Not e 2405502.

Im plem ent OSS Not e 2413682 M issing Object s w hen Im plem enting SAP Not es 2405502 and 2415115.
Im plem ent OSS Not e 2418631 Issues w hile applying GST India SAP Not e 2415115.

St ep 3 : Changes to t ransact ion dat a

1. Apply t he correction inst ruct ion as relevant for your release based on t he below point s.
2. GST India Changes t o M ast er Dat a : Im plem ent ing t he OSS Not e 2385575
3. Follow t he below m entioned st eps before im plem ent ing t he not e

Creat ion of Function Group J_1IG_UTILITIES

1. Execute transaction code SE80 and select t he drop dow n opt ion of " Funct ion Group" . 2. Provide
t he nam e J_1IG_UTILITIES and press Enter.
2. Syst em w ould prom pt for creation. Select " YES" .
3. Provide t he Short Text as " Utilit y object s for GST India".
4. Save t he object under t he package " J1I_GST_LO".
5. Act ivat e t he funct ion group.

Creat ion of M essage Class " J_1IG_M SGS"

1. Execute transaction code SE91 and provide t he name" J_1IG_M SGS". Click on " Creat e" but t on.
2. Provide t he short t ext as "GST India: M essage class" .
3. Save t he object under t he package " J1I_GST_LO".
4. Ent er t he follow ing m essages.

000 & & & & & &

001 Plant is blank. It is required t o determ ine HSN code for m at erial 002 M ultiple GST Part ner exist s in
billing document 003 M ult iple sold t o part y exist s in billing document 004 Business Place is not filled in

Page 60 of 97
t he accounting line 005 M ult iple Business Place exist s in single account ing docum ent 006 No dat a for t he
selection crit eria

St ep 4 : Changes to M IRO Invoice item level screen.

Screen 6310 is accessed in 'PO reference' t ab in below t ransact ions:

M IRO, M IR4, M IR7
As per GST India solut ion t he following new field has been int roduced in t he screen SAPLM R1M 6310:
HSN/ SAC
The fields w ill be visible only w hen:
Count ry of com pany code is IN.

Input/ Output Field

1. Execute transaction SE51, ent er Program : “ SAPLM R1M ” and Dynpro: “ 6310” .
2. Select radio but t on ‘At t ributes’ and select ‘Change’.
3. In t he ‘Ot her At t ribut es’ sub screen, you w ill find ‘Row s (lines)/ Colum ns’. In t he Column box of
‘Edit ing’ (‘M aint en.’) ent er a value w hich is an increm ent of one. E.g.: 146 is changed t o 147.

Page 61 of 97
 4. Select ‘Layout ’ but t on from t he application toolbar and confirm t he pop up w hich m ay occur.
5. In t he ‘Screen Paint er’ select t he ‘Input / Out put Field’ but t on. Scroll t o t he extrem e right of t he
t able control.

Note: Refer the highlighted elements and position in the below screenshot:

SAP_APPL 600 & 602:

Place t he ‘Input / Out put Field’ at t he end.

SAP_APPL 603 and above:

Place t he ‘Input / Out put Field’ before the field ‘rm08-addtl_data’

Page 62 of 97
6. Double click t he field t o open ‘Screen Paint er: at tributes’ w indow .

Page 63 of 97
 7. Ent er Nam e: “ DRSEG-HSN_SAC” , and confirm t he following pop up:

8. Ent er Search help: “ H_T604F” .

9. Ensure “ From dict.” checkbox is checked.

Text Field’ – “HSN/ SAC

10. Now select ‘Text Field’ and place above t he ‘Input / Out put Field’ w hich has been creat ed (st ep 5)

Page 64 of 97
11. Double click t he ‘Text Field’ t o open ‘Screen Paint er: At tribut es’ w indow

12. Ent er Nam e: “ DRSEG-HSN_SAC” and confirm the pop up

13. Ent er Text : “ HSN/ SAC”

14. Ensure “ From dict.” checkbox is checked
15. Save t he and activat e t he screen
16. Apply t he CI of t he note

Page 65 of 97
 Ensure flow logic aft er application of CI:

St ep 5 : GST in Changes for FI Invoice it em level screen.

SAPLFSKB Screen 0100 is accessed in below 'Enjoy' t ransact ions:

FB60, FB65, FB70, FB75, FV60, FV65, FV70, FV75
As per t he GST India solut ion t he following new field has been int roduced in t he screen SAPFSKB 0100:
HSN/ SAC
These fields w ill be visible only w hen:
Count ry of com pany code is IN.

1. Execute transaction SE51, ent er Program : “ SAPLFSKB” and Dynpro: “ 0100” .

2. Select radio but t on ‘At t ributes’ and select ‘Change’.
3. In t he ‘Ot her At t ribut es’ sub screen, you w ill find ‘Row s (lines)/ Colum ns’. In t he Column box of
‘Edit ing’ (‘M aint en.’) ent er a value w hich is an increm ent of one. E.g.: 147 is changed t o 148

Page 66 of 97
Input/ Output Field

4. Select ‘Layout ’ but t on from t he application toolbar and confirm t he pop up w hich m ay occur.
5. In t he ‘Screen Paint er’ select t he ‘Input / Out put Field’ but t on. Scroll t o t he extrem e right of t he
t able control and place t he ‘Input / Out put Field’
Note: Refer the highlighted elements and position in the below screenshot:

Page 67 of 97
6. Double click t he field t o open ‘Screen Paint er: at tributes’ w indow .

7. Ent er Nam e: “ ACGL_ITEM -HSN_SAC” , and confirm the follow ing pop up

8. Ent er Group: “ 001”

9. Ensure “ From dict.” checkbox is checked.

Page 68 of 97
Text Field’ – “HSN/ SAC

10. Now select ‘Text Field’ and place above t he ‘Input / Out put Field’ w hich has been creat ed (st ep 5).

11. Double click t he ‘Text Field’ t o open ‘Screen Paint er: At tribut es’ w indow

12. Ent er Nam e: “ ACGL_ITEM -HSN_SAC” and confirm t he pop up

Page 69 of 97
 13. Ent er Text : “ HSN/ SAC” .
14. Ent er Group: “ 001” .
15. Ensure “ From dict.” checkbox is checked.
16. Save t he screen.

Flow logic for the Screen SAPLFSKB 0100 – delta 1, 2& 3

Delta 1:
17. Select t he ‘Flow logic’ but t on
18. Find :

acgl_item-segment, acgl_item-psegment, "/glflex

acgl_item-prodper, "ERP05

Insert t he following st at em ent bet w een them : acgl_item-

hsn_sac,
"Note2376723

Delta 2:
There w ill be anot her inst ance of t he code m entioned in st ep 18, insert t he follow ing
st at em ent at t hat place t oo:

acgl_item-hsn_sac, "Note2376723

Page 70 of 97
Delta 3:

19. Find:
FIELD acgl_item-wrbtr MODULE star_amount ON *-INPUT.

CHAIN.
"Note594081
FIELD acgl_item-menge.
FIELD acgl_item-meins.
MODULE menge_meins ON CHAIN-
INPUT. ENDCHAIN.

Insert t he following st at em ent s as highlight ed:

CHAIN. "vN2376723
FIELD acgl_item-hsn_sac.
MODULE validate_india_gst_fields.
ENDCHAIN. "^N2376723

20. Save and activat e t he screen

Page 71 of 97
GST Implement at ion Solut ioning St eps - Process changes

St ep 1 : Changes to Tax Procedure and Pricing Procedure.

Create Condition table

Condit ion t able com binations are for your reference. You can refer t he sam e and can creat e your ow n
condition t able as per your business requirem ent .

Create Condition table for material

Transaction code: M / 05
Combination#1: Country/ Region/ PlntRegion/ GST Class./ Tax ind./ Ctrl code

Technical View:

Page 72 of 97
Combination#2: Region/ PlntRegion/ GST Class./ M aterial

Create Condition table for services

Transaction code: M / 05
Com bination#1: Region/ Plnt Region/ GST Class./ Act ivit y

Create Access Sequence

Transact ion code : OBQ2

Page 73 of 97
Field Assignment –

Create Condition type

Transaction code : OBQ1
Creat e Cent ral GST condition type.

Page 74 of 97
Create State GST Condition type

Create Integrated GST condition type

Page 75 of 97
Create state GST Non – deductible condition type

Create Central GST Non – deductible condition type

Page 76 of 97
Create Integrated GST Non- deductible condition type

Create Accounting Key

Transaction Code: OBCN
Central GST

Inegrated GST

Page 77 of 97
State GST

Update Tax Procedure – TAXINN as shown below

Transact ion code : OBQ3
Note : This is an illust rat ion of GST condit ions only, st eps m ay vary from act ual, GST
conditions should get calculate on BASE condition, for Non-deduct ible condit ions
use st andard non-deductible accounting key “ NVV” or your ow n account ing key

M aintain Tax Percentage Rate

You m ay m aint ain the t ax percent age rat es using t ransaction code FV11, eit her based
on t he proposed access sequence or your ow n access sequence

Page 78 of 97
 Pricing procedure configuration for GST

Create Condition Table

T Code: V/ 05

Create condition table for material

Com bination#1: Count ry/ PlntRegion/ TaxCl1Cust / TaxCl.M at / Region/ Ct rl code

Com bination#2: Plnt Region/ Region/ TaxCl1Cust / M at erial

Create condition table for services using T code V/ 05

Com bination#1: Plnt Region/ Region/ TaxCl1Cust / Act ivity

Page 79 of 97
Create Access sequence
T Code : V/ 07

Fields Assignment:

Create Condition type

T. Code V/ 06

Create output Central GST condition type

Page 80 of 97
Create Output State GST condition type

Create Output Integrated GST condition type

Page 81 of 97
Create Accounting Key
T. Code : OV34
Create Sales accounting key for central GST, integrated GST and State GST

Update Pricing Procedure – JINFAC

Transaction code: V/ 08
Note : This is an illust rat ion of GST condit ions only, st eps m ay vary from act ual, GST
conditions should get calculate on BASE condition

Page 82 of 97
St ep 2 : Badi definit ion for Screen enhancement in Enjoy t ransact ion in FI and M M .
A new BAdI BADI_FDCB_SUBBAS08 has been introduced w ith t his SAP Not e only for GST India specific
requirem ent s. This BAdI is used for subscreen enhancem ent in funct ion group FDCB, basic dat a screen
010 for vendors. This screen is accessed in t he Enjoy t ransact ions for FI docum ent entry or M M invoice
receipt .


Screen 0010 is accessed in 'Basic dat a' t ab in below t ransact ions:


In FI, t ransact ions FB60, FB65, FV60 and FV65.
In M M , transact ion M IRO.


Screen 0510 is accessed in 'Basic dat a' t ab in below t ransact ions:
In FI, t ransact ions FB70, FB75, FV70 and FV75.

Creation of BADI ‘BADI_FDCB_SUBBAS08’ in package ‘FBAS’

1. Go t o transact ion SE18 and select radio but t on 'Enhancement Spot '.
2. Ent er t he Enhancem ent Spot wit h t he name as ‘BADI_FDCB_SUBBAS’ and select change.
3. Select 'Create BADI' but t on.
4. Give nam e as ‘BADI_FDCB_SUBBAS08’ and Short text as " Screen Enhancem ent 8 in FDCB Screen
Basic Dat a".
5. Under usabilit y, select check box for 'Can only be im plemented SAP-int ernally'
6. Under Inst ance Creation M ode, select checkbox for 'Reusing Inst antiat ion'
7. Select 'INTERFACE' under ‘BADI_FDCB_SUBBAS08’ and ent er
'IF_EX_BADI_FDCB_SUBBAS08'

Select creat e object

Select package 'FBAS'

8. Creat e m et hod 'GET_DATA_FROM _SCREEN_OBJECT' w it h level 'Inst ance M et hod' and

descript ion " Transport data from t he class inst ance at t ributes" .
Select Param et ers and enter Paramet er - 'EX_INVFO', TYPE - Export ing, Typing M et hod -
'Type', Associat ed Type - 'INVFO'.
9. Creat e m et hod 'PUT_DATA_TO_SCREEN_OBJECT' wit h level 'Inst ance M et hod' and description
" Transport dat a t o class inst ance at t ribut es".
Select Param et ers and enter Paramet er - 'IM _INVFO', TYPE - Im porting, Typing M et hod - 'Type',
Associat ed Type - 'INVFO'.
10. Save and activat e.

11. Select 'Screen enhancem ent option under t he 'BADI_FDCB_SUBBAS08' and select t he creat e
but t on.
Ent er Calling Program -'SAPLFDCB', Dynpro Number -'0010', Subscreen Area -'SUBBAS08',
Descript ion -'Enhancement 8: Vendor Basic Dat a'.

Ent er Calling Program -'SAPLFDCB', Dynpro Number -'0510', Subscreen Area -'SUBBAS08',
Descript ion -'Enhancement 8: Cust om er Basic Dat a'.
12. Save and activat e.

Page 83 of 97
St ep 3 : Tax Calculat ion based on Vendor region and Vendor GST Classificat ion.
As part of t he SAP solution, t ax calculat ion depends upon vendor region and vendor GST classificat ion.
SAP Note 2426581 w ill pass t hese values in purchase order and invoice verificat ion

St ep 4 : Tax Calculat ion based on Vendor region and Vendor GST Classificat ion.
This SAP Not e cont ains changes relat ed t o sales process (SD) based on draft GST M odel Law. As and when
t he law is finalized, t his SAP Not e might undergo changes.


Sym pt om :
When you creat e GST relevant sales order or invoice, t axes are t o be determ ined based on bill-


t o-part yand plant region.
When you release a GST relevant invoice t o accounting, t he new fields(GST Part ner, HSN/ SAC
Code andPlace of supply) does not updat e t he BSEG t able
Follow t he below m entioned st eps before im plem ent ing t he not e


Creat ion of Function Group J_1IG_GST_IN_SD
Execute transaction code SE80 and select t he drop dow n Opt ion of " Funct ion Group" .
 Provide t he name J_1IG_GST_IN_SD and press Enter. Syst em w ould prom pt for creation. Select


" YES" .
Provide t he Short Text as " SD object s for GST India" .
 Save t he object under t he package " J1I_GST_LO". Act ivate the funct ion group

BADI ‘J1IBADI_INDIA_GST_DETAILS_POST’. Create your own implementation.

M ethods:

REDETERM INE_HSN_SAC_CODE_SD: In t his m et hod user can re-det erm ine HSN/ SAC code based on t heir
business requirem ent.

Below paramet er are passed:

LV_M ATNR

LV_W ERKS

LV_HSN_SAC: Fill t his field w ith value.

REDETERM INE_GSTPART_REG_PRICNG: In t his met hod user can change part ner and region so t hat t axes
(pricing) can be re-det erm ined in billing.

Below paramet er are passed:

FVBRK

FXVBRP

FXVBPA

Page 84 of 97
FVBRP

FTKOM K

Exam ple: Using fxvbpa user can det erm ine part ner and region. The same has t o be filled in FTKOM K in
respective fields

REDETERM INE_GSTPART_REG_ACONTG: In t his m et hod user can change part ner and region so t hat sam e
is considered for post ing int o accounting line (cust om er line w it h part ner and region and m aterial line
w it h HSN/ SAC code) while ding billing.

Below paramet er are passed:

FXVBRP

FXVBPA

FVBRK

FTKOM K

FVBRP

FTKOM P

IT_TAB1

Aft er re-det ermining part ner and region pass t he same int o IT_TAB1 internal t able wit h VBELN,POSNR,
GST_PART & PLC_SUP det ails

Badi for redetermination

1. Run transact ion SE18 and give enhancem ent spot nam e as ‘ J1IENHAN_INDIA_GST_POSTING’
and click on ‘ Create ’ but t on as show n below

Page 85 of 97
2. Now give short t ext as ‘ Enhancement spot for India GST details posting ‘ and uncheck sap
internal use as show n below and click on continue

3. Now click on but t on ‘ Create BADI definition’ as shown below

4. Now give BADI definition name as ‘ J1IBADI_INDIA_GST_DETAILS_POST ‘ and give short text as
‘ BADI definition for gst details posting ‘ and click on continue but t on

5. Now in the below screen select int erface and give int erface name as
“ IF_EX_BADI_INDIA_GST_DETAILS

Page 86 of 97
6. Click on ‘ Save ’ but t on. Save t he object in package ‘ J1I_GST_LO’

7. Now give m et hod nam e as ‘ REDETERM INE_HSN_SAC_CODE_SD’ and give Descript ion
as ‘ Redetermination HSN/ SAC code’

8. Now select met hod and click on parameter but t on and give param ater nam e as below ,
Parameter Type Typing M ethod Associated Type
LV_M ATNR Importing Type M ATNR
LV_WERKS Importing Type WERKS_D
LV_HSN_SAC Changing Type STEUC

Page 87 of 97
9. Sam e w ay add m et hod ‘REDETERM INE_GSTPART_REG_PRICNG’ and add description as
‘ Redetermination GST partner and region for pricing in vf01’
10. Now select met hod and click on parameter but t on and give param ater nam e as below ,

Parameter Type Typing M ethod Associated Type

FVBRK Importing Type VBRKVB
FXVBRP Importing Type VBRPVB_T
FXVBPA Importing Type VA_VBPAVB_T
FVBRP Importing Type VBRPVB
FTKOM K Changing Type KOM K

11. Add met hod ‘ REDETERM INE_GSTPART_REG_ACONTG’ and descript ion

‘ Redetermination GST partner & reg & posting it to accounting’
12. Now select met hod and click on parameter but t on and give param ater nam e as below ,
Parameter Type Typing M ethod Associated Type

FXVBRP Importing Type VBRPVB_T

FXVBPA Importing Type VA_VBPAVB_T
FVBRK Importing Type VBRKVB
FTKOM K Importing Type KOM K
FVBRP Importing Type VBRPVB
FTKOM P Changing Type KOM P
IT_TAB1 Changing Type J_1IG_TT_GST_PART_REG

Page 88 of 97
 13. Now save and act ivat e in package ‘J1I_GST_LO’

Classify SD conditon type

Classify SD condit on t ype as below ,

Condition type Conditon name Short Description

JOCG CGSTAR A/ R CGST

JOIG IGSTAR A/ R IGST

JOSG SGSTAR A/ R SGST

Page 89 of 97
St ep 5 : Line it em wise Tax calculat ion for sales invoices.
Changes related t o sales process (SD) based on draft GST M odel Law. As and w hen t he law is finalized, t his
SAP Not e 2410917 might undergo changes

St ep 6 : GST India - St ock Transafer Scenarios.

As per t he M odel GST draft law , st ock t ransfers across st at es or different regist rations wit hin t he same
st at e are GST relevant transactions. These processes m ust have a GST Invoice.
To avail t he solution need t o im plement t he follow ing st eps.

Set up t he STO process as per t he cust omizings

Configure plant as a vendor

The sending plant in a St ock Transfer process m ust be configured as a Vendor.

• Execute transaction code for Vendor Creat ion/ Change and provide t he Vendor,
Com pany code and Purchasing Org det ails.
• Wit hin t he CONTROL view of t he vendor, m aint ain t he relevant GSTIN for t he
plant w it hin t he Tax Num ber 3 field.

• Wit hin t he PURCHASING DATA view of t he vendor, navigat e t o Extras -> Add.
Purchasing dat a

Page 90 of 97
 • Assign an appropriate plant t o t he vendor and save t he dat a.

Configure Plant as a Cust om er

The receiving plant in a St ock Transfer process m ust be configured as a Cust omer.

 Execute transaction code for Cust omer Creation/ Change and provide t he Cust omer, Com pany
code and Sales area det ails.

 Wit hin t he CONTROL DATA view of t he vendor, m aint ain t he relevant GSTIN for t he plant wit hin
t he Tax Num ber 3 field.

• From SPRO, navigate t o t he following pat h

M at erials M anagement - > Purchasing -> Purchase Order -> Set Up St ock t ransfer ->
Define Shipping dat a for Plant s

Assign t he cust om er num ber and save t he dat a.

Page 91 of 97
Creat e Info record
NOTE: The t ax code m aint ained in t his st ep w ill be referred during t he GST Inbound invoice
Creat ion for post ing GL account s.

• Execute t he transaction code for Info record creation/ change. Provide t he Vendor,
M at erial, Purchasing Org and Plant .
• Check t he Info Cat egory as “ STANDARD” .
• Under t he Purchasing Org dat a view , M aint ain a FI relevant Tax code and save
t he dat a.

New Billing Docum ent Type

A new docum ent t ype t o be creat ed for out bound GST invoice.
• Execute transaction code VOFA.
• Copy docum ent t ype F2 int o ZGST (The document t ype name ZGST is only for reference.
You m ay creat e document w it h any ot her nam e.
• The Billing t ype det ails like “ Docum ent Type” , “ Cancell.Billing Type” , etc can be
configured as per your business needs.

Pricing Procedure for STO Billing

It is recom mended t hat you configure separate pricing procedure for t he new billing
t ype created in st ep 4.

The following screenshot is for illust ration only. SAP will not provide any reference pricing
procedure for GST invoices (relat ed t o STO process).

Page 92 of 97
You can configure t he pricing procedure as per your business needs. The condit ion t ype for base
price (ZSTO in above screenshot) is t o be configured accordingly. This m ay serve as a base for
GST t ax calculations. Ensure t hat you are assigning an appropriat e Account ing Key (ZST in t he
above screenshot) against t he base condit ion t ype. Also, m aint ain suit able G/ L account s for t his
accounting key and not t he sales revenue relat ed account s. The G/ L account s det erm ined via
t his account ing key serve as int ermediate account s for GST invoice post ings.

Copy Control

Set up ‘Delivery t o Billing’ copy cont rol.



Execute transaction code VTFL.
Creat e copy control for t he new Billing t ype(ZGST) created in previous st ep, by copying
t he exist ing copy cont rol sett ing of t he Billing t ype ‘F2’ and delivery ‘LF’ .

NOTE: In case you are using a different docum ent t ype t han LF for Out bound deliveries w.r.t STO
process, t hen t he Copy Cont rols m ust be set accordingly.

 Save t he set t ings.

Steps for Creating PF Status J_1IG_STO_STAT



Execute transaction code SE41.


Provide t he program name as “ SAPLKKBL” and St at us ‘STANDARD’.


Select t he Copy St at us from t he applicat ion t oolbar.
Provide t he To program nam e ‘J_1IG_INB_INV_STO’ and st at us ‘J_1IG_STO_STAT’

Page 93 of 97
 Delete t he follow ing highlight ed element s

 Creat e a new function code (& GST) and provide t he det ails as show n in t he follow ing screenshot.

Page 94 of 97
  Save and activat e

Creation of Tcode J_1IG_INV



Execute transaction code SE93
Provide t he t ransaction code ‘J_1IG_INV’ and select Create. ฀ Provide the short text ‘Create GST


Inb. Inv. for STO Process’


Select t he radio but t on for ‘Program and Select ion screen (report t ransaction)


Select all the checkboxes wit hin t he GUI Support box.
Provide t he program name J_1IG_INB_INV_STO.

Page 95 of 97
  Save t he t code under package ‘J1I_GST_LO’

Selection Texts



Execute transaction code SE38. Provide t he program name ‘J_1IG_INB_INV_STO’.
Select t he radiobut t on for ‘Text Elem ent s’ and choose ‘Change’

Page 96 of 97
  Select t he t ab ‘Select ion Text s’ and updat e t he following

 Save and activat e

Process Overview – Stock Transfer

1. Creat e St ock transfer order.

2. Creat e Out bound delivery document and Issue t he goods.
3. Creat e GST Out bound invoice.
4. Post Goods receipt.
5. Creat e GST inbound invoice docum ent via transact ion code 'J_1IG_INV'

Page 97 of 97