AIPA_F4_PLAN_VERSION SAP Function module

AIPA_F4_PLAN_VERSION 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 AIPA_F4_PLAN_VERSION into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM AIPA_F4_PLAN_VERSION - AIPA F4 PLAN VERSION

CALL FUNCTION 'AIPA_F4_PLAN_VERSION' "
  EXPORTING
    i_program =                 " d020s-prog
    i_dynnr =                   " d020s-dnum
*   i_fn_gjahr_proposal =       " dynpread-fieldname
*   i_fn_prnam_proposal =       " dynpread-fieldname
*   i_fn_versn = 'RAIP_DYNP-VERSN'  " dynpread-fieldname
*   i_takeover_allowed = 'X'    " c
  IMPORTING
    e_versn =                   " raip3-versn
    .  "  AIPA_F4_PLAN_VERSION

ABAP code example for Function Module AIPA_F4_PLAN_VERSION

The ABAP code below is a full code listing to execute function module AIPA_F4_PLAN_VERSION 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_e_versn  
 
 TYPE RAIP3-VERSN
.

 

SELECT single PROG 
  FROM D020S 
  INTO @DATA(ld_i_program).

 

SELECT single DNUM 
  FROM D020S 
  INTO @DATA(ld_i_dynnr).



DATA(ld_i_fn_gjahr_proposal) = some text here


DATA(ld_i_fn_prnam_proposal) = some text here


DATA(ld_i_fn_versn) = some text here

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

CALL FUNCTION 'AIPA_F4_PLAN_VERSION'
  EXPORTING
    i_program =                  ld_i_program
    i_dynnr =                    ld_i_dynnr
*   i_fn_gjahr_proposal =        ld_i_fn_gjahr_proposal
*   i_fn_prnam_proposal =        ld_i_fn_prnam_proposal
*   i_fn_versn =                 ld_i_fn_versn
*   i_takeover_allowed =         ld_i_takeover_allowed
  IMPORTING
    e_versn =                    ld_e_versn
    .  "  AIPA_F4_PLAN_VERSION

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_e_versn
 
 TYPE RAIP3-VERSN ,
ld_i_program
 
 TYPE D020S-PROG ,
ld_i_dynnr
 
 TYPE D020S-DNUM ,
ld_i_fn_gjahr_proposal
 
 TYPE DYNPREAD-FIELDNAME ,
ld_i_fn_prnam_proposal
 
 TYPE DYNPREAD-FIELDNAME ,
ld_i_fn_versn
 
 TYPE DYNPREAD-FIELDNAME ,
ld_i_takeover_allowed
 
 TYPE C .



SELECT single PROG 
  FROM D020S 
  INTO ld_i_program.


SELECT single DNUM 
  FROM D020S 
  INTO ld_i_dynnr.


ld_i_fn_gjahr_proposal = some text here

ld_i_fn_prnam_proposal = some text here

ld_i_fn_versn = some text here
ld_i_takeover_allowed = 'Check type of data required'.