SAP AAPM_PM_SYNC_BY_WORKFLOW Function Module for
AAPM_PM_SYNC_BY_WORKFLOW is a standard aapm pm sync by workflow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 aapm pm sync by workflow FM, simply by entering the name AAPM_PM_SYNC_BY_WORKFLOW into the relevant SAP transaction such as SE37 or SE38.
Function Group: AAPM
Program Name: SAPLAAPM
Main Program: SAPLAAPM
Appliation area: A
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AAPM_PM_SYNC_BY_WORKFLOW 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 'AAPM_PM_SYNC_BY_WORKFLOW'".
EXPORTING
I_ACTIVITY_TYPE = "
I_EQUNR = "
* I_ANLNR = "
* I_ANLUN = "
* I_BUKRS = "
* I_DIALOG = "
EXCEPTIONS
ERR_READ_EQUI = 1 ERR_READ_EQUI_ASSET = 2 ERR_SYNCHRONIZE = 3 ERR_PROCESS_EQUI_ASSET = 4 ERR_PROCESS_EQUI = 5
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_SAPLAAPM_001 User Exit for Deriving Asset Class from Fields of Plant Maintenance
EXIT_SAPLAAPM_002 User Exit for Deriving Equipment Category from Fields of Asset Accounting
IMPORTING Parameters details for AAPM_PM_SYNC_BY_WORKFLOW
I_ACTIVITY_TYPE -
Data type: T370-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_EQUNR -
Data type: ITOB-EQUNROptional: No
Call by Reference: No ( called with pass by value option)
I_ANLNR -
Data type: ITOB-ANLNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_ANLUN -
Data type: ITOB-ANLUNOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUKRS -
Data type: ITOB-BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DIALOG -
Data type: ITOB_TYPES-BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERR_READ_EQUI -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERR_READ_EQUI_ASSET -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERR_SYNCHRONIZE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERR_PROCESS_EQUI_ASSET -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERR_PROCESS_EQUI -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AAPM_PM_SYNC_BY_WORKFLOW 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_err_read_equi | TYPE STRING, " | |||
| lv_i_activity_type | TYPE T370-AKTYP, " | |||
| lv_i_equnr | TYPE ITOB-EQUNR, " | |||
| lv_err_read_equi_asset | TYPE ITOB, " | |||
| lv_i_anlnr | TYPE ITOB-ANLNR, " | |||
| lv_err_synchronize | TYPE ITOB, " | |||
| lv_i_anlun | TYPE ITOB-ANLUN, " | |||
| lv_err_process_equi_asset | TYPE ITOB, " | |||
| lv_i_bukrs | TYPE ITOB-BUKRS, " | |||
| lv_err_process_equi | TYPE ITOB, " | |||
| lv_i_dialog | TYPE ITOB_TYPES-BOOL. " |
|   CALL FUNCTION 'AAPM_PM_SYNC_BY_WORKFLOW' " |
| EXPORTING | ||
| I_ACTIVITY_TYPE | = lv_i_activity_type | |
| I_EQUNR | = lv_i_equnr | |
| I_ANLNR | = lv_i_anlnr | |
| I_ANLUN | = lv_i_anlun | |
| I_BUKRS | = lv_i_bukrs | |
| I_DIALOG | = lv_i_dialog | |
| EXCEPTIONS | ||
| ERR_READ_EQUI = 1 | ||
| ERR_READ_EQUI_ASSET = 2 | ||
| ERR_SYNCHRONIZE = 3 | ||
| ERR_PROCESS_EQUI_ASSET = 4 | ||
| ERR_PROCESS_EQUI = 5 | ||
| . " AAPM_PM_SYNC_BY_WORKFLOW | ||
ABAP code using 7.40 inline data declarations to call FM AAPM_PM_SYNC_BY_WORKFLOW
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 AKTYP FROM T370 INTO @DATA(ld_i_activity_type). | ||||
| "SELECT single EQUNR FROM ITOB INTO @DATA(ld_i_equnr). | ||||
| "SELECT single ANLNR FROM ITOB INTO @DATA(ld_i_anlnr). | ||||
| "SELECT single ANLUN FROM ITOB INTO @DATA(ld_i_anlun). | ||||
| "SELECT single BUKRS FROM ITOB INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single BOOL FROM ITOB_TYPES INTO @DATA(ld_i_dialog). | ||||
Search for further information about these or an SAP related objects