3.4 FunctionalSpecification

7/30/2019 3.4 FunctionalSpecification

1/12

Ernst & Young Private Limited 2012. All rights reserved. Confidential and proprietary

Page 1 of 12

Project :

Functional SpecificationFormat No/ Rev:

Version:

Specification No:

Development No:

Business Process No:< BBP Reference in which the related process is

captured>

Issue Date

(dd/mm/yyyy):

In Preparation ReviewApproved Released

Revision History

Version Date Description of changes

< Provide a brief of the reason for the change in the version>

Responsible

To be discussed To be discussed

Section I: Justification

Area:

Module

name:

Sub area:

Date :

Requested by:


2/12


Page 2 of 12

Brief description:

Generic question:

Impact of not creating the program:

Legal requirements will not be fulfilled

Lack of information required for the business

Lose functionality compared to the old system

Others

Is there any alternative in the standard system:

Yes No

Describe the alternative found: < If answer to the above is yes then give a description of the alternative

in details>

Reason why this alternative was not acceptable:

Performance problems Complexity

Others:

Program type:

Report Module Pool Interface

Enhancement Conversion Form

Application Development Others

Priority:

High/mandatory Medium/recommended Low/optional

Charateristics < If

the development is a

report please

provide whether its

a Drill Down or ALV.

In case of any other

development pleaseselect Others>

Drill Down ALV Others


3/12


Page 3 of 12

Frequency:< Frequency at which the

business transaction/report is carried out for

which this development is to be made>

Daily Weekly Monthly

Biweekly Other:

Only for Interfaces:< Describe the details of

interface>

Type of interface:

Direction of interface:

Real-Time Batch

Inbound Outbound Both

Sign off Functional Specification

Prepared By

Date

Comments

Team LeadDate

Lead ConsultantDate

Approved by Project Management Team(in case of Application development)

Received Team Lead/ Lead Consultant

Date


4/12


Page 4 of 12

Section II: (a) Business Needs & Requirement (Please use this section for describing the business requirement in

detail preferably with flow diagram)

Description and PurposeThe enhancement is developed to track different sale tax form issued by saletax

department

Business Process Detail

C Form is given by the buyer to the supplier of goods in case it is an out-of-state (ex. OMS - Outside Maharashtra State)

sale that attracts CST (Central Sales Tax).

If you as a buyer provide C Form, you have to pay lower CST (ex. 3% CST in lieu of 9% CST).

However, it is considered the supplier's responsibility (funny policies) to collect the C Form from the buyer, failing which

he will have to pay the differential Sales Tax. i.e. he will get penalised if the buyer defaults.

C Forms are issued by Sales Tax Department which have to be collected from there by the buyer so that he can give it

to the supplier for CST transaction.

Goods-in-Transit transactions also attract CST, hence C Forms come in play.

Authorization requirements:< State if any additional authorization will be needed if the development is implemented>

Section III: Only For Enhancements

Name Description

Process Logic

C Form is given by the buyer to the supplier of goods in case it is an out-of-state (ex. OOS - Outside Orissa State)

sale that attracts CST (Central Sales Tax).There will er two T-Codes

1. Create and close c-form

2. Change and display


5/12


Page 5 of 12

Screen 1:

SCREEN 2 FOR CHANGE AND DISPLAY


6/12


Page 6 of 12

NOTE: Add entry tax amount, debit note or credit note issued against any

invoice in table control.

A status check box will be there at the end which will be X automatically if

form amount is equal to total amount or the user can also close the invoice by

clicking on status check box and put their remarks in remarks field.

Create different section in screen

If Entry tax is .5 % then we need form E15

Form Tracking System Sales

Fields Char Description Technical Details

Receive No. I/O User Should enter manualy

Add entry tax amount, debitnote or credit note issued

against any invoice ,Statuscheck .in table control.

Create different sections aboxes and include the fiellayout header screen e.g.

1. Form details2. Organization deta3. Customer details


7/12


Page 7 of 12

Receive ID Output System generated id

use number range objectto generate system aunique no.

Receive DateI/O with f4help

State/Central

I/O with f4

help

CompanyCode

I/O with f4help

user should enter company code manually orthrough search help and company codedescription will appear in another field

PlantI/O with f4help

Sales AreaI/O with f4help

Three fields (Sales org/distribution channel/division)

Customer No.I/O with f4help

enter customer no. and description will appear innext field

AddressI/O with f4help

will come from customer master and user canchange it

R.C. No I/O user should enter after getting formsActualR.C.No. I/O user should enter after getting forms

Form typeI/O with f4help maintain values at domain lebel

Form Details I/O

Contactperson I/O

Show PushbuttonClick on pushbutton will display data in bleow gridbased on certain selection criteria

Billing datefrom and to

I/O with f4help

Logic for data selection and display in Grid.

Once the user click on SHOW button, based on company code,sales area,customer code,billing date select all theinvoices of the particular customer which has been raised during the selected period from table vbrk an vbrp,

How to get the form details of particular sales?

Goto va03 ->header->Billing document->alt tax classification

See the below screen


8/12


Page 8 of 12

Get all the sales order created for the invoices and check the alt tax classification field,Fields details for grid

Billing No->Invoice no (VBRK-VBELN)Billing Dt-Invoice Dt.(VBRK-ERDAT)Taxable amount, tax amount total amount are condition basedForm amountmanually entered based on hard copy of form receivedShortage = Total amount form amount.

Add New Add new lines

SAVE Save data in custom z table

EXIT Exit fr

Structure of Custom Table

This field denoteswhich form is usedfor the sales


9/12


Page 9 of 12

Header Table


10/12


Page 10 of 12


11/12


Page 11 of 12

Item Table


12/12


Page 12 of 12

1. Input details, (Selection screen / screen design).Selection Parameters will be:< Provide the selection parameters at screen level>

2. Output format, (Report layout, Form Layout).< Provide the layout where applicable>

3. Flow Diagram.< Provide a flow diagram for an easier understanding of the complete logic>

Sign-Off and Acceptance of developed object

Names and Signatures

_______________________________________________________________________________________Team Lead

_______________________________________________________________________________________

Lead Consultant

3.4 FunctionalSpecification

Documents

Transcript of 3.4 FunctionalSpecification