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_P004_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............................................................................................................................3
3.3 INPUT / HEADER / SUB-HEADING / OBJECT BODY...................................................................................4
3.3.1
Object Name:....................................................................................................................................4
3.3.2
Heading:
CREDIT NOTE FOR NIL BALANCE.....................................................................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............................8
3.6 ASSUMPTIONS/ DEPENDENCIES/ CHECKS/ FILTERS/ HARD CODED FIELDS:.......................................8

4.0

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

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

5.0

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

Page 2 of 10

Functional
Specification

SAN_FS_SD_P004_1.0

1.0 Purpose

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

business in order to pass on nil balance discounts to a particular market segments
(Trade) at the month end and at same time to issue consolidated Credit Memo if the
customer outstanding is zero by considering all the debit and credit notes and
payments received from the customer through all modes of payment.

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

AUTOMATIC SETTLEMENT OF THE REBATE

AGREEMENTS

Specification Number

SAN_FS_SD_P004_1.0

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

Process Development

Functional Module
Priority (H /M /L)

Functional Consultant Name

Arun Kumar

Technical Consultant Name

Kiran

Functional / Technical Estimated

Person Days
For Modification, name of
current report / object

3.2

Object Version History

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

complete)
Objects Created / Modified

New

Page 3 of 10

Previous

Date of

Functional
Specification

SAN_FS_SD_P004_1.0
Version

Program Name

Development Class

Transaction Code

Completion Date

Actual Person Days

Version

3.3

Input / Header / Sub-Heading / Object Body

3.3.1
3.3.2
3.3.3
3.3.4

Object Name:
Heading:
CREDIT NOTE FOR NIL BALANCE
Sub-Heading (if any):
Sub-Heading (if any):

3.4
3.4.1

change

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

At the month end the sales officer issues the credit note based on the slab qty discount for the nil balance of the
customer. The system should calculate the base on the below mentioned parameters.
Z table has to be created with the following parameters with a table maintenance generator:
Sales Org VKORG (Primary Key)
Distribution Channel-VTWEG (Primary Key)
Division SPART (Primary Key)
State of Customer- REGIO_AUFT (Primary Key)
Type of Discount B- Nil Balance (Z field)
Qty-From MENGE
Qty To-MENGE
Rate-KBETR
Update From- DATAM
Update To-DATAM
Input Parameters with Two push buttons:

Page 4 of 10

Functional
Specification

SAN_FS_SD_P004_1.0

1. Update Slab rate

2. Process Credit note
On selecting the push button Update slab rate, system should take the user to the Z table maintenance and user can
enter the slabs --- On saving the transaction, the Z table has to be updated.
On selecting the push button Process credit note, system should prompt the user with the following fields
Step1: Create an selection screen with the values as
Sales Org VKORG (Primary Key)
Distribution Channel-VTWEG (Primary Key).
Division-SPART (Primary Key).
State of Customer- REGIO_AUFT (Primary Key)
Plant-WERKS (Primary Key)
FKDAT From- FKDAT
FKDAT To- FKDAT
Process Credit Memo Request (Radio Button)
Process Credit Note (Radio Button)
On executing the above, system should process the same as follows:
Step 2: 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
KUNRG
Payer
Step 3: 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
REGIO_AUFT State of Customer
WERKS
Plant
PRCTR
Profit Center
Step 4: Clubbing the above steps
Output parameters from Step 2 and Step 3 should be clubbed based on the field VBELN (Billing document). Final
output will be
VBELN
VKORG
VTWEG
FKDAT

Billing Document
Sales Organization
Distribution Channel
Billing date for billing index

Page 5 of 10

Functional
Specification

SAN_FS_SD_P004_1.0

BELNR
Accounting Document Number
REGIO_AUFT Region (State)
WERKS
Plant
PRCTR
Profit Center
KUNRG
Payer
FKIMG
Actual Invoiced Quantity
MEINS
Base Unit of Measure
MATNR Material Number
Also fetch Customer Name (NAME1) from KNA1 based on KUNRG and Material Description (MAKTX) from
MAKT based on MATNR.
Based on billing date (FKDAT), billing document VBRK- VBELN system should check the debit and credit entries
of the customer for the given selection date range. After the comparison of the debit and credit entries and if the
credit balance of the customer is greater than or equal to zero, then proceed for that particular invoice.
And if the profit center (PRCTR) of the billing documents is different then the system should create two credit notes
for the customer but after the quantity cumulation i.e., the slab is applicable irrespective of profit center but splitting
of credit notes is based on the profit center.
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 slab as defined in Z table and then multiply rate * 100 MT (based on the profit center 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 profit center
3) On double clicking the customer (KUNRG), other details should be populated in ALV Grid list.
Note: While creating the sales order through BAPI, pass 0 into VBAK- TAXK1 where region (VBRPREGIO_AUFT) of customer is not equal to 35.
Execution of BAPI
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 BAPI
Step-5-Credit Note Processing through BAPI
A. Creation of Credit note request (VA01)
Order Type ZSCM- Factory
Sales Organization 1000
Distribution Channel 10 / 11 / 12 (Trade / Non- Trade /Exports)
Sales Office -1000
Sold to Party
Order Reason- AUGRU
Target Qty
Material
Plant
Shipping Point
Date

Page 6 of 10

Functional
Specification

SAN_FS_SD_P004_1.0

Save

Note: If VBRP-WERKS = 1000, 2000, 3000, 5000, 6000, 7000 then take the document type as ZSCM.

Sample Output
Customer
Code
1100
1100
1100
1100
1100
1100
1102
1102

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

Billing
Document
14000001
14000002

Billing date
01.01.2009
01.01.2009

Credit
Memo Req
10001
10002

14000003
14000004

01.01.2009
01.01.2009

10003
10004

14000005
14000006

01.01.2009
01.01.2009

10005
10006

Continuation
Profit
Center

Material
Number

1000

FERT1

1000

FERT1

1000

FERT1

2000

FERT2

2000

FERT2

2000

FERT2
FERT1
FERT1

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

Quantity

Unit of
Measure

500

MT

400

MT

900

MT

200

MT

100

MT

300

MT

800

MT

900

MT

Output should show only items marked in yellow and select all options to be provided.
After the execution of the create Credit memo request, the user will go to VA02 transaction (if required) and put a
billing block or reason for rejection in the Credit memo request and then runs the transaction again to see for the
billing block or reason for rejection and run the program for the generation of the Credit note (billing document).
And then system should give the following output after the execution of the BAPI for Credit note.
B. Creation of Credit Note through BAPI (VF01)

Select the billing type (ZFCM - Factory) - FKART

Enter the Credit note request # - VBELN

Page 7 of 10

Functional
Specification

SAN_FS_SD_P004_1.0

Press Enter
Save.

Finally, it also output the list of Credit notes generated.

Sample Output
Customer
Code
1100
1100
1100
1100
1100
1100
1102
1102

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

Credit
Memo
Req
10001
10002

Credit
Note
14000001
14000002

Rate
20
20

10003
10004

14000003
14000004

20
20

Value
1000
800
1800
400
200

10005
10006

14000005
14000006

20
20

1600
1800

Continuation
Profit
Center

Material
Number

1000

FERT1

1000

FERT1

1000

FERT1

2000

FERT2

2000

FERT2

2000

FERT2
FERT1
FERT1

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

Quantity

Unit of
Measure

500

MT

400

MT

900

MT

200

MT

100

MT

300

MT

800

MT

900

MT

3.5

Any special remarks wrt Program Logic other then given in

excel sheet

3.6

Assumptions/ Dependencies/ Checks/ Filters/ Hard coded

fields:

Page 8 of 10

Functional
Specification

SAN_FS_SD_P004_1.0

1) The program is run irrespective of the FI clearing program (ZFR001

transaction) as the current program is designed based on the actual
credit and debit balance of the customer at a particular given point of
time.
2) The customer balance is at the company code level.
3) Cheque / DD entered in the system even though it is not cleared by bank
would be considered in this program i.e., any amount which is entered in
the system as receivables would be considered in this program.
4) Zero tolerance limits for the debit balance i.e., if the customer credit
balance is greater than equal to zero would be considered.
5) No CST / VAT is applicable for Century or Manikgarh units where as it is
applicable in case of only in Uttaranchal.
6) In this program no holidays would be considered.
7) At the time of slab update, check if the To date is greater than or equal
to From date.
8) If for a particular combination slab exists then it should not proceed
further and give a message stating that Date Already Exists for this
Combination.

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)

Page 9 of 10

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

Functional
Specification

SAN_FS_SD_P004_1.0

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)

___________________
Requested By (Originator)

___________________
Functional Consultant

_____________________
Technical Consultant

Page 10 of 10