SAP ISH_N2_TBS_SM_TRANS Function Module for









ISH_N2_TBS_SM_TRANS is a standard ish n2 tbs sm trans 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 ish n2 tbs sm trans FM, simply by entering the name ISH_N2_TBS_SM_TRANS into the relevant SAP transaction such as SE37 or SE38.

Function Group: N2LTE_TBS_SET
Program Name: SAPLN2LTE_TBS_SET
Main Program: SAPLN2LTE_TBS_SET
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISH_N2_TBS_SM_TRANS 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 'ISH_N2_TBS_SM_TRANS'"
EXPORTING
I_N2DT_SETS = "

IMPORTING
CT_AFFECTED_TABS = "
CT_AFFECTED_ROWS = "

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for ISH_N2_TBS_SM_TRANS

I_N2DT_SETS -

Data type: N2DT_SETS
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISH_N2_TBS_SM_TRANS

CT_AFFECTED_TABS -

Data type: TR_OBJECTS
Optional: No
Call by Reference: Yes

CT_AFFECTED_ROWS -

Data type: TR_KEYS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISH_N2_TBS_SM_TRANS 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_error  TYPE STRING, "   
lv_i_n2dt_sets  TYPE N2DT_SETS, "   
lv_ct_affected_tabs  TYPE TR_OBJECTS, "   
lv_ct_affected_rows  TYPE TR_KEYS. "   

  CALL FUNCTION 'ISH_N2_TBS_SM_TRANS'  "
    EXPORTING
         I_N2DT_SETS = lv_i_n2dt_sets
    IMPORTING
         CT_AFFECTED_TABS = lv_ct_affected_tabs
         CT_AFFECTED_ROWS = lv_ct_affected_rows
    EXCEPTIONS
        ERROR = 1
. " ISH_N2_TBS_SM_TRANS




ABAP code using 7.40 inline data declarations to call FM ISH_N2_TBS_SM_TRANS

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!