SAP ETP_STANDALONE_ADD_TEXT Function Module for NOTRANSL: EasytaskPlanning: Text zu Task/Subtask hinzufügen
ETP_STANDALONE_ADD_TEXT is a standard etp standalone add text SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: EasytaskPlanning: Text zu Task/Subtask hinzufügen 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 etp standalone add text FM, simply by entering the name ETP_STANDALONE_ADD_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ETP_STANDALONE
Program Name: SAPLETP_STANDALONE
Main Program: SAPLETP_STANDALONE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ETP_STANDALONE_ADD_TEXT 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 'ETP_STANDALONE_ADD_TEXT'"NOTRANSL: EasytaskPlanning: Text zu Task/Subtask hinzufügen.
EXPORTING
ID_NUMB = "Task Number
ID_SUBNUMB = "Sub Task No.
ID_TEXTTYPE = "
* ID_TXT_NUM = "
* ID_CREATOR = SY-UNAME "
IMPORTING
FLAG_OK = "
TABLES
TI_LINES = "
TE_RETURN = "Messages
IMPORTING Parameters details for ETP_STANDALONE_ADD_TEXT
ID_NUMB - Task Number
Data type: ETP_TASKS-NUMBOptional: No
Call by Reference: No ( called with pass by value option)
ID_SUBNUMB - Sub Task No.
Data type: ETP_TASKS-SUBNUMBOptional: No
Call by Reference: No ( called with pass by value option)
ID_TEXTTYPE -
Data type: ETP_TEXTHEADER-TYPE_TEXTOptional: No
Call by Reference: No ( called with pass by value option)
ID_TXT_NUM -
Data type: ETP_TEXTHEADER-TXT_NUMOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_CREATOR -
Data type: ETP_PARTNER-PARNRDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ETP_STANDALONE_ADD_TEXT
FLAG_OK -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ETP_STANDALONE_ADD_TEXT
TI_LINES -
Data type: ETP_LINESOptional: No
Call by Reference: No ( called with pass by value option)
TE_RETURN - Messages
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ETP_STANDALONE_ADD_TEXT 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_flag_ok | TYPE C, " | |||
lv_id_numb | TYPE ETP_TASKS-NUMB, " | |||
lt_ti_lines | TYPE STANDARD TABLE OF ETP_LINES, " | |||
lt_te_return | TYPE STANDARD TABLE OF BAPIRETURN1, " | |||
lv_id_subnumb | TYPE ETP_TASKS-SUBNUMB, " | |||
lv_id_texttype | TYPE ETP_TEXTHEADER-TYPE_TEXT, " | |||
lv_id_txt_num | TYPE ETP_TEXTHEADER-TXT_NUM, " | |||
lv_id_creator | TYPE ETP_PARTNER-PARNR. " SY-UNAME |
  CALL FUNCTION 'ETP_STANDALONE_ADD_TEXT' "NOTRANSL: EasytaskPlanning: Text zu Task/Subtask hinzufügen |
EXPORTING | ||
ID_NUMB | = lv_id_numb | |
ID_SUBNUMB | = lv_id_subnumb | |
ID_TEXTTYPE | = lv_id_texttype | |
ID_TXT_NUM | = lv_id_txt_num | |
ID_CREATOR | = lv_id_creator | |
IMPORTING | ||
FLAG_OK | = lv_flag_ok | |
TABLES | ||
TI_LINES | = lt_ti_lines | |
TE_RETURN | = lt_te_return | |
. " ETP_STANDALONE_ADD_TEXT |
ABAP code using 7.40 inline data declarations to call FM ETP_STANDALONE_ADD_TEXT
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."SELECT single NUMB FROM ETP_TASKS INTO @DATA(ld_id_numb). | ||||
"SELECT single SUBNUMB FROM ETP_TASKS INTO @DATA(ld_id_subnumb). | ||||
"SELECT single TYPE_TEXT FROM ETP_TEXTHEADER INTO @DATA(ld_id_texttype). | ||||
"SELECT single TXT_NUM FROM ETP_TEXTHEADER INTO @DATA(ld_id_txt_num). | ||||
"SELECT single PARNR FROM ETP_PARTNER INTO @DATA(ld_id_creator). | ||||
DATA(ld_id_creator) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects