SAP J_1BEFD_T052_READ_SINGLE Function Module for T052 Single Read
J_1BEFD_T052_READ_SINGLE is a standard j 1befd t052 read single SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for T052 Single Read 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 j 1befd t052 read single FM, simply by entering the name J_1BEFD_T052_READ_SINGLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: J_1BEFD
Program Name: SAPLJ_1BEFD
Main Program: SAPLJ_1BEFD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1BEFD_T052_READ_SINGLE 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 'J_1BEFD_T052_READ_SINGLE'"T052 Single Read.
EXPORTING
I_ZTERM = "Terms of Payment Key
IMPORTING
ES_T052 = "Terms of Payment
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for J_1BEFD_T052_READ_SINGLE
I_ZTERM - Terms of Payment Key
Data type: DZTERMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for J_1BEFD_T052_READ_SINGLE
ES_T052 - Terms of Payment
Data type: T052Optional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1BEFD_T052_READ_SINGLE 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_es_t052 | TYPE T052, " | |||
| lv_i_zterm | TYPE DZTERM, " | |||
| lv_not_found | TYPE DZTERM. " |
|   CALL FUNCTION 'J_1BEFD_T052_READ_SINGLE' "T052 Single Read |
| EXPORTING | ||
| I_ZTERM | = lv_i_zterm | |
| IMPORTING | ||
| ES_T052 | = lv_es_t052 | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " J_1BEFD_T052_READ_SINGLE | ||
ABAP code using 7.40 inline data declarations to call FM J_1BEFD_T052_READ_SINGLE
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