Customer-specific solutions in SAP Business ByDesign
Now let's go ahead and go into the studio, and we'll create our own customer-specific solution
that we will be ready to start development.
So you can log in to the SAP Cloud Applications Studio. In the left-hand part
is the My Solutions screen. These are all the solutions that exist on this tenant.
Let's go ahead and create one new solution here.
We are going to use this button at the top of the My Solutions part that says Create Solution.
And it gives me a screen here for some details for me to enter. What's the solutions type? You
can see there's Customer-Specific Solution and Solution Template.
For now, we're going to stick with a customer-specific solution. I can see what the customer is.
Now it's grayed out because this is considered a customer test tenant.
If I had a partner development tenant, I could develop solutions for any number of customers.
And I would have to say which customers I want to maintain or which customer am I building
this solution for.
And here, we don't have that, it's just a specific customer tenant, so we can continue on. I
would give it some type of description. Let's go ahead and say openSAP_DEMO.
And then a deployment unit. You see there's a large list of deployment units. We're going to go
ahead and select Customer Relationship Management for now.
We'll come back to what a deployment unit is in the next unit. For now, assume CRM. And
then I've some final details.
Basically, who's responsible for the solution. So now we can see that I'm responsible. Here's
my company here's my e-mail address, so that way if anybody wants to know anything they
can always come to contact me regarding this solution.
Let's go ahead and say OK. And now this is going to generate the solution for me.
So this solution is created by me and my user, but it's relevant and visible to all other
developers within this tenant. So that means if I have a colleague of mine that logs into the studio with their user, they would
also see the solution. They would be able to see any solutions that are created there, just like I
can.
There's no content that's developer-specific. So that means that any developer can log in to
the studio, and then they can go and maintain content with any solution. There are no restrictions
there.
If I have any kind of such restriction, I need to maintain and manage it myself with that other
a person or other people.
Now you can see that my solution is created. We have openSAP_DEMO, the name of the
solution that I gave it. You'll see there's this technical name: YOTWMM8, why?
00:07:13 This is the ID of my solution so to speak. You'll see this Y ID in a lot of different places going
forward,
And then on the right, you see, in the Solution Explorer, that it has the name as well there. It
says that it's in development, meaning I'm currently available to develop items and content
within a solution, and what content the solution currently has. Right now it's empty, so we don't have anything
but we will start maintaining it going forward.
One other thing that I want to mention about solutions in the studio is that every customer-specific solution that we use is specific only to itself and exclusive with its content.
That means that if I have more than one solution in a tenant – I have solution A and solution B
– the content of the two don't know each other that they exist, they cannot talk to each other.
So if I have a business object in solution A, I won't be able to directly use that business object
in solution B.
There's segregation between each solution that's there. This is a really important point when
it comes to developing.
You'll even see in the help content, it's recommended that you try to keep to one solution per
customer. This is just a recommendation, it's not a requirement, it's not a rule.
Really the reasoning is just that any content again that's built-in one solution cannot be reused
in another solution.
So this is something to keep in mind when you're building your solutions when you're
developing your content. It doesn't mean that you can't have more than one solution,
you very well may have different projects that will have no relevance to each other in the
future, in which case there's no reason not to use different solutions.
Really, the decision is up to you, and what you plan to do with this solution and the future of
that solution.
that we will be ready to start development.
So you can log in to the SAP Cloud Applications Studio. In the left-hand part
is the My Solutions screen. These are all the solutions that exist on this tenant.
Let's go ahead and create one new solution here.
We are going to use this button at the top of the My Solutions part that says Create Solution.
And it gives me a screen here for some details for me to enter. What's the solutions type? You
can see there's Customer-Specific Solution and Solution Template.
For now, we're going to stick with a customer-specific solution. I can see what the customer is.
Now it's grayed out because this is considered a customer test tenant.
If I had a partner development tenant, I could develop solutions for any number of customers.
And I would have to say which customers I want to maintain or which customer am I building
this solution for.
And here, we don't have that, it's just a specific customer tenant, so we can continue on. I
would give it some type of description. Let's go ahead and say openSAP_DEMO.
And then a deployment unit. You see there's a large list of deployment units. We're going to go
ahead and select Customer Relationship Management for now.
We'll come back to what a deployment unit is in the next unit. For now, assume CRM. And
then I've some final details.
Basically, who's responsible for the solution. So now we can see that I'm responsible. Here's
my company here's my e-mail address, so that way if anybody wants to know anything they
can always come to contact me regarding this solution.
Let's go ahead and say OK. And now this is going to generate the solution for me.
So this solution is created by me and my user, but it's relevant and visible to all other
developers within this tenant. So that means if I have a colleague of mine that logs into the studio with their user, they would
also see the solution. They would be able to see any solutions that are created there, just like I
can.
There's no content that's developer-specific. So that means that any developer can log in to
the studio, and then they can go and maintain content with any solution. There are no restrictions
there.
If I have any kind of such restriction, I need to maintain and manage it myself with that other
a person or other people.
Now you can see that my solution is created. We have openSAP_DEMO, the name of the
solution that I gave it. You'll see there's this technical name: YOTWMM8, why?
00:07:13 This is the ID of my solution so to speak. You'll see this Y ID in a lot of different places going
forward,
And then on the right, you see, in the Solution Explorer, that it has the name as well there. It
says that it's in development, meaning I'm currently available to develop items and content
within a solution, and what content the solution currently has. Right now it's empty, so we don't have anything
but we will start maintaining it going forward.
One other thing that I want to mention about solutions in the studio is that every customer-specific solution that we use is specific only to itself and exclusive with its content.
That means that if I have more than one solution in a tenant – I have solution A and solution B
– the content of the two don't know each other that they exist, they cannot talk to each other.
So if I have a business object in solution A, I won't be able to directly use that business object
in solution B.
There's segregation between each solution that's there. This is a really important point when
it comes to developing.
You'll even see in the help content, it's recommended that you try to keep to one solution per
customer. This is just a recommendation, it's not a requirement, it's not a rule.
Really the reasoning is just that any content again that's built-in one solution cannot be reused
in another solution.
So this is something to keep in mind when you're building your solutions when you're
developing your content. It doesn't mean that you can't have more than one solution,
you very well may have different projects that will have no relevance to each other in the
future, in which case there's no reason not to use different solutions.
Really, the decision is up to you, and what you plan to do with this solution and the future of
that solution.
0 comments:
Post a Comment