Mapping Between SPI and OData Model

The nodes, Data Structure, ID Structure in the SPI Model are transformed to the corresponding entities in an OData Model. Mapping on the same is provided here:

Gateway Relevance Analyzer validates the SPI application internally for Gateway relevance. It runs through the metadata of the SPI model and checks for entities, associations, actions, navigation relevant for SAP NetWeaver Gateway. This runs automatically when you try to create an SAP NetWeaver Gateway Service for SPI. If the SPI application is Gateway relevant, the SAP NetWeaver Gateway Service Generator for SPI generates a Gateway service along with the necessary configuration entries. It checks for the following:

Node

1. For each node of SPI layer there is either an ID Structure or an ID Table Type (in SPI layer) which are mapped as Keys in the SAP NetWeaver Gateway layer. The Gateway Relevance Analyzer checks for this and:

   • If either one of them is present, it checks for other conditions

   • If both the ID Structure and the ID Table Type are missing, the node is skipped

2. For each node of SPI layer there is either a Data Structure or a Data Table Type (properties), which is used to get the properties in SAP NetWeaver Gateway layer. The Gateway Relevance Analyzer checks for this and:

   • If either one of them is present, it checks for other conditions

   • If both the Data Structure and the Data Table Type are missing, the node is skipped

3. If the ID Structure or the ID Table type or the Data Structure or the Data Table Type is of Deep type (has a table inside it), then the node is skipped.

4. If the ID Structure or the ID Table type or the Data Structure or the Data Table Type has a Group Name for any of the Named Include then the node is skipped.

5. If the parent node is skipped then all the child nodes are also skipped.

Action

1. If the Action Structure has a Deep Type, the action is skipped.

2. If a node is skipped then all actions of that node are also skipped.