SAP AIA_CHECK_PROJ_CODE_CHANGE Function Module for









AIA_CHECK_PROJ_CODE_CHANGE is a standard aia check proj code change 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 aia check proj code change FM, simply by entering the name AIA_CHECK_PROJ_CODE_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function AIA_CHECK_PROJ_CODE_CHANGE 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 'AIA_CHECK_PROJ_CODE_CHANGE'"
EXPORTING
IS_IMAK = "

IMPORTING
E_POSID_PROJ = "

TABLES
* RETURN = "

EXCEPTIONS
CODING_NOT_VALID = 1
.



IMPORTING Parameters details for AIA_CHECK_PROJ_CODE_CHANGE

IS_IMAK -

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

EXPORTING Parameters details for AIA_CHECK_PROJ_CODE_CHANGE

E_POSID_PROJ -

Data type: PROJ-PSPID
Optional: No
Call by Reference: Yes

TABLES Parameters details for AIA_CHECK_PROJ_CODE_CHANGE

RETURN -

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

CODING_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for AIA_CHECK_PROJ_CODE_CHANGE 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_is_imak  TYPE IMAK, "   
lv_e_posid_proj  TYPE PROJ-PSPID, "   
lv_coding_not_valid  TYPE PROJ. "   

  CALL FUNCTION 'AIA_CHECK_PROJ_CODE_CHANGE'  "
    EXPORTING
         IS_IMAK = lv_is_imak
    IMPORTING
         E_POSID_PROJ = lv_e_posid_proj
    TABLES
         RETURN = lt_return
    EXCEPTIONS
        CODING_NOT_VALID = 1
. " AIA_CHECK_PROJ_CODE_CHANGE




ABAP code using 7.40 inline data declarations to call FM AIA_CHECK_PROJ_CODE_CHANGE

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 PSPID FROM PROJ INTO @DATA(ld_e_posid_proj).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!