SAP AIPP_ALLOCATE_POSITION Function Module for
AIPP_ALLOCATE_POSITION is a standard aipp allocate position 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 aipp allocate position FM, simply by entering the name AIPP_ALLOCATE_POSITION into the relevant SAP transaction such as SE37 or SE38.
Function Group: AIPP
Program Name: SAPLAIPP
Main Program: SAPLAIPP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function AIPP_ALLOCATE_POSITION 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 'AIPP_ALLOCATE_POSITION'".
EXPORTING
* I_AKTYP = 'A' "Action category (A=display, V=change, H=create)
I_OBART = "Object type (OR = order, PR = WBS element)
I_KOKRS = "Controlling area
I_OBJNR = "CO object number
* I_AUART = "
* I_POSID = ' ' "WBS ID (only for title bar in window)
* I_PRART_IQ = "
* I_FLG_UPD_ON_COMMIT = 'X' "
* I_FLG_SKIP_FIRST_POPUP = ' ' "
IMPORTING
E_UPDATE = "Ind: 'There are assignments to be changed'
IMPORTING Parameters details for AIPP_ALLOCATE_POSITION
I_AKTYP - Action category (A=display, V=change, H=create)
Data type: T020-AKTYPDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_OBART - Object type (OR = order, PR = WBS element)
Data type: IMPS-OBARTOptional: No
Call by Reference: No ( called with pass by value option)
I_KOKRS - Controlling area
Data type: IMPR-KOKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJNR - CO object number
Data type: IMZO-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
I_AUART -
Data type: COAS-AUARTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_POSID - WBS ID (only for title bar in window)
Data type: PRPS-POSIDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PRART_IQ -
Data type: IMAK-PRARTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_UPD_ON_COMMIT -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_SKIP_FIRST_POPUP -
Data type: XFELDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AIPP_ALLOCATE_POSITION
E_UPDATE - Ind: 'There are assignments to be changed'
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AIPP_ALLOCATE_POSITION 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_aktyp | TYPE T020-AKTYP, " 'A' | |||
lv_e_update | TYPE C, " | |||
lv_i_obart | TYPE IMPS-OBART, " | |||
lv_i_kokrs | TYPE IMPR-KOKRS, " | |||
lv_i_objnr | TYPE IMZO-OBJNR, " | |||
lv_i_auart | TYPE COAS-AUART, " | |||
lv_i_posid | TYPE PRPS-POSID, " ' ' | |||
lv_i_prart_iq | TYPE IMAK-PRART, " | |||
lv_i_flg_upd_on_commit | TYPE C, " 'X' | |||
lv_i_flg_skip_first_popup | TYPE XFELD. " ' ' |
  CALL FUNCTION 'AIPP_ALLOCATE_POSITION' " |
EXPORTING | ||
I_AKTYP | = lv_i_aktyp | |
I_OBART | = lv_i_obart | |
I_KOKRS | = lv_i_kokrs | |
I_OBJNR | = lv_i_objnr | |
I_AUART | = lv_i_auart | |
I_POSID | = lv_i_posid | |
I_PRART_IQ | = lv_i_prart_iq | |
I_FLG_UPD_ON_COMMIT | = lv_i_flg_upd_on_commit | |
I_FLG_SKIP_FIRST_POPUP | = lv_i_flg_skip_first_popup | |
IMPORTING | ||
E_UPDATE | = lv_e_update | |
. " AIPP_ALLOCATE_POSITION |
ABAP code using 7.40 inline data declarations to call FM AIPP_ALLOCATE_POSITION
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 AKTYP FROM T020 INTO @DATA(ld_i_aktyp). | ||||
DATA(ld_i_aktyp) | = 'A'. | |||
"SELECT single OBART FROM IMPS INTO @DATA(ld_i_obart). | ||||
"SELECT single KOKRS FROM IMPR INTO @DATA(ld_i_kokrs). | ||||
"SELECT single OBJNR FROM IMZO INTO @DATA(ld_i_objnr). | ||||
"SELECT single AUART FROM COAS INTO @DATA(ld_i_auart). | ||||
"SELECT single POSID FROM PRPS INTO @DATA(ld_i_posid). | ||||
DATA(ld_i_posid) | = ' '. | |||
"SELECT single PRART FROM IMAK INTO @DATA(ld_i_prart_iq). | ||||
DATA(ld_i_flg_upd_on_commit) | = 'X'. | |||
DATA(ld_i_flg_skip_first_popup) | = ' '. | |||
Search for further information about these or an SAP related objects