SAP ABAP Fresher World (Blog dedicated to all SAP ABAP Freshers)

Speed up your regression tests with the ABAP debugger - A.Regression testing: Regression testing mean is to compare the result a piece of software is giving before and after changes were made to the source-code. Sustainable development meets the customer requirement no unwanted changes of existing behavior.. The regression tests are part of sustainable development, because they should fail, if enhancements or refactoring's break existing behavior. B.Unit-tests: The Unit-tests can be executed as regression tests.. Before they can be executed, values must be assigned to input parameters, & to the parameters of the test doubles and to the expected results (test data). C.How to determine the test-data: IF source-code is already covered by unit-tests or mainly free of technical debts, this is quite a simple task. But things getting difficult, if nobody developed unit-tests before, test-data unknown and the source-code contains high technical debts. First approach we can set a breakp

  Moderate way of the Debugging for Technical Consultants & ABAP Learners– 'Art of Removing Errors': What is Debugging???  Identify Error. Identify the Error Location. Analyze Error. Prove the Analysis. Cover the Lateral Damage. The debugging efficiently means not only removing the errors & it will help us to understand the flow of the program and also we can understand the business process or model of that particular requirement . The purpose of this blog is to the give overview of the various debugging techniques available in SAP. The primary focus of the document is for the SAP ABAP consultants at moderate level & ABAP learners. Introduction to Debugging ABAP Debugger is used to execute and analyze the programs line by line. Using it we can check the flow logic of a program and display runtime values of the variables. Currently, SAP offers two types of Debuggers The Classic ABAP Debugger. The New ABAP Debugger. Recent release New Debugger is also called as the  ‘

  How to debug a pop-up (A useful trick to debug a pop-up) Sometime you need to debug a process but the logic that you need to debug is after a button event after 3 pop ups. So, what we do? Debug everything trying to find out when our point starts.  NO! We can create a shortcut on your desktop & drop down it into your pop-up or before the event & the debug will start after it. Creating a debug shortcut: Change title to help you to identify the client, change the tcode to /h and chose a place where to save the shortcut, And Finish. Go to desktop & find your shortcut- Now, how the magic happens: A message will be shown… Continue the process… And the debug will starts after your click event!

Get Report Details for External Calls, Database Operations, Internal Table Operations, Internal Objects without Debugging: Introduction: This Blog will be very useful for Technical as well as functional consultant for preparing or providing technical specification and functional specification. With this post you will be able to get External Calls, Database Operations, Internal Table Operations, Internal Objects performed on report without Debugging it. Solution : Get the program name from Transaction code (Tcode) and go to Tcode  - SE38 as shown in below snapshot. I am taking example of std. Tcode  FAGLL03  report name  FAGL_ACCOUNT_ITEMS_GL. Transaction Code SE38 Go to the utilities & click on the Internal Program environment Internal Program Environment We will get all options to get Internal Objects/ External Calls/Internal Table Operations & Database operations performed in that particular report as shown below: After you click on any parameter for which you want to get the

  What is LUW? How LUW works? Different types of LUW? LUW (Logical Unit of Work). It's basically a required time for a system to complete the process of Database (DB) data modifications. Either full/rollback all changes done in Database (DB) data. The main purpose of LUW is to ensure that the data consistency in the system. There are two types of LUW’s available: 1.Database LUW 2.SAP LUW 1.Database LUW: LUW’s consists of various database operations like Insert/Update/ Delete & Modify on data which make changes at database level. This used to make data consistent. Following is the list of points at which database LUW's begin and end. Database LUW Begins When each time a dialog step starts,  when the dialog step is sent to the work process. When ever the previous database, LUW ends in a database commit. When ever the previous database, LUW ends in a database rollback. Database LUW Ends Each time a database commit occurs , this will writes all the changes to the database. Each

  Find Customer/User Exits in SAP ABAP? Exit for Batch Management       This is the place/area where we can add your custom logic which will get executed along with the Standard SAP code. We are taking example of User Exit for Batch Management(BM) . Lets proceed - To create Batch execute the Transaction code tcode – MSC1n Go to system : Status. Check & click on the program and open it. Once program opens, click on Goto – Attributes Check the package & note it for the next execution. Goto tcode SMOD - to check the available enhancement. Click on Find Lets put the package as VB (which we got from the program) & execute. The list of different enhancement which are available for this Transaction code - We have double clicked on the SAPLV01Z, here we get two function modules(FM) where we need to check the documentation if available or we need to apply break-point & try to check if it is getting triggered. Double click on the Include and hit enter to get it into the include &