SAP J_1UF_GET_BALANCE Function Module for Balance from New GL Totals Table
J_1UF_GET_BALANCE is a standard j 1uf get balance SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Balance from New GL Totals Table processing and below is the pattern details for this FM, 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 j 1uf get balance FM, simply by entering the name J_1UF_GET_BALANCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1UF_TAX
Program Name: SAPLJ1UF_TAX
Main Program: SAPLJ1UF_TAX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1UF_GET_BALANCE 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 'J_1UF_GET_BALANCE'"Balance from New GL Totals Table.
EXPORTING
* I_GLT0_RLDNR = '00' "Ledger
* I_DRCRK = "Debit/Credit Indicator
* I_RPMAX = "Period
* I_MONAT = "Fiscal Period
* I_RRCTY = "Record Type
* I_RVERS = "Version
* I_BUKRS = "Company Code
* I_RYEAR = "Fiscal year
* I_IND_DR = "Indicator D/R
* I_RACCT = "Account number
* I_RBUSA = "Business Area
* I_RTCUR = "Currency Key
IMPORTING
E_BALANCE = "Total transactions in the period in local currency (curr 2)
EXCEPTIONS
INVALID_SELECTION = 1
IMPORTING Parameters details for J_1UF_GET_BALANCE
I_GLT0_RLDNR - Ledger
Data type: RLDNRDefault: '00'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DRCRK - Debit/Credit Indicator
Data type: SHKZGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RPMAX - Period
Data type: RPMAXOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MONAT - Fiscal Period
Data type: MONATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RRCTY - Record Type
Data type: RRCTYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RVERS - Version
Data type: RVERSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUKRS - Company Code
Data type: BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RYEAR - Fiscal year
Data type: RYEAROptional: Yes
Call by Reference: No ( called with pass by value option)
I_IND_DR - Indicator D/R
Data type: J_1UF_TYPE_PARSTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RACCT - Account number
Data type: RACCTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RBUSA - Business Area
Data type: GSBEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_RTCUR - Currency Key
Data type: RTCUROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for J_1UF_GET_BALANCE
E_BALANCE - Total transactions in the period in local currency (curr 2)
Data type: HSLXXOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_SELECTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_1UF_GET_BALANCE 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_e_balance | TYPE HSLXX, " | |||
| lv_i_glt0_rldnr | TYPE RLDNR, " '00' | |||
| lv_invalid_selection | TYPE RLDNR, " | |||
| lv_i_drcrk | TYPE SHKZG, " | |||
| lv_i_rpmax | TYPE RPMAX, " | |||
| lv_i_monat | TYPE MONAT, " | |||
| lv_i_rrcty | TYPE RRCTY, " | |||
| lv_i_rvers | TYPE RVERS, " | |||
| lv_i_bukrs | TYPE BUKRS, " | |||
| lv_i_ryear | TYPE RYEAR, " | |||
| lv_i_ind_dr | TYPE J_1UF_TYPE_PARST, " | |||
| lv_i_racct | TYPE RACCT, " | |||
| lv_i_rbusa | TYPE GSBER, " | |||
| lv_i_rtcur | TYPE RTCUR. " |
|   CALL FUNCTION 'J_1UF_GET_BALANCE' "Balance from New GL Totals Table |
| EXPORTING | ||
| I_GLT0_RLDNR | = lv_i_glt0_rldnr | |
| I_DRCRK | = lv_i_drcrk | |
| I_RPMAX | = lv_i_rpmax | |
| I_MONAT | = lv_i_monat | |
| I_RRCTY | = lv_i_rrcty | |
| I_RVERS | = lv_i_rvers | |
| I_BUKRS | = lv_i_bukrs | |
| I_RYEAR | = lv_i_ryear | |
| I_IND_DR | = lv_i_ind_dr | |
| I_RACCT | = lv_i_racct | |
| I_RBUSA | = lv_i_rbusa | |
| I_RTCUR | = lv_i_rtcur | |
| IMPORTING | ||
| E_BALANCE | = lv_e_balance | |
| EXCEPTIONS | ||
| INVALID_SELECTION = 1 | ||
| . " J_1UF_GET_BALANCE | ||
ABAP code using 7.40 inline data declarations to call FM J_1UF_GET_BALANCE
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_i_glt0_rldnr) | = '00'. | |||
Search for further information about these or an SAP related objects