Prevent Creation of CDS Views and AMDP Methods

    Hi,

    At my company we are currently implementing SAP HANA as a backend database for our ECC system. We are not sure when we will go live.  At the same time we want to roll out the ADT to all of our ABAP developers.  However, there is a concern that people will create CDS views and AMDP methods using sqlscript for projects that will go live before we migrate to SAP HANA DB as our backend database.  That would mean that projects would either have to rework or push.  We’d like to prevent this from happening by preventing someone from creating a CDS view or AMDP based method.  Does anyone know of a way to do this?

    I did check the authorization list, but I did not see anything.

    Thanks!. 

    Hi,At my company we are currently implementing SAP HANA as a backend database for our ECC system. We are not sure when we will go live.  At the same time we want to roll out the ADT to all of our ABAP developers.  However, there is a concern that people will create CDS views and AMDP methods using sqlscript for projects that will go live before we migrate to SAP HANA DB as our backend database.  That would mean that projects would either have to rework or push.  We'd like to prevent this from happening by preventing someone from creating…

    Prevent Creation of CDS Views and AMDP Methods

    Very Helpfull

    User Rating: Be the first one !
    Reviewer Asked on November 2, 2016 in eclipse.
    Add Comment
    1 Answer(s)

      Hi Richard,

       

      if there is no authorization object for AMDPs, you could at least monitor all created AMDP classes by just performing the where-used list on the interface IF_AMDP_MARKER_HDB as all implementations need to declare it.

       

      In the result list, you can filter on the packages you are using in your projects if there are too many results.

       

      Best regards, Sebastian

       

      Add Comment

        Hi Richard,

         

        if there is no authorization object for AMDPs, you could at least monitor all created AMDP classes by just performing the where-used list on the interface IF_AMDP_MARKER_HDB as all implementations need to declare it.

         

        In the result list, you can filter on the packages you are using in your projects if there are too many results.

         

        Best regards, Sebastian

         

        Add Comment

        Your Answer

        By posting your answer, you agree to the privacy policy and terms of service.