1. Where Do SAP Changes Happen?
A. Configuration via SPRO
Purpose: Set up and customize SAP modules to align with business
processes.abapcookbook.com+1community.sap.com+1
Steps:
1. Execute transaction code SPRO.
2. Click on "SAP Reference IMG" to access the Implementation Guide.
3. Navigate through the modules (e.g., Financial Accounting, Sales and Distribution)
to configure settings.
Reference: SAP Help Portal – Implementation Guide
B. Enhancements via BADI (SE18/SE19)
Purpose: Implement custom logic without modifying standard SAP
code.community.sap.com+2sappond.wordpress.com+2community.sap.com+2
Steps:
1. Execute transaction code SE18 to display the BADI definition.
2. Use SE19 to create a new implementation.
3. Define the implementation name and implement the desired methods.
4. Activate the implementation to make it effective.
Reference: SAP Help Portal – Business Add-Ins (BAdIs)tcodesearch.com /
https://www.tcodesearch.com/sap-tcodes/ST03N?utm_source=chatgpt.com
C. ABAP Development via SE38/SE80
Purpose: Develop custom reports, programs, and applications.community.sap.com
Steps:
1. Use transaction code SE38 to create and execute programs.
2. Alternatively, SE80 provides an integrated development environment for
managing various development objects.sappond.wordpress.com
Reference: SAP Help Portal – ABAP Editortcodesearch.com /
https://www.tcodesearch.com/sap-tcodes/ST03N?utm_source=chatgpt.com
✅ 2. How Do We Manage SAP Data & Documents?
A. Data Archiving via SARA
Purpose: Move obsolete data to archive storage to optimize system performance.
Steps:
1. Execute transaction code SARA.
2. Select the appropriate archiving object (e.g., FI_DOCUMNT for financial
documents).
3. Follow the steps: Write → Store → Delete.
4. Monitor the archiving process and ensure successful completion.
Reference: SAP Community – Archiving SAP
Datacommunity.sap.com+5community.sap.com+5community.sap.com+5
B. Table Buffering via SE11
Purpose: Enhance performance by storing frequently accessed table data in memory.
Steps:
1. Execute transaction code SE11.
2. Enter the table name and click on "Display".
3. Navigate to "Technical Settings" to view or modify buffering settings.
Reference: SAP Community – Table Buffering in Application
Serverhelp.sap.com+7community.sap.com+7community.sap.com+7
C. System Monitoring via ST03N
Purpose: Analyze system performance and workload statistics.
Steps:
1. Execute transaction code ST03N.
2. Select the desired time period and instance.
3. Review workload data, including response times, transaction profiles, and user
statistics.
Reference: SAP Technical Guru – System Usage: ST03Nsaptechnicalguru.com
✅ 3. Can We Recover Deleted Data?
A. Archived Data
Recovery: Yes, archived data can be accessed using specific transactions.
Tools:
SARI: Search for archived data.
OAAD: Display archived documents.community.sap.com+1community.sap.com+1
Reference: SAP Community – Archiving SAP
Datacommunity.sap.com+1community.sap.com+1
B. Deleted Data (Not Archived)
Recovery: Generally not possible unless backups are available.
Tools:
DB12 and DB13: Monitor and schedule database backups.
Reference: SAP Help Portal – Database Backup and Recoverytcodesearch.com
C. Purged Data
Recovery: Not recoverable; purging is a permanent deletion
process.community.sap.com+1community.sap.com+1
Best Practices:
Implement data retention policies.
Ensure regular backups are in place.
Use Information Lifecycle Management (ILM) to manage data
aging.saptechnicalguru.com
Reference: SAP Community – Overview of ILM Policies and
Rulescommunity.sap.com+4community.sap.com+4community.sap.com+4
