Comparing Process Integration Scenario with Procomp Interaction Model

Posted on Aug. 16, 2010 at 09.30 PM - Kuala Lumpur, Malaysia

Which one is better? ProComp interaction or process integration scenario model? Let's list down advantages and disadvantages of each technique:

Advantages of ProComp interaction model:

1. It is based on ARIS modeling tool, even though there is no guarantee objects created using ARIS tool can be directly imported to SAP PI modelling tool
2. It better describes objects involved in the integration/interaction, from business object level up to message type level
3. It is used as a template to create repository objects as well as configuration objects.

Disadvantages of ProComp interaction model:

1. It's more difficult to create this model as compared to process integration model
2. The message type and operation type can not be linked directly to SAP IDOC or RFC. We need to create a freely defined operation and message type to wrap it.

Advantages of process integration scenario model:

1. It's easier to create as it ONLY describes actions involved in the integration.
2. It's easier to be imported to integration builder to create configuration objects
3. The action can be linked directly to SAP IDOC or RFC right away.

Disdvantages of process integration scenario model:

1. It does NOT describe the objects involved in the integration/interaction detail enough
2. It only provides a limited template in creating repository objects

All in all, I personally will still be using process integration model, while waiting for ProComp model to be more mature, or become significantly more useful than process integration model.

Life is beautiful! Let's make it meaningful and colorful!