SAP BAPI_ECMREQ_GET_DETAIL Function Module for Read Engineering Change Request









BAPI_ECMREQ_GET_DETAIL is a standard bapi ecmreq 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 Read Engineering Change Request 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 ecmreq get detail FM, simply by entering the name BAPI_ECMREQ_GET_DETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: ECM_BAPI_REQUEST
Program Name: SAPLECM_BAPI_REQUEST
Main Program:
Appliation area:
Release date: 20-Nov-2002
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_ECMREQ_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_ECMREQ_GET_DETAIL'"Read Engineering Change Request
  EXPORTING
   REQUEST =  "Engineering Change Request
*  LANGUAGE = SY-LANGU "Language Key from SAP Logon
*  LANGUAGE_ISO =  "Language According to ISO 639

 IMPORTING
   ES_DETAILS =  "Engineering Change Request: Basic Data

TABLES
*  ET_DESCRIPTIONS =  "Engineering Change Request: Descriptions
*  ET_STATUS =  "Engineering Change Management: BAPI Structure for Status
*  ET_HIERARCHY =  "Engineering Change Request: Hierarchy
*  RETURN =  "Return Parameters
.



IMPORTING Parameters details for BAPI_ECMREQ_GET_DETAIL

REQUEST - Engineering Change Request

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

LANGUAGE - Language Key from SAP Logon

Data type: BAPI_ECMREQ_FIELDS-LANGUAGE
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE_ISO - Language According to ISO 639

Data type: BAPI_ECMREQ_FIELDS-LANGUAGE_ISO
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_ECMREQ_GET_DETAIL

ES_DETAILS - Engineering Change Request: Basic Data

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

TABLES Parameters details for BAPI_ECMREQ_GET_DETAIL

ET_DESCRIPTIONS - Engineering Change Request: Descriptions

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

ET_STATUS - Engineering Change Management: BAPI Structure for Status

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

ET_HIERARCHY - Engineering Change Request: Hierarchy

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

RETURN - Return Parameters

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

Copy and paste ABAP code example for BAPI_ECMREQ_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_request  TYPE BAPI_ECMREQ_FIELDS-REQUEST, "   
lv_es_details  TYPE BAPI_ECMREQ_DETAIL, "   
lt_et_descriptions  TYPE STANDARD TABLE OF BAPI_ECMREQ_DESCR, "   
lv_language  TYPE BAPI_ECMREQ_FIELDS-LANGUAGE, "   SY-LANGU
lt_et_status  TYPE STANDARD TABLE OF BAPI_ECM_STATUS, "   
lt_et_hierarchy  TYPE STANDARD TABLE OF BAPI_ECMREQ_HIERAR, "   
lv_language_iso  TYPE BAPI_ECMREQ_FIELDS-LANGUAGE_ISO, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_ECMREQ_GET_DETAIL'  "Read Engineering Change Request
    EXPORTING
         REQUEST = lv_request
         LANGUAGE = lv_language
         LANGUAGE_ISO = lv_language_iso
    IMPORTING
         ES_DETAILS = lv_es_details
    TABLES
         ET_DESCRIPTIONS = lt_et_descriptions
         ET_STATUS = lt_et_status
         ET_HIERARCHY = lt_et_hierarchy
         RETURN = lt_return
. " BAPI_ECMREQ_GET_DETAIL




ABAP code using 7.40 inline data declarations to call FM BAPI_ECMREQ_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 REQUEST FROM BAPI_ECMREQ_FIELDS INTO @DATA(ld_request).
 
 
 
"SELECT single LANGUAGE FROM BAPI_ECMREQ_FIELDS INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
 
"SELECT single LANGUAGE_ISO FROM BAPI_ECMREQ_FIELDS INTO @DATA(ld_language_iso).
 
 


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!