In Data Services 4.2 SP2, 4.2 SP1 Patch 5, 4.1 SP3 Patch 2 and later Data Services will first attempt to use the /SAPDS/* functions included with Netweaver. In Data Services 4.0, the the name was changed to /BODS/* and they were installed into the /BODS/BODS namespace/function group. Z_AW_ABAP_INSTALL_AND_RUN) The Z at the beginning was necessary because SAP deemed the functions as custom, and custom objects in SAP need to either start with a Z or a Y. In Data Services 3.x the functions were named Z_AW* and installed under the ZAW0 namespace/function group by default. To see what parameters to use for each function, you can do an RFC_TRACE=3 To examine the functions and their descriptions or to test functionality go into se37, type Z_AW*, /BODS/*, or /SAPDS/* and hit F4 and choose the function you want to test.įunction Names and descriptions are displayed and grouped by namespace/function group. The function /SAPDS/RFC_ABAP_INSTALL_AND_RUN is called by al_engine when a job is set to generate and execute and the ABAP code needs to be uploaded and ran on the fly. For example, the function /SAPDS/TABLE_IMPORT is called by Data Services Designer when importing an SAP table in designer, to get the table metadata. Each function provides a specific purpose and is called when needed by the engine or designer. Data Services will call these functions on the SAP server to get the data or metadata to complete it's task. In order for Data Services to operate with SAP systems, the SAP Data Services functions need to be available on an SAP system (ECC, BW, CRM.