SAP FVD_GDPDU_CHECK_DATES Function Module for Check Transferred Period or Fill It for Multiple Company Codes if Necess.

Search SAP Function Modules

FVD_GDPDU_CHECK_DATES is a standard fvd gdpdu check 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 Check Transferred Period or Fill It for Multiple Company Codes if Necess. 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 fvd gdpdu check dates FM, simply by entering the name FVD_GDPDU_CHECK_DATES into the relevant SAP transaction such as SE37 or SE38.

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

Function FVD_GDPDU_CHECK_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 'FVD_GDPDU_CHECK_DATES'"Check Transferred Period or Fill It for Multiple Company Codes if Necess.
  EXPORTING
*  IM_APPLICATION = 'TR-TM' "Application indicator for BTE
   IM_RNG_COMPANY_CODE =  "Range Table for Company Code
*  IM_USER = SY-UNAME "User Name
*  IM_PROGRAM = SY-CPROG "ABAP Program Name

 IMPORTING
   EX_FLG_TAX_AUDITOR =  "Benutzer ist Steuerprüfer

CHANGING
   CH_RNG_DATE =  "Date Area

EXCEPTIONS
   NO_AUTHORITY = 1    WRONG_INPUT = 2 

.

IMPORTING Parameters details for FVD_GDPDU_CHECK_DATES

IM_APPLICATION - Application indicator for BTE

Data type: APPLK_BF
Default: 'TR-TM'
Optional: Yes
Call by Reference: Yes

IM_RNG_COMPANY_CODE - Range Table for Company Code

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

IM_USER - User Name

Data type: USNAM
Default: SY-UNAME
Optional: Yes
Call by Reference: Yes

IM_PROGRAM - ABAP Program Name

Data type: PROGNAME
Default: SY-CPROG
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FVD_GDPDU_CHECK_DATES

EX_FLG_TAX_AUDITOR - Benutzer ist Steuerprüfer

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

CHANGING Parameters details for FVD_GDPDU_CHECK_DATES

CH_RNG_DATE - Date Area

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

EXCEPTIONS details

NO_AUTHORITY - Unauthorized

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

WRONG_INPUT - Incorrect Entry

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

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