SAP /1BCDWB/SF00000002 Function Module for Smart Form ZSF_THAI
/1BCDWB/SF00000002 is a standard /1bcdwb/sf00000002 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Smart Form ZSF_THAI 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 /1bcdwb/sf00000002 FM, simply by entering the name /1BCDWB/SF00000002 into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWB/SF00000002
Program Name: /1BCDWB/SAPLSF00000002
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function /1BCDWB/SF00000002 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 '/1BCDWB/SF00000002'"Smart Form ZSF_THAI.
EXPORTING
* ARCHIVE_INDEX = "
* ARCHIVE_INDEX_TAB = "
* ARCHIVE_PARAMETERS = "
* CONTROL_PARAMETERS = "
* MAIL_APPL_OBJ = "
* MAIL_RECIPIENT = "
* MAIL_SENDER = "
* OUTPUT_OPTIONS = "
* USER_SETTINGS = 'X' "
IMPORTING
DOCUMENT_OUTPUT_INFO = "
JOB_OUTPUT_INFO = "
JOB_OUTPUT_OPTIONS = "
EXCEPTIONS
FORMATTING_ERROR = 1 INTERNAL_ERROR = 2 SEND_ERROR = 3 USER_CANCELED = 4
IMPORTING Parameters details for /1BCDWB/SF00000002
ARCHIVE_INDEX -
Data type: TOA_DARAOptional: Yes
Call by Reference: No ( called with pass by value option)
ARCHIVE_INDEX_TAB -
Data type: TSFDARAOptional: Yes
Call by Reference: No ( called with pass by value option)
ARCHIVE_PARAMETERS -
Data type: ARC_PARAMSOptional: Yes
Call by Reference: No ( called with pass by value option)
CONTROL_PARAMETERS -
Data type: SSFCTRLOPOptional: Yes
Call by Reference: No ( called with pass by value option)
MAIL_APPL_OBJ -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
MAIL_RECIPIENT -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
MAIL_SENDER -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
OUTPUT_OPTIONS -
Data type: SSFCOMPOPOptional: Yes
Call by Reference: No ( called with pass by value option)
USER_SETTINGS -
Data type: TDBOOLDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /1BCDWB/SF00000002
DOCUMENT_OUTPUT_INFO -
Data type: SSFCRESPDOptional: No
Call by Reference: No ( called with pass by value option)
JOB_OUTPUT_INFO -
Data type: SSFCRESCLOptional: No
Call by Reference: No ( called with pass by value option)
JOB_OUTPUT_OPTIONS -
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: No ( called with pass by value option)
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SEND_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
USER_CANCELED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /1BCDWB/SF00000002 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_archive_index | TYPE TOA_DARA, " | |||
lv_formatting_error | TYPE TOA_DARA, " | |||
lv_document_output_info | TYPE SSFCRESPD, " | |||
lv_internal_error | TYPE SSFCRESPD, " | |||
lv_job_output_info | TYPE SSFCRESCL, " | |||
lv_archive_index_tab | TYPE TSFDARA, " | |||
lv_send_error | TYPE TSFDARA, " | |||
lv_archive_parameters | TYPE ARC_PARAMS, " | |||
lv_job_output_options | TYPE SSFCRESOP, " | |||
lv_user_canceled | TYPE SSFCRESOP, " | |||
lv_control_parameters | TYPE SSFCTRLOP, " | |||
lv_mail_appl_obj | TYPE SWOTOBJID, " | |||
lv_mail_recipient | TYPE SWOTOBJID, " | |||
lv_mail_sender | TYPE SWOTOBJID, " | |||
lv_output_options | TYPE SSFCOMPOP, " | |||
lv_user_settings | TYPE TDBOOL. " 'X' |
  CALL FUNCTION '/1BCDWB/SF00000002' "Smart Form ZSF_THAI |
EXPORTING | ||
ARCHIVE_INDEX | = lv_archive_index | |
ARCHIVE_INDEX_TAB | = lv_archive_index_tab | |
ARCHIVE_PARAMETERS | = lv_archive_parameters | |
CONTROL_PARAMETERS | = lv_control_parameters | |
MAIL_APPL_OBJ | = lv_mail_appl_obj | |
MAIL_RECIPIENT | = lv_mail_recipient | |
MAIL_SENDER | = lv_mail_sender | |
OUTPUT_OPTIONS | = lv_output_options | |
USER_SETTINGS | = lv_user_settings | |
IMPORTING | ||
DOCUMENT_OUTPUT_INFO | = lv_document_output_info | |
JOB_OUTPUT_INFO | = lv_job_output_info | |
JOB_OUTPUT_OPTIONS | = lv_job_output_options | |
EXCEPTIONS | ||
FORMATTING_ERROR = 1 | ||
INTERNAL_ERROR = 2 | ||
SEND_ERROR = 3 | ||
USER_CANCELED = 4 | ||
. " /1BCDWB/SF00000002 |
ABAP code using 7.40 inline data declarations to call FM /1BCDWB/SF00000002
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