XCO framework expects C1-released database table

[Sandra_Rossi]

Hi SAP-Community,

I am currently very desperate, and I count with your help.

In the ABAP Cloud context I am trying to get the information dynamically, if a field of a database table is a key field.

The relevant RTTI/RTTS objects are forbidden in the ABAP Cloud scope, so now I'm looking at the XCO framework.

Specifically, I try to do something like this (this is copied from the SAP documentation):

" Content handle for the field KEY_FIELD of database table ZMY_DBT.
DATA(lo_field_content) = xco_cp_abap_dictionary=>database_table( 'ZMY_DBT'
  )->field( 'KEY_FIELD'
  )->content( ).
" Get the complete content (i.e. all the available attributes of the field)
" as a structure of all attributes.
DATA(ls_field_content) = lo_field_content->get( ).
DATA(lv_key_indicator) = lo_field_content->get_key_indicator( ).

The problem is that when I'm trying to get the content (line 7), I get a CX_XCO_NEWS_EXCEPTION "Database table ZMY_DBT does not exist.

After some debugging, I found out, that the framework expects that ZMY_DBT is C1-released. But I cannot release database tables with C1.

This seems highly contradictory.

Did I find a bug or am I missing something?

What are alternative solutions to dynamically get the key indicator of a database table field (without creating a CDS View)? 

Thank you very much in advance!

[Sandra_Rossi]

To clarify "I found out, that the framework expects that ZMY_DBT is C1-released", here's the place where the C1 check is done (check done in the on-premise system 7.58 SP 1 which has the same issue), SELECT returns no line because the table is not listed in the CDS view ARS_APIS_RELEASED_FOR_SC1_SCP (table ARS_W_API_STATE):

SELECT:

• DATA(rt_object_keys) = VALUE sxco_t_ar_object_key( ).
• SELECT DISTINCT (lv_list) FROM (lv_data_source) WHERE (lv_condition) INTO CORRESPONDING FIELDS OF TABLE @RT_object_keys.

Variables:

• DATA(LV_DATA_SOURCE) = `TADIR INNER JOIN ARS_APIS_RELEASED_FOR_C1_SCP ON ARS_APIS_RELEASED_FOR_C1_SCP~OBJECT_TYPE = TADIR~OBJECT AND ARS_APIS_RELEASED_FOR_C1_SCP~OBJECT_KEY = TADIR~OBJ_NAME`
• DATA(LV_LIST) = `TADIR~OBJECT AS TYPE, TADIR~OBJ_NAME AS NAME`
• DATA(LV_CONDITION) = `( ( ( PGMID EQ 'R3TR' ) AND ( DELFLAG EQ '' ) ) AND ( TADIR~OBJECT EQ 'TABL' ) ) AND ( TADIR~OBJ_NAME EQ 'table name' )`.

ABAP Stack:

• CL_XCO_AR_SELECTION_DATABASE    execute_select [method]             
• CL_XCO_AR_SELECTION_ABSTRACT    if_xco_ar_selection~execute [method]    
• CL_XCO_AR_SELECTION_UNION    if_xco_ar_selection~execute [method]          
• CL_XCO_AR_OBJECTS_SELECTED    if_xco_ar_objects~get_keys [method]           
• CL_XCO_CP_AR_OBJECT    is_hidden [method]           
• CL_XCO_CP_AR_OBJECT    if_xco_ar_object~exists [method]  
• CL_XCO_TAB_RA_LOCAL    if_xco_ad_read_access~exists [method]      
• CL_XCO_TAB_RA_LOCAL    if_xco_tab_read_access~ensure_existence [method]              
• CL_XCO_TAB_RA_LOCAL    if_xco_tab_ra_field~ensure_existence [method]       
• CL_XCO_DBT_FIELD_CONTENT    if_xco_dbt_field_content~get [method]           

Sandra

[Sandra_Rossi]

To clarify "The relevant RTTI/RTTS objects are forbidden in the ABAP Cloud scope": only few RTTS methods are not released for ABAP Cloud, specifically those methods with names containing _DDIC_. RTTS itself is relased for ABAP Cloud.

[Saftladen · Accepted solution]

Hi all,

I consulted SAP Support regarding this issue and wanted to share the outcome in case others run into the same problem.

The key factor was the software component, which in our case was not configured for ABAP Cloud.

If a database table belongs to a package that is assigned to an ABAP Cloud software component, the corresponding XCO APIs can be used for that table without requiring a C1 release contract.

There is another important aspect: if your system contains at least one ABAP Cloud software component, it is also possible to assign a C1 release contract to database tables outside that component. These tables can then also be accessed using the corresponding XCO APIs.

This was the main source of confusion in my case. We had two systems with seemingly identical circumstances, but one contained an ABAP Cloud software component while the other did not. As a result, assigning a C1 contract to a database table was possible in one system but not in the other.

I personally found this behavior quite confusing, especially since other object types can be assigned a C1 contract even when no ABAP Cloud software component exists in the system.

SAP Support confirmed that the documentation will be updated to make the prerequisites for using the XCO APIs clearer.

I hope this helps anyone running into the same issue!

[Sandra_Rossi · Accepted solution]

Nice to know, thanks for the feedback!