SAP CRS_CLASS_SEND_TO_SERVER Function Module for NOTRANSL: Datentransfer zum SFA-Server: Klassen









CRS_CLASS_SEND_TO_SERVER is a standard crs class send to server 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: Datentransfer zum SFA-Server: Klassen 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 crs class send to server FM, simply by entering the name CRS_CLASS_SEND_TO_SERVER into the relevant SAP transaction such as SE37 or SE38.

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



Function CRS_CLASS_SEND_TO_SERVER 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 'CRS_CLASS_SEND_TO_SERVER'"NOTRANSL: Datentransfer zum SFA-Server: Klassen
  EXPORTING
   I_DOWNLOAD_HEADER =  "BAPI Structure for Downloading Header Data
*  I_MESSAGE_HEADER =  "BAPI Structure: Messages per Data Record
   I_KEYWORD_IN =  "Keyword for Customer Enhancements
   I_DESTINATION =  "RFC Destination Server System
   I_SERVER_RELEASE =  "SFA Release in Server System
   I_TRFC_QUEUE =  "Name of tRFC Queue

TABLES
*  TI_KEY_INFO =  "BAPI Structure: Key Information
*  TI_TEXTS =  "Texts
*  TI_OLD_TEXTS =  "Classes: Long Texts
*  TI_MESSAGES =  "BAPI Structure: Messages per Data Record
*  TI_OTHER_INFO =  "Container for 'Customer Exit' Parameter
*  TI_CLASS_HEADER =  "Class Header Data
*  TI_OLD_CLASS_HEADER =  "Class Header Data
*  TI_CHARACT =  "Characteristics of a Class
*  TI_OLD_CHARACT =  "Characteristics of a Class
*  TI_CATCHWORD =  "Classification System: Keywords
*  TI_OLD_CATCHWORD =  "Classification System: Keywords
.



IMPORTING Parameters details for CRS_CLASS_SEND_TO_SERVER

I_DOWNLOAD_HEADER - BAPI Structure for Downloading Header Data

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

I_MESSAGE_HEADER - BAPI Structure: Messages per Data Record

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

I_KEYWORD_IN - Keyword for Customer Enhancements

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

I_DESTINATION - RFC Destination Server System

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

I_SERVER_RELEASE - SFA Release in Server System

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

I_TRFC_QUEUE - Name of tRFC Queue

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

TABLES Parameters details for CRS_CLASS_SEND_TO_SERVER

TI_KEY_INFO - BAPI Structure: Key Information

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

TI_TEXTS - Texts

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

TI_OLD_TEXTS - Classes: Long Texts

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

TI_MESSAGES - BAPI Structure: Messages per Data Record

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

TI_OTHER_INFO - Container for 'Customer Exit' Parameter

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

TI_CLASS_HEADER - Class Header Data

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

TI_OLD_CLASS_HEADER - Class Header Data

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

TI_CHARACT - Characteristics of a Class

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

TI_OLD_CHARACT - Characteristics of a Class

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

TI_CATCHWORD - Classification System: Keywords

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

TI_OLD_CATCHWORD - Classification System: Keywords

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

Copy and paste ABAP code example for CRS_CLASS_SEND_TO_SERVER 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:
lt_ti_key_info  TYPE STANDARD TABLE OF BAPICRMKEY, "   
lv_i_download_header  TYPE BAPICRMDH2, "   
lt_ti_texts  TYPE STANDARD TABLE OF KLAT, "   
lt_ti_old_texts  TYPE STANDARD TABLE OF KLAT, "   
lt_ti_messages  TYPE STANDARD TABLE OF BAPICRMMSG, "   
lv_i_message_header  TYPE BAPICRMMSG, "   
lv_i_keyword_in  TYPE CRM_PARA-KEYWORD_IN, "   
lt_ti_other_info  TYPE STANDARD TABLE OF BAPIEXTC, "   
lv_i_destination  TYPE CRM_PARA-RFCSERVER, "   
lt_ti_class_header  TYPE STANDARD TABLE OF KLAH, "   
lv_i_server_release  TYPE CRM_PARA-SERVER_REL, "   
lt_ti_old_class_header  TYPE STANDARD TABLE OF KLAH, "   
lt_ti_charact  TYPE STANDARD TABLE OF KSML, "   
lv_i_trfc_queue  TYPE BAPICRMDH1-RFC_QUEUE, "   
lt_ti_old_charact  TYPE STANDARD TABLE OF KSML, "   
lt_ti_catchword  TYPE STANDARD TABLE OF SWOR, "   
lt_ti_old_catchword  TYPE STANDARD TABLE OF SWOR. "   

  CALL FUNCTION 'CRS_CLASS_SEND_TO_SERVER'  "NOTRANSL: Datentransfer zum SFA-Server: Klassen
    EXPORTING
         I_DOWNLOAD_HEADER = lv_i_download_header
         I_MESSAGE_HEADER = lv_i_message_header
         I_KEYWORD_IN = lv_i_keyword_in
         I_DESTINATION = lv_i_destination
         I_SERVER_RELEASE = lv_i_server_release
         I_TRFC_QUEUE = lv_i_trfc_queue
    TABLES
         TI_KEY_INFO = lt_ti_key_info
         TI_TEXTS = lt_ti_texts
         TI_OLD_TEXTS = lt_ti_old_texts
         TI_MESSAGES = lt_ti_messages
         TI_OTHER_INFO = lt_ti_other_info
         TI_CLASS_HEADER = lt_ti_class_header
         TI_OLD_CLASS_HEADER = lt_ti_old_class_header
         TI_CHARACT = lt_ti_charact
         TI_OLD_CHARACT = lt_ti_old_charact
         TI_CATCHWORD = lt_ti_catchword
         TI_OLD_CATCHWORD = lt_ti_old_catchword
. " CRS_CLASS_SEND_TO_SERVER




ABAP code using 7.40 inline data declarations to call FM CRS_CLASS_SEND_TO_SERVER

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 KEYWORD_IN FROM CRM_PARA INTO @DATA(ld_i_keyword_in).
 
 
"SELECT single RFCSERVER FROM CRM_PARA INTO @DATA(ld_i_destination).
 
 
"SELECT single SERVER_REL FROM CRM_PARA INTO @DATA(ld_i_server_release).
 
 
 
"SELECT single RFC_QUEUE FROM BAPICRMDH1 INTO @DATA(ld_i_trfc_queue).
 
 
 
 


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!