Name: Discovering B2B Terminology in SAP Customer Data Cloud
Uploaded: 2024-5-29
Duration: 235 s
Description: This video explains the CIAM for B2B terminology, which will help you to understand the next videos.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div>This video explains the CIAM for B2B terminology, which will help you to understand the next videos.</div></div></div></div></div></div>

Discovering B2B Terminology in SAP Customer Data Cloud

I'm going to spend a bit of time just talking about terminology in the context of the Kiantha B2B solution. When we talk about entities that we interact with from the solution point of view, and especially from an authorization point of view, we've got terminology that means different things to different people, even though maybe we're referring to the same thing. So we're going to just talk about those different entities and talk about what else they might be referred to us. So, the first thing is an organization and when you think about it, it's actually quite a simple concept. It's an organization that a business works with and that could be their customers. It could be a partner of theirs. It could be a distributor, a vendor, a reseller. There are lots of different concepts. The point is these are organizations that your own organization is working with. Now, we might see these referred to as business partners or sold to parties, especially in the context of backend SAP systems. You might also see them called accounts in those same systems. You might see them referred to as commerce B2B accounts if you're speaking with commerce colleagues. The point is that these are organizations that are external to your own organization that you work with to fulfill your business duties. We will always refer to it as an organization when we talk about the solution. Next, we have an organization member, which of course is very easy to understand, someone who works for those external organizations that we just talked about to fulfill their business duties. Now, these could take lots of different forms within that organization. People can have different job titles and roles within those organizations, but ultimately they are the people who use the systems that we are granting access to. We might also see them referred to as a contact or we might see them referred to as a commerce B2B customer when talking with our commerce colleagues. Next, we've got the concept of roles. And I think probably of all the terminology, this is probably the most complex one because it's gonna mean different things to different people. In the traditional world of authorization, when we talk about roles, we probably refer more to what we call these technical roles or functional roles. Roles that are given to you in a system that might describe what you're able to do in that system. Maybe a very simple example of that might be like an AD group. And then on the other side of things, we've got business roles. And these business roles really describe who you are as an identity rather than what you can do. So this might be that you're a doctor, or a technician, or an installer. It doesn't necessarily describe what you have permissions to do, but it describes who you are as an identity. And then we also have organizational roles, which describe your role within an organization. And these could be based on attributes like a job title or department. I think this is really a key concept to understand, especially when we start talking about policy-based access control later on, to understand the differentiation between these different types of roles. And finally, we talk about assets, the things that we're trying to protect, the things that we are protecting access to from the users. We might also see these referred to as resources.