SAP TSW - Nomination

TSW - Nomination

The nomination transaction and screen supports three main processes:

1. Creation and maintenance of logical collections of scheduled movements as they relate to a carrier nomination process.
2. Communication and tracking of status of outputs to carriers and their responses.
3. Providing sufficient information to subsequent R/3 processes to support the automatic execution routines.

Each nomination and the schedule lines within it are tracked using statuses that are used both to generate alerts to the scheduler as well as control the execution of subsequent steps.

For example, the schedule lines are in status “Planned” whilst they remain internal to the oil company, then become “Scheduled” once the nomination that contains them has been transmitted to the carrier.

The updating of the schedule lines to status “Confirmed” can be achieved via an inbound interface (Inbound nomination BAPI), or manually based upon a paper or verbal update from the carrier, or by a so-called “quick confirm” function, where scheduling (sending) and confirmation occurs in one step.

Once confirmation has been achieved, the nomination schedule items are then enabled for execution (i.e. actualization via the ticket process).

Throughout the scheduling and nomination process, events can be defined and updated for each schedule line to track progress (e.g. planned loading time, actual loading time etc).

Other types of events can be also defined, for example to record references to other service partner and associated contracts (e.g. inspectors) as well as free-form text entries.

Recent enhancements to the TSW nomination include a new screen layout, enabling more schedule information to be visible at one time, new interface links to APO the links to contracts , and functions to allow speedy confirmation status updates at time of scheduling.