http://scn.sap.com/people/stephen.pfeiffer/blog/2010/12/14/abap-debugger-scripting-advancedhttp://www.slideshare.net/ravitejacs627/abap-debugging-from-basic-to-advance#http://scn.sap.com/community/abap/blog/2013/11/15/six-kinds-of-debugging-tips-to-find-the-source-code-where-the-message-is-raisedhttp://www.saptechies.org/working-debugging-techniques/http://scn.sap.com/community/abap/testing-and-troubleshooting/blog/2010/11/10/new-abap-debugger-tips-and-trickshttp://www.saptechnical.com/Tips/ABAP/Debug/RFC.htmhttp://sapignite.com/archives/1275 (debug RFC,backgrd job,update FM)http://troublefreeabap.blogspot.in/2013/06/abap-debugger-tips.htmlhttp://www.saptraininghq.com/use-sap-abap-debugger-efficiently/======================================================================== 1. Starting abap debugging 1. Putting /H in command box and hitting execute button 2. Setting breakpoint in program. Difference among F5 , F6 ,F7 and F8 F5: debug in single step (line by line) F6: Skips Subroutines/FM Whenever a control encounters a subroutine or FM debug them unlike F5 F7: controls return to main program from Subroutines & FM F8: executes program until next break point. Breakpoint Types 1. Debugger breakpoint: When you set a breakpoint in the Debugger, it is created as a debugger breakpoint by default. A debugger breakpoint is only valid while the Debugger instance, in which it was set, is active. When the Debugger is closed, all debugger breakpoints set in it are deleted. 2. Session breakpoint: If you set a breakpoint in the ABAP Editor, for example, this breakpoint is a session breakpoint. Session breakpoints remain active independently of the existence of a Debugger and are valid for all external sessions of a logon. Within the Debugger, you can convert a debugger breakpoint into a session breakpoint and vice versa. If the setting Session Breakpoints Active Immediately is checked (via Utilities ? Settings ? ABAP Editor ? Debugging in the ABAP Editor or Object Navigator), you can set a session breakpoint in an external session of a logon to force a running program into the Debugger that runs in the same logon (for example, in an external session) and will process the point at which the session breakpoint was set. 3. User breakpoints: User breakpoints (previously known as external breakpoints) are valid for all user logons on the current server of the current system. User breakpoints are specifically required when debugging BSP or Web Dynpro applications. In these cases, you do not log on using the SAP GUI but via a browser, for example. Therefore, any breakpoints must be set before logging on. User breakpoints are only valid for a period of 2 hours. As of Release 7.00, user breakpoints set for BSP or Web Dynpro applications are also valid for SAP GUI logons. 2. Within the Debugger, you can convert debugger or session breakpoints into user breakpoints and vice versa. We can create maximum 30 breakpoints only. System Debugging If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved. Update Debugging Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option you can display and debug them after the COMMIT WORK. 3. Remote abap debugging 1. Open the Function module/ Proxy class and set an external break-point. Execute the transaction code SRDEBUG (Note: this tcode is available only in ECC 6.0 system onwards) Click on the button Activate Debugging. A pop-up screen will be opened. Fill the User-ID with which break-point has been set. (The same user-id should be used as authentication data in the XI while creating RFC communication channel). Select the radio buttons all Appl. Servers and External breakpoints already set. Click on OK. 4. Another pop-up will be opened with a message End debugging? Leave the pop-up as it is. (Dont close the transaction). When you run transaction in source system debugger will start in target system where SRDEBUG transaction is set 5. 2. For example we are calling an RFC enabled FM in ECC system from CRM system. Scenario 1: Calling a custom RFC FM 1: Add an infinite loop in the remote custom Function Module (adding a DO. ENDDO. statement at the start of the FM would be enough). 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop. 3: login to the ECC system and go to transaction SM50. Select the process which is executing the RFC and navigate to the menu: Program/Session->Program->Debugging this triggers the debugger Session in a separate window. Scenario 2: Calling a Standard RFC FM When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM50 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger. Debugging a Popup Window Sometimes we might want to start debugging from a popup window / information message, in this case we cannot type "/h" as the OK Code box is not available. Method 1: From any SAP windows press the Customize Local Layout button (Alt + F12) and select Create Shortcut Select system command in Type and and put /h in Command Provide desktop in location and click on finish. A file is generated on your desktop. Now drag the file onto the popup window / information message or click on file and debugging is enabled! 6. Method 2: For this create a text file with .SAP extension on your desktop, and type the below lines into the file: 7. [System] Name= ECD Description= ECD [host.com] Client=100 [User] Name= Username Language=EN [Function] Title= Command=/H Type=SystemCommand [Configuration] WorkDir=C:Documents and SettingsJohnSapWorkDir [Options] Reuse=1 Debugging background job 1. To debug active background process Go to the transaction SM37 and select the background job (with job status Active) that you want to debug. Now select Capture: active job from menu Job, 2. Also you can do the same from transaction SM50. Select the work process where this job is running and then choose the menu path Program/Mode?Program?Debugging. 3. To debug completed background process select job in SM37 and write 'JDBG' in command prompt and press enter. You will be in debug mode. Press F7 couple of time until you get into the code. 8. Watchpoints Watchpoints allow you the option of monitoring the content of individual variables. The Debugger stops as soon as the value of the monitored variable changes. In addition, conditions can be specified. The Debugger also checks whether such a condition is fulfilled. Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger. Use You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program. We can create maximum 24 watchpoints in a session Creating a Watchpoint In the toolbar of the New Debugger, you will find the pushbutton Create Watchpoint you to the dialog box Create Watchpoint. Using this function, you can enter the variable to be monitored. All possible ABAP data structures are allowed here. . It brings 9. Watchpoint is reached After you have created the watchpoint, the value of the variable will be monitored. As soon as a change is found in the content of the variable after a Debug step and any conditions set have been met, the Debugger will stop and you see the message "Watchpoint is reached (). In the Breakpoints tool (desktop Breakpoints/Watchpoints / Tab Watchpoints), you can view this reached watchpoint in detail. The reached watchpoint is marked with a yellow arrow. The old and the new values of the watchpoint variable are at your disposal. In addition, you can use the pushbutton Compare Variables ( ) to determine the differences between the old and the new variable. In addition, you can maintain the watchpoint in this view that is change, activate, deactivate, or delete it. Validity Area for Watchpoints In contrast to breakpoints, watchpoints are only valid locally in the roll area. If a roll area changes, none of the watchpoints defined in the underlying roll area are visible. Also, watchpoints that were created in the New ABAP Debugger cannot be used further in the Classic Debugger (for example, after changing the Debugger) and vice versa. 10. To debug script: Execute the report RSTXDBUG to activate the script debugger. OR Goto SE71 and give your form name and go to Utilities-->Active De-bugger. To debug Smart form: 1. One way to debug smart form is to debug the Function Module of that smart form. Within PERFORM %GLOBAL_INIT node level coding can be found. 2. If you want to debug particular smart form node that the solution would be, insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint. 3. SFTRACE can be used for debugging SMARTFORMS. Go to tcode SFTRACE / SMARTFORM_TRACE --> click "trace on" and click checkboxes Warning/Error under abap breakpoints tab. So whenever you call the smart forms, it will stop at this breakpoint and you can debug onwards ======================================================================Ways of starting the DebuggerChoosing different viewsChoosing different execution options in the DebuggerDisplaying source code in the Debugger Setting and deleting breakpoints Setting and deleting watchpoints Stopping a program at a particular statement or event Displaying and changing field contents at runtimeDisplaying ABAP Objects and referencesDisplaying and positioning stringsSetting and deleting database locksOpening the ABAP Editor, or Object NavigatorSystem settings and runtime warnings Starting the Debugger There are two possible strategies for starting the Debugger in the ABAP Workbench: By setting breakpoints then running the programBy running the program in debugging mode.Setting Breakpoints A breakpoint is a signal in a specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints. Direct Processing You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows: From the Object NavigatorSelect a report or transaction and choose Program Test Debugging. From the ABAP EditorChoose Program Execute Debugging (or the Debugging pushbutton). From any screenChoose System Utilities Debug ABAP. From any screenEnter /h in the command field. Display Modes in the Debugger When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes. Display Modes Available Using PushbuttonsFieldsThe scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields TableDisplays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables BreakpointsA scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also Managing Dynamic Breakpoints WatchpointsYou can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also Setting Watchpoints CallsThis mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display. OverviewThis mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed. SettingsThis mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings Other Display Modes You can access other display modes by choosing Goto Display data object. Single fieldDisplays the contents and technical attributes of a field. Structured fieldDisplays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it. StringsDisplay the content and current length of the string. You can also display part of the content by means of offset and length. Internal tableDisplays the type, line numbers and contents of an internal table. ObjectDisplays the structure of an ABAP Object. For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects Checking System Programs for ErrorsTo check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System Utilities Debug System from any screen. To stop the system Debugger, choose Debugger Debugging off. Displaying Program Attributes You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Goto Further Information Program Attributes. Restarting the Debugger If you choose Debugging Restart, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Debugging Restart will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose Debugging. Breakpoints Apart from direct execution of an ABAP program in the Debugger, it is also possible to start the Debugger call by the exact setting of a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached. There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints. Breakpoint Variants The Debugger contains different breakpoint variants: StaticThe BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific. Directly-set dynamic breakpointsCan be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System. Breakpoints at statementThe Debugger stops the program directly before the specified statement is executed. Breakpoints at subroutineThe Debugger stops the program directly before the specified subroutine is called. Breakpoint at function moduleThe Debugger stops the program directly before the specified function module is called. Breakpoint at methodThe Debugger stops the program directly before the specified method is called. Breakpoints at system exceptionsThe Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted. Static Breakpoints Static breakpoints are not normally user-specific. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application, when the program execution is always to be interrupted at the same place. For further information, refer to Static Breakpoints. In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21. Dynamic Breakpoints Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System. Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages: You do not have to change the program codeYou can set them even when the program is locked by another programmerYou can define a counter that only activates the breakpoint after it has been reachedSpecial dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For further information, refer to Dynamic Breakpoints. In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution. Lifetime and Transfer of Breakpoints A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they are effective during the entire user session, if they are saved by choosing Breakpoints Save in the ABAP Debugger. For more details on the subject of sessions and user sessions, refer to Modularization Techniques in the ABAP keyword documentation. If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities Settings HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor. If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here. Breakpoints at StatementsYou can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed. PrerequisitesYou must already be running the program in the Debugger. ProcedureTo set a breakpoint at an ABAP statement: 1.Choose Breakpoint Breakpoint at Statement...The following dialog box appears: 2.Enter the ABAP statement.The system sets a breakpoint at all points in the program at which the ABAP statement occurs. 3.Choose ENTER.The breakpoint applies to all lines containing the specified statement. ResultThe system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it. Breakpoints at Subroutines You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called. Prerequisites You must already be running the program in the Debugger. Procedure To set a breakpoint for a subroutine: Choose Breakpoint Breakpoint at Event/Subroutine.The following dialog box then appears:Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.Choose ENTER.Result The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed. Breakpoints at Function Module You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called. Prerequisites You must already be running the program in the Debugger. Procedure To set a breakpoint for a function module: Choose Breakpoint Breakpoint at Function module...The following dialog box appears:Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.Choose ENTER. Result If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list. Breakpoints at MethodsYou can use this special kind of dynamic breakpoint to interrupt a program directly before a method is called. PrerequisitesYou must be already running the program in the debugger. ProcedureTo set a breakpoint for methods: ... 1. Choose Breakpoint Breakpoint at Method...The following dialog box then appears: 2. Enter the name of the method and class before which you want to interrupt the program. A breakpoint is then set each time the specified processing block appears in the source code. 3. Choose ENTER. ResultThe system confirms the breakpoint. The breakpoint is added to the list in the display. Breakpoints at System Exceptions You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred. Prerequisites You must already be running the program in the Debugger. Procedure To set a breakpoint at a system exception: Choose Breakpoint Breakpoint at System exception. Result The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed. When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears. Static Breakpoints You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it. Setting Breakpoints To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program. program RSDEBUG_01. .... if SY-SUBRC 0. break-point. endif. .... When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ). Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it. However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name. Deleting Breakpoints Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities Global search. You can also use the Extended Program Check to find them. If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system. Dynamic Breakpoints You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger. Setting Dynamic Breakpoints in the ABAP Editor You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor: Position the cursor on the line of the source code at which you want to set the breakpoint.Choose Utilities Breakpoints Set or the Stop icon. The system confirms that the breakpoint has been set.To display a list of all dynamic breakpoints in a program, choose Utilities Breakpoints Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program. Setting Dynamic Breakpoints in Debugging Mode To set a dynamic breakpoint in the Debugger: Position the cursor on the line in which you want to set the breakpoint.Select the line by double-clicking it or choosing Breakpoint Set/delete.The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it. Saving Breakpoints If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.To save the breakpoints that you have set in the Debugger: Choose Breakpoint Save.The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system. You can also delete breakpoints that you have saved:By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.By choosing Breakpoint Delete all. In this case, the system deletes all dynamic breakpoints. Managing Dynamic Breakpoints The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto Control debugging Breakpoints. ExampleFunctionsThis display mode contains the following functions for breakpoints: Breakpoint Display The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set. Counter In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display. Deleting Breakpoints Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint Set/delete. To delete all breakpoints, choose Breakpoint Delete all. Activating and Deactivating Breakpoints Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint Activate/deactivate. Watchpoints Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger. Use You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program. Features You can set up to five watchpoints in a program.See also Setting Watchpoints.You can also specify the conditions on which a watchpoint is to become active.You can specify logical conditions between up to five conditional watchpoints.See Specifying a Logical Expression.You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.You can change and delete watchpoints.See Changing Watchpoints.You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.See Memory Monitoring with Watchpoints Setting Watchpoints If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings. A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls. Procedure To set a watchpoint, start the Debugger and proceed as follows: Choose Breakpoint Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears: Decide whether you want to set a local or global watchpoint.Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.OperatorMeaning