SAP MAINT_CALL_NEXT_FOR_OBJECT Function Module for NOTRANSL: Read next maintenance call for Technical Object









MAINT_CALL_NEXT_FOR_OBJECT is a standard maint call next for object 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: Read next maintenance call for Technical Object 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 maint call next for object FM, simply by entering the name MAINT_CALL_NEXT_FOR_OBJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function MAINT_CALL_NEXT_FOR_OBJECT 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 'MAINT_CALL_NEXT_FOR_OBJECT'"NOTRANSL: Read next maintenance call for Technical Object
  EXPORTING
*  MAINT_CALL_TPLNR = ' ' "Functional Location
*  MAINT_CALL_EQUNR = ' ' "Equipment Number
   OFFSET_DATE =  "Basic start date
*  OFFSET_INCLUSIVE = 'X' "Yes/No (X/ )
*  INSTFL_INCLUSIVE = ' ' "Yes/No (X/ )
*  INSTEQ_INCLUSIVE = ' ' "Yes/No (X/ )

 IMPORTING
   CALL_WA =  "Order List of a Technical Object (Short)

EXCEPTIONS
   CALL_NOT_FOUND = 1    OBJECT_NOT_FOUND = 2
.



IMPORTING Parameters details for MAINT_CALL_NEXT_FOR_OBJECT

MAINT_CALL_TPLNR - Functional Location

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

MAINT_CALL_EQUNR - Equipment Number

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

OFFSET_DATE - Basic start date

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

OFFSET_INCLUSIVE - Yes/No (X/ )

Data type: IREF-IIND
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

INSTFL_INCLUSIVE - Yes/No (X/ )

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

INSTEQ_INCLUSIVE - Yes/No (X/ )

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

EXPORTING Parameters details for MAINT_CALL_NEXT_FOR_OBJECT

CALL_WA - Order List of a Technical Object (Short)

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

EXCEPTIONS details

CALL_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

OBJECT_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for MAINT_CALL_NEXT_FOR_OBJECT 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_call_wa  TYPE FLEET_ORDERS, "   
lv_call_not_found  TYPE FLEET_ORDERS, "   
lv_maint_call_tplnr  TYPE ILOA-TPLNR, "   SPACE
lv_maint_call_equnr  TYPE EQUI-EQUNR, "   SPACE
lv_object_not_found  TYPE EQUI, "   
lv_offset_date  TYPE MHIO-GSTRP, "   
lv_offset_inclusive  TYPE IREF-IIND, "   'X'
lv_instfl_inclusive  TYPE IREF-IIND, "   SPACE
lv_insteq_inclusive  TYPE IREF-IIND. "   SPACE

  CALL FUNCTION 'MAINT_CALL_NEXT_FOR_OBJECT'  "NOTRANSL: Read next maintenance call for Technical Object
    EXPORTING
         MAINT_CALL_TPLNR = lv_maint_call_tplnr
         MAINT_CALL_EQUNR = lv_maint_call_equnr
         OFFSET_DATE = lv_offset_date
         OFFSET_INCLUSIVE = lv_offset_inclusive
         INSTFL_INCLUSIVE = lv_instfl_inclusive
         INSTEQ_INCLUSIVE = lv_insteq_inclusive
    IMPORTING
         CALL_WA = lv_call_wa
    EXCEPTIONS
        CALL_NOT_FOUND = 1
        OBJECT_NOT_FOUND = 2
. " MAINT_CALL_NEXT_FOR_OBJECT




ABAP code using 7.40 inline data declarations to call FM MAINT_CALL_NEXT_FOR_OBJECT

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 TPLNR FROM ILOA INTO @DATA(ld_maint_call_tplnr).
DATA(ld_maint_call_tplnr) = ' '.
 
"SELECT single EQUNR FROM EQUI INTO @DATA(ld_maint_call_equnr).
DATA(ld_maint_call_equnr) = ' '.
 
 
"SELECT single GSTRP FROM MHIO INTO @DATA(ld_offset_date).
 
"SELECT single IIND FROM IREF INTO @DATA(ld_offset_inclusive).
DATA(ld_offset_inclusive) = 'X'.
 
"SELECT single IIND FROM IREF INTO @DATA(ld_instfl_inclusive).
DATA(ld_instfl_inclusive) = ' '.
 
"SELECT single IIND FROM IREF INTO @DATA(ld_insteq_inclusive).
DATA(ld_insteq_inclusive) = ' '.
 


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!