Data Element Generation (GDE)

Intro

Using the automatic Data Element Generation based on QPPD elements can save a lot of manual work by developers working with QPPD. Often, QPPD elements are maintained by different departments within your company. Not very often the QPPD elements are maintained by developers which usally has requirements for classic Data Elements to proceed with their work regarding technical interfaces, apps, queries, .... In this case a developer first needs to translate the QPPD element customizing to a DDIC data element. Each time the QPPD element got updated, the developer needs to adapt the Data Elements.

warning

This is a time consuming task which is prone to errors. Let the developer focus on the important/business logic things!

Our solution is to have a Workbench generating Data Elements/Domains which then can be easily used anywhere in your SAP system. The Data Elements are generated automatically and visualized in a user-friendly workbench where all differences and errors can be resolved.

info

The Data Element Generation is only the first step in our journey simplifying and reducing efforts and can be seen as a precondition to open doors for your Business Layer/Interfaces/Interface Views(CDS).

Technical Overview

Data Elements for QPPD elements gets administrated in our very own Workbench called /MXP/QP_GDE (transaction). As this is an UI5 App you can also start GDE using the following information:

Each Data Elements gets its own Domain (where it makes sense, e.g. not for BOOL which is simply BOOLE). A Data Element gets linked to a QPPD element by automatically adding it as a attribute for the QPPD element customizing (which can be called with transaction /SCT/QP_C21).
Please note, that you cannot see the Data Element linked to a QPPD element directly in /SCT/QP_C21 as the field is an extension (/SCT/QP_TELEM-/MXP/QP_DTELNAME):

Limitations

Whilst it is technically possible to override Element definitions like the conversion method in QPPD custimzing /SCT/QP_C20, it is highly discouraged. Consider creating new elements if it is technically different.
Currently we only support Data Element Generation for QPPD elements and not element assignments to element groups. Thus, overriden conversion methods have no effect.

Usage

1. Open transaction /MXP/QP_GDE or the App directly from the Fiori Launchpad On the first screen you will find an overview of all QPPD Elements and can see to which one already a Data Element is linked. You can also see information about last generation, if any.

2. Go to the details of one Element
   
   You will find information about:

   • The assigned Data Element, if yet one
   • Regeneration needed -> anything changed in the Element Customizing which results in different Data Element/Domain Attributes? (e.g., Conversion Method changed, Element added)
   • Admin Data for the Data Element Generation
   • If there are any "Errors" An Error itself identifies that something needs to be done with the Element before a Generation can take place. Every Error needs to be resolved before a Regeneration can be started. Possible Errors are:
     • Names too long => Data Element Name needs to be adapted to fulfill technical restrictions
     • Element without Conversion Method
   info

   You can find the same information in Result List on the first page.

3. Start the generation, either by:

   1. Single Generation, if we expect any Error or want to distinguish Go to the details page and click on „Edit“ -> a new "Draft" will be opened. You will work on this Draft, complete it, and once you Save it the (Re) Generation will be done. As stated above, every Error needs to be resolved first if there is one.
      
      As we will generate Artifacts and link to Customizing Tables, you are forced to specify Information in section Configuration like:
      1. Elements Section
         • DDIC Prefix Every new Data Element gets prefixed, the following pattern applies <<ddic_prefix>>_<<element_name>>
         • Package Every new Data Element needs to be assigned to a Development Package in the system. Normally starting with Z or Y.
      2. Transports Section
         • Workbench Request As we generate Artifacts which needs to be transported, this is simply for specifying a Transport Request the changes will be recorded.
         • Customizing Request
           to save the link between QPPD Specification type and Root CDS View.
   2. Multi Generation Simply select one to many Elements from the Overview List and click on "(Re) generate:
      
      The same Configuration for Generation has to be done as before. Valid for all selected lines.
      
      info

      Please note that for every Data Element which will have an Error like "No Conversion Method assigned" the Generation cannot take place. An Error message will be shown. It has to be processed in Single Generation mode (see above).

4. The Generation results will be shown in a Message Popup. Open SAPGUI/Eclipse ADT for any details of the Data Element. The link to you newly generated Data Elements gets persisted in QPPD customizing table and will be transported using the Transport Requests stated before.

tip

For troubleshooting purposes you will find a Button "Unlink", which essentially unlinks the Data Element from the Element in Customizing /SCT/QP_C21. Please make sure the Data Element is not used in any other Objects, as the Deletion cannot succeed then.