Functional Specifications

Wipro

Confidentiality
This document is the property of WI, who owns the copyright thereof. The
information in this document is given in confidence and without the written
consent of WI, given by contract or otherwise, this document must not be
copied, reprinted or reproduced in any material form, either wholly or in
part. Also the contents of this document or any methods or techniques
available there from, must not be disclosed to any third party whatsoever

Functional
Specification

SAN_FS_SD_AUTO
GENERATION
OF
EXCISE INVOICE_19_1.0
Table of Contents

1.0

PURPOSE................................................................................................................. 3

2.0

ROLE......................................................................................................................... 3

3.0

TEMPLATE FOR CAPTURING FUNCTIONAL SPECIFICATIONS.............3

3.1

HEADER............................................................................................................................................................3

SPECIFICATION NAME.......................................................................................................3
FUNCTIONAL MODULE.......................................................................................................3
3.2 OBJECT VERSION HISTORY............................................................................................................................4
3.3 INPUT / HEADER / SUB-HEADING / OBJECT BODY...................................................................................4
3.3.1
Object Name:....................................................................................................................................4
3.3.2
Heading:
PGI Proforma & Excise Invoice Creation.......................................................4
3.3.3
Sub-Heading (if any):....................................................................................................................4
3.3.4
Sub-Heading (if any):....................................................................................................................4
3.4 PROGRAM FUNCTIONS....................................................................................................................................4
3.4.1
Pls. use the FS Format/ Program Logic cum selection screen template in this
way
4
3.5 ANY SPECIAL REMARKS WRT PROGRAM LOGIC OTHER THEN GIVEN IN EXCEL SHEET............................5
3.6 ASSUMPTIONS/ DEPENDENCIES/ CHECKS/ FILTERS/ HARD CODED FIELDS:.......................................6

4.0

OPTIONS FOR PROGRAM (TO BE TICKED).................................................6

4.1 OUTPUT: A) LIST.....................................................................................................................................6

4.2 EXECUTION:................................................................................................................................................6
B) BACKGROUND.......................................................................................................................................................6
4.3 SAMPLE OBJECT (IF ANY, TO BE ATTACHED)..........................................................................................6

5.0

PRODUCTION CHECKLIST.................................................................................6

Page 2 of 7

Functional
Specification

SAN_FS_SD_AUTO
GENERATION
OF
EXCISE INVOICE_19_1.0

1.0 Purpose

The purpose of this development is to develop the functionality to enable the

business in do the PGI of the outbound delivery if it is complete and ready for
dispatch and also create the Proforma invoice and the corresponding excise invoice
and also issue the excise invoice print out.

2.0 Role

Fn co to provide logic / source of data

Developer translate the logic provided by the function consultant into program
code.

3.0 Template for capturing Functional specifications

3.1

Header

Specification Name
Specification Number
Specification Type
(Report / Module Pool / Interface
/ BDC / SAP Script / Dictionary/
Enhancements)

AUTO GENERATION OF EXCISE INVOICE

SAN_FS_SD_AUTO
GENERATION
EXCISE INVOICE_19_1.0
Process Development

Functional Module
Priority (H /M /L)

Functional Consultant Name

Arun Kumar

Technical Consultant Name

Sumil Sinha

Functional / Technical Estimated

Person Days
For Modification, name of
current report / object

Page 3 of 7

OF

Functional
Specification

3.2

SAN_FS_SD_AUTO
GENERATION
OF
EXCISE INVOICE_19_1.0

Object Version History

(To be filled in by the Programmer after the Development or Modification is

complete)
Objects Created / Modified

Program Name

Development Class

Transaction Code

Completion Date

Actual Person Days

3.3
3.3.1
3.3.2
3.3.3
3.3.4

3.4
3.4.1

New
Version

Previous
Version

Date of
change

Input / Header / Sub-Heading / Object Body

Object Name:
Heading:
PGI Proforma & Excise Invoice Creation
Sub-Heading (if any):
Sub-Heading (if any):

Program Functions
Pls. use the FS Format/ Program Logic cum selection screen
template in this way

After the delivery document is created and the document is complete then the user will check the details of the
delivery and then do the Post goods issue and Proforma invoice and then excise invoice through this transaction and
can also issue a print out of the excise invoice.
There will be three radio buttons to process the delivery:
1) PGI Details: Once user inputs the delivery number and executes this radio button
2) Process Proforma and Excise Invoice

Page 4 of 7

Functional
Specification

SAN_FS_SD_AUTO
GENERATION
OF
EXCISE INVOICE_19_1.0

3) Print Excise Invoice

Note: For all the options, input is the delivery number.
Step 1: PGI Details
On executing the radio button PGI details,
below:
Delivery Number
Ship to Party code
Ship to Party name
Material Desc
Route Desc
Truck No
Transporter code
Transporter Name
-

the system will give the details of the delivery number as mentioned
LIKP-VBELN
ADRC-NAME1
VBPA-KUNNR
LIPS-ARKTX
TVROT- BEZEI
LIKP-TRAID
VBPA-LIFNR
ADRC-NAME1

Step 2: Process Proforma and Excise Invoice

On executing the radio button Process Proforma and Excise Invoice radio button, the system does the PGI of the
delivery if the document is complete in all respects and if the PGI is already done then the system will issue a
message as PGI is already done for the delivery and if the PGI is not done then the system processes the PGI and
then the Proforma Invoice with document type ZPBC in case of factory sales and JEX in case of stock transfers
and then the system will process the excise invoice and then user can take the print out of the excise invoice at the
end of the transaction.
2.1 For the PGI of the delivery
Pass the delivery number into the BAPI and then do the PGI
2.2 Once the PGI of the delivery is done run the BAPI for invoice where LIKP-LFART = NL then RV60A-FKTYP
= JEX else RV60A-FKTYP = ZPBC and then save the Proforma invoice.
2.3 Once the Proforma invoice is saved then run the BDC for the Excise Invoice creation by passing the VBRKVBELN and check if MARA-SPART is not equal to 51 then pass the sub transaction type as Z1 else space and
also pass the time as document time plus 20 minutes into J_1IEXCHDR-REMTIME and save.
Step 3: Print Excise Invoice
On executing the radio button Print Excise Invoice radio button, the system takes you to next screen and displays the
delivery number for which PGI has already been done and Proforma invoice already created and the excise invoice
already created and then the user can take the print out of the excise invoice.

3.5

Any special remarks wrt Program Logic other then given in

excel sheet

3.6

Assumptions/ Dependencies/ Checks/ Filters/ Hard coded

fields:

Page 5 of 7

Functional
Specification

SAN_FS_SD_AUTO
GENERATION
OF
EXCISE INVOICE_19_1.0

4.0 Options for program (to be ticked)

4.1

OUTPUT:

A) List
B) Grid Display
C) Interactive
D) Direct Download

Filename if (D) is ticked above Grid Display

4.2

EXECUTION:
B) Background

4.3

SAMPLE OBJECT (if any, to be attached)

5.0 Production Checklist

Item

Check
(tick)

User Sign-Off In QA after Testing

Program Documentation
ABAP programmer

done

by

Authorization Profiles to which the

Transaction Code is to be attached
All Components Related
Development released

To

The

Transport Request Number generated

Test Case attached
Test results Dev/ Qual / Prod (To be
attached in E-help line)

Page 6 of 7

Notes (Names of
reports, tr. code, etc.)

Functional
Specification

SAN_FS_SD_AUTO
GENERATION
OF
EXCISE INVOICE_19_1.0

___________________
Requested By (Originator)

___________________
Functional Consultant

_____________________
Technical Consultant

Page 7 of 7