Monitoring of VS Alerts
Use
You can use the Alert Monitor to monitor alerts for Vehicle Scheduling (VS) . To do this, you define a VS alert profile containing a user-specific selection of alerts that are relevant to your planning area.
Features
The
VS
alert profile contains a number of alert types specific to
Vehicle
Scheduling
activities. The following tables show the available alert types and alerts:
Alert |
Explanation |
|---|---|
Check availability. Order due date changed by VS |
An existing order was rescheduled by
|
Loading resource is overloaded |
A loading resource (inbound/outbound) is overloaded. This can only occur if multiple planners work at the same time with the same locations to which loading resources are assigned. |
Order not scheduled in shipment by optimizer |
The order was not scheduled in a shipment. This can be due to various reasons: a suitable transportation lane or resource was not found for the shipment belonging to the order. Non-delivery costs are lower than the relevant transportation costs and the costs for earliness/lateness. The optimizer could not find a solution in the given runtime. |
Order was changed in OLTP |
This alert can be used in control rules to recognize situations where an order that was already assigned to a shipment was changed in the OLTP system. |
Shipment: resource is overloaded |
This alert indicates that a shipment quantity exceeds the available capacity of the shipment resource. This situation can occur if the resource was manually overloaded or if the order quantity has increased after the shipment was already generated. |
Alert |
Explanation |
|---|---|
No transportation service provider found |
A suitable transportation service provider (TSP) was not found to execute a shipment. This can be due to the following reasons: No TSP is assigned to the transportation lane. The TSP’s capacity is insufficient to execute a shipment (error occurs only in the case of automatic TSP assignment with transportation allocation). |
Alert |
Explanation |
|---|---|
Shipment rejected by TSP |
A tendered shipment was rejected by the TSP. |
Proposed dates/times changed by TSP |
Date/time proposals (planned departure/arrival) were changed by TSP (planned shipment). |
Transferred shipment: shipment rejected by TSP |
A shipment already transferred to the OLTP system was rejected by the TSP. |
Transferred shipment: proposed dates/times changed by TSP |
Date/time proposals (planned departure/arrival) were changed by TSP (shipments already transferred to OLTP system). |
For the first two transportation tendering alerts, you can use the context menu in the shipment to perform tendering again, or to cancel the request for quotations.
To create user-specific alerts, you can use the following Business Add-Ins (BAdIs):
/SAPAPO/VS_SHIPMENT
/SAPAPO/VS_INB_PROC
The following alerts can also be triggered from
Supply Chain Event Management
(
SCEM
):
Proposed shipment rejected by TSP
Proposed dates/times changed by TSP
Transferred shipment: proposed dates/times changed by TSP
Transferred shipment: proposed shipment rejected by TSP
No response from transportation service provider (only used by
SCEM
)
The following alert is used if the shipment tendering is monitored in
SCEM
:
Alert from
Supply Chain Event Management
Activities
Select the alerts that are relevant to you.
Assign a VS optimization profile .
In the optimization profile, you specify the planning version, the period, and the objects for which the
Alert Monitor
determines alerts. If you do not enter an optimization profile, theAlert Monitor
only determines alerts with typeLoading resource is overloaded
for the planning version and period defined in the overall alert profile.If required, assign the VS alert profile to your overall alert profile , your SCC user profile , or if you want to display alerts in interactive planning in TP/VS, to the optimization profile for TP/VS.