SAP Community - NW ABAP Gateway (OData)

Avoiding repetitive Post call in SAP Odata

2024-03-28T20:16:57.523000+01:00

Hi everyone,

I'm encountering issues with duplicate data being posted through SAP OData. Is there a way to identify and prevent these repetitive submissions?

Regards,

Nikhil

SAP Gateway ignored the filter pass by OData receiver adapter in Integration Sute

2024-03-30T12:21:40.136000+01:00

Dear All,

I am trying to implement an OData API in Integration Suite and having issues passing the filter to the backend S/4HANA system. This is an end-to-end OData service (Receiver and sender). The requirement is to publish an OData endpoint to expose an OData service built in S/4 HANA using Integration Suite.

Details are :

S/4 HANA development environment has two clients 400 and 411. Cloud connector has access only to client 411. OData service was developed consuming a CDS view using Eclipse in client 400 and copied to 411.

Processing mode = Routing Based and added system alias

2. I tested the OData service with the following URL internally and it is giving the expected result.

https://<hostname>/sap/opu/odata/sap/ZAPI_O2_SALESORDERETA/SalesOrderETA/?$filter=(SoldToParty%20eq%20%2747474%27%20and%20OpenReqdDelivQtyInBaseUnit%20gt%200)

3. iFlow has been configured with the following information.

a.Runtime configuration - Allowed Header(s) : CamelHttpQuery

b. OData sender – System generated values.

c. Odata sender -Script

I tried with following two options.

if(uriInfo.getFilter() != null){

def filter = uriInfo.getFilter();

if(odataURI.size()!=0)

odataURI.append(urlDelimiter);

odataURI.append("\$filter=").append(filter);

log.logErrors(LogMessage.TechnicalError, "Filter value:"+filterExpression);

}

message.setHeader("odataEntity",entityName);

message.setHeader("odataURI",odataURI.toString());

When I do this, trace has following value for the filter.

odataURI : $filter=org.apache.olingo.odata2.core.uri.expression.FilterExpressionImpl@7d1f5f10

Then I tried with this

if(uriInfo.getFilter() != null){

def filterExpression = uriInfo.getFilter().getExpressionString()

odataURI.append(urlDelimiter);

odataURI.append("\$filter=").append(filter);

odataURI.append("\$filter=").append(filterExpression);

}

message.setHeader("odataEntity",entityName);

message.setHeader("odataURI",odataURI.toString());

Trace had the following value for the filter.

odataURI : $filter=(SoldToParty eq '47474' and OpenReqdDelivQtyInBaseUnit gt 0)

d. OData receiver configuration looks like this.

Connection Address http://<hostname>:443/sap/opu/odata/sap/ZAPI_O2_SALESORDERETA

Proxy On-Premise

Authentication Basic

Credential Name – Populated with valid credential ID

Processing

Operation details : Query(GET)

Resource Path : SalesETA

HEADER DETAILS – Request Header = *

METADATA DETAILS – Customer query parameter = sap-client=411

The external endpoint is

https://<hostname>.hana.ondemand.com/gw/odata/SAP/S4_SALESORDERETA;v=1/SalesOrderETATypeSet/?$filter=(SoldToParty eq '47474' and OpenReqdDelivQtyInBaseUnit gt 0)

Message log sys com.sap.gateway.core.ip.component.odata.exception.OsciException: Unauthorized : 401 : HTTP/1.1

It would be great if someone could help me.

Kind Regards

Shantha

Odata Query not working when using '=' symbol

2024-04-02T04:36:19.146000+02:00

Hi,

I have an Odata Query which is working (getting data) fine when i use 'eq' as below:

/sap/opu/odata/SAP/Z*****_01/BPInputsSet?$format=json&$filter= Account eq '800000012341' and Prodtyp eq 'EWR' &$expand=NavtoData1,NavtoData2&$format=json

But when i replace 'EQ' with '=' its throwing error like " 400 : Invalid token detected at position.".etc

How to correct this error?

Navigating OData Service Customization in ABAP Cloud

2024-04-02T18:27:39.220000+02:00

Hello everyone!

I'm engaged in a project on SAP BTP ABAP environment and encountering challenges with OData services. Traditionally, in the on-premises ABAP environment, we could utilize the SEGW transaction to create and adjust OData services, including renaming entities to meet our naming standards or needs. However, SEGW is not accessible in the SAP BTP ABAP environment, where RAP has become the preferred technology. I'm exploring alternative methods to achieve similar outcomes.

One of our goals is to rename navigation properties (associations) in OData services generated from referenced CDS views. I aim to align the names of navigation properties in OData services with our project's naming guidelines, preferring "Entity" over the usual "toEntity".

Additionally, I've encountered issues with reserved words, such as CDS fields, in the SAP BTP ABAP environment, which were not problematic in on-premises settings (link).

The reason I wish to keep the services identical (at a metadata level) in SAP BTP ABAP environment and on-premises is to connect the new cloud OData services to existing development resources, such as Fiori applications and third-party integrations.

Creative solutions or indirect methods may be necessary due to these limitations. Any advice, tips, or documentation references would be highly valued.

Looking forward to your insights and suggestions.

Thank you!

Rafael

Pass variable value dynamically in POST Request body - Postman

2024-04-04T03:51:00.671000+02:00

Good afternoon all.

Running my Odata services from Postman , just for the ease of doing testing.

I have to post some master data with external number range and every time I am changing variable value in the POST request body to the next number.?(some random number or last number+1 from table).

Is there way to automate this in Postman? I created variable and used it in body. not sure if it works. it doesn't ask for variable when I run. I want to make it easy for someone who wants to test it. I can pass on some variables from 'GET' but this key number has to be from user input.

like, when I click run, it just asks for variable value, or should be able to add this variable just before running from collection.(without going into individual service)

is there an option for this? i couldn't find much help from existing threads.

Retrieve metadata failed because the OData server returned HTTP code, 401

2024-04-04T13:08:28.401000+02:00

Dear Experts,

Could you please help/support on the below error. Recently we have been facing an issue when accessing the SAP Hybrid App in IPAD, After the successful authentication when the call goes to gateway system we are getting this error. More details on the error

Error Retrieve metadata failed because the OData server returned HTTP code, 401 with message "Logon Error Message"

The connections is via SAP BTP and we are seeing the same error logs in cloud platform. But I am not able to see any logs in gateways system.

Kindly let me know or help me to fix this issue. This is very urgent

Workflow user decision step with link of FIORI screen

2024-04-06T19:55:50.310000+02:00

Dear All,

I am having requirement of 'Link of Fiori screen' in workflow User decision step which is available in MYINBOX. On clicking the Link in user decision step FIORI screen should appear.

Can anybody kindly guide what work is required from ODATA and FIORI side is needed.

My workflow template triggering from Odata.

Regards.

MYINBOX is connected to HUB system and workflow exists in ECC system

2024-04-06T20:12:20.153000+02:00

Dear All,

MyINBOX is connected to HUB system and workflow exists in ECC system also the tasks are in ECC Inbox. Kindly help how can I have the ECC inbox tasks in NetWeaver Gateway inbox so that NW gateway MyINbox will have the ECC WF tasks.

Regards.

Business Partner Creation using ODATA V2.0

2024-04-08T07:10:52.987000+02:00

Objective:Business Partner Creation using ODATA V2.0

Step 1. To Create OData go to T-Code SEGW.

Step 2. Create a New Project(Ex--> Z_CUSTOMER)

Step 3. Then create a Entity Type(Ex--> Customer)

Step 4 . In properties, insert field by referring below attached screenshot.

Step 5. Source Code

1. Get EntitySet Method

method CUSTOMERSET_GET_ENTITYSET.
data lwa_entity LIKE LINE OF et_entityset.
SELECT * FROM kna1 INTO TABLE @DATA(lt_cust).
LOOP AT lt_cust INTO data(lwa_cust).
SELECT SINGLE city1, country, region
INTO (@lwa_entity-city, @lwa_entity-country, @lwa_entity-region)
FROM adrc
WHERE addrnumber = @lwa_cust-adrnr.
lwa_entity-name1 = lwa_cust-name1.
lwa_entity-businesspartner = lwa_cust-kunnr.
lwa_entity-businesscategory = '2'.
lwa_entity-partnergroup = 'Customer'.
append lwa_entity to et_entityset.
ENDLOOP.
endmethod.

2. Get Entity Method

METHOD customerset_get_entity.

DATA : bp TYPE kunnr.
DATA : address TYPE bapicustomer_04.
DATA : gen_detail TYPE bapicustomer_kna1.
DATA : comp_Detail TYPE bapicustomer_05.
DATA : return TYPE bapiret1.

DATA(lwa_key) = it_key_tab[ name = 'CustomerCode' ].
IF lwa_key-value IS NOT INITIAL.
bp = lwa_key-value.
CALL FUNCTION 'BAPI_CUSTOMER_GETDETAIL2'
EXPORTING
customerno = bp
* COMPANYCODE =
IMPORTING
customeraddress = address
customergeneraldetail = gen_detail
customercompanydetail = comp_detail
return = return
* TABLES
* CUSTOMERBANKDETAIL =
* CUSTOMERIBANDETAIL =
* CUSTOMERSEPADETAIL =
.
IF sy-subrc = 0 and return-type <> 'E'.
er_entity-city = address-city.
er_entity-country = address-country.
er_entity-region = address-region.
er_entity-name1 = address-name.
er_entity-businesspartner = bp.
er_entity-businesscategory = '2'.
er_entity-partnergroup = 'Customer'.
else.
er_entity-businesspartner = 'Not Found.'.
er_entity-return = 'No customer found.'.
ENDIF.
ELSE.
RAISE EXCEPTION TYPE /iwbep/cx_mgw_not_impl_exc
EXPORTING
textid = /iwbep/cx_mgw_busi_exception=>business_error
method = 'Please pass Customer Key to get the details.'.
ENDIF.

3. Create Entity Method

METHOD customerset_create_entity.
    DATA centraldataorg TYPE BAPIBUS1006_CENTRAL_ORGAN.
    DATA partner_data TYPE bapibus1006_central.
    DATA address TYPE bapibus1006_address.
    DATA bp TYPE bapibus1006_head-bpartner.
    DATA return TYPE TABLE OF bapiret2.



    DATA ls_request_input_data  TYPE zcl_z_customer_mpc=>ts_customer.
    io_data_provider->read_entry_data( IMPORTING es_data = ls_request_input_data ).
    IF ls_request_input_data IS NOT INITIAL.

      partner_data-searchterm2  = 'SaleForceCustomer'.
      centraldataorg-name1 = ls_request_input_data-name1.
      address-city = ls_request_input_data-city.
      address-country = ls_request_input_data-country.
      address-region = ls_request_input_data-region.
      address-c_o_name = ls_request_input_data-name1.
      address-time_zone = ls_request_input_data-time_zone.
      address-postl_cod1 = '123456'.
      address-langu = 'EN'.


      CALL FUNCTION 'BAPI_BPCONSUMER_CREATE'
        EXPORTING
*         PARTNER_EXTERNAL_NO       =
          partner_group             = 'BP02'
          partner_category          = '2'
          partner_central_data      = partner_data
*         CENTRAL_DATA_PERSON       =
          central_data_organization = centraldataorg
*         CENTRAL_DATA_GROUP        =
          partner_addr              = address
*         DUPLICATE_MESSAGE_TYPE_ADDR       =
*         ACCEPT_ERROR_ADDR         =
        IMPORTING
          businesspartner           = bp
        TABLES
*         PARTNER_TEL_ADDR          =
*         PARTNER_FAX_ADDR          =
*         PARTNER_TELETEX_ADDR      =
*         PARTNER_TELEX_ADDR        =
*         PARTNER_EMAIL_ADDR        =
*         PARTNER_RML_ADDR          =
*         PARTNER_X400_ADDR         =
*         PARTNER_RFC_ADDR          =
*         PARTNER_PRT_ADDR          =
*         PARTNER_SSF_ADDR          =
*         PARTNER_URI_ADDR          =
*         PARTNER_PAGER_ADDR        =
*         PARTNER_NOTE_ADDR         =
*         PARTNER_NOTECOM_ADDR      =
*         PARTNER_TEL_NONADDRESS    =
*         PARTNER_FAX_NONADDRESS    =
*         PARTNER_TELETEX_NONADDRESS        =
*         PARTNER_TELEX_NONADDRESS  =
*         PARTNER_EMAIL_NONADDRESS  =
*         PARTNER_RML_NONADDRESS    =
*         PARTNER_X400_NONADDRESS   =
*         PARTNER_RFC_NONADDRESS    =
*         PARTNER_PRT_NONADDRESS    =
*         PARTNER_SSF_NONADDRESS    =
*         PARTNER_URI_NONADDRESS    =
*         PARTNER_PAGER_NONADDRESS  =
*         PARTNER_NOTECOM_NONADDRESS        =
*         PARTNER_ADDRESSDUPLICATES =
*         PARTNER_BANK_ATTR         =
          return                    = return.

      IF  bp IS  NOT INITIAL.
        CALL FUNCTION 'BAPI_BUPA_ROLE_ADD'
          EXPORTING
            businesspartner     = bp
            businesspartnerrole = 'FLCU01'
*           DIFFERENTIATIONTYPEVALUE       =
*            TABLES
*           RETURN              =
          .

        IF ls_request_input_data-commit IS NOT INITIAL.
          COMMIT WORK.
*          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*              EXPORTING
*                WAIT          = ' '
*              IMPORTING
*          return                    = return.
          ER_ENTITY-businesspartner =  bp.
          er_entity-name1 = ls_request_input_data-name1.

        ELSE.
          "// error handling
        ENDIF.
      ELSE.
        "// error handling
      ENDIF.
    ENDIF.
  ENDMETHOD.

🙂Thank you

Pranjali Sharma

How can we export all entityTypes along with properties/ABAP Filed name

2024-04-09T04:28:23.478000+02:00

Hi Team

How can we export all entityTypes along with properties/ABAP Filed name related to corresponding standard ODATA Services which we activated under our landscape as per the business requirement

Best Regards

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

odata url accessibility

2024-04-12T19:59:12.964000+02:00

Inside the SAP S4 HANA 2021 fully activated appliance, i have enabled the SAP gateway to access odata service.

I am able to successfully execute the http and https using the SAP Gateway Client in GUI t code /n/IWFND/MAINT_SERVICES

same URLs are accessible in the browser

http://localhostfqdn/sap/opu/odata/sap/ MD_SUPPLIER_MASTER_SRV

http://localhostfqdn/sap/opu/odata/sap/ API_BUSINESS_PARTNER

http://localhostfqdn/sap/opu/odata/sap/ API_SUPPLIERINVOICE_PROCESS

Although the following odata is getting successfully executed using the SAP Gateway Client in GUI t code /n/IWFND/MAINT_SERVICES

FAP_VENDOR_LINE_ITEMS

While accessing through the browser, on prompt of user id password, the above SAP GUI user id if provided, it's not allowing me to access

http://localhostfqdn/sap/opu/odata/sap/ FAP_VENDOR_LINE_ITEMS

Please suggest some solution

The authorizations are checked and found to be in place, I mean the required ones are available

The url http://localhostfqdn/sap/opu/odata/sap/ FAP_VENDOR_LINE_ITEMS used with an entity set and a filter, its able to produce the data in the browser

How to pass parameter to getEntitySet from SAPUI5?

2024-04-17T17:09:05.155000+02:00

Hello everyone! I read the following post Solved: How to pass filter parameters to Get EntitySet fro... - SAP Community but it was not helpful. Basically, I need to pass a string as a parameter to my OData Gateway (getEntitySet) to bring a set of data filtered by said string from a Z table. My code for my controller in SAPUI5 is as follows:

var oFilterN = new Filter('FilterExample', FilterOperator.EQ, oExample);

var oParams = {
  filters: [oFilterN]
}
var oFilter = "/GetEntitySetExample";

oModel.read(oFilter, oParams, {
   success: function(oData){
      var oDataObtained = oData;
      var oModel = new JSONModel(oData);
      this.getView().setModel(oModel, "modelExample");
   }.bind(this),
    error: function(oError){}

});

(In the gateway service, I manage to obtain the parameter with this code, but it never enters the success or error of the controller in sapui5, so it does not allow me to obtain the data set)

And the code for my gateway service is as follows:

method getEntitySetExample_get_entityset.
  DATA: my_filter_options type /iwbep/t_mgw_select_option,
  lv_param type ztable-keycamp.
  READ TABLE it_filter_select_options INTO DATA(ls_filter) INDEX 1.
  lv_param = ls_filter-select_options[ 1 ]-low.
  select * from ZTABLE INTO CORRESPONDING FIELDS OF TABLE et_entityset WHERE keycamp EQ lv_param.
endmethod.

Annotation in SEGW

2024-04-18T16:26:51.058000+02:00

I have created a SEGW service . I have enabled the filter options so that when i consume it in VS so that I automatically get those fields as filter parameters .

But

I have some CDS views which are also part of the same OData .I want them to be a value help on the same those filter parameter .

I looked into this blog https://community.sap.com/t5/technology-blogs-by-members/odata-annotations-in-segw-with-example-and-consume-it-in-visual-studio-to/ba-p/13551588

.Instead of this fixed values , I want the CDS to be displayed or a table .

can anybody tell me what would be the right annotation for this .

Error While activating Odata service

2024-04-23T21:55:57.362000+02:00

Hi Experts,

I am unable to activate following odata services which are required for standard fiori app: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F4024')/S28OP

Tried adding the service from /Iwfnd/maint/service . Following Service appear in while adding the service, but error starts appearing.

C_EWM_ODOOVPGQ_2_CDS

C_EWM_OUTBDELIVORDADJQ_2_CDS

C_EWM_WAREHOUSEORDERQ_2_CDS

C_EWM_WAREHOUSETASKOVPGQ_2_CDS

C_EWM_WAREHOUSETASKQ_2_CDS

C_EWM_WHSEORDEROVPGQ_2_CDS

Able to see following error message when checked from /IWBEP/ERROR?LOG

Exception of type 'CX_RS_MSG' has occurred; see details for more information

-<CX_RS_MSG>

<MSGID>RSODP</MSGID>

<MSGNO>099</MSGNO>

<MSGTY>X</MSGTY>

<MSGV1/>

<MSGV2/>

<MSGV3/>

<MSGV4/>

</CX_RS_MSG>

Regards,

Nikhil1

MYINBOX: Issue with user decision task link from MYINBOX

2024-04-24T05:36:30.203000+02:00

Dear All,

I am facing below issue in FIORI MY Inbox, the link has ABAP code at the backend from BO-Method.

The task is user decision task and link open from SAP Inbox successfully. However, "Object Link 1" doesn't open.

Can anybody guide how this can be fixed?

I found below similar post however what to mention in SWUVISU in Frontend (Netweaver gateway server) is not mentioned clearly neither in post nor in Note. I will be thankful for kindly guiding further:

Solved: How to open Object Link in Fiori My Inbox - SAP Community

Regards.

odata Metadata issue for standard service

2024-04-25T20:39:20.474000+02:00

I am seeing an issue with the standard odata service delivered by SAP where function import parameters are not appearing correctly in the metadata. When I copy the standard project to custom and generate service, it shows all parameters as expected in metadata.

Setting the backend OData Service Alias in a BTP Destination. Possible?

2024-04-30T20:23:14.071000+02:00

Hi,

We have a scenario as follows with BTP UI5 apps making OData calls to backend ECC systems:

BTP Cloud Foundry UI5 App > BTP Destination > SAP Cloud Connector > Gateway Hub > ECC (NW 7.00)

For a very specific reason we would like to set the Alias assigned to the OData service on the Gateway Hub via the BTP Destination, rather than inside the UI5 app itself, or via other external means. I'm talking about the ";o=<ALIAS>" part of the OData URL.

I am hoping that SAP have some internal option within the SAP BTP Destination service (specifically on Cloud Foundry) which can inject the ";o=<ALIAS>" into the correct place in the OData URL if we specify it in a special Destination Property.

I have searched high and low and tried various properties like "sap-system-alias" or "sap-system" but they don't work, or were designed to work somewhere else. I have also tried these names and some others as HTTP Headers as a guess, but no luck.

Anyone have any idea if an 'Alias' Property exists in Cloud Foundry Destinations which can do what I need?

Note also that we are very experienced with all of this and know every other possible way to handle Aliases on OData calls in relation to BTP, ECC or S/4. But we have one very specific requirement where using a BTP Destination would save us a lot of hassle.

Thanks in advance,

Brendan

Issue in retrieving Delta link in MAIF OData response in application/json format only

2024-05-08T10:25:42.336000+02:00

I exposed some database tables as entities using Mobile Application Integration Framework(MAIF). Here, server-side paging is enabled, and delta sync is on in MAIF. When I try to retrieve the data using application/XML format, server is sending the data along with delta token but When I change accept format to application/json, server is not sending delta link.

When retrieving data in XML format

When retrieving the data in JSON format

Is something needs to be done in MAIF side? it seems weird that it work in XML but not in JSON.

Not able to locate sap:updatable or sap:creatable tags in metadata for SAP S/4HANA OData V4 APIs

2024-05-10T12:29:08.292000+02:00

Hi Team,

For any OData V4 APIs in SAP S/4HANA Cloud or On-premise, when we query for the $metadata for any service, we do not find these tags anymore: sap:creatable, sap:updatable, sap:delectable, etc to know if each entityset or field/property within an entity is supported for these operations or not.

Have we changed the mechanism to check this information on the compatibility?

Would be really helpful if someone in SAP S/4HANA product team can help us in answering this question since we are unable to know that which all fields supports what all operations within an entity by looking at the metadata which was pretty much clear in OData V2 APIs. @SAPSupport

Regards,

Sidhant Mahajan

Data transfer from Databricks to SAP - ODATA API

2024-05-14T06:54:56.450000+02:00

We need to move 200,000 records daily from a Data bricks environment on GCP to a custom table in SAP.
Since Data bricks can't expose workbook APIs due to their current capabilities , SAP will provide an OData API with a POST operation for data transfer. With the huge volume of data , performance can be a bottleneck . Below are the questions -

a) Is OData API intended for large data transfer ? What are the limitations ?
b) what are the best practices while transmitting huge volume data through ODATA rest API . Already aware of the Pagination / batching .
c) What other interfacing methods are possible with data bricks other than FTP and without any level of integration.

P.S : Exploring PyRFC from data bricks to call SAP RFC as an alternative.
We don't use SAP Datasphere