SAP GM_GET_BDGT_VALIDITY_DATES Function Module for Get the date range of a budget validity period for a grant

Search SAP Function Modules

GM_GET_BDGT_VALIDITY_DATES is a standard gm get bdgt validity dates 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 the date range of a budget validity period for a grant 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 gm get bdgt validity dates FM, simply by entering the name GM_GET_BDGT_VALIDITY_DATES into the relevant SAP transaction such as SE37 or SE38.

Function Group: GMBDGTVALIDITY
Program Name: SAPLGMBDGTVALIDITY
Main Program: SAPLGMBDGTVALIDITY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GM_GET_BDGT_VALIDITY_DATES 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 'GM_GET_BDGT_VALIDITY_DATES'"Get the date range of a budget validity period for a grant
  EXPORTING
   I_GRANT_NBR =  "Grant
   I_BDGT_PHASE =  "Budget phase
   I_BDGT_VLDTY_NBR =  "Budget validity number
   I_RELEASE_STATUS =  "Budget release status

 IMPORTING
   E_FROM_DATE =  "Valid from date
   E_TO_DATE =  "Valid to date
   E_BLOCK =  "Block a budget validity period

EXCEPTIONS
   INVALID_BDGT_VALIDITY = 1 

.

IMPORTING Parameters details for GM_GET_BDGT_VALIDITY_DATES

I_GRANT_NBR - Grant

Data type: GM_GRANT_NBR
Optional: No
Call by Reference: Yes

I_BDGT_PHASE - Budget phase

Data type: GM_BDGT_PHASE
Optional: No
Call by Reference: Yes

I_BDGT_VLDTY_NBR - Budget validity number

Data type: GM_BDGT_VLDTY_NBR
Optional: No
Call by Reference: Yes

I_RELEASE_STATUS - Budget release status

Data type: GM_BDGT_STATUS
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for GM_GET_BDGT_VALIDITY_DATES

E_FROM_DATE - Valid from date

Data type: GM_FROM_DATE
Optional: No
Call by Reference: Yes

E_TO_DATE - Valid to date

Data type: GM_TO_DATE
Optional: No
Call by Reference: Yes

E_BLOCK - Block a budget validity period

Data type: GM_BDGT_BLOCK
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_BDGT_VALIDITY - Invalid budget validity range

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

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

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