← Back to gists

ABAP Vibe Coders

AI lists required context

AI lists all the BADI's, classes, function modules etc. for a change request

Published Oct 14, 2025View on LinkedIn
Darshita Chaturvedi - Adri AI | LinkedIn

Shared by

Darshita Chaturvedi - Adri AI | LinkedIn

As the founder of Adri AI (YC W23), I lead the development of products in the AI risk… · Experience: Adri AI · Education: Y Combinator · Location: San Francisco · 500+ connections on LinkedIn. View Darshita Chaturvedi’s profile on LinkedIn, a professional community of 1 billion members.

How-to guide

  1. Paste the prompt template in any leading LLM agent (ChatGPT, Adri)
  2. Paste the change request inside <task> tag

Files

prompt-template.md

markdown
You are an expert ABAP developer analyzing a change request. Based on the task description provided, identify and list all the necessary ABAP development objects and system information required to implement this change request successfully. **IMPORTANT**: For any specialized, less common, or module-specific objects that you're not completely certain about, use web search to verify current best practices, latest SAP documentation, and accurate technical details. This is particularly important for:- Industry-specific functionality (IS-U, IS-Oil, IS-Media, etc.)- Newer SAP technologies (RAP, CDS, Fiori, S/4HANA Cloud)- Module-specific objects (HCM, SRM, CRM, SCM, etc.)- Enhancement techniques and their current recommendations- SAP version-specific features and deprecations For the given task, provide a comprehensive analysis covering the following categories: ## **Database Objects**- Tables (standard SAP tables and custom Z/Y tables)- Views (database views, maintenance views, help views)- Indexes that might be affected- Table relationships and foreign keys- **Use web search** for industry-specific or less common table structures ## **Development Objects to Review/Create/Modify**- Programs/Reports (executable programs, includes, module pools)- Function Modules (including BAPIs if applicable)- Classes and Methods (global and local classes)- Interfaces- CDS Views (if S/4HANA environment)- **Use web search** to verify current best practices for modern ABAP development patterns ## **Enhancement and Extension Points**- Existing BADIs (Business Add-Ins) - both Classic and Kernel BADIs- User Exits and Customer Exits (Function Module, Screen, Menu, Field exits)- Enhancement Points and Enhancement Sections- Enhancement Spots and Enhancement Implementations- Implicit and Explicit enhancement options- **Use web search** to confirm current SAP recommendations on enhancement techniques and deprecation notices ## **User Interface Elements**- Transaction Codes (T-codes) involved- Screen/Dynpro numbers- Menu paths and GUI status- Selection screens and parameters- Subscreens and modal dialogs- **Use web search** for UX/UI best practices in current SAP versions ## **Configuration and Customizing**- Customizing tables (T-code SPRO related)- Configuration entries required- Number ranges- Message classes and message numbers- Variants and selection criteria- **Use web search** for module-specific configuration requirements ## **Modern SAP Objects (if applicable)**- Business Objects for RAP (RESTful ABAP Programming)- Behavior Definitions and Implementations- Service Definitions and Bindings- OData Services- Fiori Elements or Fiori Freestyle apps- **Use web search** for latest RAP development guidelines and S/4HANA Cloud considerations ## **Integration and Workflow Objects**- RFC Function Modules- Web Services (SOAP/REST)- IDoc types and message types- Workflow objects (Business Objects, Tasks, Events)- BTE (Business Transaction Events)- **Use web search** for current integration patterns and cloud connectivity options ## **Authorization and Security**- Authorization objects- User roles and profiles affected- Security considerations- **Use web search** for current SAP security best practices and compliance requirements ## **Testing and Transport**- Test scenarios to consider- Transport request dependencies- Regression testing areas- **Use web search** for current testing methodologies in SAP environments ## **System Information Needed**- SAP version and relevant support packages- Development environment details- Integration touchpoints with other systems- **Use web search** to verify version-specific features and limitations ## **Industry/Module-Specific Considerations**- **Always use web search** to identify industry-specific objects, transactions, and best practices- Look for module-specific BADIs, user exits, and enhancement points- Verify current support status of legacy objects <task>[Insert the specific change request/task description here]</task> **Output Format:**1. Provide your analysis in a structured format with clear categorization2. For each category, include brief explanations of why each object/table is needed3. **Mark with [WEB SEARCH USED]** any items where you used web search for verification4. Include confidence levels: HIGH (certain), MEDIUM (likely), LOW (needs verification)5. Flag any deprecated or legacy objects that might need modern alternatives **Note**: If the task involves unfamiliar business processes, industry solutions, or recent SAP innovations, prioritize web search to ensure accuracy and current best practices.