HSS: Required PTV license for BYOL model

[jef]

Hi folks,

I would like to use HANA Spatial Services in conjunction with the SAP TM integration. To do this, in addition to the HSS license, I need to provide my own license (BYOL) for the provider behind the HSS.
What license do I need if I want to use PTV as the provider? Is there a trial license available for this?

Thank you very much and best regards
Jens

[Bernd Welter]

Hi Jens,

thanks for that question - that is a very good one! I hope the following statements give clarity - I will also forward this article to some guys in the SAP HSS team for a cross check:

• Besides PTV Developer the HSS concept supports multiple backend providers. Depending on the chosen provider you need to check the SAP documentation about how to enable the BYOL authentication. With PTV Developer this is based on a unique ID which is called "the ApiKey".
• From PTV Developer's perspective an ApiKey is associated with a so-called plan and depending on the plan the ApiKey is regulated.
  • Right after "buying" the initial product "Free Developer" you will have access to one initial ApiKey which grants access to a bare minimum of functions. I recommend that you immediately get back to your account manager within PTV Logistics who can elevate your plan to a more powerful version.
  • Extended plans such as "Personal Contract Plan VRP-PD Entry", ... "Personal Contract Plan VRP-PD Power" enable your ApiKey to compute more complex scenarios. Furthermore an elevated plan enables you to use the Account API to create sub-ApiKeys.
• On top of the Plan specific regulations there are also restrictions that apply for all ApiKeys - no matter which plan they use. Please check the Request Limits and the Rate Limits.
• The specific usage of the ApiKey via HSS is then implemented based on SAPs business logic, therefore we as PTV Logistics cannot comment directly on how this is implemented. But if you are running into error messages with an elevated plan/ApiKey get back to ME 1:1 and I will contact SAP on behalf of this. Please do NOT bypass me in this case - I really need to be aware of any issue that might come from this topic.

Do not hesitate to return to us if you need more answers.

Bernd

PS: especially the rate limits often require users to use multiple ApiKeys and to apply some load distribution, e.g. based on

• Round Robin
• One ApiKey per frontend user / per depot...

Please check this right from the start - it might be necessary to develop a proper strategy in advance. Applying a strategy afterwards might cause morfe efforts than a a-priori consideration.