SAP BAPI_EQUI_CREATE Function Module for PM BAPI: Create Equipment
BAPI_EQUI_CREATE is a standard bapi equi create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PM BAPI: Create Equipment 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 equi create FM, simply by entering the name BAPI_EQUI_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ITOB_BAPI_EQ
Program Name: SAPLITOB_BAPI_EQ
Main Program: SAPLITOB_BAPI_EQ
Appliation area:
Release date: 23-Dec-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_EQUI_CREATE 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_EQUI_CREATE'"PM BAPI: Create Equipment.
EXPORTING
* EXTERNAL_NUMBER = "Number of Equipment to be Created (Initial => Internal Assignment)
DATA_GENERAL = "General Data for Technical Objects
DATA_SPECIFIC = "Equipment-Specific data
* DATA_FLEET = "Vehicle-Specific Data
* VALID_DATE = SY-DATUM "Valid-From Date for Equipment to be Created
* DATA_INSTALL = "Installation Date for Equipment
IMPORTING
EQUIPMENT = "Number of Equipment Created
DATA_GENERAL_EXP = "General Data for Technical Objects
DATA_SPECIFIC_EXP = "Equipment-Specific data
DATA_FLEET_EXP = "Vehicle-Specific Data
RETURN = "Return Parameter
IMPORTING Parameters details for BAPI_EQUI_CREATE
EXTERNAL_NUMBER - Number of Equipment to be Created (Initial => Internal Assignment)
Data type: BAPI_ITOB_PARMS-EQUIPMENTOptional: Yes
Call by Reference: No ( called with pass by value option)
DATA_GENERAL - General Data for Technical Objects
Data type: BAPI_ITOBOptional: No
Call by Reference: No ( called with pass by value option)
DATA_SPECIFIC - Equipment-Specific data
Data type: BAPI_ITOB_EQ_ONLYOptional: No
Call by Reference: No ( called with pass by value option)
DATA_FLEET - Vehicle-Specific Data
Data type: BAPI_FLEETOptional: Yes
Call by Reference: No ( called with pass by value option)
VALID_DATE - Valid-From Date for Equipment to be Created
Data type: BAPI_ITOB_PARMS-INST_DATEDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
DATA_INSTALL - Installation Date for Equipment
Data type: BAPI_ITOB_EQ_INSTALLOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_EQUI_CREATE
EQUIPMENT - Number of Equipment Created
Data type: BAPI_ITOB_PARMS-EQUIPMENTOptional: No
Call by Reference: No ( called with pass by value option)
DATA_GENERAL_EXP - General Data for Technical Objects
Data type: BAPI_ITOBOptional: No
Call by Reference: No ( called with pass by value option)
DATA_SPECIFIC_EXP - Equipment-Specific data
Data type: BAPI_ITOB_EQ_ONLYOptional: No
Call by Reference: No ( called with pass by value option)
DATA_FLEET_EXP - Vehicle-Specific Data
Data type: BAPI_FLEETOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_EQUI_CREATE 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_ITOB_PARMS-EQUIPMENT, " | |||
lv_external_number | TYPE BAPI_ITOB_PARMS-EQUIPMENT, " | |||
lv_data_general | TYPE BAPI_ITOB, " | |||
lv_data_general_exp | TYPE BAPI_ITOB, " | |||
lv_data_specific | TYPE BAPI_ITOB_EQ_ONLY, " | |||
lv_data_specific_exp | TYPE BAPI_ITOB_EQ_ONLY, " | |||
lv_data_fleet | TYPE BAPI_FLEET, " | |||
lv_data_fleet_exp | TYPE BAPI_FLEET, " | |||
lv_return | TYPE BAPIRET2, " | |||
lv_valid_date | TYPE BAPI_ITOB_PARMS-INST_DATE, " SY-DATUM | |||
lv_data_install | TYPE BAPI_ITOB_EQ_INSTALL. " |
  CALL FUNCTION 'BAPI_EQUI_CREATE' "PM BAPI: Create Equipment |
EXPORTING | ||
EXTERNAL_NUMBER | = lv_external_number | |
DATA_GENERAL | = lv_data_general | |
DATA_SPECIFIC | = lv_data_specific | |
DATA_FLEET | = lv_data_fleet | |
VALID_DATE | = lv_valid_date | |
DATA_INSTALL | = lv_data_install | |
IMPORTING | ||
EQUIPMENT | = lv_equipment | |
DATA_GENERAL_EXP | = lv_data_general_exp | |
DATA_SPECIFIC_EXP | = lv_data_specific_exp | |
DATA_FLEET_EXP | = lv_data_fleet_exp | |
RETURN | = lv_return | |
. " BAPI_EQUI_CREATE |
ABAP code using 7.40 inline data declarations to call FM BAPI_EQUI_CREATE
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_ITOB_PARMS INTO @DATA(ld_equipment). | ||||
"SELECT single EQUIPMENT FROM BAPI_ITOB_PARMS INTO @DATA(ld_external_number). | ||||
"SELECT single INST_DATE FROM BAPI_ITOB_PARMS INTO @DATA(ld_valid_date). | ||||
DATA(ld_valid_date) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects