Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Tech. Spec for function call prog

Former Member
0 Likes
1,050

Hi all

I need to write a tech spec for a function call prgram ... but I dont know how to write this, can someone help me out and send me some sample for the same?

or what are the requirements to write this spec.

Thanks!

9 REPLIES 9
Read only

Former Member
0 Likes
989

Functional Specs differ from company to company as every company has its own format for all the design documents and hence sharing my FD wont help.

However, The main blocks of FD contains

1. Business Need

2. Process Flow

3. Technical info like tables/field names, user exits, etc.

4. Test scenarios

5. Test cases.

Below are the standards for Tech specs

1.1 Development Attributes

Program Name:

Title:

Application:

Development Class:

Message Class:

Program Type:

Execution Mode:

Schedule Frequency:

Variant:

1.2 Program Functionality

1.3 Output Fields

Output Label

Related SAP table-field (if any)

Length

Output Characteristics

1.4 Proposed Solutions

1.5 Solution to be implemented

1.6 Reasons of selection/rejection

1.7 Pseudo-Code / Flow Logic of the selected solution

1.8 Selection Screen

1.9 Database Tables Used

Table Name

Table Description

How the table is used in the program

1.10 External Files Used

1.10.1 External File Layout <file name>

1.11 Components External to Program Used

1.12 Error Conditions

1.13 Key Technical Test Conditions

1.14 Sample Test Data

1.15 Assumptions

1.16 Comments

Every organization may have diff template , you may require to follow the template . In TS you have to write clearly in technical term but dont do any copy pase from the code , which not at all sound good.

Pl find the tips below:

1.In 1st page you may require to give heading and company logo also at the RHS.

2.Give title of the document , SAP Module Name, Specification Type (Giv ein a tabular format)

3.Revision History in Tabluar Format including Author , Description , Date , Version ( Version management very imp try to maintain it)

4.Requirement Description : Enter in detail wat is u r reqmt.

5.U may add Process flow diagram using visio etc.

6.Outstanding issues

7.Prerequisites

8.Input Parameter Details

9.Processign logic Details

10.Out Put Details (if Report Output Format)

11.The few unit testing scripts also u can include

12.Proper file name , in header & Footer

13. Always try to keep track changes on for version management. If u need to create new version try to accept previous version then keep track for curren tchanges.

14. Maintain index & Page no in table content .

regards,

srinivas

<b>*reward for useful answers*</b>

Read only

Former Member
0 Likes
989

Hi Saritha,

As you are aware, tech-spec would be written to explain the functional spec in technical terms to the developer.

So just mention what is the function that is to be called and where?

It is in your discretion whether to mention the ABAP statements used in callling the function and to include the logic which goes into the Function Module.

Specify the import parameters and export parameters that are to be used by the Function Module.

Try to include a flow diagram which explains the logic flow of the code. That's it.

<b>Reward points if this info helps,</b>

Kiran

Read only

0 Likes
989

Thanks for your replies guys but any of you has the ready technical spec for a function call program, so I can follow the same approach.

I know format vaires company to company but it will be helpful to me if someoen can send me that.

Thanks !

Read only

0 Likes
989

Hi Saritha,

Please specify your mail id so that i can send you a copy of the tech spec. Please do not forget to reward with points.

Kiran

Read only

0 Likes
989

my email is sunshine31in@yahoo.co.in

wait for a your reply

Thanks !

Read only

0 Likes
989

kiran I am waiting for your email !!

sunshine31in@yahoo.co.in

Read only

0 Likes
989

I have sent one document to you and try to see how we are writing.

use your client standard template.

always maintain technical logic if possible use pseudo code in document.

Thanks

Seshu

Read only

0 Likes
989

Hi Saritha,

I've sent you those docs through email, plz reward points accordingly.

Kiran

Read only

Former Member
0 Likes
989

Hi Saritha,

Take a look at the std Functional spec template.

Hope this helps

http--www.sceis.sc.gov-content-FI-MM_Implementation_Prep-Blueprint-Gap-1.5_support_Functional_Spec_IDT-1.pdf

Cheers

VJ