Welcome Guest, you are in: Login

QVSource: The QlikView & Qlik Sense API Connector (Docs)


The Blue Yonder Connector for QlikView will be available in the next release of QVSource.

Usage

The Connector has a single table with the following inputs.

You should receive values for the:
  • Base URL
  • Interface Version
  • User Name
  • Password
  • Tenant ID

From Blue Yonder.

Image

You should have a list of product and location IDs that you are interested in displaying demand predictions for. We expect you already have the IDs in QlikView. If not, export the list of relevant product and location IDs to a text file or other location where they can be read into QlikView.

You have the option of specifying either both the location ID or product ID or both (or neither - however this is not recommended) when requesting your forward demand predictions. The choice you make will depend on your data set.

By specifying the location or product ID (or both) you directly influence the amount of data returned for each request. When testing connectivity in QVSource you should specify a location and a product ID. The maximum number of data rows returned is equal to the prediction horizon (typically 21 days). If you specify the predictionDay at most one record will be returned for every product/location ID combination. Here is a guideline to determine which parameters to set:

  • It is good practice to target for roughly 50000 result rows per request
  • The number of result rows are determined by #locations * #products * #predictions
    • If you do not specify a location ID, all location IDs are retrieved; if you specify a location ID, only this location ID is retrieved
    • If you do not specify a product ID, all product IDs are retrieved; if you specify a product ID, only this product ID is retrieved
    • If you do not specify a predictionDay, the latest predictions with the full prediction horizon are retrieved; if you specify a predictionDay, only this day is retrieved
  • Example: let’s assume you have 400 locations and 2500 products with 21 days prediction horizon in your Blue Yonder application
    • If you specify location, product and predictionDay you will get at maximum one result row >> not recommended as this require 1.000.000 requests to retrieve all predictions
    • If you do not specify any parameter you will get up to 21.000.000 results row (400 * 2500 * 21) >> not recommended as this will retrieve too many rows in one request
    • If you specify just the location ID you will get up to 52.500 result rows per request >> recommended in this case, it will require 400 requests in total to retrieve all predictions

Sample Application

You can find an sample load script here.

It is strongly recommended that you use the Async feature of QVSource (as shown in the sample) which will allow the connector to process the demand requests for all locations and products in an efficient way using parallel requests to the API. You will see an example of this below.

Image

Change Log

0.8.4 - 13/02/16
  • Minor internal note renaming.

0.8.3 - 01/12/15
  • Minor update so that there is now a maximum of 3 concurrent requests across all instances of the connector.

0.8.2 - 11/03/14
  • Version drop down now also accepts a text input.
  • Default version in drop down now set to 1.14.0.

0.8.1 - 29/11/13
  • Message Box warning added when neither product or location ID is specified.

0.8.0 - 26/11/13
  • First release.
  Name Size
- Blue Yonder Connector.png 80.02 KB
- Screenshot.png 122.55 KB


(QVSource works with Qlik Sense as well as QlikView - See this page for notes.)
QVSource - The QlikView & Qlik Sense API Connector | © Copyright 2011 - 2016 Industrial CodeBox Ltd