Amazon Selling Partner (SP-API) Connector for Informatica PowerCenter : Get orders items (for all orders **slow**) via SQL

Learn how to get orders items (for all orders **slow**) using the Amazon Selling Partner (SP-API) Connector for Informatica PowerCenter. This connector enables you to read and write Amazon Selling Partner (SP-API) data effortlessly. Integrate, manage, and automate listings, orders, payments, and reports — almost no coding required. We'll walk you through the exact setup.

Let's dive in!

Create data source using Amazon Selling Partner (SP-API) ODBC Driver

1. Download and install ODBC PowerPack (if you haven't already).

2. Search for odbc and open the ODBC Data Sources (64-bit):

   

3. Create a User data source (User DSN) based on the ZappySys API Driver driver:

   ZappySys API Driver

   
   • Create and use a User DSN if the client application runs under a User Account. This is the ideal option at design time (e.g., when developing in Visual Studio). Use it for both types of applications (64-bit and 32-bit).
   • Create and use a System DSN if the client application runs under a System Account (e.g., as a Windows Service). This is usually the required option in a production environment. If your Windows Service is a 32-bit application, you must use the 32-bit ODBC Data Source Administrator to configure this

4. When the Configuration window appears give your data source a name if you haven't done that already, then select "Amazon Selling Partner (SP-API)" from the list of Popular Connectors. If "Amazon Selling Partner (SP-API)" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

   AmazonSellingPartnerSpApiDSN

   Amazon Selling Partner (SP-API)

   

5. Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

   Private app

   Amazon Selling Partner (SP-API) authentication

   Amazon Sellers can use SP-API to set up private integrations and build solutions exclusively for their Amazon store. Private app is available only to your organization and is self-authorized. A private developer builds application(s) that integrate their own company with Amazon APIs. [API reference]

   Perform the following steps to authenticate calls using Amazon SP-API Private app:

   1. Register as an Amazon Private SP-API Developer. You may need to wait for a day or two to get approved (check approval status).
   2. Once your developer account is approved, login to your account, visit developer console and click Add new app client button to create a Private app:
   3. Continue by naming your application in the App name field, choose SP API as API Type, and select the Roles for your app (i.e. permissions):
   4. Once you do that, click View link in LWA credentials column to copy Client identifier and Client secret (we will use them later):
   5. Now it's time to Authorize your app:
   6. Finish authorizing it by presing Authorize app button:
   7. Finally, copy the Refresh Token (we will use it in the next step):
   8. Now go to SSIS package or ODBC data source and use Private app authentication configuration:
      • In the ClientId field paste the Client identifier value you copied in the previous step.
      • In the ClientSecret field paste the Client secret value you copied in the previous step.
      • Leave the default value in the TokenUrl field.
      • In the Refresh Token field paste the Refresh Token value you copied in the previous step.
   9. Click Test Connection to confirm the connection is working.
   10. Done! Now you are ready to use Amazon Selling Partner (SP-API) Connector!

   API Connection Manager configuration

   Just perform these simple steps to finish authentication configuration:

   1. Set Authentication Type to Private app [OAuth]
   2. Optional step. Modify API Base URL if needed (in most cases default will work).
   3. Fill in all the required parameters and set optional parameters if needed.
   4. Press Generate Token button to generate the tokens.
   5. Finally, hit OK button:

   AmazonSellingPartnerSpApiDSN

   Amazon Selling Partner (SP-API)

   Private app [OAuth]

   https://sellingpartnerapi-na.amazon.com

   Required Parameters
   ClientId	Fill-in the parameter...
   ClientSecret	Fill-in the parameter...
   TokenUrl	Fill-in the parameter...
   Optional Parameters
   TokenUIMode	OnlyRefreshToken
   AuthUrl (Do not Use for Private app - Self Authorization)	https://sellercentral.amazon.com/apps/authorize/consent?application_id=[YOUR-APPLICATION-ID]&version=beta
   OrdersApiVersion	v0
   SellerApiVersion	v1
   ShippingApiVersion	v1
   ServicesApiVersion	v1
   FbaApiVersion	v1
   SalesApiVersion	v1
   ReportsApiVersion	2021-06-30
   ProductsFeesApiVersion	v0
   ProductPricingApiVersion	v0
   CatalogItemsApiVersion	2022-04-01
   VendorOrdersApiVersion	v1
   RetryMode	RetryWhenStatusCodeMatch
   RetryStatusCodeList	429
   RetryCountMax	5
   RetryMultiplyWaitTime	True

   

6. Then go to Preview tab to start building a SQL query.

7. Once you do that, proceed by opening Query Builder:

   

   ZappySys API Driver - Amazon Selling Partner (SP-API)

   Read and write Amazon Selling Partner (SP-API) data effortlessly. Integrate, manage, and automate listings, orders, payments, and reports — almost no coding required.

   AmazonSellingPartnerSpApiDSN

   

8. Then simply select the Get Orders Items (For All Orders **Slow**) endpoint (action).

9. Continue by configuring the Required parameters. You can also set optional parameters too.

10. Move on by hitting Preview Data button to preview the results.

11. If you see the results you need, simply copy the generated query:

    Get Orders Items (For All Orders **Slow**)

    Required Parameters
    MarketplaceIds	Select the value from the dropdown
    Optional Parameters
    CreatedAfter
    CreatedBefore
    LastUpdatedAfter
    LastUpdatedBefore
    OrderStatuses
    FulfillmentChannels
    PaymentMethods
    BuyerEmail
    SellerOrderId
    MaxResultsPerPage
    EasyShipShipmentStatuses
    ElectronicInvoiceStatuses
    AmazonOrderIds
    ActualFulfillmentSupplySourceId
    IsISPU
    StoreChainStoreId
    Advanced Properties
    NextUrlAttributeOrExpr	$.payload.NextToken
    NextUrlSuffix	NextToken=<%nextlink_encoded%>

    SELECT * FROM OrderItems
    WITH(
    	  CreatedAfter='1900-01-01T00:00:00'
    --	, CreatedBefore='1900-01-01T00:00:00'
    --	, LastUpdatedAfter='1900-01-01T00:00:00'
    --	, LastUpdatedBefore='1900-01-01T00:00:00'
    --	, OrderStatuses='Pending~Unshipped~PartiallyShipped~PendingAvailability~Shipped~Canceled~Unfulfillable'
    --	, MarketplaceIds='ATVPDKIKX0DER~A2Q3Y263D00KWC~A2EUQ1WTGCTBG2'
    --	, FulfillmentChannels='AFN~MFN'
    --	, PaymentMethods='COD~CVS~Other'
    --	, AmazonOrderIds='1111111,222222,333333'
    )
    --CONNECTION(
    --	ServiceUrl='https://sellingpartnerapi-na.amazon.com'
    --)

    

12. Click OK to use built SQL query and close the Query Builder.

13. Now hit Preview Data button to preview the data using the generated SQL query. If you are satisfied with the result, use this query in Informatica PowerCenter:

    

    ZappySys API Driver - Amazon Selling Partner (SP-API)

    Read and write Amazon Selling Partner (SP-API) data effortlessly. Integrate, manage, and automate listings, orders, payments, and reports — almost no coding required.

    AmazonSellingPartnerSpApiDSN

    SELECT * FROM OrderItems
    WITH(
    	  CreatedAfter='1900-01-01T00:00:00'
    --	, CreatedBefore='1900-01-01T00:00:00'
    --	, LastUpdatedAfter='1900-01-01T00:00:00'
    --	, LastUpdatedBefore='1900-01-01T00:00:00'
    --	, OrderStatuses='Pending~Unshipped~PartiallyShipped~PendingAvailability~Shipped~Canceled~Unfulfillable'
    --	, MarketplaceIds='ATVPDKIKX0DER~A2Q3Y263D00KWC~A2EUQ1WTGCTBG2'
    --	, FulfillmentChannels='AFN~MFN'
    --	, PaymentMethods='COD~CVS~Other'
    --	, AmazonOrderIds='1111111,222222,333333'
    )
    --CONNECTION(
    --	ServiceUrl='https://sellingpartnerapi-na.amazon.com'
    --)

    
    You can also access data quickly from the tables dropdown by selecting <Select table>.
    A WHERE clause, LIMIT keyword will be performed on the client side, meaning that the whole result set will be retrieved from the Amazon Selling Partner (SP-API) API first, and only then the filtering will be applied to the data. If possible, it is recommended to use parameters in Query Builder to filter the data on the server side (in Amazon Selling Partner (SP-API) servers).

Let's not stop here and explore SQL query examples, including how to use them in Stored Procedures and Views (virtual tables) in the next steps.

Amazon Selling Partner (SP-API) SQL query examples

Use these SQL queries in your Informatica PowerCenter data source:

List order items for all orders

Read order items for all matching orders in one query. This can be slower than fetching items per order, especially for large date ranges.

SELECT * FROM OrderItems
WITH(
	  CreatedAfter='1900-01-01T00:00:00'
--	, CreatedBefore='1900-01-01T00:00:00'
--	, LastUpdatedAfter='1900-01-01T00:00:00'
--	, LastUpdatedBefore='1900-01-01T00:00:00'
--	, OrderStatuses='Pending~Unshipped~PartiallyShipped~PendingAvailability~Shipped~Canceled~Unfulfillable'
--	, MarketplaceIds='ATVPDKIKX0DER~A2Q3Y263D00KWC~A2EUQ1WTGCTBG2'
--	, FulfillmentChannels='AFN~MFN'
--	, PaymentMethods='COD~CVS~Other'
--	, AmazonOrderIds='1111111,222222,333333'
)
--CONNECTION(
--	ServiceUrl='https://sellingpartnerapi-na.amazon.com'
--)

Create SQL view in ODBC data source

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

1. Go to Custom Objects Tab and Click on Add button and Select Add Table:
   

2. Enter the desired Table name and click on OK:
   

3. And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.

4. Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
   Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
   

   SELECT
     "ShipCountry",
     "OrderID",
     "CustomerID",
     "EmployeeID",
     "OrderDate",
     "RequiredDate",
     "ShippedDate",
     "ShipVia",
     "Freight",
     "ShipName",
     "ShipAddress",
     "ShipCity",
     "ShipRegion",
     "ShipPostalCode"
   FROM "Orders"
   Where "ShipCountry"='USA'

   
   

5. That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:

   SELECT * FROM "vt__usa_orders_only"

   

Get orders items in Informatica PowerCenter via SQL view

1. Open Informatica Mapping Designer (Click [D] icon)

2. Click on Source Icon to switch to Sources designer

3. From the top menu > Click on Sources > Import from Database …

   

   Import Amazon Selling Partner (SP-API) Source definition in Informatica Mapping Designer (JSON file or REST API)

4. Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)

5. Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.

   DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
   —————————————————-
   Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.
   

   Select Amazon Selling Partner (SP-API) Source Table in Informatica Mapping Designer (JSON file or REST API)

6. Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
7. Optionally once table structure is imported you can rename it
   

   Rename imported table definition in Informatica Source Designer

Advanced topics

Creating SQL stored procedures

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
   

2. Enter the desired Procedure name and click on OK:
   

3. Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver. Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

   CREATE PROCEDURE [usp_get_orders]
       @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
    AS
       SELECT * FROM Orders where OrderDate >= '<@fromdate>';
   

   

4. That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:

   Exec usp_get_orders '1996-01-01';

   

Conclusion

And there you have it — a complete guide on how to get orders items (for all orders **slow**) in Informatica PowerCenter without writing complex code. All of this was powered by Amazon Selling Partner (SP-API) ODBC Driver, which handled the REST API pagination and authentication for us automatically.

Download the trial now or ping us via chat if you have any questions or are looking for a specific feature (you can also reach out to us by submitting a ticket):

More actions supported by Amazon Selling Partner (SP-API) Connector

Got another use case in mind? We've documented the exact setups for a variety of essential Amazon Selling Partner (SP-API) operations directly in Informatica PowerCenter, so you can skip the trial and error. Find your next step-by-step guide below:

• Download Report File to Local Disk
• Get FBA Inventory Summaries (Fulfilled By Amazon)
• Get Market Place Participations
• Get Order (Single)
• Get Order Items (For Single Order)
• Get Orders
• Get Report Data - Comma Separated File (CSV)
• Get Report Data - JSON File
• Get Report Data - Tab Separated File (TSV)
• Get Report Data - XML File
• Get Report Filters
• Get Report Options
• Get Report Types
• Get Vendor PurchaseOrder Items
• Get Vendor PurchaseOrders
• Search Catalog Items
• Make Generic REST API Request
• Make Generic REST API Request (Bulk Write)

More Amazon Selling Partner (SP-API) integrations

SSIS

SQL Server

Microsoft Fabric

Power BI

SSRS

MS Access

Excel

SSAS

C#

Python

Java

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

Alteryx

ODBC