SAP SSF_OPEN Function Module for
SSF_OPEN is a standard ssf open 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 ssf open FM, simply by entering the name SSF_OPEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: STXBE
Program Name: SAPLSTXBE
Main Program: SAPLSTXBE
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SSF_OPEN 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 'SSF_OPEN'".
EXPORTING
* ARCHIVE_PARAMETERS = "ImageLink structure
* USER_SETTINGS = 'X' "Checkbox (yes or no)
* MAIL_SENDER = "Structure for Object ID
* MAIL_RECIPIENT = "Structure for Object ID
* MAIL_APPL_OBJ = "Structure for Object ID
* OUTPUT_OPTIONS = "SAP Smart Forms: Smart Composer (transfer) options
* CONTROL_PARAMETERS = "Smart Forms: Control structure
IMPORTING
JOB_OUTPUT_OPTIONS = "Smart Forms: Return value at start of form printing
EXCEPTIONS
FORMATTING_ERROR = 1 INTERNAL_ERROR = 2 SEND_ERROR = 3 USER_CANCELED = 4
IMPORTING Parameters details for SSF_OPEN
ARCHIVE_PARAMETERS - ImageLink structure
Data type: ARC_PARAMSOptional: Yes
Call by Reference: No ( called with pass by value option)
USER_SETTINGS - Checkbox (yes or no)
Data type: TDBOOLDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MAIL_SENDER - Structure for Object ID
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
MAIL_RECIPIENT - Structure for Object ID
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
MAIL_APPL_OBJ - Structure for Object ID
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
OUTPUT_OPTIONS - SAP Smart Forms: Smart Composer (transfer) options
Data type: SSFCOMPOPOptional: Yes
Call by Reference: No ( called with pass by value option)
CONTROL_PARAMETERS - Smart Forms: Control structure
Data type: SSFCTRLOPOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SSF_OPEN
JOB_OUTPUT_OPTIONS - Smart Forms: Return value at start of form printing
Data type: SSFCRESOPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FORMATTING_ERROR -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR - Internal Error
Data type:Optional: No
Call by Reference: Yes
SEND_ERROR -
Data type:Optional: No
Call by Reference: Yes
USER_CANCELED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SSF_OPEN 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_formatting_error | TYPE STRING, " | |||
lv_archive_parameters | TYPE ARC_PARAMS, " | |||
lv_job_output_options | TYPE SSFCRESOP, " | |||
lv_user_settings | TYPE TDBOOL, " 'X' | |||
lv_internal_error | TYPE TDBOOL, " | |||
lv_send_error | TYPE TDBOOL, " | |||
lv_mail_sender | TYPE SWOTOBJID, " | |||
lv_user_canceled | TYPE SWOTOBJID, " | |||
lv_mail_recipient | TYPE SWOTOBJID, " | |||
lv_mail_appl_obj | TYPE SWOTOBJID, " | |||
lv_output_options | TYPE SSFCOMPOP, " | |||
lv_control_parameters | TYPE SSFCTRLOP. " |
  CALL FUNCTION 'SSF_OPEN' " |
EXPORTING | ||
ARCHIVE_PARAMETERS | = lv_archive_parameters | |
USER_SETTINGS | = lv_user_settings | |
MAIL_SENDER | = lv_mail_sender | |
MAIL_RECIPIENT | = lv_mail_recipient | |
MAIL_APPL_OBJ | = lv_mail_appl_obj | |
OUTPUT_OPTIONS | = lv_output_options | |
CONTROL_PARAMETERS | = lv_control_parameters | |
IMPORTING | ||
JOB_OUTPUT_OPTIONS | = lv_job_output_options | |
EXCEPTIONS | ||
FORMATTING_ERROR = 1 | ||
INTERNAL_ERROR = 2 | ||
SEND_ERROR = 3 | ||
USER_CANCELED = 4 | ||
. " SSF_OPEN |
ABAP code using 7.40 inline data declarations to call FM SSF_OPEN
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.DATA(ld_user_settings) | = 'X'. | |||
Search for further information about these or an SAP related objects