SAP BAPI_RE_BE_GET_DETAIL Function Module for Return Business Entity Data









BAPI_RE_BE_GET_DETAIL is a standard bapi re be 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 Business Entity 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 be get detail FM, simply by entering the name BAPI_RE_BE_GET_DETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: REBD_BAPI_BUS_ENTITY
Program Name: SAPLREBD_BAPI_BUS_ENTITY
Main Program: SAPLREBD_BAPI_BUS_ENTITY
Appliation area:
Release date: 19-Aug-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_RE_BE_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_BE_GET_DETAIL'"Return Business Entity Data
  EXPORTING
   COMPCODE =  "Company Code
   BUSINESSENTITYNUMBER =  "Number of Business Entity
*  DETAIL_DATA_FROM = RECA0_DATE-MIN "Date: Detailed Data Valid From
*  DETAIL_DATA_TO = RECA0_DATE-MAX "Date: Detailed Data Valid To

 IMPORTING
   BUS_ENTITY =  "Business Entity
   OBJECT_ADDRESS =  "Address
   COSETTLE_PARAM =  "CO Settlement Rule: Parameter

TABLES
*  TERM_ORG_ASSIGNMENT =  "Org. Assignment
*  ARCH_RELMS =  "Architectural Linkage Object Parts
*  STATUS =  "Status
*  EXTENSION_OUT =  "Data of User Fields
*  RETURN =  "Return Parameters
*  INFRASTRUCTURE =  "Infrastructure
*  MEASUREMENT =  "Measurements
*  PARTNER =  "Partner
*  OPTION_RATE =  "Option Rates
*  COSETTLE_RULE =  "CO Settlement Rule: Allocation Rules
*  OBJ_ASSIGN =  "Object Assignment
*  RESUBM_RULE =  "Reminder Rule
*  RESUBM_DATE =  "Reminder Date
*  ARCH_REL =  "Architectural Linkage Objects
.



IMPORTING Parameters details for BAPI_RE_BE_GET_DETAIL

COMPCODE - Company Code

Data type: BAPI_RE_BUS_ENTITY_KEY-COMP_CODE
Optional: No
Call by Reference: No ( called with pass by value option)

BUSINESSENTITYNUMBER - Number of Business Entity

Data type: BAPI_RE_BUS_ENTITY_KEY-BUSINESS_ENTITY
Optional: 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_FROM
Default: RECA0_DATE-MIN
Optional: No
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_TO
Default: RECA0_DATE-MAX
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_RE_BE_GET_DETAIL

BUS_ENTITY - Business Entity

Data type: BAPI_RE_BUS_ENTITY
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_ADDRESS - Address

Data type: BAPI_RE_OBJ_ADDRESS
Optional: No
Call by Reference: No ( called with pass by value option)

COSETTLE_PARAM - CO Settlement Rule: Parameter

Data type: BAPI_RE_COSETTLE_PAR
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_RE_BE_GET_DETAIL

TERM_ORG_ASSIGNMENT - Org. Assignment

Data type: BAPI_RE_TERM_OA
Optional: Yes
Call by Reference: Yes

ARCH_RELMS - Architectural Linkage Object Parts

Data type: BAPI_RE_ARCH_RELMS
Optional: Yes
Call by Reference: Yes

STATUS - Status

Data type: BAPI_RE_STATUS
Optional: Yes
Call by Reference: Yes

EXTENSION_OUT - Data of User Fields

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameters

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

INFRASTRUCTURE - Infrastructure

Data type: BAPI_RE_INFRA
Optional: Yes
Call by Reference: Yes

MEASUREMENT - Measurements

Data type: BAPI_RE_MEASUREMENT
Optional: Yes
Call by Reference: Yes

PARTNER - Partner

Data type: BAPI_RE_PARTNER
Optional: Yes
Call by Reference: Yes

OPTION_RATE - Option Rates

Data type: BAPI_RE_OPTION_RATE
Optional: Yes
Call by Reference: Yes

COSETTLE_RULE - CO Settlement Rule: Allocation Rules

Data type: BAPI_RE_COSETTLE_RL
Optional: Yes
Call by Reference: Yes

OBJ_ASSIGN - Object Assignment

Data type: BAPI_RE_OBJ_ASSIGN
Optional: Yes
Call by Reference: Yes

RESUBM_RULE - Reminder Rule

Data type: BAPI_RE_RESUBM_RULE
Optional: Yes
Call by Reference: Yes

RESUBM_DATE - Reminder Date

Data type: BAPI_RE_RESUBM_DATE
Optional: Yes
Call by Reference: Yes

ARCH_REL - Architectural Linkage Objects

Data type: BAPI_RE_ARCH_REL
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_RE_BE_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_BUS_ENTITY_KEY-COMP_CODE, "   
lv_bus_entity  TYPE BAPI_RE_BUS_ENTITY, "   
lt_term_org_assignment  TYPE STANDARD TABLE OF BAPI_RE_TERM_OA, "   
lt_arch_relms  TYPE STANDARD TABLE OF BAPI_RE_ARCH_RELMS, "   
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_infrastructure  TYPE STANDARD TABLE OF BAPI_RE_INFRA, "   
lt_measurement  TYPE STANDARD TABLE OF BAPI_RE_MEASUREMENT, "   
lv_object_address  TYPE BAPI_RE_OBJ_ADDRESS, "   
lv_businessentitynumber  TYPE BAPI_RE_BUS_ENTITY_KEY-BUSINESS_ENTITY, "   
lt_partner  TYPE STANDARD TABLE OF BAPI_RE_PARTNER, "   
lv_cosettle_param  TYPE BAPI_RE_COSETTLE_PAR, "   
lv_detail_data_from  TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROM, "   RECA0_DATE-MIN
lt_option_rate  TYPE STANDARD TABLE OF BAPI_RE_OPTION_RATE, "   
lv_detail_data_to  TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TO, "   RECA0_DATE-MAX
lt_cosettle_rule  TYPE STANDARD TABLE OF BAPI_RE_COSETTLE_RL, "   
lt_obj_assign  TYPE STANDARD TABLE OF BAPI_RE_OBJ_ASSIGN, "   
lt_resubm_rule  TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE, "   
lt_resubm_date  TYPE STANDARD TABLE OF BAPI_RE_RESUBM_DATE, "   
lt_arch_rel  TYPE STANDARD TABLE OF BAPI_RE_ARCH_REL. "   

  CALL FUNCTION 'BAPI_RE_BE_GET_DETAIL'  "Return Business Entity Data
    EXPORTING
         COMPCODE = lv_compcode
         BUSINESSENTITYNUMBER = lv_businessentitynumber
         DETAIL_DATA_FROM = lv_detail_data_from
         DETAIL_DATA_TO = lv_detail_data_to
    IMPORTING
         BUS_ENTITY = lv_bus_entity
         OBJECT_ADDRESS = lv_object_address
         COSETTLE_PARAM = lv_cosettle_param
    TABLES
         TERM_ORG_ASSIGNMENT = lt_term_org_assignment
         ARCH_RELMS = lt_arch_relms
         STATUS = lt_status
         EXTENSION_OUT = lt_extension_out
         RETURN = lt_return
         INFRASTRUCTURE = lt_infrastructure
         MEASUREMENT = lt_measurement
         PARTNER = lt_partner
         OPTION_RATE = lt_option_rate
         COSETTLE_RULE = lt_cosettle_rule
         OBJ_ASSIGN = lt_obj_assign
         RESUBM_RULE = lt_resubm_rule
         RESUBM_DATE = lt_resubm_date
         ARCH_REL = lt_arch_rel
. " BAPI_RE_BE_GET_DETAIL




ABAP code using 7.40 inline data declarations to call FM BAPI_RE_BE_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_BUS_ENTITY_KEY INTO @DATA(ld_compcode).
 
 
 
 
 
 
 
 
 
 
"SELECT single BUSINESS_ENTITY FROM BAPI_RE_BUS_ENTITY_KEY INTO @DATA(ld_businessentitynumber).
 
 
 
"SELECT single DETAIL_VALID_FROM FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_from).
DATA(ld_detail_data_from) = RECA0_DATE-MIN.
 
 
"SELECT single DETAIL_VALID_TO FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_to).
DATA(ld_detail_data_to) = RECA0_DATE-MAX.
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!