SAP AAPM_AA_DETERMINE_ACTION Function Module for
AAPM_AA_DETERMINE_ACTION is a standard aapm aa determine action 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 aa determine action FM, simply by entering the name AAPM_AA_DETERMINE_ACTION 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_AA_DETERMINE_ACTION 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_AA_DETERMINE_ACTION'".
EXPORTING
ID_ACTIVITY_TYPE = "
* ID_CALLTIME = "
* IS_EQUI_DAT = "
* IS_SAAPM2_FROM_ASSET = "
IS_ANLA = "
IS_ANLZ = "
IS_ANLU = "
IMPORTING
ED_CHANGE_AA = "
ED_CREATE_AA = "
ED_CHANGE_PM = "
ED_NO_CHANGES = "
ES_ITOB = "
ES_ITOB_FROM_EQUI = "
EXCEPTIONS
ERR_READ_ASSET = 1 DATA_INCONSISTENCE = 2
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_AA_DETERMINE_ACTION
ID_ACTIVITY_TYPE -
Data type: T020-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
ID_CALLTIME -
Data type: AAPMT_CALLTIMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_EQUI_DAT -
Data type: AAPM_AA_EQUI_DATOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_SAAPM2_FROM_ASSET -
Data type: SAAPM2Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_ANLA -
Data type: ANLAOptional: No
Call by Reference: No ( called with pass by value option)
IS_ANLZ -
Data type: ANLZOptional: No
Call by Reference: No ( called with pass by value option)
IS_ANLU -
Data type: ANLUOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AAPM_AA_DETERMINE_ACTION
ED_CHANGE_AA -
Data type: AAPM_ACT_CHANGE_AAOptional: No
Call by Reference: No ( called with pass by value option)
ED_CREATE_AA -
Data type: AAPM_ACT_CREATE_AAOptional: No
Call by Reference: No ( called with pass by value option)
ED_CHANGE_PM -
Data type: AAPM_ACT_CHANGE_PMOptional: No
Call by Reference: No ( called with pass by value option)
ED_NO_CHANGES -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
ES_ITOB -
Data type: ITOBOptional: No
Call by Reference: No ( called with pass by value option)
ES_ITOB_FROM_EQUI -
Data type: ITOBOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERR_READ_ASSET -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_INCONSISTENCE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AAPM_AA_DETERMINE_ACTION 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_ed_change_aa | TYPE AAPM_ACT_CHANGE_AA, " | |||
lv_err_read_asset | TYPE AAPM_ACT_CHANGE_AA, " | |||
lv_id_activity_type | TYPE T020-AKTYP, " | |||
lv_id_calltime | TYPE AAPMT_CALLTIME, " | |||
lv_ed_create_aa | TYPE AAPM_ACT_CREATE_AA, " | |||
lv_data_inconsistence | TYPE AAPM_ACT_CREATE_AA, " | |||
lv_is_equi_dat | TYPE AAPM_AA_EQUI_DAT, " | |||
lv_ed_change_pm | TYPE AAPM_ACT_CHANGE_PM, " | |||
lv_ed_no_changes | TYPE C, " | |||
lv_is_saapm2_from_asset | TYPE SAAPM2, " | |||
lv_es_itob | TYPE ITOB, " | |||
lv_is_anla | TYPE ANLA, " | |||
lv_is_anlz | TYPE ANLZ, " | |||
lv_es_itob_from_equi | TYPE ITOB, " | |||
lv_is_anlu | TYPE ANLU. " |
  CALL FUNCTION 'AAPM_AA_DETERMINE_ACTION' " |
EXPORTING | ||
ID_ACTIVITY_TYPE | = lv_id_activity_type | |
ID_CALLTIME | = lv_id_calltime | |
IS_EQUI_DAT | = lv_is_equi_dat | |
IS_SAAPM2_FROM_ASSET | = lv_is_saapm2_from_asset | |
IS_ANLA | = lv_is_anla | |
IS_ANLZ | = lv_is_anlz | |
IS_ANLU | = lv_is_anlu | |
IMPORTING | ||
ED_CHANGE_AA | = lv_ed_change_aa | |
ED_CREATE_AA | = lv_ed_create_aa | |
ED_CHANGE_PM | = lv_ed_change_pm | |
ED_NO_CHANGES | = lv_ed_no_changes | |
ES_ITOB | = lv_es_itob | |
ES_ITOB_FROM_EQUI | = lv_es_itob_from_equi | |
EXCEPTIONS | ||
ERR_READ_ASSET = 1 | ||
DATA_INCONSISTENCE = 2 | ||
. " AAPM_AA_DETERMINE_ACTION |
ABAP code using 7.40 inline data declarations to call FM AAPM_AA_DETERMINE_ACTION
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 T020 INTO @DATA(ld_id_activity_type). | ||||
Search for further information about these or an SAP related objects