You are on page 1of 12

Functional Specification Document:

Development ID: FS_TS_SD_REP_003 Document Information Description SAP Module Author (s) GAP Number Pre-Sales Register SD R Sengupta

Change Log
Version Version 1.0 1.0 Date effective 18/12/2007 27/12/2007 Reason for Change Submission of 1st version Technical Specification Changed By R Sengupta Arnab Mandal Role SD PwC ABAP PwC

Page 1 of 12

Table of Contents
I. DOCUMENT PUR POSE : ..................................................................................................................................................3 II. OPTIONS CONSIDERED:.................................................................................................................................................3 III. DESCRIPTION OF GAP RESOLUTION:......................................................................................................................3 IV. FIELD MAPPING.............................................................................................................................................................3 V. INPUT SELECTION SCREEN & OUTPUT LAYOUT:.................................................................................................6 VI. SAP SCRIPT SPECIFICATION:.....................................................................................................................................7 VII. CUSTOM TRANSACTION / MODULE SPECIFICATION:......................................................................................8 VIII. PROGRAM/OBJECT DETAIL:....................................................................................................................................8 IX. PROCESS/PROGRAM LOGIC:......................................................................................................................................8 X. ERROR HANDLING AND VALIDATIONS:NA.............................................................................................................9 XI. CUSTOM DATA DICTIONARY OBJECTS:NA...........................................................................................................9 XII. SAPSCRIPT TECHNICAL SPECIFICATION:NA....................................................................................................10 XIII. CUSTOM TRANSACTION / MODULE POOL TECHNICAL SPECIFICATION:NA.......................................11 < SCREEN HEADER INFORMATION. TO BE FILLED BY TECHNICAL RESOURCE> ....................................................................................11 <SCREEN FIELD MAPPING: TO BE FILLED BY TECHNICAL RESOURCE>..............................................................................................11 XIV. USER EXIT / ENHANCEMENT TECHNICAL SPECIFICATION:NA................................................................11 < TABLE EXITS. TO BE FILLED BY TECHNICAL RESOURCE>.............................................................................................................12

Page 2 of 12

I. Document Pur pose :


Standard SAP does not provide a Pre-Sales Register in the way ECL & LIL generates the same

II. Options Considered:


Since, this is not possible through standard SAP in a manner, which suits the need of ECL & LIL, a development is the only option.

III. Description of GAP Resolution:


An ALV Report design which will be triggered after a Pre-Inquiry/Inquiry/Quotation has been created in the system. Data Flow Diagram: Fields in the table will be as mentioned above -

IV. Field Mapping


Sl. No. Table Name Field Name Field Description Date Type Data Lengt h Comments

01 02 03 04 05 06 07

VBAK V_TVAK VBAK VBAK VBAK VBAK

AUART BEZEI VBELN ANGDT BNDDT AUDAT

Document Type Document Type Name Document No Valid From Valid To Document date

Pick-up the document type from VBAK-AUART

1. Put VBAK-VBELN in VBPA table

Sold-toParty Code
08

2. Pick up VBPA-KUNNR when VBPA_PARVW=AG Put the Code in KNA1 to fetch the name from field NAME1

Sold-toParty name

Page 3 of 12

09

1. Put VBAK-VBELN in VBPA table

Payer Code
10 11

2. Pick up VBPA-KUNNR when VBPA_PARVW=PY Put the Code in KNA1 to fetch the name from field NAME1 Go To KNA1 & put the payer code as determined to extract payer name from field LAND1 Go To KNA1 & put the payer code as determined to extract payer name from field REGIO

Payer Name Country

12

Region
13 14 15

VBAK VBAK

BSTNK BSTDK

Ref Doc No Ref Date Doc


1. Put VBAK-VBELN in VBPA table

Scheme No
16 17 18

2. Pick up VBPA-KUNNR when VBPA_PARVW=Z1 Put the SCHEME Code in KNA1 to fetch the name from field NAME1

Scheme Name KNVV KNVV FUNAG SCHVAL Source Fund Scheme value Currency of

Put the SCHEME Code in KNVV to fetch the name from field FUNAG Put the SCHEME Code in KNVV to fetch the name from field SCHVAL Put the SCHEME Code in KNVV to fetch the name from field CURRENCY

19

KNVV

CURRENC Y

19

From Column No 20 till Column No 37 , multiple line items will appear against each doc NUMBER (Sl No 3)

20 21 22 23 24

VBAP VBAP VBAP VBAP VBAP Calculated

MATKL MATNR ARKTX KWMENG VRKME

Material Group Material Code Material description Quantity Sales Unit Quantity Base Unit
Sl No 23 * VBAP-UMVKZ Pick VBAP-MATNR & select MARAMEINS 1. Go to VBAK-KNUMV & pick-up the value

25 26 27

Basic price

2. Go to KNOV & put the value to extract KONV-KSCHL=JCST

Page 4 of 12

28 29 30

VBAP VBAP Calculated Default

WAERK STCUR

31 32

INR

Doc Currency Exchange Rate Value in Local Currency Local Currency BED

Sl_No 27*Sl_No 29

1. Go to VBAK-KNUMV & pick-up the value 2. Go to KNOV & put the value to extract KONV-KSCHL=JEXP 1. Go to VBAK-KNUMV & pick-up the value

33

ECS
34

2. Go to KNOV & put the value to extract KONV-KSCHL=ZECS 1. Go to VBAK-KNUMV & pick-up the value

S.E-Cess
35

2. Go to KNOV & put the value to extract KONV-KSCHL=ZECH 1. Go to VBAK-KNUMV & pick-up the value

VAT

2. Go to KNOV & put the value to extract KONV-KSCHL=JLST 1. Go to VBAK-KNUMV & pick-up the value

CST
36

2. Go to KNOV & put the value to extract KONV-KSCHL=JCST 1. Go to VBAK-KNUMV & pick-up the value 2. Go to KNOV & put the value to extract KONV-KSCHL=JISP A. VBAP-NETWR +

Inspection Charges
37

Calculated Gross value

B. VBAP-MWSBP

38

VBAP VBAP

KONDM VKAUS

Mat Pricing Group Usage

Page 5 of 12

V. Input Selection Screen & Output layout:


Name Table Field/Check box/Radio button Selectoption (S) or Parameter (P) Comments (Range, Single/Multipl e Selection, Patterns, Mandatory, etc.)
Range , MultipleMandatory Range , MultipleOptional SingleMandatory Single -Mandatory Range , MultipleOptional Range , Multiplemandatory

Default Value

Date from Date to Sold-to-party Sales Org Distribution Channel Division Material Type

VBAK-AUDAT VBAK-AUDAT VBAK- KUNNR

VBAK-VKORG VBAK-VTWEG VBAK-SPART Pick-up VBAPMATNR & put in MARA to extract MTART

Output should be in ALV format


Only the documents having VBAK-VBTYP = A or B ( SD document category)

Page 6 of 12

VI. SAP Script Specification:


Not applicable

Output type Program Name Layout Form Name IMG path to access output type and layout set assignment Type of solution (Standard R/3, custom ABAP) Owner of existing solution Menu Path for transaction: Values to be used and output type: Actions to be taken:

A New transaction Z_PRESALES_REGISTER needs to be created.

Output type(s): Form Types: Transmission medium: Legal requirements: Type of printer: Paper Size:
Label R/3 Field Table: Screen: Functionality Calculation Logic Print-onPage Label Position Font Font Format

Page 7 of 12

Table: Screen:

VII. VIII.

Custom Transaction / Module Specification: Program/Object Detail:


Object Summary Program Name Type Status Application Development Class Transaction Code Logical Database Tables Message Class Authorization Class/Object
Details
YSD_PRESALES_REGISTER

A Z-Transaction code to be created so as to run the report

Executable Customer Production Program SD YDSD

YPRESALES

NA

VBAK,VBAP NA

IX. Pro cess/Progr am Logic:

The selection screen has 4 ranges :SO Date,SO Customer,Division and Maetrial of which only Date is mandetory.There are 2 obligatory parameters :sales organisation and distribution channel.
NA

According to the selection criterion given,first Sales Document header data are fetched from VBAK and Item Data are fetched from VBAP.Document Type Description is fetched from TVAK.Then Sold-to-party and Payer data are fetched form VBPA and KNA1.Scheme Details are obtained from KNVV.Also the Pricing Details are fetched from KONV. All these header and item data are now merged to form an internal table to dispaly the list of documents in ALV.

Page 8 of 12

The code is attached below-

X.Error Handling and Validations:NA


<To be filled by Technical Resource>
Serial Numbe r Error Message Message Type Comments

XI. Custom Data Dictionary Objects:NA


<This section should detail the attributes of any custom table used, and the properties of its fields. NB: Existing SAP Data Elements and/or Domains should be used whenever possible when creating custom table fields, in order to avoid unnecessary typos. In this instance, the data table row for that field should not be completed beyond Domain, as the remaining attributes will be default values for the selected Domain. To be filled by Technical Resource >
Name: Short text: Size Category: Table Maintenance Allowed:

Page 9 of 12

Data class: Size: Buffering: Table locking: Table Maintenance Generation : Authorisation Group:

Field Name

Data Element

Domain

Type

Length

Check TableField

Key Field

Foreign Key

Description

XII. SAPScript Technical Specification:NA


<Layout Details. Provide information about how to position the layout set with respect to the page and how to position various items (such as the logo). To be filled by Technical Resource.>
Position (Specify Position (Specify Position (Specify Position Window (Specify of Left Margin Unit) of Right Margin Unit) of Logo Unit) of Main Unit)

<Standard Texts. Please describe here all the standard texts that need to be created and attached to the development transport request with the SAPScript. To be filled by Technical Resource.>
Description of use Text Name Text ID Error Case

Page 10 of 12

XIII. Custom Transaction / Module Pool Technical Specification:NA


<This section should contain a detailed description of the Custom Transaction / Module Pool detailed description. This should include a description of the purpose of the transaction, the data flow and screen flow. Any data dictionary read/write logic should be explained from a functional point of view. To be filled by Technical Resource.>
Transaction Code: Menu Path:

< Screen Header Information. To be filled by Technical Resource>


Screen # Screen Title Purpose Title Bar GUI Status

<Screen Field Mapping: To be filled by Technical Resource>


Field #* Field Descrip tion Field Type SAP Referen ce Field Scre en Field Leng th Inpu t/ Outp ut Field Manda tory/ Option al Defaul t values Get Value (G) Set Value (S) Or Both (B)) Match codes used (if any) Other field formatting requirements

XIV. User Exit / Enhancement Technical Specification:NA


<Complete the following table to give details of the exit to be used. To be filled by Technical Resource >
Type of Exit Name of Exit / Business Add-In / Business Transaction Event Project Enhancement

Page 11 of 12

Component(s) SAP Program Function Module Transactions impacted Include(s) Screen Number(s) Menu/Path

< Table Exits. To be filled by Technical Resource>


Project Enhancement Components Table Name Append Name Include Name

Page 12 of 12