2/19/2022

Oil & Gas

Generated on: 2022-02-19 07:47:41 GMT+0000

SAP S/4HANA | 2020 (Oct 2020)

PUBLIC

Original content: https://help.sap.com/viewer/0f4ab800d01c4366b0c9aaff06a64320/2020.000/en-US

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/viewer/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 2/19/2022

Apps in Trader's and Scheduler's Workbench

My Nominations

Use
With this app you can:

View all the nominations for which you are authorized

Mass edit single nominations

Mass update nomination elds in edit mode

Create single or multiple copies of a nomination

View, edit, or delete the events in a nomination

This app is available for the role(s) SAP_BR_TRANSP_SCHDLR_IOG (Transportation Scheduler (OG)).

Key Features
Dynamic tile to show the number of open nominations (not in status complete, rejected, or dummy) on the tile

Table variants for all tables and lter criteria

Save as a tile Feature

View the nominations in the system based on various lter criteria

View the latest event present in a nomination

View all the events present in all nominations

Add new events and change existing events in a nomination

Edit multiple nominations at once and mass update elds in the edit mode

Create single or multiple copies of a nomination or a group of nominations at once

Navigate to respective reference document based of reference document type

Navigate to nomination transaction from the nomination number

Calculate scheduled end date to the end of every month based on the scheduled start date, this option is provided as
default. If you wish to change this default behavior, you can use the extension point provided and customize it according
to your business needs.

Save the lter criteria as a variant and retrieve for later use

Save the variant as a new tile, which can be accessed from the SAP Fiori launchpad as a separate tile

Component for Customer Incidents

IS-OIL-DS-TSW

More Information

This is custom documentation. For more information, please visit the SAP Help Portal 2
 2/19/2022
App Implementation: My Nominations

App Extensibility: My Nominations

App Implementation: My Nominations

System Landscape Requirements

For information about the system requirements, see System Requirements.

 Note
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an
appropriate virus scanner in your SAP Fiori system landscape and de ne sufficiently restrictive scan pro les to prevent the
upload of malicious content.

For more information on virus scanning and scan pro les for apps, see section Virus Scanning in the SAP S/4HANA Security
Guide .

Tile Type for Launching App

The My Nominations transactional app is launched using SAP Fiori tile.

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F2231.

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 2/19/2022
Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) TSW_MYNOMINATIONS_SRV_01(1)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAP UI5 Application

Component Technical Name

SAP UI5 Application TSW_NOM_S1

Generic Drill-Down Application /default_host/sap/bc/ui5_ui5/sap/sbrt_appss1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server: Activate ICF Service

Component Technical Name

ICF Service TSW_MYNOMINATIONS_SRV_01

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

This is custom documentation. For more information, please visit the SAP Help Portal 4
 2/19/2022
SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

TSW_MYNOMINATIONS_SRV_01 (1) You can use the example business catalog Use an existing role or create a new one.
or your custom catalog to create the back-
SAP_BR_TRANSP_SCHDLR_IOG
end PFCG role.

You can use the authorization object

O_OIJ_NOM to create the PFCG role.

App Extensibility: My Nominations

Use
You can extend the My Nominations app according to your business needs for different aspects.

For Developers
To add a customer eld to the app, the extensibility entities listed below are available on the different software layers. You have
to extend each of these entities according to your speci c business needs:

UI Back End/ABAP

View Design Time: Gateway Entity Design Time: CDS View

COIJ06_MYNOM TSW_MYNOMINATIONS C_Oij06_MyNominations

Further Extensibility Entities

Extension Points

For custom elds in a table and lters, for example, the following extension points are available:

This is custom documentation. For more information, please visit the SAP Help Portal 5
 2/19/2022

View Extension Point Use

Nominations extNominationsFilterBarItems Add elds to lterbar

Nominations extNominationsFilterBarGroupItems Add elds (Group) to lterbar

Nominations extNominationsViewAddTableFields Add elds to Nominations Table

Nominations extNominationsViewToolbar Add elds to Nominations Table Toolbar

If there are additional elds available in the OData service, you can display these elds on the UI. For more information about
extension points, see Extend SAP Fiori Apps.

UI Controller Hooks

To plug in and execute custom code to <business case>, for example, the following hooks are available in the controller code:

Controller Hook Use

CopyChangeNominations extHookAddMassChangeFields Adds elds to mass update fragment in

controller

CopyChangeNominations extHookAddAdditionalFields Adds elds to additional eld fragment in

controller

CopyChangeNominations extHookModifyChangeNomData Changes elds of Nom Data in controller

CopyChangeNominations extHookModifyCreatedNomData Modi es created elds of Nom Data in

controller

CopyChangeNominations extHookModifyMultiCreatedNomData Modi es multiple created elds of Nom

Data in controller

CopyChangeNominations extHookModifyD tSchedEndDate Mod es the defaulting of scheduled end

date to end of the month

If there are additional UI controller hooks available in the controller code, you can extend the UI controller code. For more
information about UI controller hooks, see Extend SAP Fiori Apps.

Display of UI Controls

As an example, the following UI controls can be hidden from the app UI:

View Control ID Use

CopyChangeNominations extCopyChangeNominationsAddTableFields Add elds to table elds in the view

SortNominationsTable extAddSortFields Add elds to for table sort options in

fragment

GroupNominationsTable extAddGroupTableFields Add elds to provide necessary

grouping of elds in fragment

Fragment Control ID Use

MassChange extMassChangeFields Add elds to mass change fragment

SortNominationsTable extAddSortFields Add elds to for table sort options in

fragment

This is custom documentation. For more information, please visit the SAP Help Portal 6
 2/19/2022

Fragment Control ID Use

GroupNominationsTable extAddGroupTableFields Add elds to provide necessary grouping of

elds in fragment

For more information about hiding UI controls, see Extend SAP Fiori Apps.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.

Regional Inventory View

Use
With this SAP Fiori app you can view the inventory gures for multiple location-material combinations over a date range. User-
speci c alerts con gured in the Inventory Planning Workbench can be categorized in this SAP Fiori app, which will be displayed
along with the inventory gures. A drill-down with the alert details is also displayed. You can also navigate to Inventory Planning
Workbench for the selected location-material combinations.

This SAP Fiori app is available for the role(s) SAP_BR_TRANSP_SCHDLR_IOG (Transportation Scheduler (OG)).

Key Features
View inventory gures for location-material-valuation type combinations for a selected date range.

Categorize the alerts con gured in Inventory Planning Workbench into alerts, warnings, information.

View the alert details pertaining to all the inventory types over a date range for the selected location-material
combinations using the heat map option.

Navigate to Inventory Planning Workbench for selected location-material combinations.

Save the lter criteria as a variant and retrieve for later use.

Save the variant as a new tile, which can be accessed from the ori launchpad as a separate tile.

Save a default variant and the count of the alerts will be displayed as a KPI on the KPI tile.

Navigation Targets
The SAP Fiori app enables users to access other SAP Fiori apps directly (for example to display detailed information).

 Note
These linked SAP Fiori apps have to be already available in your system landscape or you have to implement them along with
this SAP Fiori app.

Inventory Planning Workbench

Component for Customer Incidents

IS-OIL-DS-TSW

This is custom documentation. For more information, please visit the SAP Help Portal 7
 2/19/2022

More Information
App Implementation: Regional Inventory

App Implementation: Regional Inventory

Prerequisites
You have:

Implemented the Inventory Planning Workbench (IPW)

Set the alerts in the IPW user settings

Set the alert preferences in the SAP Fiori app Regional Inventory

Set a default variant or con gured lters in the evaluation, if you want to view the alert count on the tile.

System Landscape Requirements

For information about the system requirements, see System Requirements.

 Note
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an
appropriate virus scanner in your SAP Fiori system landscape and de ne sufficiently restrictive scan pro les to prevent the
upload of malicious content.

For more information on virus scanning and scan pro les for apps, see section Virus Scanning in the SAP S/4HANA Security
Guide .

Tile Type for Launching App

The Regional Inventory analytical app is launched using a KPI tile.

Implementation Tasks
The following sections list tasks that have to be performed to implement this SAP Fiori app. The tables contain the app-speci c
data required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F2232.

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 8
 2/19/2022
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) TSW_REGIONAL_INVENTORY_SRV_01(1)

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAP UI5 Application

Component Technical Name

SAP UI5 Application TSW_REG_INVS1

Generic Drill-Down Application /default_host/sap/bc/ui5_ui5/sap/sbrt_appss1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server: Activate ICF Service

Component Technical Name

ICF Service TSW_REGIONAL_INVENTORY_SRV_01

This is custom documentation. For more information, please visit the SAP Help Portal 9
 2/19/2022
For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

TSW_REGIONAL_INVENTORY_SRV_01 (1) You can use the example business catalog SAP_BR_TRANSP_SCHDLR_IOG
or your custom catalog to create the back-
end PFCG role.

You can use the authorization object

O_OIJ6_INV to create the PFCG role.

Con guration Settings: Regional Inventory View

Use
This document contains con guration information for the SAP Fiori app Regional Inventory View.

SAP Jam Integration

For information on how to con gure SAP Jam, see http://help.sap.com/sapjam .

SAP Smart Business Modeler

This is custom documentation. For more information, please visit the SAP Help Portal 10
 2/19/2022
Before you can use this app, you need to con gure it using the SAP Smart Business Modeler. For more information, see SAP
Smart Business Modeler Apps.

 Note
You can edit the following details related to an SAP-delivered evaluation:

Parameters values

Filter values

Thresholds

Semantic object and action

You can also revert the changes you make to SAP-delivered evaluations. When you upgrade to the next version of SAP Smart
Business Modeler apps, the changes made to the SAP-delivered evaluation in the existing version will be merged with the
new version.

KPI: Regional Inventory

KPI ID: .K.1465378267554

KPI Description: KPI Tile for Regional Inventory

Goal Type: Minimizing (Lower is better)

Data Source

Parameter Value

OData Service /sap/opu/odata/SAP/TSW_REGIONAL_INVENTORY_SRV_01

Entity Set KPISet

The following templates for evaluations, drill-downs, and tiles are provided.

Evaluations

The following evaluations are assigned to this KPI:

View

Evaluation

Evaluation ID: .E.1465900850825

Evaluation Description: KPI tile for Regional Inventory

Data Source

Parameter Value

OData Service /sap/opu/odata/SAP/TSW_REGIONAL_INVENTORY_SRV_01

Entity Set KPISet

Value Measure Alert

This is custom documentation. For more information, please visit the SAP Help Portal 11
 2/19/2022

Parameter Value

Semantic Object/Action RegionalInventory/Display

Scaling Factor Auto

Select Additional Measures Warning Information

Input Parameters and Filters

The KPI tile loads the data based on the lters set in the KPI con gurator. For the default shipped tile, the lters are not set and
the default variant if set inside the SAP Fiori app is used. In the optional lters section you can add the lters location, material,
and valuation type multiple times. Do not choose the other lters like base unit of measure, inventory type, horizon, and start
date multiple times. Set start date only when horizon lters Weekly, Fortnightly and Monthly are used. Use the format
YYYY/MM/DD.

The following tables show the input parameters, lters, and some precon gured example values. Use your own values where
required, according to the data in your backend system.

Input Parameters

Input Parameter Operator Example Value Explanation

Location EQ LOCARAS-Z4 Location Filter

Material EQ DIESEL_ULS_1 Material Filter

Valuation Type EQ TAX Valuation Type Filter

Base Unit of Measure EQ BBL Base Unit of Measure Filter

Inventory Type EQ Beginning Physical Inventory Inventory Type Filter

Horizon EQ Monthly Horizon Filter

Start Date EQ 2016/07/31 Start Date

Targets, Thresholds, and Trend

Parameter Value

KPI Goal Type Minimizing

Value Type Measure

Critical Alert

Warning Warning

Target Information

Tile

Title: Regional Inventory

Subtitle: View

Catalog: SAP_TC_OILDS_TSW_COMMON

Cache Duration: 0

This is custom documentation. For more information, please visit the SAP Help Portal 12
 2/19/2022

Measures Semantic Color

Alert Critical

Warning Warning

Information Neutral

Parameter Value

Tile Format Comparison Tile Multiple Measures

Semantic Object RegionalInventory

Action Display

Client Con guration Settings

1. Navigate to transaction in front end server /n/iwfnd/maint_service.

2. Add the service TSW_REGIONAL_INVENTORY_SRV_01.

3. Filter for the services SMART_BUSINESS_DESIGNTIME_SRV and SMART_BUSINESS_RUNTIME_SRV.

4. Maintain the system aliases of backend server with the user role as SAP_BR_TRANSP_SCHDLR_IOG.

Mass Change Events

Use
With this app you can view the events across all nominations. This app also provides you the option to mass edit events. Using
this app, you can also create a new event for an existing nomination as well as delete existing events.

This app is available for the role SAP_BR_TRANSP_SCHDLR_IOG (Transportation Scheduler (OG)).

Key Features
View events across all nominations

Mass edit events across nominations

Add new events for a nomination

Delete events for a nomination

Edit and update an event for a nomination

This app uses the C_OIJ06_MYEVENTSS1_MAIN, C_OIJ06_MYEVENTSS1_NOMITEM, C_OIJ06_MYEVENTSS1_OBJECT,

I_OIJ06_MYEVENTSS1_MAIN, I_OIJ06_MYEVENTSS1_NOMITEM, and I_OIJ06_MYEVENTSS1_OBJECT CDS view.

Component for Customer Incidents

IS-OIL-DS-TSW

More Information

This is custom documentation. For more information, please visit the SAP Help Portal 13
 2/19/2022
App Implementation: Mass Change Events

App Implementation: Mass Change Events

System Landscape Requirements

For information about the system requirements, see System Requirements.

 Note
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an
appropriate virus scanner in your SAP Fiori system landscape and de ne sufficiently restrictive scan pro les to prevent the
upload of malicious content.

For more information on virus scanning and scan pro les for apps, see section Virus Scanning in the SAP S/4HANA Security
Guide .

Tile Type for Launching App

The Mass Change Events transactional app is launched using SAP Fiori tile.

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F2233.

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

This is custom documentation. For more information, please visit the SAP Help Portal 14
 2/19/2022
You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Front-End Server : Activate OData Services

Component Technical Name

OData Service (Version Number) TSW_MYEVENTS_SRV(1)

OData Service (Version Number) for the Nomination Information TSW_MYNOMINATIONS_SRV_01(1)

page

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAP UI5 Application

Component Technical Name

SAP UI5 Application TSW_MYEVENTSS1

Generic Drill-Down Application /default_host/sap/bc/ui5_ui5/sap/sbrt_appss1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server: Activate ICF Service

Component Technical Name

ICF Service TSW_MYEVENTS_SRV

ICF Service for the Nomination Information page TSW_MYNOMINATIONS_SRV_01

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

This is custom documentation. For more information, please visit the SAP Help Portal 15
 2/19/2022
SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to Users

You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

TSW_MYEVENTS_SRV(1) You can use the example business catalog SAP_BR_TRANSP_SCHDLR_IOG

or your custom catalog to create the back-
end PFCG role.

You can use the authorization object

O_OIJ_NOM to create the PFCG role.

My Nomination Tickets
With this app you can view the nomination with ticket information.

Key Features
Filter the nomination worklist based on different nomination attributes like location, material, nomination number,
transport system, mode of transport and so on.

See ticket details corresponding to the nomination in the nomination object page.

Navigate to the TSW ticket app for a ticket from the nomination object page.

Create a ticket seamlessly using the Create Ticket option that navigates to the TSW Tickets app in create mode.

In addition, the app supports the following technical features and options:

Save as tile option so that you can save the details as a new tile.

You can export the nomination worklist to a spreadsheet.

This app uses the C_NominationLineItem and C_NominationTicketRecord CDS views.

Supported Device Types

This is custom documentation. For more information, please visit the SAP Help Portal 16
 2/19/2022
Desktop

Tablet

Smartphone

App Extensibility: My Nomination Tickets

You can extend the My Nomination Tickets app according to your business needs for different aspects. For this purpose, the
following extensibility options are available:

For key users and developers

Key users can extend the app in the Custom Fields and Logic app using the following context(s)

TSW Nomination Header: TSW_NOMINATIONHEADER

TSW Nomination Item: TSW_NOMINATIONITEM

For Key Users and Developers

You can add elds to the following UI elements using UI adaptations at runtime:

UI Element Business Context

Nomination Line Item TSW Nomination Header

Nomination Ticket Main TSW Nomination Header

Nomination Line Item TSW Nomination Item

Nomination Ticket Main TSW Nomination Item

For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.

CDS Views
Nomination Ticket Items
Technical Name C_NominationTicketRecord

View Type Dimensional

Release Status Released

Purpose
This CDS view is used to fetch Ticket item data against nomination data.

Structure
This is custom documentation. For more information, please visit the SAP Help Portal 17
 2/19/2022
This view is built on the following business objects:

OIJ_EL_TICKET_I

OIJ_EL_TICKET_H

OIJ_EL_ERROR_LOG

Measures and attributes

Some important measures and attributes are:

NominationTicketKey – Ticket Key

NominationTicketItem – Ticket Item

NominationTicketVersion – Ticket Version

NominationTicketPurpose - Purpose

TicketExternalNumber – Ticket External Number

NominationTicketExtNumber – External Position Number

NominationItemStatus – Nomination Item Status

TicketStatusColorCode – Ticket Criticality Code

LatestTicketStatus – Ticket Item Status

TicketCreatedByUser – Created By

TicketCreationDate – Date on Which Record Was Created

NominationDoc – Nomination Key

NominationDocItem – Nomination Item

Nomination Line Item

Technical Name C_NominationLineItem

View Type Dimensional

Release Status Released

Purpose
This CDS view is used to fetch Nomination header and item data along with the last ticket key & status if there was a ticket
created against the nomination.

Structure
The following are the list of tables which are used in this CDS:

OIJNOMH

OIJNOMI

OIJ_EL_TICKET_I

This is custom documentation. For more information, please visit the SAP Help Portal 18
 2/19/2022
Measures and attributes

Some important measures and attributes are:

NominationDoc – Nomination Key

NominationDocItem – Nomination Item

NominationTicketVersion – Nomination Ticket Version

NominationTicketKey – Last Ticket Key

NominationExtNumber – Nomination Number

NominationTicketPurpose - Nomination Ticket Purpose

TicketStatusColorCode - Ticket Criticality Code

LatestTicketStatus - Last Ticket Status

NominationScheduleDate - Scheduled Date

NominationCreatedByUser - Nomination Created By

NominationCreationDate - Nomination Created On

NominationChangedDate - Nomination Changed On

LastChangedByUser - Nomination Changed By

LocationId - Location

LocationName - Location Name

DemandMaterial - Demand Material

MaterialDesc - Material Name

TicketItemStatus - Status

ScheduledQuantityUnit - UoM

NumberOfTickets - Number of Tickets

ActualScheduledQuantityUnit - Actual UoM

NominationScheduleType - Scheduled Type

NominationType - Nomination Type

TransportSystem - Transport System

NominationReferenceDocType - Ref. Doc. Indicator

VehicleIdenti er - Transport Distribution Vehicle Identi er

VehicleId - Transport Distribution Vehicle Number

NominationCreationTime - Creation Time

InTransitPlant - In-Transit Plant

NominationReferenceDocItem - Ref. Doc. Item

NominationReferenceDocument - Document Number

This is custom documentation. For more information, please visit the SAP Help Portal 19
 2/19/2022
NominationShipper - Shipper

NominationCarrier - Carrier

ValuationTypeDestination - Valuation Type Destination

ValuationTypeOrigin - Valuation Type Origin

LocationPartner - Location Partner

TransportationPlanningPoint - Transportation Planning Point

InTransitStorageLocation - InTransit Storage Location

NominationPipelineCycleID - Cycle ID

BatchDestinationLocation - Batch Destination

BatchOriginLocation - Batch Origin

BusinessType - Business Type

NominationIsBlocked - Blocking Indicator

NominationIsMarkedForDeletion - Deletion Indicator

NominationItemStatus - Item Status

NominationItemSubStatus - Item Substatus

ContractPartner - Contract Partner

ConsigneePartner - Consignee Partner

IsImportExportPartner - Import/Export Partner Indicator

ImportExportPartner - Import/Export Partner

NominationInspector - Inspector

IsNominationWorklistEntry - Worklist Entry Indicator

QuickCon rm - Quick Con rmation

ScheduledBatchStartDateTime - Scheduled Start Date

ScheduledBatchEndDateTime - Scheduled End Date

BulkShipmentType - Bulk Shipment Type

NominationModeOfTransport - Mode of Transport

NominationUnitOfMeasure - Header UoM

NominationItemIsComplete - Nomination Item Complete Flag

NominationIsIncomplete - Incompletion Flag

NominationRefDocType - Ref. Doc. Type

Attributes

ScheduledQuantity - Scheduled Quantity

ActualScheduledQuantity - Actual Quantity

This is custom documentation. For more information, please visit the SAP Help Portal 20
 2/19/2022

TSW Tickets
With this app you can work on the nomination tickets. You can create, display, edit, delete, actualize, corrupt and reverse a
ticket.

Key Features
You can use the ticket header worklist to lter based on different attributes like ticket key, nomination key, ticket
purpose, ticket version, ticket type, ticket status and so on.

You can see the ticket item details corresponding to the ticket header in the ticket object page.

You can see the ticket item detailed information in the ticket item object page.

You can create, display, edit, delete, actualize, corrupt, and reverse a ticket.

You can navigate to My Nomination app on clicking the nomination number.

In addition, the app supports the following technical features and options:

Draft capability which allows you to save incomplete work as draft and resume later. Device switch is also supported; you
can resume the work using a different devices. For example, you can save your incomplete work using a tablet and then
resume work using the desktop.

You can save the details as a new tile using the save as tile option.

You can export the ticket header and item worklist to a spreadsheet.

This app uses the C_TICKETHEADTP, C_TicketItemTP , C_TICKETADDITIONALQTYTP and C_TICKETADDITIONALPARAMTP CDS
view.

Supported Device Types

Desktop

Tablet

Smartphone

App Extensibility: TSW Tickets

You can extend the TSW Tickets app according to your business needs for different aspects. For this purpose, the following
extensibility options are available:

For developers

Business Add-Ins (BAdIs)

For key users

Key users can extend the app in the Custom Fields and Logic app using the following context(s)

TSW Ticket Header: TSW_TICKETHEADER

TSW Ticket Item: TSW_TICKETITEM

For Key Users

This is custom documentation. For more information, please visit the SAP Help Portal 21
 2/19/2022
You can add elds to the following UI elements using UI adaptations at runtime:

UI Element Business Context

Ticket Header TSW Ticket Header

Ticket Items TSW Ticket Item

For Developers

Further Extensibility Entities

Business Add-Ins (BAdIs)

The following BAdI is available for extensibility purposes:

BAdI: Extend Fields in TSW Tickets (BADI_OIJ07_TICKET_ADD_FIELDS)

You can use this BAdI to extend elds in the backend for the TSW Tickets App.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.

CDS Views
Ticket UoM Parameters
Technical Name C_TicketAdditionalParamTP

View Type Dimensional

Release Status Released

Purpose
This CDS view is used to fetch Ticket Item’s additional parameters’ data.

Structure
The following are the list of tables which are used in this CDS:

OIJ_EL_TKT_I_O1

Measures and attributes

Some important measures are:

NominationTicketKey – Ticket Key

NominationTicketItem – Ticket Item

NominationTicketVersion – Ticket Version

This is custom documentation. For more information, please visit the SAP Help Portal 22
 2/19/2022
UnitOfMeasureParameter – Unit of Measure Parameter

NominationDoc – Nomination Key

NominationDocItem – Nomination Item

NominationTicketPurpose - Purpose

AdditionalQuantityIsMarked – Quantity is Marked

UnitOfMeasureParameterDesc – Unit of Measure Description

AdditionalUnitOfMeasure – Additional Unit of Measure

OutputParameterText – Parameter Text

IsTicketParameterEnabled – Ticket Parameter Enabled Flag

IsQuantityEnabled – Quantity Enabled Flag

IsTicketQuantityEnabled – Ticket Quantity Enabled Flag

TicketUnitOfMeasure – Ticket Unit of Measure

IsTicketUnitOfMeasureEnabled – Ticket Unit of Measure Enabled Flag

OilPhysParamUomFieldName – Physical Parameter Unit of Measure Name

UnitOfMeasureParameterSequence – Unit of Measure Parameter Sequence

OilPhysParamFieldName – Physical Parameter Name

OilPhysParamValue – Physical Parameter Value

Attributes

TicketAdditionalQuantity – Ticket Additional Quantity

Ticket Item Additional Quantities

Technical Name C_TicketAdditionalQtyTP

View Type Dimensional

Release Status Released

Purpose
This CDS view is used to fetch Ticket Item’s additional quantities data.

Structure
The following are the list of tables which are used in this CDS:

OIJ_EL_TKT_I_O2

Measures and attributes

Some important measures and attributes are:

This is custom documentation. For more information, please visit the SAP Help Portal 23
 2/19/2022
NominationTicketKey – Ticket Key

NominationTicketItem – Ticket Item

NominationTicketVersion – Ticket Version

TicketUnitOfMeasure – Unit of Measure

NominationDoc – Nomination Key

NominationDocItem – Nomination Item

NominationTicketPurpose - Purpose

QuantityIsMarked – Quantity Marked

IsTicketQuantityEnabled – Quantity Enabled Indicator

IsTicketUnitOfMeasureEnabled- Unit of Measure Enabled Indicator

IsQuantityEnabled – Quantity Enabled Indicator

Attributes

TicketAdditionalQuantity – Ticket Additional Quantity

Ticket Header
Technical Name C_TicketHeadTP

View Type Dimensional

Release Status Released

Purpose
This CDS view is used to fetch Ticket header data.

Structure
The following are the list of tables which are used in this CDS:

OIJ_EL_TICKET_H

OIJ_EL_TICKET_I

OIJ_EL_ERROR_LOG

Measures and attributes

Some important measures and attributes are:

NominationTicketKey – Ticket Key

NominationTicketVersion – Ticket Version

NominationTicketPurpose – Ticket Purpose

TicketExternalNumber – External Number

This is custom documentation. For more information, please visit the SAP Help Portal 24
 2/19/2022
NominationTicketStatus – Ticket Status

NominationTicketStatusCode – Ticket Status Code

TicketStatusColorCode – Ticket Criticality Code

NominationTicketType – Ticket Type

NominationDoc – Nomination Key

TransportSystem – Transport System

TransportationPlanningPoint – Transportation Planning Point

NominationExtNumber – Nomination Number

TicketCreationDate – Created On

TicketCreatedByUser – Created By

TicketChangedDate – Changed On

TicketChangedByUser – Changed By

TicketApprovalStatus – Approval Status

NominationCarrier - Carrier

ConsigneePartner – Consignee Partner

NominationInspector - Inspector

NominationShipper- Shipper

TicketSupplier- Supplier

Trader – Trader

Ticket Items
Technical Name C_TicketItemTP

View Type Dimensional

Release Status Released

Purpose
This CDS view is used to fetch Ticket item data.

Structure
The following are the list of tables which are used in this CDS:

OIJ_EL_TICKET_H

OIJ_EL_TICKET_I

OIJNOMH

OIJNOMI

This is custom documentation. For more information, please visit the SAP Help Portal 25
 2/19/2022
OIJ_EL_ERROR_LOG

Measures and attributes

Some important measures and attributes are:

NominationTicketKey – Ticket Key

NominationTicketItem – Ticket Item

NominationTicketVersion – Ticket Version

NominationTicketPurpose - Purpose

TicketExternalNumber – Ticket External Number

TicketStatusColorCode – Ticket Criticality Code

LatestTicketStatus –Ticket Item Status

NominationTicketStatus – Ticket Status

NominationDoc – Nomination Key

NominationDocItem – Nomination Item

NominationExtNumber – Nominaton Number

NominationScheduleType – Scheduled Type

NominationType – Nomination Type

DemandMaterial – Demand Material

LocationName – Location Name

TransportSystem – Transport System

NominationTicketType – Ticket Type

ScheduledMaterial – Scheduled Material

BaseUnit - UoM

LocationId – Location ID

TicketDocumentPostingDate – Posting Date

TicketCorruptMode – Corrupt Mode Flag

TicketReverseMode – Reverse Mode Flag

TicketCorrectionMode – Correction Mode Flag

TypeOfMovement – Type of Movement

QuantityStartDateTime – Quantity Start Date/Time

QuantityEndDateTime – Quantity End Date/Time

GeneralMeterNumber – Meter Number

OpenMeterDateTime – Meter Open Date/Time

CloseMeterDateTime – Meter Close Date/Time

This is custom documentation. For more information, please visit the SAP Help Portal 26
 2/19/2022
StopMeterUnitOfMeasure – Unit of Measure

TankSequenceNumber – Tank Sequence Number

StorageObjectSegmentNumber – Storage Object

GaugeTimeZone – Gauge Timezone

OpenTankDipDateTime – Tank Open Dip Date/Time

CloseTankDipDateTime – Tank Close Dip Date/Time

IsNominationItemClosed – Closed Nomination Indicator

TicketCreatedByUser – Created By

TicketCreationTimeStmp – Created On

TicketChangedByUser – Changed By

NominationItemStatus – Nomination Item Status

NominationItemSubStatus – Nomination Item Sub Status

TicketChangedDate – Changed On

NominationEventDate – Event Date

StopGaugeUnitOfMeasure – Gauge Unit of Measure

BulkShipmentType – Shipment Type

OriginPlant – Origin Plant

OriginStorageLocation – Origin Storage Location

DestinationPlant – Destination Plant

Descriptive text on the important measures & attributes

Attributes

ScheduledQuantity – Scheduled Quantity

MeterOpenQuantity – Meter Open Quantity

EndCounterMeterReading – Meter End Quantity

StopMeterCalculationQuantity – Meter Calculated Quantity

GaugeOpenDipReading – Gauge Open Dip Reading

GaugeCloseDipReading – Gauge Close Dip Reading

CalculcatedGaugeQuantity – Gauge Calculated Quantity

Actual vs Planned Nominations

With this app you can view the actual, current and planned nomination quantities in graphical format.

Key Features
You can perform yearly, monthly, weekly and daily analysis of actual and planned nominations in graphical format like
column chart, line chart and tabular view.
This is custom documentation. For more information, please visit the SAP Help Portal 27
 2/19/2022
You can lter based on different nomination attributes like location, material, nomination number, transport
system,mode of transport and so on.

You can navigate to My Nominations app. Nomination can be selected from daily analysis and the selected nominations
can be opened in the My Nominations app.

Using the smart business KPI tile you can display the daily current nomination quantity for the past one week from the
current date.

In addition, the app supports the following technical features and options:

Save as tile option so that you can save the details as a new tile.

This app uses the C_NOMINATIONPLANACTUAL and C_NOMINATIONPLANACTUALKPI CDS views.

Supported Device Types

Desktop

Tablet

Smartphone

CDS Views
Actual vs Planned Nomination Fields
Technical Name C_NominationPlanActual

View Type Consumption

Release Status Released

Purpose
This CDS view is used to fetch Actual vs Planned Nomination data.

Structure
The following are the list of tables which are used in this CDS:

OIJNOMH

OIJNOMI

OIJNOMH_VERS

OIJNOMI_VERS

Measures and attributes

Some important measures and attributes are:

NominationDoc – Nomination Key

NominationDocItem- Nomination Key Item

This is custom documentation. For more information, please visit the SAP Help Portal 28
 2/19/2022
TransportSystem – Transport System

LocationId – Location ID

NominationExtNumber – Nomination Number

NominationCurrentQuantity – Scheduled quantity

NominationActualQuantity - Actual quantity

NominationPlannedQuantity - Planned quantity

ScheduledQuantityUnit – Scheduled UoM

ActualQuantityUnit – Actual UoM

PlannedQuantityUnit – Planned UoM

NominationScheduleDate – Scheduled date

NominationCalendarYear – Calendar year

NominationCalendarMonth – Calendar month

NominationCalendarWeek – Calendar week

NominationPipelineCycleID – Cycle ID

NominationCarrier - Carrier

ContractPartner – Contract Partner

NominationVersion - Version

NominationShipper- Shipper

ScheduledMaterial – Material

NominationScheduleType - Scheduled type

VehicleId – Vehicle Number

IsReferenceDocument – Reference document number

ScheduledBatchStartDateTime – Scheduled start date time

ScheduledBatchEndDateTime – Scheduled end date time

Actual vs Planned Nomination KPI

Technical Name C_NominationPlanActualKPI

View Type Consumption

Release Status Released

Purpose
This CDS view is used to fetch the tile Actual vs Planned Nomination data.

Structure

This is custom documentation. For more information, please visit the SAP Help Portal 29
 2/19/2022
The following are the list of tables which are used in this CDS:

C_NominationPlanActual

Measures and attributes

Some important measures and attributes are:

NominationCurrentQuantity – Scheduled quantity

NominationActualQuantity - Actual quantity

NominationPlannedQuantity - Planned quantity

NominationScheduleDate – Scheduled date

Supply Chain Visualization

With this app you can visualize the shipments that are scheduled between various locations (own stock holding and 3P
locations) on the map as path between the locations. TSW carrier nomination is the exclusively source of shipment. Based on
the speci c company codes that you are authorized to, you can visualize all the shipments that pertain to the selection criteria
that is entered (for example, a date range or product group and so on). Further you can view the location details in terms of
physical measured and projected inventory and also view product price and future price of all materials assigned to locations.
The app also allows you to view the alerts on shipments as well as location inventories, and lets you x the shipment alerts by
adjusting the scheduled quantities, date and time. You can visualize vehicle delay impact using Gantt chart and this also
provides an option to adjust the schedule by adjusting the date and time. You can also view global simulations of nominations
for a given time horizon.

This app also provides location level information like, Berth Scheduling and Silo Tank details for the selected location. In berth
scheduling, it shows all nominations which are assigned to a berth on berth planning board and offers berth rescheduling
functionality. In silo tank, you can view the aggregation gures of last inventories of material assigned to multiple tanks and
utilization histogram for tanks.

In addition to that, this app also support visualizing Transshipment in Gantt chart view and helps to predict the shipment
obstacles due to weather forecast conditions and send noti cation to intended business partners and terminals.

Key Features
Visualize location and shipments on the Map.

Provides last physical and projected inventory stock by valuation type.

Visualize multiple inventory graphs for heal, capacity, target and safety determined from silo tanks, material-location
assignment as time constraints static values.

Simulates shipments scheduled for a vehicle with Gantt chart and allows to adjust the dates.

Displays alerts on shipments and allows you to adjust shipment alerts by adjusting the quantities and dates.

Displays shipment alerts for plan vs actual as per con guration of events for actual per MOT and allowed tolerance.

Displays inventory alerts on locations based on the alerts con gured in inventory planning workbench (IPW).

Allows you to save variants.

Personalize and save it as a new tile.

View the total number of shipment alerts on the tile, for the saved default variant.

This is custom documentation. For more information, please visit the SAP Help Portal 30
 2/19/2022
Displays shipments along routes with different colors based on different modes of transport.

Build route from route information or from drop date/time sequence

Locate the shipment.

Displays shipment and location details.

View the shipment details in the map and table format.

Download the open shipments into an excel sheet in the tabular view

Berth Scheduling using berth planning board and display plan, actual laytime and potential demurrage.

View the nomination line items that are pegged with Berth Scheduling but not assigned to any berth. Re-berth
unassigned nomination to actual berth.

Silo tank with recent physical inventory details with tank capacity and utilization details.

Weather information and forecast help to predict the obstacles impacting the supply chain execution.

Helps to visualize transshipment delay impact.

Notify the impacted shipments to intended business partners with user comments through mail.

Helps to visualize various product price at location level (market and rack price).

Helps to visualize global simulations on geo map.

You can use the SAP analytics cloud (SAC) to report deviations in planned versus actual shipments.

View the open contracts valid for any location/material combination. Use the menu option on any location to view all the
valid materials. You can select any material to view the valid list of open contracts. The open quantities available for each
contract are displayed as a graphical representation for quantity schedule.

In addition to the current aggregated quantity, the graph also displays all the other quantities maintained for different
valuation types for a material. You can visualize the same with different colors to depict the various valuation types.

View the shipment costs ( load cost and discharge cost) with the complete cost details and the location speci c costs
are highlighted.

View a nomination created for rebrand scenario with the locations having inventory details of the demand material. The
demand material is different from the schedule material in a rebrand scenario.

View the Intank rebrand at load and discharge locations on the IPW graph. You can select the demand or schedule
material to view in the graph accordingly. On selecting the intank option in the graph, the locations are zoomed for a
valid Intank rebrand scenario.

View the inventory details at a location for a non scheduled materials in a different tab.The current day inventory,
projected inventory are shown for all the such materials.

View both IPW simulation of movements and scheduled nominations by choosing the option Yes from the simulation
lter.

In addition, the app supports the following technical features and options:

Supports con guration of any third-party map service provider URL to be loaded as the map in the application.

Con gure linkage between load and discharge movement scenario codes into a table.

Con gure the tolerance threshold for various event type per mode of transport for shipment alerting.

Con gure a pegging type linkage between load and discharge nomination items.

Con gure weather integration and other weather-related parameter into the table.
This is custom documentation. For more information, please visit the SAP Help Portal 31
 2/19/2022
Con gure your own pump phase and relevant event type for berth planning calendar.

Con gure tank shape for silo tank used to store the products.

Con guration is used to select the required elds in email noti cation to business partners.

This app uses the C_VisualNominations and C_VisualLocations CDS views.

Supported Device Types

Desktop

App Extensibility: Supply Chain Visualization

You can extend the Supply Chain Visualization app according to your business needs for different aspects. For this purpose, the
following extensibility options are available:

For Key Users and Developers

You can add elds to the following UI elements using UI adaptations at runtime:

UI Element Business Context

Shipments table Add columns to Shipments table (in Table View Mode)

Filters Add lters to the lter bar

Market Price table heading Add additional column headings to the table in Market Price view

Market Price table data Add additional column data to the table in Market Price view

Silo Tanks detail view form layout Add additional data to the form in detail view of Silo Tank Detail
view

Weather details table heading Add additional column headings to the table in Weather details
view

Weather details table data Add additional column data to the table in Weather details view

You can implement logic for the following Business Add-Ins (BAdIs):

Business Add-Ins (BAdIs) Business Context

OIJ07_GET_GEO_COORDINATES You can use this BAdI to change the service for obtaining geo
coordinates of locations in the map.

OIJ07_BERTH_SCHEDULING You can use this BAdI to change data fetched for Berth Scheduling

OIJ07_VISUAL_SHIPMENT_BADI You can use this BAdI to change or re determine the pegging logic
for Nominations

OIJ07_NOTIFICATION_SERVICE You can use this BAdI to change Noti cation Service data for
Nominations

OIJ07_COMMODITY_PRICE You can use this BAdI to add/ change data for Commodity price in
Shipment visualization

For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes.

This is custom documentation. For more information, please visit the SAP Help Portal 32
 2/19/2022
For more information about the extensibility app, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP
NetWeaver for SAP S/4HANA General Functions for Key Users Extensibility .

Key users can also make custom elds available in several apps including handing over data by using business scenarios.

For Developers
To add a custom elds to the app, for example, the extensibility entities listed below are available on the different software
layers. You have to extend each of these entities according to your speci c business needs:

UI Back End/ABAP

View Extension Point Design Time: Gateway Entity Design Time: CDS View Design Runtime
Time: Supercl
Extension Method
Include Be
(in DDIC Rede n
Structure)

Worklist extVisualizationViewAddTableFields TSW_VISUAL_SHIPMENT_SRV C_VISUALNOMINATIONS

Worklist extVisualizationFilterBarItems TSW_VISUAL_SHIPMENT_SRV C_VISUALNOMINATIONS

Worklist extHookAddModeTransport TSW_VISUAL_SHIPMENT_SRV C_VISUALNOMINATIONS

Worklist extHookAddFilterItems TSW_VISUAL_SHIPMENT_SRV C_VISUALNOMINATIONS

Berth extHookChangeTooltip TSW_VISUAL_SHIPMENT_SRV C_BERTHSCHEDULING

Shipment extVisualizationFlexiColShipmentDetails TSW_VISUAL_SHIPMENT_SRV C_VISUALNOMINATIONS

Details

Market extPriceViewAddTableFields TSW_VISUAL_SHIPMENT_SRV

price

Market extPriceViewAddTableData TSW_VISUAL_SHIPMENT_SRV

price

Silo tank extSiloTankAddFormField TSW_VISUAL_SHIPMENT_SRV C_TANKVISUALIZATION

detail

Weather extWeatherViewAddTableFields TSW_VISUAL_SHIPMENT_SRV

detail

Weather extWeatherViewAddTableData TSW_VISUAL_SHIPMENT_SRV

detail

Further Extensibility Entities

Extension Points

For visualization of shipments following extension points are available in the view:

View Extension Point Use

Worklist extVisualizationFilterBarItems Add lters to the lter bar in the Supply

Chain Visualization screen

Worklist extVisualizationViewAddTableFields Add elds in the Shipments Table (in Table

View mode)

This is custom documentation. For more information, please visit the SAP Help Portal 33
 2/19/2022

View Extension Point Use

Worklist extHookAddModeTransport Allows you to add additional colors to the

Modes of transport con gured for Legend

Worklist extHookAddFilterItems Allows to interpret the lter elds there by

letting you add more lters

Shipment details extVisualizationFlexiColShipmentDetails Add additional elds to the shipment

details in the end column of exible column
layout

For berth scheduling, the following extension points are available in the view:

View Extension Point Use

Berth extHookChangeTooltip Allows to add more information to the

Tooltip that displays Event start/end time
on Berth view

For tank visualization, the following extension points are available in the view:

View Extension Point Use

Silo tank detail extSiloTankAddFormField Add additional data to the form in detail
view of Silo Tank Detail view

For weather visualization, the following extension points are available in the view:

View Extension Point Use

Weather detail extWeatherViewAddTableFields Add additional elds to the table in table

view of Weather Details view

Weather detail extWeatherViewAddTableData Add additional data to the table in table

view of Weather Details view

For Market Price Visualization, the following extension points are available in the view:

View Extension Point Use

Market Price extPriceViewAddTableFields Add additional elds to the table in table

view of Market Price view

Market Price extPriceViewAddTableData Add additional data to the table in table

view of Market Price view

If there are additional elds available in the OData service, you can display these elds on the UI. For more information about
extension points, see Extend SAP Fiori Apps.

UI Controller Hooks

To plug in and execute custom code to the map view, the following hooks are available in the controller code:

Controller Hook Use

This is custom documentation. For more information, please visit the SAP Help Portal 34
 2/19/2022

Controller Hook Use

Worklist extHookAddFilterItems Allows to interpret the lter elds for adding more
lters

Worklist extHookAddModeTransport Add colors to the custom modes of transport (in

Legend)

To plug in and execute custom code to the berth view, the following hooks are available in the controller code:

Controller Hook Use

Berth extHookChangeTooltip Allows to add more information to the

Tooltip

If there are additional UI controller hooks available in the controller code, you can extend the UI controller code. For more
information about UI controller hooks, see Extend SAP Fiori Apps.

For more information about hiding UI controls, see Extend SAP Fiori Apps.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.

App Con guration: Supply Chain Visualization

Business Context
Supply Chain Visualization application displays a map control as its pivotal feature. In order for the map control to be used
efficiently a map provider is important. You can con gure the map provider of your choice out of the list providers available in
the market. In Customizing, you can overwrite the map server default URLs assigned to the SAP delivered map products. The
map product URLs contain a token, app ID, or something equivalent, which identi es the service consumer at the map provider.
For productive use you need to license the map product of your choice. With the license agreement you get your own token. In
order to use this you have to overwrite the default URLs. The application holds de nitions for the behavior and appearance of
the navigation and toolbar control.

Prerequisites
You must do the following to add the VBI service in the frontend system:

1. Enter transaction /n/iwfnd/maint_services.

2. Click on Add Service. Find *vbi* with the corresponding System Alias (to the backend system).

3. Select VBI_APPL_DEF2_SRV and choose Add Selected Services

4. Select local object in the next dialog and choose Ok.

The system displays the message Metadata was loaded successfully. Make sure the system alias is added to
the corresponding backend system.

Settings
To overwrite the URL for third-party Map Provider -Settings do the following:

This is custom documentation. For more information, please visit the SAP Help Portal 35
 2/19/2022
1. In Customizing under SAP NetWeaver -> UI technologies -> SAP Visual Business execute Overwrite
Map Server default URLs

2. Select any work area from the input help. The default that is delivered is HERE_NORMAL. Choose ok.

3. Overwrite the URL with the corresponding URL. If you want to add more entries with different server ids, then choose
New Entries.

To add more map layer stacks:

1. In Customizing under SAP NetWeaver -> UI technologies -> SAP Visual Business execute Maintain
Application De nitions.

2. Expand the folder structure Applications and select Shipment Visualization. Choose Map Layer Stack Assignments. You
can edit and add more assignments to the application.

3. The Map Layer Stacks displays the available map layers and you can add more map layers as per requirement.

4. In order to check the properties associated with each Layer, you can select one of them and choose Map Product
Assignments.It displays the default con gurations associated with that layer and you can edit the same.

This con gures the required URLs for the map provider for the Supply Chain Visualization application.

Related Links

https://wiki.scn.sap.com/wiki/display/SVE/Con guring+or+changing+a+map+provider+in+SAP+Visual+Business

CDS Views
Supply Chain Visualization
CDS Name Description DDL SQL View Name

C_BERTHSCHEDULING Berth Scheduling Information CBERTHSCHEDULING

C_NOMINATIONNUMBERVH Visual Nomination Number CVISUALNOMNUM

C_NOMINATIONSTATUSVH Visual Nomination Status CVISUALNOMSTAT

C_SILOTANKDIPANALYSIS Silo Tank Dip height analysis across several CTANKANALYSIS

days

C_TANKVISUALIZATION Consumption of Tank Visualization Details CTANKVISU

C_VISUALLOCATIONS Location Master Data CVISUALLOC

C_VISUALLOCATIONVH Visual Location Value help CVISULOCATIONVH

C_VISUALMATERIALGROUPVH Visual Material Group Value Help VISUMATGROUP

C_VISUALMODEOFTRANSPORTVH Visual Mode Of Transport CVISUMODEOFTRANS

C_VISUALNOMINATIONSTATUSVH Visual Nomination Status CVISUNOMSTAT

C_VISUALNOMINATIONS Visual Nominations CVISUALNOM

C_VISUALNOMINATIONTYPEVH Visual Nomination Type CVISUNOMTYPE

C_VISUALPRODUCTHIERARCHYVH Visual Hierarchy CPRODHIER

C_VISUALPRODUCTIDVH Visual Product ID CVISUPRODID

This is custom documentation. For more information, please visit the SAP Help Portal 36
 2/19/2022

CDS Name Description DDL SQL View Name

C_VISUALSIMULATION IPW Simulation in Visualization CVISUSIM

C_VISUALTRANSPORTSYSTEMVH Visual Transport System CVISUTRANSPORT

C_VISUALVEHICLENUMBERVH Visual Vehicle Number Value Help CVISUVEHICLENUM

Prerequisites
This view is only available if business function LOG_COMMODITY_TRANSPORT_MGMT_8 is activated.

Structure
Refer to DDL SQL view name from above table for structure related information.

Visual Nominations
Technical Name I_VisualNominations

View Type Composite

Release Status Released

Purpose
The consumption view C_VisualNominations of this view is used in the project TSW_VISUAL_SHIPMENT (SAP Gateway
Service).

C_VisualNominations of this view provides the relevant metadata and entity sets as its used as SADL-based OData
services.

This view selects data needed for shipment visualization application like Material, Customer, Vendor, Address, Location,
Mode of transport, Nomination, Vehicle and so on.

Prerequisites
This view is only available if Business Function LOG_COMMODITY_TRANSPORT_MGMT_8 is activated.

This view has access control I_NominationAnalysisPath check which has OIJ_NOMTYP, OIJ_TSYST, OIJ_SHPR, OIJ_LOC as
authorization objects.

Structure
Refer to the SQL view name IVISUALNOM

Location Master Data

Technical Name I_VisualLocations

View Type Basic

Release Status Released

This is custom documentation. For more information, please visit the SAP Help Portal 37
 2/19/2022

Purpose
This view is used for fetching location details from different tables for the Shipment Visualization application.

The consumption view C_VisualLocations of this view is used in the project TSW_VISUAL_SHIPMENT. (SAP Gateway
Service).

The consumption view C_VisualLocations of this view provides the relevant metadata and entity sets as its used as
SADL-based OData services.

This view selects the data from Plants/Branches, Partner Roles, Physical Location, Address data, Region Key , Country
Names.

Prerequisites
This view is only available if Business Function LOG_COMMODITY_TRANSPORT_MGMT_8 is activated.

Structure
This view has the below structure:

Field Name Description

MANDT Client

COMPANYCODE Company Code

PLANT Plant

LOCATIONID Location ID

BUSINESSPARTNERROLETYPE OIL-TSW: Role partner type

BUSINESSENTITYLOCATIONNAME Internal name eld

LOCATIONTYPE Business Location Type (IS-Oil MRN)

ADDRESSNUMBER Address number

CITYNAME City

COUNTRYNAME Country Name (Max. 50 Characters)

REGION Description

POSTALCODE City Postal Code

LATITUDE Generated Column for Functions, Literals

LONGITUDE Generated Column for Functions, Literals

Plan vs Actual Shipments

Technical Name I_PlanVsActualNomination

View Type Composite

Release Status Released

This is custom documentation. For more information, please visit the SAP Help Portal 38
 2/19/2022

Purpose
The consumption view C_PlanVsActualNomination of this view is used in the project TSW_SHIPMENT_PLAN_VS_ACTUAL
(SAP Gateway Service).

C_PlanVsActualNomination of this view provides the relevant metadata and entity sets as its used as SADL-based
OData services.

This view selects data for SAP Analytics Cloud where Shipment KPI’s for TSW nomination are visualized.

Prerequisites
This view contains the access control I_PlanVsActualNomination check which has OIJ_NOMTYP, OIJ_TSYST,
OIJ_SHPR, OIJ_LOC as authorization objects.

Structure
Refer to this SQL view name IPLANVSACTUAL for structure details.

Constraints
This view does not support analytics.

Visual Analysis
Technical Name I_VisualAnalysis

View Type Composite

Release Status Released

Purpose
This view is used for fetching data from different tables for the Planned Vs Actual Shipment application.

The consumption view C_KPIOverall of this view is used in the project TSW_VISUAL_ANALYSIS. (SAP Gateway
Service).

Prerequisites
This view is only available if Business Function LOG_COMMODITY_TRANSPORT_MGMT_8 is activated.

This view has access control I_NominationAnalysisPath check which has OIJ_NOMTYP, OIJ_TSYST, OIJ_SHPR, OIJ_LOC as
authorization objects.

Structure
This view has the below structure:

Fields Description

MANDT Client

NOMINATIONDOC Nomination (technical) Key

NOMINATIONDOCITEM Nomination Key Item

This is custom documentation. For more information, please visit the SAP Help Portal 39
 2/19/2022

Fields Description

NOMINATIONDOCDISCHARGEITEM Char Column

ISNOMINATIONDOCITEM Character Field Length = 10

ISLOAD Version Number Component

SCHEDULEDMATERIAL Scheduled material

COMPANYCODE Company Code

NOMINATIONCARRIER Transport system Carrier

NOMINATIONMODEOFTRANSPORT Mode of transport

MODEOFTRANSPORTTEXT Description

LOCATIONID Location ID

VEHICLEID TD Vehicle Number

SHIPPINGROUTE Route

DESTINATIONLOCATION Char Column

MATERIALGROUP Material Group

TRANSPORTSYSTEM Transport system

NOMINATIONSCHEDULETYPE Schedule type

ISBOOKEDTRANSPORTSYSTEM Book TS indicator

ISREFERENCEDOCUMENT Reference document indicator (PSX)

NOMINATIONREFERENCEDOCUMENT Nomination Reference Document

NOMINATIONITEMSTATUS Nomination Item status

NOMINATIONSCHEDULEDATE Scheduled date

NOMINATIONCALENDARWEEK Year Week

NOMINATIONCALENDARMONTH Year Month

NOMINATIONCALENDARYEAR Calendar Year

SCHEDULEDBATCHSTARTDATETIME Scheduled / Acceptance / Pipe Batch Start Timestamp

ACTUALDISCHARGEQUANTITY Quantity Column

TRANSITTIME Decimal Column

ACTUALSTARTDATEFROM TD - Actual Start Date of Event (From)

ACTUALSTARTTIMEFROM TD - Actual Start Time of Event (From)

DISCHARGEBATCHSTARTDATETIME Generated Column for Functions, Literals, ...

DISCHARGEDATE Date Column

DISCHARGETIME Time Column

DELTALOADDISCHARGETIME Decimal Column

NOMINATIONOVERALLLOAD Decimal Column

This is custom documentation. For more information, please visit the SAP Help Portal 40
 2/19/2022

Fields Description

NOMINATIONOVRLDISCHARGE Decimal Column

SCHEDULEDQUANTITY Scheduled qty

SCHEDULEDQUANTITYUNIT Scheduled UoM

ACTUALSCHEDULEDQUANTITY Actual posted quantity

ACTUALSCHEDULEDQUANTITYUNIT Actual posted quantity Unit of Measure

DELTALOADQUANTITY Quantity Column

DELTADISCHARGEQUANTITY Quantity Column

NOMINATIONDOCITMINDICATOR Version Number Component

DELTATEXT Char 15

Nomination Items View

Technical Name I_NominationItemDetails

View Type Basic

Release Status Released

Purpose
This CDS view is used:

To fetch header (Table: oijnomh) and Item (Table: oijnomi) elds for Planned vs Actual Shipment application.

To select only records where nomination header or item is not deleted and nomination header status is Closed and
nomination item status is Complete with nomination item complete indicator as Yes.

In I_PlanVsActualNomination.

Structure
Refer to this SQL view name INOMITEMDET for structure details.

Constraints
This view does not support analytics.

OData Service
Plan vs Actual Shipments OData Service Overview

Overview
This service is used to expose TSW nomination data for plan vs actual shipments for visualization. It also exposes data to SAP
Analytics Cloud (SAC) that is used to perform analytics on this exposed data.

This is custom documentation. For more information, please visit the SAP Help Portal 41
 2/19/2022
OData Version: 2.0

Root URI:/sap/opu/odata/SAP/TSW_SHIPMENT_PLAN_VS_ACTUAL_SRV/

Permissions: NA

Entity Data Model

Technical Model Name: TSW_SHIPMENT_PLAN_VS_ACTUAL_MDL

Model Version:1

Model Provider Class: CL_PLAN_VS_ACTUAL_MPC_EXT

Description: Shipment Plan Vs Actual

CDS-Entity Exposures: C_PlanVsActualNomination

Entity Type: C_PlanVsActualNominationType

Entity Set: C_PlanVsActualNomination

Service Metadata URI: HTTP: /sap/opu/odata/SAP/TSW_SHIPMENT_PLAN_VS_ACTUAL_SRV/$metadata

Supply Chain Visualization Service Overview

Overview
This service is used to expose TSW nomination data for for visualization.

OData Version: 2.0

Root URI:/sap/opu/odata/SAP/TSW_VISUAL_SHIPMENT_SRV/

Permissions: NA

Entity Data Model

Description: Service for TSW Visualization

Service Metadata URI: /sap/opu/odata/SAP/TSW_VISUAL_SHIPMENT_SRV/$metadata

Refer SEGW project for additional information on entity sets, entity types, and so on.

Planned vs Actual Shipments

With this app you can view the below following charts.

Planned Vs Actual Scheduled Date and Transit Time - Overall

Planned Vs Actual Scheduled Date and Transit Time - Carrier

Planned Vs Actual Scheduled Date and Transit Time - Mode of Transport

This is custom documentation. For more information, please visit the SAP Help Portal 42
 2/19/2022
Planned Vs Actual Scheduled Date and Transit Time – Mode of Transport vs Carrier

Planned Vs Actual Quantity - Overall

Planned Vs Actual Quantity - Location Load

Planned Vs Actual Quantity - Location Discharge

Planned Vs Actual Transit Time - Overall

Planned Vs Actual Transit Time - Carrier

Planned Vs Actual Transit Time - Mode of Transport

Planned Vs Actual Transit Time – Mode of Transport vs Carrier

Key Features
Yearly, monthly, company code, location, transport system, material group analysis of planned vs actual shipments in
graphical format like column chart, line chart and tabular view.

You can lter based on different nomination attributes like yearly, monthly, company code, location, transport system,
material group.

You can use the smart business KPI tile to display the overall load/discharge time, overall load/discharge quantity and
overall transit time.

This app uses the CKPIOVERALL and CVISUALOVERALL CDS view.

Supported Device Types

Desktop

Tablet

Smartphone

Mobile Ticket Data Capture

With this app you can capture ticket data and display ticket details.

Key Features
You can download necessary nomination item details to a mobile device. This includes product, From/to location, Vehicle,
Date, Schedule/Actualized/In-process quantities etc.

The date and number format as per the device settings.

The ticket data can be captured with minimal details, such as the quantity and load end date

Physical parameters are downloaded for each nomination item, this can be changed as per what is recorded at time of
loading. Dynamic validation of the parameters based on the input values.

The in-process quantity is dynamically recalculated when the nomination schedule quantity is changed.

The quantity entered in base UoM or additional UoM is validated with converted quantity.

Additional quantities if available can also be keyed in along with other loading details, though these are not
calculated.Validation of additional quantity that is out of tolerance.

This is custom documentation. For more information, please visit the SAP Help Portal 43
 2/19/2022
Offline features help in capturing Ticket details even as the device is offline, save and push the data to the backend
system once it is online

Fields visible in worklist page can be personalized as required.Any settings with personalization can be saved so that you
can use the same settings across devices when logged in.

The ticket event details can also be captured when offline.

Multiple tickets can be created when device is offline or online for a single nomination item. Also a nomination item with
multiple tickets created could also be displayed in the device app.

This app uses the C_NOMINATIONTICKETDETAIL CDS view.

Supported Device Types

Tablet

Smartphone

App Implementation: Mobile Ticket Data Capture

System Landscape Requirements

For information about the system requirements, see System Requirements.

Implementation Tasks
The following section list tasks that have to be performed to implement this app.

To enable the Hybrid Application Toolkit, see https://help.sap.com/viewer/8e5c63b6470a4255861c259f3b2d9b41/Cloud/en-

US/ff3a6540704040afba7ee5e5a43b14f2.html

When the BSP app is loaded into Web IDE, follow the steps listed below:

1. Load the application into Web IDE and mobile enable the app.Right-click on the project, choose Mobile Enable as Hybrid
Mobile Project . A mobile folder appears under the project.

2. Navigate to webapp Mobile under the project.

Copy all the les from webapp mobile (source) to mobile folder(destination) present just under the project.

3. While copying the les from source to destination, rename the les and remove the -1909 in destination folders.

Uncomment the contents of the les copied from source to destination folders.

4. To build the app using mobile services, see

(https://help.sap.com/viewer/8e5c63b6470a4255861c259f3b2d9b41/Cloud/en-
US/84867c7280cd4a9880769f3905daf551.html)

For managing the mobile application, see

https://help.sap.com/viewer/38dbd9fbb49240f3b4d954e92335e670/Cloud/en-US

App Extensibility: Mobile Ticket Data Capture

You can extend the TSW Ticket Data Capture app according to your business needs for different aspects. For this purpose, the
following extensibility options are available:

This is custom documentation. For more information, please visit the SAP Help Portal 44
 2/19/2022
For key users and developers

Key users can extend the app in the nomination item fetch logic and external number assignment using the following
context(s):

This is used to complement the standard logic to fetch nomination items that are downloaded to the mobile
device during a synchronization

This is used to change the external number assignment for the tickets created through the Mobile Ticketing app

For developers

BAdI Implementation

Further Extensibility Entities

Business Add-Ins (BAdIs)

The following BAdIs are available for extensibility purposes:

OIJ07_NMT_NOMINATIONFETCH

You can use this BAdI to complement the standard logic to fetch nomination items that are downloaded to the mobile
device during a synchronization. The nomination items are fetched by the standard logic which can be further altered to
the requirement of the customer by implementing the bespoke logic in this BAdI implementation.

OIJ07_NMT_EXTKTNUM

In Standard External Number generated as per the number range group con gured with the ticket type. You can use this
BAdI to change the external number assignment for the tickets created through the Mobile Ticketing app.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.

CDS Views
Nomination Ticket Additional Quantity
Technical Name C_NOMINATIONTICKETADDLQUANTITY

View Type Consumption

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

What are the additional quantities for every ticket created against the nomination line item?

Prerequisites
This view is based on I_NOMINATIONTICKETADDLQUANTITY

This is custom documentation. For more information, please visit the SAP Help Portal 45
 2/19/2022

Structure
Measures and attributes

Some important measures and attributes are:

Quantity

Unit of Measure

Nomination Ticket Additional Parameter

Technical Name C_NOMINATIONTICKETPARAMETER

View Type Consumption

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

This CDS view does not provide any relevant data on its own, the data is populated by the GET_EXPANDED_ENTITYSET
method of the class CL_TSW_MULTI_CHANNEL_T_DPC_EXT

Prerequisites
This view is dependent on I_NOMINATIONTICKETPARAMETER

Structure
Measures and attributes

Some important measures and attributes are:

Physical Parameter Name

Physical Parameter Value

Nomination Ticket Detail Interface

Technical Name I_NOMINATIONTICKETDETAIL

View Type Interface

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

Which are the Nomination Line Items for which a ticket is due?

Which are the Nomination Line Items for which a Ticket has been captured and sent to backend?

This is custom documentation. For more information, please visit the SAP Help Portal 46
 2/19/2022
Which are the Nomination Line Items for which a Ticket has been created

Which are the Nomination Line Items for which a Ticket has been successfully actualized

What is the Scheduled Quantity for each nomination line item?

What is the Actualized Quantity for each nomination line item?

What is the In-Process Quantity for each nomination line item?

What are the origin and destination locations?

What is the Scheduled Date, Location, Mode of Transport etc?

Measures and attributes

Some important measures and attributes are:

Scheduled Quantity. This is derived from the Nomination Item table (OIJNOMI)

Quantity In-Process. This is derived as a summation from the OIJNMTC1 table and Ticket Item table (OIJ_EL_TICKET_I)

Actualized Quantity. Derived from the Nomination Items Table (OIJNOMI)

Nomination Ticket Additional Quantity

Technical Name I_NOMINATIONTICKETADDLQUANTITY

View Type Interface

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

What are the additional quantities for every ticket created against the nomination line item?

Measures and attributes

Some important measures and attributes are:

Quantity

Unit of Measure

Ticket Status for Mobile Ticketing

Technical Name I_NOMINATIONTICKETSTATUS

View Type Interface

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

This is custom documentation. For more information, please visit the SAP Help Portal 47
 2/19/2022
What is the status of ticketing with respect to the nomination line item?

What is the Quantity In-Process and the corresponding UoM?

Structure
Measures and attributes

Some important measures and attributes are:

Nomination Ticket Status

Quantity In-Process

Unit of Measure of Quantity In-Process

Nomination Con guration

Technical Name I_NOMINATIONMBLTICKETCONFIGN

View Type Interface

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

What is Number of days in past and present for which the nomination line item should be retrieved for each combination
of Location and Transport System?

What are statuses for which nomination line items are to be retrieved for each combination of Location and Transport
System?

Prerequisites
Table OIJNMTC1 has to be lled using the transaction O4NMTC

Structure
Measures and attributes

Some important measures and attributes are:

Nomination Scheduled days in past. This eld determines the Scheduled dates in past for which the Nominations are
picked.

Nomination Scheduled days in future. This eld determines the Scheduled dates in future for which the Nominations are
picked.

Nomination Ticket Detail Consumption

Technical Name C_NOMINATIONTICKETDETAIL

This is custom documentation. For more information, please visit the SAP Help Portal 48
 2/19/2022

Technical Name C_NOMINATIONTICKETDETAIL

View Type Consumption

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

Which are the Nomination Line Items for which a ticket is due?

Which are the Nomination Line Items for which a Ticket has been captured and sent to backend?

Which are the Nomination Line Items for which a Ticket has been created

Which are the Nomination Line Items for which a Ticket has been successfully actualized

What is the Scheduled Quantity for each nomination line item?

What is the Actualized Quantity for each nomination line item?

What is the In-Process Quantity for each nomination line item?

What are the origin and destination locations?

What is the Scheduled Date, Location, Mode of Transport etc?

Prerequisites
This view requires ʻCreate’ authorization for the object O_OIJ_TCKT.

This view is based on I_NOMINATIONTICKETDETAIL

Structure
Measures and attributes

Some important measures and attributes are:

Scheduled Quantity. This is derived from the Nomination Item table (OIJNOMI).

Quantity In-Process. This is derived as a summation from the OIJNMTC1 table and Ticket Item table (OIJ_EL_TICKET_I).

Actualized Quantity. Derived from the Nomination Items Table (OIJNOMI).

Nomination Tickets
Technical Name C_NominationMultiTickets

View Type Consumption

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

This is custom documentation. For more information, please visit the SAP Help Portal 49
 2/19/2022
What are the tickets available for nomination line items?

Prerequisites
This view is dependent on I_NominationMultiTickets.

Structure
Measures and attributes

Some important measures and attributes are:

Ticket External Number

Ticket Quantity

Ticket UoM

Date

Ticket Status

Related Information
Analytics

Nomination Tickets
Technical Name I_NominationMultiTickets

View Type Interface

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

What are the tickets available for nomination line items?

Prerequisites
This view is dependent on I_NominationItemFld, I_NominationTicketList

Structure
Measures and attributes

Some important measures and attributes are:

Ticket External Number

Ticket Quantity

Ticket UoM
This is custom documentation. For more information, please visit the SAP Help Portal 50
 2/19/2022
Date

Ticket Status

Related Information
Analytics

Nomination Ticket Event

Technical Name C_NominationTicketEvent

View Type Consumption

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

what are the events captured for every ticket?

Prerequisites
This view is dependent on I_NominationTicketEvent.

Structure
Measures and attributes

Some important measures and attributes are:

Event Text

Sequence Number

Start/end date/time

Related Information
Analytics

Nomination Ticket Event

Technical Name I_NominationTicketEvent

View Type Interface

Release Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

This is custom documentation. For more information, please visit the SAP Help Portal 51
 2/19/2022
what are the events captured for every ticket?

Prerequisites
This view is dependent on I_TicketEvent.

Structure
Measures and attributes

Some important measures and attributes are:

Event Text

Sequence Number

Start/end date/time

Related Information
Analytics

OData Service
Multi-Channel Ticketing OData Service Overview

Overview
The OData service provides the nomination data and the related ticket data for nominations that are in the date range and
statuses as con gured. The service also provides details relevant to the QCI physical parameters and additional quantities.

The service also supports the creation of tickets against the nominations with the data provided from the UI related to ticket
quantity and load start, end time.

OData Version: 2.0

Root URI:/sap/opu/odata/sap/TSW_MULTI_CHANNEL_TICKET/C_NominationTicketDetail

Entity Data Model

This is custom documentation. For more information, please visit the SAP Help Portal 52
 2/19/2022

Service Metadata URI: /sap/opu/odata/sap/TSW_MULTI_CHANNEL_TICKET/C_NominationTicketDetail

Multi-Channel Ticketing OData Resource

This resource provides the nomination data and the related ticket data for nominations that are in the date range and statuses
as con gured. The service also provides details relevant to the QCI physical parameters and additional quantities.

Resource Path: /sap/opu/odata/sap/TSW_MULTI_CHANNEL_TICKET/C_NominationTicketDetail

Operations
CRUD Operations

HTTP Operation URI

Method

GET /sap/opu/odata/sap/TSW_MULTI_CHANNEL_TICKET/C_NominationTicketDetail?
$expand=to_NominationMultiTickets/to_NominationTicketAddlQuantity,to_NominationMult

PUT /sap/opu/odata/sap/TSW_MULTI_CHANNEL_TICKET/$batch

Multi-Channel Ticketing OData Operation: GET

This is custom documentation. For more information, please visit the SAP Help Portal 53
 2/19/2022
The operation retrieves the nomination data and the related ticket data for nominations that are in the date range and
statuses as con gured. The service also provides details relevant to the QCI physical parameters and additional quantities.

Request
URI: /sap/opu/odata/sap/TSW_MULTI_CHANNEL_TICKET/C_NominationTicketDetail?
$expand=to_NominationTicketAddlQuantity,to_NominationTicketParameter

Operation Type: CRUD

HTTP Method: GET

Multi-Channel Ticketing OData Operation: PUT

The operation sends details captured in the UI to the backend to create/actualize tickets against the selected nomination
items.

Request
URI: /sap/opu/odata/sap/TSW_MULTI_CHANNEL_TICKET/$batch

Operation Type: CRUD

HTTP Method: PUT

Scheduling Assistant
With this app, the scheduler can make a decision on the sourcing options available to ful ll the demand for a particular material
of certain quantity at a location on a target date.

For any given demand (either nomination or simulation), a list of the feasible sources of supply is displayed . Feasible sources
are determined either from locations that are directly connected or connected through an intermediate location to the demand
location. The list shows if the source is from own stock or from a purchase, the material or purchase price, the associated
simulated logistics costs, the duration based on mode of transport and the proposed loading date. The list is ranked by total
cost. The scheduler makes the nal decision by selecting from the sources of supply suggested by the app to ful ll the demand
and complete the respective nomination or simulation in the backend system.

The transshipment points are shown in addition to the source locations (with no stock or purchasing option shown for the
transhipment leg). The logistics costs are shown for each leg and in total. The system supports a single transhipment (two
modes of transport)

Key Features
This app provides the following key features:

List view of the open demands from various sources

Provides an option to capture a new demand line

Option to lter the demands speci c to a Location, Product and so on

Helps to identify potential sources of supply for a selected demand and transshipment points if required

This is custom documentation. For more information, please visit the SAP Help Portal 54
 2/19/2022
The duration for each source or transshipment point is calculated based on the shortest path as per the stages
maintained in the routes

Quick view feature for the purchase contract to display the relevant contract details

Ability to open the Demand/Source in the Inventory Planning Workbench (IPW) application, once it is con rmed

Sources of supply are displayed based on the logistics cost ranking. Transshipments are shown as a second line under the
same ranking

Provides an option to recalculate the logistic cost by supplying additional Business Partners used in shipment costing
(For example, Insurance, Inspector and so on).The selected source line can be saved in the backend system completing
the Nomination or Simulation

Supported Device Types

Desktop

Tablet

Smart phone

App Implementation: Scheduling Assistant

System Landscape Requirements

For information about the system requirements, see System Requirements.

Tile Type for Launching App

The Scheduling Assistant app is launched using a dynamic tile.

Implementation Tasks
The following sections list tasks that have to be performed to implement this app. The tables contain the app-speci c data
required for these tasks.

You can also nd the data required to perform these tasks in the SAP Fiori apps reference library at
https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/#/detail/Apps('F4163')/S14OP.

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

This is custom documentation. For more information, please visit the SAP Help Portal 55
 2/19/2022
Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (1) TSW_SCHEDULINGASSISTANT_SRV

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application TSW_SCHEDASSTS1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server: Activate ICF Service

Component Technical Name

ICF Service tsw_schedassts1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server : Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those apps that have been
assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see User Management and
Authorization.

SAP delivers technical catalogs for groups of apps as repositories to create your own catalogs in the launchpad designer. Along
with these catalogs, more technical content is delivered for each SAP Fiori app. You can nd the delivered technical content for
each SAP Fiori app in the SAP Fiori apps reference library.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

This is custom documentation. For more information, please visit the SAP Help Portal 56
 2/19/2022

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

TSW_SCHEDULINGASSISTANT_SRV (1) You can use the example business catalog Use an existing role or create a new one.
SAP_OILDS_BC_TSW_PLAN or your
custom catalog to create the back-end
PFCG role.

O_OIJ_NOM – create a role

App Extensibility: Scheduling Assistant

You can extend the Scheduling Assistant app according to your business needs for different aspects. For this purpose, the
following extensibility options are available:

For key users and developers

Key users can extend the app in the Custom Fields and Logic app using the following context(s)

TSW_DEMAND_NOM_SCHED - TSW Demand Nomination Schedule Lines

TSW_SOURCE_NOM_SCHED - TSW Source Nomination Schedule Lines

TSW_NOMINATIONHEADER - TSW Nomination Header

TSW_NOMINATIONITEM - TSW Nomination Item

For Key Users and Developers

You can add elds to the following UI elements using UI adaptations at runtime:

UI Element Business Context

I_NOMINATIONSIMULATION - I_NominationSimulation TSW_DEMAND_NOM_SCHED

I_DEMANDNOMINATIONSCHEDULETP - Demand Schedule TSW_DEMAND_NOM_SCHED

C_DEMANDNOMINATIONSCHEDULETP - Scheduling Assistant TSW_DEMAND_NOM_SCHED

I_SOURCENOMINATIONSCHEDULETP - Source Schedule TSW_SOURCE_NOM_SCHED

C_SOURCENOMINATIONSCHEDULETP - Source Schedule TSW_SOURCE_NOM_SCHED

For more information about how to adapt an SAP Fiori UI at runtime, see Making UI Changes.

Key users can also make custom elds available in several apps including handing over data by using business scenarios.

This is custom documentation. For more information, please visit the SAP Help Portal 57
 2/19/2022

For Developers
To add a customer eld to the app, the extensibility entities listed below are available on the different software layers. You have
to extend each of these entities according to your speci c business needs:

UI Back End/ABAP

View Extension Design Time: Gateway Entity Design Time: CDS View Design Time: E
Point DDIC Structur

I_NOMINATIONSIMULATION TSW_SCHEDULINGASSISTANT E_DemandNominationSchedule DEMAND_NOM

I_DEMANDNOMINATIONSCHEDULETP E_SourceNominationSchedule DEMAND_NOM

C_DEMANDNOMINATIONSCHEDULETP SRC_NOM_SC

I_SOURCENOMINATIONSCHEDULETP SRC_NOM_SC

C_SOURCENOMINATIONSCHEDULETP

Further Extensibility Entities

Business Add-Ins (BAdIs)

The following BAdIs are available for extensibility purposes:

Scheduling Assistant Defaulting on Source Con rmation (OIJ09_SCHDASST_DEFAULTING)

You can use this BAdI to default the necessary elds in source line while saving the source line to the respective demand
line item.

Modifying Demand Lines for Scheduling Assistant (OIJ09_SCHDASST_DEMANDS)

You can use this BAdI to de ne additional logic for the selection of demand lines (Simulations and nominations) from the
backend system.

Scheduling Assistant: Maintain Movement Scenario (OIJ09_SCHDASST_MVSCEN)

You can use this BAdI to add additional logic to determine the movement scenario of the sourcing option beyond what is
covered in the movement scenario determination table (OIJ09_SA_MOVSCN) before saving the source line in the
backend system.

Scheduling Assistant: Determine the rank of the Scheduling Options (OIJ09_SCHDASST_RANK)

You can use this BAdI to de ne custom logic to rank the identi ed sourcing options for a particular demand line item.

Determine Scheduling Options for Scheduling Assistant (OIJ09_SCHDASST_SOURCES)

You can use this BAdI to de ne additional logic or custom logic in the derivation of sourcing options.

Extension Includes

In addition to the extension includes described above, the following extension includes are available:

DDIC Extension Include Use

This is custom documentation. For more information, please visit the SAP Help Portal 58
 2/19/2022

DDIC Extension Include Use

OIJ_SCHED DEMAND_NOM_SCHED_INCL_EEW_PS To access the persistent custom elds in

table OIJ09_SCHED in the application.
DEMAND_NOM_SCHED_INCL_EEW_TR
To set the eld visibility properties of
custom elds added under
DEMAND_NOM_SCHED_INCL_EEW_PS

OIJ09_SCHED SRC SRC_NOM_SCHED_INCL_EEW_PS To access the persistent custom elds in

table OIJ09_SCHEDSRC in the
SRC_NOM_SCHED_INCL_EEW_TR
application.

To set the eld visibility properties of

custom elds added under
SRC_NOM_SCHED_INCL_EEW_PS

For more information about extension includes, see Extend SAP Fiori Apps.

Extension Points

If there are additional elds available in the OData service, you can display these elds on the UI. For more information about
extension points, see Extend SAP Fiori Apps.

UI Controller Hooks

If there are additional UI controller hooks available in the controller code, you can extend the UI controller code. For more
information about UI controller hooks, see Extend SAP Fiori Apps.

Display of UI Controls

For more information about hiding UI controls, see Extend SAP Fiori Apps.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.

For more information, also see:

Extensibility

Extensibility Information

Custom Fields and Logic

CDS views
Demand Nomination Schedule
CDS View Name C_DemandNominationScheduleTP

Status Released

Purpose

This is custom documentation. For more information, please visit the SAP Help Portal 59
 2/19/2022
This CDS view provides the prerequisites for answering the following business questions:

Which are the Demand Nomination lines that are available in the system without a scheduled Source Nomination line?

Which are the Demand Nomination Simulation lines that are available in the system without a scheduled Source
Nomination Simulation line?

Which are the Demand Nomination Simulation lines that are available in the system without a scheduled Source
Nomination Simulation line?

Prerequisites
Users who want to run reports using this CDS view must have a role based on the business role template listed in the table
above. In this role, the following restrictions must be set to read access:

Appropriate authorizations assigned for Authorization Object O_OIJ_NOM for the location eld and Activity ʻ03’ (Display)

Structure
Object types

This view is built on the following object types:

Nominations

Simulations

Main CDS parameters and lters

The main lters are:

LocationId - Used to lter the Demands by Business Location

ScheduledMaterial - Used to lter the Demands by the Material

NominationScheduleDate - Used to lter the Demands by the Scheduled Date

Measures and attributes

Some important measures and attributes are:

LocationId - Location at with the requirement exists

ScheduledMaterial - Required Material

NominationScheduleDate - Required Date

ScheduledQuantity - Required Quantity

ScheduledQuantityUnit - Unit of Measure

ModeOfTransport - Mode of Transport expected

Related Information
Analytics

Source Nomination Schedule

This is custom documentation. For more information, please visit the SAP Help Portal 60
 2/19/2022

CDS View Name C_SourceNominationScheduleTP

Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

What are the available Sources from which the Demand can be met?

Prerequisites
Users who want to run reports using this CDS view must have a role based on the business role template listed in the table
above. In this role, the following restrictions must be set to read access:

Appropriate authorizations assigned for Authorization Object O_OIJ_NOM for the location eld and Activity ʻ03’ (Display)

Structure
Object types

This view is built on the following object types:

Location

Material

Transport System

Route

Purchase Contract

Measures and attributes

Some important measures and attributes are:

LocationId - Location from which the demand can be met

ScheduledMaterial - Required Material

NominationScheduleDate - Date of Departure

ScheduledQuantity - Required Quantity

ScheduledQuantityUnit - Unit of Measure

ModeOfTransport - Mode of Transport for supply

TransportSystem - Transport System for Supply

Route - Route for Supply

Related Information
Analytics

This is custom documentation. For more information, please visit the SAP Help Portal 61
 2/19/2022

Source Nomination Schedule Partner

CDS View Name C_SourceNominationSchedPartner

Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

What are the available Partner Functions/Partners for a scheduling option?

Structure
Object types

This view is built on the following object types:

Business Partner

Measures and attributes

Some important measures and attributes are:

Partner Function

Partner

Purchase Contract Quick View

CDS View Name C_PurContrSourceNomination

Business Role (Template) NA

Business Catalog NA

Data Category Dimension

Status Released

Data Extraction Type NA

Corresponding DataSource (Extractor) NA

Corresponding DataSource (for use in SAP Analytics Cloud and NA

analytical clients)

Purpose
This CDS view is used to get the purchase contract information as a quick view in the source options of a demand schedule.

This CDS view provides the prerequisites for answering the following business questions:

How to get the purchase contract information ?

This is custom documentation. For more information, please visit the SAP Help Portal 62
 2/19/2022

Prerequisites
This view is dependent on the CDS view I_PurchasingDocumentItem

Structure
Object types

This view relates to the following SAP object types:

Purchase Contract

Measures and attributes

Some important measures and attributes are:

PurchaseContract – Purchase Contract of the sourcing options

PurchaseContractItem – Purchase Contract Item of the sourcing options

SupplierName – Supplier of the Purchase Contract

ValidityEndDate – Validity End Data

PaymentTerms - Payment Terms

IncotermsClassi cation – Inco terms

DocumentCurrency – Currency of Purchase Contract

Related Information
Analytics

Mobile Event Data Capture

With this app you can download the nomination items that you are authorized to load. The load/discharge event details for each
item can be captured and saved even as the device is offline. Once online, the device can be synced where the event data
captured gets pushed to the backend systm and nomination items downloaded are refreshed. The Terminal Operator captures
actual event details as well as additional comments during loading or discharging activities performed for the scheduled
nomination line item.

Key Features
You can use this app to:

Download nomination item details necessary for Terminal operator to a device. This includes nomination number,
schedule date, movement type, schedule quantity, material, location, mode of transport and so on.

Display event type associated with nomination line item in a separate screen.

Enter comment to capture user key notes.

Capture adhoc event type using create event type functionality.

Capture actual event date and time compared to the planned for a speci c nomination event type.

Capture event details even as the device is offline, save and push the data to the backend system once it is online.

This is custom documentation. For more information, please visit the SAP Help Portal 63
 2/19/2022
Personalize the worklist page as required.

You can map SAP speci c master data for example, Material, Location and so on to external representation for other
users.

Supported Device Types

Tablet (iOS, Android, Windows Mobile)

Smartphone (iOS, Android, Windows Mobile)

App Implementation: Mobile Event Data Capture

Prerequisites
The mobile services license for using the Mobile Event Data Capture app.

Before implementing the app, you must ensure the following:

System Landscape Requirements

For information about the system requirements, see System Requirements.

Implementation Tasks
The following sections list tasks that have to be performed to implement this app.

To enable the Hybrid Application Toolkit, see https://help.sap.com/viewer/8e5c63b6470a4255861c259f3b2d9b41/Cloud/en-

US/ff3a6540704040afba7ee5e5a43b14f2.html

When the BSP app is loaded into Web IDE, follow the steps listed below:

1. Load the application into Web IDE and mobile enable the app.Right-click on the project, choose Mobile Enable as Hybrid
Mobile Project . A mobile folder appears under the project.

2. Navigate to webapp Mobile under the project.

Copy the le sap-mobile-hybrid.js. Replace the le sap-mobile-hybrid.js under your project path
mobile hybrid with the copied le. Uncomment the contents of the le.

3. To build the app using mobile services, see

(https://help.sap.com/viewer/8e5c63b6470a4255861c259f3b2d9b41/Cloud/en-
US/84867c7280cd4a9880769f3905daf551.html)

For managing the mobile application, see

https://help.sap.com/viewer/38dbd9fbb49240f3b4d954e92335e670/Cloud/en-US

Back-End Server: Create Connectors

This app is based on ABAP Core Data Services and does not require search models to work. However, if you want to start the
app from the search results list, you must activate the underlying search connectors. You can create connectors in transaction
ESH_COCKPIT.

This is custom documentation. For more information, please visit the SAP Help Portal 64
 2/19/2022
For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Object pages are based on search models. To be able to use an object page, you must activate the underlying search models by
creating connectors. Create connectors in transaction ESH_COCKPIT.

You can nd the search models for this app in the SAP Fiori apps reference library.

For more information, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA View
All Function-Oriented View Search and Operational Analytics Setting Up Enterprise Search Creating Connectors .

 Note
Note the following system behavior:

Search software components build a stack. Different layers can be installed on top of the basis component.

Search models can be available in different components - in their original component, but also in higher layer components
(extension components).

Once you create a search connector in an extension component, all search models from the original component are
transferred into the extension component. You will therefore no longer nd the search models in the original component, as
is shown in the table below.

Front-End Server: Activate OData Services

Component Technical Name

OData Service (1) TSW_MOBILE_EVENTS_SRV

For more information about activating OData services, see Activating OData Services.

Front-End Server : Activate SAPUI5 Application

Component Technical Name

SAPUI5 Application TSW_MOBEVENTSS1

Generic Drill-Down Application /default_host/sap/bc/ui5_ui5/sap/sbrt_appss1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

This is custom documentation. For more information, please visit the SAP Help Portal 65
 2/19/2022

Front-End Server: Activate ICF Service

Component Technical Name

ICF Service TSW_MOBEVENTSS1

For more information about how to activate the ICF service, see Activate ICF Services of SAPUI5 Application.

Front-End Server and Back-End Server: Assign OData Service Authorizations to

Users
You must assign OData service authorizations for the app to your users.

 Caution
Several authorization default values are connected to the OData service. To ensure that all these default values are
assigned to a user, you have to follow the instructions given under the documentation links provided.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see
Creating Authorization Roles for Catalogs.

On the front-end server, you must assign the OData service authorization to a new or existing role, such as a business
role that has been adjusted according to your needs. For more information, see Creating Roles on Front-End and
Assigning Launchpad Catalogs and Spaces/Pages and Assigning Roles to Users on Front-End.

OData Service (Version Number) Back-End Server: Authorization Role Front-End Server: Assignment to
(PFCG Role) Authorization Role

TSW_MOBILE_EVENTS_SRV (1) O_OIJ_NME – create a role

AIF Con guration

The following AIF con guration is available in the /OIL namespace:

Interfaces

Inbound Interface – OILIANMEVT

The system invokes the inbound interface when data is passed from the mobile device to the server. For example, saving
a nomination event.

Outbound Interface – OILOSNMEVT

The system invokes the outbound interface when data is fetched from the server to the mobile device. For example, pull
to refresh.

Value Mappings

The value mapping is used to map the internal values of the SAP system to the external values provided by the user.

OIJ09_NME_LOCATION

OIJ09_NME_MATERIAL

This is custom documentation. For more information, please visit the SAP Help Portal 66
 2/19/2022
OIJ09_NME_MOT

OIJ09_NME_SCHD_TYPE

OIJ09_NME_UOM

For more information on error handling and value mapping, see

https://help.sap.com/viewer/1cefaed5b7a3471cb08564e54d5ba866/4.0/en-US/d02c5cc67114450e848b74dfa6b11efb.html

App Extensibility: Mobile Event Data Capture

You can extend the Mobile Event Data Capture app according to your business needs for different aspects. For this purpose, the
following extensibility options are available:

Further Extensibility Entities

Business Add-Ins (BAdIs)

The following BAdI is available for extensibility purposes:

Mobile Events (TSW) : Nomination Fetch (OIJ09_MBLEVTS_NOMEVTFETCH)

You can use this BAdI to add custom logic to fetch the nominations to be downloaded.

If there are additional elds available in the OData service, you can display these elds on the UI. For more information about
extension points, see Extend SAP Fiori Apps.

UI Controller Hooks

To plug in and execute custom code, for example, the following hooks are available in the controller code:

Controller Hook Use

Master View Master.view.extMasterViewTableFields Allows you to add an additional elds to the

table heading in Master table view

Master.view.extMasterViewTableData Allows you to add an additional data to the

table in Master table view

Detail View Detail.view.extDetailViewTableFields Allows you to add an additional elds to the

table heading in Event table in Detail view

Detail.view.extDetailViewTableData Allows you to add an additional data to the

table in in Event table in Detail view

CreateEntity View Create.view.extCreateViewFormFields Allows you to add an additional elds to the

form in form view of Create table view

If there are additional UI controller hooks available in the controller code, you can extend the UI controller code. For more
information about UI controller hooks, see Extend SAP Fiori Apps.

For more information about hiding UI controls, see Extend SAP Fiori Apps.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see Extend SAP Fiori Apps.

This is custom documentation. For more information, please visit the SAP Help Portal 67
 2/19/2022
For more information, also see:

Extensibility

Extensibility Information

Custom Fields and Logic

CDS Views
Nomination Details
CDS View Name C_NominationDetail

Status Released

Purpose
This CDS view provides the prerequisites for answering the following business questions:

What are the Nominations that are available in the system based on the con guration maintained for Location ID,
Transport system, Nomination Type and Rolling Period?

Prerequisites
Users who want to run reports using this CDS view must have a role based on the business role template listed in the table
above. In this role, the following restrictions must be set to read access:

Appropriate authorizations assigned for Authorization Object O_OIJ_NME for the location, transport system and
nomination type elds and Activity ʻ23’ (Maintain)

Structure
Object types

This view is built on the following object types:

Nominations

Nomination Events

Main CDS parameters and lters

The main lters are:

LocationId - Used to lter the Nominations by Business Location

TransportSystem - Used to lter the Nominations by the Transport System

NominationType - Used to lter the Nominations by the Nomination Type

Measures and attributes

Some important measures and attributes are:

This is custom documentation. For more information, please visit the SAP Help Portal 68
 2/19/2022
LocationId - Location at with the requirement exists

Descriptive text on the important measures & attributes

NominationType - Nomination Type

TransportSystem - Transport System for the Nomination

NominationScheduleDate - Date of Departure

ScheduledMaterial - Material Scheduled for the Nomination

ScheduledQuantity - Material Quantity

ScheduledQuantityUnit - Unit of Measure

Related Information
Analytics

Integration of TSW with SAP IBP

With the integration of Trader's and Scheduler's Workbench (TSW) with SAP Integrated Business Planning (IBP) the following
features are available:

Integration with SAP Integrated Business Planning (IBP) demand planning.

Oil-speci c modeling is done with new IBP demand planning area

Allows monthly, weekly and daily planning

Creation of a new Bulk Forecast column in inventory planning workbench (IPW) to allow IBP demand planning data to be
stored.

A consumption logic is provided so that the bulk forecast can be used in the stock projection calculation as well. For more
information, see Bulk Forecast Consumption

The O-data service is used to insert Rack Forecast, Bulk Forecast data and global simulations from IBP supply planning
into IPW. You can directly pass the Rack and Bulk Forecast quantities or pass the quantity and MoT.

As an alternate approach to the O-data service, RFC function modules are provided for the following:

To insert Rack or Bulk Forecast data into the respective database tables. These forecasts can be viewed in IPW
and are used in the stock projection calculation.

To create nomination simulations which is then published from IPW.

For more information, see SAP Note 2960331.

Logistic Cost using Shipment Costing

Shipment costing is used to capture all movement relevant logistics costs that is not only transport costs, but items such as
throughput, inspection, harbour fees, last mile costs and so on.

To simulate shipment costing fully, the relevant partners are required (the instantiation of the respective shipment cost items is
dependent on the presence of the partner role relevant for the item/ fee type). It may happen that at the time of the shipment
costing simulation not all the relevant partners are populated in the nomination/ simulation.

For these cases, you can use the following solution:

This is custom documentation. For more information, please visit the SAP Help Portal 69
 2/19/2022
1. Read the shipment cost customizing for the relevant shipment cost type (the relevant item categories and their
respective partner roles)

2. Invoke the shipment costing simulation (using the partner roles which are present)

3. Compare the resulting internal representation of the shipment cost document with the customizing from the rst step –
for the missing item categories.

For these simulation cases where the partner role has not yet been provided, the latter is sufficient.

4. Using this entry – evaluate the relevant pricing procedure/ condition type – which will be partner/ supplier independent
– for example for a default freight condition, an appropriate condition key might be:

Mode of Transport, Origin, Destination

5. This process is followed for all item categories/ fee types that could not be evaluated using the shipment cost simulation
because of missing partners.

Partner completion in the supply options screen

You can add missing partners in the supply options, to achieve a more accurate logistics cost simulation. You can use the Add
Partners option to enter the partner details.

Logistics cost calculation for CIF (Costs, Insurance & Freight) / DES (Delivered ex-
ship) contracts
In the case of delivered or ʻCIF’ purchases there are normally no freight costs as these are included in the purchase price based
on the incoterms. There may however be other logistics costs related to the movement (such as throughput, inspection and so
on.). For several reasons it is necessary to cater to these through shipment costing (correct allocation of costs, MI and so on).

In the standard system the shipment type (which in turn determines the shipment cost type) is derived from the transport
system, which does not consider incoterms. In implementation projects, it may therefore be necessary to override this standard
determination so that incoterms can be considered in the determination of the shipment type and therefore the shipment cost
type (for example, to determine a shipment cost type which does not calculate freight in the case of DES/ CIF incoterms).

While setting up the shipment costs that are used for the simulated logistics costs in Scheduling Assistant and IPW, incoterms
are considered so that freight costs are not calculated if a DES/ CIF contract is selected as the source. If Scheduling Assistant is
used to select the source for a simulation, the system can only use the default shipment type; however where the Scheduling
Assistant is used to select the source for a nomination demand line, the system rst simulates costs using the shipment type in
the nomination header, if this is overridden using the type of enhancement mentioned above, then only relevant costs are
determined. If no shipment type is speci ed, or the default is used, it is still possible to calculate costs correctly if a reference to
incoterms (or the correct OIG_GLPOD indicator) is used in the access sequence.

You can use the BAdI (OIJ09_COST_DETERMINATION)) for cost calculation and determination.

Freight Cost Allocation

In a multi drop scenario that is, one origin and multiple drop locations, there can be costs that are related to the entire
shipment. This can be considered as a header cost for all the stages involved in the shipment.

Inspection, demurrage, throughput, harbor fees, own eet costs and so on are some of the costs that are related to entire
shipment. There needs to be a mechanism to allocate these costs to respective deliveries. This helps in showing the margins in
analysis of costs like in waterfall analysis model.

To achieve this, you can use the SAP BRF (Business Rule Framework) plus, where you can maintain business rules, that is used
to allocate header costs across drop points.

This is custom documentation. For more information, please visit the SAP Help Portal 70
 2/19/2022
You can use the BAdI (OIJ09_COST_ALLOCATION) for cost allocation.

Usage of BRF+ (Business Rules Framework Plus)

You can use the object Freight Cost Allocation (OIJ09_COST_FREIGHT_ALLOC)) for cost allocation.

Two rules have been included as standard for Cost Allocation:

Using spoke distance.

Using volumetric split

User can also disable the standard rules and introduce a new rule for cost allocation as per your requirement.

Decision Support using Scheduling Assistant

There are often many alternative ways to ful ll a demand or replenish a depot from own stock at a different depot; through a
purchase and using different modes of transport and Incoterms. The scheduler is faced with the problem of determining the
most cost effective supply options.

Using the Scheduling Assistant, the scheduler can lter existing demands (nominations and simulations); select from a list of
existing demands or enter a new simulated demand .

 Note
Only global simulations are considered. Demands are selected based on movement scenario; a BAdI is provided if there are
additional requirements.

The demand types are separated and listed by object type (nomination or simulation).

When a demand is selected, the application presents the scheduler with a list of viable alternative supply options displaying the:

Source location/ Transshipment Location

Source location

Stock (for own locations)

Purchasing contracts with open quantity (for purchase locations)

Material valuation price (for own locations)

Purchase price (for purchase locations)

Logistics costs

Departure date (under consideration of duration)

Duration

Mode of transport

The options are sorted by total cost (there are BAdIs available for customers to implement their own selection and
prioritization logic) .

There is an option to recalculate logistics costs based on adding relevant partners

This is custom documentation. For more information, please visit the SAP Help Portal 71
 2/19/2022
The scheduler is able to select the appropriate supply option from the list and complete the respective simulation or nomination
which is saved in the backend system. The resulting movement scenarios can be customized in the system, based on the
scenario of the demand, the type of source (own stock or purchase) and if purchase, the incoterms.If there are additional
requirements relating to the movement scenario determined, a BAdI is provided.

Source location
The entries shown are retrieved from the transport system, assigned locations and materials and route information . A BAdI is
provided so that you can apply you own lter on the list of valid source locations.

The scheduler can also identify transportation connection points and read the connected routes and transport systems.
Transshipment legs are shown separately with the same ranking as the primary source legs. One transshipment is allowed for
two modes of transport.

Stock
If the location has own stock of the required product, the AMDP for the physical inventory rundown as used in IPW is executed
for the scheduled load date (demand date – transport duration obtained from the route stages) to calculate the physical
inventory available on the desired loading date in the demand unit of measure.

Material Price
In the case of own stock locations, the valuation price is displayed.

Purchase contracts/ items

Purchase contracts can be subject to different incoterms. FOB/ EXW contracts are selected if they are tenable at any of the
selected source locations (selection either by plant or by the TSW location in the TSW details) for the required product.

CIF/ DES (and derivatives of these) purchases are selected if they are tenable at the demand location.

the contract quantity displays the open contract quantity ( target quantity – (call off quantity + committed quantity).

Material Purchase Price

In the case of purchase contracts the purchase price is displayed for the demand quantity unit of measure (the app supports
both F&A and CPE pricing)

Logistics Costs
Logistics costs are calculated by simulating a shipment cost document. Additional customizing is provided so that:

If relevant partners are not known, a default pricing procedure can be assigned per shipment cost item.

Fields related to partners in the nomination can be mapped to shipment cost partner roles.

You can also add relevant partners for the purpose of cost simulation.

In the case of delivered or CIF purchases there are normally no freight costs as these are included in the purchase price based
on the incoterms. There may however be other logistics costs related to the movement ( such as throughput, inspection etc.). It
can be desirable for a number of reasons to cater for these through shipment costing (correct allocation of costs, MI etc)

This is custom documentation. For more information, please visit the SAP Help Portal 72
 2/19/2022
While setting up the shipment costs that are used for the simulated logistics costs in Scheduling Assistant and IPW, incoterms
are considered so that freight costs are not calculated if a DES/ CIF contract is selected as the source. If Scheduling Assistant
is used to select the source for a simulation, the system can only use the default shipment type; however where the Scheduling
Assistant is used to select the source for a nomination demand line, the system rst simulates costs using the shipment type in
the nomination header, if this is overridden using the type of enhancement mentioned above, then only relevant costs are
determined. If no shipment type is speci ed, or the default is used, it is still possible to calculate costs correctly if a reference to
incoterms (or the correct OIG_GLPOD indicator) is used in the access sequence.

In the case of transshipment each leg is costed separately and total costs are shown

Duration in days
The transport duration is read from the stage information if the routes are maintained.

Integration with IPW

The Scheduling Assistant functionality can also be invoked from IPW by selecting a nomination demand line or simulation.

This is custom documentation. For more information, please visit the SAP Help Portal 73