SAP Community - NW ABAP Gateway (OData)

Malformed syntax error in ODATA for $batch for GET operation

2025-11-13T11:32:07.701000+01:00

I am trying to test $batch for GET request in ABAP Gateway tcode, but I am getting error Malformed syntax. However when i execute the get entity seperately it works.

I have attached the snapshots for the same.

Body

--batch
Content-Type: application/http
Content-Transfer-Encoding: binary
Accept: application/json

GET SalesOrderHeaderSet('5100000030') HTTP/1.1

--batch--

Also, if I understand correctly since I am going to use only GET requests inside the $batch so there is no need to redefine or implement the CHANGESET method.

OData Delta extract failing with error RSODP_ODATA042.

2025-11-17T04:49:41.139000+01:00

Dear Sap Community

We are facing an issue with one custom Delta Extract service where it works for Full extract but after a few delta extracts, it starts failing with error RSODP_ODATA042.

Full Error message:

Failure happened on 'Source' side. ErrorCode=ODataRequestNotSucceeded,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Requesting response from path DeltaLinksOfFactsOfZEWM_PROD_NEW('D20251113231117_000041000')//ChangesAfter and query $filter=&sap-client=400 failed with status code BadRequest and message <?xml version="1.0" encoding="utf-8"?><error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><code>RSODP_ODATA/042</… xml:lang="en">S:RSODP_ODATA:042</message><innererror><application><component_id/><service_namespace>/SAP/</service_namespace><service_id>ZEWM_PROD_MASTER_ODP_NEW_SRV</service_id><service_version>0001</service_version></application><transactionid>D8C8D15E33990390E006919C91406949</transactionid><timestamp>20251116224624.6897370</timestamp><Error_Resolution><SAP_Transaction>For backend administrators: run transaction /IWFND/ERROR_LOG on SAP Gateway hub system and search for entries with the timestamp above for more details</SAP_Transaction><SAP_Note>See SAP Note 1797736 for error analysis

We have tried to create new CDS/Service as well and face same issue again. Also, the message RSODP_ODATA042 does not exists in our EWM system yet where this service call is failing. If we do a Full extract again which resets the Delta counter, it again works for a few times for delta extract before again failing with same error.

OData Service: “No system alias found for service” after transport to QA – why is “LOCAL” missing?

2025-11-17T08:27:44.907000+01:00

Hi everyone,

I’ve created an OData service that reads data from a custom table and provides PDF downloads. Everything is fully implemented and working in our development system (DEV). The service also runs fine in the Gateway Client (/IWFND/GW_CLIENT).

After transporting it to QA, I’m getting the following error in the Gateway Client:

500 – No system alias found for service

When I checked the service in QA via /IWFND/MAINT_SERVICE, I noticed that there is no system alias “LOCAL” defined at all.

This confused me because in DEV the service is assigned to the alias “LOCAL”, but in QA it doesn’t exist.

What also makes it strange:

Other OData services in QA and PROD are working fine—even though they also don’t have any system alias assigned. So the system somehow works without explicitly having “LOCAL” configured.

My questions:

Why does “LOCAL” exist in DEV but not in QA/PROD?

Shouldn’t this be consistent?

How is it possible that other OData services work without any system alias at all?

Is the system using some kind of implicit local alias?

What is the correct way to fix this issue for my new OData service?

Do I need to create the alias manually in QA, or is there a better approach?

How can I make sure that existing productive OData services won’t be affected by this configuration?

SAP ODdata This page contains the following errors: error on line 1 at column 5105996:

2025-11-19T17:18:15.366000+01:00

Hello Expert,

Getting OData URI PROJSet? $skip=0&$top=5000 issue. When I use $top=1000, it works fine; above $top=1000, I get this error.

Please help.

SU01 User group mandatory field

2025-11-27T11:19:32.300000+01:00

Are there any SAP Note to inform how to configure in SU01 tcode that the User group mandatory is a mandatory field to avoid creation of user with blank groups?

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

Why sapdevcenter doesn't work?

2025-12-01T18:40:41.458000+01:00

More than a month and it does not work or I cant Change my password... Or New registration... If anyone have a, link to reset password I appreciate.

Updates on ODATA V2 Deprecation

2025-12-04T07:26:37.827000+01:00

Dear Community,

I have confusion on latest rumors' on stopping support for ODATA v2 from SAP. I am not really finding any SAP note on that to get clear idea. Can someone help me to get it and also do you have idea on below points?

If ODATA v2 support is going to stop then what will happen to old service/integrations done with non-sap systems after system upgrade?
Are ODATA services created through SEGW comes under ODATA v2?
If creating ODATA services is not recommended in SEGW then how same can be done in v4 version(may be following RAP Model)?(Any blog or documentation on creating READ, UPDATE, CREATE Operations in ODATA v4 same like how we were doing in SEGW?)

Thanks for your time in reading my queries, please drop ur comments.

Regards,

Omkar

CX_SADL_DUMP_APPL_MODEL_ERROR while sending GET Request to ODATA v4 with /IWBEP/IF_V4_DP_BASIC

2025-12-05T10:20:33.007000+01:00

Dear Community,

I am trying to create ODATA V4 as mentioned in SAP Note 2485370, So I created a custom entity in Eclipse and also a Class with below method implemented from interface /IWBEP/IF_V4_DP_BASIC.

@EndUserText.label: 'ZSAMPLE_SERVICE'
@ObjectModel.query.implementedBy: 'ABAP:ZCL_SAMPLE_SERVICE'
define custom entity ZSAMPLE_SERVICE
{
   key component_material : abap.char(40);
       fg_material  : abap.char(40);
       fg_material_descr : abap.char(40);
  
}

And Class as below

CLASS ZCL_SAMPLE_SERVICE DEFINITION
  PUBLIC
  inheriting from /iwbep/cx_gateway
  FINAL
  CREATE PUBLIC .

  PUBLIC SECTION.

    INTERFACES /IWBEP/IF_V4_DP_BASIC.
  PROTECTED SECTION.
  PRIVATE SECTION.
ENDCLASS.



CLASS ZCL_SAMPLE_SERVICE IMPLEMENTATION.
  METHOD /IWBEP/IF_V4_DP_BASIC~CREATE_ENTITY.

  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~CREATE_REFERENCE.

  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~DELETE_ENTITY.

  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~EXECUTE_ACTION.

  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~EXECUTE_FUNCTION.

  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~READ_ENTITY.

    DATA: TS_DATA TYPE zsample_service.
    TS_DATA-COMPONENT_MATERIAL = '12333333'.
    TS_DATA-FG_MATERIAL = '321'.
    TS_DATA-FG_MATERIAL_DESCR = 'This is material description'.


    IO_RESPONSE->SET_BUSI_DATA( TS_DATA ).
  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~READ_ENTITY_LIST.
    DATA: TS_DATA TYPE zsample_service,
          TT_DATA TYPE TABLE OF zsample_service.
    TS_DATA-COMPONENT_MATERIAL = '12333333'.
    TS_DATA-FG_MATERIAL = '321'.
    TS_DATA-FG_MATERIAL_DESCR = 'This is material description'.
    APPEND TS_DATA TO TT_DATA.
    IO_RESPONSE->SET_BUSI_DATA( TT_DATA[] ).
  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~READ_REF_TARGET_KEY_DATA.

  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~READ_REF_TARGET_KEY_DATA_LIST.

  ENDMETHOD.

  METHOD /IWBEP/IF_V4_DP_BASIC~UPDATE_ENTITY.

  ENDMETHOD.

ENDCLASS.

After this, I created service definition to explose above cds entity and then service binding.

When I do Get request to my service URL from postman I am getting dump saying as below

Error analysis                                                                                    |
|    The application has indicated exception "CX_SADL_DUMP_APPL_MODEL_ERROR" as the                |
|     reason for the                                                                               |
|    termination:                                                                                  |
|    Processing was aborted because of an application modeling error: See previous                 |
|    in exception chain.                                                                           |
|                                                                                                  |
|    The exception is related to the previous exception                                            |
|     "LCX_RAP_QUERY_PROV_BAD_IMPLMNT" that occurred in                                            |
|    program "CL_SADL_UNMANAGED_QUERY_ENGINECP", in line 6 of include                              |
|     "CL_SADL_UNMANAGED_QUERY_ENGINECM00J". The reason for this exception                         |
|    was:                                                                                          |
|    Error occurred during execution of query provider 'ZCL_SAMPLE_SERVICE'                        |
|                                                                                                  |
|    The exception is related to the previous exception                                            |
|     "CX_RAP_QUERY_PROV_CONSTRUCTION" that occurred in                                            |
|    program "CL_RAP_QUERY_PROVIDER_FACTORY=CP", in line 6 of include                              |
|     "CL_RAP_QUERY_PROVIDER_FACTORY=CM004". The reason for this exception                         |
|    was:                                                                                          |
|    Error during construction of the Unmanaged Query Provider for entity                          |
|    ZSAMPLE_SERVICE                                                                               |
|                                                                                                  |
|    The exception is related to the previous exception "CX_SY_CREATE_OBJECT_ERROR"                |
|     that occurred in                                                                             |
|    program "CL_RAP_QUERY_PROVIDER_FACTORY=CP", in line 3 of include                              |
|     "CL_RAP_QUERY_PROVIDER_FACTORY=CM004". The reason for this exception                         |
|    was:                                                                                          |
|    Could not create object; reference variable does not match specified class                    |
|    ZCL_SAMPLE_SERVICE.

Can anyone help on this?

I appreciate your time and reply on this query.

Regards,

Omkar

SAP API Delta Load not creating delta token

2025-12-12T10:35:48.421000+01:00

Hi,

We have a requirement to retrieve delta changes from a change log. For this purpose, we created a CDS view with the following delta-related annotations:

@analytics: { dataCategory: #FACT, dataExtraction: { enabled: true, delta: { byElement: { name: 'LastChangeDate', maxDelayInSeconds: 1800 } } } }

We then exposed the CDS view as an OData service using both OData Publish and RAP service binding.
However, when we call the API, the response does not contain any delta link (delta URL).

Could you please advise on how we should proceed?

Dual line chart using macros and odata v4

2025-12-16T00:43:21.839000+01:00

Dear experts,

I am facing some problems to implement a chart in Fiori, using macros, xml annotations and odata v4. It works when I only have one dimension, but fails when the second is included.

The annotation "@Aggregation.default: #SUM" is included in the entity view, and the xml annotation is being used as follow:

<edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx" Version="4.0">
    <edmx:Reference Uri="https://sap.github.io/odata-vocabularies/vocabularies/Analytics.xml">
        <edmx:Include Namespace="com.sap.vocabularies.Analytics.v1" Alias="Analytics"/>
    </edmx:Reference>
    <edmx:Reference Uri="https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Aggregation.V1.xml">
        <edmx:Include Namespace="Org.OData.Aggregation.V1" Alias="Aggregation"/>
    </edmx:Reference>
    <edmx:Reference Uri="https://sap.github.io/odata-vocabularies/vocabularies/Common.xml">
        <edmx:Include Namespace="com.sap.vocabularies.Common.v1" Alias="Common"/>
    </edmx:Reference>
    <edmx:Reference Uri="https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Org.OData.Capabilities.V1.xml">
        <edmx:Include Namespace="Org.OData.Capabilities.V1" Alias="Capabilities"/>
    </edmx:Reference>
    <edmx:Reference Uri="https://sap.github.io/odata-vocabularies/vocabularies/HTML5.xml">
        <edmx:Include Namespace="com.sap.vocabularies.HTML5.v1" Alias="HTML5"/>
    </edmx:Reference>
    <edmx:Reference Uri="https://sap.github.io/odata-vocabularies/vocabularies/UI.xml">
        <edmx:Include Namespace="com.sap.vocabularies.UI.v1" Alias="UI"/>
    </edmx:Reference>
    <edmx:Reference Uri="/sap/opu/odata4/sap/zui_newblick/srvd/sap/zsd_newblick/0001/$metadata">
        <edmx:Include Namespace="com.sap.gateway.srvd.zsd_newblick.v0001" Alias="SAP__self"/>
    </edmx:Reference>
    <edmx:DataServices>
        <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="local">

            <Annotations Target="SAP__self.Container/ZI_BLK_OPEN_RESOLVED">
                <Annotation Term="Aggregation.ApplySupported">
                    <Record Type="Aggregation.ApplySupportedType">
                        <PropertyValue Property="Transformations">
                            <Collection>
                                <String>aggregate</String>
                                <String>groupby</String>
                            </Collection>
                        </PropertyValue>
                        <PropertyValue Property="AggregatableProperties">
                            <Collection>
                                <Record Type="Aggregation.AggregatablePropertyType">
                                    <PropertyValue Property="Property">
                                        <PropertyPath>openTickets</PropertyPath>
                                    </PropertyValue>
                                </Record>
                                <Record Type="Aggregation.AggregatablePropertyType">
                                    <PropertyValue Property="Property">
                                        <PropertyPath>resolvedTickets</PropertyPath>
                                    </PropertyValue>
                                </Record>
                            </Collection>
                        </PropertyValue>
                        <PropertyValue Property="GroupableProperties">
                            <Collection>
                                <PropertyPath>openResolvedDate</PropertyPath>
                            </Collection>
                        </PropertyValue>
                    </Record>
                </Annotation>
            </Annotations>

            <Annotations Target="SAP__self.ZI_BLK_OPEN_RESOLVEDType">
                
                <Annotation Term="UI.Chart" Qualifier="TicketsOpenResolved">
					<Record Type="UI.ChartDefinitionType">
						<PropertyValue Property="Title" String="Open x Resolved" />
						<PropertyValue Property="ChartType" EnumMember="UI.ChartType/Line" />
						<PropertyValue Property="Description" String="Open x Resolved Tickets" />
                        <PropertyValue Property="Dimensions">
							<Collection>
								<PropertyPath>openResolvedDate</PropertyPath>
							</Collection>
						</PropertyValue>
                        <PropertyValue Property="DimensionAttributes">
							<Collection>
								<Record Type="UI.ChartDimensionAttributeType">
									<PropertyValue Property="Dimension" PropertyPath="openResolvedDate" />
									<PropertyValue Property="Role" EnumMember="UI.ChartDimensionRoleType/Category" />
								</Record>
							</Collection>
						</PropertyValue>
                        <PropertyValue Property="Measures">
                            <Collection>
                                <PropertyPath>openTickets</PropertyPath>
                                <PropertyPath>resolvedTickets</PropertyPath>
                            </Collection>
                        </PropertyValue>
                        <PropertyValue Property="DynamicMeasures">
                            <Collection>
                                <AnnotationPath>@Analytics.AggregatedProperty</AnnotationPath>
                                <AnnotationPath>@Analytics.AggregatedProperty#ResolvedSum</AnnotationPath>
                            </Collection>
                        </PropertyValue>
						<PropertyValue Property="MeasureAttributes">
							<Collection>
								<Record Type="UI.ChartMeasureAttributeType">
									<PropertyValue Property="Measure" PropertyPath="openTickets" />
									<PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis1" />
								</Record>
                                <Record Type="UI.ChartMeasureAttributeType">
                                    <PropertyValue Property="Measure" PropertyPath="resolvedTickets" />
                                    <PropertyValue Property="Role" EnumMember="UI.ChartMeasureRoleType/Axis1" />
                                </Record>
							</Collection>
						</PropertyValue>
						
					</Record>
				</Annotation>

                <Annotation Term="Analytics.AggregatedProperty">
                    <Record Type="Analytics.AggregatedPropertyType" >
                        <PropertyValue Property="Name" String="openSum"/>
                        <PropertyValue Property="AggregationMethod" String="sum"/>
                        <PropertyValue Property="AggregatableProperty" PropertyPath="openTickets"/>
                        <Annotation Term="Common.Label" String="Open Tickets"/>
                    </Record>
                </Annotation>
                <Annotation Term="Analytics.AggregatedProperty" Qualifier="ResolvedSum" >
                    <Record Type="Analytics.AggregatedPropertyType">
                        <PropertyValue Property="Name" String="resolvedSum"/>
                        <PropertyValue Property="AggregationMethod" String="sum"/>
                        <PropertyValue Property="AggregatableProperty" PropertyPath="resolvedTickets"/>
                        <Annotation Term="Common.Label" String="Resolved Tickets"/>
                    </Record>
                </Annotation>

            </Annotations>

        </Schema>
    </edmx:DataServices>
</edmx:Edmx>

The chart opens with the message "To start, set the relevant filters and choose "Go" when even there isn't any filter to be applied.

Its associated batch call returns the errors: "Dynamic property 'openSum' not provided by provider application", "Property 'openSum' not found". The attribute in the backend entity is openTickets, and the aggregated property in the xml annotation is "openSum", which doesn't fail with only one dimension, but It does fail with two.

<Annotation Term="Analytics.AggregatedProperty">
                    <Record Type="Analytics.AggregatedPropertyType" >
                        <PropertyValue Property="Name" String="openSum"/>
                        <PropertyValue Property="AggregationMethod" String="sum"/>
                        <PropertyValue Property="AggregatableProperty" PropertyPath="openTickets"/>
                        <Annotation Term="Common.Label" String="Open Tickets"/>
                    </Record>
                </Annotation>
                <Annotation Term="Analytics.AggregatedProperty" Qualifier="ResolvedSum" >
                    <Record Type="Analytics.AggregatedPropertyType">
                        <PropertyValue Property="Name" String="resolvedSum"/>
                        <PropertyValue Property="AggregationMethod" String="sum"/>
                        <PropertyValue Property="AggregatableProperty" PropertyPath="resolvedTickets"/>
                        <Annotation Term="Common.Label" String="Resolved Tickets"/>
                    </Record>
                </Annotation>

What could be wrong in my xml annotation?

SEGW CREATE payload: distinguish property filled, possible or not?

2025-12-17T17:52:08.044000+01:00

I've got a SEGW project. In the CREATE method of the DPC_EXT class, is it possible to know if a property is transmitted in the JSON payload or not?

e.g. "AirlineCompanyName" transmitted:

{
  "AirlineCompanyCode": "LH",
  "AirlineCompanyName": ""
}

versus not transmitted:

{
  "AirlineCompanyCode": "LH"
}

In both cases, the method CREATE_entity_type gets an empty string for "AirlineCompanyName".

The client wants to have one logic if the property "AirlineCompanyName" is transmitted (empty), and another logic if the property is not transmitted.

Thanks.

Sandra

ODATA_CALLING_ERROR: How to configure Resource Path in OData Sender Adapter

2026-01-13T20:08:21.313000+01:00

Hi All,

We are working on an OData to JDBC integration where we are trying to fetch IDoc status information from SAP and update it on the client side.

This is a CDS view with parameters exposed as ODATA which we are trying to consume from ODATA Sender channel.
We have created an HTTP Destination as shown below:

Destination Name: ZCAD_I_IDOC_STATUS
URL:
https://agvdwdci01.corp.mooginc.com/sap/opu/odata/sap/ZCAD_I_IDOC_STATUS_CDS?sap-client=250&sap-language=EN

Resource Path : ZCAD_I_IDOC_STATUS(p_days=7)/Set
OData Sender Adapter and OData structure snapshots are attached for reference.

However, we are encountering the following error in the PO channel:

ODATA_CALLING_ERROR: OData call failed
404 : NOT_FOUND [ZCAD_I_IDOC_STATUS(p_days=7)/Set]

The same destination works correctly when tested directly in the browser as well as via Postman.

Could someone please advise what the correct Resource Path should be in the OData channel configuration to make this work successfully?

Any guidance or suggestions would be greatly appreciated.

Thank you in advance.

Custom fields added to extended SEGW OData entity not available in metadata

2026-01-14T21:44:53.666000+01:00

Hello Experts,

In Fiori App ID: F0843 (Post Goods Receipt for Purchasing Document), we are trying to add some custom fields in entity GR4PO_DL_Item of OData service MMIM_GR4PO_DL_SRV by redefinition and importing properties that are already available as an .include in the line item type MMIM_GR4PO_DL_ITEM.

After this we redefined "Define" method of MPC_EXT class with code:

  METHOD define.

  super->define( ).

  DATA(lo_entity_type) = model->get_entity_type( iv_entity_name = 'GR4PO_DL_Item' ).

  " Expand the specific include structure to expose its fields
  lo_entity_type->add_auto_expand_include(
    EXPORTING
      iv_include_name     = 'MMIM_GR4PO_DL_ITEM'
      iv_bind_conversions = abap_true
  ).
ENDMETHOD.

We followed the same approach as shown in this learning journey:

https://learning.sap.com/courses/building-odata-services-with-sap-gateway/redefining-an-sap-gateway-service

We already generated the Runtime objects and there seems to be no error as metadata loading properly. However, in the metadata the custom fields are not available and we are not sure what could be missing. The metadata does show the all the inlcudes but does not show the fields added to include, even though they are available in extended entity type.

Did someone face similar situation and can help in finding the solution?

Use BTP Malware Service with VSCAN (VSI) - Detect hidden code in metadata of image file

2026-01-26T11:01:11.928000+01:00

Hi,

I have a requirement where we need to scan files uploaded via a Fiori application for malware (in our case attachments for a leave request). After some research I came across this amazing github project ( https://github.com/gregorwolf/sap-malware-scanning-vsi ) that explains how you can use the BTP malware service via the VSI BAdI to do your virus/malware scanning.

We initiated the BTP Malware instance, created the SM59 config, created all the classes and interfaces as per the github project, implemented the BADI and created the basic VSI configuration.

Now that all seems to be working correctly. When I use VSCANTEST with the standard Eicar test virus, it correctly detects the virus.

However when I try something more complex like hiding executable PHP code within the metadata of an image file, it does not detect this as malware :(. I tried searching through all available documentation, and it seems as if the VSI profile configuration options where you specify MIME types for active content is only if you configure a malware service via VSI and not when you use the BADI?

Has anyone tried this before where you use the VSI BADI to call a malware scanning service (Like the BTP one) and scan for things like PHP code in metadata? How I do that?

Kind Regards

Deon

How to activate OData API on SAP ECC R3

2026-01-27T11:57:24.503000+01:00

Hello SAP Specialists

We want to use API_ATTACHMENT_SRV on SAP ECC, but so far on our SAP ECC system no OData API has been activated or used so far. primary mode of interface so far are IDocs, files, BAPIs for this system.

Since OData API is to be activated which has never been done so far on this system, could you please help me with the pre-requisites?

SAP NetWeaver Gateway is available on the system, software component SAP_GWFND too is available on the system on the list of installed software.

Regards,

12 characters limit on UserID in SU01

2026-02-03T13:41:51.062000+01:00

We are not able increase the 12 character limit on UserID created in SU01. it is not accepting UserID longer than 12 characters.

PATCH operation failed on API_SALES_ORDER_SRV

2026-02-06T03:22:37.023000+01:00

Hello Team,

I am going to update two fields one from header i.e "PurchaseOrderByCustomer" and another from Item "RequestedQuantity".
These two fields available in A_SalesOrderItem EntitySet. But when I am doing PATCH operation only "RequestedQuantity" is updating not "PurchaseOrderByCustomer".

I am using url
/sap/opu/odata/sap/API_SALES_ORDER_SRV/A_SalesOrderItem(SalesOrder='7000000223',SalesOrderItem='0010')

{

"PurchaseOrderByCustomer": "Alex",

"RequestedQuantity": "20"

}

Is it not possible to update header field from item ? Is $batch operation work on this API ?

Can you please help me on this?

Dynamic programming in RAP for excel upload

2026-02-12T15:57:39.780000+01:00

Hello All,

We have a requirement to have a single interface in RAP, which can upload excel data to around 30 tables that we select via drop-down or screen.

In the report program, we have an option upload excel to tables with dynamic programming with minimum efforts. We were achieving this by maintaining the tables in tvarvc, using the system classes and use Excel upload to populate the tables, and this would rarely require any enhancement.

Is there any way that we can do the same in RAP framework, as creating i view, c view. Meta data extension and behaviour definition for 30 tables is a tedious task.

Regards

Naga

SAP NetWeaver Gateway OAuth 2.0: avoid client secret / ABAP password for token call

2026-02-16T18:28:40.441000+01:00

Hi Team,

We’ve configured an OAuth 2.0 setup in our environment, but when calling the token endpoint it appears to require the client secret (and/or it’s being treated like an ABAP user password). We suspect this may be related to our SAP NetWeaver Gateway 7.50 SP30 level.

Goal: Identify the best-supported approach to obtain an access token without sending a client secret or ABAP user password in the token request.

Question:
Would using Client Credentials grant with client authentication set to “SSL client certificate” in transaction SOAUTH2 be the recommended approach? If not, what alternative approach would you recommend for this requirement?

If “SSL client certificate” is the right path, could someone share step-by-step configuration guidance, including:

Required settings in SOAUTH2 (grant type, client authentication, etc.)
Certificate prerequisites (where to import/maintain it, trust setup)
Any related ICF/service or Gateway configuration
How the token request should look once configured (high level)

Happy to provide additional details if needed .

Thanks in advance.

Fiori "My Inbox" Error - Intermittent issue,

2026-02-17T03:28:43.975000+01:00

Hello,

I encounter an issue in fiori " My Inbox". The error is intermittent (sometimes there's an error but sometimes it is working properly)

sample uri with error(sorry but I cannot post the whole URI): /sap/opu/odata/IWPGW/TASKPROCESSING;v=2;mo/TaskCollection/$count/?$filter=Status%20eq%20%27READY%........

Method: GET

Status code: 500 after successful login, 400 after clicking the My Inbox with error

If the tile has error , this error message will appear

I think there's no issue in the configuration because sometimes it is working

The RFC Destination is NONE, and connection Type is "I" (Internal Connection)

the ZTASKPROCESSING we maintained in /IWFND/MAINT_SERVICE and the taskprocessing maintained in SICF is activated

no dump in ST22

no duplicate keys/task

but there is an error in /IWFND/ERROR_LOG and IWBEP/ERROR_LOG

Frontend - An exception was raised

Backend - Soapfaultcode: Authentication failed (not sure yet if this is the root cause)

FYI: we are using BPM for the workflow, the standard software version we used in /IWFND/ROUTING is /IWPGW/BPM, current system is ECC. The tasks in the "My Inbox" is coming from custom table

what could be the other possible cause of the intermittent error, any idea or anyone has experienced this kind of issue? or can you share your techniques on how to find the root cause of error