SAP PM_OBJECT_MTBR Function Module for NOTRANSL: PM-IS: Berechnung der Kennzahlen MTTR MTBR für Technische Objekt

Search SAP Function Modules

PM_OBJECT_MTBR is a standard pm object mtbr 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: PM-IS: Berechnung der Kennzahlen MTTR MTBR für Technische Objekt 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 pm object mtbr FM, simply by entering the name PM_OBJECT_MTBR into the relevant SAP transaction such as SE37 or SE38.

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

Function PM_OBJECT_MTBR 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 'PM_OBJECT_MTBR'"NOTRANSL: PM-IS: Berechnung der Kennzahlen MTTR MTBR für Technische Objekt
  EXPORTING
   I_OBKNZ =  "Created Date
*  SO_EQUNR =  "
*  SO_TPLNR =  "
*  I_IMAGE =  "
*  I_VIQMEL =  "Generated Table for View VIQMEL

 IMPORTING
   ET_STARTUP_EQUI =  "
   ET_STARTUP_IFLO =  "
   ET_BRKDWN_REP =  "
   ET_BRKDWN_EFF =  "
   ET_RESULT =  "
   ET_MCIQMADD =  "

.

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_SAPLMCI1_001 PMIS/QMIS User Exit: Update

IMPORTING Parameters details for PM_OBJECT_MTBR

I_OBKNZ - Created Date

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

SO_EQUNR -

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

SO_TPLNR -

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

I_IMAGE -

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

I_VIQMEL - Generated Table for View VIQMEL

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

EXPORTING Parameters details for PM_OBJECT_MTBR

ET_STARTUP_EQUI -

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

ET_STARTUP_IFLO -

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

ET_BRKDWN_REP -

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

ET_BRKDWN_EFF -

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

ET_RESULT -

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

ET_MCIQMADD -

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

Copy and paste ABAP code example for PM_OBJECT_MTBR 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.

ABAP code using 7.40 inline data declarations to call FM PM_OBJECT_MTBR

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