Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
MC
Uploaded byMichelle Crapo
PPT, PDF1,105 views

General Discussion Abap Tips

This document provides tips and tricks for working with ABAP. It discusses using ZMD_CONSTANT to define reusable constants, using change documents to track changes to code, implementing search helps for custom tables, using ALV grids for reports, and various debugging and programming techniques. Examples are provided and suggestions from others in the field are solicited.

Technology◦
Downloaded 258 times
General ABAP Discussion Tips and Tricks Michelle Crapo [email_address]
Who is this person? Michelle Crapo Perrigo – produce over the counter pharmaceuticals. (Rx) 1998 Started in SAP Titles varied by the year: Programmer/ Analyst, Sr. Project Manager, Business Analyst I enjoy riding horses. I have 2 horses, 2 miniatures and one pony.
Expectations
Tips – ZMD_CONSTANT ZMD_CONSTANT contains: MANDT Program or name Subroutine – usually empty Statement - plant Generic count as part of the key Sign – I or E Option – EQ, BT FIELD LOW - Value Field High – Value or empty Used All over in custom code
Pros/Cons ZMD_CONSTANT Value – Pros One Place to find all changes. IE A new material group is added. That material group should work the same in all programs. Normally all programs would be searched for similar constants. In ZMD_CONSTANT there is only one place to change it. No programming change required. User can not “mess it up”. Drawbacks – Cons It has be transported. Custom table. Multiple entries for the same thing with the program field.
ZMD_CONSTANT at work Demo ZMCSIMPLE ZMD_CONSTANT document ZMD_CONSTANT Example
Tip - Change Documents Transaction SCDO. Generated code for audit trails. Easy to add to custom code, all the code has been written.
Pros and Cons Change Documents Pro Programming for change is done for you. SCU3 can be used to display changes. Cons Not all data elements have the change document checked. Change data uses CDHDR, and CDPOS
Demo Change documents DEMO ZSPN, ZSPINSTR Example of Change documents
Tips - Search Helps Quick and easy way to provide for searching tables – custom screens or adding to the SAP search help.
Pros and Cons Search Help Pros Ease of use No programming Cons More custom objects on system. Parameter IDs become important.
Search Help Demo Demo ZM_RID1, ZID_INIT Search Help Example
ALV Grid Used instead of list reports. It contains functionality that will help users – help themselves. Sub-total, sort, total.. It is like excel. That makes it very easy to learn, and use.
Pros and Cons ALV Grid Pros Like Excel Easy to code User friendly Cons None that I know of???
Demo Link to ALV grid document Layout User-command ZQM0050 – Object ZPP0102
Misc. Enqueue Dequeue Table Maintenance generator Custom Transaction Read/loop/if/exit/endloop vs. loop where
Suggestions by the crowd! Notes: For non-dumps - SM37 - Set the breakpoints for a scheduled job, then run JDBG to restart from first loop for a canceled job Triggering debug while on a pop-up screen.  Create a file on the desktop. "SAP Debug.txt". The contents of the file contains four lines of text: [FUNCTION] Command=/H Title=Debugger Type=SystemCommand Drag and drop this on the GUI; it's as if you had typed /H. Thank you Jeffrey Hopwood for that one.
Suggestions by the crowd – cont.   ABAP Docs is from the monthly SDN.  Here's the link:   To avoid modification of SAP code - use field symbols in your user exit.   Then you can point to any field in the SAP program.   Please note!  User exits can be called from many places, if that field is not in the other programs, it will cause them to short-dump.   MM01/MM02 - when recording a BDC - go to the first view and then move to the others.  This is a good trick for any screen similiar to MM01 or MM02 that does not have a BAPI. SE11 - generate table maintenance for a table.  Utilities -> table maintenance generator, you can change the table in SM30.  To limit so that only that table can be maintained.  Create a parameter transaction. Name of screen - Update  value X Name of screen - viewname value - your table name. transaction SM30 - skip first screen.
Suggestions by the crowd – Cont. You can use these routines to parse any input file, to see if your field definitions in the record layout match the data, or to print a subset of fields from an input file (e.g. list just the vendor number or employee number, etc).  The p_any_rec values above can literally  be changed to any structured record definition.  I mostly use this when working on new interfaces, or when diagnosing a problem with an interface file. From Gordon Tobias Program for Parsing