SAP (Systems, Applications and Products in Data Processing) is one of the most widely used ERP platforms across the world. Job interviews for SAP modules—whether ABAP, BW/BI, Basis, HANA, FICO, MM, SD, or HR—usually include questions on ERP fundamentals, SAP architecture, ABAP programming, BW concepts, reporting techniques, BDC, data dictionary, and real-time scenarios.
This complete interview guide compiles all important SAP questions in a structured, rewritten, and easy-to-understand format. It covers conceptual, technical, functional, and advanced topics. Whether you are a fresher or an experienced consultant, these questions help you gain deep clarity before interviews.
SECTION 1: BASIC ERP & SAP FUNDAMENTALS
1. What is ERP?
Enterprise Resource Planning (ERP) refers to integrated software solutions designed to manage an organization’s business processes. ERP systems unify functions like finance, production, HR, logistics, supply chain, and sales into a single platform.
The goal is to eliminate redundancy, improve data accuracy, enhance decision-making, and streamline operations.
Originally developed for manufacturing companies, ERP now covers all industries—from retail and banking to healthcare and government organizations.
2. What are the different ERP products?
Several ERP packages exist today. Popular solutions include:
-
SAP
-
Oracle / Oracle Financials
-
PeopleSoft
-
JD Edwards
-
BAAN
-
Siebel CRM
Among these, SAP is the global leader due to its flexibility, robust security, cross-functional integration, and vast module ecosystem.
3. What is SAP?
SAP is an enterprise-grade ERP software developed in 1972 in Germany (Systeme, Anwendungen und Produkte).
It offers comprehensive modules for:
-
Finance
-
Sales
-
Materials
-
HR
-
Production
-
Analytics
-
Supply Chain
-
Cloud
-
CRM
SAP is known for stability, scalability, and real-time business processing.
4. What is Business Content in SAP BW?
Business Content is a pre-built collection of BI objects delivered by SAP. It includes:
-
InfoCubes
-
InfoObjects
-
Queries
-
Extractors
-
Update rules
-
Roles
-
Workbooks
These ready-made models help companies implement analytics quickly without designing everything from scratch.
5. Why do companies prefer SAP?
Companies adopt SAP because:
-
Highly configurable
-
Strong integration across modules
-
Minimum redundancy, maximum consistency
-
Secured data processing
-
Strong global support
-
Wide industry solutions
-
Very stable & future-proof
6. Can SAP BW run without SAP R/3?
Yes. BW can load data from:
-
Flat files
-
Third-party databases
-
Non-SAP applications
With mapping tools and ETL connectors, BW can function independently of R/3.
7. What is IDES?
IDES (International Demonstration and Education System) is SAP’s training environment used for learning, demos, and practice.
8. What is SAP Workflow (WF)?
SAP Workflow automates business processes by coordinating:
-
Users
-
Tasks
-
Data
-
Approvals
Benefits include reduced processing time, lower cost, improved transparency, and better quality.
9. What is SAP R/3?
SAP R/3 is a 3-tier architecture consisting of:
-
Presentation layer (GUI)
-
Application layer (business logic)
-
Database layer (data storage)
It supports multinational business operations.
10. What are presentation, application, and database servers?
-
Presentation server: The SAP GUI installed on user machines
-
Application server: Executes ABAP programs, manages logic
-
Database server: Stores SAP tables and data
SECTION 2: ABAP, DATA DICTIONARY & TECHNICAL CONCEPTS
(✔ All answers rewritten & expanded)
11. What is the approach to writing a BDC program?
Steps:
-
Extract legacy data → convert into flat file
-
Load flat file into internal table
-
Create BDC session or use CALL TRANSACTION
-
Handle errors
-
Process session
12. Open SQL vs Native SQL
Open SQL
-
Database-independent
-
Works across all SAP-supported DBs
-
Safer & recommended
Native SQL
-
Database-specific
-
Executed directly using EXEC SQL
-
Not portable across systems
13. What are datasets?
Sequential files processed on the application server using DATASET statements. Used for file handling.
14. Internal table, check table, value table, transparent table
-
Internal Table: Temporary in-memory table
-
Check Table: Used for foreign key validation
-
Value Table: Domain-level fixed values
-
Transparent Table: 1:1 mapping between DDIC & database
15. Benefits of BW reporting over R/3
-
High performance
-
Designed for analytics
-
Uses OLAP engine
-
Reduces load on OLTP system
16. How does ERP help business understanding?
Users learn integrated business flows (sales → finance → production), gaining deep operational knowledge.
17. Difference between OLAP & Data Mining
-
OLAP: Reporting, analysis, predefined queries
-
Data Mining: Pattern detection, predictive analytics
18. Extended Star Schema
SAP BW separates master data into independent tables linked through SID tables, extending traditional star schema.
19. Meta Data, Master Data, Transaction Data
-
Meta Data: Data about data
-
Master Data: Stable long-term data
-
Transaction Data: Day-to-day business transactions
20. Drawbacks of SAP
-
Expensive
-
Complex
-
Long implementation
-
Requires skilled staff
ABAP TECHNICAL DEEP DIVE (BDCs, TABLES, DDIC, REPORTING, UI)
This section explains the core ABAP technical building blocks hiring managers test for: internal tables, BDC and Call Transaction, table types, data dictionary elements (domains/data elements), reporting tools (ABAP Query, ALV), screen programming, scripts and forms, transports (CTS) and integration objects (IDocs/RFCs).
Internal Tables, Field Symbols, and Performance
Internal tables are in-memory data structures used heavily in ABAP. They simulate database tables at runtime and are crucial for aggregations, joins, temporary storage and reformatting. Key points:
-
Types:
STANDARD TABLE,SORTED TABLE,HASHED TABLE. Choose based on lookup/update patterns:-
STANDARD— good for appending/looping; index-based access. -
SORTED— keeps data sorted by key; binary search available. -
HASHED— fastest for key-based direct access, no index access.
-
-
Use
FIELD-SYMBOLSfor zero-copy processing (ASSIGN <fs> TO <itab>-line), reducing memory overhead and improving speed. -
Use
READ TABLE itab WITH KEYcarefully — for large tables prefer proper keys or hashed tables. -
Use
COLLECTto aggregate numeric values into an internal table with a key;APPENDsimply adds rows.
Performance tips:
-
Avoid nested loops over large tables — replace with hashed lookups or sort + binary search.
-
Use
SELECTwithINTO TABLEto do bulk fetches; useSELECTfields when you don’t need entire row. -
Use proper buffering and indexes on DB tables to reduce I/O.
Data Dictionary (DDIC): Domains, Data Elements, Tables & Indexes
Domain defines the technical attributes of a field: data type, length, decimals, and value ranges.
Data Element gives semantic meaning — short text labels and references to domains. Developers create tables with fields that reference data elements, so UI and reports show meaningful texts.
Table types in DDIC:
-
Transparent Table: Has a one-to-one mapping in the database. Use for application data.
-
Pooled Table: Many logical tables stored together in a table pool in the RDBMS. Rarely used for modern apps.
-
Cluster Table: Groups several related tables stored in a single physical table (cluster). Used for specific SAP scenarios; not common for new developments.
-
Internal Table: Not a DDIC object; runtime only.
Check table vs Value table:
-
Check Table: used for foreign key check at field level — ensures relational integrity on input.
-
Value Table: recommended domain-level default table for value checks.
Indexes:
-
Add indexes to speed up SELECT queries on frequently filtered fields.
-
Balance: more indexes = faster reads but slower writes and more space. Choose primary and secondary indexes wisely.
Open SQL vs Native SQL vs EXEC SQL
-
Open SQL: SAP’s portable subset of SQL. Database independent, recommended for ABAP programs.
-
Native SQL: Passes DB-specific SQL statements (e.g., Oracle syntax). Use only when DB-specific features are required.
-
EXEC SQL: Dynamic, embedded SQL using the database’s native syntax — breaks portability and should be used cautiously.
Reporting Tools: ABAP/4 Query, ALV and Interactive Reports
ABAP/4 Query
-
A no-code or low-code tool to build reports quickly using user groups, functional areas, and logical DBs.
-
Good for simple reporting needs and rapid prototyping; limited for complex logic.
ALV (ABAP List Viewer)
-
ALV enhances list output: column sorting, exporting, variants, layouts, and interactive features.
-
There are several flavors:
REUSE_ALV_LIST_DISPLAY,CL_GUI_ALV_GRID,CL_SALV_TABLE(modern OO wrapper). -
Use ALV for tabular reports that require dynamic UI features, column dialogs, totals and quick data analysis.
Interactive and Drill-Down Reports
-
Interactive reports allow the user to double-click rows to trigger secondary logic (
AT LINE-SELECTION), creating drill-down navigation. -
Use modularization and event-driven logic (selection screen → start-of-selection → top-of-page → end-of-selection → at line-selection) to structure interactive outputs.
BDC (Batch Data Communication) and Call Transaction
When migrating legacy data or automating UI-driven transactions, two common options are:
BDC (Batch Input Sessions)
-
BDC reads data and simulates user input to SAP screens, storing actions in sessions.
-
Typical functional modules used:
-
BDC_OPEN_GROUP— open session group -
BDC_INSERT— insert records into session -
BDC_CLOSE_GROUP— close session
-
-
Sessions can be processed interactively or in background. Use session monitoring and error handling to retry or log failures.
-
Pros: Mimics exact transaction flow; good for complex screen sequences.
-
Cons: Sensitive to screen changes and slow compared to direct updates.
CALL TRANSACTION USING (Call Transaction)
-
CALL TRANSACTIONruns the transaction in the same process and can be used for synchronous processing. -
Use
CALL TRANSACTION ... USING bdcdata MODE 'A'or withBATCHoptions. -
It’s faster than session processing but runs in the same work process and may fail without session recovery.
Alternative to BDC: Use direct API or BAPI calls where available — they are more robust, DB-safe and less dependent on screen flows.
Uploading Data: CATT, LSMW, and Other Tools
-
CATT (Computer Aided Test Tool) — originally for automated testing and upload; can record transactions and upload data.
-
LSMW (Legacy System Migration Workbench) — the more modern, supported tool for uploading master data & transactions using recording, conversions, and BAPI/IDoc/Batch input methods.
-
BAPI and IDoc — recommended when available: standard programmatic interfaces for data exchange.
Steps for CATT/LSMW:
-
Record transaction or mapping.
-
Export template.
-
Prepare and modify source file.
-
Upload and execute; review logs & errors.
Smart Forms, SAPscript and Layouts
SAPscript
-
Older SAP printing solution. Components:
-
Layout Sets — windows, pages, paragraph and character formats.
-
Standard texts and forms assembled by ABAP programs via function modules.
-
-
SAPscript uses SAPGUI for design but is being phased out.
Smart Forms
-
Graphical tool to create forms (in place of SAPscript). Advantages:
-
Better UI for designing forms
-
Supports colors and improved formatting
-
Easier maintenance and faster development
-
-
Smart Forms generate a function module which ABAP programs call to print or display documents.
Recommendation: Use Smart Forms (or Adobe Forms in newer landscapes) for print outputs. Migrate old SAPscript where possible.
Screen Programming: DynPro, Screen Painter, Menu Painter, Flow Logic (PBO/PAI)
DynPro (Dynamic Programming) represents SAP screens and their logic. Each screen (DynPro) contains layout and flow logic sections.
-
Screen Painter: Visual tool to design screen layout components.
-
Menu Painter: Design menus, GUI status, function keys, titles.
-
PBO (Process Before Output): Event block executed before screen is rendered — initialize screen fields, set attributes.
-
PAI (Process After Input): Event block executed after user action — validate input, perform actions, navigate.
Use modular coding, validations in PAI, and minimal code in PBO to keep screens responsive.
Transport Management: CTS (Change & Transport System)
CTS organizes development objects into change requests and transports them across system landscape (DEV → QA → PROD). Key points:
-
Transport tasks contain objects (programs, table entries, layout sets).
-
Choose transport strategy: branching, package assignment and authorizations.
-
Client-dependent objects vs client-independent: ensure correct objects are captured. Certain customizing may require separate transport of customizing requests.
Follow strict CTS policies in team projects: version control, transport locks, and documentation.
Logical Databases & Their Use
Logical databases provide a hierarchical view of related tables and offer built-in GET events and selection functionality. Advantages:
-
Centralized authorization checks
-
Reusable selection logic across reports
-
Improved read performance for hierarchical retrievals
Disadvantages:
-
Less flexible for complex logic
-
GET events require specific program structure
-
Limited to read-only access
ABAP Query can use logical DBs to speed up report creation; otherwise modern approaches rely on Open SQL or AMDP/HANA views.
IDocs and RFC — Integration Interfaces
IDoc (Intermediate Document):
-
SAP’s standard format for asynchronous data exchange.
-
Common for EDI, EAI and communication with third-party systems.
-
IDocs are processed by inbound/outbound ALE layers; map data segments to application logic.
RFC (Remote Function Call):
-
Synchronous or asynchronous function call mechanism between SAP systems or external programs.
-
Synchronous RFC (sRFC) — waits for response.
-
Transactional RFC (tRFC) and Queued RFC (qRFC) — provide guaranteed delivery and transactional integrity for asynchronous processing.
Use IDocs for decoupled, message-based integration and RFC/BAPI for direct, procedural integration.
Error Handling and Debugging in Batch Processes
When batch sessions or background jobs fail:
-
Check SM35 for session logs.
-
Review job logs in SM37.
-
Use ST22 for dump analysis and check short dumps.
-
For performance, analyze SQL statements with ST05 (SQL trace) and check expensive SELECTs.
For BDC sessions: log failed records, provide retry utilities, and build idempotent import routines to avoid duplicates.
Use ALV for rich interactive reports and ABAP Query for quick reports.Prefer Open SQL for portability; use native SQL sparingly.For data migration, prefer BAPI/IDoc/LSMW over raw screen simulation when possible.Use Smart Forms/Adobe for modern form output; move away from legacy SAPscript.Optimize internal tables and indexes; choose appropriate table type for use case.Organize transports with CTS and maintain strict change control.For integration, choose RFC for synchronous and IDoc for asynchronous scenarios.
SAP BW/BI (Business Warehouse / Business Intelligence) COMPLETE INTERVIEW GUIDE
SAP BW/BI is one of the most crucial parts of SAP’s analytics ecosystem. Companies rely on BW to extract, store, model, and analyze business data. This section covers every major BW concept used in interviews—from InfoCubes and ODS objects to ETL, metadata, and reporting through Business Explorer.
4.1 What Is SAP BW/BI?
SAP BW (Business Warehouse), later evolved into BI (Business Intelligence), is SAP’s enterprise data warehousing solution. It provides a central repository to collect data from multiple SAP and non-SAP systems, clean it, consolidate it, and make it available for reporting and analytics.
Key features:
-
Data Modeling
-
Data Extraction
-
Staging & Transformation
-
Storage in InfoCubes, DSOs, MultiProviders
-
Reporting using BEx tools
-
OLAP processing
-
Delta loading capabilities
BW is used for high-level analytics, management dashboards, KPIs, and business performance reporting.
4.2 What Is Business Content? (Fully Rewritten)
Business Content is a library of pre-delivered SAP BI objects designed to provide ready-to-use analytics. It includes:
-
InfoObjects
-
InfoCubes
-
DSO/ODS objects
-
Queries
-
Workbooks
-
Update Rules
-
Transfer Rules
-
Roles & authorizations
-
Extractors for SAP modules (FI, CO, HR, MM, SD etc.)
Benefits:
-
Speeds up implementation
-
Reduces development efforts
-
Provides SAP-standard best practices
-
Ensures compatibility with R/3 and ECC data structures
Companies use Business Content when they want standard analytics without building everything from scratch.
4.3 What Is an InfoCube?
An InfoCube is a multi-dimensional data model used for OLAP reporting. It consists of:
-
Fact Table → Stores key figures (measures)
-
Dimension Tables → Store foreign keys for characteristics
-
SID Tables → Master data reference
-
Master Data Tables → Attributes, texts, hierarchies
InfoCubes follow the Extended Star Schema, SAP’s optimized model for faster reporting.
4.4 What Is Extended Star Schema?
Extended Star Schema enhances the classical star schema by:
-
Storing master data (attributes, texts, hierarchies) in separate tables
-
Keeping dimension tables small
-
Improving performance of fact table joins
-
Reusing master data across multiple InfoCubes
Advantages:
-
Reduced redundancy
-
Smaller dimension tables → faster joins
-
Better scalability
4.5 What Is a DSO / ODS Object?
A DSO (Data Store Object) or ODS holds detailed, document-level data at an atomic level.
It consists of:
-
Active table – final, consolidated data
-
Change log – delta entries
-
New data table – staging layer
Use ODS when:
-
Detailed reports are needed
-
You need overwrite capability
-
Change history tracking required
-
Data acts as staging for InfoCubes
Difference from InfoCube:
| Feature | ODS/DSO | InfoCube |
|---|---|---|
| Data Type | Transaction-level | Aggregated |
| Storage | Transparent tables | Multidimensional |
| Reporting | Detail reporting | Summary reporting |
| Delta | Overwrite / append | Only append |
4.6 What Is AWB (Administrator Workbench)?
AWB is the central cockpit for BW administration.
You use AWB for:
-
Data modeling
-
ETL monitoring
-
Managing InfoObjects
-
Activating data targets
-
Checking load failures
-
Performance tuning
-
Creating transfer/update rules
-
Scheduling data loads
Think of AWB as the “control center” for BW operations.
4.7 What Are Transfer Rules & Update Rules?
Transfer Rules
Define how data maps from Source System → Communication Structure.
Used before 7.0 versions; replaced by Transformations later.
Update Rules
Define how data goes from Communication Structure → Data Target (Cube/ODS).
After SAP BI 7.0:
-
Transfer rules + update rules are replaced with Transformations
-
Mapping is done using Transformation & DTP (Data Transfer Process)
4.8 What Is an Extractor?
Extractors are mechanisms that retrieve data from SAP/non-SAP source systems into BW. They fill the extract structure for a DataSource.
Types of extractors:
-
Content extractors (FI, CO, MM, SD, HR etc.)
-
Logistics cockpit extractors
-
Generic extractors (table/view/function module)
-
Delta-capable extractors
Extraction methods:
-
Full load
-
Delta load
-
Init + delta
4.9 Types of Source Systems
BW supports:
-
SAP R/3 / ECC
-
SAP BW itself
-
Flat files (CSV, TXT)
-
External systems (Oracle, SQL Server, Apps)
-
Third-party ETL tools (Informatica, DataStage)
-
Web services / API
4.10 What Is Metadata, Master Data & Transaction Data in BI?
Meta Data
-
Describes structure of data
-
Definitions of tables, fields, relationships
-
Technical/semantic properties
Master Data
-
Long-term reference data
-
Example: Customer, Material, Vendor
Transaction Data
-
Day-to-day business values
-
Example: Sales quantity, billing records
4.11 What Is BEx? (Business Explorer)
SAP BEx is the BW reporting layer.
It includes:
-
BEx Analyzer – Excel-based reporting
-
BEx Query Designer – Build queries
-
BEx Browser – Launch queries
-
BEx Web – Web-based analytics
-
BEx Map – Geo analysis
BEx queries define:
-
Filters
-
Key figures
-
Structures
-
Variables
-
Navigational states
4.12 What Are Variables in BEx?
Variables allow dynamic input during query runtime.
Types:
-
Characteristic variables
-
Hierarchy variables
-
Text variables
-
Formula variables
-
Processing types (manual input, replacement path, authorization variable)
Used for:
-
Dynamic filtering
-
User-specific reports
-
Reusable query logic
4.13 What Are ODS/DSO Key Features?
-
Stores detailed transactional data
-
Supports overwrite capability
-
Allows delta propagation
-
Suitable for audit-level reporting
-
Flat table storage (transparent DB tables)
-
Acts as staging for InfoCubes
4.14 Explain Delta Loads in BW
Delta load ensures only changed records are loaded after the initial load.
Delta types:
-
After image
-
Before image
-
Additive delta
-
Delta queue-based
-
Delta initialization
Delta mechanisms help avoid reading full data sets repeatedly.
4.15 Why Not Use R/3 Directly for Reporting?
Reasons BW is superior:
1. Performance
Heavy OLAP queries slow down OLTP (ECC/R3) systems.
2. Data Consolidation
BW collects data from multiple systems.
3. Historical Storage
ECC stores limited history; BW stores years of data.
4. Predefined Models
SAP provides InfoCubes and extractors for quick analytics.
5. Faster Querying
OLAP engine optimized for analytical queries.
6. Scalability
BW handles massive data loads efficiently.
4.16 AWB Monitoring & Data Load Checks
BW administrators check:
-
Load failures
-
Short dumps
-
Error requests
-
PSA failures
-
Delta queue issues
-
DB locks
-
Aggregates / compression issues
Tools used:
-
RSA1 – Administration Workbench
-
RSMO – Monitor
-
ST22 – Dumps
-
SM37 – Background jobs
4.17 What Are InfoObjects?
Basic building blocks of BW.
Two types:
-
Characteristics → Customer, Material, Plant
-
Key Figures → Quantity, Sales, Amount
Characteristics have:
-
Texts
-
Attributes
-
Hierarchies
Key figures have:
-
Aggregation types
-
Units
-
Currency conversions
4.18 InfoSet & MultiProvider
InfoSet
-
Joins multiple ODS/DSO objects
-
Used for detail reporting
-
Does NOT support Cubes
MultiProvider
-
Logical union of multiple InfoProviders
-
Supports Cubes, DSOs, InfoSets
-
Used for combined reporting
4.19 What is Open Hub?
Used for exporting BW data to:
-
Flat files
-
External DB
-
3rd-party systems
It supports controlled, scheduled data extraction.
4.20 Administrator Responsibilities (BI Consultant Role)
SAP BI consultants must handle:
-
Data modeling
-
Creating Transformations & DTPs
-
BW queries design
-
Monitoring data loads
-
Fixing extractor issues
-
Performance tuning
-
Managing master data
-
Enhancing BI content
✔ ABAP Technical Interview 100+ Questions (FULL REWRITTEN)
including:
-
BDC
-
Batch Jobs
-
LDB
-
IDocs
-
RFCs
-
SAP Scripts
-
SmartForms
-
Data Dictionary
-
Selection Screens
-
Background Jobs
-
Table Maintenance
-
Performance Optimization
5.1 What Is the Typical Structure of an ABAP Program?
ABAP program runs based on events, not sequential execution like normal languages.
Standard structure includes:
-
REPORT / PROGRAM statement
-
TYPE-POOLS, TYPES, CONSTANTS
-
DATA declarations
-
SELECTION-SCREEN (optional)
-
START-OF-SELECTION (main logic)
-
TOP-OF-PAGE, END-OF-PAGE (for reports)
-
FORM routines or METHODS
-
END-OF-SELECTION
-
LIST EVENTS (AT LINE-SELECTION for interactive reports)
ABAP event blocks control program flow, making the structure predictable and modular.
5.2 What Are Field Symbols & Field Groups?
Field Symbols (like pointers in ABAP)
Used for dynamic field access without copying data.
Syntax:Benefits:
-
Faster processing
-
No memory duplication
-
Ideal for loops & dynamic assignments
Field Groups
Used in extract datasets (rare in new projects).
Help structure extract data for sorting/summarizing.
5.3 Best Approach for Writing a BDC Program
-
Record transaction (SHDB).
-
Convert legacy file → internal table.
-
Populate BDC structure (BDCDATA).
-
Use BDC session or CALL TRANSACTION to update SAP.
-
Log errors for reprocessing.
5.4 What Is a Batch Input Session?
A batch input session stores:
-
Screens
-
Fields
-
Values
-
Transaction codes
-
Sequence of user actions
Sessions are processed later using SM35.
5.5 Alternative to Batch Input Session
-
CALL TRANSACTION USING
-
BAPI
-
IDoc
-
LSMW
-
Direct Input Programs (DIP)
-
BODS (in some landscapes)
5.6 How to Run Program + Batch Session in Background?
Use:
Process batch session using SM35 with background run.
5.7 Difference Between Pool Table & Transparent Table
Transparent Table
-
1:1 mapping with DB table
-
Holds application data
Pooled Table
-
Many SAP tables → stored inside one DB table
-
Used for small tables like TSTC, TVARV
5.8 Problems While Processing Batch Input Sessions
-
Screen changes cause failure
-
Missing mandatory fields
-
Incorrect field sequence
-
Authorizations issues
-
Data format mismatches
-
Locks on tables
Batch input = slow + screen dependent → better use BAPIs whenever available.
5.9 What Do You Define in Domain & Data Element?
Domain
Technical attributes:
-
Type (CHAR, NUMC, DEC, INT etc.)
-
Length
-
Value range
Data Element
Semantic attributes:
-
Field description
-
Labels
-
Search helps
5.10 Types of Data Dictionary Objects
-
Tables (Transparent, Pooled, Cluster)
-
Views (Database, Projection, Maintenance, Help)
-
Search Helps
-
Lock Objects
-
Data Elements
-
Domains
-
Structures
-
Table Types
5.11 Types of Tables
-
Transparent
-
Pooled
-
Cluster
5.12 Steps to Create a Table in DDIC
-
Create table → set delivery class
-
Assign fields with elements
-
Define key fields
-
Create technical settings
-
Create indexes
-
Maintain foreign keys
-
Activate table
5.13 Can Transparent Table Exist Without Physical DB Table?
Yes — before activation.
After activation: both dictionary + database are synchronized.
5.14 Can You Create Table Fields Without Data Elements?
Yes, using direct type.
But not recommended because:-
No reusability
-
No F4 help
-
No description
-
Hard to maintain
5.15 Advantages of Structures
-
Reusable for internal tables
-
Use in global structures
-
Simplify modular programming
-
Helpful for interface design
5.16 What Does EXTRACT Statement Do?
Used in extract datasets (old reporting).
It collects records for sorting/summarizing before writing output.
5.17 Difference Between COLLECT & APPEND
APPEND
Adds new line.
COLLECT
Aggregates existing line based on key → sums numeric fields.
5.18 Open SQL vs Native SQL
Already covered above.
Open SQL = DB independent
Native SQL = DB-specific
5.19 What Does EXEC SQL Do?
Executes DB-specific SQL code.
Disadvantages:
-
Not portable
-
No syntax check
-
Dangerous if not careful
5.20 ABAP Editor Integrated With DDIC
Means:
-
F4 help from dictionary
-
Field labels auto picked
-
Type checking
-
Automatic formatting
5.21 ABAP Events
-
INITIALIZATION
-
AT SELECTION-SCREEN
-
START-OF-SELECTION
-
END-OF-SELECTION
-
TOP-OF-PAGE
-
END-OF-PAGE
-
AT LINE-SELECTION
-
AT USER-COMMAND
5.22 What Is an Interactive Report?
Classic report with “drill down”.
After user clicks on line:
-
AT LINE-SELECTION triggers
-
Second list displayed
5.23 Drill Down Report
Multi-level reporting where user navigates to detailed data.
Used in FI/CO/MM/SD analytics.
5.24 How to Write a Function Module
Steps:
-
Go to SE37
-
Create F.M
-
Define import/export parameters
-
Add tables/changing
-
Write logic
-
Activate
-
Assign to Function Group
5.25 Exceptions in FMs
Used for error handling:
or
Exception numbers.
5.26 What Is a Function Group?
Collection of function modules sharing:
-
Global data
-
Memory area
5.27 How SAP Stores Date & Time
-
DATE → YYYYMMDD
-
TIME → HHMMSS
Stored as character type internally.
5.28 Fields in BDC_Tab Table
-
Program
-
Dynpro
-
Dynprostart
-
FNAM
-
FVAL
5.29 Few Data Dictionary Objects
-
Domains
-
Data elements
-
Tables
-
Views
-
Search helps
-
Lock objects
5.30 What Happens When Table Is Activated?
-
Dictionary → DB table created
-
Indexes created
-
Buffers invalidated
-
Metadata updated
5.31 What Is Check Table vs Value Table?
Already covered above.
5.32 What Are Matchcodes?
Old search help mechanism superseded by modern search help.
5.33 Transactions Used for Data Analysis
-
SE16 / SE16N
-
SQ01 / SQ02 / SQ03
-
RSA3 (extract preview)
-
RSRT
-
LISTCUBE
5.34 Table Maintenance Generator
Used to generate:
-
Maintenance dialog
-
Insert/update/delete screens
Transaction → SE54 / SM30
5.35 What Are Ranges & Number Ranges?
Ranges
RANGE TYPE: LOW, HIGH, EQ/BT/GE/CP
Number Ranges
Used for generating unique document numbers (FI, MM, SD).
5.36 Select Options vs Parameters
PARAMETERS SELECT-OPTIONS Single value Multiple values No intervals Supports ranges Easy More powerful
5.37 How to Validate Selection Screen?
Use:
To display default values:
5.38 What Are Selection Texts?
Labels used for fields in selection screen (maintained via Goto → Texts).
5.39 CTS (Change Transport System)
Explained in previous section.
5.40 Are Programs Client Dependent?
Standard ABAP programs → client independent
Some SAPscript, variants, TMG → client dependent
5.41 System Global Variables
-
SY-DATUM
-
SY-UZEIT
-
SY-UNAME
-
SY-SUBRC
-
SY-MANDT
-
SY-REPID
5.42 How to Count Internal Table Lines?
Or:
5.43 Performance Techniques
-
Use SELECT with WHERE
-
Avoid SELECT *
-
Use proper indexes
-
Use hashed tables for lookups
-
Run ST05 SQL trace
-
Use parallel cursor technique
5.44 What Are Datasets?
File handling on application server.
5.45 How to Get Return Code of SQL?
Check:
5.46 Interface / Conversion Programs
Used for:
-
Migrating master data
-
Migrating transactional data
Tools:
-
BDC
-
BAPI
-
IDoc
-
LSMW
5.47 Using SAP Supplied Programs to Load Data
SAP provides:
-
RFBIBL00
-
RFBIDE00
-
RMDATIND
-
RM06IBI0
Better use LSMW & BAPI for modern systems.
-
ADVANCED SAP TECHNICAL (IDocs, RFCs, BAPIs, SAPscripts, Smart Forms, Batch Jobs, Debugging, Screens, Transactions)
This section covers advanced SAP topics that interviewers ALWAYS focus on for experienced ABAP developers. These concepts define your real-time project knowledge, integration understanding, and problem-solving skills.
6.1 What Are IDocs? (Fully Rewritten)
IDoc (Intermediate Document) is a standard SAP data exchange format used for asynchronous communication between systems.
Used in:
-
EDI interfaces (Orders, Invoices)
-
Integration with external systems
-
ALE scenarios (Distributed SAP systems)
-
Master data transfers
-
Third-party communication
Key components:
-
Control Record → Sender, receiver, message type
-
Data Records → Segments containing actual data
-
Status Records → Logs (success/failure)
IDoc Types:
-
Basic Type – SAP-delivered structure
-
Extension Type – Customized fields
-
Message Type – Business meaning (ORDERS05, MATMAS etc.)
Processing:
-
Inbound → External → SAP
-
Outbound → SAP → External
Transactions:
-
WE02/WE05 (monitor)
-
WE19 (test tool)
-
BD87 (reprocess)
6.2 What Are RFCs (Remote Function Calls)?
RFCs allow two systems to communicate and execute function modules remotely.
Types:
-
sRFC – Synchronous RFC (waits for response)
-
tRFC – Transactional RFC (queued + guaranteed delivery)
-
qRFC – Queued RFC (ensures sequence)
-
bgRFC – Background RFC (advanced reliable delivery)
Advantages:
-
Reliable
-
Fast
-
Standard SAP communication
-
Used for BAPI calls across systems
Used in:
-
SAP integration
-
Third-party connection
-
Middleware integration (PI/PO, CPI)
6.3 What Are BAPIs?
BAPI = Business Application Programming Interface.
These are standardized APIs to access SAP business functionality.Features:
-
SAP standard
-
Used for CRUD operations
-
Stable interfaces
-
Preferred instead of BDC
-
Used in integrations, migration, mobile apps
Examples:
-
BAPI_MATERIAL_SAVE_DATA -
BAPI_SALESORDER_CREATEFROMDAT2 -
BAPI_PO_CREATE1
Advantage over BDC:
-
Faster
-
Screen independent
-
Upgrade safe
-
Error handling available
6.4 SAP Script & Smart Form Differences
SAPscript Smart Forms Older technology Modern & graphical Complex maintenance Easy drag-drop UI No color/image support Supports advanced formatting Multiple windows limited Rich layout options Requires driver program Generates FM automatically Smartforms recommended for new developments.
6.5 What Is Output Determination?
SAP determines what document prints, how it prints, to whom, and when.
Used in:
-
Sales order output
-
Billing document
-
Purchase order print
-
Delivery note
-
Invoice print
Controlled by:
-
Condition tables
-
Access sequences
-
Output types
-
Procedures
Transactions:
-
NACE → Configuration
-
VF31 → Reprint billing
6.6 What Are Screen Painter, Menu Painter & Flow Logic?
Screen Painter
Used for designing DynPro screens:
-
Input fields
-
Texts
-
Tables
-
Buttons
-
Subscreens
Menu Painter
Designs GUI elements:
-
Menu bar
-
Toolbar buttons
-
PF keys
-
Function codes
Flow Logic
Controls screen behavior:
PBO (Process Before Output)
-
Prepare screen
-
Set defaults
-
Manipulate field attributes
PAI (Process After Input)
-
Validate user input
-
Trigger function codes
-
Write back data
6.7 What Are Step Loops?
Step loops are repeated screen blocks used to display multiple records on screen.
Used in:
-
Table controls
-
Multi-line data entry screens
Paging (Page up/down) coded in:
-
LOOP AT statements
-
Scroll logic
6.8 How Do You Write Transaction Programs in SAP?
Steps:
-
Build DynPro screens
-
Assign PBO/PAI events
-
Write business logic in modules
-
Create a transaction code in SE93
-
Link to program
-
Test navigation, authorization checks
6.9 What Files Are Generated in Transaction Programs?
-
TOP include
-
O01 include (PBO)
-
I01 include (PAI)
-
C01 include (subroutines)
XXXXXTOP is a default include containing:
-
Global variables
-
Data declarations
-
Type definitions
6.10 Include Programs
Reusable pieces of code:
-
TOP include
-
FORM routines
-
DYNPRO logic
-
Submodules
Used for modular programming and team development.
6.11 Can You Call Subroutines Across Programs?
Yes.
Using:
Note:
-
Must be PUBLIC
-
Calling program must have access
6.12 What Are User Exits?
User exits allow customer enhancements without modifying SAP standard code.
Types:
-
Function module exits
-
Screen exits
-
Menu exits
-
Field exits
Tools:
-
SMOD (exit info)
-
CMOD (project to implement exit)
Requirement:
-
Create extra logic inside SAP-approved extension points
6.13 Background Jobs – How to Create?
Used to run programs automatically.
Steps:
-
Go to SM36
-
Create job
-
Assign ABAP program
-
Set variant
-
Set schedule (time/event)
-
Save
Monitor via SM37.
Event-driven jobs trigger when an event occurs:
-
Finance closing
-
Data load finish
-
IDoc arrival
6.14 Host Commands from SAP
Use:
Or SXPG_COMMAND_EXECUTE.
6.15 Financial Period Tables
Table: T009 (Fiscal year variant)
Controls:-
Periods
-
Special periods
-
Year shifts
6.16 Does SAP Support Multiple Currencies & Languages?
YES.
SAP is globally enabled.Supports:
-
40+ languages
-
Multi-currency
-
Unicode
-
Country-specific configurations
6.17 Currency Factoring Technique
Used for currency conversion (e.g., JPY doesn’t use decimals).
SAP uses factor (100 or 1) to normalize currency calculations.6.18 How Do You Document ABAP Programs?
Options:
-
SE38 → Documentation
-
Program comments
-
SAPscript texts
-
Functional/Technical specs
-
Transport documentation
6.19 SAP Script Commands That Link to Layout Set
-
WRITE_FORM
-
OPEN_FORM
-
CLOSE_FORM
-
START_FORM
-
END_FORM
6.20 What Are IDOCs?
Already explained above — asynchronous communication tool.
6.21 What Is Screen Flow Logic?
Two major blocks:
-
PBO → Before rendering
-
PAI → After user input
Additional:
-
MODULE … END MODULE
-
FIELD statements
-
CHAIN/ENDCHAIN
6.22 Logical Database Related Questions
Already explained — used in ABAP Query, hierarchical data selection.
6.23 Finding Table Names Behind Transactions
Methods:
-
Technical help (F1 → F9)
-
System → Status → Program → Table
-
Debugger (watch variables)
-
ST05 SQL trace
-
SE84 repository search
6.24 IMG – Implementation Guide
IMG is SAP’s configuration tool (SPRO).
Used for:-
Customizing
-
Business processes setup
-
Functional configuration
6.25 SAP Help & ABAP Editors
Editors:
-
SE38
-
SE80
-
ADT (Eclipse) – Modern and recommended
6.26 Layout Set Elements
-
Windows
-
Pages
-
Paragraph formats
-
Character formats
-
Graphic areas
6.27 SAPScript Variables for Output
-
&VAR& → value
-
&SY-DATUM& → system date
-
&VBDKR-VBELN& → table-field variables
6.28 Page Numbering in SAPScript
Use system symbol:
6.29 Backup SAP Scripts
Use:
-
RSTXSCRP program for import/export
-
SE71 → Upload/Download
6.30 Presentation vs Application Server
Presentation server: local PC (GUI)
Application server: runs code & logic6.31 Accessing Data from Presentation vs Application Server
Presentation →
GUI_UPLOAD
Application → DATASET statements6.32 Data Types in ABAP
-
Elementary types (C, N, D, T, I, P, F)
-
Complex types (structures, tables)
-
Reference types
6.33 BDC vs Call Transaction
BDC Session Call Transaction Offline processing Synchronous Logs stored Logs optional Slower Faster Good for large loads Best for real-time 6.34 Packed Fields for BDC
Packed numbers must be converted to CHAR using:
-