SAP BAPI_EQMT_DISMANTLEHR Function Module for Dismantle equipment from equipment hierarchy
BAPI_EQMT_DISMANTLEHR is a standard bapi eqmt dismantlehr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dismantle equipment from equipment hierarchy 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 eqmt dismantlehr FM, simply by entering the name BAPI_EQMT_DISMANTLEHR into the relevant SAP transaction such as SE37 or SE38.
Function Group: IWWW
Program Name: SAPLIWWW
Main Program: SAPLIWWW
Appliation area: I
Release date: 05-Nov-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_EQMT_DISMANTLEHR 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_EQMT_DISMANTLEHR'"Dismantle equipment from equipment hierarchy.
EXPORTING
EQUIPMENT = "Number of equipment to be dismantled
* SUPEREQUI = "Number of dismantling location (Equipment)
* DATE = SY-DATLO "Date of dismantling
* TIME = SY-TIMLO "Time of dismantling
IMPORTING
EQUIMASTER = "Structure for equipment EQUI data
EQUITIME = "Structure for equipment EQUZ data
EQUITEXT = "Structure for equipment EQKT data
EQUILOCATION = "Structure for equipment ILOA data
EQUISALES = "Structure for equipment sales data
EQUIHIERARCHY = "Structure for equipment hierarchy data
RETURN = "Structure for Return Parameters (Code, Text)
IMPORTING Parameters details for BAPI_EQMT_DISMANTLEHR
EQUIPMENT - Number of equipment to be dismantled
Data type: BAPI_EQUI-EQUIPMENTOptional: No
Call by Reference: No ( called with pass by value option)
SUPEREQUI - Number of dismantling location (Equipment)
Data type: BAPI_EQHR-SUPEREQUIOptional: Yes
Call by Reference: No ( called with pass by value option)
DATE - Date of dismantling
Data type: BAPI_EQPRM-DISM_DATEDefault: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)
TIME - Time of dismantling
Data type: BAPI_EQPRM-DISM_TIMEDefault: SY-TIMLO
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_EQMT_DISMANTLEHR
EQUIMASTER - Structure for equipment EQUI data
Data type: BAPI_EQUIOptional: No
Call by Reference: No ( called with pass by value option)
EQUITIME - Structure for equipment EQUZ data
Data type: BAPI_EQUZOptional: No
Call by Reference: No ( called with pass by value option)
EQUITEXT - Structure for equipment EQKT data
Data type: BAPI_EQKTOptional: No
Call by Reference: No ( called with pass by value option)
EQUILOCATION - Structure for equipment ILOA data
Data type: BAPI_ILOAOptional: No
Call by Reference: No ( called with pass by value option)
EQUISALES - Structure for equipment sales data
Data type: BAPI_EQSDOptional: No
Call by Reference: No ( called with pass by value option)
EQUIHIERARCHY - Structure for equipment hierarchy data
Data type: BAPI_EQHROptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Structure for Return Parameters (Code, Text)
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_EQMT_DISMANTLEHR 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_equipment | TYPE BAPI_EQUI-EQUIPMENT, " | |||
| lv_equimaster | TYPE BAPI_EQUI, " | |||
| lv_equitime | TYPE BAPI_EQUZ, " | |||
| lv_superequi | TYPE BAPI_EQHR-SUPEREQUI, " | |||
| lv_date | TYPE BAPI_EQPRM-DISM_DATE, " SY-DATLO | |||
| lv_equitext | TYPE BAPI_EQKT, " | |||
| lv_time | TYPE BAPI_EQPRM-DISM_TIME, " SY-TIMLO | |||
| lv_equilocation | TYPE BAPI_ILOA, " | |||
| lv_equisales | TYPE BAPI_EQSD, " | |||
| lv_equihierarchy | TYPE BAPI_EQHR, " | |||
| lv_return | TYPE BAPIRETURN. " |
|   CALL FUNCTION 'BAPI_EQMT_DISMANTLEHR' "Dismantle equipment from equipment hierarchy |
| EXPORTING | ||
| EQUIPMENT | = lv_equipment | |
| SUPEREQUI | = lv_superequi | |
| DATE | = lv_date | |
| TIME | = lv_time | |
| IMPORTING | ||
| EQUIMASTER | = lv_equimaster | |
| EQUITIME | = lv_equitime | |
| EQUITEXT | = lv_equitext | |
| EQUILOCATION | = lv_equilocation | |
| EQUISALES | = lv_equisales | |
| EQUIHIERARCHY | = lv_equihierarchy | |
| RETURN | = lv_return | |
| . " BAPI_EQMT_DISMANTLEHR | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_EQMT_DISMANTLEHR
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 EQUIPMENT FROM BAPI_EQUI INTO @DATA(ld_equipment). | ||||
| "SELECT single SUPEREQUI FROM BAPI_EQHR INTO @DATA(ld_superequi). | ||||
| "SELECT single DISM_DATE FROM BAPI_EQPRM INTO @DATA(ld_date). | ||||
| DATA(ld_date) | = SY-DATLO. | |||
| "SELECT single DISM_TIME FROM BAPI_EQPRM INTO @DATA(ld_time). | ||||
| DATA(ld_time) | = SY-TIMLO. | |||
Search for further information about these or an SAP related objects