FEW ABAP TIPS

Retrieving the deleted program
If you have deleted a custom program (which is already transported to production) accidentally and was wondering if there is any method of retrieving the program back. After some research, I found a way of getting back the program. Following are the steps in getting back the program:
1) Create a program with the same name as earlier (which is deleted)
2) Click on "Utilities" --> "Versions" --> "Version Management"
3) Select the version of your earlier program and click on display.
4) Your earlier program is displayed here.
Find out in what all Tables a specified field is available.
You can find out through transaction code SE15.
1) Give SE15 on command prompt.
2) Select ABAP Dictionary
3) Select "fields" folder
4) Click on table fields
5) Then you can enter the desired field name (In your case EKGRP)
6) Run OR press F8.
The system will list out all the tables which contain your desired field name.
or
1) using transactin Code SE11( ABAP Dictionary)
2) enter the Data table name where-in the respective field (EKGRP) is used eg; EKKO
3) Click the where -used list button
4) Check out the box(DB tables) Only .
There you can see entire list of tables containing the desired field.
Here the difficulty is that one should know at least the name of the one of the data tables which contain the desired field.

Find the Table Name For a Field.
I know couple of ways to find the table name for a field.
like.
1. Part the cursor at the field and press F1 & F9.
2. se84 or se15
3. st05 (sql trace).
4. Setting Break point in ABAP.
*
* How to print Apostrophe using the write statement
* For e.g. You'll be there.
*
report zapostrophe message-id z1.
DATA: LINE(20).
CONCATENATE 'You''' 'll be there.' INTO LINE.
WRITE:/ LINE.
**********
Given a transaction code, how can I find the menu path?
In 4.6c, you can used tcode search_sap_menu to find the SAP MENU tcode.
Please note that there are no tcode available to find the path of the IMG transaction.
**********
How to un-encrypt SAP user password?
It is not possible to un-encrypt the SAP password, because a one-way encoding (with strong 1024 bit key) is used for this. The result is stored and each time one has entered the password the encoding result is checked.
**********
When you delete an entry from an internal table in ABAP, the system has to re-generate the index for all entries after your delete, slowing the report if you have many records to eliminate.
It is much quicker to do an insert of the correct records into a second table than to delete entries from the first. The reason for this is because the index is only generated for the newest element.
**********
If you want to protect a program against debugging, you just have to set the STATUS = S in the attributes view of the main program.
**********
BDC.
When You use a call transaction ,and populate the BDCDATA table.
Make sure you pass the "DATE FIELDS" of any transaction by formatting it as "XX/XX/YYYY" cos if you pick this data from database it will be of the format 20030505 or something like that. Make sure You pass this value as character field.
Same is true for the "Rate Fields". Make sure you pass them as "Character Fields" by formatting them.
**********
If you need to find out the Okcodes for BDC sessions, look for program RSBDCCUA and run it for any platform say 'WN' for windows or MC for Mac and it will generate list of function codes
**********
To save the contents of an internal table as a Microsoft Excel Worksheet when debugging code in SAP R/3 Enterprise:
1. Click on the "Table" button
2. Type in the name of your internal table in the "Internal table" field and hit Enter.
3. Hit CTRL + F11 or click on the "Save as Excel Worksheet" button.
4. Type in the record numbers that you want to save. (Ex. From Line: 1 To Line: 10) Hit Enter.
5. Save your file.
**********
Starts with a Z is homegrown program
You cannot be sure that anything which starts with a Z is a homegrown program.
SAP provide a number of correction programs, especially within the archiving area, which start with a Z.
For e.g. ZZSTOCKL from note 202345.
**********
Can line-size of abap report large than 255?
You can have line-size upto 1023.
Along with Report statement pass the line-size as 1023. Ex. Report xyz line-size 1023.
**********
How to find out the number of days between a given date, excluding Saturdays and Sundays and public holidays?
Try functions,
=> DATE_CONVERT_TO_FACTORYDATE
=> HR_HK_DIFF_BT_2_DATES

SAP ABAP Tips links

There are so many good ABAP tips and tricks posted all over SDN and other forums and websites that I though it might be good to begin collating them here. Please feel free to suggest or make changes to this page to keep it fresh. Thanks

External Webs dedicated to ABAP Tips and Tricks

ALV

Adobe Forms

ALE

ALE Introduction

BAdI

BAPI

Basis

BDC

Business Object

Triggering a Business Object eventusing Function Module enhancement

Class

Dates

Debug

dialog

Enhancements

FAQ

FTP

Standard SAP FTP programs

Functional

General

LSMW

LSMW Steps in Detail

NetWeaver

Netweaver Overview presenter

OLE

PDF

Report

SAP Script

Smart Form

Tips

Utility

Workflow

Custom Function Modules to extract the data from SAP SYSTEM to BW

Table of Contents
How BW Extractor works:
Function module Interface:
Code Snippet
Testing BW Extractors:
Pre-requisites:
Steps for Testing:
Common Mistakes during development and their consequences:
References.

How BW Extractor works:

The BW Extract program (Function module) is called twice. The first time the extractor program is called, the extraction parameters are retrieved and then the function module is called once again when the actual data extraction takes place.

This is handled by using a flag 'I_INITFLAG'. This Flag is a part of the FM input Interface and is set during the first call and reset for all subsequent calls.

The Data extract should be done only when it is called the second time.

Function module Interface:

- I_DSOURCE - Datasource Name

- I_INITFLAG - Initialize flag is for Initialize call up: When the FM is called for the first time, this parameter is set to 'X', afterwards it is set to ' ' (blank).

- I_MAXSIZE - Package size: This parameter contains the no of rows expected for a read call up.

- I_REQUNR - Request number

TABLES INTERFACE:

- I_T_SELECT - Input Selection Criteria

- I_T_FIELDS - Output Structure

- E_T_DATA - Output Data

Code Snippet

FUNCTION Z<CUTOMER NAMING STANDARDS>
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(I_REQUNR) TYPE  SRSC_S_IF_SIMPLE-REQUNR
*"     VALUE(I_DSOURCE) TYPE  SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE  SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE  SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE  SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*"  TABLES
*"      {}I_T_SELECT TYPE  SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*"      {}I_T_FIELDS TYPE  SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*"      {}E_T_DATA STRUCTURE  ZSBW_POHEADER_TEXT OPTIONAL
*"  EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
*"      SELECTION_INPUT_INVALID
*"----------------------------------------------------------------------
*Auxiliary Selection criteria structure
  DATA: r_rsselect TYPE srsc_s_select.

* Maximum number of lines for DB table
  STATICS: i_s_if TYPE srsc_s_if_simple,

* Counter
c_datapakid LIKE sy-tabix,

* DB Cursor
v_cursor TYPE cursor.

* Initialization mode (first call by SAPI) or data transfer mode
IF I_INITFLAG = SBIWA_C_FLAG_ON.
* Check DataSource validity
       *CASE *i_dsource.
           * WHEN **<custom data source>.*

      *      *WHEN OTHERS.
                *RAISE *error_passed_to_mess_handler.
    *   *ENDCASE.
* Obtain / Populate parameter buffer for data extraction calls and the field list table for an optimized select   statement.
ELSE. "Data extraction

    * First data package -> OPEN CURSOR
    IF C_DATAPAKID = 0.
* For the first data package, range tabs gets filled, a cursor will be opened or a initial dataset will be read from database into a global internal table this has to be done here, with the first data package, to avoid getting the same data with each call of the BW Extractor Function Module.
                       << Place your code here >>
    ENDIF. "Subsequent data package(s)

* From now on records get fetched from the database or gets read from the internal table
    FETCH NEXT CURSOR v_cursor
               APPENDING CORRESPONDING FIELDS
               OF TABLE <internal table>
               PACKAGE SIZE i_s_if-maxsize.

    IF sy-subrc <> 0.
      CLOSE CURSOR v_cursor.
      RAISE no_more_data.
    ENDIF.
* Populate the Output Data Structure into table E_T_DATA and you need to raise the EXEPTION NO_MORE_DATA and close the cursor to avoid any memory leaks
   << Place your code here to populate the internal table E_T_DATA >>
* After each data package increment the counter C_DATAPAKID.
c_datapakid = c_datapakid + 1.
    ENDIF.
ENDFUNCTION |

Testing BW Extractors:

Pre-requisites:

1. Valid Datasource should be present. If not available, create a Datasource using RS02 Transaction.

2. Need access to RSA3 Transaction to perform the extract.

Steps for Testing:

1. Run the transaction RS02, and enter the Data Source Name

2. Press Enter.

3. Enter the Input Selection Criteria.

4. Execute (F8).

Common Mistakes during development and their consequences:

The counter C_DATAPAKID is not incremented correctly.

Consequences:

The RSA3 transaction will execute correctly, but when the program is executed using BW system the records are never transferred. The Extractor enters into a never ending loop and finally gets timed out.

2. The Cursor V_CURSOR is not closed after the last data packet is transferred.

Consequences:

Leads to Memory Leaks.

3. The Exception 'NO_MORE_DATA' is not raised at the end of the last record.

Consequences:

The Extractor enters into a never ending loop and finally gets timed out.

References

[stage:www.sdn.sap.com]

[stage:www.help.sap.com]

http://help.sap.com/saphelp_nw04/helpdata/en/86/1c8c3e94243446e10000000a114084/frameset.htm

ABAP program to find BI lookups and code Patterns

Brief abstract of the Solution

The solution is intended to help SAP BI Developers / consultants etc to easily find out BI lookups, code patterns etc during development, high level design, analysis, reviews etc.

To Be noted

- Solution works for both BW3.5 and BI 7.0

- Lookups in ABAP programs, Function modules, BSP applications etc cannot be analysed

Scenario 1 : Lookups

Imagine a scenario in which a DSO C is looked up while loading data from DSO A to DSO B and the code for lookup is written in the transformation from DSO A to DSO B. In a complex project there can be multiple transformations that are looking up the same DSO (see diagram below).

Now if a requirement comes wherein we needs to change the structure of DSO C, then we need to manually adjust all these lookup codes accordingly to ensure that everything is working fine after the change. The analysis will be too difficult because there is no direct way to find out in which all places the DSO is looked up. The solution comes handy in this case. You can execute the program by giving DSO C as input and it will give as output all the Transformations/Update rules where C is looked up. (see sample screen shots below)

Sample Output of the program

In case you need to find the lookups of a master data, then the program should be executed as shown below

Senario 2: Analysis (finding patterns)

Imagine there is a logic change for the country TAIWAN wherein you need to replace an existing logic with a new logic. You know that in the existing logics, in which all transformations its present, the code will be written in IF clauses with a condition for country Taiwan, but you don't know exactly in which all transformations the code is present. The solution is useful in this scenario. You can enter patterns and execute the program to find out in which all transformations(see fig below)

Scenario 3: Reviews (finding patterns)

The pattern finder functionality is also useful during reviews. On scenario is to find out Break-points that are transported to production accidently which can adversely affect performance of code sometimes. The pattern finder can be used to find out all the codes in production where break points are left accidently (see fig below)

How to get the List of standard SAP exits in SAP BW system

There are many ways in which we can view the list of standard SAP exits in the SAP system. I will show you two ways in which we can view the list and also share the entire list with all of you.

Method 1:

1. Go to transaction code CMOD.There on the menu bar you will find Utilities. On clicking on Utilities you will find SAP Enhancements, click on it.

2. On clicking on SAP enhancements you will be taken to a new window "Repository Info system:Find Exits". Simply click on execute or press F8.

3. On clicking on execute you will get the entire List of standard SAP exits as follows:

Method 2:

1. Go to transaction code RSINFO00_BCE_AUD_MOD. A window will open as given below. Click on execute or press F8.

2. On clicking on execute a new window opens as given below.This is the repository which contains the list of projects present in the system. These are the projects which we can enhance in CMOD. Here double click on 'Checking for user exits' .

3. On double clicking 'Checking for user exits' we get a new window as given below. Now go to the column 'Enhancement' and press F4.

4. On pressing F4, a new window opens as given below. Now simply click on the tick sign to proceed.

5. On pressing the tick sign we get the list of the standard SAP exits present in the system.

The above are only two methods out of many to get the list of standard SAP exits.

The entire list of standard SAP exits is as follows:

Exit name	Short text

AFAR0001	External determination of ref. value for dep. calculation
AIBW0001	IM-BCT: Assignment of Actual Values to Budget Categories
AIBW0002	Corporate IM: Settings for Group Currency
AINT0001	Extended checks when posting an asset
ALE00001	ALE User Exit
ALTD0001	Individual additional checks when transferring old data
ANLR0001	Additional control level texts in AM reporting
ARVL0001	Determine manual revaluation
BADA0001	Customer-specific conversion method in asset reports
BADA0002	Customer-specific asset number
CCUX0500	Configuration - Techn. parameters - Strategy table access
CCUX0510	Configuration: Addnl Proc. for Changing Var. Table Entries
CLCLRS01	Additional Fields on the Result Screen
CLCLRS02	Fill the Additional Fields on the Result Screen
CLCTMS01	Default values for finding objects
CLCTMS02	Check for Same Classification
CLCTMS03	Dependencies for Finding Objects
CLFM0001	Change or set default for classification of object
CLFM0002	Call classification data before saving
CLFM0003	Call Up After Check of Assigned Characteristic Values
CLIDL001	Object Table Customizing for Initial Data Transfer
CLMMD001	Selection of Objects for Mass Processing
CLSC0001	Manipulation of search result
CNEX0001	PS: User fields
CNEX0002	PS Authorization check
COOPA_01	Customer check modules for internal orders
CSALES01	corp. sales no.1
CUST1	Enhancement to area menu S000 (Office)
CUST2	Enhancement to area menu S000 (Logistics)
CUST3	Enhancement to area menu S000 (Accounting)
CUST4	Enhancement to area menu S000 (Human Resources)
CUST5	Enhancement to area menu S000 (Info Systems)
CUST6	Enhancement to area menu S000 (Tools)
CY190001	Capacity Planning: Change order operation
DW_BEAC1	Enhancements for BEAC flight system
F40K0001	Manual account statement
F40S0001	Check deposit
FARC0001	Enhancements within archiving (FI)
FEB00001	Electronic account statement
FEB00002	Interface - external check entry
FEDI0001	Function exits for EDI in FI
FICT0001	Exits for inter-company transactions
GLX_MD01	Customer-specific user exits
HRPBAS01	User Exit for HR Master Data
HRPTIM01	Customer Enhancement for HR Time Management
KKAG0001	Period costing in make-to-order production
KKCD0001	SAP-EIS: User exits for data transfer
KKCD0002	Data entry user exit before update
KPSHZIN1	Project interest calc.: Modification of single item table
KPSHZIN2	Project interest calculation: Checking single item relevance
MCS10001	SIS: Statistics update, sales documents
MCS50001	SIS: Statistics update, deliveries
MCS60001	SIS: Statistics update, invoices
MM06E001	User exits for EDI inbound and outbound purchasing documents
MM06E002	IDOC processing for contracts in inbox
MWMK0001	Warehouse management: Customer exit for storage unit number
PCASELEK	EC-PCA: Selection criteria for data transfer
PCCD0001	ECM: customer error in change master
PCCD0002	ECM: check values for effectivity type
PCCD0003	ECM: Check when setting a system status
PCCD0004	ECH: Check before saving the change number
PCCD0005	ECM: Check following initial screen (dynpro 100)
PCCD0006	Parameter effectivity: Format effectivity output control
PCSD0001	Applications development R/3 BOMS
QPAA0001	Enhancements: Formula checking / editing
QPAA0002	Customer exit - info fields
QPAA0003	Additional (auth.) check in plan (inspection chars.)
QPAP0001	Enhancement - plan reading
QPAP0002	Enhancement for material/plan assignment, plan selection
QUARK	Quark component E28
QVDM0001	Customer functions for info fields in Table QVDM
RFBVX001	Enhancement for bank directory transfer (Austria)
RFFOX001	Frame for user exit RFFOX001 (in program RFFOD__L)
RFFOX002	Frame for user exit RFFOX002 (in program RFFOD__U)
RHALE001	HR-CA: Enhancement for ALE functionality in HR
RHGB0001	Function Group RHGB Customer-specific field (list)
RHGP0001	FuGr RHGP Customer-Specific Field (List)
RHIV0001	OrgManagement: Customer-specific number assignment
RMCSTEXT	LIS: Determine Characteristic Texts in Standard Analyses
RSAP0001	Customer function calls in the service API
RSR00001	BI: Enhancements for Global Variables in Reporting
RSR00002	BI: Virtual Characteristics and Key Figures in Reporting
RSR00003	BW: Moving characteristic values
RTR00010	Exit in report tree (display transactions)
RTR00020	Exit in node in report tree (change mode)
S38MREP1	Exit at Start report
SABP0003	Asynch. RFC: When should error entry be deleted
SALIN001	SAP ArchiveLink: Customer exit for ARCHIVELINK_FUNCTION
SAPLBANK	User exit: Bank data
SAPLCOAV	Automatic assignment of values to proc. instruction charact.
SAPLSSRV	User exit: Bank account numbers
SAPLXCKA	Exits for product costing
SAPMF02D	User exits: Customer master data
SAPMF02H	Function exit: G/L account master data
SAPMF02K	User exits: Vendor master data
SDEVWORK	Development Workbench customer exits
SDW00001	Customer menu in Workbench menu 'Overview'
SDW00002	Customer menu in Workbench menu 'Development'
SDW00003	Customer menu in Workbench menu 'Test'
SDW00004	Customer menu in Workbench menu 'Utilities'
SEDD0001	Customer exits in ABAP/4 Dictionary
SEMBPS01	Enhancement for checking characteristic value combinations
SEMBPS02	Enhancement for characteristic derivation
SEU00001	Function exit in program attributes
SEU00002	Cust. func. in ABAP/4 Editor init. screen ('Environ.' menu)
SEU00003	Exit Object Browser
SEU00004	Customer exits in the Function Library
SEUED001	ABAP Editor
SEUMP001	Menu Painter (SE41)
SEUMP002	Exit Menu Painter
SEUSCRP1	Screen Painter
SEUTR001	Exit transaction code maintenance
SEUTR002	Transaction code maintenance
SGRP0002	Customer-specific virus check during upload
SGRPDL00	Authorization and trace during download on PC
SIDOC001	Customer function for module pool EDI1
SIDOC002	CA-EDI: Exits in Function Group EDI6 (Partner Profile)
SOADRESS	SAPoffice
SPHO0001	SAPphone: Define indiv. activation for outgoing calls
SPOOACC	Accounting extension for spool requests
SPOOAUTH	Customer exit for spool authorization check
SQUE0001	SAP Query: Private data file
SSC00001	Appointments diary: Conversion and F4 help for user name
SSC00002	Appointments diary: Conversion and F4 help for customer no.
SUSR0001	User exit after logon to SAP System
SZAD0001	Address formatting: Country-specific routines
SZRS0001	Regional structure - City duplication check
SZRS0002	Regional structure - Street duplication check
SZRS0003	Address check - Interface to external providers
TEST	Test SMOD
V43A3X1	GUI exit '+3X1': Sales activities/actions (GOTO menu)
V43A5X1	GUI exit '+5X1': Sales activities/actions (INFORMATION menu)
V43A6X1	GUI exit '+6X1': Sales activities/actions (ENVIRONMENT menu)
V43AGUI1	Sales activities/actions: Exclusion of FCodes in GUI
V43ASAVE	SlsActiv/actions:Exit after no.assignment before COMMIT WORK
WETEST01	Test SMOD
WPDA0001	Function exits for POS interface (POS download)

Pages

SAP Technical

External Webs dedicated to ABAP Tips and Tricks

Table of Contents

ALV

Adobe Forms

ALE

BAdI

BAPI

Basis

BDC

Business Object

Class

Dates

Debug

dialog

Enhancements

FAQ

FTP

Functional

General

LSMW

NetWeaver

OLE

PDF

Report

SAP Script

Smart Form

Tips

Utility

Workflow

How BW Extractor works:

Function module Interface:

TABLES INTERFACE:

Code Snippet

Testing BW Extractors:

Pre-requisites:

Steps for Testing:

Common Mistakes during development and their consequences:

Consequences:

Consequences:

Consequences:

References

1 comment: