SAP ASSET_MOVEMENT_SIMULATE Function Module for

Search SAP Function Modules

ASSET_MOVEMENT_SIMULATE is a standard asset movement simulate 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 asset movement simulate FM, simply by entering the name ASSET_MOVEMENT_SIMULATE into the relevant SAP transaction such as SE37 or SE38.

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

Function ASSET_MOVEMENT_SIMULATE 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 'ASSET_MOVEMENT_SIMULATE'"
  EXPORTING
*  I_ANBTR = 0 "
   I_ANLAV =  "
*  I_BWASL = '   ' "
   I_GJAHR =  "
   I_BZDAT =  "
   I_WAERS =  "
*  I_XSTOR = ' ' "
*  I_XVABG = ' ' "

 IMPORTING
   E_ANTS =  "

TABLES
   T_ANEA =  "
   T_ANEP =  "
   T_ANFM =  "
   T_ANLB =  "
   T_ANLC =  "
   T_ANLZ =  "

EXCEPTIONS
   PARAMETER_INCONSISTENT = 1    PARAMETER_MISSING = 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_SAPLAINT_002 Dummy, needed for expanded syntax check, not used!!!

IMPORTING Parameters details for ASSET_MOVEMENT_SIMULATE

I_ANBTR -

Data type: ANEP-ANBTR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ANLAV -

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

I_BWASL -

Data type: ANEP-BWASL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_GJAHR -

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

I_BZDAT -

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

I_WAERS -

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

I_XSTOR -

Data type: RA01B-XSTOR
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XVABG -

Data type: ANEP-XAWBT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ASSET_MOVEMENT_SIMULATE

E_ANTS -

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

TABLES Parameters details for ASSET_MOVEMENT_SIMULATE

T_ANEA -

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

T_ANEP -

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

T_ANFM -

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

T_ANLB -

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

T_ANLC -

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

T_ANLZ -

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

EXCEPTIONS details

PARAMETER_INCONSISTENT -

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

PARAMETER_MISSING -

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

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

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