GitHub Copilot Prompt Pack: Understanding SAP Projects

How to use:

• Open your SAP repository
• Run: copilot (GitHub Copilot CLI interactive mode)
• Paste ONE prompt at a time
• Iterate with follow-up questions for deeper understanding

Tip:

• These prompts are intentionally verbose and explicit.
• Copilot performs best when given SAP-specific context.

1. MASTER PROMPT – FULL SAP PROJECT UNDERSTANDING

Use this when you first open an unfamiliar SAP repository

You are an experienced SAP Technical Architect.

Analyze this repository as an SAP project and explain it clearly and accurately.

Your output should include:

1. SAP landscape involved (ECC, S/4HANA, BW, BTP, CPI, Fiori, PI/PO, etc.)
2. Business purpose of the project (what problem it solves)
3. High-level architecture and system interactions
4. SAP modules involved (FI, CO, MM, SD, PP, HR, etc.)
5. Key technical assets:
   - ABAP programs, classes, function modules
   - CDS views, AMDP, RAP objects
   - Interfaces and services
6. Integration patterns (IDoc, RFC, OData, REST, SOAP, events)
7. Main business processes implemented (e.g., Order-to-Cash)
8. Configuration vs custom development split
9. Assumptions, dependencies, and risks
10. A README-style summary suitable for onboarding

Use correct SAP terminology.
Be precise and avoid speculation.
If something is unclear, state assumptions explicitly.

2. SAP ONBOARDING PROMPT – NEW ENGINEER VIEW

Best for quickly understanding a project as a new team member

Assume I am a new engineer joining this SAP project.

Create a concise onboarding guide that includes:

- What this SAP project does in simple terms
- Systems involved and how they communicate
- Key folders and files I should read first
- Important business flows and entry points
- How to debug or troubleshoot issues
- Common pitfalls or non-obvious behavior

Structure the response as a 30–60 minute onboarding walkthrough.

3. ABAP-CENTRIC ANALYSIS PROMPT

Use when the repository is primarily ABAP-based

Analyze this repository as an SAP ABAP project.

Explain:

- Custom vs standard SAP objects
- Naming conventions (Z/Y objects) and what they indicate
- Key ABAP artifacts:
  - Reports
  - Classes
  - Function modules
  - Enhancements, BADIs, user exits
- Transaction codes involved
- Performance considerations
- Transport and dependency order

Highlight any technical debt or risks.

4. S/4HANA & CLEAN CORE PROMPT

Ideal for modern SAP or cloud-aligned projects

Analyze this repository as an SAP S/4HANA project.

Focus on:

- Use of CDS views, AMDP, RAP, or OData services
- Fiori/UI5 components and backend services
- Extensibility approach (in-app vs side-by-side)
- Clean core compliance
- Deprecated ECC patterns (if any)
- Readiness for cloud or BTP deployment

Call out modernization opportunities.

5. INTEGRATION & MIDDLEWARE PROMPT

Best for CPI, PI/PO, or hybrid SAP landscapes

Analyze this SAP project focusing on integrations.

Explain:

- Source and target systems
- Integration patterns used:
  - IDoc
  - RFC
  - OData
  - REST / SOAP
- Middleware involved (CPI, PI/PO, MuleSoft, etc.)
- Message flow and data transformation
- Error handling and retries
- Security and authentication mechanisms

Summarize the end-to-end data flow.

6. BUSINESS PROCESS FLOW PROMPT

Use when business logic understanding is critical

Analyze this repository and identify the primary business processes implemented.

For each process:

- Business context and trigger
- SAP modules involved
- Technical execution flow
- Key tables and data objects
- Integration touchpoints
- Success and failure paths

Examples:
- Order-to-Cash
- Procure-to-Pay
- Record-to-Report

7. CONFIGURATION VS CUSTOMIZATION PROMPT

Useful for audits, upgrades, or risk assessments

Analyze this SAP project and classify:

- What is configuration-driven
- What is custom-developed
- Where standard SAP was extended or modified
- Any implicit business rules in code
- Upgrade or S/4HANA conversion risks

Provide a summary suitable for an architect or program manager.

8. TECHNICAL DEBT & QUALITY PROMPT

Use before refactoring or modernization

Review this SAP codebase and identify:

- Code smells and anti-patterns
- Performance risks
- Hard-coded values or assumptions
- Missing error handling
- Documentation gaps
- Opportunities for simplification or reuse

Provide prioritized recommendations.

9. SECURITY & COMPLIANCE PROMPT

Important for enterprise and regulated environments

Analyze this SAP project from a security perspective.

Focus on:

- Authorization checks
- Sensitive data handling
- Interface security
- Logging and auditability
- Compliance risks (SOX, GDPR, etc.)

Highlight any potential vulnerabilities.

10. README GENERATION PROMPT

Use to generate or improve repository documentation

Generate a professional README.md for this SAP project.

Include:

- Project overview
- SAP systems and modules
- Architecture overview (text-based diagram)
- Key business processes
- Deployment and transport considerations
- Known limitations
- Contact or ownership placeholders

Write for SAP consultants and architects.

BONUS: RECOMMENDED .github/copilot-instructions.md

Place this file in your repository root

This repository contains SAP-related code.
Use SAP terminology such as ECC, S/4HANA, ABAP, CDS, IDoc, RFC, CPI.
Assume the reader is an SAP consultant or architect.
Prefer enterprise-grade explanations over generic descriptions.
Avoid guessing—state assumptions explicitly.

---