Skip to main content

Data Model

Create a new Data Model or adapt an existing Data Model

After extracting all the necessary data and adapting it to the requirements, it must now be added to the O2C data model. This can be done using an existing DM or in a separate DM.

Visual of the relevant part of the DM:

data_model_overview.PNG

Table

Description

Sections

SHIPMENT_NETWORK

  • Mandatory

  • Link table between Sales Order, Delivery and Shipment tables

  • Table structure enables use of Signal Link technology and Network Explorer

Add SHIPMENT_NETWORK table to data model

UNIQUE_SHIPPING_STAGES

  • Mandatory

  • Derived from VTTS

  • Includes all unique shipment stages (unique in terms of the combination of departure address - arrival address - transport mode - shipping type)

  • Used for the calculation of emissions

  • Data from this table is input for the carbon engine

Add UNIQUE_SHIPPING_STAGES table to data model

TRANSPORT_EMISSIONS_DATA

  • Mandatory

  • Includes emissions (results from carbon engine) of unique shipping stage

Add TRANSPORT_EMISSIONS_DATA table to data model

TRANSPORT_SECTIONS_EMISSIONS_DATA

  • Mandatory

  • Leg emissions (results from carbon engine)

Add TRANSPORT_SECTIONS_EMISSIONS_DATA table to data model

TRANSPORT_EMISSION_FACTORS

  • Mandatory

  • Includes detailed information about the calculated emissions (results from carbon engine)

Add TRANSPORT_EMISSION_FACTORS table to data model

UNIQUE_SHIPPING_ROUTES

  • Optional

  • Derived from UNIQUE_SHIPPING_STAGES

  • Includes all unique shipment stages (unique in terms of the combination of departure address - arrival address)

  • Used for shipping type simulation use case

Add UNIQUE_SHIPPING_ROUTES table to data model

TRANSPORT_EMISSIONS_DATA_ROUTE

  • Optional

  • Same table as previous, but joined to UNIQUE_SHIPPING_STAGES with different foreign key

  • Used for shipping type simulation use case

Add the TRANSPORT_EMISSIONS_DATA_ROUTE table to the data model

TRANSPORT_SECTIONS_EMISSIONS_DATA_ROUTES

  • Optional

  • Same table as previous, but joined to UNIQUE_SHIPPING_STAGES with different foreign key

  • Used for shipping type simulation use case

Add the TRANSPORT_SECTIONS_EMISSIONS_DATA_ROUTE table to the data model

TRANSPORT_EMISSION_FACTORS_ROUTE

  • Optional

  • Same table as previous, but joined to UNIQUE_SHIPPING_STAGES with different foreign key

  • Used for shipping type simulation use case

Add the TRANSPORT_EMISSION_FACTORS_ROUTE table to the data model

VTTK

  • Mandatory

  • SAP - Shipment Header Table

Add the VTTS table to data model

VTTP

  • Mandatory

  • SAP - Shipment Item Table

Add the VTTP table to the data model

VTTS

  • Mandatory

  • SAP - Shipment Stage Table

Add the VTTK table to the data model

SHIPPING_LIKP

  • Mandatory

  • SAP - Delivery Header Table

Add the SHIPPING_LIPS table to the data model

SHIPPING_LIPS

  • Mandatory

  • SAP - Delivery Items Table

Add SHIPPING_LIKP table to data model

SHIPPING_TYPE_METADATA

  • Mandatory

  • Contains metadata about each shipping type which is used for the emission calculation

Add SHIPMENT_NETWORK table to data model

  • Add the O2C_SHIPMENT_NETWORK view, give it the alias SHIPMENT_NETWORK, and connect it to VBAP.

    image58.png
    image57.png

Add UNIQUE_SHIPPING_STAGES table to data model

  • Add the O2C_UNIQUE_SHIPPING_STAGES view, give it the alias UNIQUE_SHIPPING_STAGES, and connect it to SHIPMENT_NETWORK.

    image63.png
    image60.png

Add TRANSPORT_EMISSIONS_DATA table to data model

  • Add the O2C_TRANSPORT_EMISSIONS_DATA view, give it the alias TRANSPORT_EMISSIONS_DATA, and connect it to UNIQUE_SHIPPING_STAGES.

    image20.png
    image25.png

Add TRANSPORT_SECTIONS_EMISSIONS_DATA table to data model

  • Add the O2C_TRANSPORT_SECTIONS_EMISSIONS_DATA view, give it the alias TRANSPORT_SECTIONS_EMISSIONS_DATA, and connect it to UNIQUE_SHIPPING_STAGES.

    image36.png
    image28.png

Add TRANSPORT_EMISSION_FACTORS table to data model

  • Add the O2C_TRANSPORT_EMISSION_FACTORS view, give it the alias TRANSPORT_EMISSION_FACTORS, and connect it to UNIQUE_SHIPPING_STAGES.

    image34.png
    image37.png

Add UNIQUE_SHIPPING_ROUTES table to data model

  • Add the O2C_UNIQUE_SHIPPING_ROUTES view, give it the alias UNIQUE_SHIPPING_ROUTES, and connect it to UNIQUE_SHIPPING_STAGES.

    image21.png
    image27.png

Add the TRANSPORT_EMISSIONS_DATA_ROUTE table to the data model

  • Add the O2C_TRANSPORT_EMISSIONS_DATA view again, and resolve the naming conflict by giving it the alias TRANSPORT_EMISSIONS_DATA_ROUTE. Then connect it to UNIQUE_SHIPPING_ROUTES.

    image30.png
    image22.png

Note

TRANSPORT_EMISSIONS_DATA_ROUTE is linked with UNIQUE_SHIPPING_ROUTES via UNIQUE_STAGE.

Add the TRANSPORT_SECTIONS_EMISSIONS_DATA_ROUTE table to the data model

  • Add the O2C_TRANSPORT_SECTIONS_EMISSIONS_DATA view again, and resolve the naming conflict by giving it the alias TRANSPORT_SECTIONS_EMISSIONS_DATA_ROUTE. Then connect it to UNIQUE_SHIPPING_ROUTES.

    image8.png
    image18.png

Note

TRANSPORT_EMISSIONS_DATA_ROUTE is linked with UNIQUE_SHIPPING_ROUTES via UNIQUE_STAGE.

Add the TRANSPORT_EMISSION_FACTORS_ROUTE table to the data model

  • Add the O2C_TRANSPORT_EMISSION_FACTORS view again, and resolve the naming conflict by giving it the alias TRANSPORT_EMISSION_FACTORS_ROUTE. Then connect it to UNIQUE_SHIPPING_ROUTES.

    image13.png
    image9.png

Note

TRANSPORT_EMISSIONS_DATA_ROUTE is linked with UNIQUE_SHIPPING_ROUTES via UNIQUE_STAGE.

Add the VTTS table to data model

  • Add the O2C_VTTS view, give it the alias VTTS, and then connect it to SHIPMENT_NETWORK.

    image14.png
    image5.png

Add the VTTP table to the data model

  • Add the O2C_VTTP view, give it the alias VTTP, and then connect it to SHIPMENT_NETWORK.

    image11.png
    image24.png

Add the VTTK table to the data model

  • Add the O2C_VTTK view, give it the alias VTTK, and then connect it to VTTP.

    image16.png
    image1.png

Add the SHIPPING_LIPS table to the data model

  • The view LIPS is already part of the data model. Add O2C_LIPS again and resolve the conflict by naming it SHIPPING_LIPS. Then connect it to SHIPMENT_NETWORK.

    image19.png
    image10.png

Add SHIPPING_LIKP table to data model

  • The LIKP view is already part of the data model. Add O2C_LIKP again and resolve the conflict by naming it SHIPPING_LIKP. Then connect it to SHIPMENT_NETWORK.

    image3.png
    image4.png