You are on page 1of 10

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_SPECIAL
DISCOUNT_18_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:
SPECIAL DISCOUNTS............................................................................................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
5
3.5 ANY SPECIAL REMARKS WRT PROGRAM LOGIC OTHER THEN GIVEN IN EXCEL SHEET............................9
3.6 ASSUMPTIONS/ DEPENDENCIES/ CHECKS/ FILTERS/ ‘HARD CODED’ FIELDS:.......................................9

4.0

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

4.1 OUTPUT: A) LIST.....................................................................................................................................9
4.2 EXECUTION:................................................................................................................................................9
B) BACKGROUND.......................................................................................................................................................9
4.3 SAMPLE OBJECT (IF ANY, TO BE ATTACHED)..........................................................................................9

5.0

PRODUCTION CHECKLIST.................................................................................9

Page 2 of 10

Functional
Specification

SAN_FS_SD_SPECIAL
DISCOUNT_18_1.0

1.0 Purpose

The purpose of this development is to develop the functionality to enable the
business in order to pass on different types of special discount to a particular market
segments (Trade) at a particular point of time and at same time to issue consolidated
Credit Memo.

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
QTY DISCOUNT CALCULATION

Specification Name
Specification Number

SAN_FS_SD_SPECIAL DISCOUNT_18_1.0

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

Process Development

Functional Module
Priority (H /M /L)

H

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 10

Functional
Specification
3.2

SAN_FS_SD_SPECIAL
DISCOUNT_18_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:
SPECIAL DISCOUNTS
Sub-Heading (if any):
Sub-Heading (if any):

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

At the month the sales officer issues the credit note based on the slab qty discount. The system calculate the base on
the below mentioned parameters.
Note: 1) No CST / VAT / Additional VAT are applicable in any of the discounts mentioned below.
2) All the discounts are applicable in case of distribution channel ‘10’ – Trade.
Types of Special Discounts:
1. Monsoon Discount

Page 4 of 10

Functional
Specification

SAN_FS_SD_SPECIAL
DISCOUNT_18_1.0

2. Festival Discount…if two or more festivals come in one month then they would be grouped under one discount
3. Exclusive /Loyal Dealer Discount. Mapped through price group in the customer master with value ‘07’
4. Rake Discount
5. Depot Discount
6. Stockist Discount- Mapped through price group in the customer master with value ‘06’
7. Super Stockist / Wholesaler Discount- Mapped through price group in the customer master with value ‘05’
8. Retailer Discount- Mapped through price group in the customer master with value ‘04’
9. Special Discount
10. PPC Discount- If the customer lifts the PPC material qty > = 90% of the PPC then he is entitled for PPC
discount. PPC discount can not be processed through this program.
11. To- Pay Discount- Based on Inco-terms…FR2 inco-terms
12. Freight Discount
13. Super Retailer Discount- Mapped through price group in the customer master with value ‘03’
13. Sales Promoter Discount—SA is not created as a customer and hence cannot be processed through this program.
All the type of discount would be mapped through order reason and the condition types would be maintained based
on the order reason.
Order Reason
D01
D02
D03
D04
D05
D06
D07
D08
D09
D10
D11
D12
D13
D14

Description
Monsoon Discount
Festival Discount
Exclusive /Loyal Dealer Discount
Rake Discount
Depot Discount
Stockist Discount
Super Stockist / Wholesaler Discount
Retailer Discount
Special Discount
PPC Discount
To- Pay Discount
Freight Discount
Super Retailer Discount
Sales Promoter Discount

Condition Type
ZSLD
ZSLD
ZSLD
ZSLD
ZSLD
ZSLD
ZSLD
ZSLD
ZSLD
ZPPD
ZSLD
ZSLD
ZSLD

If Order reason is ‘D11’ then pick only those billing documents, VBRK- VBELN where VBRK-INCO1 = ‘FR2’.
If Order reason is ‘D13’ then pick only those billing documents, VBRK-VBELN where VBRK- KONDA = ‘03’.
If Order reason is ‘D08’ then pick only those billing documents, VBRK-VBELN where VBRK- KONDA = ‘04’.
If Order reason is ‘D07’ then pick only those billing documents, VBRK-VBELN where VBRK- KONDA = ‘05’.
If Order reason is ‘D06’ then pick only those billing documents, VBRK-VBELN where VBRK- KONDA = ‘06’.
If Order reason is ‘D03’ then pick only those billing documents, VBRK-VBELN where VBRK- KONDA = ‘07’.
Input Parameters with Two Radio buttons:
1. Process Credit note
2. Display Report
On selecting the radio button Process credit note, system should prompt the user with the following fields
 Sales Organization
VKORG
 Distribution channel
VTWEG
 Division
SPART
 Region of Del Plant
WKREG
 Plant
WERKS

Page 5 of 10

Functional
Specification


Order Reason
Date
Posting Date

SAN_FS_SD_SPECIAL
DISCOUNT_18_1.0
-

AUGRU
FKDAT
BUDAT

On executing the above, system should process the same as follows:
Step 1: Calculation from Header table
Input parameters in VBRK
Sales Organization
Distribution channel
Billing Date
-

VKORG (As per input parameters)
VTWEG (As per input parameters)
FKDAT (As per input parameters)

Following fields should be fetched:
VBELN
Billing Document
VKORG
Sales Organization
VTWEG
Distribution Channel
FKDAT
Billing date for billing index
BELNR
Accounting Document Number
BLAND
State (plant)
KUNRG
Payer
Step 2: Calculation from Item table
From the above data following field will be the input parameter for the next selection in the table VBRP
VBELN Billing Document
Following fields should be fetched:
VBELN
Billing Document
FKIMG
Actual Invoiced Quantity
MEINS
Base Unit of Measure
MATNR Material Number
WERKS
Plant
Step 3: Clubbing the above steps
Output parameters from Step 1 and Step 2 should be clubbed based on the field VBELN (Billing document). Final
output will be
VBELN
Billing Document
VKORG
Sales Organization
VTWEG
Distribution Channel
FKDAT
Billing date for billing index
BELNR
Accounting Document Number
BLAND
Region (State)
KUNRG
Payer
FKIMG
Actual Invoiced Quantity
MEINS
Base Unit of Measure
MATNR Material Number
WERKS
Plant
Also to fetch
Customer Name (NAME1) from KNA1 based on KUNRG and
Material Description (MAKTX) from MAKT based on MATNR
And check the plant (WERKS) of the billing documents and if the plant is different then the system should create
two credit notes for the customer and after the quantity cumulation

Page 6 of 10

Functional
Specification

SAN_FS_SD_SPECIAL
DISCOUNT_18_1.0

Eg: If the customer is billed for 100 MT in depot 1901 and 200 MT in depot 2901, then the system should check for
the condition record as defined in VK11 and then multiply rate * 100 MT (based on the plant in the invoice) as one
credit note and rate* 200 MT as another credit note.
Output:
1) Output should be in ALV Grid form.
2) Summation for the field Quantity (FKIMG)
a) For every material
b) For every customer
c) For each plant
3) On double clicking the customer (KUNRG), other details should be populated in ALV Grid list.

Sample Output
Sales
Organization
1000
1000
1000
1000
1000
1000
1000
1000

Distribution
Channel
10
10
10
10
10
10
10
10

Continuation
A/c Doc Material
No.
Number
9000001

FERT1

9000002

FERT1
FERT1

9000003

FERT2

9000004

FERT2
FERT2

9000005

FERT1

9000006

FERT1

Plant
1000
1000
1000
2000
2000
2000

Customer
Code
1100
1100
1100
1100
1100
1100
1102
1102

Material Description
BIRLA GOLD OPC 43
GRADE
BIRLA GOLD OPC 43
GRADE
BIRLA GOLD OPC 43
GRADE
BIRLA GOLD OPC 53
GRADE
BIRLA GOLD OPC 53
GRADE
BIRLA GOLD OPC 53
GRADE
BIRLA GOLD OPC 43
GRADE
BIRLA GOLD OPC 43
GRADE

Customer
Name
ABC Ltd
ABC Ltd
ABC Ltd
ABC Ltd
ABC Ltd
ABC Ltd
XYZ Ltd
XYZ Ltd

Quantity

Unit of
Measure

500

MT

400

MT

900

MT

200

MT

100

MT

300

MT

800

MT

900

MT

1st Level output should show only items marked in yellow
On double clicking system should give complete output
Apart from the above list, following columns need to be appended
1) Rate from condition records based on the order reason.
2) Credit Note Value (Qty in yellow color multiplied with Rate)
Execution of BDC

Page 7 of 10

Billing
Document
14000001
14000002

Billing date
01.01.2009
01.01.2009

14000003
14000004

01.01.2009
01.01.2009

14000005
14000006

01.01.2009
01.01.2009

Functional
Specification

SAN_FS_SD_SPECIAL
DISCOUNT_18_1.0

Once the user validates the record and upon execution / F8 the system should check whether, these credit notes are
already generated. This can be checked by verifying whether the input month is already appended in the field
Update from- DATAM and Update To-DATAM.
If it is blank, then system should prompt a message “Do you want you process for generating the Credit Notes",
On clicking OK, system should process the BDC
Step-6-Credit Note Processing through BDC
A. Creation of Credit note request (VA01)
 Order Type – ZDCM- Depot, ZSCM- Factory
 Sales Organization – 1000
 Distribution Channel – 10 (Trade)
 Sales Office -1000…
 Sold to Party
 Order Reason- AUGRU
 Target Qty
 Material
 Plant
 Alternate Tax Classification – ‘0’
 Save
Note: If VBRP-WERKS = 1000, 2000, 3000, 5000, 6000, 7000 then take the document type as ZSCM
else ZDCM.
B. Creation of Credit Note – (VF01)



Select the billing type (ZBCM- Depot, ZFCM- Factory) - FKART
Enter the Credit note request # - VBELN
Press Enter
Save.

Note: If VBAK-AUART = ZDCM then FKART should be ZBCM and if it is ZSCM then FKART
should be ZFCM.
Finally,
(1) System should output the list of credit notes generated.
(2) If a credit note is generated based on corresponding invoice for a particular type of discount then the system
should not generate the credit note.

3.5

Any special remarks wrt Program Logic other then given in
excel sheet

3.6

Assumptions/ Dependencies/ Checks/ Filters/ ‘Hard coded’
fields:

4.0 Options for program (to be ticked)
Page 8 of 10

Functional
Specification

4.1

OUTPUT:

SAN_FS_SD_SPECIAL
DISCOUNT_18_1.0

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 9 of 10

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

Functional
Specification

SAN_FS_SD_SPECIAL
DISCOUNT_18_1.0

Requested By (Originator)

___________________
Functional Consultant

_____________________
Technical Consultant

Page 10 of 10