SAP AKB_DISPLAY_CHECK_HISTORY Function Module for
AKB_DISPLAY_CHECK_HISTORY is a standard akb display check history SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for akb display check history FM, simply by entering the name AKB_DISPLAY_CHECK_HISTORY into the relevant SAP transaction such as SE37 or SE38.
Function Group: PA_AKB_COMPCHECK
Program Name: SAPLPA_AKB_COMPCHECK
Main Program: SAPLPA_AKB_COMPCHECK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function AKB_DISPLAY_CHECK_HISTORY pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'AKB_DISPLAY_CHECK_HISTORY'".
EXPORTING
* EDIT_MODE = 'X' "Edit mode
CHANGING
OBJECT = "Compatibility Control
* VERSIONS = "Versions
EXCEPTIONS
NO_VERSIONS = 1
IMPORTING Parameters details for AKB_DISPLAY_CHECK_HISTORY
EDIT_MODE - Edit mode
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for AKB_DISPLAY_CHECK_HISTORY
OBJECT - Compatibility Control
Data type: AKB_TRANS_CHECKOptional: No
Call by Reference: Yes
VERSIONS - Versions
Data type: AKB_TRANS_CHECK_TYPEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_VERSIONS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for AKB_DISPLAY_CHECK_HISTORY Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_object | TYPE AKB_TRANS_CHECK, " | |||
lv_edit_mode | TYPE FLAG, " 'X' | |||
lv_no_versions | TYPE FLAG, " | |||
lv_versions | TYPE AKB_TRANS_CHECK_TYPE. " |
  CALL FUNCTION 'AKB_DISPLAY_CHECK_HISTORY' " |
EXPORTING | ||
EDIT_MODE | = lv_edit_mode | |
CHANGING | ||
OBJECT | = lv_object | |
VERSIONS | = lv_versions | |
EXCEPTIONS | ||
NO_VERSIONS = 1 | ||
. " AKB_DISPLAY_CHECK_HISTORY |
ABAP code using 7.40 inline data declarations to call FM AKB_DISPLAY_CHECK_HISTORY
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.DATA(ld_edit_mode) | = 'X'. | |||
Search for further information about these or an SAP related objects