enaio® data2s

enaio® data2s • 11.10 »

enaio® data2s enables RFC-enabled function modules in an SAP® system to be called via a web-based interface using HTTP or HTTPS. To this end, an HTTP request is sent to the SAP® system, in which a login to the SAP® as well as all parameters for calling the function module are transferred.

The function executed by the respective SAP® function module is highly variable. Typical examples include creating/posting SAP® documents (for example, for incoming invoices) and reading out information (for example, purchase order properties). OPTIMAL SYSTEMS also provides two function modules with document-related functions:

  • /OSGMBH/D2S_MOVE_DOCUMENT – to move a document to the technical cabinet

  • /OSGMBH/D2S_INSERT_CONNECTION – to link a document in the technical cabinet with an SAP® object (document).

If the call is successful, the function module’s return parameters are returned in the response and can be evaluated. However, the request can also fail due to one of several causes of errors. These must be evaluated by the program performing the evaluation:

  • Connection and interface problems: server unreachable, incorrect login, incorrect parameters/values, missing permissions, syntax errors. This type of error leads to timeouts or HTTP error codes (404, 500, etc.).
  • Exceptions of the called module: These lead to a SOAP exception in the response.
  • Technical error: Module is successfully called with return parameters, but messages are issued in one of the return values (BAPI standard).

So that a function module can be called via enaio® data2s, the following requirements must be ensured and the following preparations must be made:

  • The SAP® system must meet the necessary requirements and, in principle, be accessible via HTTP or HTTPS.
  • An enterprise service must be created in the SAP® system for the specific function module.
  • An endpoint must have been generated for the Enterprise Service in the SOA MANAGER transaction. A WSDL file containing the description of the interface can also be called via the endpoint.
  • The specific call is implemented and executed in any chosen programming language.