1. Business process summary

The SELFY solution support the site logistics / shipment execution journey related to the yard management, for drivers arriving at site, registering, checking in, loading, and checking out. The core functional flow is: driver arrival → ATM or Selfy Web registration → SAP Get Data → check-in validation → SAP check-in → loading → ATM or Selfy Web check-out → SAP check-out. The SAP check-in and check-out steps are noted as applying only for loading scenarios.

The SELFY sites including Spinatte site (PF2 & Inovyn ECC), Ospiate (WP2) and Mereville (WP2), and indicate that the same core business pattern is used with both WP2 and PF2 SAP ECC back ends.

2. Functional modules used by SAP / SELFY

For both WP2 and PF2, the same SAP functional modules are referenced:

Get Data → Z_1T_SELFY_GET_DATA
Check-In → Z_1T_SELFY_CHECK_IN
Check-Out → Z_1T_SELFY_CHECK_OUT
Shipment List / Backup retrieval → Z_1T_SELFY_SHIPMENT_GET_LIST

The purpose of these modules as described below:

Get Data retrieves shipment / process information from SAP for SELFY.
Check-In updates the check-in status in SAP.
Check-Out completes the shipment in SAP.
Shipment Get List is used as a backup list, especially if there is an issue with SAP ECC and/or SAP Integration Suite.

Reference Documents

Document
Project's High-Level Design Document
Use Case: Customer Creation Sync

High Level Design Diagram

Integration Platform > Selfy and SAP Integration > Selfy Integration Architecture - High Level.png

Integration Platform > Selfy and SAP Integration > Selfy Integration Architecture - Interfaces.jpeg

Sequence Diagram

Visual flow of message between system(s)