SAP CBIF_PMTO_EQUIPMENT_READ Function Module for NOTRANSL: EHS-INT: Lesen von Equipment Stammdaten und Kurztext zu Equipmen









CBIF_PMTO_EQUIPMENT_READ is a standard cbif pmto equipment read 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: EHS-INT: Lesen von Equipment Stammdaten und Kurztext zu Equipmen 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 cbif pmto equipment read FM, simply by entering the name CBIF_PMTO_EQUIPMENT_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: CBIF_PMTO
Program Name: SAPLCBIF_PMTO
Main Program: SAPLCBIF_PMTO
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CBIF_PMTO_EQUIPMENT_READ 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 'CBIF_PMTO_EQUIPMENT_READ'"NOTRANSL: EHS-INT: Lesen von Equipment Stammdaten und Kurztext zu Equipmen
EXPORTING
I_PM_EQUI_NO = "Equipment Number
* I_PM_READING_DATE = '99991231' "

IMPORTING
E_PM_EQKT = "
E_PM_EQUI = "
E_FLG_NO_AUTHORITY = "Missing Authorizations
E_FLG_NOT_FOUND = "Data Not Found
E_EXCEPTION_CODE = "

TABLES
* X_PARAMVAL_TAB = "Parameter Values

EXCEPTIONS
MISSING_PARAMETER = 1 PM_METHOD_ERROR = 2 PM_INTERNAL_ERROR = 3 PM_RELEASE_ERROR = 4
.



IMPORTING Parameters details for CBIF_PMTO_EQUIPMENT_READ

I_PM_EQUI_NO - Equipment Number

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

I_PM_READING_DATE -

Data type: EQUZ-DATBI
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CBIF_PMTO_EQUIPMENT_READ

E_PM_EQKT -

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

E_PM_EQUI -

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

E_FLG_NO_AUTHORITY - Missing Authorizations

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

E_FLG_NOT_FOUND - Data Not Found

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

E_EXCEPTION_CODE -

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

TABLES Parameters details for CBIF_PMTO_EQUIPMENT_READ

X_PARAMVAL_TAB - Parameter Values

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

EXCEPTIONS details

MISSING_PARAMETER - Missing Input Parameters

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

PM_METHOD_ERROR -

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

PM_INTERNAL_ERROR -

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

PM_RELEASE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CBIF_PMTO_EQUIPMENT_READ 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_e_pm_eqkt  TYPE EQKT, "   
lv_i_pm_equi_no  TYPE EQUI-EQUNR, "   
lt_x_paramval_tab  TYPE STANDARD TABLE OF CCIFS_PARAMVAL, "   
lv_missing_parameter  TYPE CCIFS_PARAMVAL, "   
lv_e_pm_equi  TYPE EQUI, "   
lv_pm_method_error  TYPE EQUI, "   
lv_i_pm_reading_date  TYPE EQUZ-DATBI, "   '99991231'
lv_pm_internal_error  TYPE EQUZ, "   
lv_e_flg_no_authority  TYPE BOOLE-BOOLE, "   
lv_e_flg_not_found  TYPE BOOLE-BOOLE, "   
lv_pm_release_error  TYPE BOOLE, "   
lv_e_exception_code  TYPE I. "   

  CALL FUNCTION 'CBIF_PMTO_EQUIPMENT_READ'  "NOTRANSL: EHS-INT: Lesen von Equipment Stammdaten und Kurztext zu Equipmen
    EXPORTING
         I_PM_EQUI_NO = lv_i_pm_equi_no
         I_PM_READING_DATE = lv_i_pm_reading_date
    IMPORTING
         E_PM_EQKT = lv_e_pm_eqkt
         E_PM_EQUI = lv_e_pm_equi
         E_FLG_NO_AUTHORITY = lv_e_flg_no_authority
         E_FLG_NOT_FOUND = lv_e_flg_not_found
         E_EXCEPTION_CODE = lv_e_exception_code
    TABLES
         X_PARAMVAL_TAB = lt_x_paramval_tab
    EXCEPTIONS
        MISSING_PARAMETER = 1
        PM_METHOD_ERROR = 2
        PM_INTERNAL_ERROR = 3
        PM_RELEASE_ERROR = 4
. " CBIF_PMTO_EQUIPMENT_READ




ABAP code using 7.40 inline data declarations to call FM CBIF_PMTO_EQUIPMENT_READ

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 EQUNR FROM EQUI INTO @DATA(ld_i_pm_equi_no).
 
 
 
 
 
"SELECT single DATBI FROM EQUZ INTO @DATA(ld_i_pm_reading_date).
DATA(ld_i_pm_reading_date) = '99991231'.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_flg_no_authority).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_flg_not_found).
 
 
 


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!