Data Provider Classes

The core of our solution is a set of ABAP classes which expose common SAP objects via REST. These data provider classes (DPC) are delivered per object, so can be imported selectively based on your specific use case.

CRUISE Abstract Class.png

Extracting SAP content in a "clean" way

Our classes are designed to handle:

Field Mapping

We provide pre-filled mapping tables for converting SAP names into business standard names. This way consumers of the APIs will see "business friendly" names:

mapping_table_head.png

In the example below see how the description field for an equipment has been converted. Note how we base this naming convention on the SAP S/4HANA CDS names:

mapping_table_fields.png

The mappings can be done directly in SAP Gui (via a view cluster) we also provide a UI5 Application to do this via our Cruise Administration tooling:

Employee mapping.png

Delivery mechanism

These classes can be imported via ABAPGit and we maintain versions per API level. The only dependancy we have is on the logging framework (which is optional but recommended for efficient tracking and support processes).

Config driven

As part of the Cruise framework we include a metadata extraction method (fields and data types) of our APIs - this is used in the downstream no-code systems.

Logging

On the SAP side we leverage application logs for each of the objects, this allows for detailed analysis and tracking on APIs (this is over and above the logging provided by Neptune Software) and is designed to help support functional users who are trying to evaluate any functional issues that may be occuring:

application_log_example_equipment.png