SAP FAGL_SEGMENT_ALLOCATION Function Module for
FAGL_SEGMENT_ALLOCATION is a standard fagl segment allocation 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 fagl segment allocation FM, simply by entering the name FAGL_SEGMENT_ALLOCATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FAGL_SEGMENT
Program Name: SAPLFAGL_SEGMENT
Main Program: SAPLFAGL_SEGMENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FAGL_SEGMENT_ALLOCATION 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 'FAGL_SEGMENT_ALLOCATION'".
EXPORTING
* ID_SR_TYPE = ' ' "
CHANGING
CS_GLU1 = "G/L user table 1
IMPORTING Parameters details for FAGL_SEGMENT_ALLOCATION
ID_SR_TYPE -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for FAGL_SEGMENT_ALLOCATION
CS_GLU1 - G/L user table 1
Data type: GLU1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FAGL_SEGMENT_ALLOCATION 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_cs_glu1 | TYPE GLU1, " | |||
| lv_id_sr_type | TYPE C. " SPACE |
|   CALL FUNCTION 'FAGL_SEGMENT_ALLOCATION' " |
| EXPORTING | ||
| ID_SR_TYPE | = lv_id_sr_type | |
| CHANGING | ||
| CS_GLU1 | = lv_cs_glu1 | |
| . " FAGL_SEGMENT_ALLOCATION | ||
ABAP code using 7.40 inline data declarations to call FM FAGL_SEGMENT_ALLOCATION
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.| DATA(ld_id_sr_type) | = ' '. | |||
Search for further information about these or an SAP related objects