Skip to Content

S4HANA Transports - Embedded Analytics & Custom CDS

Hi All,

Had some questions on transport of standard and custom CDS views on S4HANA. Can you please help me with the below:

1. Do standard CDS views need a transport from Dev to Prod or do they exist as part of the initial state of S4HANA installation?

2. I assume extensions and custom CDS are transported via the SAP standard transport mechanism of an object assigned to a non $TMP package. Is this correct?

Any references/links in this regards would be helpful as well.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 17, 2018 at 10:50 AM


    mind that a CDS View is a Definition only.
    Standard CDS Views must exist in the Q or Prod system.
    Customized CDS views or extensions to standard CDS views must be transported.

    Mind that a CDS View generates Code ( Analytical, ODATA, etc.).
    You must transport the CDS definition.
    You may not transport the CDS View generated Code ( Analytical, ODATA, etc.).
    NoGos: Never Change the CDS View File name AND/OR the CDS view Definition AND/OR the ABAP View name in a Q or P System.

    In Detail:
    A customized or standard CDS view is assigend to an (ABAP -) Package:

    A customized CDS Views is a transport object of its own (Question 2):

    A customized CDS View must be transported:
    ( NOT the underlying ABAP or SQL views):

    I hope that clearifies.

    Best Martin

    Add comment
    10|10000 characters needed characters exceeded