Loading Templates from SAP

The dialogue offers three different possibilities. Templates, IDocs, RFCs.

images/download/attachments/21305754/SAP_3_EN-version-1-modificationdate-1529995123000-api-v2.png

(1) Selection of a supplied IDoc structure template. An online connection to the SAP system is not necessary here. These structure templates are also available to users without a license for the SAP service. There are templates for the source and destination structure. See section Loading an IDoc Structure from Lobster_data.

(2) The IDoc types including the segment types (the currently activated version) can be read from the repository of a connected SAP system and imported into Lobster_data. CIM types and even own IDocs (Z types) can be imported. See section Loading an IDoc Structure from SAP Repository

(3) You can import the interface structure of the IMPORT and TABLE parameters of a function module (RFC) from the repository of a connected SAP system into the destination or source structure of a Lobster_data profile. User function modules (Z types) are also supported. See section Loading an RFC Structure from SAP Repository.

Particularities in a Development Environment

Immediately after the modification of an RFC or IDoc is activated in the SAP Repository, it may happen that Lobster_data still 'sees"' the old structure for a certain period of time. This is because repository information that has once been read into the interface of the SAP service, is cached for the current connection. Therefore, you can only be sure to see the current state of the SAP side after a new connection to the SAP system has been established.

In a Lobster production system, an existing connection is usually used as long as possible to achieve the highest possible performance. However, an SAP development system should be connected and disconnected each time in order to be able to use changes in the repository as immediately as possible. For this purpose, the properties maxSize and minSize of the SAP alias for the development system in the configuration file ./etc/sap.xml must both have the value 0.

<Set name="minSize">0</Set>
<Set name="maxSize">0</Set>