Sir,
First of all I want to thank Mr. Abdel DADOUCHE for his answer on the blog ”Predictive analytics Forecast service”. It will really help me out to generate my analysis.
I have some below mentioned queries on SAP predictive service forecast api.
Queries 1: Is it possible to register dataset and forecast data based on the generated json or odata model which we are used in the SAPUI5 application?
Actually I want to build one application based on the forecast api which will forecast next 3/6/9/12 months required man-hour on different skillset in different project at one shot. Here I am facing an another problem, suppose if in my dataset there are 10 skillsets are present then do we need to create 10 backend table for each skill and register these 10 dataset and then forecast? If answer is “yes” then I think there is no point to create any application for the end user using this predictive service, because in this situation we need to give “create table privilege” for the end user which is bare impossible task for any organization. That’s why I back to my first question again
Is it possible to register dataset and forecast data based on the generated json or odata model which we are used in the SAPUI5 application?
Regards,
Mriganka Basak
3 Answers
-
Best AnswerSep 15, 2017 at 07:40 AM
Hi Former Member
Thanks for the feedback!
To your question: Is it possible to register dataset and forecast data based on the generated json or odata model which we are used in the SAPUI5 application?
The answer is no, the predictive service cannot consume directly data from a JSON stream or an OData model in SAPUI5.
As the process takes place in SAP HANA, the data must be stored for the service to be executed.
Therefore, you will have to persist or surface the data you want to consume from your JSON stream or your OData model into SAP HANA as a table or a view.
The idea behind the predictive services, is that the service API itself is never touching the data, only the SAP HANA APL does. This also explains why the service API will not inject "data" into SAP HANA, and you can also imagine the impact on performances or security.
To your question: if in my dataset there are 10 skillsets are present then do we need to create 10 backend table for each skill and register these 10 dataset and then forecast?
The answer is no too. In the forecast service you have the ability to skip variables when computing your forecast. You can register your table once, then use it in 10 forecast calls where the list of skipped variables will vary.
For example, when forecasting skill set 1, you would exclude the other including the skippedVariables attribute in your payload:
"skippedVariables" : ["skill02", "skill03",..., "skill10"]
Hope this helps
Regards
@bdel
PS: Antoine CHABERT thanks for the notification!
Add comment
-
Sep 15, 2017 at 07:06 AM
Thierry BRUNET Abdel DADOUCHE thanks for your help. Kind regards Antoine
Add comment
-
Former MemberSep 19, 2017 at 08:28 AMHi Abdel,
As per your answer on my second question "if in my dataset there are 10 skillsets are present then do we need to create 10 backend table for each skill and register these 10 dataset and then forecast?" --- you told me to implement "skippedVariables" parameter, but as per understanding "skippedVariables" parameter is used to skip other columns which is not related with forecasting not for same column other values. Here I am giving you a scenarios which will drive you for correct understanding.
Suppose in my table there is a column name "Product", in this column we have product values like "P1","P2","P3".now if I want to forecast only on "P1" product then I don't think "skippedVariables" will help us to do this. So my question is "in this scenario what would be the correct way for forecasting?"
Regards,
Mriganka
Add comment
Add comment