ABAP Tutorials » function module

Display a Popup and Get Values from User

Admin — Fri, 23 Sep 2011 12:19:32 +0000

In some cases, we are needed to get some inputs from the user at run-time of an application based on certain dynamic conditions.

Function Module POPUP_GET_VALUES can be used to display a popup to get inputs from user. The specialty of this function module is we can add as many number of fields as we want. The fields can be of any data type.

REPORT ztestpopup.

DATA: t_fields LIKE sval OCCURS 0 WITH HEADER LINE.

START-OF-SELECTION.

*— Prepare Parameters for FM ————-*
t_fields-tabname = ’BKPF’.
t_fields-fieldname = ’BUDAT’.
APPEND t_fields.

t_fields-tabname = ’BKPF’.
t_fields-fieldname = ’BLART’.
APPEND t_fields.

*—- Function Module Call —————–*
CALL FUNCTION ’POPUP_GET_VALUES’
EXPORTING
* NO_VALUE_CHECK = ’ ’
popup_title = ’Test Popup’
* START_COLUMN = ’5’
* START_ROW = ’5’
* IMPORTING
* RETURNCODE =
TABLES
fields = t_fields
EXCEPTIONS
error_in_fields = 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.
ENDIF.

*— Display Report —————-*
LOOP AT t_fields.
WRITE:/ t_fields-value.
ENDLOOP.

You might also be interested in these posts:

Useful Function Modules in ABAP-HR

Admin — Wed, 09 Dec 2009 09:48:37 +0000

Function modules are always helpful, specially when dealing a complex module like ABAP HR. Thanks to SAP that has provided strong Function Module support.

Here is the list of some useful ABAP HR function modules:

RS_PROGRAM_CHECK_NAME: To check program names if you are generating them.
RS_CORR_INSERT : To insert the correction request in the repository.
REPS_OBJECT_ACTIVATE: To activate repository objects, for example – to activate a newly generated program.
RS_DELETE_PROGRAM: To delete the program.
RS_ACCESS_PERMISSION: To lock or unlock a program.

Function Modules related to Date and Time Calculations
CALCULATE_DATE: Calculates the future date based on the input .
DATE_TO_DAY: Returns the Day for the entered date.
DATE_COMPUTE_DAY: Returns weekday for a date
DATE_GET_WEEK: Returns week for a date
RP_CALC_DATE_IN_INTERVAL: Add days / months to a date

Function Modules related to (ALV) ADVANCED LIST VIEWER
REUSE_ALV_LIST_DISPLAY: ABAP List viewer (LIST DISPLAY)
REUSE_ALV_GRID_DISPLAY: ALV GridControl full screen
REUSE_ALV_FIELDCATALOG_MERGE: Create field catalog from dictionary structure or internal table

Function Module related to Change Tracking
CHANGEDOCUMENT_READ_HEADERS: Read and format change documents
DAY_ATTRIBUTES_GET: Returns attributes for a range of dates specified
MONTHS_BETWEEN_TWO_DATES: To get the number of months between the two dates.
END_OF_MONTH_DETERMINE_2: Determines the End of a Month.
HR_HK_DIFF_BT_2_DATES: Find the difference between two dates in years, months and days.
FIMA_DAYS_AND_MONTHS_AND_YEARS: Find the difference between two dates in years, months and days.
MONTH_NAMES_GET: Get the names of the month
IDWT_READ_MONTH_TEXT: Get the MONTH Text
WEEK_GET_FIRST_DAY : Get the first day of the week
HRGPBS_HESA_DATE_FORMAT: Format the date in dd/mm/yyyy format
SD_CALC_DURATION_FROM_DATETIME: Find the difference between two date/time and report the difference in hours
L_MC_TIME_DIFFERENCE: Find the time difference between two date/time
HR_99S_INTERVAL_BETWEEN_DATES: Difference between two dates in days, weeks, months
LAST_DAY_OF_MONTHS: Returns the last day of the month
DATE_CHECK_PLAUSIBILITY: Check for the invalid date.
DATE_2D_TO_4D_CONVERSION: Year entry: 2-character to 4-character.
DAY_IN_WEEK: Input date and will give the name of the day 1-monday,2-Tuesday….
SD_DATETIME_DIFFERENCE: Give the difference in Days and Time for 2 dates

Function Modules Related To Formatting

CLOI_PUT_SIGN_IN_FRONT: Displays the negative sign in front of the numeral.

RKD_WORD_WRAP: Wrap text into several lines

CONVERSION_EXIT_ALPHA_INPUT: Pad zeros to the number at the left

CONVERSION_EXIT_ALPHA_OUTPUT: Eliminate zeros to the number at the left

READ_EXCHANGE_RATE: Exchange Conversion

SPELL_AMOUNT: Transforms numeric values into text

Function Modules Related To Dialog Prompts

POPUP_TO_CONFIRM: Displays a popup dialog with a user defined message for confirmation

POPUP_TO_GET_VALUE: Displays a popup dialog requesting a value for a particular table-fieldname

SAPGUI_PROGRESS_INDICATOR: Displays a progress bar with text to denote the percentage of completion and status

FILENAME_GET: Displays a popup dialog to get the presentation server filename

F4_DATE: Displays a popup dialog to choose date

POPUP_TO_SELECT_MONTH: Display a pop-up to select a month

GET_PRINT_PARAMETERS: Printer parameters

Function modules related to RFC communication

RFC_CONNECTION_CLOSE: Close a RFC connection

RFC_GET_SYSTEM_INFO : Give system’s information of a remote system

Function modules related to reading/writing files

FILE_READ_AND_CONVERT_SAP_DATA: Uploads the file from either presentation or application server into an internal table

SUBST_GET_FILE_LIST: To get the list of files from Application Server.

ALSM_EXCEL_TO_INTERNAL_TABLE: Legacy Data Transfer w/ Excel

WS_FILE_DELETE: Delete files on UNIX server

PFL_COPY_OS_FILE: Copy UNIX files

EPS_GET_DIRECTORY_LISTING: Returns all files from a Server directory

Function Modules related to sending emails

SO_NEW_DOCUMENT_ATT_SEND_API1 – Sends emails with texts and attachments
SO_NEW_DOCUMENT_SEND_API1 – Sends emails with texts.

Function Modules related to F4 Help

F4IF_INT_TABLE_VALUE_REQUEST – F4 help also returning the value to be displayed in internal table

Function Modules related to data maintenance

VIEW_MAINTENANCE_CALL – To maintain data from a table

You might also be interested in these posts:

Date formatting for Display in ABAP Program

Admin — Thu, 15 Oct 2009 12:47:51 +0000

Function module FORMAT_DATE_4_OUTPUT comes in handy in case we need simple formatting on date. Formatting which involves change in position day, month and year, changing the separator we can achieve with this function module. Following sample code shows how we can manipulate date directly to different formats.

Sample code:

Program ZDATEFORMAT.
DATA : v_date TYPE syst-datum ,
      lv_foramt TYPE char10  .

START-OF-SELECTION .
PERFORM format_date USING 'DD.MM.YYYY' .
PERFORM format_date USING 'DD/MM/YYYY' .
PERFORM format_date USING 'DD/MM/YY' .
PERFORM format_date USING 'YY-MM-DD' .
PERFORM format_date USING 'MM*DD*YYYY' .
PERFORM format_date USING 'YY,MM,DD' .

*&---------------------------------------------------------------------*
*&      Form format_date
*&---------------------------------------------------------------------*
FORM format_date USING iv_format TYPE rn1datum-format.
  DATA : lv_date TYPE rn1datum-datex .
  CALL FUNCTION 'FORMAT_DATE_4_OUTPUT'
  EXPORTING
    datin  = sy-datum
    format = iv_format
  IMPORTING
    datex  = lv_date.
  WRITE : / sy-datum , ' Format : ' , iv_format , lv_date .
ENDFORM.                    "format_date

You might also be interested in these posts:

ABAP code for saving Long Text in BDC

Admin — Sat, 19 Sep 2009 05:59:51 +0000

There has been requirements for recording BDC for screens involving Long Text (Free field for text entry). The part that is a bit tricky is, the TextEdit control (Long Text field) does not gets recorded in the BDC.

The following function module is used to save the data with respect to the screen (say, Sales Order Number in case recording ‘Description’ and ‘Created By’ using VA01).

Steps:

1. Create an internal table of type TLINE and structure of type THEAD.
DATA: lines TYPE tline occurs 0 with header line,
header TYPE thead.

2. Fill the data in the internal table.
NOTE: TO get tdobject, tdname, tdid, tdspras; double click in TextArea and the select GOTO- > HEADER.

      header-tdobject   = 'VBBK'.
      header-tdname     = 'XXXXXXXXXX'.
      header-tdid       = 'ZM01'.
      header-tdspras    = 'EN'.
      header-tdlinesize = '072'.

*--- Calling the function and getting the retrieved data
*--- to be dispalyed
      call function 'EDIT_TEXT'
        exporting
*   DISPLAY             = ' '
*    EDITOR_TITLE       = ' '
          header              = header
*   PAGE                = ' '
*   WINDOW              = ' '
          save                = ''
*   LINE_EDITOR         = ' '
*   CONTROL             = ' '
*   PROGRAM             = ' '
*   LOCAL_CAT           = ' '
* IMPORTING
*   FUNCTION            =
*   NEWHEADER           =
*   RESULT              =
        tables
          lines               = lines
* EXCEPTIONS
*   ID                  = 1
*   LANGUAGE            = 2
*   LINESIZE            = 3
*   NAME                = 4
*   OBJECT              = 5
*   TEXTFORMAT          = 6
*   COMMUNICATION       = 7
*   OTHERS              = 8
                .
      if sy-subrc <> 0.
        message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      endif.

3. Now, at the time of saving, Save the data into Database with reference to Sales Document Number(v_vbeln). Note: this code should be written after the Sales Document is saved.

if lines[] is NOT INITIAL.
      header-tdobject   = 'VBBK'.
      header-tdname     =  v_vbeln.
      header-tdid       = 'ZM01'.
      header-tdspras    = 'EN'.
      header-tdlinesize = '072'.

      CALL FUNCTION 'SAVE_TEXT'
        EXPORTING
*         CLIENT                = SY-MANDT
          HEADER                = header
          INSERT                = 'V'
          SAVEMODE_DIRECT       = 'X'
*         OWNER_SPECIFIED       = ' '
*         LOCAL_CAT             = ' '
*       IMPORTING
*         FUNCTION              =
*         NEWHEADER             =
        TABLES
          LINES                 = lines
*       EXCEPTIONS
*         ID                    = 1
*         LANGUAGE              = 2
*         NAME                  = 3
*         OBJECT                = 4
*         OTHERS                = 5
                .
      IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.

endif.

You might also be interested in these posts:

Type of Database Updates in SAP

Admin — Mon, 20 Jul 2009 23:51:11 +0000

There are three types of Updates that can occurs to the database, depending upon the priorty given to the work.

V1 – Synchronous update
V2 – Asynchronous update
V3 – Batch asynchronous update

These are different work processes on the application server that takes the update LUW (which may have various DB manipulation SQLs) from the running program and execute it. These are separated to optimize transaction processing capabilities.

Synchronous Updating (V1 Update)
The statistics update is made synchronously with the document update.
While updating, if problems that result in the termination of the statistics update occur, the original documents are NOT saved. The cause of the termination should be investigated and the problem solved. Subsequently, the documents can be entered again.

Asynchronous Updating (V2 Update)
With this update type, the document update is made separately from the statistics update. A termination of the statistics update has NO influence on the document update (see V1 Update).

Asynchronous Updating (V3 Update)
With this update type, updating is made separately from the document update. The difference between this update type and the V2 Update lies, however, with the time schedule. If the V3 update is active, then the update can be executed at a later time.

Practical Examples

If you create/change a purchase order (me21n/me22n), when you press ‘SAVE’ and see a success message (PO…. changed..), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.

There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S012 stores purchasing data (it is the same data as EKKO/EKPO stored redundantly, but in a different structure to optimize reporting). Now, these tables are updated with the txn you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message). You can see V1/V2/V3 queues in SM12 or SM13.

V3 is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately. You have to schedule a job (eg in LBWE definitions) to process these. This is again to optimize performance.

V2 and V3 are separated from V1 as these are not as realtime critical (updating statistical data). If all these updates were put together in one LUW, system performance (concurrency, locking etc) would be impacted.

Serialized V3 update is called after V2 has happened (this is how the code running these updates is written) so if you have both V2 and V3 updates from a txn, if V2 fails or is waiting, V3 will not happen yet.

BTW, ‘serialized’ V3 is discontinued now, in later releases of PI you will have only unserialized V3.

In contrast to V1 and V2 Updates , no single documents are updated. The V3 update is, therefore, also described as a collective update.

Creating Update Modules

Update Modules can be created as follows:

1. ChooseTools – > ABAP Workbench,Function Builder.

2. To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to one of the following values:

Update with immediate start

Set this option for high priority (“V1″) functions that run in a shared (SAP LUW). These functions can be restarted by the update task in case of errors.

Update w. imm. start, no restart

Set this option for high priority (“V1″) functions that run in a shared (SAP LUW). These functions may not be restarted by the update task.

Update with delayed start

Set this option for low priority (“V2″) functions that run in their own update transactions. These functions can be restarted by the update task in case of errors.

Collective Run

Unlike V1 and V2 updates, V3 updates (or collective runs) are not started directly. The update is performed by a background job (report RSM13005). In this case, the update requests are not updated separately, but rather all modules of the same type are updated in a single database transaction. As the database can operate with far fewer database transactions, system performance is dramatically improved. Background jobs should be started in Customizing of the relevant applications that use the V3 update.

Defining Update Type (Function Module)

Summing Up !

V1: The update should be performed soon. The update record is protected by R/3 locks. The update is critical for the operational consistency of the system.
V2: The update does not have to be performed soon. The update is not protected by locks. The update modules do not contain “vital” data.
V3: As V2, but, you use report RSM13005 to start the updates.

Note that the V3 update offers an advantage with regard to speed when considering its disadvantages. Report RSM13005 also eliminates some of the disadvantages of the V3 update.

You might also be interested in these posts: