SAP EHSWA_FILL_EHSWAT_APPBP Function Module for
EHSWA_FILL_EHSWAT_APPBP is a standard ehswa fill ehswat appbp 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 fill ehswat appbp FM, simply by entering the name EHSWA_FILL_EHSWAT_APPBP into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHSWA_004B
Program Name: SAPLEHSWA_004B
Main Program: SAPLEHSWA_004B
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHSWA_FILL_EHSWAT_APPBP 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_FILL_EHSWAT_APPBP'".
EXPORTING
I_PARTNER_RECN = "
* I_FLG_UPDATE = ESP1_FALSE "
* I_FLG_SHOW_MSG_IN_DIALOG = ESP1_TRUE "
* I_RVLID = "
I_RLTYP = "
I_PARTNER = "
I_APPROVAL_RECN = "
I_APPROVAL_APC = "
I_APPROVAL_APMNCAT = "
* I_APPROVAL_INTAPPNO = "
* I_SY_TABIX = "
IMPORTING
E_FLG_ERROR = "
E_PARTNER = "
E_FATHER = "
TABLES
* X_MESSAGE_TAB = "
IMPORTING Parameters details for EHSWA_FILL_EHSWAT_APPBP
I_PARTNER_RECN -
Data type: EHSWAT100-RECNOptional: No
Call by Reference: No ( called with pass by value option)
I_FLG_UPDATE -
Data type: ESP1_BOOLEANDefault: ESP1_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_SHOW_MSG_IN_DIALOG -
Data type: ESP1_BOOLEANDefault: ESP1_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RVLID -
Data type: EHSWAT_BPID-RVLIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RLTYP -
Data type: EHSWAT100-RLTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_PARTNER -
Data type: EHSWAT000-PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
I_APPROVAL_RECN -
Data type: EHSWAT_APPROVAL-RECNOptional: No
Call by Reference: No ( called with pass by value option)
I_APPROVAL_APC -
Data type: EHSWAT_APPROVAL-APCOptional: No
Call by Reference: No ( called with pass by value option)
I_APPROVAL_APMNCAT -
Data type: EHSWAT_APPROVAL-APMNCATOptional: No
Call by Reference: No ( called with pass by value option)
I_APPROVAL_INTAPPNO -
Data type: EHSWAT_APPROVAL-INTAPPNOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SY_TABIX -
Data type: SY-TABIXOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EHSWA_FILL_EHSWAT_APPBP
E_FLG_ERROR -
Data type: ESP1_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
E_PARTNER -
Data type: EHSWAS_APPBPIOTOptional: No
Call by Reference: Yes
E_FATHER -
Data type: EHSWAS_APPBPIOTOptional: No
Call by Reference: Yes
TABLES Parameters details for EHSWA_FILL_EHSWAT_APPBP
X_MESSAGE_TAB -
Data type: EHSWAS_ERROR_TABOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for EHSWA_FILL_EHSWAT_APPBP 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_flg_error | TYPE ESP1_BOOLEAN, " | |||
| lt_x_message_tab | TYPE STANDARD TABLE OF EHSWAS_ERROR_TAB, " | |||
| lv_i_partner_recn | TYPE EHSWAT100-RECN, " | |||
| lv_i_flg_update | TYPE ESP1_BOOLEAN, " ESP1_FALSE | |||
| lv_i_flg_show_msg_in_dialog | TYPE ESP1_BOOLEAN, " ESP1_TRUE | |||
| lv_i_rvlid | TYPE EHSWAT_BPID-RVLID, " | |||
| lv_e_partner | TYPE EHSWAS_APPBPIOT, " | |||
| lv_i_rltyp | TYPE EHSWAT100-RLTYP, " | |||
| lv_e_father | TYPE EHSWAS_APPBPIOT, " | |||
| lv_i_partner | TYPE EHSWAT000-PARTNER, " | |||
| lv_i_approval_recn | TYPE EHSWAT_APPROVAL-RECN, " | |||
| lv_i_approval_apc | TYPE EHSWAT_APPROVAL-APC, " | |||
| lv_i_approval_apmncat | TYPE EHSWAT_APPROVAL-APMNCAT, " | |||
| lv_i_approval_intappno | TYPE EHSWAT_APPROVAL-INTAPPNO, " | |||
| lv_i_sy_tabix | TYPE SY-TABIX. " |
|   CALL FUNCTION 'EHSWA_FILL_EHSWAT_APPBP' " |
| EXPORTING | ||
| I_PARTNER_RECN | = lv_i_partner_recn | |
| I_FLG_UPDATE | = lv_i_flg_update | |
| I_FLG_SHOW_MSG_IN_DIALOG | = lv_i_flg_show_msg_in_dialog | |
| I_RVLID | = lv_i_rvlid | |
| I_RLTYP | = lv_i_rltyp | |
| I_PARTNER | = lv_i_partner | |
| I_APPROVAL_RECN | = lv_i_approval_recn | |
| I_APPROVAL_APC | = lv_i_approval_apc | |
| I_APPROVAL_APMNCAT | = lv_i_approval_apmncat | |
| I_APPROVAL_INTAPPNO | = lv_i_approval_intappno | |
| I_SY_TABIX | = lv_i_sy_tabix | |
| IMPORTING | ||
| E_FLG_ERROR | = lv_e_flg_error | |
| E_PARTNER | = lv_e_partner | |
| E_FATHER | = lv_e_father | |
| TABLES | ||
| X_MESSAGE_TAB | = lt_x_message_tab | |
| . " EHSWA_FILL_EHSWAT_APPBP | ||
ABAP code using 7.40 inline data declarations to call FM EHSWA_FILL_EHSWAT_APPBP
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.| "SELECT single RECN FROM EHSWAT100 INTO @DATA(ld_i_partner_recn). | ||||
| DATA(ld_i_flg_update) | = ESP1_FALSE. | |||
| DATA(ld_i_flg_show_msg_in_dialog) | = ESP1_TRUE. | |||
| "SELECT single RVLID FROM EHSWAT_BPID INTO @DATA(ld_i_rvlid). | ||||
| "SELECT single RLTYP FROM EHSWAT100 INTO @DATA(ld_i_rltyp). | ||||
| "SELECT single PARTNER FROM EHSWAT000 INTO @DATA(ld_i_partner). | ||||
| "SELECT single RECN FROM EHSWAT_APPROVAL INTO @DATA(ld_i_approval_recn). | ||||
| "SELECT single APC FROM EHSWAT_APPROVAL INTO @DATA(ld_i_approval_apc). | ||||
| "SELECT single APMNCAT FROM EHSWAT_APPROVAL INTO @DATA(ld_i_approval_apmncat). | ||||
| "SELECT single INTAPPNO FROM EHSWAT_APPROVAL INTO @DATA(ld_i_approval_intappno). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_i_sy_tabix). | ||||
Search for further information about these or an SAP related objects