Back Forward

Introduction

Introduction


Booking is the process of reserving space on a PCC Vessel and Voyage for shipping Cargo, in advance. Customers request for space confirmation declaring the Port of loading and discharging, type of Cargo, its Weight, and Volume. The information received is processed by MOL Users and a Booking number is given to the Customer.

All Customers who wish to book a Cargo shipping with MOL require a prior Contract with MOL stating the basic shipment information, such as the Contract type, Main Customer and Sales Person of the Contract, validity period of the Contract, Origin and Destination of the Booking, Cargo Type, Make and Model. Any one of the Booking Customers must be present in the associated Contract. The Contract must be valid, non-expired and accepted by the Customer. Moreover, the Estimated Time of Departure (ETD) from the First Load Port, of the concerned Vessel and Voyage must be within the Contract’s validity period.

Types of Booking

A Customer can send a Booking request using any of the following means of communication:

Based on how a Booking request is received in PCC.NET, the process of creating PCC.NET Booking varies as follows:

User-created Booking

For Booking requests placed through E-mail, Phone Call and Fax, you (as the Booking user) can directly create the Booking from the customer’s Contract with MOL. You can create a Booking from the Create/Update Booking (OPBKW02) screen.

Details on how to create a Booking from Contract.

User-created Bookings can mainly be categorized into the following two types:

Notes:

EDI Booking

Booking requests that are received through EDI are automatically created in PCC.NET, with default indicative dataindicative dataData received through EDI that does not match with the actual data defined in PCC.NET., in Draft status. Contract No may not always be available in such Booking requests. Thus, as a Booking user you must assign a Contract number for the respective Customer, Port pair, Make and Model and update its information after replacing the default indicative data by the desired actual data. You can search for the Booking using the Search Booking (OPBKW01) screen and update the information.

Details on how to update an EDI Booking.

Web Booking from RoRo Website

Customers send Web Booking Requests from the RoRo Website that is saved in PCC.NET in Draft status. Similar to an EDI Booking, these Web Bookings may also have actual data or some default data for a Booking.

Contract Number may not always be available in such a Booking request. Thus, as a Booking User, you must assign a Contract number for the respective Customer, Port pair, Make and Model and update its information after replacing default indicative data by the desired actual data. You can search the Booking using the Search Booking (OPBKW01) screen and update the information.

Details on how to update an Web Booking.

Space Charter In/Out Booking

Some of the Booking in PCC.NET may involve a third party carrier (for example, NYK Lines). These types of Booking are categorized in PCC.NET as following:

Life Cycle of a Booking

A Booking matures stage by stage, starting as a Draft and ending with its completion and reconciliation with the corresponding B/L. The status of a Booking changes based on the information entered and user discretion. Booking statuses also vary based on the Booking type.

Click herehere to read more about the different statuses of a Booking.

Customer-Requested Booking:

  • Draft: Indicates the initial status of the Booking. It means that you have not provided all required information required for Booking creation.

  • Requested: Indicates all required information is available in the Booking and it is ready for Route leg approval. After you select this status, you cannot change it back to Draft.

  • Accepted: Indicates Bookings whose all Route legs have been approved and all the necessary checks are passed. PCC.NET changes the status to Accepted after all necessary checks are validated and all route legs of the Booking are approved. You can attach Model vessel to the Booking when the Booking is in this status. If required, you can provide extra information after the Booking is accepted. At this stage, you need to also send the Booking Confirmation Note to the Customer and Sales Person.

  • Declined: Bookings that are rejected by the Approver on behalf of MOL. A Booking may be declined for a number of reasons when it is in Requested status. If the Voyage Controller rejects any leg and you (as the Booking user) are unable to find any alternate route, you can change the Booking status to Declined. You need to send e-mail to the concerned users about the Booking being declined.

  • Cancelled: Indicates Bookings that are cancelled by customer to terminate the Booking request. In case of a Customer-requested Booking, you need to send e-mail to the concerned users about the Booking cancellation. For a Space Checking Booking, PCC.NET does not send e-mails.

  • Reconciled: After creation of the respective B/L in Complete status, you can perform the Mass Reconciliation process to make the Booking Reconciled. Reconciliation between Booking and B/L is done based on their Units of Cargo associated with the concerned Port.

 

Space Checking Booking:

  • Draft: Indicates that all information required for Booking creation is not yet entered in the Booking.

  • For Space Checking: Indicates that the data entry is complete for the Space Checking Booking.

  • Cancelled: Indicates that the Voyage Controller has cancelled the Booking.

After you convert Space Checking Booking to a Customer-requested Booking, the status of the Booking follows the behavior of the Customer Requested Booking.

Different Types of Customers in Booking

Customers who play a role in the Booking creation process:

Initiator or Shipper is required for saving a Booking with status as Requested or Accepted.

PCC.NET Booking Functions

A user with appropriate access rights and privileges can perform the following functions in the Booking module of PCC.NET:

Click on each function to navigate to the corresponding screen.

 

                                                                                                                                             Return