SAP COM_EEW_BW_PR_SETTYPE Function Module for
COM_EEW_BW_PR_SETTYPE is a standard com eew bw pr settype 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 com eew bw pr settype FM, simply by entering the name COM_EEW_BW_PR_SETTYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_EEW_BW_INTERFACE
Program Name: SAPLCOM_EEW_BW_INTERFACE
Main Program: SAPLCOM_EEW_BW_INTERFACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_EEW_BW_PR_SETTYPE 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 'COM_EEW_BW_PR_SETTYPE'".
EXPORTING
* IV_MODE = "
IT_EXTENSIONDEF = "
IT_GOX_HEADER_OLD = "
IT_TAB_HEADER_OLD = "
IV_DEVCLASS = "
IV_NAME' ' = "
IV_NSPCSHT_DEV = "
IV_NSPCSHT_CUS = "
CHANGING
CT_GOX_HEADER = "
* CT_TABLE_ENTRIES = "
* CT_TASKPARAMLIST = "
CT_POSTPROC = "
TABLES
T_RETURN = "
EXCEPTIONS
TECHNICAL_ERROR = 1 SEMANTICAL_ERROR = 2
IMPORTING Parameters details for COM_EEW_BW_PR_SETTYPE
IV_MODE -
Data type: CHAR1Optional: Yes
Call by Reference: Yes
IT_EXTENSIONDEF -
Data type: TOXT_PARAMLISTOptional: No
Call by Reference: Yes
IT_GOX_HEADER_OLD -
Data type: COMT_GOX_DEF_HEADEROptional: No
Call by Reference: Yes
IT_TAB_HEADER_OLD -
Data type: COMT_GOX_TABLE_ENTRY_HEADEROptional: No
Call by Reference: Yes
IV_DEVCLASS -
Data type: DEVCLASSOptional: No
Call by Reference: Yes
IV_NAMESPACE -
Data type: NAMESPACEOptional: No
Call by Reference: Yes
IV_NSPCSHT_DEV -
Data type: OXT_NSPC_SHORTOptional: No
Call by Reference: Yes
IV_NSPCSHT_CUS -
Data type: OXT_NSPC_SHORTOptional: No
Call by Reference: Yes
CHANGING Parameters details for COM_EEW_BW_PR_SETTYPE
CT_GOX_HEADER -
Data type: COMT_GOX_DEF_HEADEROptional: No
Call by Reference: Yes
CT_TABLE_ENTRIES -
Data type: COMT_GOX_TABLE_ENTRY_HEADEROptional: Yes
Call by Reference: Yes
CT_TASKPARAMLIST -
Data type: TOXT_PARAMLISTOptional: Yes
Call by Reference: Yes
CT_POSTPROC -
Data type: TOXT_RT_TF_PPROCOptional: No
Call by Reference: Yes
TABLES Parameters details for COM_EEW_BW_PR_SETTYPE
T_RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TECHNICAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SEMANTICAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for COM_EEW_BW_PR_SETTYPE 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_iv_mode | TYPE CHAR1, " | |||
| lt_t_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_ct_gox_header | TYPE COMT_GOX_DEF_HEADER, " | |||
| lv_technical_error | TYPE COMT_GOX_DEF_HEADER, " | |||
| lv_it_extensiondef | TYPE TOXT_PARAMLIST, " | |||
| lv_ct_table_entries | TYPE COMT_GOX_TABLE_ENTRY_HEADER, " | |||
| lv_semantical_error | TYPE COMT_GOX_TABLE_ENTRY_HEADER, " | |||
| lv_ct_taskparamlist | TYPE TOXT_PARAMLIST, " | |||
| lv_it_gox_header_old | TYPE COMT_GOX_DEF_HEADER, " | |||
| lv_ct_postproc | TYPE TOXT_RT_TF_PPROC, " | |||
| lv_it_tab_header_old | TYPE COMT_GOX_TABLE_ENTRY_HEADER, " | |||
| lv_iv_devclass | TYPE DEVCLASS, " | |||
| lv_iv_namespace | TYPE NAMESPACE, " | |||
| lv_iv_nspcsht_dev | TYPE OXT_NSPC_SHORT, " | |||
| lv_iv_nspcsht_cus | TYPE OXT_NSPC_SHORT. " |
|   CALL FUNCTION 'COM_EEW_BW_PR_SETTYPE' " |
| EXPORTING | ||
| IV_MODE | = lv_iv_mode | |
| IT_EXTENSIONDEF | = lv_it_extensiondef | |
| IT_GOX_HEADER_OLD | = lv_it_gox_header_old | |
| IT_TAB_HEADER_OLD | = lv_it_tab_header_old | |
| IV_DEVCLASS | = lv_iv_devclass | |
| IV_NAMESPACE | = lv_iv_namespace | |
| IV_NSPCSHT_DEV | = lv_iv_nspcsht_dev | |
| IV_NSPCSHT_CUS | = lv_iv_nspcsht_cus | |
| CHANGING | ||
| CT_GOX_HEADER | = lv_ct_gox_header | |
| CT_TABLE_ENTRIES | = lv_ct_table_entries | |
| CT_TASKPARAMLIST | = lv_ct_taskparamlist | |
| CT_POSTPROC | = lv_ct_postproc | |
| TABLES | ||
| T_RETURN | = lt_t_return | |
| EXCEPTIONS | ||
| TECHNICAL_ERROR = 1 | ||
| SEMANTICAL_ERROR = 2 | ||
| . " COM_EEW_BW_PR_SETTYPE | ||
ABAP code using 7.40 inline data declarations to call FM COM_EEW_BW_PR_SETTYPE
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.Search for further information about these or an SAP related objects