SAP OData connector for Amazon AppFlow

To create an SAP OData connection

1. Sign in to the AWS Management Console and open the Amazon AppFlow console at https://console.aws.amazon.com/appflow/.

2. In the navigation pane on the left, choose Connections.

3. On the Manage connections page, for Connectors, choose SAP OData.

4. Choose Create connection.

5. In the Connect to SAP OData window, enter the following information:

   1. Under Application Host URL, enter your Application host url. This application host url must be accessible over public internet for non PrivateLink connection.

   2. Under Application Service Path, enter your catalog service path. e.g./sap/opu/odata/iwfnd/catalogservice;v=2. Amazon AppFlow doesn’t accept specific object path.

   3. Under Port Number, enter your port number.

   4. Under Client Number, enter your 3 digit client number. Acceptable values are [001-999]. e.g.010

   5. Under Logon Language, enter your two character logon language. e.g. EN.

   6. (Optional) To use private connection for data transfer, under AWS PrivateLink service name, enter your VPC Endpoint (PrivateLink) service name. e.g. com.amazonaws.vpce.us-east-1.vpce-svc-xxxxxxxxxxxxxx

   7. Select your preferred Authentication Mode.

      • If Basic,

        1. Under User name, enter your useraname.

        2. Under Password, enter your password.

      • If OAuth2,

        1. Under Authorization Code URL, enter your authorization code URL.

        2. Under Authorization Tokens URL, enter your authorization token URL.

        3. Under OAuth Scopes, enter your OAuth scopes separated by space. e.g./IWFND/SG_MED_CATALOG_0002 ZAPI_SALES_ORDER_SRV_0001

        4. Under Client ID, enter your client id .

        5. Under Client Secret, enter your client secret .

   8. Optionally, under Data encryption, choose Customize encryption settings (advanced) if you want to encrypt your data with a customer managed key in the AWS Key Management Service (AWS KMS).

      By default, Amazon AppFlow encrypts your data with a KMS key that AWS creates, uses, and manages for you. Choose this option if you want to encrypt your data with your own KMS key instead.

      Amazon AppFlow always encrypts your data during transit and at rest. For more information, see Data protection in Amazon AppFlow.

      If you want to use a KMS key from the current AWS account, select this key under Choose an AWS KMS key. If you want to use a KMS key from a different AWS account, enter the Amazon Resource Name (ARN) for that key.

   9. Under Connection name, specify a name for your connection.

   10. Choose Continue.

   11. If using OAuth, you will be redirected to the SAP login page. When prompted, grant Amazon AppFlow permissions to access your SAP account.

   

1. Choose Run flow on schedule.

2. Use the scheduling fields to specify when the flow begins, how often it repeats, and when it ends.

3. Under Transfer mode, choose Incremental transfer.

   For ODP data objects specifically, the console requires no additional input. This behavior differs from SAP data objects that don't come from an ODP provider. For those objects, you must specify a source timestamp field that Amazon AppFlow uses to identify new or changed records. For ODP data, no such timestamp is necessary because Amazon AppFlow uses the information that's provided by the delta token that it receives from the operational delta queue.

• Under Choose how to trigger the flow, do either of the following:

  • Choose Run on demand. After you create an on-demand flow, you run it manually by choosing Run flow on its details page in the Amazon AppFlow console.

  • Choose Run flow on schedule and define your schedule:.

    1. Use the scheduling fields to specify when the flow begins, how often it repeats, and when it ends.

    2. For Transfer mode, choose Full transfer.

       Note

       To create a flow that runs full data transfers, the frequency that you choose must be no more frequent than Daily. If it is more frequent, then you won't be able to choose Full transfer.

To capture the SAP success response for new records

1. Create an Amazon S3 bucket. The bucket must be in the same AWS Region as the flow that you create for your SAP OData connector. For the steps to create a bucket, see Creating a bucket in the Amazon S3 User Guide.

2. Configure the flow by following the steps in Creating flows in Amazon AppFlow, but do one additional step:

   1. On the Configure flow page, under Response handling, select the bucket that you created. The SAP success response payload is delivered to this bucket when finish creating your flow.

To create SAP deep entities

1. Generate a JSON Lines input file that defines one deep entity per line, as shown by the following example.

   JSON Lines (required format)

   The following input file defines two deep entities in JSON Lines format (also called newline-delimited JSON). In this format, each line is a complete JSON object that defines an individual deep entity.

   Each deep entity can include multiple levels of hierarchical data. This example creates two Sales Orders, and each contains two associated Sales Order Items.

   {"SalesOrderType": "OR","SalesOrganization": "1710","DistributionChannel": "10","OrganizationDivision": "00","SoldToParty": "USCU_S13","TransactionCurrency": "USD","PurchaseOrderByCustomer": "TEST-PO2021","to_Item": [{"Material": "MZ-FG-C990","RequestedQuantity": "10","RequestedQuantityUnit": "PC"},{"Material": "MZ-FG-M500","RequestedQuantity": "10","RequestedQuantityUnit": "PC"}]}
   {"SalesOrderType": "OR","SalesOrganization": "1710","DistributionChannel": "10","OrganizationDivision": "00","SoldToParty": "USCU_S13","TransactionCurrency": "USD","PurchaseOrderByCustomer": "TEST-PO2021","to_Item": [{"Material": "MZ-FG-C990","RequestedQuantity": "10","RequestedQuantityUnit": "PC"},{"Material": "MZ-FG-M500","RequestedQuantity": "10","RequestedQuantityUnit": "PC"}]}

   Formatted JSON (for readability)

   The following example shows one of the deep entities from the JSON Lines input file. This example is formatted for readability so that you can more easily see the nested JSON values.

   {
     "SalesOrderType": "OR",
     "SalesOrganization": "1710",
     "DistributionChannel": "10",
     "OrganizationDivision": "00",
     "SoldToParty": "USCU_S13",
     "TransactionCurrency": "USD",
     "PurchaseOrderByCustomer": "TEST-PO2021",
     "to_Item":
     [
       {
         "Material": "MZ-FG-C990",
         "RequestedQuantity": "10",
         "RequestedQuantityUnit": "PC"
       },
       {
         "Material": "MZ-FG-M500",
         "RequestedQuantity": "10",
         "RequestedQuantityUnit": "PC"
       }
     ]
   }

   Remember that Amazon AppFlow requires JSON Lines format, so this example would be an invalid input file.

2. Create an Amazon S3 bucket. The bucket must be in the same AWS Region as the flow that you create for your SAP OData connector. For the steps to create a bucket, see Creating a bucket in the Amazon S3 User Guide.

3. Upload your deep entities input file to the bucket that you created. For the steps to upload a file, see Uploading objects in the Amazon S3 User Guide.

4. Configure the flow by following the steps in Creating flows in Amazon AppFlow, but do one alternate step:

   1. On the Map data fields page, under Mapping method, choose Passthrough fields without modification.

      Note

      When you choose this option, the console disables the options under Source to destination field mapping. With this option, you don't define mappings in the console. Instead, the fields in your input file must match the fields that you use in SAP.

To transfer your data with concurrent processes

Configure the flow by following the steps in Creating flows in Amazon AppFlow, and do these additional steps:

1. On the Configure flow page, choose your SAP OData connector under Source details.

2. In the Source details section, under Additional settings, set the following options:

   Batch size

   The maximum number of records that Amazon AppFlow receives in each page of the response from your SAP application. For transfers of OData records, the maximum page size is 3,000. For transfers of data that comes from an ODP provider, the maximum page size is 10,000.

   Maximum number of concurrent processes

   The maximum number of processes that Amazon AppFlow runs at the same time when it retrieves your data. The default value is one. You can specify up to 10.