Configure the SAP ERP system

This page describes how to configure your SAP system to use one of the SAPplugins in Cloud Data Fusion.

Install SAP plugin components in SAP using the SAP transport files

To use the SAP plugins in Cloud Data Fusion, add Remote Function Modules(RFMs) andAuthorization Roles in your SAP system. TheRFMs provide the extraction APIs called by the plugin in Cloud Data Fusion.

Download the transport file

You get the required SAP code and configurations through SAP transportfiles, which are archived in a zip file.

The transport zip file is available for download when youdeploy SAP plugins in the Cloud Data Fusion Hub.

The transport zip file contains two zip files:

  • Thecofile, which has the following naming convention:KSIX_DIGITS.SID
  • Thedata file, which has the following naming convention:RSIX_DIGITS.SID

Example:

ODP

The following example shows the files in the SAP ODP transport zip file:

Zip filenameTransport request IDCofileDatafileContent
Google_CDF_connector_SAP_ODP.zipSIDK123456K123456.SIDR123456.SIDSAP RFMs in a Google namespace
Authorization_Role_SAP_ODP.zipSIDK123456K123456.SIDR123456.SIDAuthorization Role

Table

The following example shows the files in the SAP Table transport zip file:

Zip filenameTransport request IDCofileDatafileContent
SAP_TABLE_READER_TR.zipSIDK123456K123456.SIDR123456.SIDSAP RFMs in a Google namespace

Import the SAP transport files

To install the SAP transports, follow these steps:

  1. Sign in to the operating system of the SAP Instance.
  2. To get the path for theDIR_TRANS folder, use the SAP transaction codeAL11. Typically, the path is/usr/sap/trans/.
  3. Copy the cofile to theDIR_TRANS/cofiles folder.
  4. Copy the data files to theDIR_TRANS/data folder.
  5. Set the User and Group of data and cofiles folders and files toSIDadm andsapsys.

An SAP administrator can import the transport request files by using the SAPtransport management system or the operating system command line:

Transport management

  1. Sign in to the SAP system as an SAP administrator.
  2. Enter the transactionSTMS.
  3. ClickOverview> Imports.
  4. In theQueue column, double-click the current SID.
  5. ClickExtras> Other Requests> Add.
  6. Select the transport request ID and clickContinue.
  7. Select the transport request in the import queue and clickRequest> Import.
  8. Enter the client number.
  9. On theOptions tab, selectOverwrite Originals andIgnoreInvalid Component Version (if available).
  10. Optional: To plan for SAP system upgrades and backup restorations, youcan choose to import the transports again later. ClickLeaveTransports Requests in Queue for Later Import andImport TransportRequests Again.
  11. ClickContinue.
  12. Verify that the function module and authorization roles were importedsuccessfully by using transactions, such asSE80 andPFCG.

SAP CLI

  1. Sign in to the SAP system as an SAP administrator.

  2. Add requests to the import buffer:

    tp addtobufferTRANSPORT_REQUEST_IDSID

    Replace the following:

    • TRANSPORT_REQUEST_IDwith the transport request ID
    • SID with the SAPID

    Example:tp addtobuffer IB1K903958 DD1

  3. Import the transport requests:

    tp importTRANSPORT_REQUEST_IDSID client=CLIENT_NUMBER U1238

    ReplaceCLIENT_NUMBER withthe client number.

    Example:tp import IB1K903958 DD1 client=800 U1238

    Note:U1238 indicates to set the options described in steps 9-10 in the Transport management tab on this page. The numbers indicate the corresponding option order number in the SAP user interface, which might vary by system. The numbers must be adjusted by an SAP administrator.

  4. Verify that the function module and authorization roles were importedsuccessfully by using appropriate transactions, such asSE80 andPFCG.

After the transport is imported into the SAP system, the following SAPobjects are created:

Set up authorizations in SAP

To set up user authorizations in SAP, either assign the ODP authorization rolethat's included in the transport file, or manually create an authorization role.

From Transport

SAP ODP plugin

In SAP, assign the Authorization Role,/GOOG/ODP_AUTH, which is included inthe SAP transports you download when you deploy the SAP ODP plugin.

Create

To create the Authorization Role manually, follow these steps:

  1. In the SAP GUI, enter the transaction codePFCG. TheRoleMaintenance window opens.
  2. In theRole field, enter a name for the role—for example,zcdf_role.
  3. ClickSingle Role. TheCreate Roles window opens.
  4. In theDescription field, enter a description—for example,Authorizations for ODP plugin orAuthorizations for Table plugin.
  5. ClickSave.
  6. Click theAuthorizations tab. The title of the window changes toChange Roles.
  7. In theEdit Authorization Data and Generate Profiles section, clickChange Authorization Data.TheChoose Template window opens.
  8. ClickDo not select templates. TheChange role: Authorizationswindow opens.
  9. ClickManually.
  10. Provide the authorizations shown in the following SAP Authorizationtable.
  11. ClickSave.
  12. To activate the Authorization Role, click theGenerate icon.

SAP Authorizations include the following:

ODP

Note: To restrict a user from running ODP pipelines with specificDataSources, for authorization object S_RO_OSOA, provide the requiredDataSource names in OLTPSOURCE (for example,2LIS_02_ITM,0MATERIAL_ATTR). Don't use*.

The following authorizations apply for the ODP plugin:

Object classObject class textAuthorization objectAuthorization object textAuthorizationTextValue
AAABCross-application Authorization ObjectsS_RFCAuthorization Check for RFC AccessACTVTActivity16
AAABCross-application Authorization ObjectsS_RFCAuthorization Check for RFC AccessRFC_NAMEName of RFC object to which access is allowed
  • /GOOG/CDF_ODP_FG
  • /GOOG/ODP_DS_EXTRACT_DATA
  • /GOOG/ODP_DS_FETCH_DATA
  • /GOOG/ODP_DS_METADATA
  • DDIF_FIELDINFO_GET
  • RFCPING
  • RFC_GET_FUNCTION_INTERFACE
  • RODPS_REPL_ODP_CLOSE
  • RODPS_REPL_SOURCES_GET_LIST
  • SAPTUNE_GET_SUMMARY_STATISTIC
  • TH_WPINFO
AAABCross-application Authorization ObjectsS_RFCAuthorization Check for RFC AccessRFC_TYPEType of RFC object to which access is allowed
  • FUGR
  • FUNC
AAABCross-application Authorization ObjectsS_TCODETransaction Code Check at Transaction StartTCDTransaction CodeSM50
BC_ABasis: AdministrationS_ADMI_FCDSystem AuthorizationsS_ADMI_FCDSystem administration function
  • PADM
  • ST0R
BC_ABasis: AdministrationS_BTCH_ADMBackground Processing: Background AdministratorBTCADMINBackground Administrator IDY
BC_ABasis: AdministrationS_BTCH_JOBBackground Processing: Operations on Background JobsJOBACTIONJob operationsRELE
BC_ABasis: AdministrationS_BTCH_JOBBackground Processing: Operations on Background JobsJOBGROUPSummary of jobs for a group''
MM_EMaterials Management: PurchasingM_BEST_BSADocument Type in Purchase OrderACTVTActivity03
MM_EMaterials Management: PurchasingM_BEST_BSADocument Type in Purchase OrderBSARTPurchasing Document Type*
ROAuthorizations: BW Service APIS_RO_OSOASAP DataSource AuthorizationsACTVTActivity03
ROAuthorizations: BW Service APIS_RO_OSOASAP DataSource AuthorizationsOLTPSOURCEDataSource (OSOA/OSOD)*
ROAuthorizations: BW Service APIS_RO_OSOASAP DataSource AuthorizationsOSOAAPCOApplication Component of a DataSource (OSOA/OSOD)*
ROAuthorizations: BW Service APIS_RO_OSOASAP DataSource AuthorizationsOSOAPARTSubobject for DataSourceDATA

Table

The following authorizations apply for the Table plugin:

Object classObject class textAuthorization objectAuthorization object textAuthorizationTextValue
AAABCross-application Authorization ObjectsS_RFCCross-application Authorization ObjectsACTVTActivity16
AAABCross-application Authorization ObjectsS_RFCAuthorization Check for RFC AccessRFC_NAMEName of RFC object to which access is allowed
  • /GOOG/RFC_READ_TABLE
  • DDIF_FIELDINFO_GET
  • RFC_GET_FUNCTION_INTERFACE
  • RFCPING
  • SAPTUNE_GET_SUMMARY_STATISTIC
  • TH_WPINFO
AAABCross-application Authorization ObjectsS_RFCCross-application Authorization ObjectsRFC_TYPEType of RFC object to which access is allowedFUNC
AAABCross-application Authorization ObjectsS_TCODETransaction Code Check at Transaction StartTCDTransaction CodeSM50
BC_ABasis: AdministrationS_ADMI_FCDSystem AuthorizationsS_ADMI_FCDSystem administration functionST0R
BC_ABasis: AdministrationS_TABU_NAMTable Access by Generic Standard ToolsACTVTActivity03
BC_ABasis: AdministrationS_TABU_NAMTable Access by Generic Standard ToolsTABLETable Name*

Set up the SAP Java Connector

Download the following SAP Java Connector (SAP JCo) artifacts.The minimum supported JCo version is3.0.20.

  • One platform-independent (sapjco3.jar)
  • One platform-dependent (libsapjco3.so on Unix)

Copy the files to the Cloud Storage bucket.

For ODP: Activate data sources for extraction

To extract the data, a DataSource must be activated in the source SAP system. Toactivate a DataSource in SAP, follow these steps:

  1. Sign into the SAP system.
  2. Go to the transaction codeRSA5.

  3. Expand theDataSources list.

    1. Open the CDS view in the SAP CDS Editor.

    2. In the CDS view, look for the following annotations:

      • @Analytics.dataCategory
      • @Analytics.dataExtraction.enabled

      If the CDS view has both of these annotations, then it's exposed for ODPdata extraction. Without them, it isn't exposed.

  4. ClickSearch.

  5. Provide the DataSource name and click

  6. If the search is successful, the DataSource appears in the result list.

    Select the DataSource name and click

  7. Select the DataSource and clickActivate DataSources.

  8. In theCreate Object Directory Entry dialog, enter the Package name andclickSave.

  9. In thePrompt for transportable workbench request dialog, enter theTransport Number in theRequest field. Click

    The selected DataSource is activated in SAP.

Check that the DataSource is exposed for extraction

  1. Sign in to the SAP system.
  2. Go to t-codeSE16N.
  3. Enter the table name,ROOSATTR, and enter the DataSource name inOLTPSOURCE.
  4. ClickExecute or press F8.
  5. If theEXPOSE_EXTERNAL field has anX, the DataSource is exposed andready for extraction.

If the DataSource doesn't appear in theROOSATTR table, or theEXPOSE_EXTERNAL field is blank, follow these steps to expose the DataSourcefor ODP extraction:

  1. Sign in to the SAP system.
  2. Go to t-codeSA38.
  3. Enter the program name,RODPS_OS_EXPOSE, and clickExecute.
  4. Enter the DataSource name and clickRelease DataSource.
  5. Save the changes in the transport.

What's next

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-15 UTC.