Skip to Content

Add Data model to OPI scenario

I am trying to add a Data Model to OPI. The documentation does not make is clear what is required in the table structure, except a "key field". I tried with a simple table like below, with a PROCESS_INSTANCE_ID key field, and the data model can be configured OK. However on Generate, the current context view is modified and ends up being corrupted ("Open failed: cannot read the input file"). The old solution I have found is to revert to a previous version using Replace With, Local History, ...

1. Why does the Generation modify the context view? I would expect that the Data Model is separate to that?
2. The Generate creates a new table definition named like

SPVR_MNTCE1__238047043_CTX.hdbtable in the project. Is this normal and what is its purpose.

3. Can anyone supply a working table structure as a starting point for an OPI Data Model?

I am using HANA SPS 11, OPI SPS 12


Thanks, Andy

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Feb 04, 2017 at 08:13 AM

    Just to close this off for other readers - the Data Model feature in OPI is apparently deprecated from HANA SPS12, and it is not recommended to use it. I heard this from the OPI Product team.

    Andy

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2016 at 11:28 AM

    Hello Andrew,
    What kind of data model are you referring ? Are you trying to enhance the existing context ? or change the existing context attributes ?
    Once you have generated the scenario with the context, and if you have made any incompatible changes in the context like change in used field like name change, data type change etc. then there is a process to be followed as the generated artifacts would be using it and it corrupts the business scenario. (1) For any incomaptible changes, you have to delete the gen folder (2) Reselect the source table in process context to ensure that you have reloaded the latest changes and (3) Save and Generate business scenario.

    Now answers to your questions:

    1. Generation does not modify the context calculation view. Any change in the original process context will cause this change in context calculation view and if the change is incompatible and you have not reloaded the context then it would end up issues like you had.

    2. Yes that is normal. It is not created on generation but on Save. This is the hdbtable for the context attributes that is attached to the process of the business scenario. This table is then referred in the context calculation view

    3. The table structure varies with the process participant. You can check the documentation. Like in case of Observed Process Model - we have mentioned the mandatory columns that are required and rest is upto user scenario as how they want to keep their process context.

    Hope that answers.
    You may set up a call to understand more.

    Regards,

    Archana

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 18, 2016 at 12:30 PM

    Hi,

    Sorry - my question was not clear, and this is not about the context view. The "Data Model" is an additional feature described in the Developer Guide at the link below. It is an additional table that the user can record data in.

    With a data model, you can define a structure for entering data for the business scenario during runtime, thus enabling business users to read, edit, and add business scenario instance-relevant data.

    The data model holds the business scenario instance context data. The data of the data model is stored in an SAP HANA table and is available to the user in the scenario instance view of space.me on the DETAILS tab for create, read, and update operations.

    http://help.sap.com/saphelp_opint_sp12/helpdata/en/0b/56ed2418584a1281e39450afe8c049/content.htm?frameset=/en/ea/0c164851fa42fba77a2cd200051aef/frameset.htm¤t_toc=/en/ea/0c164851fa42fba77a2cd200051aef/plain.htm&node_id=46&show_children=false

    Thanks, Andy

    Add comment
    10|10000 characters needed characters exceeded