SAP GET_BUDCAT_FROM_ANY_LDNR Function Module for Get corresponding budcat from input ledger
GET_BUDCAT_FROM_ANY_LDNR is a standard get budcat from any ldnr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get corresponding budcat from input ledger 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 get budcat from any ldnr FM, simply by entering the name GET_BUDCAT_FROM_ANY_LDNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: FM_DERIVE_TOOLS
Program Name: SAPLFM_DERIVE_TOOLS
Main Program: SAPLFM_DERIVE_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_BUDCAT_FROM_ANY_LDNR 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 'GET_BUDCAT_FROM_ANY_LDNR'"Get corresponding budcat from input ledger.
EXPORTING
IM_LDNR = "Ledger number
IMPORTING
EX_BUDCAT = "Budget Category
EXCEPTIONS
INVALID_INPUT_LDNR = 1
IMPORTING Parameters details for GET_BUDCAT_FROM_ANY_LDNR
IM_LDNR - Ledger number
Data type: BUBAS_LDNROptional: No
Call by Reference: Yes
EXPORTING Parameters details for GET_BUDCAT_FROM_ANY_LDNR
EX_BUDCAT - Budget Category
Data type: BUKU_BUDCATOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_INPUT_LDNR - Invalid Input Ledger
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GET_BUDCAT_FROM_ANY_LDNR 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_im_ldnr | TYPE BUBAS_LDNR, " | |||
| lv_ex_budcat | TYPE BUKU_BUDCAT, " | |||
| lv_invalid_input_ldnr | TYPE BUKU_BUDCAT. " |
|   CALL FUNCTION 'GET_BUDCAT_FROM_ANY_LDNR' "Get corresponding budcat from input ledger |
| EXPORTING | ||
| IM_LDNR | = lv_im_ldnr | |
| IMPORTING | ||
| EX_BUDCAT | = lv_ex_budcat | |
| EXCEPTIONS | ||
| INVALID_INPUT_LDNR = 1 | ||
| . " GET_BUDCAT_FROM_ANY_LDNR | ||
ABAP code using 7.40 inline data declarations to call FM GET_BUDCAT_FROM_ANY_LDNR
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