Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to configure your SAP system to use one of the SAP
plugins 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) and Authorization Roles in your SAP system. The
RFMs 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 transport
files, which are archived in a zip file.
The cofile, which has the following naming convention:
KSIX_DIGITS.SID
The data 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 filename
Transport request ID
Cofile
Datafile
Content
Google_CDF_connector_SAP_ODP.zip
SIDK123456
K123456.SID
R123456.SID
SAP RFMs in a Google namespace
Authorization_Role_SAP_ODP.zip
SIDK123456
K123456.SID
R123456.SID
Authorization Role
Table
The following example shows the files in the SAP Table transport zip file:
Zip filename
Transport request ID
Cofile
Datafile
Content
SAP_TABLE_READER_TR.zip
SIDK123456
K123456.SID
R123456.SID
SAP RFMs in a Google namespace
Import the SAP transport files
To install the SAP transports, follow these steps:
Sign in to the operating system of the SAP Instance.
To get the path for the DIR_TRANS folder, use the SAP transaction code
AL11. Typically, the path is /usr/sap/trans/.
Copy the cofile to the DIR_TRANS/cofiles folder.
Copy the data files to the DIR_TRANS/data folder.
Set the User and Group of data and cofiles folders and files to
SIDadm and sapsys.
An SAP administrator can import the transport request files by using the SAP
transport management system or the operating system command line:
Transport management
Sign in to the SAP system as an SAP administrator.
Enter the transaction STMS.
Click Overview > Imports.
In the Queue column, double-click the current SID.
Click Extras > Other Requests > Add.
Select the transport request ID and click Continue.
Select the transport request in the import queue and click
Request > Import.
Enter the client number.
On the Options tab, select Overwrite Originals and Ignore
Invalid Component Version (if available).
Optional: To plan for SAP system upgrades and backup restorations, you
can choose to import the transports again later. Click Leave
Transports Requests in Queue for Later Import and Import Transport
Requests Again.
Click Continue.
Verify that the function module and authorization roles were imported
successfully by using transactions, such as SE80 and PFCG.
SAP CLI
Sign in to the SAP system as an SAP administrator.
Add requests to the import buffer:
tp addtobuffer TRANSPORT_REQUEST_IDSID
Replace the following:
TRANSPORT_REQUEST_ID
with the transport request ID
Verify that the function module and authorization roles were imported
successfully by using appropriate transactions, such as SE80 and
PFCG.
After the transport is imported into the SAP system, the following SAP
objects are created:
ODP plugin
RFC-enabled function modules:
/GOOG/ODP_DS_EXTRACT_DATA_V2
/GOOG/ODP_DS_FETCH_DATA_V2
/GOOG/ODP_DS_METADATA_V2
/GOOG/ODP_REPL_CLEANUP_V2
Authorization Role: /GOOG/ODP_AUTH
Table plugin
RFC-enabled function modules:
/GOOG/RFC_READ_TABLE
/GOOG/RFC_READ_TABLE_SNAPSHOT
/GOOG/RFC_READ_TABLE_CLEANUP
/GOOG/RFC_READ_TABLE_JOBSTATUS
/GOOG/RFC_TABLE_STAGE_READ
/GOOG/RFC_GET_PACKAGE_SIZE
/GOOG/RFC_GET_TABLE_LIST
Set up authorizations in SAP
To set up user authorizations in SAP, either assign the ODP authorization role
that'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 in
the SAP transports you download when you deploy the SAP ODP plugin.
Create
To create the Authorization Role manually, follow these steps:
In the SAP GUI, enter the transaction code PFCG. The Role
Maintenance window opens.
In the Role field, enter a name for the role—for example,
zcdf_role.
Click Single Role. The Create Roles window opens.
In the Description field, enter a description—for example,
Authorizations for ODP plugin or Authorizations for Table plugin.
Click Save.
Click the Authorizations tab. The title of the window changes to
Change Roles.
In the Edit Authorization Data and Generate Profiles section, click
editChange Authorization Data.
The Choose Template window opens.
Click Do not select templates. The Change role: Authorizations
window opens.
Click Manually.
Provide the authorizations shown in the following SAP Authorization
table.
Click Save.
To activate the Authorization Role, click the Generate icon.
SAP Authorizations include the following:
ODP
The following authorizations apply for the ODP plugin:
Object class
Object class text
Authorization object
Authorization object text
Authorization
Text
Value
AAAB
Cross-application Authorization Objects
S_RFC
Authorization Check for RFC Access
ACTVT
Activity
16
AAAB
Cross-application Authorization Objects
S_RFC
Authorization Check for RFC Access
RFC_NAME
Name 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
AAAB
Cross-application Authorization Objects
S_RFC
Authorization Check for RFC Access
RFC_TYPE
Type of RFC object to which access is allowed
FUGR
FUNC
AAAB
Cross-application Authorization Objects
S_TCODE
Transaction Code Check at Transaction Start
TCD
Transaction Code
SM50
BC_A
Basis: Administration
S_ADMI_FCD
System Authorizations
S_ADMI_FCD
System administration function
PADM
ST0R
BC_A
Basis: Administration
S_BTCH_ADM
Background Processing: Background
Administrator
BTCADMIN
Background Administrator ID
Y
BC_A
Basis: Administration
S_BTCH_JOB
Background Processing: Operations on Background
Jobs
JOBACTION
Job operations
RELE
BC_A
Basis: Administration
S_BTCH_JOB
Background Processing: Operations on Background
Jobs
JOBGROUP
Summary of jobs for a group
''
MM_E
Materials Management: Purchasing
M_BEST_BSA
Document Type in Purchase Order
ACTVT
Activity
03
MM_E
Materials Management: Purchasing
M_BEST_BSA
Document Type in Purchase Order
BSART
Purchasing Document Type
*
RO
Authorizations: BW Service API
S_RO_OSOA
SAP DataSource Authorizations
ACTVT
Activity
03
RO
Authorizations: BW Service API
S_RO_OSOA
SAP DataSource Authorizations
OLTPSOURCE
DataSource (OSOA/OSOD)
*
RO
Authorizations: BW Service API
S_RO_OSOA
SAP DataSource Authorizations
OSOAAPCO
Application Component of a DataSource
(OSOA/OSOD)
*
RO
Authorizations: BW Service API
S_RO_OSOA
SAP DataSource Authorizations
OSOAPART
Subobject for DataSource
DATA
Table
The following authorizations apply for the Table plugin:
To extract the data, a DataSource must be activated in the source SAP system. To
activate a DataSource in SAP, follow these steps:
Sign into the SAP system.
Go to the transaction code RSA5.
Expand the DataSources list.
Open the CDS view in the SAP CDS Editor.
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 ODP
data extraction. Without them, it isn't exposed.
Click Search.
Provide the DataSource name and click check_circleEnter.
If the search is successful, the DataSource appears in the result list.
Select the DataSource name and click check_circleEnter.
Select the DataSource and click Activate DataSources.
In the Create Object Directory Entry dialog, enter the Package name and
click Save.
In the Prompt for transportable workbench request dialog, enter the
Transport Number in the Request field. Click check_circleEnter.
The selected DataSource is activated in SAP.
Check that the DataSource is exposed for extraction
Sign in to the SAP system.
Go to t-code SE16N.
Enter the table name, ROOSATTR, and enter the DataSource name in
OLTPSOURCE.
Click Execute or press F8.
If the EXPOSE_EXTERNAL field has an X, the DataSource is exposed and
ready for extraction.
If the DataSource doesn't appear in the ROOSATTR table, or the
EXPOSE_EXTERNAL field is blank, follow these steps to expose the DataSource
for ODP extraction:
Sign in to the SAP system.
Go to t-code SA38.
Enter the program name, RODPS_OS_EXPOSE, and click Execute.
Enter the DataSource name and click Release DataSource.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThis guide outlines the process of configuring an SAP system for use with SAP plugins in Cloud Data Fusion, focusing on installing SAP transport files and setting up necessary authorizations.\u003c/p\u003e\n"],["\u003cp\u003eSAP transport files, which contain the required Remote Function Modules (RFMs) and configurations, are available for download after deploying SAP plugins in the Cloud Data Fusion Hub, with specific naming conventions for the cofile and data files.\u003c/p\u003e\n"],["\u003cp\u003eThe installation process involves copying the cofile and data files into the \u003ccode\u003eDIR_TRANS/cofiles\u003c/code\u003e and \u003ccode\u003eDIR_TRANS/data\u003c/code\u003e folders, respectively, and then using either the SAP transport management system or the command-line interface to import the transport requests.\u003c/p\u003e\n"],["\u003cp\u003eSetting up user authorizations in SAP involves assigning a provided authorization role like \u003ccode\u003e/GOOG/ODP_AUTH\u003c/code\u003e, or creating a custom one through transaction code \u003ccode\u003ePFCG\u003c/code\u003e, with detailed authorizations provided for both the ODP and Table plugins.\u003c/p\u003e\n"],["\u003cp\u003eThe document specifies the minimum JCo version needed and the process to download and install, and steps to activate DataSources for extraction.\u003c/p\u003e\n"]]],[],null,["# Configure the SAP ERP system\n\nThis page describes how to configure your SAP system to use one of the SAP\nplugins in Cloud Data Fusion.\n\nInstall SAP plugin components in SAP using the SAP transport files\n------------------------------------------------------------------\n\nTo use the SAP plugins in Cloud Data Fusion, add Remote Function Modules\n(RFMs) and [Authorization Roles](#sap-authorization) in your SAP system. The\nRFMs provide the extraction APIs called by the plugin in Cloud Data Fusion.\n\n### Download the transport file\n\nYou get the required SAP code and configurations through SAP transport\nfiles, which are archived in a zip file.\n\nThe transport zip file is available for download when you\n[deploy SAP plugins in the Cloud Data Fusion Hub](/data-fusion/docs/how-to/deploy-a-plugin#deploy-sap-plugin).\n\nThe transport zip file contains two zip files:\n\n- The *cofile* , which has the following naming convention: `K`\u003cvar label=\"Six digit number in file name\" translate=\"no\"\u003eSIX_DIGITS\u003c/var\u003e`.`\u003cvar label=\"SAP ID\" translate=\"no\"\u003eSID\u003c/var\u003e\n- The *data file* , which has the following naming convention: `R`\u003cvar label=\"Six digit number in file name\" translate=\"no\"\u003eSIX_DIGITS\u003c/var\u003e`.`\u003cvar label=\"SAP ID\" translate=\"no\"\u003eSID\u003c/var\u003e\n\nExample: \n\n### ODP\n\nThe following example shows the files in the SAP ODP transport zip file:\n\n### Table\n\nThe following example shows the files in the SAP Table transport zip file:\n\nImport the SAP transport files\n------------------------------\n\nTo install the SAP transports, follow these steps:\n\n1. Sign in to the operating system of the SAP Instance.\n2. To get the path for the `DIR_TRANS` folder, use the SAP transaction code `AL11`. Typically, the path is `/usr/sap/trans/`.\n3. Copy the cofile to the `DIR_TRANS/cofiles` folder.\n4. Copy the data files to the `DIR_TRANS/data` folder.\n5. Set the User and Group of data and cofiles folders and files to \u003cvar label=\"SAP ID\" translate=\"no\"\u003eSID\u003c/var\u003e`adm` and `sapsys`.\n\nAn SAP administrator can import the transport request files by using the SAP\ntransport management system or the operating system command line: \n\n### Transport management\n\n1. Sign in to the SAP system as an SAP administrator.\n2. Enter the transaction `STMS`.\n3. Click **Overview \\\u003e Imports**.\n4. In the **Queue** column, double-click the current SID.\n5. Click **Extras \\\u003e Other Requests \\\u003e Add**.\n6. Select the transport request ID and click **Continue**.\n7. Select the transport request in the import queue and click **Request \\\u003e Import**.\n8. Enter the client number.\n9. On the **Options** tab, select **Overwrite Originals** and **Ignore\n Invalid Component Version** (if available).\n10. Optional: To plan for SAP system upgrades and backup restorations, you can choose to import the transports again later. Click **Leave\n Transports Requests in Queue for Later Import** and **Import Transport\n Requests Again**.\n11. Click **Continue**.\n12. Verify that the function module and authorization roles were imported successfully by using transactions, such as `SE80` and `PFCG`.\n\n### SAP CLI\n\n1. Sign in to the SAP system as an SAP administrator.\n2. Add requests to the import buffer:\n\n tp addtobuffer \u003cvar label=\"Transport request\" translate=\"no\"\u003eTRANSPORT_REQUEST_ID\u003c/var\u003e \u003cvar label=\"SAP ID\" translate=\"no\"\u003eSID\u003c/var\u003e\n\n Replace the following:\n - \u003cvar label=\"Transport request\" translate=\"no\"\u003eTRANSPORT_REQUEST_ID\u003c/var\u003e with the transport request ID\n - \u003cvar label=\"SAP ID\" translate=\"no\"\u003eSID\u003c/var\u003e with the SAP ID\n\n Example: `tp addtobuffer IB1K903958 DD1`\n3. Import the transport requests:\n\n tp import \u003cvar label=\"Transport request\" translate=\"no\"\u003eTRANSPORT_REQUEST_ID\u003c/var\u003e \u003cvar label=\"SAP ID\" translate=\"no\"\u003eSID\u003c/var\u003e client=\u003cvar label=\"Client number\" translate=\"no\"\u003eCLIENT_NUMBER\u003c/var\u003e U1238\n\n Replace \u003cvar label=\"Client number\" translate=\"no\"\u003eCLIENT_NUMBER\u003c/var\u003e with\n the client number.\n\n Example: `tp import IB1K903958 DD1 client=800 U1238`\n | **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.\n4. Verify that the function module and authorization roles were imported\n successfully by using appropriate transactions, such as `SE80` and\n `PFCG`.\n\nAfter the transport is imported into the SAP system, the following SAP\nobjects are created: \n\n### ODP plugin\n\n- RFC-enabled function modules:\n - `/GOOG/ODP_DS_EXTRACT_DATA_V2`\n - `/GOOG/ODP_DS_FETCH_DATA_V2`\n - `/GOOG/ODP_DS_METADATA_V2`\n - `/GOOG/ODP_REPL_CLEANUP_V2`\n- Authorization Role: `/GOOG/ODP_AUTH`\n\n### Table plugin\n\n- RFC-enabled function modules:\n - `/GOOG/RFC_READ_TABLE`\n - `/GOOG/RFC_READ_TABLE_SNAPSHOT`\n - `/GOOG/RFC_READ_TABLE_CLEANUP`\n - `/GOOG/RFC_READ_TABLE_JOBSTATUS`\n - `/GOOG/RFC_TABLE_STAGE_READ`\n - `/GOOG/RFC_GET_PACKAGE_SIZE`\n - `/GOOG/RFC_GET_TABLE_LIST`\n\nSet up authorizations in SAP\n----------------------------\n\nTo set up user authorizations in SAP, either assign the ODP authorization role\nthat's included in the transport file, or manually create an authorization role. \n\n### From Transport\n\n### SAP ODP plugin\n\nIn SAP, assign the Authorization Role, `/GOOG/ODP_AUTH`, which is included in\nthe SAP transports you download when you deploy the SAP ODP plugin.\n\n### Create\n\nTo create the Authorization Role manually, follow these steps:\n\n1. In the SAP GUI, enter the transaction code `PFCG`. The **Role\n Maintenance** window opens.\n2. In the **Role** field, enter a name for the role---for example, `zcdf_role`.\n3. Click **Single Role** . The **Create Roles** window opens.\n4. In the **Description** field, enter a description---for example, `Authorizations for ODP plugin` or `Authorizations for Table plugin`.\n5. Click **Save**.\n6. Click the **Authorizations** tab. The title of the window changes to **Change Roles**.\n7. In the **Edit Authorization Data and Generate Profiles** section, click edit **Change Authorization Data** . The **Choose Template** window opens.\n8. Click **Do not select templates** . The **Change role: Authorizations** window opens.\n9. Click **Manually**.\n10. Provide the authorizations shown in the following SAP Authorization table.\n11. Click **Save**.\n12. To activate the Authorization Role, click the **Generate** icon.\n\nSAP Authorizations include the following: \n\n### ODP\n\n| **Note:** To restrict a user from running ODP pipelines with specific DataSources, for authorization object S_RO_OSOA, provide the required DataSource names in OLTPSOURCE (for example, `2LIS_02_ITM`, `0MATERIAL_ATTR`). Don't use `*`.\n\nThe following authorizations apply for the ODP plugin:\n\n### Table\n\nThe following authorizations apply for the Table plugin:\n\nSet up the SAP Java Connector\n-----------------------------\n\n[Download the following SAP Java Connector (SAP JCo) artifacts](http://service.sap.com/connectors).\nThe minimum supported JCo version is `3.0.20`.\n\n- One platform-independent (`sapjco3.jar`)\n- One platform-dependent (`libsapjco3.so` on Unix)\n\nCopy the files to the Cloud Storage bucket.\n\nFor ODP: Activate data sources for extraction\n---------------------------------------------\n\nTo extract the data, a DataSource must be activated in the source SAP system. To\nactivate a DataSource in SAP, follow these steps:\n\n1. Sign into the SAP system.\n2. Go to the transaction code `RSA5`.\n3. Expand the **DataSources** list.\n\n 1. Open the CDS view in the SAP CDS Editor.\n 2. In the CDS view, look for the following annotations:\n\n - `@Analytics.dataCategory`\n - `@Analytics.dataExtraction.enabled`\n\n If the CDS view has both of these annotations, then it's exposed for ODP\n data extraction. Without them, it isn't exposed.\n4. Click **Search**.\n\n5. Provide the DataSource name and click check_circle **Enter**.\n\n6. If the search is successful, the DataSource appears in the result list.\n\n Select the DataSource name and click check_circle **Enter**.\n7. Select the DataSource and click **Activate DataSources**.\n\n8. In the **Create Object Directory Entry** dialog, enter the Package name and\n click **Save**.\n\n9. In the **Prompt for transportable workbench request** dialog, enter the\n Transport Number in the **Request** field. Click check_circle **Enter**.\n\n The selected DataSource is activated in SAP.\n\n### Check that the DataSource is exposed for extraction\n\n1. Sign in to the SAP system.\n2. Go to t-code `SE16N`.\n3. Enter the table name, `ROOSATTR`, and enter the DataSource name in `OLTPSOURCE`.\n4. Click **Execute** or press F8.\n5. If the **EXPOSE_EXTERNAL** field has an `X`, the DataSource is exposed and ready for extraction.\n\nIf the DataSource doesn't appear in the `ROOSATTR` table, or the\n**EXPOSE_EXTERNAL** field is blank, follow these steps to expose the DataSource\nfor ODP extraction:\n\n1. Sign in to the SAP system.\n2. Go to t-code `SA38`.\n3. Enter the program name, `RODPS_OS_EXPOSE`, and click **Execute**.\n4. Enter the DataSource name and click **Release DataSource**.\n5. Save the changes in the transport.\n\nWhat's next\n-----------\n\n- [Configure the SAP ODP plugin in Cloud Data Fusion](/data-fusion/docs/how-to/use-sap-odp-plugin)."]]
