Hyd It High Level Design Template

Document Number:

TCS-XYZ-SDD-VAT-PH1-1.0

Copy Number: 1.0

XXX

ASDFGH, Hyderabad

Name of the Project

Software Design Document for Registration - Ver 1.0

December **th, 200*

This is a controlled document. Unauthorised access, copying, replication and usage for a purpose other than for which this is intended are prohibited.

Commercial Taxes Department, Govt of AP. – XYZ SDD - Version 1.0

PF3020

DOCUMENT RELEASE NOTICE

Notice No.Client XXXProject XYZ full formDocument details

System Design Document for Registration module

Name Version No.

Description

SDD for Registration module 1.0 Base Version

Revision details:Action taken (add/del/chg)

Precedingpage No.

Newpage No.

Revisiondescription

Change Register serial numbers covered:The documents or revised pages are subject to document control.Please keep them up-to-date using the release notices from the distributor of the document.These are confidential documents. Unauthorised access or copying is prohibited.

Approved by : PL/ML /LQC Date: 21st Dec 2001

Authorised by:GL/PL Date: 24th Dec 2001

ii


PF2060C

DOCUMENT REVISION LIST

Client NameProject NameDocument Name SDD For XXXXRelease Notice Reference (for release)

Rev.No.

Revisiondate

Revisiondescription

PageNo.

Prevpage

Actiontaken

Addenda/New page

ReleaseNotice reference

Page iii


CONTENTS

1 INTRODUCTION ...................................................................................................................... 1

1.1 BACKGROUND.......................................................................................................................11.2 PURPOSE................................................................................................................................11.3 SCOPE....................................................................................................................................11.4 DEFINITIONS.........................................................................................................................11.5 PROJECT REFERENCES.........................................................................................................21.6 ORGANISATION OF THE DOCUMENT...................................................................................2

2 SYSTEM DESCRIPTION ........................................................................................................ 4

2.1 PROJECT FUNCTIONS...........................................................................................................42.1.1 LIST OF FUNCTIONS.........................................................................................................42.2 USER CATEGORIES...............................................................................................................42.3 DESIGN OBJECTIVES............................................................................................................42.4 SYSTEM ARCHITECTURE......................................................................................................52.5 TECHNICAL ARCHITECTURE................................................................................................62.6 DEVELOPMENT METHODOLOGY.........................................................................................62.6.1 THREE-TIER APPLICATIONS..............................................................................................62.6.2 BUSINESS COMPONENTS..................................................................................................62.6.3 DEVELOPMENT AND DEPLOYMENT..................................................................................72.7 HARDWARE ENVIRONMENT.................................................................................................72.8 SOFTWARE ENVIRONMENT..................................................................................................82.9 NETWORK ENVIRONMENT...................................................................................................82.10 DESIGN CONSTRAINTS........................................................................................................82.11 ASSUMPTIONS AND DEPENDENCIES...................................................................................9

3 BUSINESS FUNCTIONS ........................................................................................................ 11

3.1 REGISTRATION....................................................................................................................113.1.1 SCREENS........................................................................................................................113.1.2 REPORTS........................................................................................................................113.1.3 PROCESS CONTROL OBJECTS /WEB BEANS...................................................................113.1.4 BUSINESS COMPONENTS / APPLICATION MODULES, VIEWS & ENTITIES......................123.1.5 PACKAGES.....................................................................................................................13

4 SCREENS ................................................................................................................................. 14

4.1 SCRACK.............................................................................................................................144.2 SCRREGENTRY..................................................................................................................154.3 SCRVAT100........................................................................................................................17

Page iv


4.4 SCRVAT100A....................................................................................................................254.5 SCRVAT100B....................................................................................................................284.6 SCRLSTREGPROC..............................................................................................................304.7 SCRVAT104.......................................................................................................................324.8 SCRCST.............................................................................................................................344.9 SCRTOT001.......................................................................................................................394.10 SCRVAT112.....................................................................................................................444.11 SCRVAT121.....................................................................................................................494.12 SCRTOT014.....................................................................................................................534.13 SCRCNCLBYDPT..........................................................................................................574.14 SCRNOTICE......................................................................................................................594.15 SCRREGREP...................................................................................................................60

APPENDIX - A .............................................................................................................................. 63

APPENDIX - B .............................................................................................................................. 65

APPENDIX - C .............................................................................................................................. 66

APPENDIX - D .............................................................................................................................. 67

Total Number of Pages -77

Page v

Name of the Project SDD - Version 1.0

1 INTRODUCTION

1.1 BACKGROUND

TCS submitted Software Requirements Specifications (SRS) of XXX on November 12, 2001, and subsequently, YYY provided feedback on the SRS. The current Software Desing Document (SDD) is based on the SRS document and subsequent feedback from XXX.

1.2 PURPOSE

This SDD for the XXX application has been prepared to provide a development framework and primarily intended for TCS consultants working on the development and also for XXX, to provide an overview of TCS’s development perspective.

This document defines the overall system specification in terms of user interface, processes, dataflows, and internal and external linkage to the registration module.

1.3 SCOPE

The scope of the project involves detailed Analysis, Design and Development of computer based application for Xxx, Government Of Andhra Pradesh, Hyderabad.

The design phase consists of the following stages:

1. Database design, Screen design, Report painting.2. Preparation of SDD based on the functions specified in SRS3. Review of SDD.

1.4 DEFINITIONS

Table 1-1 List of Abbreviations

Abbreviations RepresentsAC Assistant CommissionerACTO Assistant Commercial Tax OfficerADC Appellate Deputy Commissioners ADLC Additional CommissionerADT AuditAPGST Andhra Pradesh General Sales TaxAPL AppealsASS AssessmentsAT Appellate Tribunal CA Civil AppealCIS Central Information SystemCom CommissionerCPR Challan Posting RegisterCST Central Sales TaxXXX XxxCTO Commercial Tax OfficerDAC Dealer AccountingDC Deputy CommissionerDCB Demand Collection & BalanceDCTO Deputy Commercial Tax OfficerDEO Data Entry OperatorDIS Divisional Information SystemDPC Data Processing ClerkFIS Field level Information SystemGIS Goods Information SystemHC High CourtI Insert

Page 1 of 77


INS InspectionsINV InvestigationsJC Joint CommissionerLTU Large Taxpayers UnitMIS Management Information SystemNoD Notice of DecisionQ QueryRC Registration CertificateREG RegistrationRTN ReturnsSC Supreme CourtSDD System Design DocumentSLP Special Leave PetitionSRS Software Requirements SpecificationTOT Turnover TaxU UpdateVAST Value Added Sales TaxXYZ XYZ full formVAT Value Added TaxWP Writ Petition

1.5 PROJECT REFERENCESTable 1-2 Project References

No. Document Author Version

1. Registration – SRS TCS 1.02. XXX Feedback summarised and communicated to

XXX on 27 November 2001TCS 27.11.01

3. TCS QMS documents TCS Current

1.6 ORGANISATION OF THE DOCUMENT

The chapters and their contents are given in the following table

Chapter Name Content Description1 Introduction This Chapter itself2 System

DescriptionProject Functions List of FunctionsUser CategoriesDesign ObjectivesSystem ArchitectureTechnical ArchitectureDevelopment MethodologyThree-tier applicationsBusiness componentsDevelopment and deploymentHardware EnvironmentSoftware EnvironmentNetwork EnvironmentDesign ConstraintsAssumptions and Dependencies

3 Business Functions RegistrationScreensReportsProcess Control Objects /Web BeansBusiness Components / Application Modules, Views & Entities

4 Screens Navigation details Process StepsDescriptionTables referredPackages (PLSQL procedures)Beans referred

Page 2 of 77


Business Object

Page 3 of 77


2 SYSTEM DESCRIPTION

2.1 PROJECT FUNCTIONS

2.1.1 List of Functions

The different functions of the Registration module are:- Identification of dealers for compulsory VAT/TOT registration system- Pre-Registration activity for VAT system (for identified list of dealers and

suspected dealers through intelligence reports)- Registering dealers (start-up, Voluntary, VAT, TOT etc)- Changes in Registration details- Cancellation of Registration

2.2 USER CATEGORIES

The users of the System can be categorised as:

Internal Users:

Head OfficeDivisional OfficeCircle OfficeCheck PostsAppellate Tribunals

External Users:

Dealers via internet Service centersBanks

2.3 DESIGN OBJECTIVES

The quality policy of the system states that the system should be delivered to meet XYZ needs. These needs, as summarised in this document, will form the basis for further design.

For different categories of users, major objective will be to implement the System and utilise it for their day-to-day operations.

The proposed system will provide XYZ with the following benefits:

All Divisions, Circles will have easy access to information. Data inaccuracies will not occur (single point data) Faster retrieval of information Reduction in manual effort in terms of

Information maintenance

Reports generation

The system has been designed to achieve the following objectives :

- to provide efficient and quicker service to all users.

- to provide controlled access to sensitive data.

- to provide flexibility to accommodate future needs.

- to eliminate duplication of work.

Page 4 of 77


- to provide complete management control.

- to design the system in line with SRS.

- to provide a convenient and an effective information system.

- to provide decision support system for the management.

2.4 SYSTEM ARCHITECTURE

The application architecture diagram is given below as per our Technical Proposal:

The salient features of the application architecture are as follows:

a. The functions are independently distributed across the Application servers distributed across the circles, divisions and head quarters.

b. This architecture will allow independent functioning of field offices without any interaction with the central servers in a real-time mode.

c. The synchronization of the databases will be done on a daily basis for shared and appeal database and on a weekly basis for the master databases (the updates to the masters is expected to be infrequent as some of them may be due to only the policy changes in the Government).

d. The security is at the application server and the data server level.e. The business logic is split across the application and the data layer allowing a 4

tiered architecture provided advanced security and better performance for some of the crucial transactions. Since, some Business Logic is stored in the data layer for retrieval of data and query processing, thus we assume a 4th layer is introduced in the architecture.

f. The infrastructure architectural components like audit trail, report generating, synchronization programs and the print services will be configurable for each of the locations.

g. The system will work under a well-defined security domain and provide auditing of important data . The output of the system will consist of numerous reports providing the information as per the client’s requirements in each of the aforesaid areas.

Page 5 of 77

MastersShared

DB

SpecificFIS DB

AppealsDB

MastersShared

DB

SpecificDIS DB

AppealsDB

MastersShared

DB

SpecificCIS DB

AppealsDB

Business Logic (FIS)

Security

Business Logic (DIS)

Security

Business Logic (CIS)

Security

Regn. Process

TOT Approval

ReturnsProcess

REPORTS PRINT SERVICES

SYNC LOGAUDIT TRAIL

PaymentAppealsProcess

Inspection&

Assessments

Security

Regn. Approval

AuditProcess

VigilanceProcess


SYNC LOGAUDIT TRAIL

PaymentInspection

& Assessments

Security

InternetRegn. &Approval

AppealsMgmt

MISCReporting


SYNC LOGAUDIT TRAIL

InternetPayment

GoodsTracking

Security

User Desktop (Circle)Browser Based

User Desktop (Division)Browser Based

User Desktop (HQ)Browser Based

Dat

a L

ayer

App

licat

ion

Lay

erPr

esen

tatio

n L

ayer Circle Division HQ


2.5 TECHNICAL ARCHITECTURE

Following picture depicts the 3-tier architecture, which will be used for this project. Browser which uses Java and HTML forms the front-end of this application. Oracle 9I Application Server which includes the web server forms the middle layer and Oracle 9I Database server is used for the data layer.

2.6 DEVELOPMENT METHODOLOGY

Business Components for Java is a programming framework, implemented in Java and XML, that enables productive development, deployment, and flexible customization of multi-tier, database-savvy applications from reusable business components.

2.6.1 Three-tier applications

Business Components for Java helps creating three-tier applications that are made of clients, a business logic tier containing the business logic and database views, and a database server containing tables with the data the application uses.

Business Components for Java wizards and editors are used to build the business logic tier based on software requirements specifications; that can create both Java and JSP clients using the JDeveloper development environment; Oracle 9i provides the database server.

Because business rules, views, and custom code are stored in a separate tier, clients can be "thin" so they are easier to install and maintain: changes in the business logic tier often require no modification to the clients that use it.

2.6.2 Business components

The framework defines these business components that are used in the applications: application module view object entity object view link association domain

A business component is implemented as an XML metadata file and possibly one or more Java files. Information that is descriptive in nature is stored as XML while programmatic information is in Java.

The business logic tier is made of one or more application modules that contain view objects, representing views of data and optionally including calculations. View objects

Page 6 of 77


can use entity objects, representing business entities and mapping to database tables, to enforce business logic.

View links represent master-detail relationships between view objects and are also contained in an application module; associations represent bidirectional relationships between entity objects.

These modular components are easy to customize, maintain, and reuse in other applications. The component-based framework handles many repetitive coding tasks, such as master-detail coordination, locking, and transaction management, including changes in the business logic tier’s data cache and posting changes to the database.

2.6.3 Development and deployment

By using the Business Components for Java design-time wizards and editors, business logic tiers are built by defining the characteristics of components: their attributes, relationships, and business rules. Business Components for Java generates Java source code and XML metadata to implement the behavior that is specified. Because the code inherits from a framework, the Java source files are concise and do not contain large amounts of generated code. It is planned to use JDeveloper to add the Java code to enhance or change the behavior, and easily test the application services, independently of the deployment platform.

The following diagram shows the deployment configurations that can be used. A horizontal line indicates that the tiers are in the same process; a diagonal line indicates tiers that are in different processes. For example, the top line shows that the User Interface tier and the Business Logic tier are in the same process on a client, while the Application Data tier is in a separate database process; this is a physical two-tier deployment configuration.

2.7 HARDWARE ENVIRONMENT

Following is the location specific hardware configuration :

Head Office : RISC Unix Server as Database Server in a cluster (Rack Server)- 2No. INTEL NT Server as Back-up Server (Rack Server)- 1No.

Local Servers : RISC Unix Server as Application Server (Rack Server)- 1No.

Personal Computers – PIV Model

Processor Intel Pentium IV @ 1.5 GhzMemory 128 MB SDRAM expandable through 3

DIMM socketsHard Drives 40 GB HDD with ATA 100 interface

Page 7 of 77


For details of the Hardware & Network environment refer to the Hardware & Networking SRS documents Version 1.0.

2.8 SOFTWARE ENVIRONMENT

Following is the location specific software environment :

Head Office : Oracle 9i Application Server Enterprise Edition on IBM RS6000- AIX platform

Oracle 9I DataBase Enterprise Edition on IBM RS6000 – AIX Platform

Oracle Real Application Cluster on IBM RS6000 – AIX PLatform

Local Servers : Oracle 9I Application Server Standard Edition on Windows NT Platform

Oracle 9I DataBase Standard Edition on Windows NT platform

End User Terminals : Browsers (Internet Explorer 5.0 and above/ Netscape Navigator 4.5 and above)

2.9 NETWORK ENVIRONMENT

Keeping in view the geographical spread and locations of various offices and their distances from nearest DNC the following Network Architecture is considered for the Application. However, the Application is independent of the network architecture that is finally implemented.

All the divisional offices with their circle offices are consolidated into 3 to 4 locations and are connected to the head offices with 2 Mbps/64 Kbps leased line with ISDN dial backup facility. These buidlings would inturn have LAN environment within the buildings and would be using common resources like servers and associated equipment. All these offices would be connected to the head office router. The intranet traffic from various divisional and circle offices through APSWAN would be routed through 2 central routers in HSRP mode (Hot Standby Routing Protocol). This would facilitate no single point of failure, ie. in case of failure of one of the routers, the other router would take the load and provide the connectivity. These routers are connected to SNC in Hyderabad using 2 links of dedicated 2 Mbps lines for redundancy.

The connectivity of various Circle offices, Division offices & Head Office has been discussed in the Hardware & Networking SRS document.

2.10 DESIGN CONSTRAINTS

The following design constraints have been identified for this application :

- Data synchronisation between various servers is dependent on availability of the 2 mbps/64 kbps link between the Head Office and the Division/Circle Office Servers.

- Some of the forms and report formats for some functionality of VAT & TOT are yet to be finalized by the department.

- All inserts and updates to any record in any table are marked by the system to contain the user-id and timestamp of the insert or update. However, an history of this record is not maintained by the system to improve response time and reduce disk space requirements. Additional auditing as per SRS requirements is however maintained by the system.

- Design is based on the AP Vat Act and Rules, and flexibility of the system design, is as per the flexibility of the APVAT Act and Rules.

Page 8 of 77


- Audit trail is required for all the transactions in the system, and this will be maintained by standard audit trial features of Oracle Database.

2.11 ASSUMPTIONS AND DEPENDENCIES

XYZ SRS - Final.doc (delivered to XXX on 12th November 2001) document was used as basis for the design, and that version was assumed as final

The VAT draft legislation will need to be passed by the AP State Legislature and become an Act prior to system implementation.

VAT Rules as given have been taken as final for the purpose of this application. Any change in these will affect the system. Prior to implementation, all relevant past data that is required by the system will need to be identified and migrated. Andhra Pradesh Value Added Sales Tax Act - 25th September 2001 and Andhra Pradesh Value Added Sales Tax Rules - 25th September 2001 draft copies were considered for this document.

The efficacy of the system will depend on the efficacy of some of the systems that it interfaces with. Any problem with data integrity in the host system will reflect in data integrity problems in this application also.

Risks

If there is no timely feedback on design from XXX, it will have an impact on the development of the system and slippage of schedules.

Non-availability of Network connectivity, such period may result in the use of the application system as a stand-alone system.

Unavailability of existing data in prescribed format may cause delay in migrating the data and Registering the existing dealers in the new VAT scenario.

Page 9 of 77


3 BUSINESS FUNCTIONS

3.1 REGISTRATION

This chapter lists the screens, reports, process control objects, business objects that will be used as part of the registration module.

3.1.1 Screens

S.No

Screen Name Description

1. ScrNotice Notices Screen

2. ScrAck Acknowledgement Screen

3. scrVAT100 VAT Registration Screen4. scrVAT100A Branch/Place of Business Address Screen5. scrVAT100B Partner Details Screen6. scrVAT104 Start up Registration Screen7. scrTOT001 TOT registration Screen8. scrTOT014 TOT Cancellation Screen9. scrCnclByDept Dealer Department Cancellation Screen10. scrCST CST Registration Screen11. scrRegRep Registration Reports Screen12. scrVAT112 Changes in Registration Details Screen13. scrVAT121 VAT Cancellation Screen14. scrRegEntry List of Acknowledgements for which data entry has

to be done15. scrLstRegProc List of Acknowledgements that are tobe

processed/Registered

3.1.2 Reports

No. Report Name Description1. RepPreVatDlr List of Identified VAT Dealers2. RepPreTotDlr List of Identified Tot dealers3. RepLstNewReg List of New Registrations in a month4. RepLstCmdtyDlrs List of Comodity wise (Liqour etc.) Dealers5. RepLstBsnsType List of Business type

dealers(Manufacturers/Importers/Exporters etc.)6. RepLstTaxInc List of Dealers having Tax Incentives7. RepLstChng List of dealers applied for changes8. RepLstDlrTypes List of dealers of different types(VAT to TOT/TOT to

VAT/CST/VAT/TOT/Forced VAT/Forced Cncl/Forced TOT/Cncl)

9. RepDlrDetails Dealer Details

3.1.3 Process Control Objects /Web Beans

No. Web Bean Name Methods Application Module1. VAT100WB InsRow()

QryRow()UpdRow()

VAT100AppMod

2. VAT100AWB InsRow()QryRow()

VAT100AAppMod

3. VAT100BWB InsRow()QryRow()

VAT100BAppMod

4. VAT104WB InsRow() VAT104AppMod5. TOT001WB InsRow()

QryRow()TOT001AppMod

Page 10 of 77


No. Web Bean Name Methods Application ModuleUpdRow()

6. CSTWB InsRow()QryRow()UpdRow()

CSTAppMod

7. VAT112WB UpdRow() VAT112AppMod8. TOT014WB InsRow()

UpdRow()TOT014AppMod

9. VAT121WB InsRow()UpdRow()

VAT121AppMod

10. DeptCnclWB InsRow()UpdRow()

DeptCnclAppMod

11. LstRegEntryWB QryRow() LstRegEntryAppMod12. LstRegProcWB QryRow() LstRegProcAppMod13. NoticeWB InsRow() NoticeAppMod14. AckWB InsRow() AckAppMod

3.1.4 Business Components / Application Modules, Views & Entities

No. Application Module Name

Method Name View Object Entity Name

1. VAT100AppMod AddRow(Row)VatEligibility()GenTIN()ChkPAN()

InsVAT100View Dealer_MasterDlr_BankDlr_Acty_DtlsDlr_Cmdty_linkDlr_Brnch_DtlsDlr_Prtnr_DetlsTin_Master

SelectRow(Row) QryVAT100View Lookup_CodesCommodity_Master

UpdRow(Row) UpdVAT100View Alert_Log

2. VAT100AAppMod AddRow(row) InsVAT100AView Dlr_Brnch_DtlsSelectRow(Row) QryVAT100AView Lookup_Codes

3. VAT100BAppMod AddRow(row) InsVAT100BView Dlr_prtnr_DtlsPhoto_Master

SelectRow(Row) QryVAT100BView Lookup_Codes4. TOT001AppMod AddRow(Row)

TOTEligibility()GenGRN()

InsTOT001View Dealer_MasterDlr_BankDlr_Acty_DtlsDlr_Cmdty_linkDlr_Brnch_DtlsDlr_Prtnr_DetlsGrn_Master

SelectRow(Row) QryTOT001View Lookup_CodesCommodity_Master

UpdRow(Row) UpdTOT001View Alert_Log5. CSTAppMod AddRow(Row)

CSTEligibility()GenCST()

InsCSTView Dealer_MasterDlr_BankDlr_Acty_DtlsDlr_Cmdty_linkDlr_Brnch_DtlsDlr_Prtnr_DetlsCST_Master

SelectRow() QryCSTview Lookup_CodesCommodity_Master

UpdateRow(Row) UpdCSTView Alert_Log6. VAT112AppMod UpdateRow(Row)

ValidTime()UpdVAT112View Dealer_Master

Dlr_BankDlr_Acty_DtlsDlr_Cmdty_link

Page 11 of 77


No. Application Module Name

Method Name View Object Entity Name

Dlr_Brnch_DtlsDlr_Prtnr_DetlsAlert_Log

7. VAT121AppMod AddRow(Row)ChkReturn()ChkRefund()ChkArrear()

InsVAT121View Dlr_Cncl_Dtls

UpdateRow(Row) UpdVAT121View Dealer_MasterAlert_Log

8. TOT014AppMod AddRow(Row)ChkReturn()ChkRefund()ChkArrear()

InsTOT014View Dlr_Cncl_Dtls

9. DeptCnclAppMod AddRow(Row)ChkReturn()ChkRefund()ChkArrear()

InsDeptCnclView Dlr_Cncl_Dtls

UpdRow() UpdDeptCnclView

Dealer_Master

10. LstRegEntryAppMod

SelectRow() QryLstRegEntryView

Ack_MasterDealer_Master

11. LstRegProcAppMod

SelectRow() QryLstRegProcView

Dealer_Master

12. NoticeAppMod AddRow() InsNoticeView Notices13. AckAppMod AddRow() InsAckView Acknowledgeme

nt

3.1.5 Packages

No. Package Name Procedures / Functions

usedReference with the URS Input/ Process/ Queries

1 None None

Page 12 of 77


4 SCREENS

4.1 SCRACK

Name: Acknowledgement Screen

Description:This Screen is used to capture the name of the dealer who wishes to register as a VAT/TOT dealer.An Acknowledgement Number is generated.

Tables Referred:

Table Name Select Insert Update DeleteAck_Master Forms_Master

Process Control Objects / Web BeansSL.No. Web Bean Name Method Name Application Module Name1. AckWB InsRow() AckAppMod

Business Components / Application Modules, Views & Entities

SL.No. Application Module Name

Method Name View object Entity Name

1. AckAppMod AddRow() InsAckView Acknowledgement

Packages Referred:

SL.No. Package Name Procedure/Function Name1. None None

Screens Called: None

Reports Called: None

Screen Layout:

Field Descriptions :

Sl.No

Field Name

Table/ Column

Validations Specifications* MIUQ LOV (select statement)

Default Value

1. Acknowledgement Number

Ack_Master:Ack_No

ADD Text item MIQ N Number is System generated

Page 13 of 77

Acknowledgement

Registration

Registration Returns & Payments Assessments

Acknowledgement Number :

Dealer Name:

Date of Application:

Form Name:

Advisory Visits

Add Save Cancel Close


2. Name of the Business to be Registered

Ack_Master:Dlr_Name

ADD Text item MIQ N None

3. Date of Application

Ack_Master:Appln_Rcpt_Date


4. Form Name

Ack_Master:Form_Name


M- Mandatory: I- Insert: U- Update: Q- Query:

* Specifications : Mention about the field specification like combo box, list values, display item, non-base table,.etc., to be mentioned

Specifications:

Mode Action (While Saving)Add Check for Not Null in Acknowledgement NumberModify Check for Not Null in Acknowledgement NumberQuery NoneDelete None

Functionality: This screen is a screen for acknowledging registration form that is submitted by

the dealer. A unique acknowledgment no. is generated by the system and displayed in the

Acknowledgement field. This cannot be changed by the user. The date field is populated with the system date. The Dealer Name and Form

Name is entered. All the fields are mandatory . The Save button would save the acknowledgment details in the acknowledgement

table. Before inserting the record a check would be performed on the validity of the Form Name from the Forms Control table.

A record is posted in the Alerts_Log table after the acknowledgement is given. The Alerts method is called to alert the data entry section for data entry of the

forms that are submitted.

4.2 SCRREGENTRY

Name: List of Dealers for Registration Data entry

Description:This Screen is a Query Screen which alerts the user about the Registrations that are to be done.This screen will be opened by the Data Entry Operator. Tables Referred:

Table Name Select Insert Update DeleteAcknowledgement Dealer_Master

Process Control Objects / Web BeansSL.No. Web Bean Name Method Name Application Module Name1. LstRegEntryWB QryRow() LstRegEntryAppMod

Business Components / Application Modules, Views & Entities


View object Entity Name Method Name

1. LstRegEntryAppMod

QryLstRegEntryView

Ack_MasterDealer_Master

SelectRow()

Page 14 of 77


Packages Referred:


Screens Called: VAT100,TOT001,CST


Screen Layout:

Sl.No Ack.Number Dealer Name Date of Application


Sl.No

Field Name

Table/ Column


Default Value


Ack_Master:Ack_No

QUERY Text item Q N None


Ack_Master:Dlr_Name



Ack_Master:Appln_Rcpt_Date




Specifications:

Mode Action (While Saving)Add NoneModify NoneQuery NoneDelete NoneFunctionality: This screen is a list of all the Registrations that the data Entry Operator has to do. This screen will populate the list of acknowledgements for the Data Entry

Operator. The Close button would close the screen. When the user clicks on the particular record then depending on either VAT or

TOT ,the particualr screen is opened.

Page 15 of 77

Close


4.3 SCRVAT100

Name: VAT 100 Screen

Description:This Screen is used to capture the details of the dealer who wishes to register as a VAT dealer.

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Tin_Master Commodity_master Dlr_Cmdty_Link Dlr_Acty_Dtls Dlr_Bank Dlr_Brnch_Dtls Dlr_Prtnr_Detls Lookup_Codes Lookup_Types Photo_Master Tin_Weightage User_Master

Process Control Objects / Web Beans

SL.No. Web Bean Name Application Module Method Name1. VAT100WB VAT100AppMod InsRow()

QryRow()UpdRow()

Business Objects / Entity Beans



1. VAT100AppMod InsVAT100View

Dealer_Master AddRow(Row)VatEligibility()GenTIN()ChkPAN()

Dlr_BankDlr_Acty_DtlsDlr_Cmdty_linkDlr_Brnch_DtlsDlr_Prtnr_DetlsTin_Master

QryVAT100View

Lookup_Codes SelectRow(Row)Commodity_Master

UpdVAT100View

Alert_Log UpdateRow()

Screens Called: scr100A,scr100B


Screen Layout :

Page 16 of 77


Page 17 of 77

APPLICATION FOR VAT REGISTRATION

01 Name of the business to be registered:

02 Address of Principal Place of Door No: Street business: Locality Town/City District Pin Code Phone No: Fax No:

03 Name of the Owner of business : Door No: Street (Residential Address of the Locality Town/City Person responsible ie., Managing District Pin Code Partner /Managing Director Phone No: Fax No: for business). Father/Husband Name:

04 Status of business: (Mark “ “ where applicable) Sole Proprietorship Partnership Private Limited Company Public Limited Company Govt. Enterprise Others (Specify)

05 Nature of Principal business activities:

06 Principal Commodities traded:

12 Bank Account Details: 1)Bank Name : (b) Branch & Code (c) Account No.

2)Bank Name: (b) Branch & Code (c) Account No.

08 Income Tax Permanent Account Number: (PAN)

09 Address of additional places of business/ Branches/ Godowns (including those outside A.P): Use form VAT 100A

10 Particulars of owners/Directors/Partners: Status & FunctionName & Surname Use Form VAT 100BAddress:Father’s/Husband’s Name:

11 Language in which books are written:

12 Are your accounts computerized: YES NO

13 Date of first taxable supply Date Month Year

14 Turnovers of taxable supplies of goods including zero rate in:08 The last 3 months: Rs.

Affix Passport SizePhoto of

Sole Proprietor.In case Partnership

firm/Companies/othersAffix photos of

responsible persons onVAT 100B



Sl.No

Field Name Table/ Column

Validations

Specifications*

MIUQ LOV (select statement)

Default Value

1. Acknowledgement number

Dealer_Master:Ack_No

ADD Text item MI N None

2. Dealer Photograph

Photo_Master:Dlr_Photo

ADDQUERY

Blob item IQ N None

3. Taxpayer No.(TIN)

Dealer_Master: Tin_GrnTin_Master: GrnDelaer_Cmdty_Link:Tin_GrnPhoto_Master:Tin_GrnDlr_Brnch_Dtls:Tin_GrnDlr_Bank:Tin_Grn

ADDQUERY

Text item MIQ N System generated

4. Door Number of the Principal place of

Dlr_Brnch_Dtls:Door_Num

ADDQUERY

Text item MIQ N None

Page 18 of 77

12 Anticipated turnovers of taxable supplies of goods including zero rate in:08 a) The next 3 months Rs. b) The next 12 months Rs.

16 Anticipated Turnover of exempted supplies of goods in the next 12 months:

17 Are you applying for voluntary registration: YES NO

18 Are you applying for registration prior tomaking taxable supplies: YES NO

a) Are you registered under C.S.T. ActIf so your Registration Number/Have you applied for CST Registration YES NO

20. Do you expect your input tax toregularly exceed your output tax?If yes Why? YES NO

21 Are you receiving investment incentives: YES NOIf so, please specify the incentive you arecurrently receiving. Tax holiday or deferment

FOR OFFICE USE ONLY

22 Date of receipt of application: 31 Date of receipt of application by the Registering Authority

23 Activity/Commodity Code 32 Date of issue of Registration Certificate.

24 Exempt Indicator 33 Effective date of Registration25 Voluntary Registration Indicator 34 Date of refusal of Registration26 Startup Business Indicator 35 Taxpayer No. (TIN)27 CST Indicator28 Refund Indicator


Business5. Principal

place of Business:Street_Num

Dlr_Brnch_Dtls:Street_Num

ADDMODQUERY

Text Item IQ N None

6. Principal place of Business:Locality

Dlr_Brnch_Dtls:Location

ADDMODQUERY

Text item IQ N None

7. Principal place of Business:Town

Dlr_Brnch_Dtls:Town

ADDMODQUERY


8. Principal place of Business:District

Dlr_Brnch_Dtls:District

ADDMODQUERY

Text Item MIQ N None

9. Principal place of Business:Pin

Dlr_Brnch_Dtls:Pin

ADDMODQUERY


10. Principal place of Business:Phone number

Dlr_Brnch_Dtls:Phone

ADDMODQUERY

Text item IQ N None

11. Principal place of Business:Fax Number

Dlr_Brnch_Dtls:Fax

ADDMODQUERY

Text item IQ N None

12. Principal place of Business: Email

Dlr_Brnch_Dtls:Email

ADDMODQUERY

Text Item IQ N None

13. Door Number of the owner/Director/Partner


ADDMODQUERY


14. Owner/Director/Partner :Street_Num

Dlr_Prtnr_Dtls:Street_Num

ADDMODQUERY

Text item IQ N None

15. Owner/Director/Partner :Locality

Dlr_Prtnr_Dtls:Location

ADDMODQUERY

Text Item IQ N None

16. Owner/Director/Partner :Town

Dlr_Prtnr_Dtls:Town

ADDMODQUERY


17. Owner/Director/Partner :District

Dlr_Prtnr_Dtls:District

ADDMODQUERY


18. Owner/Director/Partner :Pin

Dlr_Prtnr_Dtls:Pin

ADDMODQUERY

Text item IQ N None

19. Owner/Director/Partner :Phone number

Dlr_Prtnr_Dtls:Phone

ADDQUERY

Text item IQ N None

Page 19 of 77


20. Owner/Director/Partner :Fax Number

Dlr_Prtnr_Dtls:Fax

ADDQUERY

Text item IQ N None

21. Owner/Director/Partner :Email

Dlr_Prtnr_Dtls:Email

ADDQUERY

Text item IQ N None


Dealer_Master:Firm_Name

ADDQUERY


23. Status of Business

Dealer_Master:status_Code

ADDMODQUERY

Check box

MIQ N None

24. Principal Business Activity

Dealer_Master:Rg_Dlr_Bsns_Desc

ADDMODQUERY

Text Item IQ N None

25. Principal Commodities Traded

Dlr_Cmdty_Link:Cmdty_Cd

ADDQUERY

List Item MIQ Y None

26. Bank Account Number

Dlr_Bank:Account_num

ADDQUERY


27. Bank Branch Code

Dlr_Bank:Locn_Cd

ADDQUERY


28. Bank Name

Loc_Adrs_Master:Name

ADDQUERY


29. PAN Number

Dlr_Prtnr_Dtls:Pan_Num

ADDQUERYCheck for DuplicateMandatory


30. Language in which books are written

Tin_Master: AcBook_Lang

ADDQUERY

List Item MIQ N None

31. Accounts Computerized or not

Tin_Master: Acc_Cmptzd_Yn

ADDQUERY

Radio Button

MIQ N None

32. Date of First Taxable Supply

Tin_Master:Frst_Txble_Supp_Dt

ADDQUERY

Text item IQ N None

33. Turnover of Taxable Supplies in last 3 months

Tin_Master: Txble_Trnovr_last_3

ADDQUERY

Text Item IQ N None

34. Turnover of Taxable Supplies in

Tin_Master: Txble_Trnovr_last_12

ADDQUERY

Text item IQ N None

Page 20 of 77


last 12 months

35. Expected Turnover of Taxable Supplies in next 3 months

Tin_Master: Txble_Trnovr_next_3

ADDQUERY

Text item IQ N None

36. Expected Turnover of Taxable Supplies in next 12 months

Tin_Master: Txble_Trnovr_Next_12

ADDMODQUERY

Text Item IQ N None

37. Voluntary Registration

Tin_Master: vlntry_Reg_Yn

ADDQUERY

Radio Button

IQ N None

38. Registration as Startup Business

Tin_Master: Startup_bsns_Yn

ADDQUERY

Radio Button

IQ N None

39. APGST Number

Tin_Master:Tin_Apgst_Num

ADDQUERY

Text box IQ N None

40. CST Dealer Tin_Master: CST_Num

ADDQUERY

Text box IQ N None

41. CST Dealer Tin_Master: CST_Applied_Yn

ADDQUERY

Radio Button

IQ N None

42. Proffesional Tax

Tin_Master:Proff_Tax

ADDQUERY

Text box IQ N None

43. Input Tax Exceeds Output Tax

Tin_Master: Ip_xcd_op_Remark

ADDQUERY

Radio Button

IQ N None

44. Tax Incentives

Tin_Master: Tax_Incntv_cd

ADDQUERY

Radio Button

IQ N None

45. Date of Receipt of Application

Dealer_Master:Appln_Rcpt_Date

ADDQUERY

Text Box IQ N None

46. Activity/Commodity Code

Tin_Weightage:Activity_Cd

ADDQUERY

Text box IQ N None

47. Exempt Indicator

Tin_Weightage:Xmptd_Ind

ADDQUERY

Text box IQ N None

48. Voluntary Registration Indicator

Tin_Weightage:Volntry_Ind

ADDQUERY

Text box IQ N None

Page 21 of 77


49. Startup business Indicator

Tin_Weightage:Startup_Ind

ADDQUERY

Text box IQ N None

50. CST Indicator

Tin_Weightage:CST_Ind

ADDQUERY

Text box IQ N None

51. Refund Indicator

Tin_Weightage:Refund_Ind

ADDQUERY

Text box IQ N None

52. Investment Incentive Indicator

Tin_Weightage:Incntv_Ind

ADDQUERY

Text box IQ N None

53. SAT Indicator

Tin_Weightage:Sat_Ind

ADDQUERY

Text box IQ N None

54. Date of Receipt of Application by the Registering Authority

Dealer_Master:Rcpt_RA_Dt

ADDQUERY

Text Box IQ N None

55. Date of Issue of Registration Certificate

Dealer_Master:Rc_issd_Dt

ADDQUERY

Text Box IQ N None

56. Effective Date of Registration

Dealer_Master:Rc_Eff_Dt

ADDQUERY

Text Box IQ N None

57. Date of Refusal of Registration

Dealer_Master:Reg_Rfsl_Dt

ADDQUERY

Text Box IQ N None

58. Processing Authority Comments

Dealer_Master:PA_Comment

ADDQUERY

Text box IQ N None

59. PA Name User_Master:Emp_Name

QUERY Text box Q N None

60. PA Designation

User_Master:Emp_Desg


61. Registering Authority Comments

Dealer_Master:RA_Comment

ADDQUERY

Text box IQ N None

62. RA Name User_Master:Emp_Name


63. RA Designation




Page 22 of 77



Specifications:

Mode Action (While Saving)Add Check for Not Null in Tin_GrnModify Check for Not Null in Tin_GrnQuery NoneDelete None

Functionality: This screen is used to capture the details of the dealer who wishes to register as a

VAT dealer. If this screen is opened directly then the Acknowledgement Number must be

entered and the system validates the Acknowledgement number else the Acknowledgement Number will be automatically entered from the scrRegEntry.

Initially the Tin field has the Acknowledgement Number.Later when all the details are filled(including the Original TIN ) then a new record is inserted with TIN in TIN.

It captures the CST Numbers of the dealers(if any). It captures the APGST Numbers of the dealers(if any). It provides links to the Screens scrVAT100A, scrVAT100B. A unique TIN is generated by the system and displayed in the TIN field. This

cannot be changed by the user. The receipt date field is populated with the system date. A part of the Screen is filled by the Data Entry Operator. After the Screen is entered by the Data Entry Operator,the Screen is visible to the

Processing Authority. After the Screen is processed by the Data Entry Operator,the Screen is visible to

the Registering Authority. The Save button would save the details in the Dealer Master,TIN Master,Dealer

Commodity Link,Dealer Branch Details, Dealer Bank table. The Alerts method is called to alert the Processing Authority,Registering Authority

section.

4.4 SCRVAT100A

Name: VAT 100 A form

Description:This Screen is used to capture the address of additional places of Business/godowns/branches of the dealer.

Tables Referred:Table Name Select Insert Update DeleteDealer_Master Dlr_Brnch_Dtls Lookup_Codes Lookup_Types


SL.No. Web Bean Name Application Module Method Name1. VAT100AWB VAT100AAppMod InsRow()

QryRow()




1. VAT100AAppMod InsVAT100AView

Dlr_Brnch_Dtls AddRow(row)

Page 23 of 77


QryVAT100AView

Lookup_Codes SelectRow(Row)

Packages Referred:

SL.No. Procedure Name Function Name1. None None

Screens Called: ScrVAT100


Screen Layout :

Type Door No.

StreetNum

Locality

Town/City

District Pin Code

Phone No.

Fax No. Email

Field Description :

Sl.No


Validations

Specifications*


Default Value

1. Door Number of the business/Branch/Godown


ADDQUERY


2. Business/Branch/Godown:Street_Num


ADDMODQUERY

Text Item IQ N None

Page 24 of 77

Place of Business:

Door No.: Street No.:

Locality: Town/City:

District: Pin Code :

Phone No.: Fax No.:

Email:

ADD CANCEL CLOSE SAVE


3. Business/Branch/Godown:Locality


ADDMODQUERY

Text item IQ N None

4. Business/Branch/Godown:Town

Dlr_Brnch_Dtls:Town

ADDMODQUERY


5. Business/Branch/Godown:District


ADDMODQUERY


6. Business/Branch/Godown:Pin

Dlr_Brnch_Dtls:Pin

ADDMODQUERY


7. Business/Branch/Godown:Phone number


ADDMODQUERY

Text item IQ N None

8. Business/Branch/Godown:Fax Number

Dlr_Brnch_Dtls:Fax

ADDMODQUERY

Text item IQ N None

9. Business/Branch/Godown: Email


ADDMODQUERY

Text Item IQ N None



Specifications:

Mode Action (While Saving)Add Check for Door Number and Pin for not nullModify Check for Door Number and Pin for not nullQuery NoneDelete None

Functionality: This screen is used to capture the address of the branches/Godowns/Places of

Business of the dealer who wishes to register as a VAT dealer. The Save button would save the details in Dealer Branch Details.

4.5 SCRVAT100B

Name: VAT 100 B form

Description:This Screen is used to capture the address and details of the owner/director/partner etc.of the dealer.

Tables Referred:Table Name Select Insert Update DeletePhoto_Master Dlr_Prtnr_Detls Lookup_Codes


Page 25 of 77


SL.No. Web Bean Name Application Module Method Name1. VAT100BWB VAT100BAppMod InsRow()

QryRow()




1. VAT100BAppMod InsVAT100BView Dlr_prtnr_DtlsPhoto_Master

AddRow(row)

QryVAT100BView Lookup_Codes SelectRow(Row)

Packages Referred:SL.No. Procedure Name Function Name1. None None

Screens Called: ScrVAT100


Screen Layout :

Page 26 of 77


Field Description :Sl.No


Validations

Specifications*

MIUQ

LOV (select statement)

Default Value

1. Photograph Photo_Master:Dlr_Photo

ADDQUERY

Blob IQ N None



ADDMODQUERY

Text item

MIQ N None

Page 27 of 77

director/Partner:

Name:

Father Name:

Husband Name:

Date of Birth:




Phone No.: Fax No.:

Email:

PAN:

Edu.Qualification:

Reference1:

Reference2:

ADD CANCEL CLOSE SAVE

Photograph




ADDMODQUERY

Text item

IQ N None



ADDMODQUERY

Text Item

IQ N None


Dlr_Prtnr_Dtls:Town

ADDMODQUERY

Text item

MIQ N None



ADDMODQUERY

Text item

MIQ N None


Dlr_Prtnr_Dtls:Pin

ADDMODQUERY

Text item

MIQ N None



ADDQUERY

Text item

IQ N None


Dlr_Prtnr_Dtls:Fax

ADDQUERY

Text item

IQ N None



ADDQUERY

Text item

IQ N None



Specifications:

Mode Action (While Saving)Add Check for Door Number and Pin for not nullModify Check for Door Number and Pin for not nullQuery NoneDelete None

Functionality: This screen is used to capture the address of the partner/director of the dealer

who wishes to register as a VAT dealer. The Save button would save the details in Dlr_Prtnr_Dtl.

4.6 SCRLSTREGPROC

Name: List of Dealers for Processing/Registering

Description:This Screen is a Query Screen used to query the Pending Registrations.This screen will be opened by the Processing authority and Registering authority. For the Processing Authority this screen will be showing the details of the dealers whose data entry has been done and who are waiting for processing.For the Registering Authority this screen will be showing the details of the dealers whose processing has been done and who are waiting for Registered.

Page 28 of 77


Tables Referred:

Table Name Select Insert Update DeleteDealer_Master


SL.No. Web Bean Name Application Module Method Name1. LstRegProcWB LstRegProcAppMod QryRow()




1. LstRegProcAppMod

QryLstRegProcView

Dealer_Master SelectRow()

Packages Referred:


Screens Called: VAT100,TOT001


Screen Layout:

Sl.No Ack.Number

Dealer Name

Nature of Bsns

Date of Application


Sl.No

Field Name

Table/ Column


Default Value


Dlr_Master:Ack_No



Dlr_Master:Dlr_Name


3. Nature of Bsns

Dlr_Master:Status_Cd


Page 29 of 77

Close



Dlr_Master:Appln_Rcpt_Date




Specifications:

Mode Action (While Saving)Add NoneModify NoneQuery NoneDelete None

Functionality: This screen is a common screen for all the Pending Registrations. This screen will populate the pending registrations for the Data Entry

Operator,The Processing Authority,the Registering authority. The Close button would close the screen. When the user clicks on the particular record then depending on either VAT or

TOT ,the particualr screen is opened.

4.7 SCRVAT104

Name: VAT 104 form

Description:This Screen is used to capture the details of the dealer who wishes to register as a Startup dealer.

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Tin_Master






1. VAT104AppMod QryLstRegProcView

Dealer_Master InsRow()

Packages Referred:


Screens Called: scrVAT100


screen Layout :

Page 30 of 77

ADD MODIFY SAVE CANCEL CLOSE



Sl.No

Field Name

Table/ Column

Validations

Specifications*


Default Value

1. Name of the Applicant


QUERYText item MQ N None

3. Name pf the Business to be registered


QUERY

Text Item MQ N None

4. Date of origin of Business

Tin_Master:Dt_origin_Bsns

ADDQUERY

List Item MIQ Y None



QUERYText Box MQ N None



QUERYText Item MQ N None

7. Date of commencement of trading

Tin_Master:Bsns_Cmncmnt_Dt

ADDQUERY


8. VAT paid prior

Tin_Master:VAT_Paid

ADDQUERY

Text item IQ N None

4. PA Name

User_Master:Emp_Name


5. PA Designation



6. Registering

Dealer_Master:RA_

ADDQUERY

Text box IQ N None

Page 31 of 77

01 Name of business to be registered

02 Date of origin of business

03 Status of business

04 Describe planned business activities

05 Provide projected date of commencement of trading

06 Declare amount of any VAT paid prior to this application


Authority Comments

Comment

7. RA Name

User_Master:Emp_Name


8. RA Designation





Specifications:


Functionality: This screen is used to capture the details of a dealer who wishes to register as

startup dealer. This screen will be filled after the VAT 100 form is filled. So some data like the

name of the dealer,status,principal activity is queried from the Dealer_master and Tin_Master.

The Save button would save the details in Dealer_Master and Tin_Master.

4.8 SCRCST

Name: Form A( CST Registration)

Description:This Screen is used to capture the details of the dealer who wishes to register as a CST dealer.

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master CST_Master Commodity_master Dlr_Cmdty_Link Dlr_Acty_Dtls Dlr_Bank Dlr_Brnch_Dtls Dlr_Prtnr_Detls Lookup_Codes User_Master


SL.No. Web Bean Name Application Module Method Name1. CSTWB CSTAppMod InsRow()

Page 32 of 77


QryRow()UpdRow()




1. CSTAppMod InsCSTView Dealer_Master AddRow(Row)CSTEligibility()GenCST()

Dlr_BankDlr_Acty_DtlsDlr_Cmdty_linkDlr_Brnch_DtlsDlr_Prtnr_DetlsCST_Master

QryCSTview Lookup_Codes SelectRow(Row)Commodity_Master

UpdCSTView Alert_Log UpdateRow()

Packages Referred:


Screens Called: VAT100


screen Layout :


Sl.No


Validations

Specifications*


Default Value

1. Acknowledgement number

Dealer_Master:Ack_No


2. CST No Dealer_Master: Tin_GrnCST_Master: CSTNoDelaer_Cmdty_Link:Tin_GrnDlr_Brnch_Dtls:Tin_GrnDlr_Bank:Tin_Grn

QUERYText item Q N System

generated

3. Door Number of the Principal place of Business


QUERYText item Q N None

4. Principal place of Business:Street_Num


QUERYText Item Q N None



QUERY

Text item Q N None

Page 33 of 77



Dlr_Brnch_Dtls:Town

QUERY

Text item Q N None



QUERY

Text Item Q N None


Dlr_Brnch_Dtls:Pin QUERY

Text item Q N None



QUERY

Text item Q N None


Dlr_Brnch_Dtls:Fax

QUERY

Text item Q N None



QUERY

Text Item Q N None



ADDMODQUERY

Text item IQ N None



ADDMODQUERY

Text item IQ N None



ADDMODQUERY

Text Item IQ N None


Dlr_Prtnr_Dtls:Town

ADDMODQUERY

Text item IQ N None



ADDMODQUERY

Text item IQ N None


Dlr_Prtnr_Dtls:Pin

ADDMODQUERY

Text item IQ N None



ADDQUERY

Text item IQ N None


Dlr_Prtnr_Dtls:Fax

ADDQUERY

Text item IQ N None



ADDQUERY

Text item IQ N None

Page 34 of 77




ADDMODQUERY

Check box

IQ N None



QUERYText Item Q N None



ADDQUERY

List Item IQ Y None

24. Language in which books are written

Tin_Master: AcBook_Lang

ADDQUERY

List Item IQ N None

25. Accounts Computerized or not

Tin_Master: Acc_Cmptzd_Yn

ADDQUERY

Radio Button

IQ N None

26. Date of First Taxable Supply

Tin_Master:Frst_Txble_Supp_Dt

ADDQUERY

Text item IQ N None

27. Turnover of first interstate trade

CST_Master: frst_Txble_Trnovr

ADDQUERY

Text Item IQ N None

28. APGST Number

Tin_Master:Tin_Apgst_Num

ADDQUERY

Text box IQ N None


Dealer_Master:Appln_Rcpt_Date

ADDQUERY

Text Box IQ N None

30. Date of Receipt of Application by the Registering Authority

Dealer_Master:Rcpt_RA_Dt

ADDQUERY

Text Box IQ N None

31. Date of Issue of Registration Certificate


ADDQUERY

Text Box IQ N None

32. Effective Date of Registration


ADDQUERY

Text Box IQ N None

33. Date of Refusal of Registration


ADDQUERY

Text Box IQ N None



ADDQUERY

Text box IQ N None



Page 35 of 77


36. PA Designation





ADDQUERY

Text box IQ N None



39. RA Designation





Specifications:

Mode Action (While Saving)Add NoneModify NoneQuery NoneDelete NoneFunctionality: This screen is used to capture the details of a dealer who wishes to register as

CST dealer. This form is filled only if VAT details have been entered so some details can be

fetched from the Dealer_Master,Tin_Master,Dlr_Acty_Detls,Dlr_Cmdty_link. The Save button would save the details in

CST_Master.,Dlr_Cmdty_Link,Dlr_Brnch_Detls,Dlr_Prtnr_Detls.

4.9 SCRTOT001

Name: TOT 001 form

Description:This Screen is used to capture the details of the dealer who wishes to register as a TOT dealer.

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Grn_Master Commodity_master Dlr_Cmdty_Link Dlr_Brnch_Dtls Dlr_Prtnr_Detls Branch_master Dlr_Bank User_Master


SL.No. Web Bean Name Application Module Method Name1. TOT001WB TOT001AppMod InsRow()

Page 36 of 77


QryRow()UpdRow()

Business Objects / Entity BeansSL.No. Application

Module NameView object Entity Name Method Name

1.

TOT001AppMod InsTOT001View

Dealer_MasterDlr_BankDlr_Acty_DtlsDlr_Cmdty_linkDlr_Brnch_DtlsDlr_Prtnr_DetlsGrn_Master

AddRow(Row)TOTEligibility()GenGRN()

QryTOT001View

Lookup_Codes SelectRow(Row)Commodity_Master

UpdTOT001View

Alert_Log UpdateRow()

Packages Referred:


Screens Called: scrVAT100A,scrVAT100B


screen Layout :

Page 37 of 77



Sl.No


Validations

Specifications*


Default Value

1. Name of the Applicant


ADDQUERY




ADDMODQUERY


3. Door Number of the Principal place of Business


ADDQUERY


4. Principal place of Business:Street_Num


ADDMODQUERY

Text Item IQ N None



ADDMODQUERY

Text item IQ N None


Dlr_Brnch_Dtls:Town

ADDMODQUERY




ADDMODQUERY



Dlr_Brnch_Dtls:Pin

ADDMODQUERY




ADDMODQUERY

Text item IQ N None

Page 38 of 77

FOR OFFICE USE ONLY

16 Date of receipt of application17 Effective date of registration.18 Date of certification by Registering Authority19 Date of refusal of registration by Registering Authority.20 GENERAL REGISTRATION No:Processing Authority Registering Authority

Name Name

Designation Designation:



Dlr_Brnch_Dtls:Fax

ADDMODQUERY

Text item IQ N None



ADDMODQUERY

Text Item IQ N None



ADDMODQUERY

Text item IQ N None



ADDMODQUERY

Text item IQ N None



ADDMODQUERY

Text Item IQ N None


Dlr_Prtnr_Dtls:Town

ADDMODQUERY

Text item IQ N None



ADDMODQUERY

Text item IQ N None


Dlr_Prtnr_Dtls:Pin

ADDMODQUERY

Text item IQ N None



ADDQUERY

Text item IQ N None


Dlr_Prtnr_Dtls:Fax

ADDQUERY

Text item IQ N None



ADDQUERY

Text item IQ N None



ADDQUERY

Text item IQ N None


Dlr_Cmdty_Link:Cmdty_Code

ADDQUERY

List Item IQ Y None

23. Date of Commencement of Business

Grn_Master:Bsns_Cmnc_Dt

ADDQUERY

Text Box IQ N None

24. Reference1 Grn_Master:txpyr_Rfrnc1_Grn

ADDQUERY

Text Item IQ N None

Page 39 of 77


25. Reference 2

Grn_Master:Txpyr_Rfrnc2_Grn

ADDQUERY

Text Item IQ N None


Dealer_Master:Bsns_Desc

ADDQUERY


27. Bank Account Number

Dlr_Bank:Dbm_bnk_acct_number

ADDQUERY


28. Bank Branch Code

Dlr_Bank:Dbm_Bnk_Branch_Code

ADDQUERY


29. Bank Name Dlr_Bank: Dbm_Bnk_Name

ADDQUERY


30. Annual gross Turnover for previous year

Grn_Master:Prv_Ann_Trnovr

ADDQUERY

Text Item IQ N None

31. Date of turnover exceeding 2.5 lakhs

Grn_Master:Date_xcd2.5

ADDQUERY

Text Item IQ N None


Dealer_Master:Appln_rcpt_Dt

ADDQUERY

Text Box MIQ N None

33. Effective date of registration


ADDQUERY

Text Box IQ N None

34. Date of Certification by registering Authority


ADDQUERY

Text Box IQ N None

35. Date of Refusal by Registering Authority


ADDQUERY

Text Box IQ N None



ADDQUERY

Text box IQ N None



38. PA Designation





ADDQUERY

Text box IQ N None

Page 40 of 77




41. RA Designation





Specifications:

Mode Action (While Saving)Add Check for Not Null in GrnModify Check for Not Null in GrnQuery NoneDelete None

Functionality: This screen is used to capture the details of the dealer who wishes to register as a

TOT dealer. The Acknowledgement Number must be entered if the screen is opened directly. If the screen is called from the scrDatEntry then the Acknowledgement Number is

automatically populated. It provides links to the Screens scrVAT100A, scrVAT100B. A unique GRN is generated by the system and displayed in the GRN field. This

cannot be changed by the user. The receipt date field is populated with the system date. A part of the Screen is filled by the Data Entry Operator. After the Screen is entered by the Data Entry Operator,the Screen is visible to the

Processing Authority. After the Screen is processed by the Data Entry Operator,the Screen is visible to

the Registering Authority. The Save button would save the details in the Dealer Master,GRN Master Dealer

Bank table. The Alerts method is called to alert the Processing Authority,Registering Authority

section.

4.10SCRVAT112

Name: VAT 112 form

Description:This Screen is used to capture the change in the registration details of the dealer .

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Tin_Master Dlr_Brnch_Dtls Dlr_Prtnr_Detls Dlr_History


SL.No. Web Bean Name Application Module Method Name1. VAT112WB VAT112AppMod UpdRow()


Page 41 of 77




1. VAT112AppMod UpdVAT112View Dealer_MasterDlr_BankDlr_Acty_DtlsDlr_Cmdty_linkDlr_Brnch_DtlsDlr_Prtnr_DetlsAlert_Log

UpdateRow(Row)ValidTime()

Packages Referred:



Reports Called : None

Screen Layout :

Registration Number

Name

Present Name

Change in Name

Present Address:

Page 42 of 77

Place of Business:




Phone No.: Fax No.:

Email:


Proposed Address:

CST Registration

Change in legal status


Sl.No

Field Name

Table/ Column

Validations Specifications*


Default Value

1. Tin Dealer_Master:tin_grn


2. Change In Name Proposed

Dealer_Master:Firm_NameDealer_History:FieldValue

MOD Text item UQ N None

3. Change In Door Number of Principal Place of Business Proposed

Dlr_Brnch_Dtls:Door_NumDealer_History:FieldValue

MOD Text Item UQ N None

4. Change In Street_Num Number of Principal Place of Business Proposed

Dlr_Brnch_Dtls:Street_NumDealer_History:FieldValue


5. Change In Locality of Principal Place of Business

Dlr_Brnch_Dtls:LocationDealer_History:FieldVal


Page 43 of 77

Yes No

Yes No

SAVE Process APPROVE

CANC

Place of Business:




Phone No.: Fax No.:

Email:


Proposed ue6. Change In

Town of Principal Place of Business Proposed

Dlr_Brnch_Dtls:TownDealer_History:FieldValue


7. Change In District of Principal Place of Business Proposed

Dlr_Brnch_Dtls:DistrictDealer_History:FieldValue


8. Change In Pin Code of Principal Place of Business Proposed

Dlr_Brnch_Dtls:PinDealer_History:FieldValue


9. Change In Phone Number of Principal Place of Business Proposed

Dlr_Brnch_Dtls:PhoneDealer_History:FieldValue


10. Change In Fax Number of Principal Place of Business Proposed

Dlr_Brnch_Dtls:FaxDealer_History:FieldValue


11. Change In Email of Principal Place of Business Proposed

Dlr_Brnch_Dtls:EmailDealer_History:FieldValue


12. Change In Door Number of Branches/Godowns Proposed

Dlr_Brnch_Dtls:Door_NumDealer_History:FieldValue


13. Change In Street_Num Number of Branches/Godowns Proposed

Dlr_Brnch_Dtls:Street_NumDealer_History:FieldValue


Page 44 of 77


14. Change In Locality of Branches/Godowns Proposed

Dlr_Brnch_Dtls:LocationDealer_History:FieldValue


15. Change In Town of Branches/Godowns Proposed

Dlr_Brnch_Dtls:TownDealer_History:FieldValue


16. Change In District of Branches/Godowns Proposed

Dlr_Brnch_Dtls:DistrictDealer_History:FieldValue


17. Change In Pin Code of Branches/Godowns Proposed

Dlr_Brnch_Dtls:PinDealer_History:FieldValue


18. Change In Phone Number of Branches/Godowns Proposed

Dlr_Brnch_Dtls:PhoneDealer_History:FieldValue


19. Change In Fax Number of Branches/Godowns Proposed

Dlr_Brnch_Dtls:FaxDealer_History:FieldValue


20. Change In Email of Branches/Godowns Proposed

Dlr_Brnch_Dtls:EmailDealer_History:FieldValue


21. Change in Legal Status proposed

Dealer_Master:Occpncy_StatusDealer_History:FieldValue


22. With Effect From

Dealer_Master:Rg_Dlr_Regn_Eff_DateDealer_History:Chng_Dt


23. Applied for CST Registration

Tin_Master: Cst_Applied_Yn




Specifications:

Page 45 of 77


Mode Action (While Saving)Add Check for Not Null in TINModify Check for Not Null in TINQuery NoneDelete None

Functionality:

This screen is used to capture the details of the dealer who wishes to change registrations details of a dealer.

First the Tin Number is entered. The details are populated. The receipt date field is populated with the system date. The Save button would save the details in the Dealer Master,Dealer Commodity

Link, Dealer Bank table,Dealer History,Dealer Partner Details. There is check on the date of application and the changes date which should not

be greater than 10 days. If there is a difference then the system posts an alert for the Processing authority

for penalty.

4.11 SCRVAT121

Name: VAT 121 form

Description:This Screen is used to capture the Cancellation details of the dealer .

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Dlr_Cncl_Details User_Master



UpdRow()

Page 46 of 77




1. VAT121AppMod InsVAT121View

Dlr_Cncl_Dtls AddRow(Row)ChkReturn()ChkRefund()ChkArrear()

Packages Referred:




Screen Layout :

Page 47 of 77

FO R THE COMPLETIO N BY TAX O FFICIAL

Date application received 12

Check arrears of VAT…………………………………………………………………………………………………………...

Confirmation from Return Processing Section – Tax Arrears………………………………………………………………….

Final Return issued……………………………………………………………………………………………………………..

Final Return Received…………………………………………………………………………………………………………..

For Verification YES/NO

Date of cancellation from 13

Date Form VAT 122 issued 14

Date Form VAT 123 refusal of cancellation issued 15

Date Form VAT 124 issued 16

PROCESSING AUTHORITY REGISTERING AUTHORITY



Sl.No


Validations

Specifications*


Default Value

1. TIN Dlr_Cncl_Dtls:Tin_Grn


2. To Cancel Registration with effect from

Dlr_Cncl_Details:Cncl_Dt_From


Page 48 of 77

APPLICATION TO CANCEL VAT REGISTRATION. (Please see Notes on the Reverse of this Form)

Date Month Year

The

I apply to cancel my VAT reg istration with effect from 04 Date:

Reason(s) for the cancellation of registration: Delete (i) (ii) or (iii)if not applicable)

(i) My business closed on: 05 Date:

a) The value of my taxab le turnover over the previous 3 calendarmonths was 06 Value:

And the value of my taxab le turnover over the previous 12 calendar months was 07 Value:

b) I request to cancel my voluntary registration which was registered 08 Date:with effect from.

The value of my taxab le turnover over the previous 3 calendar 09 Value:months was :

The value of my taxab le turnover over the previous 12 calendar 10 Valuemonths was:

The reasons for the application under (i), (ii) or (iii) above are:…………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………. I undertake that I must account for VAT on any stock or assets on hand on which I have received refund of input tax,and file a final tax return and pay the VAT due prior to the cancellation of my reg istration.

03. Name …………………………………………………………………………………………………………………..

Address: Door No………………..……..Street………………………..……….Locality…………….………………

Town/City……………………..……….District………………………..………PIN No:……..……………………...

01 Office Address: …………………………………….…………. ……………………………………..………… ………………………………….…….. 02 TIN


3. Business Closed On

Dlr_Cncl_Details:Bsns_Clsd_Dt

ADDQUERY

Text Box IQ N None

4. Value of taxable turnover over previous 3 calendar months

Dlr_Cncl_Details:txble_trnovr_lst3

ADDQUERY

Text Item IQ N None

5. Value of taxable turnover over previous 12 calendar months

Dlr_Cncl_Details:txble_trnovr_lst12

ADDQUERY

Text Item IQ N None

6. Voluntary Registration Date



7. Reasons for Application

Dlr_Cncl_Details:Cncl_Reason

ADDQUERY

Text item IQ N None


Dlr_Cncl_Details:Cncl_Appn_dt

ADDQUERY

Text Box IQ N None

9. Date of Receiptof Application

Dlr_Cncl_Details:Appn_Rcpt_dt

ADDQUERY

Text Box IQ N None

10. Check Arrears of VAT

Dlr_Cncl_Details:Arrears

ADDQUERY

Text Item IQ N None

11. Confirmation from Returns Processing Section

Dlr_Cncl_Details:Ret_Proc_Sec

ADDQUERY

Text Item IQ N None

12. Final Return Issued

Dlr_Cncl_Details:Ret_Issd

ADDQUERY

Text Item IQ N None

13. Final Return Received

Dlr_Cncl_Details:Ret_Recvd

ADDQUERY

Text Item IQ N None

14. For Verification

Dlr_Cncl_Details:Cncl_Verfn

ADDQUERY

Radio Button

IQ N None

15. Date of Cancellation from

Dlr_Cncl_Details:Cncl_Dt

ADDQUERY

Text Box IQ N None

16. Date FormVAT122 Issued

Dlr_Cncl_Details:VAT122_Issd

ADDQUERY

Text Box IQ N None



ADDQUERY

Text Box IQ N None

Page 49 of 77




ADDQUERY

Text Box IQ N None

19. Processing Authority

User_Master:Cncl_PA

QUERY Text item IQ N None

20. Registering Authority

User_Master:Cncl_RAf

QUERY Text item IQ N None



Specifications:

Mode Action (While Saving)Add Check for Not Null in TINModify Check for Not Null in TINQuery NoneDelete None

Functionality: This screen is used to capture the details of the dealer who wishes to cancel his

registeration. The receipt date field is populated with the system date. The Save button would save the details in the Dlr_Cncl_Detls. There is check on the dealer if he is a Startup or Voluntary Registered Dealer .If

he is any of the above then the system checks for his date of registration and the date of application.The difference should be greater than 2 years.

If there is a difference then the system alerts the Processing authority . The system checks also if there are any arrears,if it has then it alerts the

processing Authority. The system checks if the dealer is Government/semi Govt. then it checks for the

difference of 4 weeks between the closure of business and the date of submission of application.

If there is a difference more than 4 weeks for the above then the system alerts the Processing authority .

For all the other dealers it check s for a difference of 2 weeks. If there is a difference more than 2 weeks for the above then the system alerts

the Processing authority . The system checks for the turnovers ,if it is above the threshold and is not closing

his business then it alerts the processing authority.

4.12 SCRTOT014

Name: TOT 014 form

Description:This Screen is used to capture the Cancellation details of the TOT dealer .

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Dlr_Cncl_Details User_Master


SL.No. Web Bean Name Application Module Method Name1. TOT014WB TOT014AppMod InsRow()

UpdRow()

Page 50 of 77




1. TOT014AppMod InsTOT014View


Packages Referred:




Screen Layout :

Page 51 of 77



Sl.No


Validations

Specifications*


Default Value

1. GRN Dlr_Cncl_Details:Tin_Grn


2. Application Dlr_Cncl_D ADD Text Box IQ N None

Page 52 of 77

APPLICATION TO CANCEL TOT REGISTRATION.

Date Month Year

I apply to cancel my TOT registration from 04 Date:

Reason(s) for the cancellation of registration:(i) My business closed on: 05 Date:

(ii) My turnover for the year has crossed Rs.30,00,000

(iii) I require CST registration for my business and intend to also apply for VAT registration

FOR THE COMPLETION BY TAX OFFICIAL

Date application received 07

Check arrears of TOT ………………………………………………………………………………………………...

Confirmation from Return Processing Section – Tax Arrears …………………………………………………

Final Return Received……YES/NO

Date of cancellation 08

03. Name ………………………………………………………………………………………………………………..

Address: Door No………………..Street……………………………….Locality……………………………………

Town/City……………………….District………………………………PIN No:……..……………………………

01 Office Address:………………………….. …………………………………………… …………………………………………...

…………………………………….

PROCESSING AUTHORITY REGISTERING AUTHORITY

02 GRN


to cancel TOT Registration from

etails:Cncl_Dt_From

3. Business Closed On

Dlr_Cncl_Details:Bsns_Clsd_Dt

ADDQUERY

Text Box IQ N None

4. Turnover Crossed 30 lakhs

Dlr_Cncl_Details:Tot_Teg_Yn

ADDQUERY

Radio Button

IQ N None

5. Require CST Registration

Dlr_Cncl_Details:CST_Apply_Yn

ADDQUERY

Radio Button

IQ N None


Dlr_Cncl_Details:Cncl_Appn_dt

ADDQUERY

Text Box IQ N None


Dlr_Cncl_Details:Appln_Rcpt_dt

ADDQUERY

Text Box IQ N None

8. Check Arrears of VAT

Dlr_Cncl_Details:Arrears

ADDQUERY

Text Item IQ N None

9. Confirmation from Returns Processing Section

Dlr_Cncl_Details:Ret_Proc_Sec

ADDQUERY

Text Item IQ N None

10. Final Return Received

Dlr_Cncl_Details:Ret_Recvd

ADDQUERY

Radio Button

IQ N None



ADDQUERY

Text Box IQ N None


Dlr_Cncl_Details:Cncl_PA

ADDQUERY

Text item IQ N None


Dlr_Cncl_Details:Cncl_RA

ADDQUERY

Text item IQ N None



Specifications:

Mode Action (While Saving)Add Check for Not Null in GRNModify Check for Not Null in GRNQuery NoneDelete None

Functionality:

Page 53 of 77


This screen is used to capture the details of the dealer who wishes to cancel his registration.

The receipt date field is populated with the system date. The Save button would save the details in the Dlr_Cncl_Detls. The system checks if the dealer’s turnover is exceeding 30 lakhs if it exceeds then

it alerts the processing Authority. It converts the dealer from TOT to VAT . The system checks if the dealer is applying for CST registration,if he does then it

converts the dealer into VAT and updates the Dealer Master ,CST Master.

4.13 SCRCNCLBYDPT

Name: Department Initiated Cancellation form

Description:This Screen is used to capture the details for which the department is cancelling the dealers .

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Dlr_Cncl_Details


SL.No. Web Bean Name Application Module Method Name1. DeptCnclWB DeptCnclAppMod InsRow()

UpdRow()



1. DeptCnclAppMod InsDeptCnclView


UpdDeptCnclView

Dealer_Master UpdRow()

Packages Referred:


Link Library Referred:




Screen Layout :

Page 54 of 77

Registration Number :

Dealer Name:

Notice Form:

Date of Sending:

SAVE CANCELGENERATE



Sl.No

Field Name

Table/ Column

Validations

Specifications*


Default Value

1. TIN/GRN Dlr_Cncl_Details:Tin_Grn


2. Reason Dlr_Cncl_Details:Reason

ADD Text item IQ N None



ADDQUERY

Text Box IQ N None


Dlr_Cncl_Details:Cncl_PA

ADDQUERY

Text item IQ N None


Dlr_Cncl_Details:Cncl_RA

ADDQUERY

Text item IQ N None



Specifications:

Mode Action (While Saving)Add Check for Not Null in GRNModify Check for Not Null in GRNQuery NoneDelete None

Functionality:

This screen is used to capture the details of the dealer who wishes to cancel his registration.

The receipt date field is populated with the system date. The Save button would save the details in the Dlr_Cncl_Detls. The system checks if the dealer’s turnover is exceeding 30 lakhs if it exceeds then

it alerts the processing Authority. It converts the dealer from TOT to VAT i.e an updation is done in Dealer_master

for the Dealer_type. The system checks if the dealer is applying for CST registration,if he does then it

converts the dealer into VAT and updates the Dealer Master ,CST Master.

Page 55 of 77


4.14SCRNOTICE

Name: Notice Screen

Description:This Screen is used to generate the notices to the dealer .

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Notice_Master


SL.No. Web Bean Name Application Module Method Name1. NoticeWB NoticeAppMod InsRow()



1. NoticeAppMod InsNoticeView Notices AddRow()

Packages Referred:SL.No. Procedure Name Function Name1. None None


Reports/Notices Called : NotVAT101 NotVAT122

NotVAT123NotVAT124NotVAT125NotVAT113

Screen Layout :


Sl.No


Validations

Specifications*


Default Value

1. Registration Number

Notice:Tin_Grn

ADD Text item

IQ N None

Page 56 of 77

Registration Number :

Dealer Name:

Notice Form:

Date of Sending:

SAVE CANCELGENERATE


2. Name Dealer_Master:Scr_Name

ADD Text item

IQ N None

3. Form Name Notice:Form_Id

ADDQUERY

Text item

IQ N None

4. Date of Sending

Notice:Dt_Sent

ADDQUERY

Text Box IQ N None



Specifications:Mode Action (While Saving)Add NoneModify NoneQuery NoneDelete None

Functionality:

This screen is used to generate notices to the dealers The form name entered will be used to generate the notice. The Save button would save the details in the Notice Master. The Generate Button will generate the notice. The cancel button clears the screen. The Generate button will generate the Notice.

4.15SCRREGREP

Name: Screen to Generate Registration Reports

Description:This Screen is used to generate Reports of Various Types basing on the parameters passed.

Tables Referred:

Table Name Select Insert Update DeleteDealer_Master Dlr_Prtnr_Detls Commodity_Master


SL.No. Web Bean Name Application Module Method Name1. None



1. None

Packages Referred:


Page 57 of 77



Reports Called : RepLstNewRegRepLstCmdtyDlrsRepLstBsnsTypeRepLstTaxIncRepLstChngRepLstDlrTypesRepDlrDetails

Screen Layout :


Sl.No

Field Name

Table/ Column

Validations

Specifications*


Default Value

1. Registration Number

Dealer_Master:Tin_Grn

Query Text item Q N None

2. Name Dealer_Master:Firm_Name

ADD Text item IQ N None

3. Status Dealer_Master: Occpncy_Status


4. Period From


QUERY Text Box Q N None

5. Period To


QUERY Text Box Q N None

6. Commodity Traded



Page 58 of 77

Registration Number : Name:

Period From: Period To:

Status:

Commodity Traded:

Dealer Type:

Nature of Business:

Status of Business:

Report CANCEL


7. Dealer_Type

Dealer_Master:




Specifications:


Functionality: This screen is used to generate Reports If the Registration Number is entered then the Name is automatically populated

and when Report button is clicked then the Dealer Detail Report is generated. If the Period From and Period To and the status is entered then it will call the

Report (List of Registrations/Cancellations depending on the status) If Commodity traded is entered then it will generate the Commodity based Report. If Dealer Type is entered then it will generate the Dealer Type Report. If Nature of Business is entered then it will generate the report of The Dealers of a

particular business type. If Status of Business is entered then it will generate the Report (List of

Govt./Pvt/Public Company/Sole Proprietors/Partners etc.) There should be atleast 1 of the above conditions satisfied. The cancel button clears the screen. The Report button will generate the Report.

Page 59 of 77


APPENDIX - A

Context Diagram

Page 60 of 77

DEALER

Registration Cancellation

Change inRegistration

Transfer o fBusiness

Rules Master CommodityMaster

Return

Assessment

Check Post

Audit

AppealTransfer o fCompact 2020to VAT

COMPACT2020

Forms Master

Back officeFunctions

Refunds

PerformanceEvaluation

DEALER

DATABASE

MIS Reports List of Manufacturers List of Liquor Dealers List of Auctioneers List of Start up Dealers List of Dealers having Incentives List of Exporters List of Public ,Local,Govt.Bodies List of CST dealers List of Voluntary Registered Dealers List of TOT dealers registered in the

Month List of Cancellations List of Pending Registrations List of LTCU Dealers List of top dealers in the division Commodity w ise dealers

Identification of dealers for compulsory VAT/TOT system- Compulsory list of VAT dealers (database table)- Compulsory list of TOT dealers (database table)- History table of VASTISPre-Registration activity for VAT system

- VAT 101 Notice- VAT 109 Notice Cancellation of Registration

- VAT 110 Notice Updated Dealer Master- Updated Notices table VAT RC Recovered and Cancelled- Updated Dealer Master VAT 108 form- Updated TOT Dealer table TOT 013 formRegistering dealers TOT 014 form- RC is generated (VAT 105/TOT 003)- Updated TOT Dealer- Updated VAT Dealer- Updated Dealer Master- Updated Acknowledgement Master- Updated Notices table- VAT 102Changes in Registration Details

- Updated Dealer Master -VAT 113- Updated Dealer History - VAT 114- Updated Registration Notice –Amended RC- VAT 113


E-R Diagram

Page 61 of 77

1 to

Lookup_Type

Type V(04) pkDescription V(60)Created_By V(15)Created_On DateUpdated_By

REGISTRATION

Lookup_Code

Type Varchar2 pkCode Varchar2 pkDescription Varchar2Created_By V(15)Created_On DateUpdated_By V(15)Updated_on Date

Grn_Master

Grn_num V(10)pkBsns_Cmnc_Date Datetxpyr_rfrnc1_Grn V(10)txpyr_rfrnc2_Grn V(10)Rfrnc!_Name v(60)Rfrnc2_Name V(60)Prv_Ann_trnovr NDt_xcd_Thrshold DateCreated_By C(15)Created_On DateUpdated_By C(15)Updated_on Date

1 to 1

1 to M

1 to 1

Dlr_Brnch_Dtls

Tin_Grn V (10) pk Bsns_Type V (4) Bsns_Cd V (4) Sl_Num Number pkDoor_Num V (20)Street_Num V(20), Location V(20), Town V (30), District V (30), Pin Number, Phone V (60), Fax V (15), Email V (60), Adrs_Wthn_State V (1) Rc_Num V (20), Created_By V (15) Created_Dt DateUpdated_By V(15)Updated_on Date

Dealer_Master

Ack_No V(10)Tin_Grn V(10)pkOwner_FName V(30)Owner_Mname V(30)Owner_Lname V(30)Firm_Name V(30)Occpncy_Status V(4)Status_Cd V(04)Appln_Rcpt_Dt dateRC_Issd_Date DateRC_Eff_Date DateRcpt_PA_Date DateRcpt_RA_Date DateRC_Reff_Date DateUnit_Cd V(04)Circle_Cd V(04)Div_Code V(04) Reg_Status V(04) PA_Remarks V(250)RA_Remarks V(250)Created_By C(15)Created_On DateUpdated_By C(15)Updated_on Date

Dlr_Bank

tin_Grn V(10)pkLocn_Type V(04)Locn_Code V(04)pkAccount_Num V(15)pkCreated_By V(15)Created_On DateUpdated_By V(15)Updated_on Date

Tin_Master

Tin _num V(10)pkAcBook_Lang V(04)Acc_Cmptrzd V(1)frst_txble_Supp_Date Datetxble_supp_trnovr_l3 Ntxble_supp_trnovr_l12 Ntxble_supp_trnovr_n3 Ntxble_supp_trnovr_n12 Nntcptd_xmptd_trnovr_n12 NStartup_bsns_yn V(1)Vlntry_Reg BooleanReg_Prior_Txble_Supp BooleanCST_Applied_YN V(1) Cst_No V(12)Proff_Tax_num V(20)Ip_Xcd_Op_Remark V(500) Tax_Incntv V(04) Created_By C(15)Created_On DateUpdated_By C(15)Updated_on Date

Photo_Master

Dlr_Tin A(10)Status_Type V(04)Status_Cd V(04)First_Name V(30)Mid_Name V(30)Last_Name V(30)Dlr_photo BlobDlr_Sign BlobCreated_By C(15)Created_On DateUpdated_By C(15)Updated_on Date

1 to 1

1 to M

Commodity_Master

Cmdty_Code V(04) pkCmdty_Desc V(25)Cmdty_tax_Rate NCreated_By V15)Created_On DateUpdated_By V(15)Updated_on Date

Dlr_Cmdty_Link

tin_Grn V(10) pkCmdty_Code V(04)pkCreated_By V(15)Created_On DateUpdated_By V(15)Updated_on Date

1 to M

Dealer_History

Tin_Grn V(10)Field_Name V(30)Field_Value V(30)Chng_Date date

1 to 1

Tin_Weightage

Tin_Num V(10) pk Activity_Ind V(50)Xmptd_Ind V(50) Volntry_Ind V(50) Startup_Int V(50) Cst_Ind V(50) Refund_Ind V(50) Incntv_Ind V(50) Regn_Ind V(50) Sat_Ind V (50) Created_By V (15) Created_Dt Date Updated_By V(15)Updated_Dt Date

1 to 1

Dlr_Prtnr_DetlsTin_Grn V (10) pkBsns_Status V (4) Sl_Num Number pk First_Name V (30) Middle_Name V (30), Last_Name V (30), Father_Name V (60), Pan_Num V (16) Date_Of_Birth Date, Edu_Qualif V(60), Interest_In_Bsns V(500), Oth_Bsns_In_StateV(500) Bsns_Out_State V(500), Pres_Door_Num V(20), Pres_Street_Num V(20), Pres_Locn V(20), Pres_Town V(30), Pres_Dstrct V(30), Pres_Pin Number Pres_Phone V(60), Pres_Fax V(15), Pres_Email V(60), Prmt_Door_Num V(20), Prmt_Street_Num V(20), Prmt_Locn V(20), Prmt_Town V(30), Prmt_Dstrct V(30), Prmt_Pin Number Prmt_Phone V(60), Prmt_Fax V(15), Prmt_Email V(60), Identity V(500), Rfrnc1_Name V(60), Rfrnc1_Adrs V(500), Rfrnc2_Name V(60), Rfrnc2_Adrs V(500), Created_By V(15) Created_Dt Date Not Null, Updated_By V(15), Updated_Dt Date, Created_By C(15)Created_On DateUpdated_By C(15)Updated_On Date

Dlr_Cncl_Detls

Tin_Grn V(10) pk Bsns_Clsd_Dt Date, Txble_Trnovr_Lst3 Number, Txble_Trnovr_Lst12 Number, Cncl_Dt_From Date, Tot_Regn_Yn V(1), Cst_Apply_Yn V(1), Cncl_Reason V(500), Cncl_Appln_Dt Date, Appln_Rcpt_Dt Date, Arrears V(30), Ret_Proc_Sec V(30), Ret_Issd V(30), Ret_Rcvd V(30), Cncl_Verfn V(1), Cncl_Dt Date, Vat122_Issd_Dt Date, Vat123_Issd_Dt Date, Vat124_Issd_Dt Date, Cncl_Pa V(15), Cncl_Ra V(15), Created_By V(15) Not Null, Created_Dt Date Not Null, Updated_By V(15), Updated_Dt Date,

Acknowledgement Ack_No V(10) , Ack_Tin V(10), Ack_Formno V(6), Ack_Remarks V(100), Ack_Created_By V(20), Ack_Created_On Date, Ack_Updated_By V(20), Ack_Updated_On Date, Dlr_Name V(60)


APPENDIX - B

Table Structure

List of Tables

Sl. No. Table Name Description Short Code

1. Dealer_master Dealer Master DM2. Tin_master Tin Master TM3. Rules_master VAT Rules Master RM4. Commodity_master Commodity Master COM5. Act_master VAT Act Master ACM6. Form_master Form Master FM7. DDO_master DDO Master DDOM8. GRN_master GRN Master GRN9. Dealer_history Dealer History DH10. Dlr_Cmdty_Link Dealer Commodity ADM11. Dlr_Bank Dealer Bank BM12. Tin_Weightage Tin Weightages BRM13. Lookup_types Look Up Types LKT14. Lookup_Codes Look Up Codes LKC15. Photo_Master Photo Master PM16. Location_Adrs_Master Location Address Master LAM17. Dlr_Prtnr_detls Dealer Partner Details DPD18. Dlr_Brnch_Detls Dealer Branch Details DBD19. Dlr_Acty_Detls Dealer Activity Details DAD20. Dlr_Cncl_Detls Dealer Cancel Details DCD

Page 62 of 77


APPENDIX - C

Codes and Codification - Not Applicable -

S.No Field/Attribute Codes1.

Page 63 of 77


APPENDIX - D

Report Layouts

Report name: RpPreLstVatDlr

XxxGovernment of Andhra Pradesh

List of Identified VAT Dealers

Circle : Xxxxxxxxxxxxxx Date: DD-MM-YYYYDivision : Xxxxxxxxxxxxxx Time: MM:HH:SS

APGSTNo Name Address

XXXXXXXX XXXXXXXXXXXXXX XXXXXXXXXXXXXXXX Xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx

XXXXXXXX XXXXXXXXXXXXXX XXXXXXXXXXXXXXXX Xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx

XXXXXXXX XXXXXXXXXXXXXX XXXXXXXXXXXXXXXX Xxxxxxxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxx

Page X of Y

Page 64 of 77

Logo


Report name: RpPreLstTotDlr


List of Identified Tot Dealers


APGSTNo Name Address

XXXXXXXXX XXXXXXXXXXXXX XXXXXXXXXXXXXXXX Xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx

XXXXXXXXX XXXXXXXXXXXXX XXXXXXXXXXXXXXXX Xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx

XXXXXXXXX XXXXXXXXXXXXX XXXXXXXXXXXXXXXX Xxxxxxxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxx

Page X of Y

Report name: RpLstVatDlr

Page 65 of 77

Logo



List of VAT Dealers


TIN Name Date of Regn. Commodity Traded

9999999999 XXXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXX XXXXXXXXXXXXXXX

9999999999 XXXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXX XXXXXXXXXXXXXXX

9999999999 XXXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Page X of Y

Report name: RpLstTotDlr

Page 66 of 77

Logo



List of TOT Dealers


GRN Name Date of Regn. Commodity Traded

XXXXXXXXX XXXXXXXXXXXXXX DD-MM-YYYYXXXXXXXXXXXXXXX XXXXXXXXXXXXXXX

XXXXXXXXX XXXXXXXXXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXX XXXXXXXXXXXXXXX

XXXXXXXXX XXXXXXXXXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXX

XXXXXXXXXXXXXXX

Page X of Y

Report name: RpLstCSTDlr


Page 67 of 77

Logo


List of CST Dealers


TIN CSTNO Name Date Commodity of Regn. Traded

9999999999 XXXXXXXX XXXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXX XXXXXXXXXXXXXXX



Page X of Y

Report name: RpLstLiqDlr


Page 68 of 77

Logo

Logo


List of Liqour Dealers


TIN Name Date of Regn.

9999999999 XXXXXXXXXXXXXXX DD-MM-YYYY



Page X of Y

Page 69 of 77

Documents

Hyd It High Level Design Template