SAP FVD_CHARGE_API_GETDETAIL Function Module for Get Detail









FVD_CHARGE_API_GETDETAIL is a standard fvd charge api getdetail 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 Detail 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 charge api getdetail FM, simply by entering the name FVD_CHARGE_API_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function FVD_CHARGE_API_GETDETAIL 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_CHARGE_API_GETDETAIL'"Get Detail
EXPORTING
I_STR_BO_KEY = "Business Operation Key Structure
I_FLG_LIKE_DIALOG = "General Indicator
I_FLG_TESTRUN = "General Indicator

IMPORTING
E_TAB_RBOBEPP_API = "Interface Structure and Control Data Charges
E_TAB_BAPIERR = "Table Types for Error Handling

EXCEPTIONS
FATAL_ERROR = 1
.



IMPORTING Parameters details for FVD_CHARGE_API_GETDETAIL

I_STR_BO_KEY - Business Operation Key Structure

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

I_FLG_LIKE_DIALOG - General Indicator

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

I_FLG_TESTRUN - General Indicator

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

EXPORTING Parameters details for FVD_CHARGE_API_GETDETAIL

E_TAB_RBOBEPP_API - Interface Structure and Control Data Charges

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

E_TAB_BAPIERR - Table Types for Error Handling

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

EXCEPTIONS details

FATAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_CHARGE_API_GETDETAIL 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_fatal_error  TYPE STRING, "   
lv_i_str_bo_key  TYPE FVD_BO_KEY, "   
lv_e_tab_rbobepp_api  TYPE TRTY_RBOBEPP_API, "   
lv_e_tab_bapierr  TYPE BAPIERR_T, "   
lv_i_flg_like_dialog  TYPE FLAG, "   
lv_i_flg_testrun  TYPE FLAG. "   

  CALL FUNCTION 'FVD_CHARGE_API_GETDETAIL'  "Get Detail
    EXPORTING
         I_STR_BO_KEY = lv_i_str_bo_key
         I_FLG_LIKE_DIALOG = lv_i_flg_like_dialog
         I_FLG_TESTRUN = lv_i_flg_testrun
    IMPORTING
         E_TAB_RBOBEPP_API = lv_e_tab_rbobepp_api
         E_TAB_BAPIERR = lv_e_tab_bapierr
    EXCEPTIONS
        FATAL_ERROR = 1
. " FVD_CHARGE_API_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM FVD_CHARGE_API_GETDETAIL

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!