|
Field
|
Description
|
|
Set Mass Rollover
|
|
Load Port
|
First port of loading cargo (or Place of Receipt, if present).
|
|
Discharge Port
|
Last port of discharging cargo (or Place of Delivery, if present).
|
|
Departure On/After
|
This date is used to select ETD of the first leg. This date/value is automatically set as the latest (maximum) of all the Departure On/After dates/values in the selected Bookings within the set; the field appears disabled. Read-only.
|
|
Booking No (BL Count)
|
Booking numbers for which you want to perform rollover in the current set. The Booking numbers are hyperlinked, clicking which, the corresponding Booking opens in the View Booking (OPBKW03) screen.
|
|
Route Details (Now): Shows the show current route details in read-only mode.
Depending on your selection of Vessel/Voyage details in the Booking Search Result, PCC.NET will group the Bookings into different sets having identical routes.
-
To determine a set of Bookings having same distinct route, PCC.NET will consider Place of Receipt, Load Port/Call, Vessel, Voyage, Line, Discharge Port/Call, Place of Delivery.
-
Any feeder leg in between the Place of Receipt and Place of Delivery is considered to be part of this distinct route.
|
|
From Location (LP)
|
Port of Loading of the itinerary leg.
|
|
C/O
|
Calling order of Port of Loading. In case, a voyage calls at a port twice, this field indicates the sequence of call on which the cargo is loaded on the vessel.
|
|
Departs On (ETD)
|
Expected Time of Departure at Load Port of the vessel associated with the currently-selected leg.
If the rollover set contains multiple Booking numbers and the leg is a Feeder/PCL leg (without a voyage), this value appears ‘blank’.
|
|
To Location (DP)
|
Port of Discharge of the itinerary leg.
|
|
C/O
|
Calling order of Port of Discharge. In case, voyage calls at a port twice, this field indicates the sequence of call on which the cargo is loaded on the vessel.
|
|
Arrives On (ETA)
|
Expected time of Departure at Load Port of the vessel associated with the currently selected leg.
If the rollover set contains multiple Booking numbers and the leg is a Feeder/PCL leg (without a voyage), this value appears ‘blank’.
|
|
Category
|
Transport mode (Line, PCL and Feeder).
|
|
Voyage Name
|
Voyage Name for the selected vessel.
|
|
PCC Line
|
PCC Line of the voyage of the currently-selected leg.
|
|
Route Details (Should): Shows the show current route details which can be edited.
-
You can revise the route in this panel that will be applicable to current set of Booking(s).
-
You can change the first Port of Loading of a Booking, provided there is no doc locked B/L associated with it.
-
You can also delete the last leg and add another leg in this panel unless the route is complete.
-
Users with Privileged Booking User Role and Booking Creation for Supplementary B/L system action can update a Booking with a Voyage from a dock locked Load Port.
|
|
From Location (LP)
|
Port of Loading for the itinerary leg. It must be a valid registered 7-character port. This field has the Auto-Complete feature, which helps to populate the full location name as you start typing.
|
|
C/O
|
Sometimes a voyage calls at the same port twice. This field will show if it is the first or the second call that the cargo will be loaded on. This is a required field, except for PCL vessels without schedule registration and Feeder vessels.
|
|
Departs On (ETD)
|
Expected Time of Departure at Load Port of the vessel associated to the currently selected leg.
-
For Line(s): This field will be automatically populated from the Voyage Schedule based on the selection of vessel.
-
For PCL: This field is required depending on whether Voyage Schedule exists for PCL. If it doesn’t exist then it is required.
-
For Feeder: This field is required. If the rollover set contains multiple Booking numbers and the leg is a Feeder/PCL leg (without a voyage) and if it is the first leg, the default value in this field is Departure On/After value; otherwise the value will be Arrives On (ETA) of the previous leg.
|
|
To Location (DP)
|
Port of Discharge for the itinerary leg. It must be a valid registered 7-character port.
This field has the Auto-Complete feature, which helps to populate the full location name as you start typing.
|
|
C/O
|
Sometimes a voyage calls at the same port twice. This field will show, if it is the first or the second call that the cargo will be loaded on.
Except the case of PCL without schedule registration and Feeder, entry of C/O is required.
|
|
Arrives On (ETA)
|
Expected time of Departure at Load Port of the vessel associated to the currently selected leg. For Feeder, this is a required field.
-
For Line(s): This field will be automatically populated from the Voyage Schedule based on the selection of vessel.
-
For PCL: This field is required depending on whether Voyage Schedule exists for PCL. If it doesn’t exist then it is required.
-
For Feeder: If the rollover set contains multiple booking numbers and the leg is a Feeder/PCL (without a voyage) leg, then this value will be shown as ‘blank’. This field is required.
|
|
Category
|
Mode of transport. Available options are:
-
PCL: Indicates the leg as Pre Carriage for Line. If voyage schedule for PCL exists during Booking creation, you have to enter the LP/DP. Otherwise you can leave Voyage blank. You can only enter the LP, DP, approximate ETD/ETA and select Category as PCL. You can also enter the associated PCL cost by clicking COST.
-
FEEDER: Select this value for feeder vessels. Enter the LP/DP. Feeder can be first leg or after any other leg (PCL or LINE). As a Booking user, you can mark the leg as FEEDER irrespective of different transport mode used as feeder like Burge, Truck etc.
|
|
Voyage Name
|
Voyage Name. For Line(s) leg this field is required. Voyage name is to be optional for both Feeder and PCL when requesting. When accepting the Booking, only Voyage for Feeder can be optional and for PCL it becomes mandatory. Also, at that time PCL Voyage can be Intended Voyage.
|
|
PCC Line
|
PCC Line of the voyage to the currently selected leg.
-
Line(s): For Line category, this field value is auto-populated from Voyage Schedule based on your selection of voyage.
-
PCL: For PCL category, this value is required depending on whether schedule exists for PCL. If schedule doesn’t exist then this field remains blank.
-
Feeder: For Feeder category, this field remains blank.
|
|
Buttons
|
|
ADD LEG
|
Clicking this button adds a new blank itinerary row. You cannot add a leg between existing legs. You must always add route after the last leg. You cannot add another leg if the route is complete.
Departs On (ETD) should be after or same as Departure On/After.
|
|
CANCEL
|
Clicking this button cancels and closes the dialog box.
|
|
ROLLOVER
|
After revising the route, click this button to apply change to current set of booking. You can then click NEXT or PREVIOUS to perform rollover for next set of Bookings.
Following are different types of rollover that you can perform:
-
Rollover of vessel legs (for LINE/PCL/Feeder category).
-
Rollover by deleting legs (for LINE/PCL/Feeder category)
-
Rollover by changing First Load Port (LP)
-
Rollover by changing Final Discharge Port (DP)
Points to remember during Mass rollover.Points to remember during Mass rollover.
Points to Remember Before You Perform Rollover of Bookings
-
You can change the first Port of Loading of a Booking, provided there is no doc locked B/L associated with it.
-
Rollover is possible at any Booking status other than Cancelled and Declined.
-
Rollover can be done for both Intended and Firmed voyages. But changing from Intended Vessel, Voyage, and Line to Firmed Vessel, Voyage, and Line is not considered as Rollover.
-
If the rollover set contains multiple Booking numbers and there is a Feeder/PCL (without voyage) leg, you must update the Departs On (ETD) and Arrives On (ETA) values corresponding to the Feeder leg. Also, after the Rollover, you have to approve the Feeder legs for each Booking.
-
Change of cost/currency is not considered as Booking rollover. If the rollover set contains multiple Booking numbers and Feeder/PCL leg is present, the corresponding Feeder/PCL Currency and Cost will have values as blank. If required, you can enter the Currency and Cost. Values present for Currency and Cost will be applied to all Booking's Feeder/PCL legs (present in the set) after the rollover.
-
After the route is revised, re-approval is required for those legs which have been changed. So, if rollover is performed against a Booking whose status is Accepted, the status automatically changes to Requested. Rollover does not impact any other Booking status.
-
Certain eventsevents related to VIN association with the Booking are soft-deleted after rollover.
-
If first leg Vessel and Voyage of a Booking is rolled over, the Assign Booking event associated with the earlier Vessel and Voyage gets soft deleted and a new Assign Booking event with the new Vessel and Voyage gets added for that Booking. Also, the Remarks column of this VIN event be updated for reference of Booking rollover.
-
If Vessel and Voyage of any Leg is changed, the Load/Discharge VIN events for the earlier Vessel and Voyage get soft deleted.
-
If To Location (Discharge Port) of any leg is rolled over to a new port, the corresponding Load/Discharge VIN events of the earlier port gets soft-deleted.
-
If any Booking leg is deleted during rollover, Load and Discharge VIN events of the corresponding ports are soft deleted.
-
To update Booking, after a port has got Doc Locked for a Voyage, you need Privileged Booking User role and Booking Creation for Supplementary B/L system action.
Impact of Change in Last Discharge Port during Rollover in PCC.NET:
If you change the first or last Discharge Port, the corresponding link between Contract and Booking gets broken. At that time, changing rating in Contract is not applied to the current Booking, that is, REFRESH RATE FROM CONTRACT does not work until modification of the Port pair in Contract. As a result, while changing the last Discharge Port, during rollover, PCC.NET works as per the following logic:
-
During Rollover with the changed first Load port (LP), PCC.NET checks for the Doc Lock status for the existing first Load port present in the Route Details (Now) panel. If the current port has already been Doc Locked for any B/L associated with the Bookings present in the set, PCC will not allow you to proceed with the rollover. Else, PCC.NET will accept any valid location as the first load port and allow you to submit the rollover.
-
During Rollover with the changed last Discharge Port (DP), PCC.NET accepts any valid location as the last Discharge Port.
-
During actual Mass Rollover, following happens in PCC.NET:
-
PCC.NET does not check whether the changed port pair (LP-DP) exists in the same Contract number or not, hence there might be a mismatch, which should be resolved after rollover using SAVE or REFRESH RATE FROM CONTRACT for the corresponding Booking.
-
PCC.NET changes the Booking Status Accepted back to Requested after Rollover. More on Booking statusMore on Booking status.
-
Draft, For Space Checking or Requested status: Rollover does not change the Booking status, hence it remains as it is.
-
Accepted status: Rollover changes the Booking status to Requested.
-
Reconciled status: Rollover does not change Booking status, hence it remains as Reconciled.
Details on FMC filing requirement for changing the last DP from Non-US to US territory during RolloverDetails on FMC filing requirement for changing the last DP from Non-US to US territory during Rollover
-
During actual Mass Rollover, PCC.NET does not validate FMC data.
-
During Mass Rollover, if a Booking was in Accepted/Reconciled status and last DP changed from US to Non-US territory, the previously entered FMC details remain within PCC.NET but is of no use.
-
During Mass Rollover, if a Booking was in Accepted status and the last DP changed from non-US to US territory, after Rollover, it changes to Requested. Henceforth when you try to change the Booking Status from Requested to Accepted, PCC.NET validates the presence of FMC Documentation within the Booking. If missing, a warning message appears during leg approval, informing that FMC filing is not yet done for the Booking and asks your agreement whether to proceed or not. If you confirm, PCC.NET approves the leg, but keeps the Booking in Requested status for which FMC documentation is not available. If you disagree to proceed, the selected route leg is not approved.
-
During Mass Rollover, if a Booking was in Reconciled status and the last DP changes from non-US to US, rollover does not check for the availability of FMC documentation. Rather, PCC.NET checks its availability during Route Leg approval for that Booking. In absence of FMC documentation, Route Leg approval is denied.
-
If Rollover does not change First LP or Last DP, there is no impact on FMC details retrieved during Refresh Rate from Contract.
Refreshing Rate from Contract after Rollover - Retrieving FMC informationRefreshing Rate from Contract after Rollover - Retrieving FMC information
-
After Rollover from a non-US port to an US port, FMC details are retrieved and selected from Contract by checking the availability of FMC details hierarchically (that is, first Booking level, then Cargo level, and lastly Revenue level in the FMC Details dialog box).
-
After Rollover from an US port to another US port, existing FMC details are deleted first and the new details retrieved from Contract are applied by checking the availability of FMC details hierarchically.
- PCC.NET updates the Booking Route as following:
- Only the changed leg gets updated.
- Rows which are not changed remain unchanged.
- Rows which have changed are updated from Route Details (Now) to Route Details (Should).
- While updating, previous row is deleted and new row is created.
- Route Status gets updated as Not approved for those leg(s) which were changed. An e-mail notification is sent to the Approver for approving the leg which was changed.
- PCC.NET retains the Booking Customer, Cargo, Revenue information unaltered.
-
After Rollover, previous Rate becomes invalid and PCC.NET does not match Revenue information automatically. Hence, you must manually click REFRESH RATE FROM CONTRACT in the Booking to sync the Revenue information of Booking with Contract. All the previously associated charges get deleted in this process and new charges associated with the Booking Cargo are inserted. However, this does not impact the Supplementary charges (which were manually added in Booking); those remain unchanged.
- After successful Rollover of the Booking if you click SAVE, PCC.NET first checks whether the changed port pair (LP-DP) exists within the same Contract Number or not:
- If the Port Pair does not exist:
- If the Port Pair exists:
- After successful Rollover of the Booking, if you click REFRESH RATE FROM CONTRACT, PCC.NET first checks whether changed port pair (LP-DP) exists within the same Contract number or not:
- If the Port Pair does not exist:
- If the Port Pair exists:
-
PCC.NET updates the Booking with the changed Port pair (LP-DP) IDs so that it becomes in sync with the Contract in that respect.
-
Then PCC.NET checks the following three validations. In case, any of these validations fails, PCC.NET asks you to add the same set of Make, Model within the new LP-DP under the Contract and quit the Refresh Rate operation. You can update the same within the Contract and come back and perform Refresh Rate again.
-
Whether this new Port pair contains same set of Make/Models present with the Booking.
-
If it is a generic Make/Model and not replaced by actual Make/Model.
-
If it is a generic Make/Model and replaced with actual Make/Model, PCC.NET checks whether the new Port pair contains the same set of generic Make/Models which were referenced into the Booking before replacement with actual Make/Model.
-
Perform Refresh Rate operation. The Cargo, as well as Revenue information, are refreshed and become in sync with respect to the new Port pair (deleting the previous revenue information). But, Supplementary charges (charges manually added in Booking) do not get deleted and remain unchanged.
B/L Operation after Booking Rollover:
- After a successful Booking rollover, PCC.NET automatically rolls over the related B/Ls without any user intervention. Consequently, a Booking log mentioning the B/L rollover gets created. If, however, the B/L rollover process fails even after a successful Booking rollover, Documentation users must initiate the B/L rollover. In this case, the Bill of Lading user needs to save the Bill of Lading or click ROLLOVER, following which the rolled-over route is inherited from the Booking to the Bill of Lading.
- During B/L Rollover, B/L does not check for any discrepancy between its Revenue Information with Contract's Revenue information.
- You must manually check the Revenue information in B/L and correct the same accordingly. This implies, if you perform REFRESH RATE FROM CONTRACT in B/L, PCC.NET may restrict you to update the B/L Revenue information if Revenue of the rolled over LP-DP combination does not exist in the corresponding Contract. In order to keep the Revenue information updated in the B/L, you must first update the new LP-DP combination and Revenue information in the associated Contract.
- During Doc lock or Test Doc lock, if PCC.NET finds any discrepancy between B/L Revenue and Contract Revenue, you are warned and advised to correct the discrepancy. But, the process of Dock lock does not stop for the particular Vessel, Voyage, and LP combination.
Who will receive e-mail notification when an accepted Booking is rolled over?
- An e-mail is sent to intimate the respective Voyage Controller/Area Manager (who last updated the Booking leg during approval) about the rollover of a Booking in Accepted status.
- If the export side port is doc locked during rollover impacting a Line or PCL leg, an additional e-mail is sent to the recipients registered in PCC.NET against the Discharge Port (DP) of the old leg. For Feeder leg, if the preceding Mother Vessel’s export leg is doc locked, the e-mail notification is sent to recipients registered against the Feeder leg’s DP. If no e-mail recipient is registered in PCC.NET against a DP, the email is sent to a default recipient registered irrespective of the DP.
The e-mail recipients are registered in the Subscription/Distribution Maintenance (SPEMW03) screen.
|
|
|
Clicking this button deletes the last the last leg of the route.
|
are described below.