Why are my solutions always available without scoping ?

[Jacques-Antoine]

Hello ByD community,

I am facing a misunderstanding in the lifecycle of my solutions.

The documentation mentions you need BAC elements in order to have the Business users scope your customer-specific solution and use it.

Documentation of the 1405:

"You must create business configuration content for all solution capabilities that you create using the studio. You

create business configuration content in the studio and anchor your solution in the business adaptation catalog

(BAC) so that it is available for activation by customers who buy your solution."

But when I create extension fields and activate them through the Studio, they appear in the Cloud Solution and the business logic is well implemented without any BAC Element needed. I do not need to click on Deploy Business Config either.

And if I create the Business Option, OK, it appears in the Business Configuration, but checking or not the question doesn't make my extension fields disappear or not. It is still there!

Is it only for solution through the SAP Store which are not Activated directly from the Studio?

What really makes your solution available in the Cloud, the Scoping from the Cloud or the Activation from the Studio?

Finally, it is also mentioned:

● You can create business configuration content on your development tenant only.

So why can I create Business Options in Tests environment? I did it in two Tests tenants already.

And what is the logic behind this?

Thank you all for your help!

I wish you all a excellent week in ByD!

Best regards.

Jacques-Antoine

[Former Member · Accepted solution]

This will work on test tenants but you can not deploy it to a production tenant without scoping it in...and having a BAC.

[Former Member · Accepted solution]

First a question:

what kind of user are you using?

If you use a development user (a user having the Partner Development Workcenter assigned), these users are special, they usually do not have access restrictions and everything is shown to them.

Therefore for testing purposes I usually recomend having a business user which is not a development user.

How is it behaving with a business user?

Furthermore, what kind of tenant did you test it with?

A development tenant behaves differently than a test tenant than a production tenant.

As william already pointed out - scoping works different on the later two.

To have your solution properly scopable, you usually have to do two things:

1. Have every object assigned to a BAC entry (using the Sap Cloud Application Studio).

2. Have your WCFs assigned to your scope context (from the UI Designer).

[Copy-Paste from the 1405-Studio Library, chapter 9.3.2.8.:]

3. Configure the work center.

a. Specify the scope rules for the work center and the view switches:

1. In the Properties Explorer, select the work center.

2. Under Configuration-ScopeRules, click ... .

3. In the Scope Rules Editor, assign the required scope rules and click OK.

4. Repeat the steps for all the view switches.

[/Copy]

[Jacques-Antoine · Accepted solution]

Thank you for the answer! It clarifies why we need the BAC elements.

[Jacques-Antoine · Accepted solution]

I tested this with my Business User. I always do this. So yes, I can see, with this user, my extension fields created in the Studio as soon as they are activated.

The tenants I tested it on is a Partner Test tenant and a Customer Test tenant.

Do we have a documentation which specify the differences between the 3 types of tenant?

Thank you very much for your help.

Best regards.

Jacques-Antoine