Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 

The SAP interfaces from Data Services Version 4.2 contains the following function modules as part of the standard installation. Some of the function modules in SAP are not RFC enabled. Since Data services utilises the RFC option to call FM in SAP, these additional components will be of help.

To check if these function modules have been installed in the corresponding SAP client, these can be checked using standard SAP transaction codes for Function Modules. One transaction code that can be used for this purpose is SE37. On the SAP Client GUI screen enter the transaction code SE37. This will open the "Function Builder: Initial Screen". Enter the details as shown below in Fig 1.

The list of function modules that are available under /SAPDS are shown below in the screen

These function modules are part of the Data Services package and hence RFC enabled. These function modules perform the same action as the corresponding standard function module (where applicable). Below is the list of the 27 function modules that was listed in the repository.

Function Module Description
/SAPDS/RS_BASISDataServices Base Functions
/SAPDS/ABAP_RUNDataServices: Execute existing ABAP
/SAPDS/AUTH_IMPORTDataServices: Import authorizations
/SAPDS/COLUMN_SEARCHDataServices: column search
/SAPDS/DATA_PROFILEDataServices: column profiling for data preview
/SAPDS/EXTRACTOR_IMPORTDataServices: Import Extractor metadata
/SAPDS/EXTRACTOR_NAVIGATEDataServices: Navigate through list of Extractors
/SAPDS/EXTRACTOR_SEARCHDataServices: Search for an Extractor
/SAPDS/FILE_ROWCOUNTDataServices: Set and get the total row count for the DS transported file
/SAPDS/FUNCTION_GETDataServices: Get metadata of functions
/SAPDS/GET_VERSIONDataServices: Get versions of all functions
/SAPDS/IDOC_IMPORTDataServices: Import IDOC metadata
/SAPDS/IDOC_SEARCHDataServices: Search IDOC by name
/SAPDS/JOB_LOGDataServices: Get the log of a background job
/SAPDS/JOB_RUNDataServices: Run a DS ABAP in background
/SAPDS/JOB_STATUSDataServices: Check the background job status
/SAPDS/READ_TEXTDataServices: SAPScript: Read Text
/SAPDS/RFC_ABAP_INSTALL_RUNDataServices: Enables to run DS generated abaps in development(!) systems
/SAPDS/RFC_READ_EXTRACTORDataServices: Read Extractor data
/SAPDS/RFC_READ_TABLEDataServices: Read ABAP table data
/SAPDS/RFC_READ_TABLE2DataServices: Read Table option 2
/SAPDS/RFC_READ_TABLE_FILEDataServices: Read Table option 3
/SAPDS/RFC_STREAM_READ_TABLEDataServices: Read table via streaming approach
/SAPDS/SYNTAX_CHECKDataServices: Allow DS generated abap to by checked in dev(!)
/SAPDS/TABLE_IMPORTDataServices: Get table metadata
/SAPDS/TABLE_SEARCHDataServices: Search for a table by name
/SAPDS/TEXTSDataServices: Get text entries
/SAPDS/UPLOADDataServices: Upload and install a DS generated ABAP in dev(!)

A very useful FM in this category is "/SAPDS/READ_TEXT". Retrieving the long text entries for SAP CRM objects using the READ_TEXT function module via BODS is not possible since READ_TEXT function module is not RFC enabled. However the "/SAPDS/READ_TEXT" is RFC enabled and performs the same task as the original READ_TEXT function module.

Labels in this area