Skip to Content

Instance authorization in Hybris Marketing

Hi,

in application help for yMkt in chapter 5.2 is explained, how to configure a custom driven authorization on any non standard relevant field.

If we do so, there is no effect on new provided authority object / configuration in PFCG in regard to have a authority check on field level in contact app.

In BOB implementation for INTERACTION_CONTACT (building sql statement) I saw there is a part for authorization but this implementation refers to authority object configured on BO.

So I am wondering if the application help (version 1702) is not up to date or what is the correct way to enable a authorization check on field level beside the standard provided fields?

BR,

Frank

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Feb 15 at 07:14 PM

    Hi Frank,

    can you pls. provide some more details on what you're trying to achieve?

    Regards,

    Matthias

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Matthias,

      I am referring to the customizing mentioned in Application Help of 1702 in chapter 5.2 for instance authorization.

      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

      I guess the other customizing view for InfoProviders is only necessary in case of Business Warehouse?

      If I use the where-used functionality for table CRA_APP_AUTHOBJ I found only this data provider class as user (CL_CUAN_S360_DPC) which is not used for CUAN_COMMON_SRV odata service where BO Interaction_Contact is embedded.

  • Feb 27 at 09:53 AM

    We have raised the OSS 105080 / 2018.

    Add comment
    10|10000 characters needed characters exceeded