SAP OIO_DOCFLOW_OBJ_PM02_CHANGE Function Module for Change: plant maintenance order component









OIO_DOCFLOW_OBJ_PM02_CHANGE is a standard oio docflow obj pm02 change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change: plant maintenance order component 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 oio docflow obj pm02 change FM, simply by entering the name OIO_DOCFLOW_OBJ_PM02_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function OIO_DOCFLOW_OBJ_PM02_CHANGE 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 'OIO_DOCFLOW_OBJ_PM02_CHANGE'"Change: plant maintenance order component
EXPORTING
I_OBJTY = "Object type for document flow
I_OBJID = "Identifier for document flow object

EXCEPTIONS
INVALID_OBJECT_TYPE = 1
.



IMPORTING Parameters details for OIO_DOCFLOW_OBJ_PM02_CHANGE

I_OBJTY - Object type for document flow

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

I_OBJID - Identifier for document flow object

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

EXCEPTIONS details

INVALID_OBJECT_TYPE -

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

Copy and paste ABAP code example for OIO_DOCFLOW_OBJ_PM02_CHANGE 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_i_objty  TYPE OIO_OBJTY, "   
lv_invalid_object_type  TYPE OIO_OBJTY, "   
lv_i_objid  TYPE OIO_OBJID. "   

  CALL FUNCTION 'OIO_DOCFLOW_OBJ_PM02_CHANGE'  "Change: plant maintenance order component
    EXPORTING
         I_OBJTY = lv_i_objty
         I_OBJID = lv_i_objid
    EXCEPTIONS
        INVALID_OBJECT_TYPE = 1
. " OIO_DOCFLOW_OBJ_PM02_CHANGE




ABAP code using 7.40 inline data declarations to call FM OIO_DOCFLOW_OBJ_PM02_CHANGE

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!