Custom Authorization-Relevant Fields

1
Custom Authorization-Relevant Fields If you require additional authorization-relevant fields, such as Customer No., perform the following steps: 1. Provide the authorization-relevant field in an appropriate SAP HANA information model by joining the respective data table. Make sure that the field is part of the model's output structure. 2. Create an authorization object for each additional authorization-relevant field. You can use Maintain Authorization Objects (transaction SU21) to define authorization objects. 3. Indicate the additional authorization object(s) in Customizing for SAP hybris Marketing (formerly SAP Customer Engagement Intelligence) under General Settings Authorization Assign Authorization Objects . In addition, assign the additional authorization-relevant fields using the customizing activity Assign Authorization Object Fields to InfoProviders . For authorization-relevant fields from SAP Business Warehouse, observe the following additional steps: 1. Set up the new fields in the respective BEx Query as an authorization field. 2. Indicate the new fields in the Customizing for SAP hybris Marketing under General Settings Authorization . Restrictions Note the following restrictions when defining authorization objects and authorization profiles: Different organizational criteria cannot be combined within one authorization object. For example, you cannot create an authorization object containing a sales organization and a sales office. However, you can create multiple authorization objects each containing a different organizational criterion, and assign these authorization objects to a role as described above. For SAP Business Warehouse data, intersections are not supported for the authorization values of organizational criteria. For example, the user is authorized for the sales organizations 1000 and 2000. Once this user indicates sales organizations 1000, 2000 and 3000, no data at all is provided by the system. This applies even though the user is authorized to access the intersection of data for sales organizations 1000 and 2000.

description

Custom Authorization-Relevant Fields

Transcript of Custom Authorization-Relevant Fields

Custom Authorization-Relevant FieldsIf you require additional authorization-relevant fields, such asCustomer No., perform the following steps:1. Provide the authorization-relevant field in an appropriate SAP HANA information model by joining the respective data table. Make sure that the field is part of the model's output structure.2. Create an authorization object for each additional authorization-relevant field. You can useMaintain Authorization Objects(transactionSU21) to define authorization objects.3. Indicate the additional authorization object(s) in Customizing forSAP hybris Marketing(formerly SAP Customer Engagement Intelligence) underGeneral SettingsAuthorizationAssign Authorization Objects. In addition, assign the additional authorization-relevant fields using the customizing activityAssign Authorization Object Fields to InfoProviders.For authorization-relevant fields from SAP Business Warehouse, observe the following additional steps:1. Set up the new fields in the respective BEx Query as an authorization field.2. Indicate the new fields in the Customizing forSAP hybris MarketingunderGeneral SettingsAuthorization.RestrictionsNote the following restrictions when defining authorization objects and authorization profiles: Different organizational criteria cannot be combined within one authorization object. For example, you cannot create an authorization object containing a sales organization and a sales office. However, you can create multiple authorization objects each containing a different organizational criterion, and assign these authorization objects to a role as described above. For SAP Business Warehouse data, intersections are not supported for the authorization values of organizational criteria. For example, the user is authorized for the sales organizations 1000 and 2000. Once this user indicates sales organizations 1000, 2000 and 3000, no data at all is provided by the system. This applies even though the user is authorized to access the intersection of data for sales organizations 1000 and 2000.