Questions and Answers For Enhancements and Modifications

1. In the case of screen exit, how is global data accessed by the subscreen?

The developer uses preplanned function module exits.
 

2. In what case will an automatic upgrade take place using modification assistance assuming no name or layout conflict exist?

  • Menu function id modified.
  • New Function Module is added to a function group.


3. Where in function module XAAA would global data of an enhancement be decalred?

In the TOP include ZxaaaTOP and not in LxaaaTOP.
 

4. Identify the situations where Append Structure are not allowed.

  • If the table is a pooled or cluster table.
  • If the table contains a field of data type LCHR or LRAW.


5. What object is not supported by modification object?

User Exits.
 

6. What is a SD User Exit technically considered?

  • Modification


7. How does a customer benefited by using SSCR?

To log modifications made by a development user.
 

8. What is SAP Software Change Registration (SSCR) used for?

To register SAP modifications made by a developer
 

9. What is true about programming a screen exit?

The screen type must be subscreen.
 

10. Where in program-exit does the customer code get inserted?

In the include program that can be found in the function module that corresponds to the enhancement component
 

11. A screen exit is used to add pushbuttons and table controls to a screen in an R/3 application.

Customer (Z*) Ok-codes are assigned to those pushbuttons in the Screen Painter. Customer Ok-codes should always be evaluated during PAI of the main-screen. If this is not possible, e.g. the main-screen does not provide a user-exit for Ok-code processing, Customer Ok-codes will have to be evaluated during PAI of the Screen Exit. However, the OK_CODE field of the main-screen is usually not available in Screen Exits and the SY-UCOMM field cannot be used as it is not overwritten by blank Ok-codes, such as scrolling in table controls (the use of the SY-UCOMM field can result in repetitive execution of Customer Ok-codes). The actual Ok-code can be obtained by calling system-function 'DYNP_OKCODE_GET'.
 

12. What is a keyword to look for to determine if a program exit has been provide?

CALL CUSTOMER-FUNCTION
 

13. Which types of enhancements do not need to be assigned to an enhancement project?

  • Field exit
  • Keyword


14. Which types of enhancements do need to be assigned to an enhancement project?

  • Screen
  • Menu exit
  • Program exit


15. What objects are not supported by modification assistance?

User Exit
 

16. What objects are supported by modification assistance?

  • Functions
  • Text Elements
  • Menus


17. Which transactions are used for adjustment when upgrading version of SAP?

  • SPDD - to adjust dictionary objects
  • SPAU - to adjust repository objects


18.  If you want to make a change in standard SAP program to fit your business process, what is the first thing you should do?

Check configuration to see if the proposed change is feasible.
 

19. What is true about the enhancement concept?

  • They are preplanned by SAP
  • A specific enhancement can only be used in one customer project


20. What is a key word to look for to determine if a screen exit has been provided?

CALL CUSTOMER-SUBSCREEN
 

21. What type of function will trigger the modification assistance to insert a modifiable line range?

  • Insert
  • Replace


22. What is valid when coding a field exit?

  • MESSAGE E101
  • BREAK-POINT
  • MESSAGE I101
  • SUBMIT RSCA101X


23. If you are using a screen exit provided by a SAP application, when typically dose the data get exported to the subscreen?

In a PBO module of the main screen.
 

24. If you noticed a function code in a menu that began with +, what type of exit would you be observing?

A menu exit
 

25. How are customizing Includes created?

Customizing transactions
 

26.How many modification logs are available in your system?

maximum of 1

ABAP Tips

Read Also

ABAP Books
ABAP Certification, BAPI, Java, Web Programming, Smart Forms, Sapscripts Reference Books

More ABAP Tips

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.