SAP’s Operational Process Intelligences (OPInt) helps line-of-business users to gain process visibility across their end-to-end business processes, without forcing IT to rip and replace existing systems. By acting as a business navigation system, SAPOPInt helps business users to achieve business outcomes

In SAP OPInt, Business Scenario is the leading entity that represents the end-to-end business process that spans across multiple systems. By bringing in all related process logs and context into cohesion, a Business Scenario provides an end-to-end visibility in a contextualized fashion to the line-of-business (LOB) users.

Solution expert (the persona who discovers processes from multiple source system and models the business scenario) can create measures and indicators that are required by the LOB users. Once the modelling is complete, the solution expert triggers a ‘Generation’ process that generates scenario artifacts like calculation models, analytical privileges, procedures, roles, OData services which can be consumed from the ‘Workspace’.

This blog concentrates on the common errors encountered during the generation processes and also tries to explain how you can overcome those errors.

  • Whenever the generation fails, check the generation log for information.
    • Basic validations like scenario cycle time should be greater than or equal to the sum of individual phase cycle time
    • Make sure you have atleast one event that is marked as Scenario Start and atleast one event marked as Scenario End.
  • If you are modifying the context calculation view, then make sure that SCENARIO_INSTANCE_ID is available in the Output along with other context attributes. Also make sure that PROCESS_INSTANCE_ID is not available in the Output.
  • When you get an exception in the generation log (PVArtifactPersistenceException).
    • Check if there are any inactive objects in the gen_* package. Validate the inactive objects individually to have more clarity on the exact problem that caused the exception.
  • Error due to Internal deployment of object failed: The error description gives you more information about the reason for failure.
    • One such example could be OutOfMemory problems in the HANA server which could be solved by restarting the server.
  • Internal Error: Create Scenario: failed aCalcEngine.createScenario() user is not authorized
    • The _SYS_REPO user doesnt have enough authorization to the schema which has the event logs. The owner of the schema should give SELECT and EXECUTE with grantable permission to the user _SYS_REPO.
  • You have changed the name of context attributes or removed some context attributes in the context calculation view and triggered a re-generation, but the generation fails.
    • You have to delete the generated objects under gen_* package in the following order and then trigger re-generation
      • Generated Roles for your scenario (If you dont see roles under gen_* package then go to menu Window -> Preferences -> Modeler ->Content Presentation and check ‘Show All Objects in Navigator’)
      • Generated Analytical Privilege
      • Generated oData services
      • Pattern Calculation Views (All generated calculation views other than the ones starting with SPVR)
  • You want to delete all the generated objects and trigger a fresh generation (if none of the above tricks work to solve error due to dependencies, you can try this). The deletion should happen in the exact following order in order to prevent error due to dependency
    • Generated Roles for your scenario (If you dont see roles under gen_* package then go to menu Window -> Preferences -> Modeler ->Content Presentation and check ‘Show All Objects in Navigator’)
    • Generated Analytical Privilege
    • Generated oData services
    • Pattern Calculation Views (All generated calculation views other than the ones starting with SPVR)
    • Generated Procedures in the following order:
      • SPVR_*_META
      • SPVR_*_CTX*
      • SPVR_*_PH_PROC
      • SPVR_*_PROC
    • Pre-processing calculation views that starts with SPVR under your scenario gen_* package
To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Andrew Frigaard

    Hi Sheshadri,

    This is a useful article – it is a couple of years old, but I think the generated objects are still largely the same.

    I found that the steps above for “You have changed the name of context attributes” also was applicable when I changed the name of a Measure or Indicator, and then got some generation errors, referring to the calculation view with the old Measure name.

    What is good practice when Measures or Indicators must be changed?  Should we delete from the right pane of the business scenario editor and then re-create?

    Andy

    (0) 
    1. Archana Shukla

      Hello Andrew,

      What Seshadri has mentioned hold true when you change the context attribute name. Because when you change the name, the references are not updated automatically and so a manual intervention is required to correct the references.

      But that is not the case with Measures or Indicators for Count and Duration type. You can rename them and just Generate the business scenario. Rest all is taken care by OPInt.

      – If you have used the generated calculation view of the measure or indicator somewhere then that issue would occur.  If you have created measure based on external measure then also you have to manually change the measure and then regenerate.

      Hope that answers.

      Regards,
      Archana

      (0) 
  2. Simon Simoni

     

    Hi Seshadri,

     

     

    I have this error message when try to generate the Business Scenario.

     

    Which prevents all the gen_<business scenario name> package’s items activation. In fact,  the error is from SPVR_< business scenario name >_META.procedure !

     

    Could you please advise also about this one?

     

    Regards,

    Simon

    (0) 

Leave a Reply