SAP FTR_SUBSCR_CREATE_SUBSCRMGR Function Module for Generate Subscreen Manager cl_ftr_subscr_flows
FTR_SUBSCR_CREATE_SUBSCRMGR is a standard ftr subscr create subscrmgr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generate Subscreen Manager cl_ftr_subscr_flows 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 ftr subscr create subscrmgr FM, simply by entering the name FTR_SUBSCR_CREATE_SUBSCRMGR into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_SUBSCR
Program Name: SAPLFTR_SUBSCR
Main Program: SAPLFTR_SUBSCR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_SUBSCR_CREATE_SUBSCRMGR 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 'FTR_SUBSCR_CREATE_SUBSCRMGR'"Generate Subscreen Manager cl_ftr_subscr_flows.
EXPORTING
PI_OREF_GUI = "
EXCEPTIONS
CREATION_FAILED = 1
IMPORTING Parameters details for FTR_SUBSCR_CREATE_SUBSCRMGR
PI_OREF_GUI -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CREATION_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTR_SUBSCR_CREATE_SUBSCRMGR 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_pi_oref_gui | TYPE STRING, " | |||
| lv_creation_failed | TYPE STRING. " |
|   CALL FUNCTION 'FTR_SUBSCR_CREATE_SUBSCRMGR' "Generate Subscreen Manager cl_ftr_subscr_flows |
| EXPORTING | ||
| PI_OREF_GUI | = lv_pi_oref_gui | |
| EXCEPTIONS | ||
| CREATION_FAILED = 1 | ||
| . " FTR_SUBSCR_CREATE_SUBSCRMGR | ||
ABAP code using 7.40 inline data declarations to call FM FTR_SUBSCR_CREATE_SUBSCRMGR
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