SAP OPEN_FI_PERFORM_EQ_BBAPI_E_OS Function Module for NOTRANSL: Ausführen des BusinessTransactionEvent EQ_BBAPI









OPEN_FI_PERFORM_EQ_BBAPI_E_OS is a standard open fi perform eq bbapi e os SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ausführen des BusinessTransactionEvent EQ_BBAPI 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 open fi perform eq bbapi e os FM, simply by entering the name OPEN_FI_PERFORM_EQ_BBAPI_E_OS into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM_EQUIPMENT_APPLI_OS
Program Name: SAPLCRM_EQUIPMENT_APPLI_OS
Main Program: SAPLCRM_EQUIPMENT_APPLI_OS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function OPEN_FI_PERFORM_EQ_BBAPI_E_OS 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 'OPEN_FI_PERFORM_EQ_BBAPI_E_OS'"NOTRANSL: Ausführen des BusinessTransactionEvent EQ_BBAPI
 IMPORTING
   EV_ABORT =  "Generic Type

TABLES
   IT_BAPIMTCS =  "Middleware Transaction Container Structure
   CT_BAPI_IHPA =  "Plant Maintenance: Partners
   CT_BAPISTXTXH =  "BAPI CRS Structure for STXH (SAPscript Text)
   CT_BAPISTXTXL =  "BAPI Structure for STX_LINES Structure
   CT_BAPICUSADR =  "BAPI Structure: Customer Address
   CT_BAPICUSTEL =  "BAPI Structure: Telephone (Business Address Services)
   CT_BAPICUSFAX =  "BAPI Structure: Fax Numbers (Business Address Services)
   CT_BAPISMJEST =  "BAPI Structure for Table Jest Mobile Service
   CT_BAPISMJSTO =  "BAPI Structure Table Jsto Mobile Service
   CT_BAPICUCFGV_EQ =  "Configuration Header data - Equipment/Serial number
   CT_BAPICUINSV_EQ =  "Configuration instances - Equipment/Serial number
   CT_BAPI_EQUIMAP =  "Mapping Equipment No. <-> iObject GUID
   CT_BAPICUVALV_EQ =  "Configuration Values - Equipment/Serial number
   ET_BAPIRET2 =  "Return Parameter
   CT_BAPI_EQUI =  "Equipment Master Data
   CT_BAPI_EQUIX =  "Transfer Structure for Equipment Master Data
   CT_BAPI_EQUZ =  "Equipment Time Segment
   CT_BAPI_EQUZX =  "Transfer Structure for Equipment Usage Period
   CT_BAPI_EQST =  "Equipment to BOM Link
   CT_BAPI_EQKT =  "Equipment Short Texts
   CT_BAPI_ILOA =  "BAPI Structure for ILOA Data of an Equipment to be Created
.



EXPORTING Parameters details for OPEN_FI_PERFORM_EQ_BBAPI_E_OS

EV_ABORT - Generic Type

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

TABLES Parameters details for OPEN_FI_PERFORM_EQ_BBAPI_E_OS

IT_BAPIMTCS - Middleware Transaction Container Structure

Data type: BAPIMTCS
Optional: No
Call by Reference: Yes

CT_BAPI_IHPA - Plant Maintenance: Partners

Data type: BAPI_IHPA
Optional: No
Call by Reference: Yes

CT_BAPISTXTXH - BAPI CRS Structure for STXH (SAPscript Text)

Data type: BAPISTXTXH
Optional: No
Call by Reference: Yes

CT_BAPISTXTXL - BAPI Structure for STX_LINES Structure

Data type: BAPISTXTXL
Optional: No
Call by Reference: Yes

CT_BAPICUSADR - BAPI Structure: Customer Address

Data type: BAPICUSADR
Optional: No
Call by Reference: Yes

CT_BAPICUSTEL - BAPI Structure: Telephone (Business Address Services)

Data type: BAPICUSTEL
Optional: No
Call by Reference: Yes

CT_BAPICUSFAX - BAPI Structure: Fax Numbers (Business Address Services)

Data type: BAPICUSFAX
Optional: No
Call by Reference: Yes

CT_BAPISMJEST - BAPI Structure for Table Jest Mobile Service

Data type: BAPISMJEST
Optional: No
Call by Reference: Yes

CT_BAPISMJSTO - BAPI Structure Table Jsto Mobile Service

Data type: BAPISMJSTO
Optional: No
Call by Reference: Yes

CT_BAPICUCFGV_EQ - Configuration Header data - Equipment/Serial number

Data type: BAPICUCFGV_EQ
Optional: No
Call by Reference: Yes

CT_BAPICUINSV_EQ - Configuration instances - Equipment/Serial number

Data type: BAPICUINSV_EQ
Optional: No
Call by Reference: Yes

CT_BAPI_EQUIMAP - Mapping Equipment No. <-> iObject GUID

Data type: BAPI_EQUIMAP_R3_OS
Optional: No
Call by Reference: Yes

CT_BAPICUVALV_EQ - Configuration Values - Equipment/Serial number

Data type: BAPICUVALV_EQ
Optional: No
Call by Reference: Yes

ET_BAPIRET2 - Return Parameter

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

CT_BAPI_EQUI - Equipment Master Data

Data type: BAPI_EQUI1
Optional: No
Call by Reference: Yes

CT_BAPI_EQUIX - Transfer Structure for Equipment Master Data

Data type: BAPI_EQUIX_R3_OS
Optional: No
Call by Reference: Yes

CT_BAPI_EQUZ - Equipment Time Segment

Data type: BAPI_EQUZ1
Optional: No
Call by Reference: Yes

CT_BAPI_EQUZX - Transfer Structure for Equipment Usage Period

Data type: BAPI_EQUZX_R3_OS
Optional: No
Call by Reference: Yes

CT_BAPI_EQST - Equipment to BOM Link

Data type: BAPI_EQST1
Optional: No
Call by Reference: Yes

CT_BAPI_EQKT - Equipment Short Texts

Data type: BAPI_EQKT1
Optional: No
Call by Reference: Yes

CT_BAPI_ILOA - BAPI Structure for ILOA Data of an Equipment to be Created

Data type: BAPI_ILOA
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OPEN_FI_PERFORM_EQ_BBAPI_E_OS 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_ev_abort  TYPE C, "   
lt_it_bapimtcs  TYPE STANDARD TABLE OF BAPIMTCS, "   
lt_ct_bapi_ihpa  TYPE STANDARD TABLE OF BAPI_IHPA, "   
lt_ct_bapistxtxh  TYPE STANDARD TABLE OF BAPISTXTXH, "   
lt_ct_bapistxtxl  TYPE STANDARD TABLE OF BAPISTXTXL, "   
lt_ct_bapicusadr  TYPE STANDARD TABLE OF BAPICUSADR, "   
lt_ct_bapicustel  TYPE STANDARD TABLE OF BAPICUSTEL, "   
lt_ct_bapicusfax  TYPE STANDARD TABLE OF BAPICUSFAX, "   
lt_ct_bapismjest  TYPE STANDARD TABLE OF BAPISMJEST, "   
lt_ct_bapismjsto  TYPE STANDARD TABLE OF BAPISMJSTO, "   
lt_ct_bapicucfgv_eq  TYPE STANDARD TABLE OF BAPICUCFGV_EQ, "   
lt_ct_bapicuinsv_eq  TYPE STANDARD TABLE OF BAPICUINSV_EQ, "   
lt_ct_bapi_equimap  TYPE STANDARD TABLE OF BAPI_EQUIMAP_R3_OS, "   
lt_ct_bapicuvalv_eq  TYPE STANDARD TABLE OF BAPICUVALV_EQ, "   
lt_et_bapiret2  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_ct_bapi_equi  TYPE STANDARD TABLE OF BAPI_EQUI1, "   
lt_ct_bapi_equix  TYPE STANDARD TABLE OF BAPI_EQUIX_R3_OS, "   
lt_ct_bapi_equz  TYPE STANDARD TABLE OF BAPI_EQUZ1, "   
lt_ct_bapi_equzx  TYPE STANDARD TABLE OF BAPI_EQUZX_R3_OS, "   
lt_ct_bapi_eqst  TYPE STANDARD TABLE OF BAPI_EQST1, "   
lt_ct_bapi_eqkt  TYPE STANDARD TABLE OF BAPI_EQKT1, "   
lt_ct_bapi_iloa  TYPE STANDARD TABLE OF BAPI_ILOA. "   

  CALL FUNCTION 'OPEN_FI_PERFORM_EQ_BBAPI_E_OS'  "NOTRANSL: Ausführen des BusinessTransactionEvent EQ_BBAPI
    IMPORTING
         EV_ABORT = lv_ev_abort
    TABLES
         IT_BAPIMTCS = lt_it_bapimtcs
         CT_BAPI_IHPA = lt_ct_bapi_ihpa
         CT_BAPISTXTXH = lt_ct_bapistxtxh
         CT_BAPISTXTXL = lt_ct_bapistxtxl
         CT_BAPICUSADR = lt_ct_bapicusadr
         CT_BAPICUSTEL = lt_ct_bapicustel
         CT_BAPICUSFAX = lt_ct_bapicusfax
         CT_BAPISMJEST = lt_ct_bapismjest
         CT_BAPISMJSTO = lt_ct_bapismjsto
         CT_BAPICUCFGV_EQ = lt_ct_bapicucfgv_eq
         CT_BAPICUINSV_EQ = lt_ct_bapicuinsv_eq
         CT_BAPI_EQUIMAP = lt_ct_bapi_equimap
         CT_BAPICUVALV_EQ = lt_ct_bapicuvalt_eq
         ET_BAPIRET2 = lt_et_bapiret2
         CT_BAPI_EQUI = lt_ct_bapi_equi
         CT_BAPI_EQUIX = lt_ct_bapi_equix
         CT_BAPI_EQUZ = lt_ct_bapi_equz
         CT_BAPI_EQUZX = lt_ct_bapi_equzx
         CT_BAPI_EQST = lt_ct_bapi_eqst
         CT_BAPI_EQKT = lt_ct_bapi_eqkt
         CT_BAPI_ILOA = lt_ct_bapi_iloa
. " OPEN_FI_PERFORM_EQ_BBAPI_E_OS




ABAP code using 7.40 inline data declarations to call FM OPEN_FI_PERFORM_EQ_BBAPI_E_OS

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!