Skip to Content

What are meshes really good for?

Hello experts,

I can't find a good reason to use the ABAP meshes, because they do not really clarify the code compared to classic programming.

I have the feeling that they can be useful in the near future (like maybe code generation from CDS views), but right now I don't see. One of the big advantage I see is the code completion while typing a mesh path, it proposes the possible mesh nodes i.e. the possible relationships to other internal tables.

Do you have real use cases where meshes are really useful?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Nov 22, 2016 at 10:42 AM

    Here's the best answer (although Kilian's is a good one). I simply forgot to check @Horst.Keller 's blog introducing the meshes (

    The full power of meshes will become more clear in the monent 
    when associations will be supported by Open SQL for database
    views (CDS views, see below) in the future.
    Add comment
    10|10000 characters needed characters exceeded

  • Nov 18, 2016 at 07:31 PM

    The absolute "killer" feature of the mesh is the * operator. You can load hierarchical data into an itab and make a mesh out of it by using the hierarchy as association. With the * operator you can get the childs and grand-childs or parents very easily.

    If the ORG management would use Meshes, they could get rid of one half of their coding ;-).

    Just kidding, but I used meshes in a similar situation where I often needed the transitive hull of a hierarchy and it saved a few dozen lines of coding (noting that these few dozen lines of coding are pushed from ABAP into fast kernel C++).

    But we need better support in Open SQL and DATA declaration for Meshes. Something like:

    DATA foo TYPE MESH OF cds_view1 cds_view2 cds_view3.

    would really be nice. How should the SELECT statement look like to fill this mesh?

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 18, 2016 at 07:52 PM

    I have a requirement coming up where the user wants to switch views on a tree structure based on material / batch or Storage Unit or Warehouse bin which are all inter-related. One option is to make 3 different programs and link them together (either as 3 different reports or essentially 3 programs in 1 report).

    I am going to explore mesh-paths as a way to relate all this data and view it in different ways. I haven't had time to start exploring this yet. I will report back here once I do. By the general nature of your question, I don't think you would mind if I take a month or two on it :)

    Add comment
    10|10000 characters needed characters exceeded