System and method for improved SAP communications
A terminator node is provided that acts as termination on one end of the communication channel and links to the SAP server on the other end. A server device is also provided that monitors communications between the SAP server and a client. The server device condenses SAP application screens to streamline user interaction with the SAP server. The server device simulates certain types of required responses to the SAP server to allow for a persistent session between a client and the SAP server when the actual connection may be intermittent. The server device stores required records for a transaction and provides them to a client for offline processing and then synchronizes stored offline transaction data from the client with the SAP server. The system may include a client device that optionally implements the terminator node to communicate either with the server device or directly to the SAP server.
1. A computer-implemented method for facilitating communications between a client mobile device and a SAP server, comprising:
receiving a communication directed to the client mobile device from the SAP server;
parsing the communication with a processor into one or more requests;
determining if each of the one or more requests requires a response to maintain a session between the client mobile device and the SAP server; and
sending a simulated response to the SAP server in response to each of the determined ones of the one or more requests that require the response to maintain the session between the client mobile device and the SAP server.
2. The computer-implemented method of claim 1 , wherein the determining if each of the one or more requests requires the response to maintain the session between the client mobile device and the SAP server further comprises determining if the each of the one or more requests is a remote function call (RFC) request; and wherein the computer-implemented method further comprises forwarding ones of the one or more requests that are determined not to be a RFC request to the client mobile device.
3. The computer-implemented method of claim 2 , wherein the determining if each of the one or more requests requires the response to maintain the session between the client mobile device and the SAP server further comprises determining if each determined RFC request requires the response to maintain the session between the client mobile device and the SAP server; and wherein the computer-implemented method further comprises generating the simulated response for the each determined RFC request that is determined to require the response to maintain the session between the client mobile device and the SAP server.
4. The computer-implemented method of claim 1 , further comprising forwarding remaining ones of the one or more requests that do not require the response to maintain the session between the client mobile device and the SAP server to the client mobile device, and forwarding a client response from the client mobile device to the SAP server for the remaining ones of the one or more requests.
5. The computer-implemented method of claim 1 , further comprising executing an action for the each of the determined ones of the one or more requests that require the response to maintain the session between the client mobile device and the SAP server after sending the simulated response to the SAP server.
6. The computer-implemented method of claim 1 , further comprising translating the communication from the SAP server into a format used by the client mobile device.
7. The computer implemented method of claim 1 , wherein the simulated response is sent to obtain a full range of available data from the SAP server.
8. The computer-implemented method of claim 2 , where the RFC request is an OLE_FLUSH_CALL associated with a plurality of discrete actions, wherein the simulated response is based on each of the plurality of discrete actions.
9. The computer-implemented method of claim 8 , wherein the simulated response comprises one or more handles associated with ones of the plurality of discrete actions that require a handle.
10. The computer-implemented method of claim 9 , wherein the client mobile device generates the one or more handles.
11. A client mobile device, comprising:
a processor configured to:
parse a communication from a SAP server into one or more requests;
determine if each of the one or more requests requires a response to maintain a session between the client mobile device and the SAP server; and
send a simulated response to the SAP server in response to each of the determined ones of the one or more requests that require the response to maintain the session between the client mobile device and the SAP server.
12. The client mobile device of claim 11 , wherein the processor is configured to determine if each of the one or more requests requires the response to maintain the session between the client mobile device and the SAP server by determining if the each of the one or more requests is a remote function call (RFC) request; and wherein the processor is further configured to designate ones of the one or more requests that are determined not to be a RFC request as a lower priority.
13. The client mobile device of claim 12 , wherein the processor is configured to determine if each of the one or more requests requires the response to maintain the session between the client mobile device and the SAP server by determining if each determined RFC request requires the response to maintain the session between the client mobile device and the SAP server; and wherein the processor is further configured to generate the simulated response for the each determined RFC request that is determined to require the response to maintain the session between the client mobile device and the SAP server.
14. The client mobile device of claim 11 , wherein the processor is further configured to designate remaining ones of the one or more requests that do not require the response to maintain the session between the client mobile device and the SAP server as having a lower priority.
15. The client mobile device of claim 11 , wherein the processor is further configured to execute an action for the each of the determined ones of the one or more requests that require the response to maintain the session between the client mobile device and the SAP server after sending the simulated response to the SAP server.
16. The client mobile device of claim 11 , wherein the processor is further configured to translate the communication from the SAP server into a format used by the client mobile device.
17. The client mobile device of claim 11 , wherein the processor is further configured to send the simulated response to receive a full range of available data from the SAP server.
18. The client mobile device of claim 12 , where the RFC request is an OLE_FLUSH_CALL associated with a plurality of discrete actions, wherein the simulated response is based on each of the plurality of discrete actions.
19. The client mobile device of claim 18 , wherein the simulated response comprises one or more handles associated with ones of the plurality of discrete actions that require a handle.
20. The client mobile device of claim 19 , wherein the client mobile device generates the one or more handles.
21. A method for a client mobile device, comprising:
parsing a communication from a SAP server with a processor into one or more requests;
determining if each of the one or more requests requires a response to maintain a session between the client mobile device and the SAP server; and
sending a simulated response to the SAP server in response to each of the determined ones of the one or more requests that require the response to maintain the session between the client mobile device and the SAP server.
22. The method of claim 21 , wherein the determining if each of the one or more requests requires the response to maintain the session between the client mobile device and the SAP server further comprises determining if the each of the one or more requests is a remote function call (RFC) request; and
wherein the method further comprises designating ones of the one or more requests that are determined not to be a RFC request as a lower priority.
23. The method of claim 22 , wherein the determining if each of the one or more requests requires the response to maintain the session between the client mobile device and the SAP server further comprises determining if each determined RFC request requires the response to maintain the session between the client mobile device and the SAP server; and wherein the method further comprises generating the simulated response for the each determined RFC request that is determined to require the response to maintain the session between the client mobile device and the SAP server.
24. The method of claim 21 , further comprising designating remaining ones of the one or more requests that do not require the response to maintain the session between the client mobile device and the SAP server as having a lower priority.
25. The method of claim 21 , further comprising executing an action for the each of the determined ones of the one or more requests that require the response to maintain the session between the client mobile device and the SAP server after sending the simulated response to the SAP server.
26. The method of claim 21 , further comprising translating the communication from the SAP server into a format used by the client mobile device.
27. The method of claim 21 , further comprising maintaining the simulated response until a full range of available data from the SAP server is obtained.
28. The method of claim 22 , where the RFC request is an OLE-FLUSH_CALL associated with a plurality of discrete actions, wherein the simulated response is based on each of the plurality of discrete actions.
29. The method of claim 28 , wherein the simulated response comprises one or more handles associated with ones of the plurality of discrete actions that require a handle.
30. The method of claim 29 , further comprising generating and simulating the one or more handles.