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 transport zip file is available for download when you deploy SAP plugins in the Cloud Data Fusion Hub.
The transport zip file contains two zip files:
- 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 codeAL11
. 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
andsapsys
.
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
andPFCG
.
SAP CLI
- Sign in to the SAP system as an SAP administrator.
Add requests to the import buffer:
tp addtobuffer TRANSPORT_REQUEST_ID SID
Replace the following:
TRANSPORT_REQUEST_ID
with the transport request IDSID
with the SAP ID
Example:
tp addtobuffer IB1K903958 DD1
Import the transport requests:
tp import TRANSPORT_REQUEST_ID SID client=CLIENT_NUMBER U1238
Replace
CLIENT_NUMBER
with the client number.Example:
tp import IB1K903958 DD1 client=800 U1238
Verify that the function module and authorization roles were imported successfully by using appropriate transactions, such as
SE80
andPFCG
.
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
/GOOG/ODP_DS_FETCH_DATA
/GOOG/ODP_DS_METADATA
/GOOG/ODP_REPL_CLEANUP
- 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
orAuthorizations 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 Change 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 |
|
AAAB |
Cross-application Authorization Objects |
S_RFC |
Authorization Check for RFC Access |
RFC_TYPE |
Type of RFC object to which access is allowed |
|
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 |
|
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:
Object class | Object class text | Authorization object | Authorization object text | Authorization | Text | Value |
---|---|---|---|---|---|---|
AAAB |
Cross-application Authorization Objects |
S_RFC |
Cross-application Authorization Objects |
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 |
|
AAAB |
Cross-application Authorization Objects |
S_RFC |
Cross-application Authorization Objects |
RFC_TYPE |
Type of RFC object to which access is allowed |
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 |
ST0R |
BC_A |
Basis: Administration |
S_TABU_NAM |
Table Access by Generic Standard Tools |
ACTVT |
Activity |
03 |
BC_A |
Basis: Administration |
S_TABU_NAM |
Table Access by Generic Standard Tools |
TABLE |
Table Name |
* |
Set up the SAP Java Connector
Download the following SAP Java Connector (SAP JCo) artifacts.
The minimum supported JCo version is 3.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. 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
Enter.If the search is successful, the DataSource appears in the result list.
Select the DataSource name and click
Enter.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
Enter.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 inOLTPSOURCE
. - 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.
- Save the changes in the transport.