Abap Mentors

Get stack value SYSTEM_CALLSTACK

2021-04-02T20:54:00.002+05:30

This example, is using two programs, where the second is accessing variables of the first program. Basically just notice that we are using the program name and the variable name when assigning the field symbol.

report zrich_0006 .


tables: mara.

parameters: p_matnr type mara-matnr..

data: matnr type mara-matnr.
data: imarc type table of marc with header line.

matnr = p_matnr.
select * from marc into table imarc up to 10 rows
               where matnr = p_matnr.

perform in in program zrich_0007.

report zrich_0007 .

*---------------------------------------------------------------------*
*       FORM in                                                       *
*---------------------------------------------------------------------*
*       ........                                                      *
*---------------------------------------------------------------------*
form in.

  data: field(50).
  data: xmarc type marc.

  field-symbols: <matnr>.
  field-symbols: <imarc> type marc_upl_tt.

* Assign an individual variable
  field = '(ZRICH_0006)matnr'.
  assign (field) to <matnr>.

* Assign an internal table
  field = '(ZRICH_0006)IMARC[]'.
  assign (field) to <imarc>.

* Write out your data
  write <matnr>.

  loop at <imarc> into xmarc.
    write: / xmarc-werks.
  endloop.

endform.

Read and Write on App.Server Files Using CL_RSAN_UT_APPSERV_FILE_READER and CL_RSAN_UT_APPSERV_FILE_WRITER

2021-04-02T20:40:00.001+05:30

Read & Write Operations on App.Server Files Using CL_RSAN_UT_APPSERV_FILE_READER and CL_RSAN_UT_APPSERV_FILE_WRITER

Summary

This Post narrates the usage of class CL_RSAN_UT_APPSERV_FILE_READER and CL_RSAN_UT_APPRSERV_WRITER for read/write operations on Application Server Files.

Class Methods used in the sample Code

Class Name	Method	Description
CL_RSAN_UT_FILES	F4	F4 Help for Choosing File Name from GUI or App. Server
CL_RSAN_UT_APPSERV_FILE_WRITER	APPSERVER_FILE_WRITE	Write Data to Specified File on Application Server
CL_RSAN_UT_APPSERV_FILE_READER	APPSERVER_FILE_READ	Read Specified File from Application Server

Sample Code

One Form routine in sample code narrates how the list materials selected from MAKT table can be written to application server file. Another form-routine narrates how to read the contents of file using the methods listed in above table.

Error rendering macro 'code': Invalid value specified for parameter 'com.atlassian.confluence.ext.code.render.InvalidValueException'

*&---------------------------------------------------------------------
* *& REPORT  ZVK_CL_RSAN_UT_APPSERV
* *&
*&---------------------------------------------------------------------
* *& PURPOSE : USE OF CLASS CL_RSAN_UT_APPSERV_FILE_READER &
* *&           CL_RSAN_UT_APPSERV_FILE_WRITER FOR READ/WRITE OPERATIONS
* *&           ON APPLICATION SERVER FILES
*&---------------------------------------------------------------------
 REPORT  ZVK_CL_RSAN_UT_APPSERV.
* ** TEXT ELEMENTS
* * P_MATNR   MATERIAL FROM  TO
* * P_FILENM  - FILE NAME
 TYPE-POOLS : RSANM, ABAP.
 TABLES : MARA.
 TYPES : BEGIN OF TY_MAKT,
            MATNR TYPE MATNR,
            MAKTX TYPE MAKTX,
          END OF TY_MAKT.
 DATA : LT_MAKT TYPE STANDARD TABLE OF TY_MAKT,
         LS_MAKT TYPE TY_MAKT,
         LT_FILE_TABLE TYPE RSANM_FILE_TABLE,
         LS_FILE_TABLE TYPE RSANM_FILE_LINE.
 DATA : LV_APPLSERV         TYPE CHAR01,
         LV_TITLE            TYPE STRING,
         LV_GUI_EXTENSION    TYPE STRING,
         LV_GUI_EXT_FILTER   TYPE STRING,
         LV_CANCELED         TYPE AS4FLAG,
         LV_APPLSERV_LOGICAL TYPE AS4FLAG,
         LV_APPLSERV_AL11    TYPE AS4FLAG,
         LV_FILE_NAME        TYPE STRING,
         LV_LINES_WRITTEN    TYPE I.
 SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME.
 SELECT-OPTIONS : P_MATNR FOR MARA-MATNR OBLIGATORY.
 SELECTION-SCREEN END OF BLOCK B1.
 SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME.
 PARAMETERS : P_FILENM LIKE IBIPPARMS-PATH OBLIGATORY.
 SELECTION-SCREEN END OF BLOCK B2.
 AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILENM.
   CLEAR : LV_CANCELED , LV_FILE_NAME.
   MOVE 'X' TO LV_APPLSERV.
   MOVE 'Select File from Application Server' TO LV_TITLE.
   MOVE ' ' TO LV_APPLSERV_LOGICAL.
   MOVE 'X' TO LV_APPLSERV_AL11.
   CALL METHOD CL_RSAN_UT_FILES=>F4
     EXPORTING
       I_APPLSERV         = LV_APPLSERV
       I_TITLE            = LV_TITLE
       I_GUI_EXTENSION    = LV_GUI_EXTENSION
       I_GUI_EXT_FILTER   = LV_GUI_EXT_FILTER
       I_APPLSERV_LOGICAL = LV_APPLSERV_LOGICAL
       I_APPLSERV_AL11    = LV_APPLSERV_AL11
     IMPORTING
       E_CANCELED         = LV_CANCELED
     CHANGING
       C_FILE_NAME        = LV_FILE_NAME
     EXCEPTIONS
       FAILED             = 1
       OTHERS             = 2.
   IF SY-SUBRC <> 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ELSE.
     IF LV_CANCELED NE 'X'.
       MOVE LV_FILE_NAME TO P_FILENM.
     ENDIF.
   ENDIF.
 START-OF-SELECTION.
   MOVE P_FILENM TO LV_FILE_NAME.
   PERFORM EXTRACT_DATA.
   PERFORM CONVERT_DATA.
   PERFORM WRITE_DATA_TO_APPSERVER.
   PERFORM READ_DATA_FROM_APPSERVER.
*  &---------------------------------------------------------------------
*  *&      FORM  EXTRACT_DATA
*  &---------------------------------------------------------------------
*  *       TEXT
*  ----------------------------------------------------------------------
 FORM EXTRACT_DATA.
   REFRESH : LT_MAKT.
   SELECT MATNR MAKTX
     FROM MAKT
     INTO TABLE LT_MAKT
     WHERE MATNR IN P_MATNR
     AND   SPRAS EQ SY-LANGU.
   IF SY-SUBRC NE 0.
     MESSAGE 'No data selected' TYPE 'I' DISPLAY LIKE 'E'.
     STOP.
   ENDIF.
 ENDFORM.                    "extract_data
*&---------------------------------------------------------------------
* *&      FORM  CONVERT_DATA
* &---------------------------------------------------------------------
* *       TEXT
* ----------------------------------------------------------------------
 FORM CONVERT_DATA.
   FIELD-SYMBOLS:<FS> TYPE ANY.
   FIELD-SYMBOLS:<FS1> TYPE ANY.
   DATA:LV_LENGTH TYPE I,
         WF_REF TYPE REF TO DATA.
   REFRESH : LT_FILE_TABLE.
   CLEAR   : LS_FILE_TABLE.
   IF LT_MAKT[] IS NOT INITIAL.
     LOOP AT LT_MAKT INTO LS_MAKT.
       DO.
         ASSIGN COMPONENT SY-INDEX OF STRUCTURE LS_MAKT TO <FS>.
         IF SY-SUBRC <> 0.
           APPEND LS_FILE_TABLE TO LT_FILE_TABLE.
           CLEAR LS_FILE_TABLE.EXIT.
         ENDIF.
         LV_LENGTH = 0.
         DESCRIBE FIELD <FS> OUTPUT-LENGTH LV_LENGTH.
         CREATE DATA WF_REF TYPE C LENGTH LV_LENGTH.
         IF WF_REF IS BOUND.
           ASSIGN WF_REF->* TO <FS1>.
           CHECK <FS1> IS ASSIGNED.
           <FS1> = <FS>.
         ENDIF.
         IF SY-INDEX = 1.
           LS_FILE_TABLE = <FS1>.
         ELSE.
           CONCATENATE LS_FILE_TABLE <FS1> INTO LS_FILE_TABLE SEPARATED BY '|'.
         ENDIF.
       ENDDO.
     ENDLOOP.
   ENDIF.
 ENDFORM.                    "convert_data
*&---------------------------------------------------------------------
* *&      FORM  WRITE_DATA_TO_APPSERVER
*&---------------------------------------------------------------------
* * FORM ROUTINE FOR CREATING THE FILE IN APPLICATION SERVER
* * =========================================================
* * PARAMETER I_OVERWRITE HAS RELEVANT IF AN EXISTING FILE IS CHOSEN TO
* * WRITE THE CONTENTS
* * IF VALUE OF PARAMETER I_OVERWRITE IS 'X' THEN FILE IS OVERWRITTEN
* * OTHERWISE THE DATA IS APPENDED TO EXISTING FILE.
* * =========================================================
* ----------------------------------------------------------------------
 FORM WRITE_DATA_TO_APPSERVER.
   IF LT_FILE_TABLE[] IS NOT INITIAL.
     CLEAR : LV_LINES_WRITTEN.
     CALL METHOD CL_RSAN_UT_APPSERV_FILE_WRITER=>APPSERVER_FILE_WRITE
       EXPORTING
         I_FILENAME      = LV_FILE_NAME
         I_OVERWRITE     = ABAP_TRUE
         I_DATA_TAB      = LT_FILE_TABLE
       IMPORTING
         E_LINES_WRITTEN = LV_LINES_WRITTEN
       EXCEPTIONS
         OPEN_FAILED     = 1
         WRITE_FAILED    = 2
         CLOSE_FAILED    = 3
         OTHERS          = 4.
     IF SY-SUBRC <> 0.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
     ELSE.
       WRITE :/ 'Data written to ',
                LV_FILE_NAME.
       WRITE :/ 'No of Lines Written ',
                LV_LINES_WRITTEN.
     ENDIF.
   ENDIF.
 ENDFORM.                    "write_data_to_appserver
*&---------------------------------------------------------------------
* *&      FORM  READ_DATA_FROM_APPSERVER
* &---------------------------------------------------------------------
* * FORM ROUTINE TO READ THE CONTENTS OF THE FILE IN APPLICATION SERVER
* ----------------------------------------------------------------------
 FORM READ_DATA_FROM_APPSERVER.
   REFRESH : LT_FILE_TABLE.
   CALL METHOD CL_RSAN_UT_APPSERV_FILE_READER=>APPSERVER_FILE_READ
     EXPORTING
       I_FILENAME   = LV_FILE_NAME
     CHANGING
       C_DATA_TAB   = LT_FILE_TABLE
     EXCEPTIONS
       OPEN_FAILED  = 1
       READ_FAILED  = 2
       CLOSE_FAILED = 3
       OTHERS       = 4.
   IF SY-SUBRC <> 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ELSE.
     WRITE :/ 'Contents of file ', LV_FILE_NAME.
     WRITE :/ '================================='.
     LOOP AT LT_FILE_TABLE INTO LS_FILE_TABLE.
       WRITE :/ LS_FILE_TABLE.
     ENDLOOP.
   ENDIF.
 ENDFORM.                    "read_data_from_appserver

Function Module to Upload and Download files from and to Application Server

2021-04-02T20:38:00.003+05:30

Function Module to Upload and Download files from and to Application Server

Summary

This function module can be used to Upload and Download files from/to application server. It must have field separator to be specified while doing the Upload/Download operations. This function module can be easily enhanced or modularized for other file operations like moving files, deleting files etc

Function Module Importing parameters

Parameter	Typing	Associated type	Description	Optional
IM_PATH	TYPE	LOCALFILE	File path for Upload/Download	No
IM_OPERATION	TYPE	ABAP_CHAR1	File Operation Upload/Download	No
IM_CODEPAGE	TYPE	CPCODEPAGE	SAP Character Set ID	Yes
IM_SEPARATOR	TYPE	ABAP_CHAR1	Field Separator	No
IM_APPEND	TYPE	ABAP_CHAR1	Dataset append mode	Yes
IM_AUTHORITY_CHECK	TYPE	ABAP_CHAR1	Authority check	Yes

Tables parameters

Parameter	Typing	Associated type	Description
IT_DATA			Table with data

Exceptions

Exception	Short text
INVALID_INPUT	Invalid Inputs
FILE_OPERATION	File Operation
DYNAMIC_TABLE_GENERATION	Dynamic table Creation

Top Include

Error rendering macro 'code': Invalid value specified for parameter 'com.atlassian.confluence.ext.code.render.InvalidValueException'

TYPE-POOLS:ABAP.
CONSTANTS:C_UPLOAD TYPE ABAP_CHAR1 VALUE 'U',
          C_DOWNLOAD TYPE ABAP_CHAR1 VALUE 'D',
          C_ACTIVITY_READ TYPE CHAR04 VALUE 'READ',
          C_ACTIVITY_WRITE TYPE CHAR05 VALUE 'WRITE'.
DATA:I_TAB TYPE TABLE OF STRING,
     I_COMP TYPE CL_ABAP_STRUCTDESCR=>COMPONENT_TABLE.
DATA:WF_STRING TYPE STRING,
     WF_OBJ TYPE REF TO CX_SY_FILE_OPEN,
     WF_CX TYPE REF TO CX_ROOT,
     WF_LTYPE TYPE C,
     WI_INDEX TYPE I,
     WF_LENGTH TYPE I,
     WF_FILENAME TYPE FILEEXTERN,
     WF_MAXIMUM TYPE I,
     WI_COUNT TYPE I,
     WF_TOTAL_FIELDS TYPE I,
     WF_INFILE TYPE REF TO DATA,
     WF_TYPE_STRUCT TYPE REF TO CL_ABAP_STRUCTDESCR,
     WF_TYPE_TABLE  TYPE REF TO CL_ABAP_TABLEDESCR,
     WF_DATA_TAB    TYPE REF TO DATA,
     WF_DATA_STR    TYPE REF TO DATA.
DATA:WA_COMP LIKE LINE OF I_COMP,
     WA_FIELDS TYPE ABAP_COMPDESCR.
FIELD-SYMBOLS:
           <FS_LINE>   TYPE ANY,
           <FS_FIELD_S>  TYPE ANY,
           <FS_FIELD_T> TYPE ANY,
           <FS_TABLE>  TYPE STANDARD TABLE,
           <FS_WA>     TYPE ANY.

Source Code

Error rendering macro 'code': Invalid value specified for parameter 'com.atlassian.confluence.ext.code.render.InvalidValueException'

 FUNCTION Z_FILE_UPLOAD_DOWNLOAD.
*"----------------------------------------------------------------------
*"*"Local Interface:
*"  IMPORTING
*"     VALUE(IM_PATH) TYPE  LOCALFILE
*"     VALUE(IM_OPERATION) TYPE  ABAP_CHAR1
*"     VALUE(IM_CODEPAGE) TYPE  CPCODEPAGE
*"     VALUE(IM_SEPARATOR) TYPE  ABAP_CHAR1
*"     VALUE(IM_APPEND) TYPE  ABAP_CHAR1 OPTIONAL
*"     VALUE(IM_AUTHORITY_CHECK) TYPE  ABAP_CHAR1 OPTIONAL
*"  TABLES
*"      IT_DATA
*"  EXCEPTIONS
*"      INVALID_INPUT
*"      FILE_OPERATION
*"      DYNAMIC_TABLE_GENERATION
*"----------------------------------------------------------------------
   CLEAR :WF_STRING,I_TAB[].
   IF IM_APPEND = ABAP_TRUE AND IM_OPERATION = C_UPLOAD.
     MESSAGE E904 WITH 'Append mode with upload not allowed'(001)
                      RAISING INVALID_INPUT.
   ENDIF.
   IF IM_OPERATION = C_UPLOAD.
     CLEAR IT_DATA[].
   ENDIF.
   IF IT_DATA[] IS INITIAL AND IM_OPERATION = C_DOWNLOAD.
     MESSAGE E904 WITH 'No data Provided to Download'(001)
                        RAISING INVALID_INPUT.
   ENDIF.
   IF IM_OPERATION NE C_UPLOAD AND
        IM_OPERATION NE C_DOWNLOAD.
     MESSAGE E904 WITH 'Invalid Operation'(002)
                        RAISING INVALID_INPUT.
   ENDIF.
   IF IM_AUTHORITY_CHECK = ABAP_TRUE.
     WF_FILENAME = IM_PATH.
     IF IM_OPERATION = C_UPLOAD.
       WF_STRING = 'No Authorization to Read'(006).
       PERFORM CHECK_AUTHORITY USING C_ACTIVITY_READ
                                     WF_FILENAME.
     ELSEIF IM_OPERATION = C_DOWNLOAD.
       WF_STRING = 'No Authorization to Write'(007).
       PERFORM CHECK_AUTHORITY USING C_ACTIVITY_WRITE
                                     WF_FILENAME.
     ENDIF.
     IF SY-SUBRC <> 0.
       MESSAGE E904 WITH WF_STRING RAISING FILE_OPERATION.
     ELSE.
       CLEAR WF_STRING.
     ENDIF.
   ENDIF.
   TRY.
       IF IM_OPERATION = C_UPLOAD.
         IF IM_CODEPAGE = '4110'.
           OPEN DATASET IM_PATH  FOR INPUT IN TEXT MODE
                                           ENCODING DEFAULT
                                           IGNORING CONVERSION ERRORS.
         ELSE.
           OPEN DATASET IM_PATH FOR INPUT IN LEGACY TEXT MODE
                                        CODE PAGE  IM_CODEPAGE
                                        IGNORING CONVERSION ERRORS.
         ENDIF.
       ELSEIF IM_OPERATION = C_DOWNLOAD.
         IF IM_CODEPAGE = '4110'.
           IF IM_APPEND = ABAP_TRUE.
             OPEN DATASET IM_PATH  FOR APPENDING IN TEXT MODE
                                             ENCODING DEFAULT
                                             IGNORING CONVERSION ERRORS.
           ELSE.
             OPEN DATASET IM_PATH  FOR OUTPUT IN TEXT MODE
                                             ENCODING DEFAULT
                                             IGNORING CONVERSION ERRORS.
           ENDIF.
         ELSE.
           IF IM_APPEND = ABAP_TRUE.
             OPEN DATASET IM_PATH FOR APPENDING IN LEGACY TEXT MODE
                                          CODE PAGE  IM_CODEPAGE
                                          IGNORING CONVERSION ERRORS.
           ELSE.
             OPEN DATASET IM_PATH FOR OUTPUT IN LEGACY TEXT MODE
                                CODE PAGE  IM_CODEPAGE
                                IGNORING CONVERSION ERRORS.
           ENDIF.
         ENDIF.
       ENDIF.
     CATCH CX_SY_FILE_OPEN INTO WF_OBJ.
       PERFORM EXP_TXT USING WF_OBJ.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
         RAISING FILE_OPERATION.
   ENDTRY.
   CREATE DATA WF_INFILE LIKE LINE OF IT_DATA.
   ASSIGN WF_INFILE->* TO <FS_LINE>.
   CLEAR:WF_LTYPE,WI_COUNT.
   DESCRIBE FIELD <FS_LINE> TYPE       WF_LTYPE
                              COMPONENTS WI_COUNT.
   WF_MAXIMUM = 0.
   WF_TOTAL_FIELDS = WI_COUNT.
   WHILE WI_COUNT GT 0.
     WI_INDEX = SY-INDEX.
     ASSIGN COMPONENT WI_INDEX OF STRUCTURE <FS_LINE> TO <FS_FIELD_S>.
     IF SY-SUBRC EQ 0.
       DESCRIBE FIELD <FS_FIELD_S> TYPE          WF_LTYPE
                                   OUTPUT-LENGTH WF_LENGTH.
       IF WF_MAXIMUM LT WF_LENGTH.
         WF_MAXIMUM = WF_LENGTH.
       ENDIF.
     ENDIF.
     WI_COUNT = WI_COUNT - 1.
   ENDWHILE.
   CLEAR:WA_COMP,I_COMP[].
   WA_COMP-NAME = 'FIELD'(005).
   WA_COMP-TYPE ?= CL_ABAP_ELEMDESCR=>GET_C( WF_MAXIMUM ).
   APPEND WA_COMP TO I_COMP.
   TRY.
       WF_TYPE_STRUCT = CL_ABAP_STRUCTDESCR=>CREATE( P_COMPONENTS = I_COMP ).
     CATCH CX_SY_STRUCT_CREATION INTO WF_CX.
       PERFORM EXP_TXT USING WF_CX.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
       RAISING DYNAMIC_TABLE_GENERATION.
   ENDTRY.
   TRY.
       WF_TYPE_TABLE = CL_ABAP_TABLEDESCR=>CREATE( WF_TYPE_STRUCT ).
     CATCH CX_SY_TABLE_CREATION INTO WF_CX.
       PERFORM EXP_TXT USING WF_CX.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
 RAISING DYNAMIC_TABLE_GENERATION.
   ENDTRY.
   CREATE DATA: WF_DATA_TAB TYPE HANDLE WF_TYPE_TABLE,
                WF_DATA_STR TYPE HANDLE WF_TYPE_STRUCT.
   ASSIGN: WF_DATA_TAB->* TO <FS_TABLE>,
             WF_DATA_STR->* TO <FS_WA>.
   CLEAR WF_STRING.
   IF IM_OPERATION = C_UPLOAD.
     DO.
       READ DATASET IM_PATH INTO WF_STRING.
       IF SY-SUBRC NE 0.
         IF SY-INDEX EQ 1.
           MESSAGE E904 WITH 'No data in the file'(003)
                        RAISING FILE_OPERATION.
         ELSE.
           CLOSE DATASET IM_PATH.
           EXIT.
         ENDIF.
       ENDIF.
       CLEAR <FS_TABLE>[].
       SPLIT WF_STRING AT IM_SEPARATOR INTO TABLE <FS_TABLE>.
       LOOP AT <FS_TABLE> ASSIGNING <FS_WA>.
         WI_INDEX = SY-TABIX.
         ASSIGN COMPONENT 'FIELD' OF STRUCTURE <FS_WA> TO <FS_FIELD_S>.
         IF SY-SUBRC = 0.
           ASSIGN COMPONENT WI_INDEX OF STRUCTURE <FS_LINE> TO <FS_FIELD_T>.
           IF SY-SUBRC = 0.
             TRY.
                 <FS_FIELD_T> = <FS_FIELD_S>.
               CATCH CX_SY_CONVERSION_NO_NUMBER.
             ENDTRY.
           ENDIF.
         ENDIF.
       ENDLOOP.
       APPEND <FS_LINE> TO IT_DATA.
       CLEAR <FS_LINE>.
     ENDDO.
   ELSE.
     LOOP AT IT_DATA ASSIGNING <FS_LINE>.
       WI_INDEX = 0.
       DO.
         WI_INDEX = SY-INDEX.
         ASSIGN COMPONENT WI_INDEX OF STRUCTURE <FS_LINE> TO <FS_FIELD_S>.
         IF SY-SUBRC = 0.
           ASSIGN COMPONENT 'FIELD' OF STRUCTURE <FS_WA> TO <FS_FIELD_T>.
           TRY.
               <FS_FIELD_T> = <FS_FIELD_S>.
             CATCH CX_SY_CONVERSION_NO_NUMBER.
           ENDTRY.
           CONDENSE <FS_FIELD_T>.
           IF WI_INDEX = 1.
             WF_STRING = <FS_FIELD_T>.
           ELSE.
             CONCATENATE WF_STRING <FS_FIELD_T> INTO WF_STRING
                                     SEPARATED BY IM_SEPARATOR.
           ENDIF.
         ENDIF.
         IF WI_INDEX =  WF_TOTAL_FIELDS.
           CONDENSE WF_STRING.
           TRANSFER WF_STRING TO IM_PATH.
           CLEAR WF_STRING.
           EXIT.
         ENDIF.
       ENDDO.
     ENDLOOP.
     CLOSE DATASET IM_PATH.
   ENDIF.
 ENDFUNCTION.

Subroutines

Error rendering macro 'code': Invalid value specified for parameter 'com.atlassian.confluence.ext.code.render.InvalidValueException'

* SUBROUTINES
*&---------------------------------------------------------------------*
*&      Form  CHECK_AUTHORITY
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*      -->P_C_ACTIVITY_READ  text
*      -->P_WF_FILENAME  text
*----------------------------------------------------------------------*
FORM CHECK_AUTHORITY  USING    PU_ACTIVITY TYPE ANY
                               PU_FILENAME TYPE FILEEXTERN.
  CALL FUNCTION 'AUTHORITY_CHECK_DATASET'
    EXPORTING
      ACTIVITY      = PU_ACTIVITY
      FILENAME      = PU_FILENAME
    EXCEPTIONS
      ERROR_MESSAGE = 1
      OTHERS        = 2.
ENDFORM.                    " CHECK_AUTHORITY
*&---------------------------------------------------------------------*
*&      Form  EXP_TXT
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*      -->P_WF_OBJ  text
*----------------------------------------------------------------------*
FORM EXP_TXT  USING    PU_OBJ TYPE ANY.
  CALL FUNCTION 'RSAN_MDL_EXCEPTION_TO_SYMSG'
    EXPORTING
      IR_EXCEPTION = PU_OBJ
      I_MSGTY      = 'E'.
ENDFORM.                    " EXP_TXT

Testing functionality

Demo Program

Error rendering macro 'code': Invalid value specified for parameter 'com.atlassian.confluence.ext.code.render.InvalidValueException'

REPORT  YUPLOAD_DOWNLOAD.
INCLUDE ZMM3X006.
DATA:I_MARD TYPE TABLE OF MARD.
DATA:WF_ALV TYPE REF TO CL_SALV_TABLE.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETER : P_CPAGE TYPE ZCACODEP-CPCODEPAGE OBLIGATORY DEFAULT '4110'.
SELECTION-SCREEN END OF BLOCK B1.
PARAMETERS DIR1 TYPE LOCALFILE .
PARAMETERS DIR2 TYPE LOCALFILE .
AT SELECTION-SCREEN ON P_CPAGE.
  PERFORM VALIDATE_CPAGE USING P_CPAGE.
START-OF-SELECTION.
  IF P_DIR IS NOT INITIAL.
    SELECT * FROM MARD INTO TABLE I_MARD UP TO 100 ROWS.
    CALL FUNCTION 'Z_FILE_UPLOAD_DOWNLOAD'
      EXPORTING
        IM_PATH                        = DIR1
        IM_OPERATION                   = 'D'    "Download
        IM_CODEPAGE                    = P_CPAGE
   IM_SEPARATOR                = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB
*       IM_APPEND                      =
*       IM_AUTHORITY_CHECK             =
      TABLES
        IT_DATA                        = I_MARD
   EXCEPTIONS
     ERROR_FOUND                    = 1
     FILE_OPERATION                 = 2
     DYNAMIC_TABLE_GENERATION       = 3
     OTHERS                         = 4.
    IF SY-SUBRC <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
  ELSE.
    CLEAR I_MARD[].
    CALL FUNCTION 'Z_FILE_UPLOAD_DOWNLOAD'
      EXPORTING
        IM_PATH                        = DIR2
        IM_OPERATION                   = 'U'     "Upload
        IM_CODEPAGE                    = P_CPAGE
   IM_SEPARATOR                = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB
*       IM_APPEND                      =
*       IM_AUTHORITY_CHECK             =
      TABLES
        IT_DATA                        = I_MARD
   EXCEPTIONS
     ERROR_FOUND                    = 1
     FILE_OPERATION                 = 2
     DYNAMIC_TABLE_GENERATION       = 3
     OTHERS                         = 4.
    IF SY-SUBRC <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    TRY.
        CL_SALV_TABLE=>FACTORY( IMPORTING R_SALV_TABLE = WF_ALV
                                CHANGING  T_TABLE      = I_MARD ).
      CATCH CX_SALV_MSG.                                "#EC NO_HANDLER
    ENDTRY.
    WF_ALV->DISPLAY( ).
  ENDIF.

How to Download Archived and Non-Archived GOS attachments into your PC (attachments from Generic Object Services (GOS) Documentum)

2017-08-07T17:01:00.001+05:30

***Attaching files to documentum using GOS services can have two ways either manual or automatic (early or late archival). Recently I came across some requirement where my customer wanted to download the attachments of an invoice for auditing purpose. This is something very rare and you would not find a straight away solution for it.
***In my requirement the invoice document could have both archived and non-archived files which was needed to be downloaded. Here is how I achieved it.
***
***Non-Archived /Manually attached Files

* Local Data Declartions
  DATA l_i_rel     TYPE obl_t_relt.
  DATA l_wa_rel    TYPE obl_s_relt.
  DATA l_wa_object TYPE sibflporb.
  DATA l_v_sys     TYPE logsys.
  DATA l_i_links   TYPE obl_t_link.
  DATA l_v_documnt TYPE so_entryid.
  DATA l_wa_document_data TYPE  sofolenti1.
  DATA l_i_header  TYPE STANDARD TABLE OF solisti1.
  DATA l_wa_text   TYPE text200.
  DATA l_v_filenam TYPE cacl_string.
  DATA l_v_filetyp TYPE sychar10.
  DATA l_v_var     TYPE cacl_string.
  DATA l_v_sortfi  TYPE sychar30.
  DATA l_wa_documntid TYPE sofmk.
  DATA l_i_content TYPE swftlisti1.
  DATA l_v_extct   TYPE so_extct.
  DATA l_v_doc_siz TYPE so_doc_len.
  DATA l_v_flename TYPE cacl_string.

  DATA: l_i_tbl1024 TYPE STANDARD TABLE OF tbl1024,
      l_i_toa02 TYPE STANDARD TABLE OF toa02,
      l_v_length TYPE syindex,
      l_v_mime TYPE sychar132,
      l_cnt TYPE belnr_d,
      l_v_archived_filename TYPE sychar132.

  FIELD-SYMBOLS: <l_fs_tab> TYPE toa02 ."toav0.
  FIELD-SYMBOLS <l_fs_links>   TYPE obl_s_link.
  FIELD-SYMBOLS <l_fs_header>  TYPE solisti1.
  FIELD-SYMBOLS <l_fs_content> TYPE solisti1.

  CONSTANTS l_c_i    TYPE ddsign     VALUE 'I'.
  CONSTANTS l_c_eq   TYPE ddoption   VALUE 'EQ'.
  CONSTANTS l_c_atta TYPE oblreltype VALUE 'ATTA'.
  CONSTANTS l_c_note TYPE oblreltype VALUE 'NOTE'.
  CONSTANTS l_c_dot  TYPE sychar01   VALUE '.'.
  CONSTANTS l_c_slas TYPE sychar01   VALUE '\'.
  CONSTANTS l_c_equ  TYPE sychar01   VALUE '='.
  CONSTANTS l_c_k    TYPE so_extct   VALUE 'K'.
  CONSTANTS l_c_und  TYPE sychar01   VALUE '_'.

  l_wa_rel-sign   = l_c_i.
  l_wa_rel-option = l_c_eq.
  l_wa_rel-low    = l_c_atta.
  APPEND l_wa_rel TO l_i_rel.
  CLEAR l_wa_rel-low.
  l_wa_rel-low    = l_c_note.
  APPEND l_wa_rel TO l_i_rel.
  CLEAR l_wa_rel.

  l_wa_object-instid = 510000062009(Your Object key e.g. Doc No+DocYear).
  l_wa_object-typeid = 'BUS2081' (For Invoice Document)
  l_wa_object-catid  = 'BO' (Keep it as it is)

* Download NON-ARCHIVED Files.
  TRY.
      CALL METHOD cl_binary_relation=>read_links
        EXPORTING
          is_object           = l_wa_object
          ip_logsys           = l_v_sys
          it_relation_options = l_i_rel
        IMPORTING
          et_links            = l_i_links.
    CATCH cx_obl_parameter_error
          cx_obl_internal_error
          cx_obl_model_error.
      RAISE no_link_found.
  ENDTRY.

  TRY.
      LOOP AT l_i_links ASSIGNING <l_fs_links>.
        MOVE <l_fs_links>-instid_b  TO l_v_documnt.
        IF l_v_documnt IS NOT INITIAL.
          CALL FUNCTION 'SO_DOCUMENT_READ_API1'
            EXPORTING
              document_id                = l_v_documnt
            IMPORTING
              document_data              = l_wa_document_data
            TABLES
              object_header              = l_i_header
            EXCEPTIONS
              document_id_not_exist      = 1
              operation_no_authorization = 2
              x_error                    = 3
              OTHERS                     = 4.
          IF sy-subrc <> 0.
            RAISE no_link_found.
          ELSE.

              CONCATENATE l_wa_document_data-obj_descr l_c_dot
                          l_wa_document_data-obj_type
              INTO l_v_filenam.

          ENDIF.

          MOVE l_wa_document_data-obj_type TO l_v_filetyp.

          READ TABLE l_i_header ASSIGNING <l_fs_header> INDEX 2.
          IF sy-subrc IS INITIAL.
            SPLIT <l_fs_header>-line AT l_c_equ INTO l_v_var l_v_filetyp.
          ENDIF.
          CONDENSE l_v_filetyp.

          l_wa_documntid = <l_fs_links>-instid_b.
          CONCATENATE l_wa_documntid-doctp
                      l_wa_documntid-docyr
                      l_wa_documntid-docno INTO l_v_sortfi.

          IMPORT objcont_tab TO l_i_content
          FROM DATABASE soc3(dt) ID l_v_sortfi.
          IF sy-subrc IS INITIAL.
            READ TABLE l_i_content ASSIGNING <l_fs_content> INDEX 1.
            IF sy-subrc IS INITIAL.
              IF <l_fs_content>-line CP 'KPro'
                l_v_extct = l_c_k.
              ELSE.
                CLEAR l_v_extct.
              ENDIF.
            ENDIF.
          ENDIF.

          MOVE l_wa_document_data-doc_size TO l_v_doc_siz.
          CALL FUNCTION 'SO_OBJECT_DOWNLOAD'
            EXPORTING
              bin_filesize     = l_v_doc_siz
              filetype         = l_v_filetyp
              path_and_file    = l_v_filenam
              extct            = l_v_extct
              no_dialog        = abap_true
            IMPORTING
              act_filename     = l_v_flename
            TABLES
              objcont          = l_i_content
            EXCEPTIONS
              file_write_error = 1
              invalid_type     = 2
              x_error          = 3
              kpro_error       = 4
              OTHERS           = 5.
          IF sy-subrc <> 0.
            RAISE no_link_found.
          ENDIF.
        ENDIF.
        CLEAR: l_i_content, l_v_extct.
      ENDLOOP.

    CATCH cx_sy_conversion_no_number
          cx_sy_conversion_overflow
          cx_sy_move_cast_error
          cx_sy_conversion_codepage
          cx_sy_import_format_error
          cx_sy_import_mismatch_error.
      RAISE no_link_found.
  ENDTRY.

* Download Archived Files
*We need the SAP to Documentum link, this is available in TOA*  tables, and it depends in which table you find the relation. For me its TOA02, it may not be same for you.
*In case you dont find use Function module ARCHIV_CONNECTINFO_GET_META and use the parameters sap_object and object_id as in below select.
*
*I am using table TOA02 to get all Archive ids.

SELECT *  FROM toa02 INTO TABLE l_i_toa02 WHERE
            sap_object = 'BUS2081' AND
            object_id = 5100000062009. (for me its Invoice document)
  IF sy-subrc NE 0.
    RETURN.
  ELSE.

    LOOP AT l_i_toa02 ASSIGNING <l_fs_tab>.
      l_cnt = l_cnt + 1.
      CLEAR: l_v_archived_filename, l_v_length, l_i_tbl1024.

      CONCATENATE ' C:\DATA\DOCUMENTUM' '\'  '_Arc_' l_cnt '.' <l_fs_tab>-reserve
      INTO l_v_archived_filename.
      CONDENSE l_v_archived_filename.
      CALL FUNCTION 'SCMS_AO_TABLE_GET'
        EXPORTING
          arc_id       = <l_fs_tab>-archiv_id
          doc_id       = <l_fs_tab>-arc_doc_id
        IMPORTING
          length       = l_v_length
        TABLES
          data         = l_i_tbl1024
        EXCEPTIONS
          error_http   = 1
          error_archiv = 2
          error_kernel = 3
          error_config = 4
          OTHERS       = 5.
      IF sy-subrc <> 0.
        CONTINUE.
      ENDIF.

      CALL FUNCTION 'SCMS_DOWNLOAD'
        EXPORTING
          filename = l_v_archived_filename "'C:\DATA\DOCUMENTUM\....
          filesize = l_v_length
          mimetype = l_v_mime
        TABLES
          data     = l_i_tbl1024
        EXCEPTIONS
          error    = 1
          OTHERS   = 2.
      IF sy-subrc <> 0.
        CONTINUE.
      ENDIF.
    ENDLOOP.
  ENDIF.

This complete code will create a folder C:\Data\Documentum in your PC and you will find all downloaded attachments there. Happy Downloading

Table

2017-07-26T19:01:00.000+05:30

Tables are defined in the ABAP Dictionary independently of the database. A table having the same structure is then created from this table definition in the underlying database.

Types of Tables in SAP Data Dictionary

Transparent tables.
Pooled tables.
Cluster tables.

A table definition in the ABAP Dictionary contains the following components:

Table fields: define the field names and data types of the fields contained in the table.

Foreign keys: define the relationships between the table and other tables.

Technical settings: control how the table should be created in the database.

Indexes: To speed up data selection, secondary indexes can be created for the table.

Send Emails with Attachments of any Format

2017-07-26T19:00:00.000+05:30

I need to send all those documents one by one via Email to a specific Mail ID with attachments. Since the folder can contain any type of document, The below program will solve this kind of requirement. Please find the below screen shots of the program for a easy go-thru of what exactly this program does.

Now a Email will be generated to the given Mail ID as shown in the below screen shots.

Similarly you will get different mails with each attachment in a seperate mail.

The explaination of the program is as follows.

Error rendering macro 'code': Invalid value specified for parameter 'lang'

REPORT YSEND_BULK_DOCUMENTS_FROM_A_FOLDER.
PARAMETERS : P_ATTACH TYPE CHAR200 OBLIGATORY,    " Select the Folder on the Desktop from F4 help
                        P_EMAIL TYPE CHAR50 OBLIGATORY,       " Email ID
                        P_SUBJ  TYPE CHAR50 OBLIGATORY.       " Subject of the Email
DATA : T_HEXTAB TYPE TABLE OF STRING,
           L_FILE TYPE STRING,
           T_MAILHEX TYPE SOLIX_TAB,
           LV_COUNT  TYPE I,
           GV_EMAIL         TYPE ADR6-SMTP_ADDR,
           T_BODY    TYPE TABLE OF SOLISTI1,
           GR_RECIPIENT     TYPE REF TO IF_RECIPIENT_BCS,
           TL_TEXTPOOL TYPE TABLE OF TEXTPOOL,
           WA_TEXTPOOL LIKE LINE OF TL_TEXTPOOL,
           IT_CONTENTS TYPE SOLI_TAB,
           LV_ATTACH_NAME TYPE SOOD-OBJDES,
           L_SUBJECT TYPE SO_OBJ_DES,
           L_DOCUMENT TYPE REF TO CL_DOCUMENT_BCS,
           W_DOCUMENT TYPE REF TO CL_BCS,
           WA_CONTENTS LIKE LINE OF IT_CONTENTS,
           LV_FILENAME TYPE STRING,
           L_RESULT TYPE OS_BOOLEAN,
          LV_STRING TYPE STRING.
DATA : FILE_TABLE LIKE TABLE OF SDOKPATH WITH HEADER LINE .
DATA : DIR_TABLE LIKE TABLE OF SDOKPATH WITH HEADER LINE .
DATA : FILE_COUNT TYPE I ,
            DIRCOUNT   TYPE I .
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_ATTACH.
  CALL METHOD CL_GUI_FRONTEND_SERVICES=>DIRECTORY_BROWSE
    CHANGING
      SELECTED_FOLDER      = LV_STRING
    EXCEPTIONS
      CNTL_ERROR           = 1
      ERROR_NO_GUI         = 2
      NOT_SUPPORTED_BY_GUI = 3
      OTHERS               = 4.
  IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ELSE.
    P_ATTACH = LV_STRING.
  ENDIF.
START-OF-SELECTION.
   * CHECK IF THE FOLDER PATH IS INITIAL, IF INITIAL LEAVE THE PROGRAM, ELSE COPY THE SUBJECT. ---> IT ALL DEPENDS ON HOW YOU VALIDATE.
  IF P_ATTACH IS INITIAL.
    LEAVE LIST-PROCESSING.
  ELSE.
    L_SUBJECT = P_SUBJ.
  ENDIF.
   * GETS ALL THE FILES NAMES IN THE SELECTED FOLDER
  CALL FUNCTION 'TMP_GUI_DIRECTORY_LIST_FILES'
    EXPORTING
      DIRECTORY  = P_ATTACH
    IMPORTING
      FILE_COUNT = FILE_COUNT
      DIR_COUNT  = DIRCOUNT
    TABLES
      FILE_TABLE = FILE_TABLE
      DIR_TABLE  = DIR_TABLE
    EXCEPTIONS
      CNTL_ERROR = 1
      OTHERS     = 2.
   * TELL HOW MANY FIELDS EXISTS
    WRITE:/ 'no of files in the floder is : '(005), FILE_COUNT.
  SKIP 1.
  WRITE:/ SY-ULINE.
  WRITE:/ SY-ULINE.
   * PROCESS THE DATA TO SEND MAIL WITH ATTACHMENT.
  LOOP AT FILE_TABLE.
    LV_COUNT = SY-TABIX.
    CONCATENATE P_ATTACH '\' FILE_TABLE INTO LV_FILENAME.
    MOVE LV_FILENAME TO L_FILE.
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        FILENAME                = L_FILE
        FILETYPE                = 'BIN'
      TABLES
        DATA_TAB                = T_MAILHEX
      EXCEPTIONS
        FILE_OPEN_ERROR         = 1
        FILE_READ_ERROR         = 2
        NO_BATCH                = 3
        GUI_REFUSE_FILETRANSFER = 4
        INVALID_TYPE            = 5
        NO_AUTHORITY            = 6
        UNKNOWN_ERROR           = 7
        BAD_DATA_FORMAT         = 8
        HEADER_NOT_ALLOWED      = 9
        SEPARATOR_NOT_ALLOWED   = 10
        HEADER_TOO_LONG         = 11
        UNKNOWN_DP_ERROR        = 12
        ACCESS_DENIED           = 13
        DP_OUT_OF_MEMORY        = 14
        DISK_FULL               = 15
        DP_TIMEOUT              = 16
        OTHERS                  = 17.
    IF SY-SUBRC <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
     * YOU NEED TO MAINTAIN TEXT SYMBOLS AND WANT TO READ THEM IN THE PROGRAM
        READ TEXTPOOL SY-REPID INTO TL_TEXTPOOL LANGUAGE SY-LANGU.
     * MY TEXT SYMBOL IS " T04: You can Add your Body here"
        READ TABLE TL_TEXTPOOL INTO WA_TEXTPOOL WITH KEY ID = 'I'
                                                         KEY = 'T04' BINARY SEARCH.
    IF SY-SUBRC = 0.
      WA_CONTENTS-LINE = WA_TEXTPOOL-ENTRY.
      APPEND WA_CONTENTS TO IT_CONTENTS.
    ENDIF.
     * CREATE THE DOCUMENT WITH CONTENTS
        CREATE OBJECT L_DOCUMENT.
    L_DOCUMENT = CL_DOCUMENT_BCS=>CREATE_DOCUMENT(
        I_TYPE       = 'HTM'
        I_SUBJECT    = L_SUBJECT
        I_LENGTH     = '1000'
        I_LANGUAGE   = SY-LANGU
        I_IMPORTANCE = '1'
        I_TEXT       = IT_CONTENTS ).
     * ATTACH THE FILE, THE ATTACHMENT TYPE SHOULD BE BIN TO ACCEPT ANY KIND OF ATTACHMENT, INCLUDING VIDEOS, AUDIO FILES ETC...
    LV_ATTACH_NAME = FILE_TABLE.
    CALL METHOD L_DOCUMENT->ADD_ATTACHMENT
      EXPORTING
        I_ATTACHMENT_TYPE    = 'BIN'
        I_ATTACHMENT_SUBJECT = LV_ATTACH_NAME
        I_ATT_CONTENT_HEX    = T_MAILHEX.
     * CREATING PERSISTENT OBJECT WILL ALLOW YOU TO SET THE DOCUMENT IN THE MAIL
        W_DOCUMENT = CL_BCS=>CREATE_PERSISTENT( ).
    CALL METHOD W_DOCUMENT->SET_DOCUMENT( L_DOCUMENT ).
     * EMAIL AS GIVEN IN THE SELECTION SCREEN.
    GV_EMAIL = P_EMAIL.
    GR_RECIPIENT = CL_CAM_ADDRESS_BCS=>CREATE_INTERNET_ADDRESS( GV_EMAIL ).
    "Add recipient to send request
    CALL METHOD W_DOCUMENT->ADD_RECIPIENT
      EXPORTING
        I_RECIPIENT = GR_RECIPIENT
        I_EXPRESS   = 'X'.
     * SEND THE MAIL
        CALL METHOD W_DOCUMENT->SEND(
          EXPORTING
            I_WITH_ERROR_SCREEN = 'X'
          RECEIVING
            RESULT              = L_RESULT ).
     * YOU CAN VERIFY THE STATUS IN THE LIST, YOU CAN ALSO SUBMIT THIS AS A BACKGROUND JOB.
    IF L_RESULT = 'X'.
      WRITE :/ , 1(9) LV_COUNT, 10(55) FILE_TABLE-PATHNAME.
      WRITE : 56(1) '-', 58(20) 'Mail sent'(003).
      COMMIT WORK.
    ELSE.
      WRITE :/ , 1(9) LV_COUNT, 10(55) FILE_TABLE-PATHNAME.
      WRITE : 56(1) '-', 58(30) 'Error in sending Mail'(004).
      ROLLBACK WORK.
    ENDIF.
    REFRESH IT_CONTENTS[].
  ENDLOOP.

You can Verify the Status of the Mail in SOST and SCOT as shown below respectively.

I Hope this WIKI would help many SAPians in sending mails with any type of attachment using ABAP.

Referance from https://wiki.scn.sap.com/wiki/display/ABAP/Send+Emails+with+Attachments+of+any+Format

ABAP DATA DICTIONARY

2017-07-26T18:58:00.000+05:30

The ABAP Dictionary centrally describes and manages all the data definitions used in the system, where we can define and maintain the objects which are related to database. Here we can create, update, delete the objects which are related to data base. SE11 is the TCODE for data dictionary. It is a utility for defining data objects.

The most important object types in the ABAP Dictionary are :-

Data Base tables
Views
Data Types (Data Elements, Structures, Table Types)
Type Group
Domains
Search helps
Lock objects

Purpose

Data definitions (metadata) are created and managed in the ABAP Dictionary.
The ABAP Dictionary permits a central description of all the data used in the system without redundancies.
New or modified information is automatically provided for all the system components.
This ensures data integrity, data consistency and data security.

ABAP Workbench

2017-07-26T18:55:00.001+05:30

SAP 's ABAP Workbench (SE80) is a set of ABAP objects and report design, implementation, testing and maintenance of tools and libraries. Table of the main tools for:

Object Navigator
ABAP Dictionary
Class Builder / Function Builder / ABAP Editor
Screen Painter / Menu Painter
Class Tester / Function Tester
Package Builder
Class Browser, Information System, Data Browser
Modification Browser, Business Add-Ins For a complete list of all workbench and documentation

SAP LOGON

2017-07-26T18:55:00.000+05:30

SAP logon is present in presentation layer, it is the procedure used to get access SAP server.

Choose the appropriate server from the logon.

Almost always a logon requires that the user have

Client :

This is a numeric field.
This number defines a whole business entity

User :

Every SAP user has a user name.
Users of SAP system are client-specific, which means that having a user identification on one client will only allow access to that particular client.

Password rules :

Letters
Numbers
Easy to remember
3-8 Characters long
No 3 Characters can be the same
Do not start with a ? or an !
Do not use previous 5 passwords

Language (optional according to configuration)

SAP supports multi-national character sets and languages on the same system, at the same time.
Default languages are English and German.

SAP Materials

2013-02-28T12:29:00.002+05:30

SAP TAW10 – SAP ABAP Workbench Fundamentals

SAP TAW12 – SAP ABAP Workbench - Concepts

SAPTEC – SAP NetWeaver Application Server Fundamentals

BC100 – Introduction to Programming (Based on ABAP Examples)

BC400 – Introduction to the ABAP Workbench – EHP2 – NW 7.02

BC401 – SAP ABAP Objects

BC402 – SAP Advanced ABAP

BC403 – SAP ABAP Debugger

BC405 – Programming ABAP Reports

BC410 – Programming User Dialogs with Classical Screens ( Dynpros )

BC414 – Programming Database Updates

BC416 – SAP ABAP Web Services

BC425 – ABAP Enhancements & Modifications

BC427 – ABAP Enhancement Framework

BC430 – ABAP Dictionary – EHP2 – NW 7.02

NET310 – Fundaments of Web Dynpro For ABAP – EHP2 – NW 7.02

NET311 – Advance ABAP Web Dynpro

NET312 – UI Development with Web Dynpro For ABAP – EHP2 – NW 7.02

NET313 – FloorPlan Manager for Web Dynpro ABAP – EHP2 – NW 7.02

BC095 – Business Integration Technologies

BC210 – Interface Programming in C/C++

BC305 – Advanced R/3 System Administration

BC314 – Technical Core Competence (NT/MS SQL Server)

BC315 – Workload Analysis

BC317 – Technical Core Competence (DB2 UDB on UNIX and NT)

BC325 – Software Logistics

BC326 – R/3 Upgrade Planning and Implementation

BC330 – E-Commerce Technical Core Competence, Internet Sales and Enterprise Buyer

BC350 – Technical Core Competence (mySAP.com Workplace)

BC355 – APO System Administration

BC360 – Technical Core Competence (UNIX / Oracle)

BC361 – Technical Core Competence (UNIX / Informix)

BC370 – Technical Core Competence (AS/400)

BC390 – Technical Core Competence (DB2 for OS/390)

BC404 – ABAP Objects: Object-Oriented Programming in R/3

BC406 – Advanced Techniques of List Processing

BC407 – Reporting: Quickviewer, Infoset Query and SAP Query (2006/Q3)

BC411 – Advanced ABAP Programming

BC412 – ABAP Dialog Programming Using Enjoy SAP Controls (2006/Q3)

BC415 – Remote Function Calls in ABAP (2006/Q2)

BC417 – BAPI Development for Accessing SAP Components

BC420 – Data Transfer (2006/Q2)

BC440 – Developing Internet Application Components

BC460 – SAP Script Form Printing and Text Management (2006/Q3)

BC470 – Form Printing with SAP Smart Forms (2006/Q2)

BC480 – PDF-Based Print Forms (2006/Q2)

BC481 – SAP Interactive Forms by Adobe in SAP Environments (2007/Q3)

BC490 – ABAP Performance Tuning (2006/Q2)

BC505 – Database Administration Oracle

BC511 – Database Administration Informix Dynamic Server UNIX / NT

BC515 – Database Administration SAP DB

BC520 – Database Administration MS SQL Server

BC525 – Database Administration DB2 for OS/400

BC530 – Database Administration DB2 for OS/390

BC535 – Database Administration DB2 UDB on UNIX / NT

BC555 – liveCache Administration

BC600 – SAP Business Workflow Introduction

BC601 – SAP Business Workflow: Build and Use

BC602 – Form Integration with SAPForms

BC610 – Workflow Development

BC615 – SAP Archive Link

BC616 – SAP Archive Link Applications

BC619 – ALE Technology

BC620 – SAP IDOC Interface (Standard)

BC621 – SAP IDOC Interface (Development)

BC635 – SAP Business Connector

BC660 – Data Archiving

BC670 – Programming Display Functions

BC680 – Dart Data Retention Tool

NET050 – Developing Web Applications

NET100 – Developing Screen Based IACs

NET170 – Internet Transaction Server

NET200 – SAP Web AS: Developing Web Applications (2006/Q2)

ABAP KEY WORDS

2012-12-10T12:48:00.001+05:30

ABAP-SOURCE	ABBREVIATED	ABSTRACT	ACCEPT	ACCEPTING
ACCORDING	ACTIVATION	ACTUAL	ADD	ADD-CORRESPONDING
ADJACENT	AFTER	ALIAS	ALIASES	ALIGN
ALL	ALLOCATE	ANALYSIS	ANALYZER	AND
ANY	APPEND	APPENDAGE	APPENDING	APPLICATION
ARCHIVE	AREA	ARITHMETIC	AS	ASCENDING
ASSERT	ASSIGN	ASSIGNED	ASSIGNING	AT
ATTRIBUTES	AUTHORITY	AUTHORITY-CHECK	AVG	BACK
BACKGROUND	BACKUP	BACKWARD	BADI	BEFORE
BEGIN	BETWEEN	BIG	BINARY	BIT
BIT-AND	BIT-NOT	BIT-OR	BIT-XOR	BLACK
BLANK	BLANKS	BLOB	BLOCK	BLOCKS
BLUE	BOUND	BOUNDARIES	BOUNDS	BOXED
BREAK-POINT	BT	BUFFER	BY	BYPASSING
BYTE	BYTE-CA	BYTE-CN	BYTE-CO	BYTE-CS
BYTE-NA	BYTE-NS	BYTE-ORDER	CA	CALL
CALLING	CASE	CASTING	CATCH	CENTER
CENTERED	CHAIN	CHAIN-INPUT	CHAIN-REQUEST	CHANGE
CHANGING	CHAR-TO-HEX	CHARACTER	CHECK	CHECKBOX
CI_	CIRCULAR	CLASS	CLASS-CODING	CLASS-DATA
CLASS-EVENTS	CLASS-METHODS	CLASS-POOL	CLEANUP	CLEAR
CLIENT	CLOB	CLOCK	CLOSE	CN
CO	CODE	CODING	COL_BACKGROUND	COL_GROUP
COL_HEADING	COL_KEY	COL_NEGATIVE	COL_NORMAL	COL_POSITIVE
COL_TOTAL	COLLECT	COLOR	COLUMN	COLUMNS
COMMENT	COMMENTS	COMMIT	COMMON	COMMUNICATION
COMPARING	COMPONENT	COMPONENTS	COMPRESSION	COMPUTE
CONCATENATE	CONDENSE	CONDITION	CONNECT	CONNECTION
CONSTANTS	CONTEXT	CONTEXTS	CONTINUE	CONTROL
CONTROLS	CONVERSION	CONVERT	COPIES	COPY
CORRESPONDING	COUNT	COUNTRY	COVER	CP
CPI	CREATE	CREATING	CRITICAL	CS
CURRENCY	CURRENT	CURSOR	CURSOR-SELECTION	CUSTOMER
CUSTOMER-FUNCTION	DANGEROUS	DATA	DATABASE	DATAINFO
DATASET	DATE	DAYLIGHT	DD/MM/YY	DD/MM/YYYY
DDMMYY	DEALLOCATE	DECIMALS	DEFAULT	DEFERRED
DEFINE	DEFINING	DEFINITION	DELETE	DELETING
DEMAND	DEPARTMENT	DESCENDING	DESCRIBE	DESTINATION
DETAIL	DIALOG	DIRECTORY	DISCONNECT	DISPLAY
DISPLAY-MODE	DISTANCE	DISTINCT	DIV	DIVIDE
DIVIDE-CORRESPONDING	DO	DUMMY	DUPLICATE	DUPLICATES
DURATION	DURING	DYNAMIC	DYNPRO	E
EDIT	EDITOR-CALL	ELSE	ELSEIF	ENABLED
ENABLING	ENCODING	END	END-ENHANCEMENT-SECTION	END-LINES
END-OF-DEFINITION	END-OF-FILE	END-OF-PAGE	END-OF-SELECTION	ENDAT
ENDCASE	ENDCATCH	ENDCHAIN	ENDCLASS	ENDDO
ENDENHANCEMENT	ENDEXEC	ENDFORM	ENDFUNCTION	ENDIAN
ENDIF	ENDING	ENDINTERFACE	ENDLOOP	ENDMETHOD
ENDMODULE	ENDON	ENDPROVIDE	ENDSELECT	ENDTRY
ENDWHILE	ENGINEERING	ENHANCEMENT	ENHANCEMENT-POINT	ENHANCEMENT-SECTION
ENHANCEMENTS	ENTRIES	ENTRY	ENVIRONMENT	EQ
EQUIV	ERRORMESSAGE	ERRORS	ESCAPE	ESCAPING
EVENT	EVENTS	EXACT	EXCEPTION	EXCEPTION-TABLE
EXCEPTIONS	EXCLUDE	EXCLUDING	EXEC	EXECUTE
EXISTS	EXIT	EXIT-COMMAND	EXPAND	EXPIRATION
EXPLICIT	EXPONENT	EXPORT	EXPORTING	EXTENDED
EXTENSION	EXTRACT	FETCH	FIELD	FIELD-GROUPS
FIELD-SYMBOLS	FIELDS	FILE	FILTER	FILTER-TABLE
FILTERS	FINAL	FIND	FIRST	FIRST-LINE
FIXED-POINT	FKEQ	FKGE	FLUSH	FONT
FOR	FORM	FORMAT	FORWARD	FOUND
FRAME	FRAMES	FREE	FRIENDS	FROM
FUNCTION	FUNCTION-POOL	FUNCTIONALITY	FURTHER	GAPS
GE	GENERATE	GET	GIVING	GKEQ
GKGE	GLOBAL	GREEN	GROUP	GROUPS
GT	HANDLE	HANDLER	HARMLESS	HASHED
HAVING	HEAD-LINES	HEADER	HEADERS	HEADING
HELP-ID	HELP-REQUEST	HIDE	HIGH	HINT
HOLD	HOTSPOT	I	ICON	ID
IDENTIFICATION	IDENTIFIER	IDS	IF	IGNORING
IMMEDIATELY	IMPLEMENTATION	IMPLEMENTATIONS	IMPLICIT	IMPORT
IMPORTING	IN	INACTIVE	INCL	INCLUDE
INCLUDES	INCLUDING	INCREMENT	INDEX	INDEX-LINE
INFOTYPES	INHERITING	INIT	INITIAL	INITIALIZATION
INNER	INOUT	*-INPUT	INPUT	INSERT
INSTANCES	INTENSIFIED	INTERFACE	INTERFACE-POOL	INTERFACES
INTERNAL	INTERVALS	INTO	INVERSE	INVERTED-DATE
IS	ISO	JOB	JOIN	KEEP
KEEPING	KERNEL	KEY	KEYS	KEYWORDS
KIND	LANGUAGE	LAST	LATE	LAYOUT
LE	LEADING	LEAVE	LEFT	LEFT-JUSTIFIED
LEFTPLUS	LEFTSPACE	LEGACY	LENGTH	LEVEL
LEVELS	LIKE	LINE	LINE-COUNT	LINE-SELECTION
LINE-SIZE	LINEFEED	LINES	LIST	LIST-PROCESSING
LISTBOX	LITTLE	LOAD	LOAD-OF-PROGRAM	LOB
LOCAL	LOCALE	LOCATOR	LOG-POINT	LOGFILE
LOGICAL	LONG	LOOP	LOW	LOWER
LPI	LT	M	MAIL	MAIN
MAJOR-ID	MARGIN	MARK	MASK	MATCH
MATCHCODE	MAX	MAXIMUM	MEDIUM	MEMORY
MESSAGE	MESSAGE-ID	MESSAGES	METHOD	METHODS
MIN	MINIMUM	MINOR-ID	MM/DD/YY	MM/DD/YYYY
MMDDYY	MOD	MODE	MODIF	MODIFIER
MODIFY	MODULE	MOVE	MOVE-CORRESPONDING	MULTIPLY
MULTIPLY-CORRESPONDING	NA	NAME	NAMETAB	NATIVE
NB	NE	NESTING	NEW	NEW-LINE
NEW-PAGE	NEW-SECTION	NEXT	NO	NO-DISPLAY
NO-EXTENSION	NO-GAP	NO-GAPS	NO-GROUPING	NO-HEADING
NO-SCROLLING	NO-SIGN	NO-TITLE	NO-TOPOFPAGE	NO-ZERO
NODE	NODES	NON-UNICODE	NON-UNIQUE	NOT
NP	NS	NULL	NUMBER	O
OBJECT	OBJECTS	OBLIGATORY	OCCURRENCE	OCCURRENCES
OCCURS	OF	OFF	OFFSET	OLE
ON	ONLY	OPEN	OPTION	OPTIONAL
OPTIONS	OR	ORDER	OTHER	OTHERS
OUT	OUTER	OUTPUT	OUTPUT-LENGTH	OVERFLOW
OVERLAY	PACK	PACKAGE	PAD	PADDING
PAGE	PAGES	PARAMETER	PARAMETER-TABLE	PARAMETERS
PART	PATTERN	PERCENTAGE	PERFORM	PERFORMING
PERSON	PF	PF-STATUS	PINK	PLACES
POOL	POS_HIGH	POS_LOW	POSITION	PRAGMAS
PRECOMPILED	PREFERRED	PRESERVING	PRIMARY	PRINT
PRINT-CONTROL	PRIORITY	PRIVATE	PROCEDURE	PROCESS
PROGRAM	PROPERTY	PROTECTED	PROVIDE	PUBLIC
PUSHBUTTON	PUT	QUEUE-ONLY	QUICKINFO	RADIOBUTTON
RAISE	RAISING	RANGE	RANGES	RAW
READ	READ-ONLY	READER	RECEIVE	RECEIVED
RECEIVER	RECEIVING	RED	REDEFINITION	REDUCED
REF	REFERENCE	REFRESH	REGEX	REJECT
REMOTE	RENAMING	REPLACE	REPLACEMENT	REPLACING
REPORT	REQUEST	REQUESTED	RESERVE	RESET
RESOLUTION	RESPECTING	RESPONSIBLE	RESULT	RESULTS
RESUMABLE	RESUME	RETRY	RETURN	RETURNCODE
RETURNING	RIGHT	RIGHT-JUSTIFIED	RIGHTPLUS	RIGHTSPACE
RISK	RMC_COMMUNICATION_FAILURE	RMC_INVALID_STATUS	RMC_SYSTEM_FAILURE	ROLLBACK
ROUND	ROWS	RUN	SAP	SAP-SPOOL
SAVING	SCALE_PRESERVING	SCALE_PRESERVING_SCIENTIFIC	SCAN	SCIENTIFIC
SCIENTIFIC_WITH_LEADING_ZERO	SCREEN	SCROLL	SCROLL-BOUNDARY	SCROLLING
SEARCH	SECONDARY	SECONDS	SECTION	SELECT
SELECT-OPTIONS	SELECTION	SELECTION-SCREEN	SELECTION-SET	SELECTION-SETS
SELECTION-TABLE	SELECTIONS	SEND	SEPARATE	SEPARATED
SET	SHARED	SHIFT	SHORT	SHORTDUMP-ID
SIGN	SIGN_AS_POSTFIX	SIMPLE	SINGLE	SIZE
SKIP	SKIPPING	SMART	SOME	SORT
SORTABLE	SORTED	SOURCE	SPACE	SPECIFIED
SPLIT	SPOOL	SPOTS	SQL	STABLE
STAMP	STANDARD	START-OF-SELECTION	STARTING	STATE
STATEMENT	STATEMENTS	STATIC	STATICS	STATUSINFO
STEP-LOOP	STOP	STRUCTURE	STRUCTURES	STYLE
SUBKEY	SUBMATCHES	SUBMIT	SUBROUTINE	SUBSCREEN
SUBSTRING	SUBTRACT	SUBTRACT-CORRESPONDING	SUFFIX	SUM
SUMMARY	SUMMING	SUPPLIED	SUPPLY	SUPPRESS
SWITCH	SWITCHSTATES	SYMBOL	SYNCPOINTS	SYNTAX-CHECK
SYNTAX-TRACE	SYSTEM-CALL	SYSTEM-EXCEPTIONS	SYSTEM-EXIT	TAB
TABBED	TABLE	TABLES	TABLEVIEW	TABSTRIP
TASK	TEST	TESTING	TEXT	TEXTPOOL
THEN	TIME	TIMES	TIMESTAMP	TIMEZONE
TITLE	TITLE-LINES	TITLEBAR	?TO	TO
TOKENIZATION	TOKENS	TOP-LINES	TOP-OF-PAGE	TRACE-FILE
TRACE-TABLE	TRAILING	TRANSACTION	TRANSFER	TRANSFORMATION
TRANSLATE	TRANSPORTING	TRMAC	TRUNCATE	TRUNCATION
TRY	TYPE	TYPE-POOL	TYPE-POOLS	TYPES
ULINE	UNASSIGN	UNDER	UNICODE	UNIQUE
UNIT	UNIX	UNPACK	UNTIL	UNWIND
UP	UPDATE	UPPER	USER	USER-COMMAND
USING	UTF-8	VALID	VALUE	VALUE-REQUEST
VALUES	VARY	VARYING	VERIFICATION-MESSAGE	VERSION
VIA	VISIBLE	WAIT	WARNING	WHEN
WHENEVER	WHERE	WHILE	WIDTH	WINDOW
WINDOWS	WITH	WITH-HEADING	WITH-TITLE	WITHOUT
WORD	WORK	WRITE	WRITER	XML
YELLOW	YES	YYMMDD	Z	ZERO
ZONE	1	2	3	4
5	6	7

Logical Operators

2012-08-29T13:47:00.001+05:30

You can combine several logical expressions together in one single expression by using the logical link operators AND and OR:

To combine several logical expressions together in one single expression which is true only if
all of the component expressions are true, link the expressions with AND.
To combine several logical expressions together in one single expression which is true if at least one of the component expressions is true, link the expressions with OR.
To negate the result of a logical expression, NOT operator can be used.

Example:

DATA: F TYPE F VALUE '100.00',

N(3) TYPE N VALUE '123',

C(3) TYPE C VALUE '456'.

WRITE 'The following logical expression is true:'.

IF ( C LT N ) AND ( N GT F ).

WRITE: / '(',C,'lt',N,') AND (',N,'gt',F,')'.

ELSE.

WRITE: / '(',C,'ge',N,') OR (',N,'le',F,')'.

ENDIF.

The output is:

The following logical expression is true:

( 456 ge 123 ) OR ( 123 le 1.000000000000000E+02 )

The logical expression in the IF statement is true, and the inverted expression is displayed.

Conditional Operators

2012-08-29T13:10:00.000+05:30

The IF Control Structure

IF statement is a conditional branching statement.The statement block starts with IF and concludes either with ENDIF, ELSEIF, or ELSE.

IF Statement

In conditional branching statement a condition is evaluated, if the expression is true then the statement or block of statements gets executed otherwise these statements are skipped.

IF <condition₁>.

ENDIF.

IF ELSE Statement

This feature permits the programmer to write a single comparison, and then execute one of the two statements depending upon whether the test expression is true or false. The general form of the if-else statement is

IF <condition₁>.

ELSE.

ENDIF.

IF ELSEIF ELSE Statement

ELSEIF statement is useful where two or more alternatives are available for selection.The various conditions are evaluated one by one starting from top to bottom, on reaching a condition evaluating to true the statement group associated with it are executed and skip other statements. If none of expression is evaluate to true, then the statement or group of statement associated with the final ELSE is executed.

IF <condition₁>.

ELSEIF <condition₂>

<statement block>.

ELSEIF <condition₃>.

.....

ELSE.

ENDIF.

To formulate conditions in IF or ELSEIF statements, you can use any logical expression

The CASE Control Structure

The CASE statement is much like a nested if .. else statement. Its mostly a matter of preference which you use, CASE statement can be slightly more efficient and easier to read.The statement block starts with CASE and concludes either with WHEN, WHEN OTHERS, END CASE.

When the CASE statement is executed, the expression in the CASE statement is evaluated and the control is transferred directly to the group of statements whose WHEN label value matches the value of the expression.If none of expression is matched, then the statement or group of statement associated with the final OTHERS is executed.

CASE <f>.

WHEN <f₁₁> [OR <f ₁₂> OR ...].

<Statement block>
WHEN <f₂₁>.[OR <f ₂₂> OR ...]

<Statement block>

WHEN <f₃₁> [OR <f ₃₂> OR ...].

<statement block>

WHEN ...

......

WHEN OTHERS.

<statement block>

ENDCASE.

Looping

2012-08-29T13:09:00.001+05:30

In a loop, a statement block is executed several times in succession. There are four kinds of loops in ABAP:

Unconditional loops using the DO statement.
Conditional loops using the WHILE statement.
Loops through internal tables and extract datasets using the LOOP statement.
Loops through datasets from database tables using the SELECT statement.

Unconditional Loops

To process a statement block several times unconditionally, use the following control structure:

DO [<n> TIMES] [VARYING <f> FROM <f₁> NEXT <f ₂>].

ENDDO.

If you do not specify any additions, the statement block is repeated until it reaches a termination statement such as EXIT or STOP (see below). The system field SY-INDEX contains the number of loop passes, including the current loop pass.Use the TIMES addition to restrict the number of loop passes to <n>.

Example:

DO 2 TIMES.
  WRITE SY-INDEX.
  SKIP.
  DO 3 TIMES.
    WRITE SY-INDEX.
  ENDDO.
  SKIP.
ENDDO.
The output is:
         1
         1          2          3
         2
         1          2          3

Conditional Loops

To repeat a statement block for as long as a certain condition is true, use the following control structure:

WHILE <condition> [VARY <f> FROM <f₁> NEXT <f ₂>].

ENDWHILE.

<condition> can be any logical expressions. The statement block between WHILE and ENDWHILE is repeated as long as the condition is true or until a termination statement such as EXIT or STOP occurs.

Example:

DATA: LENGTH     TYPE I VALUE 0,
      STRL       TYPE I VALUE 0,
      STRING(30) TYPE C VALUE 'Test String'.

STRL = STRLEN( STRING ).

WHILE STRING NE SPACE.
  WRITE STRING(1).
  LENGTH = SY-INDEX.
  SHIFT STRING.
ENDWHILE.

WRITE: / 'STRLEN: ', STRL.
WRITE: / 'Length of string:', LENGTH.

The output appears as follows:

T e s t   S t r i n g
STRLEN:                    11
Length of String:          11

Loops Statement

The LOOP and ENDLOOP statements define a loop around a statement block. The LOOP statement reads lines from internal table itab sequentially. You can either read all the lines or specify conditions cond to restrict which lines to read. The statement block between LOOP and ENDLOOP is executed once for each line.

LOOP AT itab result [cond]. 

...
ENDLOOP.

SELECT END SELECT Statement

The result of the selection is meant to be a table, the data is usually read line by line within a processing loop introduced by SELECT and concluded by ENDSELECT . For each line read, the processing passes through the loop once.SAP doesn't recommend this because of the performance issue.

If the result of the selection is meant to be a single record, the closing ENDSELECT is omitted.

Example:

SELECT SINGLE * FROM SFLIGHT

WHERE

CARRID = 'LH ' AND

CONNID = '0400' AND

FLDATE = '19950228'.

SEATSFREE = SFLIGHT-SEATSMAX - SFLIGHT-SEATSOCC

END SELECT

Terminating Loops

ABAP contains termination statements that allow you to terminate a loop prematurely. There are two categories of termination statement - those that only apply to the loop, and those that apply to the entire processing block in which the loop occurs.

The termination statements that apply only to the loop in which they occur are CONTINUE, CHECK, and EXIT.

The statment within a loop, they only apply to the execution of the loop itself. Outside of a loop, they terminate the entire processing block in which they occur (subroutine, dialog module, event block, and so on).

Example to Terminating a loop pass unconditionally:

DO 4 TIMES.
  IF SY-INDEX = 2.
    CONTINUE.
  ENDIF.
  WRITE SY-INDEX.
ENDDO.
The output is:
         1          3          4
The second loop pass is terminated without the WRITE statement being processed.
Example to Terminating a loop pass conditionally:

DO 4 TIMES.
CHECK SY-INDEX BETWEEN 2 and 3.
WRITE SY-INDEX.
ENDDO.

The output is:

         2          3
The first and fourth loop passes are terminated without the WRITE statement being processed, because SY-INDEX is not between 2 and 3.

Example to Exiting a loop:

DO 4 TIMES.
  IF SY-INDEX = 3.
    EXIT.
  ENDIF.
  WRITE SY-INDEX.
ENDDO.
The output is:
         1          2
In the third loop pass, the loop is terminated before the WRITE statement is processed.

Relational Operators

2012-08-29T11:27:00.001+05:30

Comparison between Data Types.

EQ (or) =	Equal To
NE (or) <> (or) ><	Not Equal To
LT (or) <	Less Than
LE (or) <=	Less Than or Equal to
GT (or) >	Greater Than
GE (or) >=	Greater Than or Equal To

Comparison between Strings.

CO	Contains Only
CN	Contains Not Only
CA	Contains Any
NA	Contains Not Any
CS	Contains String
NS	Contains No String
CP	Matches pattern
NP	Does not Matches pattern

The special statements for processing strings, there are special comparisons that you can apply to strings with types C, D, N, and T.

There are no conversions with these comparisons. Instead, the system compares the characters of the string.

<f1>	<operator>	<f2>	Result	SY-FDPOS
'BD '	CO	'ABCD '	true	5
'BD '	CO	'ABCDE'	false	2
'ABC12'	CN	'ABCD '	true	3
'ABABC'	CN	'ABCD '	false	5
'ABcde'	CA	'Bd '	true	1
'ABcde'	CA	'bD '	false	5
'ABAB '	NA	'AB '	false	0
'ababa'	NA	'AB '	true	5
'ABcde'	CS	'bC '	true	1
'ABcde'	CS	'ce '	false	5
'ABcde'	NS	'bC '	false	1
'ABcde'	NS	'ce '	true	5
'ABcde'	CP	*'b'*	true	1
'ABcde'	CP	*'#b'*	false	5
'ABcde'	NP	*'b'*	false	1
'ABcde'	NP	*'#b'*	true	5

Comparing Bit Sequences

O

bits are one

Z

bits are Zero

M

bits are Mixed

The above three operators to compare the bit sequence of the first operand with that of the second.
The second operand must have type X.
The comparison takes place over the length of the second operand.
The first operand is not converted to type X.

Example :
REPORT demo_log_expr_bits .
DATA: text(1) TYPE c VALUE 'C',
hex(1) TYPE x,
i TYPE i.

hex = 0.

DO 256 TIMES.
i = hex.
IF text O hex.
WRITE: / hex, i.
ENDIF.
hex = hex + 1.
ENDDO.

The output is as follows:

00 0
01 1
02 2
03 3
40 64
41 65
42 66
43 67

Arithmetic Operators

2012-08-29T11:21:00.003+05:30

ABAP supports the four basic arithmetic operations and power caluclations. You can use the following arithmetic operators in mathematical expressions:

Operator	Meaning
+	Addition
‑{}‑-	Subtraction
‑{}‑*	Multiplication
‑{}‑/	Division
DIV	Integer division
MOD	Remainder of integer division
‑{}‑**	Powers

Instead of using operators in mathematical expressions, you can perform basic arithmetic operations with the keywords ADD, SUBTRACT, MULTIPLY, and DIVIDE.

The following table shows the different ways of expressing basic arithmetic operations in ABAP:

Operation	Statement using mathematical expression	Statement using Keyword
Addition	p = n + m.	ADD n TO m.
Subtraction	P = m – n.	SUBTRACT n FROM m.
Multiplication	P = m * n.	MULTIPLY m BY n.
Division	P = m / n.	DIVIDE m BY n.
Integer division	P = m DIV n.	---
Remainder of division	P = m MOD n.	---
Powers	P = m ** n.	---

BASIC ABAP COMMANDS

2012-08-28T20:39:00.001+05:30

Screen Elements

2012-08-28T19:30:00.001+05:30

The SAP Screen consist of the following elements:

Command field: You can use the command field to go to applications directly by entering the transaction code. You can find the transaction code either in the SAP Easy Access menu or in the relevant application under System® Status.
Menu bar: The menus shown here depend on which application you are working in. These menus contain cascading menu options.
Standard toolbar: The icons in the system function bar are available on all R/3 screens. Any icons that you cannot use on a particular screen are dimmed. If you leave the cursor on an icon for a moment, a small flag will appear with the name (or function) of that icon. You will also see the corresponding function key. The application toolbar shows you which functions are available in the current application.
Title bar: The title bar displays your current position and activity in the system.
Check boxes: Checkboxes allow you to select several options simultaneously within a group.
Radio buttons: Radio buttons allow you to select one option only.
Status bar: The status bar displays information on the current system status, for example, warning and error messages.
A tab provides a clearer overview of several information screens.
Options: You can set your font size, list colors, and so on here.

Data Type

2012-08-28T19:21:00.001+05:30

Data Types are the key words which specify the type of memory and size of memory.

ABAP Data Types can be classified into 2 types.

Predefined Data Types
User defined Data Types

Integer Data Type occupies 4 bytes of memory and we can store upto 10 digits in an integer.
Float data type stores 8 bytes of memory. This stores decimal data also. It is defined with 16 decimal places by default.
Packed data type is same as Float data type except that by default, there are no decimal places and ABAPER has to specify the required no. of decimal places.
Character data type can accept all ASCII characters and it occupy 1 byte of memory.
Number accepts only numbers but treats them as characters. i.e., string operations can be executed
Date data type is of 8 bytes long and stores date in YYYYMMDD format.
Time data type is of 6 bytes long and stores time in HHMMSS format.
String data type has variable size and it adjusts based on the data in the string. It can read only .txt files
Xstring is the hexadecimal formatted and similar to String type. i.e., it can read all files like .doc, .ppt, .xcs, .jpg, .bmp etc.
We can also create our own Data Types using "Types" or by creating custom objects like Structures, Classes, Interfaces etc.

Differences between Float and Packed data types:

FLOAT has default decimal places of 16 & PACKED data type has 0.
FLOAT decimal places are fixed whereas can be decided by the ABAPer for PACKED.
PARAMETER, which creates GUI for data type is not supported by FLOAT while it is supported by PACKED type.

10 Rules for ABAP coding

2012-08-28T19:11:00.003+05:30

ABAP code can be quite free-flowing. The broad syntactiac rules governing where a statment starts and ends are:

Leading white space is ignored.you can start an ABAP statment any where you want at the beginning of the line,or even right justified if you like. Lines may be up to 72 characters long.
Statements are terminated with a periods(.)
white space outside of string literals is irrelevant;one space is a good as a hundred.That means you can split most statements over several lines for clarity, and you can place several short statments on the same line.
Literal strings are delinited by single-quotes(').
Anything on a line after a double-quote(") is ignored, and any line beginning with an asterisk(*) is ignored. use this pepper yout code with useful comments. The next line breaks ends the comment.
Many statements may follow the keyword with a colin(:) and accept comma-seperated multiple predicates; each element (keywords, parameter, grouping parentheses must be separated by one or more space or a line break. case is not distinguished by the processor, except for string comparison; you are fee to use case to enhance readability. A statment is terminated by period.
ABAP statement are not case sensitive, eg :- data, DATA, Data.
ABAP is space sensitive.
Back slash (/) is used for new line character.
The customized programs name should start with (Z) or (Y).

ABAP

2012-08-28T18:40:00.000+05:30

ABAP stands for Advanced Business Application Programming. ABAP is a programming language that was developed by SAP for developing commercial applications in SAP environment.

The development process of ABAP went through the following evolutionary stages:

In early days (1970s) ABAP stood for “Allgemeiner Berichts-Aufbereitungs Prozessor” (Generic Report Generation Processor). That time ABAP was implemented as a macro assembler under R/2 and exclusively used for creating reports to build mainframe business applications for materials management and financial and management accounting.
In mid 1980s, ABAP had become an interpreted language and was powerful enough to be used to create business application programs, in particular to program dialog-controlled transactions.
In early 1990s, the SAP R/3 system was born and ABAP become ABAP/4, that ABAP 4GL (4th Generation Programming Language). It now formed the technical and software basis of the entire SAP System. Apart from system core which is written in C, all SAP application modules, R/3 Basis System and the development environment were now created in ABAP/4.
At the end of 1990s, ABAP is extended with object oriented programming constructs and from this point on, the language was known as ABAP Objects.
In the beginning of 2000s ABAP programs were made Unicode-Compatible in order to support the internationalization of the SAP System.
With SAP technology platform under the name “SAP NetWeaver”, ABAP become the programming interface of the SAP NetWeaver Application Server ABAP (AS ABAP).
It was also intended to be used by SAP customers to enhance SAP applications, customers can develop custom reports and interfaces with ABAP programming.

Different types of sap consultants

2012-08-28T18:19:00.001+05:30

SAP is been classified into Technical and Functional Modules:

Functional Consultant :

SD (Sales and Distribution)
HRM (Human Resources Management)
FICO (Finance and Controlling)
PP (Production and Planning)
MM (Material Management)
CRM (Customer Relation Management)
SCM (Supply Chain Management)
SD with CIN

Gathers requirements from the client
Translates the requirements into functional specification.
Needs to know CRM Base Customizing and Business Terms

Technical Consultant :

ABAP (Advanced Business Application in Programming)
BASIS (System Administration)

Needs to understand the functional requirement from the functional specs.
Translates functional specs into technical specs.
Does the coding as per the technical specs.
Needs to know basic ABAP

Techno-Functional Consultant :

ABAP + HR
ABAP + SD
BIW (Business Information Warehouse)

Needs to know basic business processes

End Users :

Those who interact with sap but don't have much knowledge of sap.

Dual Consultant : (Not Imp)

SD + CRM
PP + SD
FICO + SD
HR + SD
HR + CRM

By consultant those who have more then functional module knowledge

Different Architectures

2012-08-28T14:57:00.000+05:30

Multi-tier architecture are often used when describing how clients connect to servers. But what does it all mean and do you need to make any changes to your existing infrastructure?

Let me try to explain this in non-technical terms (or as close to it I can get).

1-Tier Architecture

We all know software packages like MS Access, MS Excel, QuickBooks and Peachtree just to name a few. They all have the same in common that they access files directly. This means that the file you want to work with must be accessible from a local or shared drive. This is the simplest of all the architectures but also the least secure. Since users have direct access to the files, they could accidentally move, modify or even worse delete the file by accident or on purpose.

There is also usually an issue when multiple users access the same file at the same time: In many cases only one can edit the file while others only have read-only access.

So 1-tier architecture is simple and cheap, but usually unsecured and data can easily be lost if you are not careful.

2-Tier Architecture

This architecture is also called Client-Server architecture because of the two components: The client that runs the application and the server that handles the database back-end. When the client starts it establishes a connection to the server and communicates as needed with the server while running the client. The client computer usually can’t see the database directly and can only access the data by starting the client. This means that the data on the server is much more secure. Now users are unable to change or delete data unless they have specific user rights to do so.

The client-server solution also allows multiple users to access the database at the same time as long as they are accessing data in different parts of the database. One other huge benefit is that the server is processing data that allows the client to work on the presentation and business logic only. This mean that the client and the server is sharing the workload and by scaling the server to be more powerful than the client, you are usually able to load many clients to the server allowing more users to work on the system at the same time.

3-Tier Architecture

This involves one more layer called the business logic tier, service tier or middle tier (layer). In the client-server solution the client was handling the business logic that makes the client “thick”. A thick client means that it requires heavy traffic with the server, thus making it difficult to use over slower network connections like Internet and Wireless (3G, Edge or Wi-Fi).

By introducing the middle layer, the client is only handling presentation logic. This means that only little communication is needed between the client and the middle tier making the client “thin” or “thinner”. An example of a thin client is an Internet browser that allows you to see and provide information fast and almost with no delay.

As more users access the system a three-tier solution is more scalable than the other solutions because you can add as many middle tiers (running on each own server) as needed to ensure good performance (N-tier or multiple-tier).

Security is also the best in the three-tier architecture because the middle layer protects the database tier.

There is one major drawback to the N-tier architecture and that is that the additional tiers increase the complexity and cost of the installation.

Take a look at the differences among these three.

	1-Tier	2-Tier	Multi-Tier
Benefits	Very simple Inexpensive No server needed It has both programs and data on one computer.	Good securityMore scalable Faster execution	Exceptional securityFastest execution “Thin” client Very scalable
Issues	Poor securityMulti user issues. Time required to update the application is high. Cost of redistributing the application is high.	More costly More complex “Thick” client Excessive load on the server. High network traffic. Difficulty in implementing incremental improvements.	Very costlyVery complex
Users	Usually 1 (or a few)	2-100	50-2000 (+)

ABAP Syllabus

2012-04-23T15:50:00.000+05:30

Introduction to ERP

What is ERP?
Why we need ERP?
Advantages of ERP
Major ERP Packages

Introduction to SAP & R/3 Architecture

What is SAP?
History & Features of SAP
SAP R/2 Architecture (Limitations of R/2 Architecture)
SAP R/3 Architecture (Types of work processes)
SAP R/3 Application Modules
SAP Landscape

Introduction to ABAP/4

What is ABAP?
Logon to SAP Environment
Transaction Codes
Multitasking Commands
Comments
Errors
ABAP/4 Editor ( SE38 )
Steps for Creating a Program
Elements in R/3 Screen
Out put Statements
Operators in ABAP
Data, Parameter & Constant Statements
Data Types & Classification
Data Objects & Classification
Text Elements
String Operations
Control Statements
Field strings

ABAP Dictionary

ABAP Dictionary Introduction
Data Dictionary Functions
Data Dictionary Objects
- Data Base Tables
- Structures
- Views
- Data Elements
- Type Groups
- Domains
- Search helps
- Lock objects
Primary Key And Foreign Key
Table Maintenance Generator

Packages

Creating a package
Difference between local objects & packages
Transferring local objects to packages

Variants

Variants Introduction
Creating variants in ABAP Editor & Data Dictionary

Message Classes

Message Class Introduction
Message types
Calling message class in Report & Dialog programs

Selection Screens

Selection screen Introduction
- Parameter Statement
- Select-options Statement
- Selection-screen Statement
Screen table and its fields
Dynamic screen modification by using Modif Id key

Open SQL Statements

Select
Insert
Modify
Update
Delete

Internal Tables

Internal Tables Introduction
Declaring Internal Table
Populating Internal Table
Processing Internal Table
Initializing Internal Tables
Inner Joins And For All Entries
Control Break Statements

Debugging Techniques

Debugging Techniques Introduction
Break-points (Static & Dynamic)
Watch points
Dynamically changing internal tables contents in Debugging Editor
Options to step through the program in Debugging Editor

Modularization Techniques

Modularization Techniques Introduction
Includes
Subroutines
Passing Parameters to Subroutines
Passing Tables to Subroutines
Function Groups & Function Modules

Reports

Reports Introduction
Classical Reports
Interactive Reports
Techniques Used For Interactive Reports
- Hotspot
- Hide
- Get Cursor

Dialog / Module Pool Programming/ Transactions

MPP Introduction
Relationship between Screen, Flow Logic and Program
Flow Logic Events
- Process Before Output (PBO)
- Process After Input (PAI)
- Process On Value Request (POV)
- Process On Help Request (POH)
Include Programs in MPP
- Include TOP
- Include I01
- Include O01
- Include F01
Dynamic Screens
- Leave Screen
- Leave to Screen
- Call Screen
- Set Screen
Processing of List from Transaction and Vice Versa
Elements in Screen Layout
- Table Controls
- Step Loops
- Tabstrip Controls
- Subscreens

Batch Data Communication

BDC Introduction
Recording
BDC Methods
- Call Transaction Method
- Session Method
Handling Table Controls in BDC
Legacy System Migration Workbench
- Different Methods
- Flat file creation
- Uploading data
File Handling
- Application Server
- Presentation Server

SAP Scripts

SAP Scripts Introduction
Components of SAP Scripts
- Layout Set
- Standard Text
- Out Put Program
Modifying Standard SAP Script Layouts
Including Logos
SAP Script Utilities – Upload / Download

Smart Forms

Smart Forms Introduction
Graphics Management
Style Maintenance
- Paragraph Formats
- Character Formats
Writing print program and designing layouts

ALV Reports

ALV Reports Introduction
ALV through Function Modules
ALV Types

Runtime Analysis & SQL Tracing Cross Applications

Introduction to Distributed Environment
Introduction to Cross Applications

RFC

Introduction to RFC
Creating RFC Destination between 2 Systems
Creating Remote Enabled Function Modules
Creating program using Remote Enabled Function Modules

ALE

ALE Basics
Overview of Outbound & Inbound Process
Configuration Steps
Define logical systems
Assign client to logical system
RFC destination
Customer distribution model
Creating Ports

IDocs

What is an Idoc?
Types of Idocs
- Basic Idocs
- Extension Idocs
Creating Idocs
Message Types
Assigning Idoc type to Message type

EDI

EDI Basics
Difference between ALE & EDI
Overview of Outbound & Inbound Process
Configuration Steps
Port Creation
Partner Profile Creation

BAPIs

BAPI Overview
Creation of BAPI

Workflow

What is workflow?
Overview of workflow

User Exits

User Exits Overview
Types of User Exits
- Field Exit
- Screen Exit
- Function Exit
- Menu Exit

BADIs

BADIs Overview
Defining a BADI
Implementing a BADI

OOPS Concept

Object Oriented ABAP Overview
Defining a Class
Implementing a Class

Miscellaneous Topics

Correction & Transport request (CTS)
Transport Organizer
Work Bench Request
Task Creation
Release Objects
SAP Memory & ABAP Memory
Logical Database
SD Flow
MM Flow

Some Important Links

2012-04-23T15:45:00.001+05:30

SAP Books Store

http://www.sap-press.com

Online BC ABAP Book

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/87/56d00222c011d2954a0000e8353423/frameset.htm

Free PDF's From SAP

http://help.sap.com/printdocu/core/print46c/en/data/index_en.htm

O	bits are one
Z	bits are Zero
M	bits are Mixed