In dit plaatje ter verduidelijking

In dit plaatje ter verduidelijking nogmaals aangegeven hoe de organisatie zich vertaald naar de SAP situatie.
Stippellijn ; CSI adviseert dit niet te doen; echter deze keuze zal sterk worden bepaald door de situatie/organisatie. (voorbeeld Lum: grote en kleine fabrieken en verkoopmijen, auth concept gebaseerd op de grote organisaties immers daar zijn de functies het meest gediversificeerd. In kleine organisaties werken met meerdere functies per gebruiker, echter dit zou kunnen leiden tot cumulatie van autorisaties en SoD conflicten. Daarom wellicht te kiezen voor directe toewijzing van Single roles aan een gebruiker. (de benodigde single rol veroorzaakt geen conflict, maar wel de functie waarin deze single rol is opgenomen.
Bij Achmea is gekozen om alleen composite roles (via IDM ) toe te wijzen aan gebruikers. Consequentie is dat er een (groot?) aantal Composite rollen bestaan waarin slechts 1 single rol is opgenomen (check bijv de procuratielevels).

ผลลัพธ์ (อังกฤษ) 1:

In this picture to clarify once again shows how the organization is translated to the SAP situation. Dotted line; CSI advises not to do this; However, this choice will be greatly determined by the situation/organization. (example Lum: large and small factories and verkoopmijen, auth concept based on the large organizations, after all, there are the features the most diversified. In small organisations working with multiple functions per user, however this could lead to accumulation of authorizations and SoD conflicts. Therefore may have to opt for direct allocation of Single roles to a user. (the required single role does not cause any conflict, but the position in which this single role is included.At Achmea is chosen to only composite roles (via IDM) to users. Consequence is that there is a (big?) number of Composite roles exist in which only 1 single role is included (check e.g. the procuratie levels).

ผลลัพธ์ (อังกฤษ) 2:

In this picture to clarify once again shown how the organization is translated into the SAP situation.
Dotted line; CSI advises not to do so; However, this choice will be largely determined by the situation / organization. (example Lum: large and small factories and verkoopmijen, auth concept based on large organizations, after all, the features are the most diversified as In small organizations work with multiple functions per user, however, this could lead to a duplication of authorizations and SoD conflicts.. therefore might opt for direct allocation of Single roles to a user. (the required single role does not cause conflict, but the function in which this single role has been recorded.
Achmea has chosen to only composite roles (via IDM) attributable to users. The result is that there is a (big?) number Composite roles exist which includes only one single role (check eg the procuratielevels).

ผลลัพธ์ (อังกฤษ) 3:

in this picture to clarify again indicated how the organization is translated into the juice situation. the dotted line; csi advises not to do this; however, this choice will be strongly determined by the situation / organization. lum (example: large and small factories and verkoopmijen, auth concept based on the big organisations because there are the most gediversificeerd functions.in small organisations working with multiple functions for each user, however, this could lead to accumulation of authorisations and sod conflicts. therefore, to choose direct allocation of single roles to a user. (the necessary single role caused a conflict, but the function of this single role is included. "with achmea is chosen for composite roles (via ibm) to users. consequence is that a (?) number of composite parts which are only 1 single role is included (e.g. the procuratielevels (check).