SAP BAPI_RE_SU_GET_DETAIL Function Module for Return Settlement Unit Data
BAPI_RE_SU_GET_DETAIL is a standard bapi re su get detail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Return Settlement Unit Data processing and below is the pattern details for this FM, 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 bapi re su get detail FM, simply by entering the name BAPI_RE_SU_GET_DETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: RESC_BAPI_SETTL_UNIT
Program Name: SAPLRESC_BAPI_SETTL_UNIT
Main Program: SAPLRESC_BAPI_SETTL_UNIT
Appliation area:
Release date: 19-Aug-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_RE_SU_GET_DETAIL 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 'BAPI_RE_SU_GET_DETAIL'"Return Settlement Unit Data.
EXPORTING
COMPCODE = "Company Code
BUSINESSENTITYNUMBER = "Business Entity Number
SERVCHARGEKEY = "Service Charge Key
SETTLEMENTUNITNUMBER = "Settlement Unit
* DETAIL_DATA_FROM = "Date: Detailed Data Valid From
* DETAIL_DATA_TO = "Date: Detailed Data Valid To
IMPORTING
SETTL_UNIT = "Settlement Unit
TABLES
* PARTICIP_REL = "Assigned Participation Groups
* STATUS = "Status
* EXTENSION_OUT = "Data of User Fields
* RETURN = "Return Parameter(s)
* APPORT_RULE = "Apportionment Rules
* COST_OBJECT = "Cost Object SUs
* TERM_ORG_ASSIGNMENT = "Organizational Assignment
* MEASPT = "Measuring Point
* OPTION_RATE = "Option Rates
* COSTCOLLECTOR = "Cost Collector
* RESUBM_RULE = "Reminder Rules
* RESUBM_DATE = "Reminder Dates
IMPORTING Parameters details for BAPI_RE_SU_GET_DETAIL
COMPCODE - Company Code
Data type: BAPI_RE_SETTL_UNIT_KEY-COMP_CODEOptional: No
Call by Reference: No ( called with pass by value option)
BUSINESSENTITYNUMBER - Business Entity Number
Data type: BAPI_RE_SETTL_UNIT_KEY-BUSINESS_ENTITYOptional: No
Call by Reference: No ( called with pass by value option)
SERVCHARGEKEY - Service Charge Key
Data type: BAPI_RE_SETTL_UNIT_KEY-SERV_CHARGE_KEYOptional: No
Call by Reference: No ( called with pass by value option)
SETTLEMENTUNITNUMBER - Settlement Unit
Data type: BAPI_RE_SETTL_UNIT_KEY-SETTLEMENT_UNITOptional: No
Call by Reference: No ( called with pass by value option)
DETAIL_DATA_FROM - Date: Detailed Data Valid From
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROMOptional: Yes
Call by Reference: No ( called with pass by value option)
DETAIL_DATA_TO - Date: Detailed Data Valid To
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_RE_SU_GET_DETAIL
SETTL_UNIT - Settlement Unit
Data type: BAPI_RE_SETTL_UNITOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RE_SU_GET_DETAIL
PARTICIP_REL - Assigned Participation Groups
Data type: BAPI_RE_PARTICIP_RELOptional: Yes
Call by Reference: Yes
STATUS - Status
Data type: BAPI_RE_STATUSOptional: Yes
Call by Reference: Yes
EXTENSION_OUT - Data of User Fields
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
APPORT_RULE - Apportionment Rules
Data type: BAPI_RE_APPORT_RULEOptional: Yes
Call by Reference: Yes
COST_OBJECT - Cost Object SUs
Data type: BAPI_RE_COST_OBJECTOptional: Yes
Call by Reference: Yes
TERM_ORG_ASSIGNMENT - Organizational Assignment
Data type: BAPI_RE_TERM_OAOptional: Yes
Call by Reference: Yes
MEASPT - Measuring Point
Data type: BAPI_RE_MEASPTOptional: Yes
Call by Reference: Yes
OPTION_RATE - Option Rates
Data type: BAPI_RE_OPTION_RATEOptional: Yes
Call by Reference: No ( called with pass by value option)
COSTCOLLECTOR - Cost Collector
Data type: BAPI_RE_COSTCOLLECTOROptional: Yes
Call by Reference: Yes
RESUBM_RULE - Reminder Rules
Data type: BAPI_RE_RESUBM_RULEOptional: Yes
Call by Reference: Yes
RESUBM_DATE - Reminder Dates
Data type: BAPI_RE_RESUBM_DATEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_RE_SU_GET_DETAIL 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_compcode | TYPE BAPI_RE_SETTL_UNIT_KEY-COMP_CODE, " | |||
| lv_settl_unit | TYPE BAPI_RE_SETTL_UNIT, " | |||
| lt_particip_rel | TYPE STANDARD TABLE OF BAPI_RE_PARTICIP_REL, " | |||
| lt_status | TYPE STANDARD TABLE OF BAPI_RE_STATUS, " | |||
| lt_extension_out | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_apport_rule | TYPE STANDARD TABLE OF BAPI_RE_APPORT_RULE, " | |||
| lv_businessentitynumber | TYPE BAPI_RE_SETTL_UNIT_KEY-BUSINESS_ENTITY, " | |||
| lt_cost_object | TYPE STANDARD TABLE OF BAPI_RE_COST_OBJECT, " | |||
| lv_servchargekey | TYPE BAPI_RE_SETTL_UNIT_KEY-SERV_CHARGE_KEY, " | |||
| lt_term_org_assignment | TYPE STANDARD TABLE OF BAPI_RE_TERM_OA, " | |||
| lv_settlementunitnumber | TYPE BAPI_RE_SETTL_UNIT_KEY-SETTLEMENT_UNIT, " | |||
| lt_measpt | TYPE STANDARD TABLE OF BAPI_RE_MEASPT, " | |||
| lv_detail_data_from | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROM, " | |||
| lt_option_rate | TYPE STANDARD TABLE OF BAPI_RE_OPTION_RATE, " | |||
| lv_detail_data_to | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TO, " | |||
| lt_costcollector | TYPE STANDARD TABLE OF BAPI_RE_COSTCOLLECTOR, " | |||
| lt_resubm_rule | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE, " | |||
| lt_resubm_date | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_DATE. " |
|   CALL FUNCTION 'BAPI_RE_SU_GET_DETAIL' "Return Settlement Unit Data |
| EXPORTING | ||
| COMPCODE | = lv_compcode | |
| BUSINESSENTITYNUMBER | = lv_businessentitynumber | |
| SERVCHARGEKEY | = lv_servchargekey | |
| SETTLEMENTUNITNUMBER | = lv_settlementunitnumber | |
| DETAIL_DATA_FROM | = lv_detail_data_from | |
| DETAIL_DATA_TO | = lv_detail_data_to | |
| IMPORTING | ||
| SETTL_UNIT | = lv_settl_unit | |
| TABLES | ||
| PARTICIP_REL | = lt_particip_rel | |
| STATUS | = lt_status | |
| EXTENSION_OUT | = lt_extension_out | |
| RETURN | = lt_return | |
| APPORT_RULE | = lt_apport_rule | |
| COST_OBJECT | = lt_cost_object | |
| TERM_ORG_ASSIGNMENT | = lt_term_org_assignment | |
| MEASPT | = lt_measpt | |
| OPTION_RATE | = lt_option_rate | |
| COSTCOLLECTOR | = lt_costcollector | |
| RESUBM_RULE | = lt_resubm_rule | |
| RESUBM_DATE | = lt_resubm_date | |
| . " BAPI_RE_SU_GET_DETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RE_SU_GET_DETAIL
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 COMP_CODE FROM BAPI_RE_SETTL_UNIT_KEY INTO @DATA(ld_compcode). | ||||
| "SELECT single BUSINESS_ENTITY FROM BAPI_RE_SETTL_UNIT_KEY INTO @DATA(ld_businessentitynumber). | ||||
| "SELECT single SERV_CHARGE_KEY FROM BAPI_RE_SETTL_UNIT_KEY INTO @DATA(ld_servchargekey). | ||||
| "SELECT single SETTLEMENT_UNIT FROM BAPI_RE_SETTL_UNIT_KEY INTO @DATA(ld_settlementunitnumber). | ||||
| "SELECT single DETAIL_VALID_FROM FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_from). | ||||
| "SELECT single DETAIL_VALID_TO FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_to). | ||||
Search for further information about these or an SAP related objects