SAP BAPI_PROCESS_GETACTALLOCTYPES Function Module for

Search SAP Function Modules

BAPI_PROCESS_GETACTALLOCTYPES is a standard bapi process getactalloctypes 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 bapi process getactalloctypes FM, simply by entering the name BAPI_PROCESS_GETACTALLOCTYPES into the relevant SAP transaction such as SE37 or SE38.

Function Group: 1036
Program Name: SAPL1036
Main Program: SAPL1036
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PROCESS_GETACTALLOCTYPES 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 'BAPI_PROCESS_GETACTALLOCTYPES'"
  EXPORTING
   CONTROLLINGAREA =  "
   BUSINESSPROCESSID =  "
*  KEYDATE =  "

 IMPORTING
   DIRECT_ALLOCATION =  "
   INDIRECT_ALLOCATION =  "
   TEMPLATE_ALLOCATION =  "
   SENDER_QUANTITY =  "

TABLES
   RETURN =  "

.

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_SAPL1036_001 Exit 1 (Input) for BusinessProcess.CreateMultiple
EXIT_SAPL1036_002 Exit 2 (Output) for BusinessProcess.CreateMultiple
EXIT_SAPL1036_003 Exit 1 (Input) for BusinessProcess.ChangeMultiple
EXIT_SAPL1036_004 Exit 2 (Output) for BusinessProcess.ChangeMultiple
EXIT_SAPL1036_005 Exit 1 (Input) for BusinessProcess.CheckMultiple
EXIT_SAPL1036_006 Exit 2 (Output) for BusinessProcess.CheckMultiple
EXIT_SAPL1036_007 Exit 1 (Input) for BusinessProcess.GetList
EXIT_SAPL1036_008 Exit 2 (Output) for BusinessProcess.GetList
EXIT_SAPL1036_009 Exit 1 (Input) for BusinessProcess.GetDetail
EXIT_SAPL1036_010 Exit 2 (Output) for BusinessProcess.GetDetail

IMPORTING Parameters details for BAPI_PROCESS_GETACTALLOCTYPES

CONTROLLINGAREA -

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

BUSINESSPROCESSID -

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

KEYDATE -

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

EXPORTING Parameters details for BAPI_PROCESS_GETACTALLOCTYPES

DIRECT_ALLOCATION -

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

INDIRECT_ALLOCATION -

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

TEMPLATE_ALLOCATION -

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

SENDER_QUANTITY -

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

TABLES Parameters details for BAPI_PROCESS_GETACTALLOCTYPES

RETURN -

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

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

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