Part - 2 SAP ABAP Interview

Question 6:

Modification Assistant

What is the Modification Assistant?

ANSWER"
The modification assistant is a tool introduced in release 4.5 to simplify the upgrade process as it relates to modifications. The modification assistant can be triggered through the ABAP editor and it will assist in logging modifications for any changes that are made to the system. The modification assistant provides support for modification made through the ABAP Editor, Screen Painter, Menu Painter, text element maintenance, Function Builder and ABAP Dictionary.

Question 7:

Function Module Exit

What statement will be found in an SAP application program that implements a function module exit?

ANSWERS:

Function module exits will exist in some SAP application programs to allow a customer to add some functionality to the SAP program. Search die SAP application program globally looking for the following search string: "CALL CUSTOMER" to determine if an exit exists.

Question 8:

Transaction Variants

What is a transaction variant and why are they used?

ANWERS:

A transaction variant is a set of screen variants that is used to predefine screen behavior and defaults. Fields, subscreens and full screens that may not be required by a user can be suppressed from that users view through the use of variant functionality. Default values can also be set for any input fields and fields can have the "ready for input" status revoked.

The GuiXT script language allows a developer to modify a screen through transaction

A transaction variant can only be created for a dialog or reporting transaction and only normal, subscreen and dialog screens can be included in the variant.

variant maintenance providing more flexibility and power to the developer. Screen layouts can be modified by inserting buttons, value helps, moving objects, inserting screens and much more

Question 9;

Changing SAP



List some of the many different ways that the SAP standard functionality can be changed by a customer?

ANSWER:

The SAP standard can be changed through personalization, customizing, modifications, enhancements and custom ABAP programs developed by the customer development team. Examples of these different approaches for changing the standard are as follows:

Personalization techniques include creation of variants, set/get parameters and activity groups.

Customizing is the most common way for changing the SAP standard through the use SAP tools such as the R/3 reference model and the Implementation Guide. Customizing could be considered mandatory in order to implement R/3 and is usually performed by the functional team.

Enhancements are usually performed by the development team and include activities such as dictionary enhancements, function module exits, menu and screen exits and Business add-ins (BADI's)
Custom ABAP programs are developed for a wide variety of reasons and can work with standard SAP objects or custom developed objects.

Modifications to SAP objects are strongly discouraged. All other techniques should be explored before modifying an SAP object. The SAP Software Change Registration SSCR) is a procedure for registering all manual modification to SAP objects.

Question 10:

Adding Fields

What are two different ways to add fields to SAP tables?

ANSWER:

An append structure or a customizing include can be used to add fields to a table. Append structures are created by adding fields to the end of a table while Customizing includes are specified by the SAP developer in advance to allow for the customer to create new fields.