SAP JV_DECO_T004F_READ Function Module for Field status definition groups
JV_DECO_T004F_READ is a standard jv deco t004f read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Field status definition groups 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 jv deco t004f read FM, simply by entering the name JV_DECO_T004F_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: GVE1
Program Name: SAPLGVE1
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JV_DECO_T004F_READ 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 'JV_DECO_T004F_READ'"Field status definition groups.
EXPORTING
I_BUKRS = "
I_FSTAG = "
IMPORTING
E_T004F = "
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for JV_DECO_T004F_READ
I_BUKRS -
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_FSTAG -
Data type: T004F-FSTAGOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for JV_DECO_T004F_READ
E_T004F -
Data type: T004FOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JV_DECO_T004F_READ 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_e_t004f | TYPE T004F, " | |||
| lv_i_bukrs | TYPE T001-BUKRS, " | |||
| lv_not_found | TYPE T001, " | |||
| lv_i_fstag | TYPE T004F-FSTAG. " |
|   CALL FUNCTION 'JV_DECO_T004F_READ' "Field status definition groups |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_FSTAG | = lv_i_fstag | |
| IMPORTING | ||
| E_T004F | = lv_e_t004f | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " JV_DECO_T004F_READ | ||
ABAP code using 7.40 inline data declarations to call FM JV_DECO_T004F_READ
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 BUKRS FROM T001 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single FSTAG FROM T004F INTO @DATA(ld_i_fstag). | ||||
Search for further information about these or an SAP related objects