TSD Generator

Quick Actions

📄

New TSD

Start a technical specification from a template

📋

Browse TSDs

Search and filter all specification documents

⬇️

Download Template

Get the TSD_PROMPT.md developer input form

By SAP Module

Recent Documents

Document ID	Description	Module	Type	Priority	Status	Date

✦

Describe your requirement

Type in plain English — Claude will fill every field automatically

Try an example:

💡 T-codes: ZWC13, IW21, MB51, PA30 — name them and Claude recognises the SAP context

💡 Field values: "planning plant 1200", "department = TEM" — specifics become pseudo-code

💡 BAPIs / FMs: mention them by name — Claude maps them to the Interface section

1Document Identity

2Technology

3Business Context

4Technical Design

5Specs & Transport

6Test & Review

Document Identity Step 1 of 6

Document ID *

Format: SAP / Module / WRICEF type / Work Order number

Short Description *

Start with a verb. Name the T-code or process. Keep it under 100 characters.

Work Order / Ticket *

Date

Prepared By *

Reviewed By

Approved By

SAP Module *

SAP System

Priority

WRICEF Type

W SAP Workflow / approval routing R Report / ALV / analysis I Interface — RFC, BAPI, IDoc, file C Conversion — LSMW, BDC, migration E Enhancement — BAdI, User Exit, implicit F Form — SmartForms, Adobe Forms

Technology Selection Step 2 of 6

Select every technology this TSD covers. The generated document will include a dedicated section for each one. If you used the AI auto-fill above, these are already checked — verify they match your actual work.

0 technologies selected

Business Context Step 3 of 6

Business Context *

Who uses this? What T-code / process / team is involved? What problem does it solve? Write 3–5 sentences. Avoid vague phrases like "improve efficiency" — be specific.

Existing Process (AS-IS)

List the current manual steps in numbered order. Name every T-code used. Add a "Pain points:" section at the end describing what goes wrong today.

New Process (TO-BE) *

What happens after this development, step by step. Be precise — include exact field values, conditions, what data is copied, what message the user sees.

Technical Design Step 4 of 6

ABAP Objects Created / Modified

Object Name	Type	Status	Package	Description

Key Tables Used

Table	Operation	Key Fields	Note

Processing Logic (Pseudo-code)

Write pseudo-code or numbered logic steps. Use real SAP field names (QMNUM, IWERK, TPLNR…), real BAPI/FM names, and show error paths. This becomes the dark code block in the generated TSD.

Enhancement Type

Spot / BAdI Name

Implementation Name

Standard Program Modified

Trigger Condition

Rollback Risk

Deactivation Steps

OData Service Name

OData Version

Entity Sets

Entity Set Name	Operations (C/R/U/D)	Note

CDS Views

View Name	Type	Base Table	Note

App Type

FLP Semantic Object

FLP Action

Bilingual (EN + AR)

Screens / Views

View Name	Type	Bound Entity	Key Controls

Neptune App ID

Neptune Planet

OData Services Consumed

Key Controller Methods

Custom CSS Overrides

i18n Keys Added

BTP Subaccount

CAP Service Name

S/4 Destination

Auth Strategy

Workflow Template

Trigger Event

Trigger Class

Notification Template

Workflow Steps

Step Name	Task	Agent / Role

Form Name

Form Type

Print Program

Output Type

Data Retrieval Logic

Supporting Specifications Step 5 of 6

Interfaces & Integrations

List every external call, file, IDoc, or API

Name	Direction	Tech	Source	Target	Frequency	Note

Authorization Objects

PII / Sensitive Data

Error Messages

Code	Scenario	User Message	Action

Expected Volume

Runtime Target

SLG1 Application Log Object

SLG1 Sub-Object

Performance Notes

Transport Requests

TR Number	Task	Object Name	Object Type	Package

DEV System / Client

QA System / Client

PRD System / Client

Test Scenarios & Review Step 6 of 6

Test Scenarios

ID	Category	Condition	Test Data	Steps	Expected Result

Additional Notes / Appendices

Document Summary

Document ID	Description	Module	Type	Priority	Author	Status	Date	Actions

Sorted by date (newest first)

My TSDs ›

Module

WRICEF Type

Priority

SAP System

Status

Prepared By

Reviewed By

Date

Technologies

No documents found