Creating a Functional Specification Document (FSD) in SAP: A Comprehensive Guide

[Surendra_Karma]

When embarking on the creation of a Functional Specification Document (FSD) in SAP, there are several crucial steps you must follow to ensure that the document is comprehensive, accurate, and effective. This blog will guide you through the process using a case study involving the transaction data of a deal, specifically focusing on the FTR_DISPLAY transaction.

Step-by-Step Guide to Preparing an FSD in SAP

1. Understanding the Transaction Data

The first step is to get a good understanding of the transaction data. In our case, we are dealing with a financial deal. The transaction code we will be using to display this data is FTR_DISPLAY.

2. Displaying the Data in FTR_DISPLAY

Navigate to transaction code FTR_DISPLAY in your SAP system. This transaction will allow you to display the details of deals. Here’s how you do it:

• Open the SAP GUI.
• Enter FTR_DISPLAY in the command field and press Enter.
• Input the necessary company code, deal number or other required parameters to fetch the deal data.
• Execute the transaction to display the deal details.

3. Analyzing the Data

Carefully go through the different tabs and fields displayed for the deal in FTR_DISPLAY. These tabs may include General Data, Financial Data, Conditions, Cash Flows, Status, etc. Note down all the fields and values that are relevant to your FSD.

4. Identifying Required Data

As you explore the different tabs and fields, identify and mark the data you will need for your specification document. For example, you might need the following:

• Company Code
• Deal Number
• Product Type
• Transaction Type
• Partner
• Flow Type
• Payment Amount
• Interest Rate
• Start Date
• End Date
• Posting Status

5. Mapping Data to SAP Tables

Once you have identified the required data, the next step is to map this data to the relevant SAP tables. The primary tables you will use include:

• VTBFHA: This table contains the header data for financial transactions.
• VTBFHAPO: This table holds the position data for financial transactions.
• VW_VTBFHA: This is a view that provides a consolidated view of transaction data.

6. Checking the Relevant Entries

For each field you have identified, check the corresponding entries in the above-mentioned tables. Here’s how you can do it:

• Go to transaction code SE16 or SE16N.
• Enter the table name (e.g., VTBFHA) and press Enter.
• Input the relevant selection criteria (e.g., deal number) to filter the data.
• Execute the query to view the table entries.

7. Documenting Your Findings

As you find the relevant entries in the tables, document them in your FSD. For example:

• Company Code: Found in VTBFHA (Field: BUKRS)
• Deal Number: Found in VTBFHA (Field: RFHA)
• Product Type: Found in VTBFHA (Field: SGSART)
• Transaction Type: Found in VTBFHA (Field: SFHAART)
• Partner: Found in VTBFHAPO (Field: KONTRH)
• Flow Type: Found in VTBFHA (Field: SFHAZBA)
• Payment Amount: Found in VW_VTBFHA (Field: BZBETR)
• Interest Rate: Not Found
• Start Date: Found in VTBFHA (Field: DBFLZ)
• End Date: Found in VTBFHA (Field: DEFLZ)
• Posting Status: Found in VTBFHA (Field: SBEWEBE)

8. Handling Missing Data

If you encounter any data that you cannot find in the tables, make a note of it in your FSD. This will allow you or your colleagues to investigate further and locate the missing information. For example:

• Interest Rate Type: Not found in VTBFHA, VTBFHAPO, or VW_VTBFHA. Further investigation required.

9. Reviewing and Finalizing the FSD

Once you have documented all the required data and their corresponding table entries, review your FSD carefully. Ensure that all fields are accurately mapped, and the document is complete. Put them into a professional FSD template shared by client (if any). Share the FSD with relevant stakeholders for feedback and make any necessary revisions.

Conclusion

Creating a Functional Specification Document in SAP requires a thorough understanding of the transaction data and the ability to map this data to the appropriate SAP tables. By following the steps outlined in this blog, you will be able to prepare a comprehensive and accurate FSD that will serve as a valuable reference for your project.

[Surendra_Karma]

This FSD blog is recommended exclusively for custom reports, export files, and dashboards.