The business configuration enables customers to set up the system to meet their requirements. It controls how the SAP solution as standard software adapts to the customer’s needs.
The business configuration consists of two main working areas:
- Scoping: Setting the solution scope, that means activate and deactivate features.
- Fine Tuning: Control how activated features behave in detail.
Scoping allows administrators to activate and deactivate functionalities and enables them to control how business processes work. For instance, if the sales process contains the sales quote or if order handling should leverage the integration to a backend system rather than processing in the cloud solution.
PDI add-on solutions are just another example for functionalities that can be activated to influence business processes. Inside the development tenant all developed features are immediately reflected by default. In a productive system the solution needs to be activated by a scoping decision before you can make use of the additional features.
Before we deep dive into the developer side, let’s have a look at the Scoping from the end user’s perspective first. The following screenshot shows two consecutive steps of the scoping process next to each other: Step three, the "Scoping" on the left and step four, "Questions" on the right.
The scoping elements tree, that we can see in both steps, is a combination of business areas and their respective features on a high level (like the decision to use Sales Quotes or not). In step three we can choose these high-level features. Step four takes us to the next level where we can define what detailed features of the respective scoping element we would like to use by answering the questions (such as for sales quotes: if we want to use a multi-step approval process, or formatted text in sales notes, and so on).
Fine tuning allows us to define how the activated features will work on a more detailed level. For instance, what kind of Sales Quotes (Document Types) are defined or what number ranges should be used, and so on.
The following screenshot shows the fine tuning activity for sales quotes and the document type definition as an example:
Business Adaptation Catalog
The technical term for scoping that we use within the studio is Business Adaptation Catalog (BAC). It outlines the complete set of the SAP cloud solution’s capabilities and organizes and structures the capabilities into a hierarchy of business areas, packages, topics, and options.
Our PDI solution is yet another option like this. If you want to use it in a productive environment, it needs to be activated in scoping beforehand. That means we have to create and place an entry for our solution in the scoping, meaning the Business Adaptation Catalog. The entry for our solution is called the Business Adaptation Catalog Element (in short BAC Element) and will be created for our sample solution in the next lesson.