2628756 - SAP Gateway hub metadata cache is not used for all OData services causing slow performance (MedCacheHub=)

• Users seeing slow performance when using SAP Gateway OData services, because metadata cache is not used for all OData services.
  AND
• The sap-processing-info HTTP response header parameter contains "MedCacheHub=".
  (MedCacheHub=Table or MedCacheHub=SHM would indicate that the metadata cache is used either in a transparent table or in the shared memory.)

• SAP Gateway (SAP_GWFND software component 7.40, 7.50 and 7.51) on the hub and back-end systems:
• SAPK-74014INSAPGWFND - SAPK-74019INSAPGWFND
• SAPK-75004INSAPGWFND - SAPK-75010INSAPGWFND
• SAPK-75101INSAPGWFND - SAPK-75104INSAPGWFND
• SAP NetWeaver Application Server 7.51 for SAP S/4HANA 1610 (SAP_BASIS 7.51):
• SAPK-75103INSAPBASIS and lower

metadata, model cache, MedCacheHub, iwfnd, iwbep, sap-processing-infom, gwtotal, gwfw, /IWBEP/CL_MGW_REMOTE_HANDLER, GET_META_DATA, /iwfnd/traces, /iwbep/traces, performance trace, shared memory cache, shm, reference models, additional entities, properties, CL_DD_DDL_ANNOTATION_SERVICE, GET_ANNOS_MASS, ABAP CDS View, SADL, annotation cache, FAA_ASSET_CREATE_SRV, FAA_ASSET_MANAGE_SRV, SD_F1708_CRT_SRV, SD_F1814_SO_FS_SRV, FAC_GLV_GL_ACCOUNT_LINE_ITEMS_SRV, FAC_GL_ACCOUNT_LINE_ITEMS_SRV, FAC_MANAGE_GLACCOUNT_SRV, GET_LAST_MODIFIED_RDS_4, Annotation API, get_annos_mass , KBA , 2546487 , enqueue , model caching , v2 , OPU-GW-COR , Framework , BC-DWB-DIC-AC , ABAP Dictionary Activation and Conversion , Problem