You are on page 1of 9

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

.........................1 3.........10 ASSUMPTIONS/ DEPENDENCIES/ CHECKS/ FILTERS/ ‘HARD CODED’ FIELDS:..............11 OUTPUT: A) LIST..................................................................................4 OBJECT VERSION HISTORY................................................................3 3........................................................................10 OPTIONS FOR PROGRAM (TO BE TICKED)...........4 5................3 4...................................................4 3..........................................................................................................................................7 4..........................................................................11 EXECUTION: A) FOREGROUND........0 4..............5 3............................................1 4................................. 3 3............. TO BE ATTACHED)...............4 3...................................................................................................0 Table of Contents 1...................11 SAMPLE OBJECT (IF ANY.............................................................................................................................................0 TEMPLATE FOR CAPTURING FUNCTIONAL SPECIFICATIONS..............6 SELECTION LOGIC:................0 HEADER....................................................................................................................................2 4..........5 PROGRAM FUNCTIONS.............0 ROLE....................................................11 Page 2 of 9 ..............................................................................................11 B) BACKGROUND...................................................6 3..........................................11 TEST CASES FOR UNIT TESTING (DOCUMENT ATTACHED SEPARATELY)............................................2 3...... 3 2.......................................................................................................................11 PRODUCTION CHECKLIST.Functional Specification SAN_FS_SD_QTY DISCOUNT_005 -006_1................4 INPUT / HEADER / SUB-HEADING / OBJECT BODY.0 PURPOSE...............5 PROGRAM LOGIC................................................

 2.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 Nagaraj Functional / Technical Estimated Person Days For Modification.0 Role   Fn co – to provide logic / source of data Developer – translate the logic provided by the function consultant into program code.0 1.1 Header Specification Name QTY DISCOUNT CALCULATION Specification Number SAN_FS_SD_QTY 006_1.Functional Specification SAN_FS_SD_QTY DISCOUNT_005 -006_1.0 Purpose  The purpose of this development is to develop the functionality to enable the business in order to pass on monthly qty discount to a particular market segments (Trade) at the month end and at same time to issue consolidated Credit Memo. 3.0 Template for capturing Functional specifications 3. name of current report / object Page 3 of 9 DISCOUNT_005- .

1 3.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.4 3. Page 4 of 9 .3.1 New Version Previous Version Date of change Input / Header / Sub-Heading / Object Body Object Name: Heading: QTY DISCOUNT CALCULATION Sub-Heading (if any): Sub-Heading (if any): Program Functions Pls.4.3.2 SAN_FS_SD_QTY DISCOUNT_005 -006_1.3.Functional Specification 3.3.3 3. The system calculate the base on the below mentioned parameters.3 3. 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.2 3.4 3.

On saving the transaction. system should take the user to the Z table maintenance and user can enter the slabs --. but the system should convert the same into date format. Update Slab rate 2. 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 Page 5 of 9 . user will enter the same as Jan 2009 but the system should convert the same as "From 01/01/2009 to 31/01/2009) On executing the above.DATAM  Update To-DATAM Input Parameters with Two push buttons: 1.Functional Specification SAN_FS_SD_QTY DISCOUNT_005 -006_1. system should prompt the user with two fields  Sales Organization VKORG  Distribution channel VTWEG  Month (Mandatory) and year FKDAT  State BLAND (User will enter the month and year. the Z table has to be updated On selecting the push button Process credit note.0 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)  Material –MATNR (Primary Key)  State of Plant-BLAND (Primary Key)  Qty-From –MENGE  Qty To-MENGE  Rate-KBETR  Update From. Process Credit note On selecting the push button Update slab rate. For example.

01.01.01.Functional Specification SAN_FS_SD_QTY DISCOUNT_005 -006_1. Sample Output Sales Organization 1000 1000 1000 1000 1000 1000 1000 1000 Distribution Channel 10 10 10 10 10 10 10 10 Profit Center 1000 1000 1000 2000 2000 2000 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 Continuation Page 6 of 9 Billing Document 14000001 14000002 Billing date 01. Output: 1) Output should be in ALV Grid form.01.01. 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 Also to fetch Customer Name (NAME1) from KNA1 based on KUNRG and Material Description (MAKTX) from MAKT based on MATNR And check the profit center (PRCTR) of the billing documents and if the profit center is different then the system should create two credit notes for the customer and after the quantity cumulation Eg: If the customer is billed for 100 MT in depot 1901 and 200 MT in depot 2901. 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).0 FKIMG Actual Invoiced Quantity MEINS Base Unit of Measure MATNR Material Number PRCTR Profit Center Step 3: Clubbing the above steps Output parameters from Step 1 and Step 2 should be clubbed based on the field VBELN (Billing document). 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.2009 14000005 14000006 01.2009 01. other details should be populated in ALV Grid list.2009 14000003 14000004 01.2009 01.01.2009 01.2009 .

0 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 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) Quantity slab from and TO as per Z table (Based on the quantity shown in yellow color. these credit notes are already generated.Depot. On clicking OK.Factory  Sales Organization – 1000  Distribution Channel – 10 / 11 / 12 (Trade / Non. system should process the BDC Step-6-Credit Note Processing through BDC A.Trade /Exports)  Sales Office -1000…  Sold to Party  Remove the billing block. Creation of Credit note request (VA01)  Order Type – ZDCM.AUGRU  Target Qty  Material  Plant  Shipping Point  Storage Location  Save Page 7 of 9 .Functional Specification A/c Doc No. This can be checked by verifying whether the input month is already appended in the field Update from. ZSCM.DATAM and Update To-DATAM. If it is blank.FAKSK  Order Reason. then system should prompt a message “Do you want you process for generating the Credit Notes". Material Number 9000001 FERT1 9000002 FERT1 FERT1 9000003 FERT2 9000004 FERT2 FERT2 9000005 FERT1 9000006 FERT1 SAN_FS_SD_QTY DISCOUNT_005 -006_1. system should pick up respective data from Z table) 2) Rate from Z table (Based on the slab available for the above combination from the Z table) 3) Credit Note Value (Qty in yellow color multiplied with Rate) Execution of BDC Once the user validates the record and upon execution / F8 the system should check whether.

6000.0 Note: If VBRP-WERKS = 1000. ZFCM.0 Options for program (to be ticked) 4.5 Any special remarks wrt Program Logic other then given in excel sheet 3. Finally.VBELN Press Enter Save. 5000. 2000.DATAM and (2) Update To-DATAM as per the input parameters (2) It also output the list of credit notes generated 3.Depot.6 Assumptions/ Dependencies/ Checks/ Filters/ ‘Hard coded’ fields: 4. 7000 then take the document type as ZSCM else ZSCM.1 OUTPUT: A) List B) Grid Display C) Interactive D) Direct Download Filename if (D) is ticked above Grid Display 4. Note: If VBAK-AUART = ZDCM then FKART should be ZBCM and if it is ZSCM then FKART should be ZFCM. (1) System should update the Z table (1) Update From.2 EXECUTION: B) Background Page 8 of 9 .Functional Specification SAN_FS_SD_QTY DISCOUNT_005 -006_1. Creation of Credit Note – (VF01)     Select the billing type (ZBCM.Factory) .FKART Enter the Credit note request # . B. 3000.

) 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 9 of 9 .0 SAMPLE OBJECT (if any. to be attached) 5.Functional Specification 4.0 Production Checklist Item Check (tick) Notes (Names of reports. etc. code.3 SAN_FS_SD_QTY DISCOUNT_005 -006_1. tr.