SAP EQUIPMENT_READ_DISPLAY Function Module for NOTRANSL: Equipment lesen mit Zeitsegmentliste









EQUIPMENT_READ_DISPLAY is a standard equipment read display 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: Equipment lesen mit Zeitsegmentliste 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 equipment read display FM, simply by entering the name EQUIPMENT_READ_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

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



Function EQUIPMENT_READ_DISPLAY 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 'EQUIPMENT_READ_DISPLAY'"NOTRANSL: Equipment lesen mit Zeitsegmentliste
EXPORTING
* CHECK_AUTH = ' ' "
* IV_REFRESH_BUFFER = "
* EQUI_NO = "Equipment number
* EQUZ_ANZ = 1 "
* LISTE = ' ' "
READING_DATE = "Date is valid to
* TIME = '0' "
* HIST = "
* NO_EQUZ_SELECTION = ' ' "
* IV_UII = ' ' "Unique Item Identifier (CHAR72)

IMPORTING
EQKT = "
EQUI = "Structure equipment
EQUZ = "Structure time segment
ILOA = "

EXCEPTIONS
AUTH_NO_BEGRP = 1 AUTH_NO_BADI = 10 AUTH_NO_IWERK = 2 AUTH_NO_SWERK = 3 EQKT_NOT_FOUND = 4 EQUI_NOT_FOUND = 5 EQUZ_NOT_FOUND = 6 ILOA_NOT_FOUND = 7 AUTH_NO_INGRP = 8 AUTH_NO_KOSTL = 9
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLIE01_005 Serial Numbers, User Exit in the Update
EXIT_SAPLIE01_007 Serial Numbers, User Exit in Goods Movement

IMPORTING Parameters details for EQUIPMENT_READ_DISPLAY

CHECK_AUTH -

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

IV_REFRESH_BUFFER -

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

EQUI_NO - Equipment number

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

EQUZ_ANZ -

Data type: EQUZ-EQLFN
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

LISTE -

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

READING_DATE - Date is valid to

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

TIME -

Data type: SY-UZEIT
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

HIST -

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

NO_EQUZ_SELECTION -

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

IV_UII - Unique Item Identifier (CHAR72)

Data type: EQUI-UII
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for EQUIPMENT_READ_DISPLAY

EQKT -

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

EQUI - Structure equipment

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

EQUZ - Structure time segment

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

ILOA -

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

EXCEPTIONS details

AUTH_NO_BEGRP -

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

AUTH_NO_BADI -

Data type:
Optional: No
Call by Reference: Yes

AUTH_NO_IWERK -

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

AUTH_NO_SWERK -

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

EQKT_NOT_FOUND -

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

EQUI_NOT_FOUND - Equipment is not found

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

EQUZ_NOT_FOUND - Time segment is not found

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

ILOA_NOT_FOUND -

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

AUTH_NO_INGRP -

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

AUTH_NO_KOSTL -

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

Copy and paste ABAP code example for EQUIPMENT_READ_DISPLAY 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_eqkt  TYPE EQKT, "   
lv_check_auth  TYPE C, "   ' '
lv_auth_no_begrp  TYPE C, "   
lv_auth_no_badi  TYPE C, "   
lv_iv_refresh_buffer  TYPE FLAG, "   
lv_equi  TYPE EQUI, "   
lv_equi_no  TYPE EQUI-EQUNR, "   
lv_auth_no_iwerk  TYPE EQUI, "   
lv_equz  TYPE EQUZ, "   
lv_equz_anz  TYPE EQUZ-EQLFN, "   1
lv_auth_no_swerk  TYPE EQUZ, "   
lv_iloa  TYPE ILOA, "   
lv_liste  TYPE C, "   ' '
lv_eqkt_not_found  TYPE C, "   
lv_reading_date  TYPE EQUZ-DATBI, "   
lv_equi_not_found  TYPE EQUZ, "   
lv_time  TYPE SY-UZEIT, "   '0'
lv_equz_not_found  TYPE SY, "   
lv_hist  TYPE RM63E-INDU, "   
lv_iloa_not_found  TYPE RM63E, "   
lv_auth_no_ingrp  TYPE RM63E, "   
lv_no_equz_selection  TYPE C, "   SPACE
lv_iv_uii  TYPE EQUI-UII, "   SPACE
lv_auth_no_kostl  TYPE EQUI. "   

  CALL FUNCTION 'EQUIPMENT_READ_DISPLAY'  "NOTRANSL: Equipment lesen mit Zeitsegmentliste
    EXPORTING
         CHECK_AUTH = lv_check_auth
         IV_REFRESH_BUFFER = lv_iv_refresh_buffer
         EQUI_NO = lv_equi_no
         EQUZ_ANZ = lv_equz_anz
         LISTE = lv_liste
         READING_DATE = lv_reading_date
         TIME = lv_time
         HIST = lv_hist
         NO_EQUZ_SELECTION = lv_no_equz_selection
         IV_UII = lv_iv_uii
    IMPORTING
         EQKT = lv_eqkt
         EQUI = lv_equi
         EQUZ = lv_equz
         ILOA = lv_iloa
    EXCEPTIONS
        AUTH_NO_BEGRP = 1
        AUTH_NO_BADI = 10
        AUTH_NO_IWERK = 2
        AUTH_NO_SWERK = 3
        EQKT_NOT_FOUND = 4
        EQUI_NOT_FOUND = 5
        EQUZ_NOT_FOUND = 6
        ILOA_NOT_FOUND = 7
        AUTH_NO_INGRP = 8
        AUTH_NO_KOSTL = 9
. " EQUIPMENT_READ_DISPLAY




ABAP code using 7.40 inline data declarations to call FM EQUIPMENT_READ_DISPLAY

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.

 
DATA(ld_check_auth) = ' '.
 
 
 
 
 
"SELECT single EQUNR FROM EQUI INTO @DATA(ld_equi_no).
 
 
 
"SELECT single EQLFN FROM EQUZ INTO @DATA(ld_equz_anz).
DATA(ld_equz_anz) = 1.
 
 
 
DATA(ld_liste) = ' '.
 
 
"SELECT single DATBI FROM EQUZ INTO @DATA(ld_reading_date).
 
 
"SELECT single UZEIT FROM SY INTO @DATA(ld_time).
DATA(ld_time) = '0'.
 
 
"SELECT single INDU FROM RM63E INTO @DATA(ld_hist).
 
 
 
DATA(ld_no_equz_selection) = ' '.
 
"SELECT single UII FROM EQUI INTO @DATA(ld_iv_uii).
DATA(ld_iv_uii) = ' '.
 
 


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!