excise opening balance - aug 2004

8/2/2019 Excise Opening Balance - Aug 2004

http://slidepdf.com/reader/full/excise-opening-balance-aug-2004 1/14

V1.470

Aug 2004

English

Excise Opening Balance

Uploading

SAP AGNeurottstr. 1669190 Walldorf Germany

Business Process Procedure



SAP Best Practices Excise Opening Balance Uploading: BPP

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix aretrademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanyingsuch products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 14




Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, programnames, transaction codes, table names, and individual key words of aprogramming language, when surrounded by body text, for example,SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.

© SAP AG of 14




Abbreviations

R Required entry field

(used in the end-user procedures)

O Optional entry field


C Conditional field


© SAP AG of 14




Contents

Excise Opening Balance Uploading .....................................................................................................6

RG23A Part II and PLA Registers updation .......................................................................... .........8

RG23C Part II ........................................................................................................................... .. 11

RG23C On Hold ...................................................................................................................... .... 13

© SAP AG of 14




Excise Opening Balance UploadingThis Business Process Procedure is also included in Building Block J94. But due to the change of tax

settings, we should use this BPP instead of the original one in J94.

RG23A and RG23C Part I Registers updation

Use

Before going live of any project normally you will be uploading initial stocks by using 561 movementsin SAP system. In Indian business scenario if the said material is subject to excise duty then we needto update Part 1 register with the stock.

Using this activity, you can update the receipts of into RG23A Part I and RG23C Part I,Registers by select the radio button option.

Prerequisites

Initial stocks must have been uploaded into system by 561movement and for such materials all CINdetails (J1ID) like Chapter ID, Material and Chapter ID combination and CENVAT Determinationshould have been maintained.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP R/3 menu Country India User Menu → Indirect Taxes→ Registers → Excise

Tax → Update RG23A/C Issues and RG1

Transaction code J1I5

2. On the Update of Registers RG1 and RG23(Part1) screen, make the following entries:

Field name Description R/O/C User actionandvalues

Comment

CompanyCode

Company Code R BP01

Plant Plant – for which RG1Register is being maintained

R BP01

Excise Group Excise Group for which RG1register is being maintained

R 10

Material Material document number O <enter the 561 Movement Material

© SAP AG of 14




DocumentNumber

materialdocumentnumber>

document number

Document

Year

Material document year O Material document year

Posting Date Date of Material documentPosted

R Enter theMaterialDocumentPostingDate

MovementType

Movement Type used for posting the materials

O 561

StorageLocation

Storage location used for posting the materialmovements

O

Material Material number to update theRG1 Register O

DocumentDate

Document date of the materialdocument

O

Batch Batch number of the materials O

Stock Type Stock Type declared O

Rule Excise Classification Rule O

Classification Pre-defined Classifications R ROP ReceiptsROP-Receipt from outsideunder any other provision

RG23/ RG1 RG23 / RG1 updation date R Select theappropriate radiobutton toupdate theRegister.Pleaseselect thedocumententry dateradiobutton

Date to be considered bythe system for updation of Register

Document Entry date

Document posting date

System date

Registers Register to update R Select the

RG23A or RG23Cradiobuttons

Choose any one of

RG23A Part1

RG23C Pat1

For this transaction

Please choose enter and ignore any messages.

© SAP AG of 14




3. System will display the ‘Update of Registers RG1 and RG23 (Part1’) screen:

Displays all the line items to meet the selection criteria to update the Register.

4. Select the line items which needs to be updated to Register by selecting the check box at the

beginning of the each line item

5. Simulate the selection by using theSimulate function or use Shift+F10 to simulate the selection

6. System will display the selection Green or Red Traffic lights. The line items which can be updatedwill be displayed with Green Traffic Lights and the line items which can not be updated will bedisplayed with Red Traffic Lights.

7. After selecting the right documents select the line item and choose the Register Entry button toupdate the Register or use Ctrl+Shit+F11 to make register entry.

Please perform step 7 only once, because if you perform two or three times, the system willgenerate two or three times in register which may not required.

8. To see the changes you need to extract the respective register by transaction code J2I5 and printutility program by transaction code J2I6 as per the BPP mentioned above.

RG23A Part II and PLA Registers updation

UseBefore going live of any project normally you will be uploading initial balances by using FI transactionsin SAP system. By the time client go-live there might be some opening balance in RG23A Part II andPLA registers.

Using this activity, you can update the receipts of into RG23A Part II and PLA Registers byselect the respective register button option.

This transaction involves Direct Table Entries so, please be careful when you are doing this

transaction. You have to do this activity before Extracting (J2I5) transaction i.e. there shouldnot be any entries in J_2IACCBAL table. If they are exists you can delete them and make thefollowing transaction and then Extract (J2I5) again.

Please do note that this is purely manual transaction system does not have any control or validations in this i.e. system will cross check with any other entry.

© SAP AG of 14




Prerequisites

All CIN customization must have completed.

Procedure


SAP R/3 menu Tools → ABAP Workbench→ Development → ABAP Dictionary

Transaction code SE11

2. On the ABAP Directory: Initial Screen, make the following entries.

3. Choose J_2IACCBAL against Database Table filed and choose Display (F7) icon to enter intotable.

4. On Dictionary: Display Table screen, choose Utilities→Table contents→Create Entries from

Menu bar and make the following entries:

Field name Description R/O/C User action andvalues

Comment

MANDT Client O Leave it blank Grayed out by system, syswill give client number.

EXGRP Excise Group O 10 Choose appropriate excisegroup

REGISTER Data element for Register n

O RG23ABED for RG23A BEDregister

You can choose theappropriate register listedat the bottom.

DATUM Date O <Enter month enddate>

30.04.2004

For example if you aregoing live from 01.01.2004,then you must enter thelast day of previous monthi.e. 31.12. 2003. When youextract register the daterange should be from01.01.2004 to 31.01.2004.

WERKS Plant O Leave it blank

OP BAL Basic duty (OP BAL) O Leave it blank

CL BAL Basic duty (CL BAL) O 9999.99

for example INR

Enter the closing balanceas on 31.12.2003

EXAMT Basic duty (EXAMT) O Leave it blank

EXIND Extract Indicator O Leave it blank

USNAM User name O Enter you user ID

CPUDT Entry Date O Entry date

31.12.2003

Date on which you aremaking entry

© SAP AG of 14




CPUTM Entry time O Enter time

The following are Data elements for Registers:

RG23ABED, RG23ASED, RG23AAED, RG23CBED, RG23CSED, RG23CAED, PLABED, PLASED,PLAAED, PLACESS.

5. After making table entries save the entries by choosingSave icon or Ctrl + S.

Please do remember that this is only a direct table entry of opening balance, system does notcheck the actual FI entries. You need to make an appropriate FI entry to suitable to abovetransaction. An example is give below for your reference:

You can use F-02 transaction code to pass the following FI entry:

RG23A Part II Account DR

To Initial balances clearing a/c

Or

PLA BED Account DR


You can choose any appropriate accounting entry which is suitable to client.

6. After making table entry if you want to see you can extract register by using J2I5 transaction code(as explained 1.2.1 and 1.2.2). But you need to remember the extraction date should be01.01.2004 to 31.01.2004 as you have given closing balance as on 31.12.2003.

7. Extraction is possible only if there are some transactions (actual incoming excise invoices). Thatis to say you can extract register only after your first actual CIN transaction in system (other thanopening balance).

The same process can be followed for PLA register also.

Result

Table entry for RG23A Part II is made.

© SAP AG of 14




RG23C Part II

Use

To upload the opening balance in RG23C Part II.

This transaction involves Direct Table Entries so, please be careful when you are doing thistransaction. You have to do this activity before Extracting (J2I5) transaction i.e. there shouldnot be any entries in J_2IACCBAL table, except the balances of RG23A Part II and PLAbalance as mentioned above. If they are exists you can delete them and make the followingtransaction and then Extract (J2I5) again.

Please do note that this is purely manual transaction system does not have any control or validations in this i.e. system will cross check with any other entry.

The RG23C is for CENVAT credit on capital goods. Hence in this step you upload only thebalance in the RG23C Part II. The RG23C balance on hold will not be uploaded in the table.The balance will remain in the FI books as a balance in a GL account. When this credit for the‘On hold’ balance is due, it will be transferred to RG23C Part II using Excise JV (transactioncode J1IH).

Prerequisites

All CIN customization must have completed.

Procedure

1. Access the transaction choosing one of the following navigation options:SAP R/3 menu Tools → ABAP Workbench→ Development → ABAP Dictionary

Transaction code SE11

2. On the ABAP Directory: Initial Screen, make the following entries.

3. Choose J_2IACCBAL against Database Table filed and choose Display (F7) icon to enter intotable.

4. On Dictionary: Display Table screen, choose Utilities→Table contents→Create Entries fromMenu bar and make the following entries:

Field name Description R/O/C User action andvalues

Comment

MANDT Client O Leave it blank Grayed out by system, syswill give client number.

EXGRP Excise Group O 10 Choose appropriate excisegroup

REGISTER Data element for Register n

O RG23CBED for RG23C BED

You can choose theappropriate register listed

© SAP AG of 14




register at the bottom.

DATUM Date O <Enter month enddate>

30.04.2004

For example if you aregoing live from 01.01.2004,then you must enter the

last day of previous monthi.e. 31.12. 2003. When youextract register the daterange should be from01.01.2004 to 31.01.2004.

WERKS Plant O Leave it blank

OP BAL Basic duty (OP BAL) O Leave it blank

CL BAL Basic duty (CL BAL) O 9999.99

for example INR

Enter the closing balanceas on 31.12.2003

EXAMT Basic duty (EXAMT) O Leave it blank

EXIND Extract Indicator O Leave it blankUSNAM User name O Enter you user ID

CPUDT Entry Date O Entry date

31.12.2003

Date on which you aremaking entry

CPUTM Entry time O Enter time

The following are Data elements for Registers is available for RG23C Part II.

RG23CBED, RG23CSED, RG23CAED.

5. After making table entries save the entries by choosingSave icon or Ctrl + S.

Please do remember that this is only a direct table entry of opening balance, system does notcheck the actual FI entries. You need to make an appropriate FI entry to suitable to abovetransaction. An example is give below for your reference:

You can use F-02 transaction code to pass the following FI entry:

RG23C Part II Account DR


You can choose any appropriate accounting entry which is suitable to client.

6. After making table entry if you want to see you can extract register by using J2I5 transaction code(as explained 1.2.1 and 1.2.2). But you need to remember the extraction date should be01.01.2004 to 31.01.2004 as you have given closing balance as on 31.12.2003.

© SAP AG of 14




7. Extraction is possible only if there are some transactions (actual incoming excise invoices). Thatis to say you can extract register only after your first actual CIN transaction in system (other thanopening balance).

The same process can be followed for PLA register also.

Result

Table entry for RG23C Part II is made.

RG23C On Hold

Use

When capital purchases are made which are eligible for CENVAT, RG23C(Part II) will be credited withonly 50% of the CENVAT. The balance 50% will be CENVAT on Hold.

The CENVAT on hold opening balance is not to be uploaded into Excise Register. It will remain as abalance in GL A/c for CENVAT on hold (Account No. 24930000 in chart of Accounts CAIN).

In the new year when the credit for the CENVAT on hold is due the credit is taken using excise JV.The procedure for this is as follows, assuming CENVAT on Hold credit to be taken into RG23C (BED)is to be taken for Rs. 100.00

Procedure


SAP R/3 Menu Indirect Taxes →Excise JV →Create

Transaction code J1IH

2. On the Excise JV – Main Menu screen choose Additional Excise.

3. On the Create Excise JV – Initial Screen (Diff Excise Posting) screen make the following entries:

Field name Description User action andvalues

Comment

Document Number A Enter any dummy entry

Document year Current year Example 2004

Company Code BP01

Plant BP01

© SAP AG of 14




Excise group 10

Sub-transaction OH

Modvat AccountSelection

RG23C

4. Choose Enter to continue.

5. On the Create Excise JV – Details wrt to exc inv A 2004 for diff exc post Screen make thefollowing entries:

Field name Description User action andvalues

Comment

Document Date Today’s date

Posting date Date on which toPost

BED Amount 200.00 Enter twice the amount of credit to be taken

6. Choose Determine GL accounts.

System determines the GL accounts automatically in the dialog boxExcise JV – G/L Account Determination. No changes to be made. ChooseEnter .

7. Choose Save or Crtl+S.

Result

System issues a message successfully created with reference of the documents created. Following Accounting entry is pass

Itm PK AccountAccount shorttext Assignment Tax code Amount

1 50 24930000CENVAT hold V0 -200

2 40 24930000CENVAT hold V0 100

3 40 24850000CENVAT CapBED 20040603V0 100

RG23C (Part II) is credited for Rs. 100.00

© SAP AG of 14

excise opening balance - aug 2004

Documents