SAP CRM_SSC_SET_TABSTR_DATA Function Module for









CRM_SSC_SET_TABSTR_DATA is a standard crm ssc set tabstr data 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 crm ssc set tabstr data FM, simply by entering the name CRM_SSC_SET_TABSTR_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_SSC_SET_TABSTR_DATA 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 'CRM_SSC_SET_TABSTR_DATA'"
EXPORTING
IV_GENER_TFCODE = "Screens, Function Code That Triggered PAI
IV_DYNNR = "ABAP Program: Number of Current Screen
IV_IDENT = "

IMPORTING
EV_FUNCT_TFCODE = "Screens, Function Code That Triggered PAI

EXCEPTIONS
INVALID_INPUT_DATA = 1 CUST_DATA_INCONS = 2
.



IMPORTING Parameters details for CRM_SSC_SET_TABSTR_DATA

IV_GENER_TFCODE - Screens, Function Code That Triggered PAI

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

IV_DYNNR - ABAP Program: Number of Current Screen

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

IV_IDENT -

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

EXPORTING Parameters details for CRM_SSC_SET_TABSTR_DATA

EV_FUNCT_TFCODE - Screens, Function Code That Triggered PAI

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

EXCEPTIONS details

INVALID_INPUT_DATA -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CUST_DATA_INCONS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CRM_SSC_SET_TABSTR_DATA 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_ev_funct_tfcode  TYPE SYUCOMM, "   
lv_iv_gener_tfcode  TYPE SYUCOMM, "   
lv_invalid_input_data  TYPE SYUCOMM, "   
lv_iv_dynnr  TYPE SYDYNNR, "   
lv_cust_data_incons  TYPE SYDYNNR, "   
lv_iv_ident  TYPE CRMT_SSC_TSCTRL_IDENT. "   

  CALL FUNCTION 'CRM_SSC_SET_TABSTR_DATA'  "
    EXPORTING
         IV_GENER_TFCODE = lv_iv_gener_tfcode
         IV_DYNNR = lv_iv_dynnr
         IV_IDENT = lv_iv_ident
    IMPORTING
         EV_FUNCT_TFCODE = lv_ev_funct_tfcode
    EXCEPTIONS
        INVALID_INPUT_DATA = 1
        CUST_DATA_INCONS = 2
. " CRM_SSC_SET_TABSTR_DATA




ABAP code using 7.40 inline data declarations to call FM CRM_SSC_SET_TABSTR_DATA

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!