Building multiple applications vs single application for different regions

[Former Member]

Hi Experts and Carsten,

I have a question related to whether to go for single or multiple applications.

Our business has three regions and around 60% of the rules are shared between regions as of now.

In this situation, i am just wondering whether to go for Single application with three different functions for three regions or to go with three different applications and three functions?

What is the usual approach and what are the benefits with it?

Thank you

Kris

[Former Member]

Hi Carsten,

Thanks for providing your thoughts on this. Here are other things to consider.

1. We expect future functionalities may differ among regions, How would this factor influence the single vs multiple applications decision?

2. If we go with single consolidated application approach,

    A) From system maintenance perspective, how do we avoid impact of issue caused in one region on other regions?

    B) If a common object is used among the regions and if there is any future change, It may lead to regression test of all three regions.This may be another factor to consider.

What are your thoughts on this.

Thank you

Kris

[carsten_ziegler]

Of course, when you reuse you need to make sure an object is not just changed by anybody but only after alignment with all users. Reused object that shall be changed may be copied. This is not specific to rules.

Recommendation:

The resue parts should be changed by selected persons only and a governance model should be introduced. You may also allow changes only in certain clients or systems and then transport into the systems where the users are worked on. However, this can slow down your processes and limit your agility. The same can be achieved with authorizations within one system+client.

[carsten_ziegler]

The information you provided is not sufficient for a helpful answer.

There can be good reasons (visibility, other transport behavior) for having a reuse application that allows to share objects to three functions (applications).

Usually, it is a good practice to create reuse data objects as system objects and share them in multiple functions that are related.

[Former Member]

Hi Carsten,

Appreciate your quick response like you always do.

We have a business scenario where we receive return request and it has to go thru set of validations (some are as per policies). Validations involves data accuracy and verification of policy compliance like not allowing more than certain quantity of return, escalating if value is more than certain $ value etc..

Some of these data validations are same across regions and some are different. There is a chance to use same decision table across regions and most of the data elements if we build in same application.

Will there be any additional advantage by going with different applications?

I am not sure if this information would be suffice for you to guid us, Please let me know if any additional information would help you guide us.

Thank you

Kris

[carsten_ziegler]

A couple of times I did the following in such cases.

Application 1 (system):

Data Objects, Procedure Call expressions, .. (whatever is reuse and more technical and not expected to change often)

Application 2 (customizing)

reuse expressions (e.g. Decision Tables) that are likely to be changed more often

Application 3-n (customizing)

Complete functions reusing objects from Applications 1 and 2

Per department, area etc one new application for clear assignment of responsibilities.