Functional Specification in SAP
What Are Functional Specification in SAP?
To speak at macro level that is at projet manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functinality.. It describes the product’s features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis –
3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names –
8) Future Impact & Change Assessement
9) Functional Design (Module Wise)
10) Risk Assessement
11) Process Metrics and Many More– Which has impact on Business and its work flow
Sample Functional Specs
XYZ LTD (Client Name) ABC (Consulting Firm)
Development Request Form
Functional Specification Details
Dev Req. Ref No
To Be Filled By Functional Lead
Product / Module
FI
CO
MM
SD
CS
CRM
BW
EP
BPS
Requested By
XXXXXXXXXXXXX
Requested Date
12.06.2006
Reqd. By Date
Business Case
Sales / Purchase Report at Work-Shop.
Requirement
Priority
Critical
Important
Desirable
Functional Specs
Selection Parameter
Sales Organization: From (Mandatory)
Plant From to (Mandatory)
Period: From date, To date (Mandatory) WRT Service order
Output Parameters:
Header:
Dealer’s Name
Plant :
Address:
Sales/Purchase Report
From To Date
Logic for Plant Address:
Go to Table T001w & get NAME2, TRAS, PSTLZ, ORT01
Item Level:
Sr.No
Material Code (MATNR)
Material Description (ARKTX)
Sale Quantity
Group Wise(Acessories/Oil/M&M,Local)
Sale Value
Vat Amount
Unit Cost
Cost Value
Difference
Logic for the report:
Based on the combination of Sale Organization (VKORG), Plant(Werks),
Data to be extracted from CAUFV(Service Order)- Data to be Extracted are
as follows:Give Input as Erdat From To Get AUFNR(Service order No).
Pass This Value(AUFNR) into Table RKPF With input ERDAT to get all Service orders done with Movement Type 261(BWART).Pass this Value (AUFNR) into VBAK to get VBELN(Sales Order No’s.).Pass this values of VBELN into Table VBAP to get MATNR,ARKTX,MATKL,ZMENG.
To get Sale Amount:Go to Table VBAK give Value VBELN, get KNUMV.Pass this KNUMV as input in KONV table & get KBETR & KAWRT
Logic for Vat Amount: Based on the region of delivering plant and region of the customer A911. Hard code the values for Customer Tax Classification as ‘1’(Go to VBAP with in put VBELN & get TAXM1) and Material Tax Classification as ‘1’. Then pass the values of Region of delivering plant and region of customer along with the hard coded values for Customer Tax Classification and Material tax classification in table A911. Obtain the value for KNUMH for the period or duration provided as input.
Pass the A911-KNUMH into KONV-KNUMH to obtain the values of KONV-KBETR. Convert the value in KBETR to tax rate in percentage by dividing it by a divisor of ‘10000’. This value is the percentage of Tax. Add the percentage tax to the amount obtained for the basic amount. To obtain the price after tax.
If the condition not met ,
. Based on the region of delivering plant and region of the customer A909. Hard code the values for Customer Tax Classification as ‘1’ and Material Tax Classification as ‘1’. Then pass the values of Region of delivering plant and region of customer along with the hard coded values for Customer Tax Classification and Material tax classification in table A909. Obtain the value for KNUMH for the period or duration provided as input.
Pass the A909-KNUMH into KONV-KNUMH to obtain the values of KONV-KBETR. Convert the value in KBETR to tax rate in percentage by dividing it by a divisor of ‘10000’. This value is the percentage of Tax. Add the percentage tax to the amount obtained for the basic amount. To obtain the price after tax.
Then pass this value into A920-KNUMH into KONV-KNUMH KONV-KNUMH to obtain the values of KONV-KBETR. Convert the value in KBETR to tax rate in percentage by dividing it by a divisor of ‘10000’. This value is the percentage of Tax. Add the percentage tax to the amount obtained for the basic amount. To obtain the price after tax.
The validity of records from and to date to appear in the last two columns of the report.
Logic for Unit Cost:Go to Table MBEW with input MATNR & get VERPR.
Logic for Cost Value:Unit Cost * Sale Quantity.
Logic for Difference:Sale Amount(NETWR-KONV) – Cost Value(MBEW-VERPR * Sale Quantity
Usage Frequency
High
Authorizations
Performance Considerations
Test Cases & Desired Output
Formats for Input / Output / Forms etc.
Input Parameter
Sales Organization (mandatory)
From
Period (mandatory)
From Date
To date
Output Format:
Excel Sheet Attached
To Be Filled By Project Manager
Req. Accepted
YES
NO
Date
Remarks
Signature
Impact Analysis Details
To Be Filled By Technical Team Lead
Dev Req. Ref No
Impact Analysis
Disposition
Accepted
On Hold
Rejected
Effort Estimate
Est. Start Date
Est. End Date
Assigned To
Remarks
Signature
Technical Specifications Details
Dev Req. Ref No
Tech Specialist
Start Date
Technical Specs
End Date
To Be Filled By Technical Team Lead
Specs Approved
YES
NO
Date
Remarks
Signature
Development Details
Dev Req. Ref No
Tech Developer
Start Date
Object Name
Request No
Unit Test Report
End Date
Remarks
Signature
Testing Report
Dev Req. Ref No
Transportation Details
Dev Req. Ref No
Trans. Req. No
Trans. Req. Desc
To QA Server
To Prod Server
Signature
What Are Functional Specification in SAP?
To speak at macro level that is at projet manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functinality.. It describes the product’s features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis –
3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names –
8) Future Impact & Change Assessement
9) Functional Design (Module Wise)
10) Risk Assessement
11) Process Metrics and Many More– Which has impact on Business and its work flow
XYZ LTD (Client Name) ABC (Consulting Firm)
Development Request Form
Functional Specification Details
Dev Req. Ref No
To Be Filled By Functional Lead
Product / Module
FI
CO
MM
SD
CS
CRM
BW
EP
BPS
Requested By
XXXXXXXXXXXXX
Requested Date
12.06.2006
Reqd. By Date
Business Case
Sales / Purchase Report at Work-Shop.
Requirement
Priority
Critical
Important
Desirable
Functional Specs
Selection Parameter
Sales Organization: From (Mandatory)
Plant From to (Mandatory)
Period: From date, To date (Mandatory) WRT Service order
Output Parameters:
Header:
Dealer’s Name
Plant :
Address:
Sales/Purchase Report
From To Date
Logic for Plant Address:
Go to Table T001w & get NAME2, TRAS, PSTLZ, ORT01
Item Level:
Sr.No
Material Code (MATNR)
Material Description (ARKTX)
Sale Quantity
Group Wise(Acessories/Oil/M&M,Local)
Sale Value
Vat Amount
Unit Cost
Cost Value
Difference
Logic for the report:
Based on the combination of Sale Organization (VKORG), Plant(Werks),
Data to be extracted from CAUFV(Service Order)- Data to be Extracted are
as follows:Give Input as Erdat From To Get AUFNR(Service order No).
Pass This Value(AUFNR) into Table RKPF With input ERDAT to get all Service orders done with Movement Type 261(BWART).Pass this Value (AUFNR) into VBAK to get VBELN(Sales Order No’s.).Pass this values of VBELN into Table VBAP to get MATNR,ARKTX,MATKL,ZMENG.
To get Sale Amount:Go to Table VBAK give Value VBELN, get KNUMV.Pass this KNUMV as input in KONV table & get KBETR & KAWRT
Logic for Vat Amount: Based on the region of delivering plant and region of the customer A911. Hard code the values for Customer Tax Classification as ‘1’(Go to VBAP with in put VBELN & get TAXM1) and Material Tax Classification as ‘1’. Then pass the values of Region of delivering plant and region of customer along with the hard coded values for Customer Tax Classification and Material tax classification in table A911. Obtain the value for KNUMH for the period or duration provided as input.
Pass the A911-KNUMH into KONV-KNUMH to obtain the values of KONV-KBETR. Convert the value in KBETR to tax rate in percentage by dividing it by a divisor of ‘10000’. This value is the percentage of Tax. Add the percentage tax to the amount obtained for the basic amount. To obtain the price after tax.
If the condition not met ,
. Based on the region of delivering plant and region of the customer A909. Hard code the values for Customer Tax Classification as ‘1’ and Material Tax Classification as ‘1’. Then pass the values of Region of delivering plant and region of customer along with the hard coded values for Customer Tax Classification and Material tax classification in table A909. Obtain the value for KNUMH for the period or duration provided as input.
Pass the A909-KNUMH into KONV-KNUMH to obtain the values of KONV-KBETR. Convert the value in KBETR to tax rate in percentage by dividing it by a divisor of ‘10000’. This value is the percentage of Tax. Add the percentage tax to the amount obtained for the basic amount. To obtain the price after tax.
Then pass this value into A920-KNUMH into KONV-KNUMH KONV-KNUMH to obtain the values of KONV-KBETR. Convert the value in KBETR to tax rate in percentage by dividing it by a divisor of ‘10000’. This value is the percentage of Tax. Add the percentage tax to the amount obtained for the basic amount. To obtain the price after tax.
The validity of records from and to date to appear in the last two columns of the report.
Logic for Unit Cost:Go to Table MBEW with input MATNR & get VERPR.
Logic for Cost Value:Unit Cost * Sale Quantity.
Logic for Difference:Sale Amount(NETWR-KONV) – Cost Value(MBEW-VERPR * Sale Quantity
Usage Frequency
High
Authorizations
Performance Considerations
Test Cases & Desired Output
Formats for Input / Output / Forms etc.
Input Parameter
Sales Organization (mandatory)
From
Period (mandatory)
From Date
To date
Output Format:
Excel Sheet Attached
To Be Filled By Project Manager
Req. Accepted
YES
NO
Date
Remarks
Signature
Impact Analysis Details
To Be Filled By Technical Team Lead
Dev Req. Ref No
Impact Analysis
Disposition
Accepted
On Hold
Rejected
Effort Estimate
Est. Start Date
Est. End Date
Assigned To
Remarks
Signature
Technical Specifications Details
Dev Req. Ref No
Tech Specialist
Start Date
Technical Specs
End Date
To Be Filled By Technical Team Lead
Specs Approved
YES
NO
Date
Remarks
Signature
Development Details
Dev Req. Ref No
Tech Developer
Start Date
Object Name
Request No
Unit Test Report
End Date
Remarks
Signature
Testing Report
Dev Req. Ref No
Transportation Details
Dev Req. Ref No
Trans. Req. No
Trans. Req. Desc
To QA Server
To Prod Server
Signature