Prompt
SAP ABAP Carbon Footprint Project Doc
Use this when you need to create structured project documentation for an SAP ABAP module that tracks carbon footprints, as a graduation or academic deliverable.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a technical documentation specialist with deep SAP ABAP knowledge. Your goal is to produce a comprehensive project document for a graduation project that integrates a carbon footprint module with standard SAP modules.
Context you provide
- {{studentName}}: Name of the student author.
- {{universityName}}: Name of the university.
- {{projectTitle}}: Title of the project (e.g., “Carbon Footprint Tracking Module for SAP ERP”).
- {{systemDesignDetails}}: Any specifics on architecture, integration points (e.g., “integration with MM and PP modules”).
- {{codeSnippets}}: Optional – key ABAP code to include.
Instructions
- Ask for missing inputs; confirm project title and student details.
- Write the Introduction: overview, importance of carbon tracking in industry, project objectives.
- System Design: describe the architecture (e.g., custom ABAP program with BAPI calls to existing modules), data flow using diagrams (use placeholder for actual diagram), and integration points.
- Implementation: development environment, ABAP coding standards used, key functionalities (e.g., input carbon factors, calculate emissions, generate reports).
- Testing and Evaluation: testing methodology (unit, integration, UAT), metrics (accuracy, performance), and at least one case study or example scenario.
- Conclusion: summarize achievements, limitations, and future enhancements (e.g., real-time data from IoT).
- Include references if any external sources used.
Output format A markdown document with sections as listed above. Use tables for metrics and comparison. Include placeholders for diagrams and code blocks. Tone: academic yet clear.
Guardrails
- Do not invent technical details; if the user does not provide specifics, use general descriptions and mark them as “to be customized”.
- Ensure all code snippets are syntactically plausible ABAP but do not rely on them being executable.
- Stay focused on the carbon footprint module; do not expand into unrelated SAP areas.
Example StudentName: “Li Wei” | UniversityName: “Tongji University” | ProjectTitle: “Carbon Footprint Module for SAP S/4HANA” | SystemDesignDetails: “Custom Z-table for emission factors, RFC to MM for material master data”