SAP EHSWA_801_BAL_DATA_GET Function Module for
EHSWA_801_BAL_DATA_GET is a standard ehswa 801 bal data get 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 ehswa 801 bal data get FM, simply by entering the name EHSWA_801_BAL_DATA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHSWA_801
Program Name: SAPLEHSWA_801
Main Program: SAPLEHSWA_801
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EHSWA_801_BAL_DATA_GET 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 'EHSWA_801_BAL_DATA_GET'".
EXPORTING
* I_SELOPT_BPID = "
* I_SELOPT_DATE = "
* I_DATE_CAT = IC_DATE_TRANS_HANDOVR "
* I_SELOPT_MNCAT = "
* I_SELOPT_MNSTATUS = "
* I_FLG_DIALOG = ESP1_TRUE "Indicator: Screen Display of Critical Messages
IMPORTING
E_DOC_TAB = "List of Disposal Documents
E_MN_API_TAB = "
E_FLG_ERROR = "Indicator: Error Occurred
E_FLG_WARNING = "Indicator: Warning Occurred
E_MESSAGE_TAB = "Message Table Waste Management
IMPORTING Parameters details for EHSWA_801_BAL_DATA_GET
I_SELOPT_BPID -
Data type: EHSW_TT_SELOPT_BPIDOptional: Yes
Call by Reference: Yes
I_SELOPT_DATE -
Data type: EHSW_TT_SELOPT_DATEOptional: Yes
Call by Reference: Yes
I_DATE_CAT -
Data type: EHSWAE_DATE_CATDefault: IC_DATE_TRANS_HANDOVR
Optional: Yes
Call by Reference: Yes
I_SELOPT_MNCAT -
Data type: EHSW_TT_SELOPT_MNCATOptional: Yes
Call by Reference: Yes
I_SELOPT_MNSTATUS -
Data type: EHSW_TT_SELOPT_MNSTATUSOptional: Yes
Call by Reference: Yes
I_FLG_DIALOG - Indicator: Screen Display of Critical Messages
Data type: ESP1_BOOLEANDefault: ESP1_TRUE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for EHSWA_801_BAL_DATA_GET
E_DOC_TAB - List of Disposal Documents
Data type: EHSW_TT_BALANCE_DOCOptional: No
Call by Reference: Yes
E_MN_API_TAB -
Data type: EHSWA_MNAPI_TAB_TYPEOptional: No
Call by Reference: Yes
E_FLG_ERROR - Indicator: Error Occurred
Data type: ESP1_BOOLEANOptional: No
Call by Reference: Yes
E_FLG_WARNING - Indicator: Warning Occurred
Data type: ESP1_BOOLEANOptional: No
Call by Reference: Yes
E_MESSAGE_TAB - Message Table Waste Management
Data type: EHSW_TT_MESSAGEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EHSWA_801_BAL_DATA_GET 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_e_doc_tab | TYPE EHSW_TT_BALANCE_DOC, " | |||
lv_i_selopt_bpid | TYPE EHSW_TT_SELOPT_BPID, " | |||
lv_e_mn_api_tab | TYPE EHSWA_MNAPI_TAB_TYPE, " | |||
lv_i_selopt_date | TYPE EHSW_TT_SELOPT_DATE, " | |||
lv_i_date_cat | TYPE EHSWAE_DATE_CAT, " IC_DATE_TRANS_HANDOVR | |||
lv_e_flg_error | TYPE ESP1_BOOLEAN, " | |||
lv_e_flg_warning | TYPE ESP1_BOOLEAN, " | |||
lv_i_selopt_mncat | TYPE EHSW_TT_SELOPT_MNCAT, " | |||
lv_e_message_tab | TYPE EHSW_TT_MESSAGE, " | |||
lv_i_selopt_mnstatus | TYPE EHSW_TT_SELOPT_MNSTATUS, " | |||
lv_i_flg_dialog | TYPE ESP1_BOOLEAN. " ESP1_TRUE |
  CALL FUNCTION 'EHSWA_801_BAL_DATA_GET' " |
EXPORTING | ||
I_SELOPT_BPID | = lv_i_selopt_bpid | |
I_SELOPT_DATE | = lv_i_selopt_date | |
I_DATE_CAT | = lv_i_date_cat | |
I_SELOPT_MNCAT | = lv_i_selopt_mncat | |
I_SELOPT_MNSTATUS | = lv_i_selopt_mnstatus | |
I_FLG_DIALOG | = lv_i_flg_dialog | |
IMPORTING | ||
E_DOC_TAB | = lv_e_doc_tab | |
E_MN_API_TAB | = lv_e_mn_api_tab | |
E_FLG_ERROR | = lv_e_flg_error | |
E_FLG_WARNING | = lv_e_flg_warning | |
E_MESSAGE_TAB | = lv_e_message_tab | |
. " EHSWA_801_BAL_DATA_GET |
ABAP code using 7.40 inline data declarations to call FM EHSWA_801_BAL_DATA_GET
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_i_date_cat) | = IC_DATE_TRANS_HANDOVR. | |||
DATA(ld_i_flg_dialog) | = ESP1_TRUE. | |||
Search for further information about these or an SAP related objects