How to set up connector for SAP

Modified on Wed, 27 Aug at 8:17 AM

Table of contents

Introduction

Follow this article to find out how to setup conntectors for SAP


Prerequisites

Before creating a Safran connector, ensure you have: 

  • You should have the permission of Setup Admin role to create a connector
  • Desktop Client needs to be installed on you machine and/or Autonomous Component needs to be set up for your tenant
  • Authentication details (Depending on what type is selected)
  • Any custom request headers defined by your tenant’s configuration 


How to create 

  1. Access the IDE web application and navigate to Setup > Connectors
  2. Click on the button +New Connector
    • A modal will appear having the following required fields:
      • Title, Host System, Execution component
  3. Provide a meaningful title.
  4. Select the execution component.
  5. Select SAP from the Host system dropdown. This will populate the following new fields:
    • Required: Base URL, Authentication Type
    • Optional: Manage Customer Request Headers
  6. Lastly add details to all of the required fields and hit create. 
Please note each connector's URL must be unique otherwise error will be shown


Effect on Connector for selecting different execution component

Authentication types depend on the execution component you choose. Selecting Desktop client as execution component provides the following options as authentication types:

  • Basic
  • Windows
  • WindowsWithoutCSRFToken
  • AzureSamlOauthToken

While desktop client has more options to authenticate the connector, Autonomous Component provides only one type:

  • Basic 


Authentication types explained:

Each authentication method has its own setup process and use cases. Here's what you need to know:


Basic:



Here is the setting you need to configure, and they are shown with red numbers and described below: 

 

1TitleTitle of the connector
2Host SystemSAP
3Execution ComponentDesktop Client or Autonomous Component
4Base URLThe root URL of the SAP system or API endpoint the connector will connect to
5Authentication TypeBasic
6UsernameYour username
7PasswordPassword
8Manage Custom HeadersCustom HTTP headers if required by the host system for API 



Windows :


Here is the setting you need to configure, and they are shown with red numbers and described below:

 

1TitleTitle of the connector
2Host SystemSAP
3Execution ComponentDesktop Client 
4Base URLThe root URL of the SAP system or API endpoint the connector will connect to
5Authentication TypeWindwos
6Manage Custom HeadersCustom HTTP headers if required by the host system for API 


WindowsWithoutCSRFToken


Here is the setting you need to configure, and they are shown with red numbers and described below:

 

1TitleTitle of the connector
2Host SystemSAP
3Execution ComponentDesktop Client 
4Base URLThe root URL of the SAP system or API endpoint the connector will connect to
5Authentication TypeWindowsWithoutCSRFToken
6Manage Custom HeadersCustom HTTP headers if required by the host system for API 




AzureSamlOauthToken



Here is the setting you need to configure, and they are shown with red numbers and described below:

 

1TitleTitle of the connector
2Host SystemSAP
3Execution ComponentDesktop Client or Autonomous Component
4Base URLThe root URL of the SAP system or API endpoint the connector will connect to
5Authentication TypeAzureSamlOauthToken
6SAP AuthorityThe URL of the SAP authorization server for token-based authentication.
7SAP Client IdA unique identifier for the client application registered with the SAP system.
8SAP Api AreaDefines the specific API endpoint or module within the SAP system to interact with.
9SAP API VersionThe version of the SAP API that the connector will use to communicate with the system.
10SAP Grant TypeThe grant type used for authentication with SAP.
11SAP Apim SubscriptionThe subscription key or identifier for accessing SAP APIs through an API Management (APIM) gateway.
12SAP Secret Keyvault URLThe URL of the Azure Key Vault storing sensitive SAP credentials.
13SAP Secret Keyvault KeyThe specific key or secret name in the Azure Key Vault for SAP authentication.
14SAP Apim TraceEnables or disables tracing for API Management calls to debug SAP API interactions.
15Client IdThe unique identifier for the client 
16Client SecretA secure key paired with the Client Id for authenticating the client
17Tenant IdThe unique identifier for the Azure Active Directory tenant used in authentication.
18AuthorityThe authentication endpoint URL for the identity provider
19ScopeDefines the permissions or access level requested for the SAP API during authentication.
20Manage Custom Header (optional)Custom HTTP headers if required by the host system for API 


Note: Consult with your Tenant admin to get the required information 


Test & Persist

After creating the connector:

  • For Desktop Client execution:

    • Open the IDE Desktop Client

    • Navigate to the Connectors tab

    • Click Test to verify connection

    • Click Persist to fetch schedules and host fields from P6

  • For Autonomous Component execution:

    • Test is done periodically via a background job, but it can be also done using desktop client.

    • Alternatively: Go to Setup > Connectors in the web app, and open the newly created connector and click Persist to force retrieval of schedules and host fields from P6. After persisting, reload the page after a few minutes to verify the updated connector status. 

Checkout this article to find out more about test & persist



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article