LAFA_ASSET_CREATE SAP Function module

LAFA_ASSET_CREATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name LAFA_ASSET_CREATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FILAFA
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM LAFA_ASSET_CREATE - LAFA ASSET CREATE

CALL FUNCTION 'LAFA_ASSET_CREATE' "
  EXPORTING
    id_method =                 " fila_method   Method (Function Module Name)
*   id_bukrs =                  " anlc-bukrs    Company Code
*   id_anln1 =                  " anlc-anln1    Main Asset Number
*   id_anln2 =                  " anlc-anln2    Asset Subnumber
  IMPORTING
    et_return =                 " filae_tb_return
    ed_bukrs =                  " anla-bukrs    Company Code
    ed_anln1 =                  " anla-anln1    Main Asset Number
    ed_anln2 =                  " anla-anln2    Asset Subnumber
  CHANGING
    cty_item =                  " filae_ct_item
    .  "  LAFA_ASSET_CREATE

ABAP code example for Function Module LAFA_ASSET_CREATE

The ABAP code below is a full code listing to execute function module LAFA_ASSET_CREATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_return  
 
 TYPE FILAE_TB_RETURN
,
ld_ed_bukrs  
 
 TYPE ANLA-BUKRS
,
ld_ed_anln1  
 
 TYPE ANLA-ANLN1
,
ld_ed_anln2  
 
 TYPE ANLA-ANLN2
.


DATA(ld_cty_item) = 'Check type of data required'.

DATA(ld_id_method) = 'Check type of data required'.
 

SELECT single BUKRS 
  FROM ANLC 
  INTO @DATA(ld_id_bukrs).

 

SELECT single ANLN1 
  FROM ANLC 
  INTO @DATA(ld_id_anln1).

 

SELECT single ANLN2 
  FROM ANLC 
  INTO @DATA(ld_id_anln2).

.

CALL FUNCTION 'LAFA_ASSET_CREATE'
  EXPORTING
    id_method =                  ld_id_method
*   id_bukrs =                   ld_id_bukrs
*   id_anln1 =                   ld_id_anln1
*   id_anln2 =                   ld_id_anln2
  IMPORTING
    et_return =                  ld_et_return
    ed_bukrs =                   ld_ed_bukrs
    ed_anln1 =                   ld_ed_anln1
    ed_anln2 =                   ld_ed_anln2
  CHANGING
    cty_item =                   ld_cty_item
    .  "  LAFA_ASSET_CREATE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_cty_item
 
 TYPE FILAE_CT_ITEM ,
ld_et_return
 
 TYPE FILAE_TB_RETURN ,
ld_id_method
 
 TYPE FILA_METHOD ,
ld_ed_bukrs
 
 TYPE ANLA-BUKRS ,
ld_id_bukrs
 
 TYPE ANLC-BUKRS ,
ld_ed_anln1
 
 TYPE ANLA-ANLN1 ,
ld_id_anln1
 
 TYPE ANLC-ANLN1 ,
ld_ed_anln2
 
 TYPE ANLA-ANLN2 ,
ld_id_anln2
 
 TYPE ANLC-ANLN2 .


ld_cty_item = 'Check type of data required'.
ld_id_method = 'Check type of data required'.

SELECT single BUKRS 
  FROM ANLC 
  INTO ld_id_bukrs.


SELECT single ANLN1 
  FROM ANLC 
  INTO ld_id_anln1.


SELECT single ANLN2 
  FROM ANLC 
  INTO ld_id_anln2.