Skip to main content

Data Source

Follow the instructions below to create a new data flow that ingests data from a SAP HANA source in Nexla.
sap_hana_api.png

SAP HANA

Create a New Data Flow

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the SAP HANA connector tile from the list of available connectors. Then, select the credential that will be used to connect to your SAP HANA account, and click Next; or, create a new SAP HANA credential for use in this flow.

  3. In Nexla, SAP HANA data sources can be created using pre-built endpoint templates, which expedite source setup for common SAP HANA endpoints. Each template is designed specifically for the corresponding SAP HANA endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    SAP HANA sources can also be configured manually, allowing you to ingest data from SAP HANA endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common SAP HANA endpoints. Each template is designed specifically for the corresponding SAP HANA endpoint, making data source setup easy and efficient.

Endpoint Settings

  • Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    Get Sales Orders Without Charge

    This endpoint template retrieves all sales orders without charge from your SAP HANA account. This endpoint fetches all existing records. Use this template when you need to retrieve information about sales orders without charge, including order IDs, customer information, and other order metadata. Click on API documentation link for available filters that can be used with a REST connector.

    • This endpoint automatically retrieves all sales orders without charge from your SAP HANA account. No additional configuration is required beyond selecting this endpoint template. You can use available filters with a REST connector to customize the data retrieval.

    This endpoint returns all sales orders without charge from your SAP HANA account, including order IDs, customer information, and other order metadata. The endpoint fetches all existing records. You can use available filters with a REST connector to customize the data retrieval based on your specific requirements.

    For detailed information about sales orders, API response structures, available filters, and order data, see the SAP HANA API documentation.

Endpoint Testing

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually

SAP HANA data sources can be manually configured to ingest data from any valid SAP HANA API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex SAP HANA sources, such as sources that use chained API calls to fetch related data or sources that require custom query parameters or filters.

API Method

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the SAP HANA API from the Method pulldown menu. SAP HANA API typically uses GET method for retrieving data from endpoints.

API Endpoint URL

  1. Enter the URL of the SAP HANA API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including your SAP HANA Cloud hostname (from your credential), the API path (e.g., /sap/opu/odata/sap/API_SALES_ORDER_WITHOUT_CHARGE_SRV/A_SalesOrderWithoutCharge), and any required query parameters. Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The SAP HANA API endpoint URL should include your SAP HANA Cloud hostname and the appropriate API path. You can test the endpoint using the Test button after configuring the URL.

Response Data Path

  1. Enter the JSONPath expression in the Response Data Path field to specify which part of the API response should be treated as the relevant data by Nexla. For SAP HANA API responses, use $.d.results[*] to extract all items from the results array, or $ to extract the entire response for single record endpoints, depending on your endpoint.

The JSONPath expression must correctly reference the structure of your SAP HANA API response. SAP HANA API responses may have different structures depending on the endpoint. Ensure your JSONPath expression matches the structure returned by your specific endpoint. The JSONPath expression determines which data will be extracted and processed by Nexla.

Save the Data Source

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.