SAP AM_ASSET_INSERT_INTO_AI Function Module for
AM_ASSET_INSERT_INTO_AI is a standard am asset insert into ai 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 am asset insert into ai FM, simply by entering the name AM_ASSET_INSERT_INTO_AI into the relevant SAP transaction such as SE37 or SE38.
Function Group: RAAB
Program Name: SAPLRAAB
Main Program: SAPLRAAB
Appliation area: A
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AM_ASSET_INSERT_INTO_AI 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 'AM_ASSET_INSERT_INTO_AI'".
EXPORTING
I_BUKRS = "Company code
I_ANLN1 = "Main asset number
I_ANLN2 = "Asset Subnumber
* I_AI_ID = ' ' "Identifier for worklist
* DO_COMMIT = ' ' "Carry out commit work
IMPORTING
E_SEL_AI = "ID of the selected work list
EXCEPTIONS
ASSET_NOT_INSERTED = 1
IMPORTING Parameters details for AM_ASSET_INSERT_INTO_AI
I_BUKRS - Company code
Data type: ANLA-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_ANLN1 - Main asset number
Data type: ANLA-ANLN1Optional: No
Call by Reference: No ( called with pass by value option)
I_ANLN2 - Asset Subnumber
Data type: ANLA-ANLN2Optional: No
Call by Reference: No ( called with pass by value option)
I_AI_ID - Identifier for worklist
Data type: RBADA-AI_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DO_COMMIT - Carry out commit work
Data type: SWWCOMMIT-COMMITFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AM_ASSET_INSERT_INTO_AI
E_SEL_AI - ID of the selected work list
Data type: SWWWIHEAD-WI_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ASSET_NOT_INSERTED - Asset was not added.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AM_ASSET_INSERT_INTO_AI 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_bukrs | TYPE ANLA-BUKRS, " | |||
| lv_e_sel_ai | TYPE SWWWIHEAD-WI_ID, " | |||
| lv_asset_not_inserted | TYPE SWWWIHEAD, " | |||
| lv_i_anln1 | TYPE ANLA-ANLN1, " | |||
| lv_i_anln2 | TYPE ANLA-ANLN2, " | |||
| lv_i_ai_id | TYPE RBADA-AI_ID, " SPACE | |||
| lv_do_commit | TYPE SWWCOMMIT-COMMITFLAG. " SPACE |
|   CALL FUNCTION 'AM_ASSET_INSERT_INTO_AI' " |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_ANLN1 | = lv_i_anln1 | |
| I_ANLN2 | = lv_i_anln2 | |
| I_AI_ID | = lv_i_ai_id | |
| DO_COMMIT | = lv_do_commit | |
| IMPORTING | ||
| E_SEL_AI | = lv_e_sel_ai | |
| EXCEPTIONS | ||
| ASSET_NOT_INSERTED = 1 | ||
| . " AM_ASSET_INSERT_INTO_AI | ||
ABAP code using 7.40 inline data declarations to call FM AM_ASSET_INSERT_INTO_AI
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 BUKRS FROM ANLA INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single WI_ID FROM SWWWIHEAD INTO @DATA(ld_e_sel_ai). | ||||
| "SELECT single ANLN1 FROM ANLA INTO @DATA(ld_i_anln1). | ||||
| "SELECT single ANLN2 FROM ANLA INTO @DATA(ld_i_anln2). | ||||
| "SELECT single AI_ID FROM RBADA INTO @DATA(ld_i_ai_id). | ||||
| DATA(ld_i_ai_id) | = ' '. | |||
| "SELECT single COMMITFLAG FROM SWWCOMMIT INTO @DATA(ld_do_commit). | ||||
| DATA(ld_do_commit) | = ' '. | |||
Search for further information about these or an SAP related objects