Data dictionary
1.Tables (SE11)
Tables store the actual data in the database. There are two types of tables:
• Transparent Tables: Directly map to database tables.
o Example: MARA (Material Master) – Stores basic information about materials.
• Cluster and Pool Tables: Used for storing long text or serialized data, though they are less
common in modern implementations.
o Example: TCULOG (Transaction Log) – Stores long texts
2 What is delivery class
delivery class defines how a data base can be transported during installation, upgrading, copies
with in
landscapes, clients and customer systems.
Types of delivery class are
• Application Table (Master and Transaction Data)
• Customizing Table (Configuration, Changeable)
• Table for storing temporary data.
• Customizing Table, Protected Against Changes During Upgrades.
• Control Table (SAP and Customer)
• System Table (Entries Only Transportable by SAP)
3 How to Enhance the standard table
We can enhance table by using append / Include. We need to create new structure with required
fields
and append to table by using these two functionalities.
4. TMG -Table Maintenance Generator (SM30)
It is a tool used to generate standard maintenance views and screens for database tables, allowing
users to perform data entry and modification directly in the SAP GUI
5.Locks Objects
The lock object specifies which type of lock is to be used (e.g., single record lock, full table lock,
collective lock).
ENQUEUE and DEQUEUE function modules – These are the ABAP function modules used for
programmatically setting and releasing locks within a program.
Reports
1.Classical ALV Report Example
Classical ALV reports are created using function modules like REUSE_ALV_GRID_DISPLAY and
REUSE_ALV_LIST_DISPLAY.
2.Object-Oriented ALV Report Example
In modern SAP systems, the object-oriented approach is preferred for ALV reports because it
provides more flexibility and is easier to maintain. This method uses the class CL_SALV_TABLE.
3.What are the different events in report
INITIALIZATION: This event triggers before selection screen display.
AT-SELECTION-SCREEN: This event triggers after processing user input still selection screen is
in active mode.
AT-SELECTION-SCREEN OUTPUT: It Triggers after initialization & before calling the selection screen.
TOP OF PAGE: It triggers before first record if output in output ist.
END OF PAGE: It triggers after last record of output in output list.
START OF SELECTION: Start of selection screen triggers after processing selection screen.
END-OF-SELECTION: It is for Logical Database Reporting.
4.What is interactive reports and its events?
In interactive reporting we can display the report in 'N' number of lists called Secondary list or
Interactive list.
In 1 interactive reporting we can display 20 secondary list in sequence.
events:
At line selection: It triggers when you interacts with your list. Without this event you cannot work
with
interactive report.
At User Command: It triggers when you select push button.
At PF key: It triggers when you select a pre defined function key on your key board.
Top of page during line selection: In interactive reportng we have to print heading for 20 selecondary
lists for that we have to work with top of page during line selection.
5.System fields in interactive reporting:
Sy-LSIND: It returns current intraction in interactive reporting.
SY-LISEL: It returns current list selection from a specific offset position.
4. how many secondary windows can be created in interactive reports
We can create one Basic screen and 19 secondary windows in interactive reports
Enhancements
1.Types of Enhancements
There are several types of enhancements available to extend and customize the functionality of the
system. These enhancements enable businesses to tailor SAP's standard solutions to meet
specific business needs without modifying the core codebase.
The key types of enhancements User exits, Customer Exits , BADI’s & Enhancement frame work
2. User Exits with example
User exits are predefined hooks or points in standard SAP programs where custom code can be
inserted without modifying the original SAP code.
Example- sales Order processing where you want to add custom validation logic. Suppose the
business requirement is that:
• If the total value of a sales order exceeds $100,000, the order must be flagged for manual
review.
• User Exit: USEREXIT_CHECK_VBAK in the Sales Order process
TCodes –SMOD & CMOD
2. BAdIs (Business Add-Ins) with examples
BAdIs are a more flexible and object-oriented successor to user exits. They allow you to add
custom logic at predefined points in the application.
Singleton BADI is useful when you want to ensure that a piece of logic is executed only once during
a session or process.
Filter BADI is useful when you want to implement multiple behaviors for a BADI based on certain
conditions (like customer group, order type, etc.).
• Example: If the customer has a credit limit of $10,000 and orders materials worth $12,000,
then the system should raise an error and prevent the creation of the order.
BADI Definition: BADI_SD_SALES
• Filter Criteria: customer_group, which determines which custom logic to apply.
• Tcode : SE18 , SE19
Enhancement framework
1. Enhancement Spots
Enhancement spots are places in the SAP code where you can add custom logic using specific
enhancement techniques like BAdIs or customer-specific coding.
• Example: An enhancement spot in the Material Management (MM) module could allow for
additional checks on the stock before an automatic goods receipt is posted.
2. Implicit Enhancements
• Definition: Implicit enhancements allow for custom code to be added at specific locations
in standard programs or function modules, making them suitable for inserting custom logic
without needing explicit points or hooks.
• Example: You might use an implicit enhancement in a standard report to add additional
fields or calculations that are not available out of the box.
3. Explicit Enhancements
• Definition: Explicit enhancements refer to predefined, explicit points in a standard SAP
program or function module that are marked for custom code insertion.
• Example: In the FI (Financial Accounting) module, an explicit enhancement could be added
to validate vendor data before the creation of a vendor master record.
Forms
1.What are the key components of Adobe Forms?
The key components of Adobe Forms are:
• Form Interface: Defines the input and output parameters for the form (e.g., input fields, data
structures).
• Form Layout: Designed using Adobe LiveCycle Designer. This is where you define the look
and feel of the form, including text, tables, logos, and dynamic content.
• Function Module: Used to pass data from SAP to the Adobe Form. The function module is
executed in the SAP program and triggers the form.
• Data: The data that is passed to the form (typically from an SAP program, workflow, or a
database table).
Tcode – SFP
2.How do you handle errors in Adobe Forms?
• Errors in Adobe Forms can arise during the design phase (e.g., missing fields or incorrect
data binding) or the runtime phase (e.g., data not populating correctly). Common ways to
handle errors are:
o Use debugging: You can debug the function module and the form using the
standard SAP debugging tools.
o Error messages: Display appropriate error messages in the form when certain data
fields are missing or incorrect.
o Check form parameters: Ensure that the parameters being passed to the form are
correct.
3.How do you handle printing Adobe Forms in SAP?
• Printing Adobe Forms is handled by generating a PDF from the form and then sending it to
the printer. This is typically done using the function module FP_PDF_FULL_COLLECT or
FP_JOB_OPEN and FP_JOB_CLOSE for opening and closing the print job.
4.What is the FM to get smartform function module Details
to determine the name of the function module for the
smartform is "SSF_FUNCTION_MODULE_NAME". All
parameters for this function are added to code when U click
Pattern then select CALL FUNCTION and type
"SSF_FUNCTION_MODULE_NAME"
5.how many Types of windows in smartforms?
There are 4 types of windows in smartforms
Main window ---> Data will be flow to next page automatically.
Copies window ---> If any change in one page window automatically changes will be copied to all
page’s windows.
Secondary window ---> Fixed length text.
Final window ---> This will be executed at last of all windows processing.
CDS VIEWS
Core Data Services (CDS) views are an essential part of SAP S/4HANA, providing a way to define
semantically rich and performant database views. Below are several key interview questions on
CDS views along with answers, examples, and explanations tailored for SAP S/4HANA.
1.What are Associations in CDS Views?
Associations in CDS views define relationships between different entities or tables. They are
similar to JOINs in SQL, but are handled in a more semantic and reusable way. Associations allow
for easier navigation between related entities, and they enable the system to automatically join the
tables based on these relationships.
Types of Associations:
1. One-to-One Association: One record in a table is related to one record in another table.
2. One-to-Many Association: One record in a table is related to many records in another table.
3. Many-to-One Association: Many records in one table are related to one record in another
table.
2.Types of joins in CDS view
In CDS Views, the types of joins are critical for building efficient data models and ensuring that
your business logic is correctly represented. Here's a summary of the joins you can use:
• Inner Join: Matches rows from both tables.
• Left Outer Join: Returns all rows from the left table.
• Right Outer Join: Returns all rows from the right table.
• Full Outer Join: Returns all rows from both tables.
• Cross Join: Cartesian product of the two tables.
3.Annotation to expose a CDS view as OData service
@OData.publish: true annotation is used to expose the CDS view as an OData service
General Questions
1.What is the type of Function Modules
• Normal function module: The default option, which runs immediately and synchronously
on the current SAP system.
• Remote function module (RFC): A widely used function module in SAP.
• Update function module: A function module that is scheduled to run later in a process
called an update work process
2. What is class constructor
The static constructor is always called CLASS_CONSTRUCTER, and is called automatically before
the class is first accessed.
3. What is Super keyword
Super keyword is used to access objects of super class This special form of specifying methods
statically can be used in methods of subclasses to call the implementation of a method with the
same name in the direct superclass. The superclass is addressed using the pseudo reference
super.
4. What are different visibility options in OOPS
In SAP ABAP, there are three visibility options for classes:
• Public: Components in this section are accessible to all users, as well as in the methods of all
heirs and the class itself.
• Protected: Components in this section are accessible in the methods of all heirs and in the class
itself.
• Private: Components in this section are only accessible in the class itself, and are also not visible
to the heirs.
5.What is Final class
A final class is a class that cannot be inherited by any other class. Once a class is declared as
FINAL, no other class can inherit from it. This concept is useful when you want to prevent further
subclassing of a class to ensure that its behavior remains unchanged and protected from
modification by subclasses.
Characteristics of a Final Class:
• Cannot be subclassed: You cannot create a subclass from a final class.
• Used for complete implementations: You typically use final classes when the class
provides a complete and fixed implementation, which you do not want to be extended or
changed.
6. How can we access private components in subclass?
Private components cannot inherent to any subclass so we cannot access those components.
7.How many types of TR Numbers?
There are 2 types of TR's:
Workbench TR ( For Technical People ).
Customizing TR ( For Functional People ).
8.What is the difference b/n inner join and for all entries?
Inner join compares common data and fetch it b/n 2 or more than 2 tables. Use inner join for
joining 2 tables. If we join multiple tables there will be a performance degradation.
Generally we are using for all entries to avid nested select statements.
9.Differnce between RFC & BAPI
RFC (Remote Function Call) is a communication protocol used in SAP for calling functions
between SAP systems or between SAP and external systems. It allows the execution of a function
module in a remote system as if it were a local function call. RFC can be used for synchronous and
asynchronous communication.
Example of RFC Use Case:
• Data Transfer Between SAP Systems: When you need to transfer data from one SAP
system to another, you can use RFC to call function modules to fetch and update data in the
remote system.
BAPI (Business Application Programming Interface) is a high-level API that provides a
standardized interface for accessing business processes and data in SAP. BAPIs are a type of RFC-
enabled function module that follow a structured and well-defined API for interacting with business
objects, such as orders, invoices, and customers.
Example of BAPI Use Case:
• Create a Sales Order: You can use the BAPI BAPI_SALESORDER_CREATEFROMDAT2 to
create a sales order from an external system.
• Get Customer Details: Use BAPI_CUSTOMER_GETDETAIL to retrieve details about a
customer in SAP.
Conversions
BDC is bulk data transfer technique from one system to another system.
1.Difference b/n Session method & Call transaction method?
Session method: Use session method for uploading large amount of data.
Data is processed in foreground as well as in back ground.
After uploading data we have to store error records in a file.
Multiple applications can be processed with one BDC program in session method.
Data can be processed Asynchronously and updation is done synchronously.
Call Transaction method: Use CTM for uploading small amount of data .
Data can be processed in foreground as well as background.
No logfile is created as processing is synchronous.
In CTM we have to create a log file explicitely using structure BDCMSGCOLL.
Only single application can be processed a one time.
In CTM processing is synchronous and updation is asynchronous.
Interfaces
1. How do you reprocess failed IDocs?
Failed IDocs can be reprocessed using transaction BD87. This transaction allows users to manually
select and reprocess IDocs that encountered errors during processing. The errors must be
corrected first before reprocessing.
2.How do you monitor and troubleshoot IDocs in SAP?
IDocs can be monitored using transactions(Tcodes) like:
o WE02: Display IDoc.
o WE05: List of IDocs.
o SM58: Transaction for managing queued RFCs (for asynchronous communication).
o BD87: Reprocess IDocs.
o WE19: IDoc test tool (used to manually trigger and test IDocs).
3. What are the main message types in IDocs?
Some common message types in IDocs are:
o ORDERS: For sales orders.
o INVOIC: For invoices.
o DELVRY: For deliveries.
o CREMAS: For customer master data.
o MATMAS: For material master data.
o ORDRSP: For purchase order response.
