/IWBEP/IF_MGW_APPL_SRV_RUNTIME~GET_EXPANDED_ENTITY not returning entities

[Former Member]

Hi all,

I have several Problem with GET_EXPANDED_ENTITY :

I created a local structure corresponding to my expanded path

* Nested result type
    data: begin of ls_cfg_characteristics.
            include type /sie/cl_ad_iset_con_02_mpc=>ts_configuration.
    data: tocharacteristics type standard table of /sie/cl_ad_iset_con_02_mpc=>ts_characteristic with default key,
          end of ls_cfg_characteristics.

then I collect the data and perform:

    copy_data_to_ref(
        exporting
        is_data = ls_cfg_characteristics
        changing
        cr_data = er_entity ).

er_entity containts the correct data!

Then I add the path to the expandend clauses

      ls_expanded_clause = 'ToCharacteristics/ToValues'.
      append ls_expanded_clause to et_expanded_clauses.

This are the problems
1. The data for the expanded values is not transferred to the response, its just empty

2. I have to use the obsolete table "et_expanded_clause" instead of et_expanded_tech_clause because otherwise the corresponding get_entityset of the entity is been called additionally no matter what I put in the table (lower and uppercase).

I hope anybody can help me.

Thanks in advance.

Br Sebastian

[AshwinDutt]

Hello Sebastian,

Please check the below points :

1. Navigation Property defined in your GW model should be same as the name used to define the table while declaring the deep structure.

2. Please check the cardinality defined in the GW model between the entities.

3. Make sure Navigation Property is inserted into expand_clause in the Upper Case only.

Regards,

Ashwin

[Former Member]

Hi Ashwin,

thank you for your reply.

I checked everything (again):

1. The navigation property is named the same

2. Cardinality is  1..M

3. I tried to put the navigation in upper case in to expanded_tech_clause but it just ignores it:

append 'TOCHARACTERISTICS' to et_expanded_tech_clauses.

If I do this, the corresponding CHARACTERISTIC_GET_ENTITYSET is called afterwards!

4. I forgot to mention another problem which is definitely related to this:
When I try to determine the expand path with:

io_expand->compare_to_tech_names( 'TOCHARACTERISTICS' ).

I always get en 'N' as a result., but with

lv_compare_exp_cfg_chars = io_expand->compare_to( 'ToCharacteristics' ).

it works (returns 'E').

It seems as if there is a general problem with the handling of the "tech_clauses" table.