One of the Essences of SAP Software Design: The Design of Various Determination Logic

The Perfect Embodiment of the Configuration Over Code Principle

Any programmer who has worked on the design of moderately complex backend systems should be familiar with the principles of `Configuration Over Code` and `Convention Over Configuration`. The first principle suggests that configuration should take precedence over hardcoding logic, allowing for greater system flexibility by enabling customization through configurations rather than hardcoded logic.

While this principle is straightforward to explain, how is it applied in real development work?

Drawing from over a decade of experience in ERP software backend system development, I’d like to share my understanding of this principle.

The decision mechanism in ERP software is often overlooked, not because it isn’t important, but because it is so pervasive in both the frontend and backend implementations of ERP systems that it becomes almost invisible, much like the air we breathe.

A decision mechanism processes a set of inputs to produce a set of outputs. Essentially, it comprises three parts:

1. Input Set: This data can come directly from user input or from the output of upstream business logic. In systems running SAP software, the combinations of input data can theoretically be infinite.