okay in this video we are going to talk about how we are what is s OD what is compliance calibrator how we are going in that class we are going to talk about simulate how do how we are going to simulate or we are going to mitigate what is the rule architect and some important questions about about the interview so over here we are just I am just going to give you the overview about s OD is how how does it look like and how to remove their so D and what are the different procedures of the moving that's what is what creates their stories and stuff like data and what are the typical what what this whole bus screen looks like and what are the different objects present on this process screen okay so this is this is for point over them for compliance calculator now there is like ten before then there was 5.3 which is web-based and now it's based again in the class I can show you like I will show you five point three and ten I'll try to show you five point three in there okay so in this one let's see like the how how many different there on what basis we can analyze the expertise for example we can analyze the a so Lisa on user basis or on road races if we can analyze the on user basis how many types on a single role on a single user or a group user then on the role pieces on single rows and then on the profiles or like there's like the limit to it like parameters like you have to you can assign like you know and then like the one more combined analysis okay this is the these are the options in the first box then in the second box we have the absolutely risk level how many are the risk levels these risk levels has been defined by the company that like okay we are going to run the report on medium high critical low it's up to them or it depends like you know they want to run the report on all okay on what the month length is holy is like one of those well the critical transaction our critical authorization objects there has been a sign and everything is done then on what level we are going to run the report when the report on a critical transaction code means like a Saudi at like transaction Saudi which is going to create on there because of something because of assigning to similar transactions or asserting which are going to be created on two similar authorization objects okay then the other other parts that we are going to look in the today in this video is like user type there are different user types you can do the exclusions but we are looking at like for example lock users expired users expert rules mitigating controls so usually we just click all these three just three and now we just leave the medicating control so controller we have the before and then there is a peak global rule matrix set like you know it's called global like what they already have they already assigned all the similar transactions they already care they're basically all the similar transactions in one place which makes our job easy okay so for this one let's go and check like one role which already have the Saudi so I know like I already created one row which is there sorry I will be undressed patrol let us run the report on transaction code level and see what happened see over here it says P 0 0 1 0 0 2 e 0 0 1 0 0 2 sales create fictitious vendor and initiate payment to the vendor p 0 0 1 is the risk ID and this is 0 0 2 is the permutation combination you will go through like you know what all these things like known over all these things like you know in detail like when we are in the class so this is the technique this is this is the summary report this is the role it tells you the role role description transaction grab these two these two transactions are similar that's why like the level of the risk is high and it will it's creating there sorry that's what the report looks like so once you want to remove the sorry button what you can do is if you are going like on a transaction code level the only option you have is like - yes - break the roads right now so these are the only two other key codes so just break it and make two rules one with F 1 and F - 42 and the other one with FK 0 1 right the other report we are going to run it is on authorization object level this one has been run by SOT a transaction for doing this one will be run we will execute authorization object left ok see like an authorization object level we have like all these with the transaction code we have the authorization objects - what's the common thing was the key keeping in this one is like a we have to find out all because of all these fights create ok create 32 and create vendor we are going to find out that like what we are going to do is we are going to remove any of the authorization object or anybody course this will remove the SOT ok so what we are going to do is like we are going to remove the count type from this road ok so let's go and go in the new second so there's going the authorization of this okay once we assign this now come back to the same level again and execute on the traditional see it says no conflicts found so if you like if you like my teaching I'll call back at six three zero three three six five nine seven eight my name is Edna thanks bye