IP Library Granted Patent US 12708180
Granted Patent B2
US 12708180 · App. 18/216,896 · Granted Aug 18, 2026

Methods, systems and computer readable media for providing a user interface for HTML SAP applications

Inventor: Harsimran Singh Dhami (Zirakpur, IN)
Assignee: Precisely Software Incorporated
A43C11/14
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12708180
App. No.
18/216,896
Granted
Aug 18, 2026
Kind
B2
Abstract

A method for providing a user interface for HTML SAP applications includes identifying, by a user device and among network traffic generated for at least an SAP application, representational state transfer application programming interface (REST API) calls sent to a server. The method further includes identifying, by the user device, user-filled keys in the identified REST API calls. The method further includes displaying, by a user interface on the user device, the user-filled keys. The method further includes receiving user input for the user-filled keys on the user interface. The method further includes updating the REST API calls based on the received user input and executing the updated REST API calls. The method further includes displaying responses to the REST API calls from the server on the user interface.

Claims (41)

1 . A method for providing a user interface for HTML SAP applications, the method comprising:

upon initiation of a business activity using an SAP Web-GUI application or SAP Fiori GUI application, intercepting, by a user device, network traffic for at least the SAP Web-GUI application or the SAP Fiori GUI SAP application generated between a web browser and a server;

removing, by the user device from the network traffic, HTTP requests from the network traffic that have a property “type” set to a value other than “xhr” to produce filtered network traffic;

identifying, by the user device and among the filtered network traffic, representational state transfer application programming interface (REST API) calls sent to the server by identifying endpoint URLs of the REST API calls that include predetermined relative URL endings;

identifying, by the user device, user-filled keys and system-filled keys in the identified REST API calls based on predetermined key names;

displaying, by a user interface on the user device that is separate from the web browser, the user-filled keys;

receiving, on the user interface, user input for the user-filled keys;

updating, by the user device, the REST API calls based on the received user input;

replaying, by the user device to the server and without the web browser, the updated REST API calls; and

displaying, on the user interface, responses to the REST API calls from the server.

2 . The method of claim 1 wherein updating the REST API calls comprises updating the REST API calls to include authentication headers.

3 . The method of claim 1 wherein identifying the REST API calls sent to the server comprises:

determining, by the user device, that the server uses an alias for a relative URL of an endpoint; and

identifying the REST API calls with the alias in relative URLs of the REST API calls.

4 . A system for providing a user interface for HTML SAP applications, the method comprising:

a processor;

a memory communicatively connected to the processor; and

a user device implemented using the processor and the memory, wherein the user device is configured for:

upon initiation of a business activity using an SAP Web-GUI application or SAP Fiori GUI application, intercepting, by a user device, network traffic for at least the SAP Web-GUI application or the SAP Fiori GUI SAP application generated between a web browser and a server;

removing, by the user device from the network traffic, HTTP requests from the network traffic that have a property “type” set to a value other than “xhr” to produce filtered network traffic;

identifying, among the filtered network traffic, representational state transfer application programming interface (REST API) calls sent to the server by identifying endpoint URLs of the REST API calls that include predetermined relative URL endings;

identifying user-filled keys and system-filled keys in the identified REST API calls based on predetermined key names;

displaying the user-filled keys by a user interface on the user device that is separate from the web browser;

receiving user input for the user-filled keys on the user interface;

updating the REST API calls based on the received user input;

replaying the updated REST API calls to the server and without the web browser; and

displaying responses to the REST API calls from the server on the user interface.

5 . The system of claim 4 wherein the user device is configured for updating the REST API calls to include authentication headers.

6 . The system of claim 4 wherein the user device is configured for identifying the REST API calls sent to the server by:

determining that the server uses an alias for a relative URL of an endpoint; and

identifying the REST API calls with the alias in relative URLs of the REST API calls.

7 . A non-transitory computer readable medium having stored thereon executable instructions that when executed by at least one processor of at least one computer cause the at least one computer to perform steps comprising:

upon initiation of a business activity using an SAP Web-GUI application or SAP Fiori GUI application, intercepting, by a user device, network traffic for at least the SAP Web-GUI application or the SAP Fiori GUI SAP application generated between a web browser and a server;

removing, by the user device from the network traffic, HTTP requests from the network traffic that have a property “type” set to a value other than “xhr” to produce filtered network traffic;

identifying, among the filtered network traffic generated for at least an SAP application, representational state transfer application programming interface (REST API) calls sent to the server by identifying endpoint URLs of the REST API calls that include predetermined relative URL endings;

identifying user-filled keys and system-filled keys in the identified REST API calls based on predetermined key names;

displaying the user-filled keys by a user interface on the user device that is separate from the web browser;

receiving user input for the user-filled keys on the user interface;

updating the REST API calls based on the received user input;

replaying the updated REST API calls to the server and without the web browser; and

displaying responses to the REST API calls from the server on the user interface.