diff --git a/ja/Data-Sources/SAPGateway-Embedded.mdx b/ja/Data-Sources/SAPGateway-Embedded.mdx
new file mode 100644
index 0000000..19dbfaa
--- /dev/null
+++ b/ja/Data-Sources/SAPGateway-Embedded.mdx
@@ -0,0 +1,7 @@
+---
+title: "SAP Gateway"
+---
+
+import SAPGateway from '/ja/snippets/Data-Sources/SAPGateway.mdx';
+
+
\ No newline at end of file
diff --git a/ja/Data-Sources/SAPGateway.mdx b/ja/Data-Sources/SAPGateway.mdx
new file mode 100644
index 0000000..19dbfaa
--- /dev/null
+++ b/ja/Data-Sources/SAPGateway.mdx
@@ -0,0 +1,7 @@
+---
+title: "SAP Gateway"
+---
+
+import SAPGateway from '/ja/snippets/Data-Sources/SAPGateway.mdx';
+
+
\ No newline at end of file
diff --git a/ja/snippets/Data-Sources/SAPGateway.mdx b/ja/snippets/Data-Sources/SAPGateway.mdx
new file mode 100644
index 0000000..73081e6
--- /dev/null
+++ b/ja/snippets/Data-Sources/SAPGateway.mdx
@@ -0,0 +1,98 @@
+## Setup Guide
+
+Follow these steps to connect SAP Gateway to your Connect AI account:
+
+
+
+Open the **Connections** page of the Connect AI dashboard.
+
+
+Click **\+ Add Connection** in the upper-right corner.
+
+
+Type *SAP Gateway* into the search field, then click the data source name.
+
+
+On the **Basic Settings** tab of the new connection, enter a connection name or keep the default name.
+
+
+Enter the **URL** for your SAP Gateway environment or the full URL of the OData service. Any additional properties must be added using **Custom URL Params**.
+
+
+(Optional) Enter the service **Namespace** you want to retrieve data from. This is only required if the service is not specified in the **URL**.
+
+
+(Optional) Enter the **Service**, which is a comma-delimited list of services you want to retrieve data from. If the service is set in the **URL**, this property is ignored. In cases where the service is not set in the URL or in **Service**, the SAP Gateway's catalog service is used to discover all available services.
+
+
+(Optional) Enter any **Custom URL Params** to be included with the HTTP request. The parameters should be in the form *field1=value1&field2=value2&field3=value3*.
+
+
+Select an **AuthScheme** and follow the relevant instructions below.
+
+
+
+## Authentication Methods
+
+
+
+
+
+Enter the **User** Id for the authenticating user.
+
+
+Enter the **Password** for the authenticating user.
+
+
+
+
+
+
+
+
+Enter the **OAuth Client Id** assigned to your custom OAuth application. This Id is required to identify the application to the OAuth authorization server during authentication.
+
+
+Enter the **OAuth Client Secret** assigned to your custom OAuth application. This value is used to authenticate the custom application to the OAuth authorization server.
+
+
+Enter the **Scope**, or permission scopes, in space separated values. Scopes define what kind of access the authenicating user has, such as read or read/write. Scopes are required for OAuth 2.0.
+
+
+
+
+
+
+
+
+Enter the **API Key** of the application you have created.
+
+
+
+
+
+
+
+
+Set authentication to **OAuthPKCE** to use the Proof Key of Code Exchange (PKCE) extension of the standard OAuth2 flow. Set your own PKCEVerifier or let the driver automatically generate one for you.
+
+
+
+
+
+
+
+
+In **Advanced Settings**, enter the **Destination URL** of the SAP BTP destination source. This URL is found in the service key of your Destination Service instance in the SAP BTP Cockpit, in the **URI** field.
+
+
+In **Advanced Settings**, enter the **Destination Name** of the SAP BTP destination to retrieve the authentication details from.
+
+
+
+
+
+
+## More Information
+
+For more information about interactions between Connect AI and SAP Gateway, see [this information page](https://cdn.cdata.com/help/GCM/jp/cloud/default.htm#default).
\ No newline at end of file