如要取得 DIR_TRANS 資料夾的路徑，請使用 SAP 交易代碼 AL11。路徑通常為 /usr/sap/trans/。
將 cofile 複製到 DIR_TRANS/cofiles 資料夾。
將資料檔案複製到 DIR_TRANS/data 資料夾。
將資料和共用檔案資料夾和檔案的使用者和群組設為 SIDadm 和 sapsys。
SAP 管理員可以使用 SAP 傳輸管理系統或作業系統指令列匯入傳輸要求檔案：
運輸管理
以 SAP 管理員身分登入 SAP 系統。
輸入交易 STMS。
依序點選「總覽」>「匯入」。
在「佇列」欄中，按兩下目前的 SID。
依序點選「Extras」「Other Requests」「Add」。
選取傳輸要求 ID，然後按一下「繼續」。
在匯入佇列中選取傳輸要求，然後依序點選「要求」>「匯入」。
輸入客戶編號。
在「選項」分頁中，選取「覆寫原始檔」和「忽略無效的元件版本」 (如有)。
選用：如要規劃 SAP 系統升級和備份還原作業，您可以選擇稍後再次匯入傳輸。依序點選「Leave Transports Requests in Queue for Later Import」(將轉移要求保留在佇列中，稍後再匯入)和「Import Transport Requests Again」(再次匯入轉移要求)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\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)."]]
