Skip to Content

SAP PI 7.1 offering to create Models in the Enterprise Service Repository.

SAP Modelling uses ARIS models, modeling focuses on design and ensures reusability, naming conventions, and scalable interaction and integration scenarios. The aim of Modelling is to model business process flows. The model helps you to understand and then to implement the process flows or to enhance an implementation that already exists.

 

 

In a service-oriented architecture of business applications, you ideally initially model your application prior to implementation. This means that you can answer fundamental questions such as what components the application comprises of, which services the individual components offer, and how the various different components interact with each other before you begin implementation. A governance process ensures that by using models, all services are always identified and defined in the same way, thus avoiding redundancies.

 

 

The models are not system-landscape-specific. Later on, they provide useful information when implementing services, as well as during any configuration that may be required. Furthermore, the models document different aspects of a business process, increase understanding of applications across departments and businesses thereby reducing costs when applications need to be changed or enhanced in a later release.

 

Business Object: A business object (BO) represents a specific view of data of a well-defined and outlined business area. BOs are identified in such a way that there are no overlaps. Process Component: 

Process components group business objects (BOs). A BO belongs to exactly one process component.

 

Operation:

 

An operation is assigned to exactly one BO. Each BO can have more than one operation.

 

Deployment Unit:

Groups all process components that will later be installed together on the system. To enable these process components to run, it is sometimes necessary to configure the process components of other deployment units, even if this is not ideal.

Different type of models: 

Process component model:

 

The model contains information about what Service Interfaces are used . A Process Component Interaction model shows how different Process Components relate to each other, for instance the message flow between Process Components. The process component model (SAP ProcComp model) is used to describe the inner workings of a process component. You use one or multiple BOs to model the data, you define the operations and service interfaces that the process component uses to access the data/BOs, and you define the operations that are used to access other process components data. image 

Integration Scenario Models:

Integration scenario models describe which process components belong to which deployment units and how the process components interact with each other in an end-to-end scenario. The integration scenario models give a better understanding of the whole process. image 

Process Component Interaction Model:

 

Process component interaction models (SAP ProcComp interaction model) describe the communication between two process components in detail. The model shows all involved BOs, service interfaces, operations, and message types. A process component interaction model can only be used for an Enterprise Service Interaction and there can be none, one, or multiple process component interaction models assigned to one Enterprise Service Interaction. 

Business Object Map:

 

Business object maps (SAP entity map), or business object template maps, aggregate business objects or business object templates in a model for overview purposes. A business object map is an entity map, which is a structured directory of all entities of the main entity types. An entity map for a given application is a structured directory of all deployment units, process components, and business objects in the application. Business object maps are defined for all major applications and are shipped as ESR content. 

Integration Scenario Catalog:

 

Integration scenario catalogs (SAP Scenario Catalog) group and structure all the integration scenarios of a solution and thereby represent the business starting point for process modeling. The contained scenarios and their variants are clustered using integration scenario groups. You can navigate from a catalog to all contained elements.  reference:

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40db4735-02f9-2a10-b198-a888a056bb67

 

http://help.sap.com/saphelp_nwpi71/helpdata/EN/b4/5179348f9a3845b2d0d17d9419e5fd/content.htm 

To report this post you need to login first.

11 Comments

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

  1. Michal Krawczyk
    hi,

    I can see complete sentences from SOA handbook here:

    like:

    “You use one or multiple BOs to model the data, you define the operations and service interfaces that the process component uses to access the data/BOs, and you define the operations that are used to access other process”

    please either add quotes and mention
    from where you quote it from
    or remove it from the blog ok ?

    it’s not legal to copy whole sentences
    without a permit

    Thank you,

    Regards,
    Michal Krawczyk

    (0) 
  2. Manfred Maierhofer
    First of all thanks for the blog,
    what I am always wondering when talking about modeling in PI is whether there is really any customer using this modeling at the moment. As far as I no SAP doesn’t really push this topic since the future is not really clear. There are still different modeling tools around (ARIS, PI, NetWeaver BPM, SolMan, etc.) which shall – at least from a SAP point of view – become one “Common Process Layer” as described in the PI roadmap documents. But as long as the tools and also various models are not consolidated no customer will invest a lot of time and therefore money to dig into this rather complex modeling topic.

    This “Common Process Layer” would probably be a great boost for PI, too so looking forward.

    Thanks,
    Manfred

    (0) 
    1. Raja Sekhar Reddy Post author
      Hi Manfred,

      SAP PI using ARIS Modelling,I don’t know about SAP BPM it is using ARIS engine or other.,

      I worked on two pi7.1 implementations, I proposed to my customers designing modelling for landscape ,even he is not keen about that, the problem here is understanding Modelling concept bit tricky and developing models also bit complex, we need fair understating  and we have to invert more time as you already mentioned.

      Regards,
      Raj

      (0) 
      1. Manfred Maierhofer
        Hi Raj,
        that’s definitely true. I don’t think that modeling is the wrong way to go. For a SOA it is probably the only way to keep track of the architecture over time. But as long as it is not clear whether those models really survive the whole consolidation process it is hard to argue for it. For me it looks like not even SAP really knows which models will be necessary for the future since in PI there are around 13 different model types but only 2 or 3, exactly the once you also described are documented well by SAP.

        NetWeaver BPM uses BPMN as modeling notation since it is used as the basis for executable processes.

        Cheers,
        Manfred

        (0) 
    2. Trevor Naidoo
      Hi Manfred,

      I’m at a customer site that is using the modeling in PI at the moment but we’re using it purely for documentation purposes <& it makes our documents look prettier 🙂 >

      I was also wondering where the PI modeling was heading to but Michal’s blog (URL below that you’ve also seen) provides a start but the future is still a bit hazy & so is the documentation on these models:
      PI/XI: Generating configuration from Process Models – EhP1 for PI 7.1 (7.11)

      (0) 
      1. Manfred Maierhofer
        Hi Trevor,
        I am glad to see something going further now introducing this process components on ID side that Michal introduced. The last couple of month for me it looked like this modeling stuff is disappearing completely again.
        I am still waiting on the great shot by SAP to use this models not only for PI’s sake but for connection to other systems (ERP backend or NetWeaver BPM) but probably there is still some way to go.

        Cheers,
        Mane

        (0) 
  3. S. Gokhan Topcu
    No one can deny the need and importance for a careful modeling & documentation of the integration landscape, and SAP’s ARIS methodology does provide a way to do so, letting us to define one by one interactions of the business objects, or integration scenario models that can show the whole picture (direct communications, SSOs, etc) and many more. But even after reading almost everything about it, I still believe I wouldn’t be able to define a business object myself, define a CCTS-compliant interface from scratch, name, implement, diversify, seperate operations, or model a complete landscape correctly as there are just too many things to consider. The only way that seems best to use these models is to use the XI Content & ES Bundles that SAP has designed internally and delivers ready to use. Don’t you also think that this completely new modeling methodology somewhat dropped out of the skies and made a middleware expert’s job much more confusing, and there’s just too much information about it to be able to digest? I’m really looking for SAP to take these efforts further and combine their whole BPM methodologies into a more common & applicable practice throughout all their products.

    Regards,
    Gokhan

    (0) 

Leave a Reply