In this lesson we will create the Business Adaptation Catalog Element for our solution and view the entry in the Business Configuration work center from the end user’s perspective.
The following screenshot shows the "Create New BAC Element" dialog of the studio with the minimum amount of information filled out and a preview of the desired result, which is the scoping element in the front end. As you can see, the studio dialog asks you for everything that’s necessary to display the entry in the scoping.
It would be possible to create more detailed settings for our solution that would appear under fine tuning. However, in this beginner training we will concentrate on the BAC Element and mention the remaining Business Configuration elements only for the sake of completeness.
The following screenshot shows the "New Item" dialog of the studio with a filter on Business Configuration relevant content. Apart from BAC elements, you can see three more items.
These business configuration items can be used for:
Business Configuration Set (BC Set):
Allows you to define customer specific code lists that can be adapted in fine tuning by administrators.
Business Configuration Object (BCO):
Allows you to define additional settings for your solution that can be adapted in fine tuning.
Business Configuration View (BC view)
That’s the user interface for the BCO or BC Set. A screen that is displayed in fine tuning to adapt the configuration values.
You can find more details on the Business Configuration in the SAP Help Portal. Make sure to discover the linked subpages "Business and Technical Background" and "Tasks".
The following video shows how to create the Business Adaptation Catalog (BAC) Element in the studio and the preview of the resulting scoping entry from the front end in the Business Configuration work center.
During the preview in the front end, we could see that the scoping element is showing up at the right place. However, activating it in scoping is only necessary in production tenants. Test and development tenants work differently. In these regards we only differentiate between production tenants and test tenants. A development tenant is just another test tenant that you use for developing. In test tenants the solution can be enabled and disabled from the studio with the Implementation Manager.
Keep in mind that the Business Configuration cannot be accessed with a developer user. It is a pure business user’s place. Furthermore, for scoping changes a running change project is required. Change Project is another term for Implementation Project. In test/development tenants that’s usually given.
All changes to scoping and fine tuning are kept in such a project and the project can be moved to another tenant. That’s how the cloud solution handles basic settings and transportation of them between environments. When you receive your first tenant or request a new, empty tenant, it already contains a first change project. It’s usually called "Initial Implementation".
We will come back to this topic during the deployment of the solution in one of the next lessons. If you would like to read more about working with multiple tenants and different landscapes, you should read this excellent blog post.