SAP ROS_BUPA_SUPP_LIST_CAT Function Module for
ROS_BUPA_SUPP_LIST_CAT is a standard ros bupa supp list cat 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 ros bupa supp list cat FM, simply by entering the name ROS_BUPA_SUPP_LIST_CAT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ROS_BUPA
Program Name: SAPLROS_BUPA
Main Program: SAPLROS_BUPA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ROS_BUPA_SUPP_LIST_CAT 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 'ROS_BUPA_SUPP_LIST_CAT'".
EXPORTING
IT_PARTNER_IDS = "
IMPORTING
ES_BUPA_DATA = "
ET_BUPA_NOT_TRANS = "
TABLES
ET_MESSAGES = "
IMPORTING Parameters details for ROS_BUPA_SUPP_LIST_CAT
IT_PARTNER_IDS -
Data type: BUS_EI_INSTANCE_TOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ROS_BUPA_SUPP_LIST_CAT
ES_BUPA_DATA -
Data type: BUS_EI_MAINOptional: No
Call by Reference: Yes
ET_BUPA_NOT_TRANS -
Data type: BUS_EI_INSTANCE_TOptional: No
Call by Reference: Yes
TABLES Parameters details for ROS_BUPA_SUPP_LIST_CAT
ET_MESSAGES -
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ROS_BUPA_SUPP_LIST_CAT 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: | ||||
| lt_et_messages | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_es_bupa_data | TYPE BUS_EI_MAIN, " | |||
| lv_it_partner_ids | TYPE BUS_EI_INSTANCE_T, " | |||
| lv_et_bupa_not_trans | TYPE BUS_EI_INSTANCE_T. " |
|   CALL FUNCTION 'ROS_BUPA_SUPP_LIST_CAT' " |
| EXPORTING | ||
| IT_PARTNER_IDS | = lv_it_partner_ids | |
| IMPORTING | ||
| ES_BUPA_DATA | = lv_es_bupa_data | |
| ET_BUPA_NOT_TRANS | = lv_et_bupa_not_trans | |
| TABLES | ||
| ET_MESSAGES | = lt_et_messages | |
| . " ROS_BUPA_SUPP_LIST_CAT | ||
ABAP code using 7.40 inline data declarations to call FM ROS_BUPA_SUPP_LIST_CAT
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