SAP SATCFR_READ_TEMPLATE Function Module for Read a template of ip message.
SATCFR_READ_TEMPLATE is a standard satcfr read template SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read a template of ip message. 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 satcfr read template FM, simply by entering the name SATCFR_READ_TEMPLATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SATCFR
Program Name: SAPLSATCFR
Main Program: SAPLSATCFR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SATCFR_READ_TEMPLATE 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 'SATCFR_READ_TEMPLATE'"Read a template of ip message..
EXPORTING
IM_TEMPLATE_KIND = "
IMPORTING
EX_DESCRIPTION = "
EXCEPTIONS
TEMPL_NOTFOUND = 1
IMPORTING Parameters details for SATCFR_READ_TEMPLATE
IM_TEMPLATE_KIND -
Data type: SATCTKINDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SATCFR_READ_TEMPLATE
EX_DESCRIPTION -
Data type: SATC_DESCR255Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TEMPL_NOTFOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SATCFR_READ_TEMPLATE 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_ex_description | TYPE SATC_DESCR255, " | |||
| lv_templ_notfound | TYPE SATC_DESCR255, " | |||
| lv_im_template_kind | TYPE SATCTKIND. " |
|   CALL FUNCTION 'SATCFR_READ_TEMPLATE' "Read a template of ip message. |
| EXPORTING | ||
| IM_TEMPLATE_KIND | = lv_im_template_kind | |
| IMPORTING | ||
| EX_DESCRIPTION | = lv_ex_description | |
| EXCEPTIONS | ||
| TEMPL_NOTFOUND = 1 | ||
| . " SATCFR_READ_TEMPLATE | ||
ABAP code using 7.40 inline data declarations to call FM SATCFR_READ_TEMPLATE
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