SAP FAA_V_T093BSN_PARVAL_BEFOR_EXP Function Module for
FAA_V_T093BSN_PARVAL_BEFOR_EXP is a standard faa v t093bsn parval befor exp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 faa v t093bsn parval befor exp FM, simply by entering the name FAA_V_T093BSN_PARVAL_BEFOR_EXP into the relevant SAP transaction such as SE37 or SE38.
Function Group: AA_CUS_PARAL_VAL
Program Name: SAPLAA_CUS_PARAL_VAL
Main Program: SAPLAA_CUS_PARAL_VAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FAA_V_T093BSN_PARVAL_BEFOR_EXP 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 'FAA_V_T093BSN_PARVAL_BEFOR_EXP'".
EXPORTING
IV_CLIENT = "
TABLES
TT_E071 = "
TT_E071K = "
IMPORTING Parameters details for FAA_V_T093BSN_PARVAL_BEFOR_EXP
IV_CLIENT -
Data type: SY-MANDTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FAA_V_T093BSN_PARVAL_BEFOR_EXP
TT_E071 -
Data type: E071Optional: No
Call by Reference: Yes
TT_E071K -
Data type: E071KOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FAA_V_T093BSN_PARVAL_BEFOR_EXP 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: | ||||
lt_tt_e071 | TYPE STANDARD TABLE OF E071, " | |||
lv_iv_client | TYPE SY-MANDT, " | |||
lt_tt_e071k | TYPE STANDARD TABLE OF E071K. " |
  CALL FUNCTION 'FAA_V_T093BSN_PARVAL_BEFOR_EXP' " |
EXPORTING | ||
IV_CLIENT | = lv_iv_client | |
TABLES | ||
TT_E071 | = lt_tt_e071 | |
TT_E071K | = lt_tt_e071k | |
. " FAA_V_T093BSN_PARVAL_BEFOR_EXP |
ABAP code using 7.40 inline data declarations to call FM FAA_V_T093BSN_PARVAL_BEFOR_EXP
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."SELECT single MANDT FROM SY INTO @DATA(ld_iv_client). | ||||
Search for further information about these or an SAP related objects