`Back Forward

View Contract (OPCNW03) > Create/Update Booking > Field Descriptions

Create/Update Booking - Field Descriptions


This screen is used to create and maintain basic information of a Booking.

This option is available for a Customer-Requested Booking only. The status of the corresponding Booking must be Requested, Accepted, or Reconciled.

Based on the action you want to perform, the functionality of few fields, links, and buttons differ, which is mentioned below.

For a description of additional icons, buttons, fields and links appearing on this screen, see Common Interface Controls.

Field

Description

Header panel: Basic information of the PCC Booking.

Buttons

BOOKING LOG

Button to view both manual and auto-generated log entries of the corresponding Booking in the Booking LogBooking Log pop-up.

Field

Description

Code

Booking transaction code.

Field

Description

Manual log

CHG

User enters any message in the Add Transaction Log pop-up.

System-generated log

ADD

NEW BOOKING CREATED.

STC

BOOKING STATUS CHANGED FROM <Old Status> TO <New Status>.

CUA

NEW CUSTOMER <Customer Name>ADDED.

CUD

CUSTOMER <Customer Name> REMOVED.

CUU

CUSTOMER <Customer Name> MODIFIED.

RVA

NEW <Charge> CHARGE ADDED.

RVD

<Charge> CHARGE REMOVED.

RVU

<Charge> CHARGE MODIFIED.

 

Remarks

Remarks entered using the Add Transaction Log dialog box. A maximum of 4000 characters can be entered.

User

User name of the Booking user who saved the previous log.

Organization Description

The default name for the physical Office of the Booking user.

Email Address

Email address of the Booking user.

Phone

Phone Number of the Booking user.

Time Stamp

Date and time of log entry.

CLOSE

Button to close the dialog box.

  • Manual Log: When you modify a Booking and save the changes in the Create/Update Booking (OPBKW02) screen, PCC.NET opens the Add Transaction LogAdd Transaction Log dialog box where you can specify the details of the change in the Remarks field and click SAVE LOG. PCC.NET prompts to add a manual log only while saving any changes in the Booking details without change of status for any Accepted or Reconciled Booking.

If validation errors are not encountered, PCC.NET saves the transaction log information,

which you can view later in the Booking Log dialog box by clicking BOOKING LOG in the Booking Header.

  • Auto-generated Log: PCC.NET automatically saves the log during different stages of Booking creation.

Conditions when PCC.NET create Booking log automaticallyConditions when PCC.NET create Booking log automatically

PCC.NET enters an automatic log in case of the following:

  • Initial Booking creation

  • Change in Booking status

  • Any change in Customer details

  • Any change in Rate

  • Any Cargo Added/Removed/Modified

  • BCN Report generation

Disabled while you are adding information to a new Booking.

Booking log helps to track changes in a Booking for future references.

The drop-down list values are defined in the Code Definition (ADCMW02) screen (domain= XNS_CODE, for development usage only, by PCC.NET Administrative users).

B/L & INVOICE

Button to view what all B/L(s) and invoices that are associated with an existing Booking using the B/L & InvoiceB/L & Invoice pop-up.

Disabled if B/L is not available for the Booking.

SHIPMENT PICS

Button to display the physical Office, E-mail ID and Phone Number of the shipment contact person (PICs) for a Booking, and its associated B/L and Invoices (if any). The information is displayed in the Shipment PICsShipment PICs pop-up.

 

Field

Description

Item

Identification for Booking, B/L or Invoice.

Number

Associated number for the Booking, B/L or Invoice.

Status

Associated status of the Booking, B/L or Invoice.

Office

Associated name of the physical office, in case of the Booking, B/L or Invoice. The office in each case, is as follows:

  • Booking :It is the Booking Office

  • B/L: It is the Document Entry Office

  • Invoice: It is the Invoice Office.

PIC Email

Email address of the PIC.

The details of a PIC are displayed based on certain conditions. Click herehere to know more.

Booking PIC

B/L PIC

Invoice PIC

  • For Draft status: User who created the Booking.

  • For Other statuses: User who first updated the Booking from Draft to Requested.

  • For EDI created B/Ls: DOC entry office user.

  • Manually created: User who created the B/L.

  • C/A: User who created the C/A.

  • For invoice in Draft Status: User who created the Invoice.

  • Manually created: ser who completed the Invoice

  • C/A: User who cancelled the Invoice

PIC Phone

Phone number of the PIC.

The details of a PIC are displayed based on certain conditions. Click herehere to know more.

Booking PIC

B/L PIC

Invoice PIC

  • For Draft status: User who created the Booking.

  • For Other statuses: User who first updated the Booking from Draft to Requested.

  • For EDI created B/Ls: DOC entry office user.

  • Manually created: User who created the B/L.

  • C/A: User who created the C/A.

  • For invoice in Draft Status: User who created the Invoice.

  • Manually created: ser who completed the Invoice

  • C/A: User who cancelled the Invoice

 

 

Disabled if an active B/L is not available for the Booking.

The PICs for Booking are displayed considering following conditions:

  • For Draft status: User who created the Booking.

  • For Other statuses: User who first updated the Booking from Draft to Requested.

CANCEL

Button to cancel the entries and navigate back to the Search Booking (OPBKW01) screen.

If there is any unsaved change, a warning message appears when you click this button asking you to confirm the cancellation '100022-COM-Data is not saved, do you want to proceed?'.

SAVE

Button to save the changes you make in the Booking.

Create/Edit mode:

When you click this button, Add Transaction LogAdd Transaction Log dialog box is displayed to specify the changes you made in the Booking, so that PCC.NET can save the log entry in the Booking log.

PCC.NET considers the booking to be Used Car Booking if commodity code for any associated Cargo falls within list of domain items defined in the Code Definition (ADCMW02) screen (domain=USED_CAR_CMD_DOMAIN), for example, N07. In rest of the cases, PCC.NET considers it as New Car Booking.

Copy mode:

When you click this button, a new Booking number is generated.

Notes:

  • Mandatory information required to save a Booking and change its statuses
  • Conditions to accept a Booking
  • How PCC.NET checks for duplicate BookingsHow PCC.NET checks for duplicate Bookings

    Duplicate Booking check is done during following status changes when a similar kind of Booking exists in Requested, Accepted, and Reconciled status:

    • Draft to Requested: When you complete entering all Booking information and try to change the Booking status by clicking SAVE.

    • Accepted to Requested: For example, when you change Cargo, Voyage or Route information in a Booking in Accepted status.

    • Requested to Requested: For example, when you change Booking data keeping its status unchanged to Requested.

    It checks for duplicate Bookings based on following Booking parameters:

    • LP-DP

    • Make/Model

    • Units (along with Unit of Measurement)

    • All Customers (Initiator, Shipper, Forwarder and Consignee)

    When PCC.NET finds duplicate Bookings, it displays a warning message with the option to proceed on your confirmation.

  • Validations that PCC.NET checks internally while you save a BookingValidations that PCC.NET checks internally while you save a Booking

    PCC.NET checks the following validations when you try to save the Booking and display errors if they fail:

    • Booking date must be before or on the date of ATD/ETD at the first Load Port (applicable for PCL/Line transport modes)

    • Customer (Initiator, Shipper, Forwarder, Consignee) in a Booking information must not have been deleted.

    • Doc Entry Office and Doc Issuing Office must not have been deleted.

    • For the first leg of Route From Location (LP) must be same as the Load Port (PR). Similarly, for the last leg of Route To Location (DP) must be same as the Discharge Port (PD).

    • Location set as From Location (LP) or To Location (DP) must not be Inactive and not deleted from the selected voyage (if any).

    • ATA/ETA value for the Arrives on Port should be later than the ATD/ETD of the Departs on Port.

    • From Location (LP) and To Location (DP) has not been deleted from the selected voyage.

    FMC Details-related Checks:

    Before associating the FMC details, PCC.NET checks the following conditions and displays relevant warning messages requiring your acceptance if any of the following fails. PCC.NET associate the FMC document with the current Booking only after you accept the warning.

    • If Departs On (ETD) of the first port of Booking is before or on the Effective Date of FMC Filing, PCC.NET displays a warning that associated FMC file is not yet effective for the first port ETD.

    • If Departs On (ETD) of the first port of Booking is after or on the Expiry Date of FMC Filing, PCC.NET displays a warning that the associated FMC file has expired for the first port ETD.

    • If the day count between Expiry Date of FMC Filing and Departs On (ETD) of the first port of Booking is within 10 days, PCC.NET displays a warning that expiry date of FMC Filing is getting close.

    The first port ETD is Departs On (ETD) of first leg sequence of Route of the Booking. This first port ETD is shown in the FMC Details dialog box as the Sail Date.

Fields panel: Basic information of the PCC Booking.

Booking No.

PCC Booking number. It is an 11-character number generated out of a sequence with minimum value 18000000001 and maximum value 1999999999. The number will contain 10 digits, numbered in sequence, and a check digit at the end.

Format of Booking Number:

Booking No (11 digits) = 10 digits from Booking Number Sequence + 1 Check digit.

Examples:

  • Booking No (18000000011) = from Sequence (1800000001) + Check Digit (1)

  • Booking No (18000000027) = from Sequence (1800000002) + Check Digit (7)

Logic of check digit generation in PCC.NET Booking:Logic of check digit generation in PCC.NET Booking:

  1. Obtain the 10-digit Booking Number generated out of the Booking Number sequence.
  2. Get Booking Number digits one by one and multiply with Power (2, [digit position] -1) and loop till the last digit.
  3. Add the calculated values from Step-2 for all 10 digits.
  4. Get the total value from step-3 and find the Mod values successively first with 11 then with 10.
  5. Value obtained from step-4 will be the check digit.
  6. Take 10 digit Booking Number from the Booking Number sequence and then concatenate the check digit (obtained in Step-5 above) for getting the final Booking Number.

This field displays either New Booking (if Booking is still not saved) or the Booking Number (for a saved Booking). You can click the Booking No.  hyperlink to navigate to the View Booking (OPBKW03) screen, which displays the Booking information in Read-only mode.

Copy mode

This field displays New Booking until the Booking is saved. Once the details are saved, a new Booking number is generated.

General Details panel: Basic information of the PCC Booking.

In Copy Booking mode, relevant field information are populated from the source Booking No. You can edit the details if required and save the Booking information.

Alt Booking No.

Alternate Booking number corresponding to an EDI Booking. If not available it is represented by “-“.

Booking Date

Date on which the space is reserved in the PCC Vessel and Voyage.

Create/Edit mode:

The current system date is displayed as a default. You can change it to another date (future or past date) using the Calendar icon, but Booking date cannot be later than the ETD of the First Loading port.

Copy mode:

The current system date is displayed as a default, irrespective of the Booking Date for the source Booking.

Booking Office

The organization where MOL accepts the Booking request. By default, the current Booking user's organization is set as Booking user's organization. You can change the organization code by entering 6-character organization code or the organization name.

This field has the Auto-complete feature, which helps to populate the full organization name as you start typing the organization code. After you select the appropriate organization from the list of organizations, the name of the organization appears in this field.

An EDI Booking is loaded with dummy Booking office as EDIOFC. You must update it to a valid Booking office before saving the Booking.

Doc Entry Office

The entry organization of the Bill of Lading. The field will be Auto-populated from the Location Master (RFLCW10) if Documentation entry organization is predefined for the Booking Load Port. You can change the organization code to any organization by entering 6-character organization code or name.

This field has the Auto-complete feature, which helps to populate the full organization name as you start typing the organization code.

You cannot modify the Doc Entry office of a Booking if you have been assigned with the Update Booking Doc Entry Office role type with Update Booking Without Revenue system action and delegation as Doc Entry Office.

Doc Issuing Office

The issue organization of the Bill of Lading. The field will be Auto-populated from the Contract or from the Location Master (RFLCW10) with Booking Load Port. You can change the organization code by entering 6-character organization code or organization name. This field has the Auto-complete feature, which helps to populate the full organization name as you start typing the organization code.

Doc Issuing Office data is not refreshed if a Contract is modified after Booking creation.

Status

Drop-down list to select the Booking status, which vary based on the Booking type:

Statuses available for Space Checking Bookings:

  • 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.

 

Statuses available for Customer Requested Bookings:

  • 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.

Copy mode:

Click to know about the statusClick to know about the status.

  • 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.

  • Cancelled: Indicates Bookings that are cancelled by Customer to terminate the Booking request. In case of Customer-requested Bookings, you need to send e-mail to the concerned users about the Booking cancellation.

 

Initially, a Customer-Requested Booking is created in Draft status. After entering all the required information, you can manually change the status to Requested. Once the Booking status becomes Requested, you cannot change back the status to Draft. Booking status becomes Accepted automatically when the required information and all the Route legs are approved. You can also manually change the status Requested to Accepted. If Approver rejects any leg, the Booking remains in Requested status. Once Booking status becomes Accepted, you cannot change it manually back to Requested.

A Space-Checking Booking is also at first created as Draft. After data entry is complete, you can change the status to Space Checking. Once, you convert Space Checking Booking to a Customer Requested Booking, the status of the Booking follows the behavior of the Customer-requested Booking.

Notes:

  • In Edit mode, the values available in the drop-down list for selection are based on the present status of the Booking for each of the Booking types. Read moreRead more.

    Booking Type

    Current Status

    Values Available for Selection

     

    Space Checking

    Draft

    • Draft
    • For Space Checking
    • Cancelled

    For Space Checking

    • For Space Checking
    • Cancelled

    Customer Requested

    Draft

     

    • Draft
    • Requested
    • Cancelled

    Requested

    • Requested
    • Accepted
    • Declined
    • Cancelled

    Accepted

    • Accepted
    • Cancelled

    Reconciled

    • Reconciled
    • Cancelled
  • The drop-down list values are defined in the Code Definition (ADCMW02) screen (domain= BKG_STATUS, for development usage only, by PCC.NET Administrative users).

  • Booking status Accepted automatically changes to Requested after Booking Rollover.

Contract No.

The identification number for a Contract associated with the PCC.Net Booking. Auto-populated from the corresponding Contract. Read-only.

Create/Edit mode:

  • You can enter or change this value for EDI Booking and switch the Contract type from Agreement with Brokers to Agreement with Broker Customers. You can click and select a Contract from the Find ContractFind Contract dialog box. It displays all the valid Contracts containing Cargo and active Port pairs that match with the currently selected Booking.

    Field

    Description

    Find Contract...

    The list of Contract Numbers are populated based on the currently-selected Cargo and active PR-PD information.

    Contract No

    Contract with same Make, Model and Port pair that match with the current Booking details.

    Contract Name

    Name of the Contract.

    Main Customer Name

    Contract customer.

    Effective Date

    Effective date of the Contract.

    TD of First Loading Port that must be within the validity period.

    Expiry Date

    Expiry date of the Contract.

    TD of First Loading Port that must be within the validity period.

    SELECT

    Button to accept the Contract you select.

    CANCEL

    Button to close the dialog box.

  • For EDI Booking, you can re-select the Contract number before a B/L is created against that Booking. If an EDI Booking is in Accepted status and the associated Contract number is changed for that Booking, the status of that Booking changes to Requested once again.

  • For switching Contract type from Agreement with Broker to Agreement with Broker Customers, you can specify the Contract number in this field. You can re-select a Contract number until the Booking status becomes Requested.

An EDI Booking cannot be associated with a Contract if the Port-pair has been deleted. Also, while selecting the Contract No. to switch the Contract type from Agreement with Brokers to Agreement with Broker Customers, PCC.NET does not display the deleted Port pairs in the Find Contract dialog box.

Copy mode:

You can change the Contract number only when you have saved the Booking details, and you want to switch the Contract type from Agreement with Brokers to Agreement with Broker Customers.

For Space Checking

Drop-down list to indicate if the Booking is meant for space checking in a vessel. While creating a Booking from a Contract you can select the value Yes (Space checking) or No (Customer Requested) accordingly. Default is No, which indicates that the Booking is Customer-requested. While editing a Booking's information, this field becomes Read-only.

More on Booking TypesMore on Booking Types

  • Customer-Requested: Customer-initiated Booking details are created for specific Customers with valid, complete and non-expired Contracts existing in PCC.NET.

  • Space Checking: Space Checking Booking details are forecasted based on historical business, assuming that the Booking for space checking will materialize into a Customer-Requested Booking. These are created in PCC.NET with minimum information on the basis of long termlong term Long-term Cargo Forecast: Cargo volume to be booked for MOL for maximum 1-3 months’ period in future based upon the information from customers or the result in the past. and short termshort term Short-term Cargo Forecast: Cargo volume to be booked for MOL for about 1 month period in future based upon the information from customers or the result in the past. cargo forecasts. Once Customers send the actual Booking request, the Booking details are converted to a Customer-Requested Booking. A Space Checking Booking helps Voyage Controllers to foresee the space allocation in a Vessel and optimize the available Vessel space to the fullest extent.

Notes:

  • Both types of Booking can be completed only from valid Contracts.
  • You can search for a Booking detail using the Search Booking (OPBKW01) screen.
  • During checking space utilization, PCC.NET considers both above the types of Booking for a specific Vessel and Voyage combination. This maximizes the Vessel space utilization and hence, profitability.

 

Transshipment

Check box that indicates the presence of Transshipment leg in the Booking. Automatically selected during Booking Route creation. Read-only.

EDI Booking

Check box to indicate if the Booking is created with the data received from EDI or from the RoRo Website. Read-only.

More about EDI BookingMore about 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.

Copy mode:

Deselected even if initial source Booking is an EDI Booking.

S/C OUT

Check box to indicate if a third party shipping company (as Shipper) has requested to ship their Cargo in a MOL Vessel. Auto-populated from the Customer (RFCSW01) screen and Read-only.

PCC.NET treats Bookings with this check box selected as S/C Out booking and with this check box cleared as S/C In Booking.

  • Space Charter (S/C) In BookingSpace Charter (S/C) In Booking

    In such Bookings, MOL requests a third party Carrier to take its cargo on MOL’s behalf. In this scenario, MOL space charters to a third party vessel. All the necessary Bookings and B/Ls are created for S/C IN.

    S/C IN Bookings have the following features:

    • During Booking creation, S/C IN voyage schedule should be present in PCC.NET. When Booking user selects the particular schedule in the Booking route, PCC.NET internally will mark this Booking as S/C IN.

    • Space checking is not required for corresponding Line leg.

    • Voyage Controller/Area Manager with appropriate role and delegation can approve the legs.

  • Space Charter (S/C) Out BookingSpace Charter (S/C) Out Booking

    Third party Carriers often request MOL to accept its cargo on its behalf. In such a scenario, the third party shipping company space charters out to a MOL vessel. All the necessary Bookings and B/Ls need to be created for S/C IN cases.

    S/C Out Bookings have the following features:

    • The third party customers are marked as S/C Out in the Customer (RFCSW01) screen. A Booking is treated as S/C Out Booking when the corresponding S/C Out check box of the Booking Shipper is selected.

    • S/C Out Booking can only be created from a valid Contract.

    • S/C Out has to be considered for space utilization purpose, Manifest preparation and Accounts Receivables purpose.

    • Space checking will be needed for corresponding Line leg. Voyage Controller/Area Manager with appropriate role and delegation can approve the legs.

Japanese Freight Treatment (GGN)

Check box to indicate if freight treatment code for Japan is applicable for the Booking. PCC.NET uses only GGN as the freight treatment code for Japan. Auto-populated from the corresponding Contract. Read-only.

If the value for GGN is changed in the Contract after Booking creation, PCC.NET fetches the latest status of GGN from the last completed version of the Contract, so that Booking user can see the latest GGN value in the screen.

FDPS

Display the payment terms associated with the selected Booking. Auto-populated from the corresponding Contract. Read-only.

If the value for FDPS is changed in Contract after the Booking creation, PCC.NET fetches the latest status of FDPS from the last completed version of the Contract so that you can see the latest value of it on the screen.

PCC.NET again fetches the latest status of FDPS from the last completed version of the Contract on clicking SAVE, to ensure that the latest value is always saved.

FDPS stands for Fixed Day Payment System, that is, a fixed day of the month on which Customer makes payment against the Invoice(s). Invoices, against which Customers make payment as per their fixed payment day, are referred as FDPS Invoice. While creating any Booking for such Customer, PCC.NET automatically populates the Customer's fixed payment day in the FDPS Day field of the Booking screen.

Customer Details panel:

This panel consists of Initiator, Shipper, Forwarder, and Consignee tabs. When you open the screen, Shipper tab remains open.

Notes:

  • By default, Main Customer of Contract is populated as Shipper. You can also add additional Customer details to Booking.

  • At least, one of the Booking customers (Initiator/Shipper/Forwarder) should be either the Main Customer or the Affiliated Customer in the associated Contract. However, this is not valid when you create a Booking from a Spot Rate Guideline Contract; you can select any customer (even dummy) as the Booking customer using the Auto-complete feature. If the Booking is being created from SRG Contract ‘Dummy Customer’ information is displayed as Shipper, which needs to be changed in the Booking.

  • Cross Reference Customer is not allowed during new Booking creation. If the Booking is already created with any Customer and later on that Customer is marked as Cross Reference, PCC.NET allows to save that Booking as it is already saved with that Customer. You cannot even update a Booking with a Cross Reference Customer if it has been earlier created with a non-Cross Reference Customer.

  • You can select any of Shipper, Forwarder, or Consignee as Initiator by selecting the respective check box.

  • PCC.NET does not accept a Booking with dummy Customer. Booking created from Spot Rate Guideline may have a dummy Customer. Booking can be in Draft or Requested status with Dummy Customer. But a valid customer is needed for a Booking to be Accepted.

  • At least, Initiator or Shipper is required to save a Booking as Requested or Accepted.

  • After you select a Customer, PCC.NET populates the remaining information from the Customer (RFCSW01) screen, which you can modify in the Booking.

  • Customer must be a valid customer (not deleted and not having cross reference number assigned against it) registered in Customer (RFCSW01) screen in PCC.NET.

  • In Initiator, Shipper, Forwarder, and Consignee tabs, you can select any Customer either from the list of values of Customer, or the Booking Customer dialog box which is displayed by clicking with the list of all affiliated customers. When you change the Initiator, Shipper, Forwarder, or Consignee from the Name LOV, a Warning pop-up appears to confirm the action.

  • For EDI Bookings, while editing the Customer information, Dummy Customer (9999997) is shown for Initiator, Shipper, Consignee, Forwarder, and Payer. For Non-SRG Contracts, Dummy Customer (9999999) is populated from the corresponding Contract but it cannot be saved.

 

Copy mode

All field information are populated from the source Booking No. You can edit the details if required and save the Booking information. On saving, PCC.NET checks if at least one of the Booking Customers (Initiator/Shipper/Forwarder) is either the Main Customer or the Affiliated Customer in the associated Contract.

Initiator

Initiator is the customer who initiates the Booking of a cargo for shipment to the final destination.

  • Name: Name and code of the Customer. PCC.NET accepts only registered and active customers. This field has the Auto-complete feature, which helps you to populate the customer as you type. You can also click to select a customer from the Booking CustomerBooking Customer dialog box. 

 Notes:

  • In EDI Bookings, a warning message is displayed to update the associated Customer Code when you edit Customer (Initiator) name. Additionally, PCC.NET displays a second warning message asking you to confirm if you want to change the associated Address and other information relevant to the new Customer. 
  • PCC.NET populates the following information, except the Sales Person, from the Customer Master, however you can modify these information. PCC.NET populates the sales person name from the corresponding Contract header, but you can modify it, if required.
  • Address: Postal address of the Customer.
  • Country: Country of the Customer. You can enter only countries registered in PCC.NET. This field has the Auto-complete feature, which helps you to populate the country as you type.
  • State: State of the Customer. You can enter only states registered in PCC.NET. This field has the Auto-complete feature, which helps you to populate the state as you type.
  • City: City of the Customer.
  • Post Code: Post code / zip code of the Customer.
  • Phone: Customer phone number.
  • Email: Customer e-mail address.
  • Fax: FAX number.
  • Sales Person: Name of the MOL sales person associated with the corresponding Customer. You can enter only registered Sales Person. This field has the Auto-complete feature, which helps you to populate the sales person as you type.

Shipper

The Shipper is the customer who sends a shipment after entering into a Contract with the Carrier, that is, the person or company who is usually the supplier or owner of the cargo shipped. The shipper need not be a registered exporter. He/she can also be a freight forwarder who transfers the cargo to the Carrier for shipment.

Notes:

  • By default, PCC.NET opens Shipper tab. Shipper information is required to save a Booking.
  • Name: Name and code of the Shipper. PCC.NET accepts only registered customers. This field has the Auto-Complete feature, which helps you to populate the customer as you type. You can also click to select a customer from the Booking CustomerBooking Customer dialog box. 
    • In EDI Bookings, a warning message is displayed to update the associated Customer Code when you edit Customer (Shipper) name. Additionally, PCC.NET displays a second warning message asking you to confirm if you want to change the associated Address and other information relevant to the new Customer. 

  • Initiator: Check box to mark Shipper in the Booking as the Initiator.
  • PCC.NET populates the following information, except the Sales Person, from the Customer Master, however you can modify these information. PCC.NET populates the sales person name from the corresponding Contract header, but you can modify it, if required.
  • Address: Postal address of the Customer.
  • Country: Country of the Customer. You can enter only countries registered in PCC.NET. This field has the Auto-complete feature, which helps you to populate the country as you type.
  • State: State of the Customer. You can enter only states registered in PCC.NET. This field has the Auto-complete feature, which helps you to populate the state as you type.
  • City: City of the Customer.
  • Post Code: Post code / zip code of the Customer.
  • Phone: Customer phone number.
  • Email: Customer e-mail address.
  • Fax: FAX number.
  • Sales Person: Name of the MOL sales person associated with the corresponding Customer. You can enter only registered Sales Person. This field has the Auto-complete feature, which helps you to populate the sales person as you type.

Forwarder

The Forwarder performs the same function as a Shipper, however, he does it on behalf of a number of Shippers. Precisely, the Forwarder is a person or company who organizes shipments for individuals or corporations to transport cargo from the manufacturer or producer to the final point of distribution.

Notes:

  • Name: Name and code of the Forwarder. PCC.NET accepts only registered customers. This field has the Auto-Complete feature, which helps you to populate the customer as you type. You can also click to select a Customer from the Booking CustomerBooking Customer dialog box. 

    • In EDI Bookings, a warning message is displayed to update the associated Customer Code when you edit Customer (Forwarder) name. Additionally, PCC.NET displays a second warning message asking you to confirm if you want to change the associated Address and other information relevant to the new Customer.  

  • Initiator: Check box to mark Forwarder in the Booking as the Initiator.

  • PCC.NET populates the following information, except the Sales Person, from the Customer Master, however you can modify these information. PCC.NET populates the sales person name from the corresponding Contract header, but you can modify it, if required.

  • Address: Postal address of the Customer.
  • Country: Country of the Customer. You can enter only countries registered in PCC.NET. This field has the Auto-complete feature, which helps you to populate the country as you type.
  • State: State of the Customer. You can enter only states registered in PCC.NET. This field has the Auto-complete feature, which helps you to populate the state as you type.
  • City: City of the Customer.
  • Post Code: Post code / zip code of the Customer.
  • Phone: Customer phone number.
  • Email: Customer e-mail address.
  • Fax: FAX number.
  • Sales Person: Name of the MOL sales person associated with the corresponding Customer. You can enter only registered Sales Person. This field has the Auto-complete feature, which helps you to populate the sales person as you type.

Consignee

The Consignee is the customer to whom the Carrier is supposed to deliver the goods at the destination. He is the person or company who is legally allowed to receive the cargo. In most cases the Consignee is the buyer of the cargo but not always. Consignee could be the agent nominated by the buyer or the buyer’s bank.

  • Name: Name and code of the Consignee. PCC.NET accepts only registered customers. This field has the Auto-Complete feature, which helps you to populate the customer as you type. You can also click to select a customer from the Booking CustomerBooking Customer dialog box. 

    • In EDI Bookings, a warning message is displayed to update the associated Customer Code when you edit Customer (Consignee) name. Additionally, PCC.NET displays a second warning message asking you to confirm if you want to change the associated Address and other information relevant to the new Customer. 

  • Initiator: Check box to mark the Consignee in the Booking as the Initiator.

  • PCC.NET populates the following information, except the Sales Person, from the Customer Master, however you can modify these information. PCC.NET populates the sales person name from the corresponding Contract header, but you can modify it, if required.

  • Address: Postal address of the Customer.
  • Country: Country of the Customer. You can enter only countries registered in PCC.NET. This field has the Auto-complete feature, which helps you to populate the country as you type.
  • State: State of the Customer. You can enter only states registered in PCC.NET. This field has the Auto-complete feature, which helps you to populate the state as you type.
  • City: City of the Customer.
  • Post Code: Post code / zip code of the Customer.
  • Phone: Customer phone number.
  • Email: Customer e-mail address.
  • Fax: FAX number.
  • Sales Person: Name of the MOL sales person associated with the corresponding Customer. You can enter only registered Sales Person. This field has the Auto-complete feature, which helps you to populate the sales person as you type.

Route Details panel

  • Adding a route leg is optional in Draft Status.

  • Before creating the route, you need to select the Departure On/After date. Later on, this date is used for selecting the ATD (when available) or ETD of the first Booking route. For the Leg beyond the second line, schedules with ATD or ETD later than the ATA or ETA of the Discharging Port of the last Leg needs to be derived.

  • You can create route from three different types of transport Category in PCC.NET: Line, Feeder and PCL. Based on the Category you select, the fields in this panel varies. Click here to know about the common restrictions and validations of the different transport categories.

  • Each route must have at least one Line leg.

  • For PCL and Feeder legs, you can add cost information optionally.

  • You can add legs only at the end of the Route (after the last leg).

  • Load and Discharge port should be valid locations.

    • ATA/ETA value for the Arrives on Port should be later than the ATD/ETD of the Departs On port.

    • Load and Discharge ports should not be deleted with respect to the selected voyage.

  • In case, the From Location (LP) selected in the route is deleted for a Voyage, the Loading Port Name, C/O and ATD/ETD will appear in red font and as strike-through. Similarly, if To Location (DP) present in the route is deleted for a Voyage, PCC.NET displays Discharging Port Name, C/O and ATA/ETA in red font and strike-through.

  • During saving the Booking, if a port present in the Booking route is deleted for a Voyage, PCC.NET displays an error message asking you to change the Route.

  • To create Booking and 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.

  • When the Booking legs are approved (and arranged for Feeder leg) and all mandatory information is entered, the Booking Status automatically changes to Accepted.

  • To let you easily distinguish Booking leg’s estimated date/time from the actual date/time, the ETD/ETA and ATD/ATA values are shown in different colors. ATD and ATA is shown in blue, whereas ETD and ETA in black.

Common restrictions and validations of the different transport categoriesCommon restrictions and validations of the different transport categories

  • If Feeder leg is present in the first leg of the Booking route or no Feeder Schedule exists for the entered feeder leg:
    • You must enter the probable ETD and ETA for a feeder schedule in the Booking. ATD and ATA will be updated during the feeder leg approval and will get reflected in the associated Booking Route after updating.
  • If Feeder leg is registered in the Feeder Service (OPBKW09) screen and it is not the first leg of Booking route:
    • At the time of creating the feeder leg, PCC.NET automatically calculates the probable ETD (sum of ATA/ETA of the previous leg and the waiting time) and ETA (sum of ATD/ETD of the feeder leg and the transit time) for that Feeder Schedule based on waiting time and transit time specified in Feeder Service (OPBKW09) screen.
    • You can also enter the ETD; PCC.NET, generates the probable ETA based on transit time specified in Feeder Service (OPBKW09) screen.

Validations for LINE:

  • Route can be created with both intended and firmed voyages.

  • Each route must have at least one Line leg.

  • You cannot keep Voyage name blank. It must be either an intended or a firmed voyage.

  • Only voyages with data entry status Complete are used for Booking route creation.

  • While searching the connecting vessels, PCC.NET considers and display the ATA or ATD first if it is present, else, shows ETA or ETD.

  • If you add a transshipment leg, PCC.NET automatically selects the Transshipment check box in the Booking Header section.

 

Validations for PCL:

  • PCL can be the first leg.

  • PCL leg can be present after a feeder leg (Burge/Truck) or before LINE leg.

  • If voyage schedule is available beforehand, you can enter voyage for PCL otherwise you can leave Voyage blank. You can only enter the DP, approximate ETD/ETA and select Category as PCL.

  • While searching the connecting vessels, PCC.NET considers and display the ATA or ATD first if it is present, else, shows ETA or ETD.

 

Validations for Feeder:

  • Feeder can be the first leg or after any other leg (PCL or LINE). In addition, Feeder leg can be between LINES.

  • Multiple feeder service based on multiple service providers for same LP-DP can exist. Priority setting in Feeder Service (OPBKW09) is mandatory. During Booking creation, PCC.NET selects the feeder service with higher priority.

  • If Feeder leg is present in the first leg of the Booking route or no Feeder Schedule exists for the entered feeder leg:
    • You must enter the probable ETD and ETA for a feeder schedule in the Booking. ATD and ATA will be updated during the feeder leg approval and will get reflected in the associated Booking Route after updating.
  • If Feeder leg is registered in the Feeder Service (OPBKW09) screen and it is not the first leg of Booking route:
    • At the time of creating the feeder leg, PCC.NET automatically calculates the probable ETD (sum of ATA/ETA of the previous leg and the waiting time) and ETA (sum of ATD/ETD of the feeder leg and the transit time) for that Feeder Schedule based on waiting time and transit time specified in Feeder Service (OPBKW09) screen.
    • You can also enter the ETD; PCC.NET, generates the probable ETA based on transit time specified in Feeder Service (OPBKW09) screen.

Copy mode:

All Route details are populated from the source Booking No. where the Booking legs are unapproved.

<Serial No.>

Sequential number of the record.

Load Port

First port of loading the cargo. Auto-populated from either the Contract's Place Of Receipt or From Port field. Read-only.

For EDI Bookings, this field may appear as text box initially. In such a scenario, you need to select the correct location code as the Load Port. MoreMore.

The EDI process may send the Place of Receipt (PR) and Place of Delivery (PD) descriptions instead of the corresponding codes as route information. So, when the EDI Booking is opened in Edit mode, you may see the LP and DP as text boxes. We have to select the proper LP and DP to complete the Booking. After the Booking is saved successfully, then onwards the LP and DP will appear as labels like in normal Bookings. And after changing the PR and PD, you need to change the route accordingly.

Discharge Port

Last port of discharging the cargo. Auto-populated from either the Contract's Place Of Delivery or To Port field. Read-only.

For EDI Bookings, this field may appear as text box initially. In such a scenario, you need to select the correct location code as the Discharge Port. MoreMore.

The EDI process may send the Place of Receipt (PR) and Place of Delivery (PD) descriptions instead of the corresponding codes as route information. So, when the EDI Booking is opened in Edit mode, you may see the LP and DP as text boxes. We have to select the proper LP and DP to complete the Booking. After the Booking is saved successfully, then onwards the LP and DP will appear as labels like in normal Bookings. And after changing the PR and PD, you need to change the route accordingly.

Departure On/After

Date of vessel departure. Initially, the current date is defaulted as Departure On/After date. Click the Calendar icon to select this date.

You should enter this date before route creation. It is used to select ETD of the first leg. ETD of first leg must be later than or on the Departure On/After date. You can edit this field even after Booking creation to find proper Vessel and Voyage of first leg.

Cut-Off Date

Terminal cut-off date. For some countries (like US), this date must be notified to the customer at the time of issuing Booking Confirmation Note. This field appears blank initially. You may click the Calendar icon to select this date.

From Location (LP)

The First Port of loading for the itinerary leg. A valid registered 7-character port. For the first leg, it is Auto-populated from Contract, and second leg onwards it is same as the previous Discharge Port. Read-only.

Notes:

  • For the first leg of Route, From Location (LP) will be same as the Load Port (PR).
  • From second leg onwards, From Location (LP) will be same as the To Location (DP) of the previous leg.

  • During saving a Booking, PCC.NET will check whether the location set as From Location (LP) is in active state or not.

C/O

Calling order of Port of Loading. In case voyage calls at a port more than once, this field indicates the sequence of call on which the cargo is loaded on the vessel.

Required except for Feeder vessels and PCL vessels that do not have schedule registration.

Departs On (ATD/ETD)

Actual or expected time of Departure at Load Port of the vessel associated to the currently selected leg. The ETD of the First Loading Port (for Pre-Carriage Line or Line) should be between the validity period of the associated Contract.

Based on the Category you have selected, this field varies as follows:

  • For Line, PCC.NET automatically populates this field from the Voyage Schedule based on the selection of vessel.

  • For PCL, if Voyage Schedule exists, PCC.NET automatically populates this field. If it does not exist, you must provide this value as this is a required field.

  • For Feeder, you must provide this value as this is a required field.

  • If Feeder leg is present in the first leg of the Booking route or no Feeder Schedule exists for the entered feeder leg:
    • You must enter the probable ETD and ETA for a feeder schedule in the Booking. ATD and ATA will be updated during the feeder leg approval and will get reflected in the associated Booking Route after updating.
  • If Feeder leg is registered in the Feeder Service (OPBKW09) screen and it is not the first leg of Booking route:
    • At the time of creating the feeder leg, PCC.NET automatically calculates the probable ETD (sum of ATA/ETA of the previous leg and the waiting time) and ETA (sum of ATD/ETD of the feeder leg and the transit time) for that Feeder Schedule based on waiting time and transit time specified in Feeder Service (OPBKW09) screen.
    • You can also enter the ETD; PCC.NET, generates the probable ETA based on transit time specified in Feeder Service (OPBKW09) screen.

To Location (DP)

Port of discharge for the itinerary leg. Port must be a valid registered 7-character port. This field has the Auto-Complete feature, which helps you to populate the relevant port as you type.

For the last leg of Route, To Location (DP) should be same as the Discharge Port (PD).

C/O

Calling order of Port of Discharge. In case, voyage calls at a port more than once, this field indicates the sequence of call on which the cargo is loaded on the vessel. This is a required field, except for PCL vessels without schedule registration and Feeder vessels.

Arrives On (ATA/ETA)

Actual or expected time of arrival at Discharge Port of the vessel associated to the currently-selected leg. Based on the Category you have selected, this field varies as follows:

  • For Line, PCC.NET automatically populates this field from the Voyage Schedule based on the selection of vessel.

  • For PCL, if voyage schedule exists, PCC.NET automatically populates this field. If voyage schedule does not exist, you must provide this value as this is a required field.

  • For Feeder, you must provide this value as this is a required field.

Category

Drop-down list to select the transport category for route creation. Available values are:

  • LINE (default): Select this value to mark the leg as Line in Booking. You need to enter LP/DP and Voyage information. Each route must have at least one Line leg.

    You may also search Line by Load Port/Discharge Port and Departure On/After date (if first leg is Line leg), or ATA/ETA of the Discharge Port of the last Leg. The search result shows Intended/Firmed voyages with ETA from that searched date onwards. Firmed Voyage Schedules, if available, top the list in the search result. After transformation of Intended Voyage to Firmed Voyage in Voyage Schedule, the Booking route information gets updated automatically. If there is any transshipment, PCC.NET searches earliest second vessel after ATA/ETA of first vessel.

  • PCL: Select this value to mark the leg as Pre Carriage for Line.

    Voyage schedule for PCL has to be selected during Booking creation. You have to enter the Discharge Port. Otherwise you can leave Voyage blank. You can only enter the Load Port, Discharge Port, approximate ETD/ETA and select Category as PCL. You can also optionally enter the associated PCL cost by clicking COST.

  • FEEDER: Select this value for feeder vessels.

    You can select the leg as FEEDER irrespective of the different transport mode used as feeder like Burge, Truck etc. For feeder, you should select the Category as FEEDER, enter the Discharge Port and ETD/ETA keeping Voyage blank. Voyage Name is entered later when the leg is approved and updated as Arranged by the Area Manager.

  • If Feeder leg is present in the first leg of the Booking route or no Feeder Schedule exists for the entered feeder leg:
    • You must enter the probable ETD and ETA for a feeder schedule in the Booking. ATD and ATA will be updated during the feeder leg approval and will get reflected in the associated Booking Route after updating.
  • If Feeder leg is registered in the Feeder Service (OPBKW09) screen and it is not the first leg of Booking route:
    • At the time of creating the feeder leg, PCC.NET automatically calculates the probable ETD (sum of ATA/ETA of the previous leg and the waiting time) and ETA (sum of ATD/ETD of the feeder leg and the transit time) for that Feeder Schedule based on waiting time and transit time specified in Feeder Service (OPBKW09) screen.
    • You can also enter the ETD; PCC.NET, generates the probable ETA based on transit time specified in Feeder Service (OPBKW09) screen.

If for a feeder leg, the corresponding Auto Approval Required check box is selected in the Feeder Service (OPBKW09) screen, PCC.NET automatically marks the feeder leg as Approved.

Notes:

  • Click here to know more about the common restrictions and validations of the different transport categories.
  • The drop-down list values are defined in the Code Definition (ADCMW02) screen (domain= BKG_RTCAT, for development usage only, by PCC.NET Administrative users).

COST remains disabled if you have been assigned with the Update Booking Doc Entry Office role type along with Update Booking Without Revenue system action and delegation as Doc Entry Office.

Voyage Name

Voyage name for the selected Vessel.

For LINE and PCL, click to select the voyage from the Connecting VoyageConnecting Voyage dialog box.

Field

Description

From Location (LP)

Load Port of the selected itinerary leg for which you want to select the connecting Voyage.

To Location (DP)

Discharge Port of the selected itinerary leg for which you want to select the connecting Voyage.

Voyage Name

Name of the connecting Voyage.

PCC Line

PCC Line of the Voyage.

From Location ATD/ETD

Actual or expected time of Departure at From Location (LP).

C/O

Call order at the port (LP) for that Voyage.

To Location ATA/ETA

Actual or expected time of Arrival at To Location (DP).

C/O

Call order at the port (DP) for that Voyage.

SELECT

Button to accept the Voyage.

CANCEL

Button to close the dialog box.

Notes:

  • For Line leg this field is required while requesting Booking, whereas for Feeder and PCL this field is optional. However, during approval, this field becomes required for PCL and the PCL Voyage can be an Intended Voyage.

  • For Feeder leg, a suggestive Feeder Vessel name can be entered. The Vessel name of the suggested Feeder is reflected in the Vessel field of the Feeder Mass Approval/Arrangement (OPBKW05) screen. The Area Management can update the Feeder Vessel and its Voyage while approving/updating the particular Feeder leg. During approval, the Voyage field is updated from the approval screen, which eventually gets reflected in the Booking route.

How does PCC.NET find connecting Voyages for a Vessel?

PCC.NET finds the connecting Voyages for a Vessel according to the following conditions:

  • The Voyages are in Complete status and are of either LINE category and LINE Voyage Type, or, PCL Category and PCL Voyage Type.

  • Voyages have a port call which has the Load Port (LP) in the Route Details panel and the port is marked as a Load Port.

  • The Load Port (LP) is not doc locked for the selected voyage. However, this condition can be overruled by users with Privileged Booking User Role and Booking Creation for Supplementary B/L system action.

  • Voyages have a port call which has the Discharge Port (DP) in the Route Details panel and the port is marked as a Discharge Port.

  • ATA/ETA of the previous Leg is before or on the ATD/ETD of the port call of the Line/PCL voyage.

PCC Line

PCC Line of the voyage to the currently-selected leg. Read-only.

PCC.NET populates this value for respective type of transport categories as per the following logic:

  • For Line, PCC.NET automatically populates this field from voyage schedule based on the vessel.

  • For PCL, this field is required if voyage schedule exists for PCL. In the absence of voyage schedule, this field remains blank.

  • For Feeder, this field remains blank.

Route Status

Approval status of currently selected leg: Not Approved/Approved/Arranged/Rejected. These statuses appear as hyperlinks.

Depending on the transport mode and your role and task delegationrole and task delegation, clicking the status hyperlink displays the Line Approval Update or PCL Approval UpdateLine Approval Update or PCL Approval Update or Feeder Approval UpdateFeeder Approval Update dialog box for approving/rejecting the corresponding route leg.

Field

Description

Feeder Mass Approval Update...

From Port, To Port

The PCC ports of departure and arrival. Read-only.

Vessel

Vessel to perform this leg of the journey. Read-only.

ETD (From)

Expected Time of Departure of vessel at From Port.

ETD is auto-populated from the Booking.

ETA (To)

Expected Time of Arrival of vessel at To Port. You can change this date if required using Calendar icon.

If PCC.NET finds a registered feeder for the "From Port" to "To Port" location and the entered ETD, ETA is auto-populated as per that registered Feeder Service Schedule. The ETA is also calculated based on the Transit Time mentioned in the Feeder Service.

Vessel

Vessel to perform this leg of the journey.

Voyage

Voyage Number. You can enter up to 5 characters.

Vessel and Voyage are free text fields. You can enter any Feeder Vessel, Truck or Burge or any other transporter when such transportation service is used for the Feeder leg.

ATD (From)

Actual Time of Departure of vessel at From Port. You can use the Calendar icon to select the date.

ATA (To)

Actual Time of Arrival of vessel at To Port. You can use the Calendar icon to select the date.

Route Status

Status of the approval for route leg:

  • Not Approved

  • Approved

  • Arranged

  • Rejected

Normally, during approval Feeder Transport Mode details may not be available, the Area Manager can simply approve the leg and come back later to provide these details and select the status as Arranged.

Buttons

SAVE

Button to save the route leg status based on selected Route Status.

CANCEL

Button to exit the dialog box without saving your updates.

Current Feeder Details

Booking#

Booking Number for which you want to approve the feeder details.

Shipper

Name of the associated shipper customer type.

Make

Maker of the cargo present in the Booking.

Model

Model name of the cargo present in the Booking.

Units

Number of cargo units present in the Booking.

Vessel

Vessel to perform this leg of the journey.

Voyage

Voyage Number.

ETD (From)

Expected Time of Departure of vessel at From Port.

ETA (To)

Expected Time of Arrival of vessel at To Port.

ATD (From)

Actual Time of Departure of vessel at From Port.

ATA (To)

Actual Time of Arrival of vessel at To Port.

Route Status

Current approval status of the route leg.

  • To approve Feeder legs, you (Area Manager) can select all the feeder legs which originated from and are destined to the same port pairs. For the respective vessel, voyage, ETD (From), ETA (To), ATD (From), ATA (To) and Route Status, if they have the same value in the selected feeder legs, that value gets displayed in the corresponding field of Feeder Mass Approval Update dialog box. In case, the selected feeder legs have different values for the respective vessel, voyage, ETD (From), ETA (To), ATD (From), ATA (To) and route status, the corresponding values in Feeder Mass Approval Update dialog box are left blank and you must enter those values before saving the approval details. PCC.NET displays the current values for the above mentioned fields against the selected legs just below the dialog box to be selected before applying new feeder details.

  • The Booking status automatically becomes Accepted if all route legs get approved and all Booking validations are passed. But if any essential information is missing, you must provide the required information and then change the Booking Status manually.

  • Similarly, if all legs are approved for a particular Booking and then the route status changes for the 'first' leg from Approved to Not Approved or Rejected, PCC.NET updates the Booking status back to Requested from Accepted. The change in Booking status happens only for the first leg and Accepted Bookings; it does not apply to a Booking in Reconciled status.

  • If a Booking is in Reconciled status and it’s Discharge Port (DP) falls under US territory, PCC.NET checks for the availability of FMC documentation during Route Leg approval for that Booking. In absence of FMC documentation, route leg is not possible and it shows error for FMC.

  • If all Bookings selected for Route Leg approval are in Requested Status and one/more Bookings have their Discharge Port (DP) falling under US territory without FMC Filing information, a warning message appears informing that FMC filing is not yet done for those Requested Bookings and will ask your agreement whether to proceed further for leg approval or not. On your approval, PCC.NET approves the legs, but keeps all those Bookings in Requested status for which FMC documentation is not available. If you disagree to proceed, however, the selected route legs are not approved.

  • If Feeder vessel and voyage values are updated in Feeder Approval process, the corresponding Load and Discharge VIN events for the earlier Feeder vessel and voyage get soft deleted.

 

Display of this dialog box differs for the PCL (with Voyage) or LinePCL (with Voyage) or Line category and PCL (without Voyage)PCL (without Voyage) category.

Field

Description

Voyage Name

Voyage Number. This value can be selected for PCL category when voyage schedule for PCL is not available. On selection of proper PCL Voyage, corresponding PCC Line is populated.

PCC Line

PCC Line of the voyage. Read-only.

Route Status

Status of the approval for route leg:

  • Approved

  • Not Approved

  • Rejected

Reason

Reason for rejecting the route approval request. It should be provided if status gets rejected. You can enter maximum of 4000 characters.

If you open this dialog box to update a record, Reason gets populated with previously saved reason. For multiple records, it remains blank. On saving, Reason is saved against all selected records.

Buttons

CANCEL

Button to exit the dialog box without saving your updates.

SAVE

Button to save the route leg status based on selected Route Status.

 

Field

Description

Route Status

Status values for the Line or PCL route leg approval are:

  • Approved

  • Not Approved

  • Rejected

Reason

Reason for rejecting the route approval request. It should be provided if status gets rejected. You can enter maximum of 4000 characters.

If you open this dialog box to update a record, Reason gets populated with previously saved reason. For multiple records, it remains blank. On saving, Reason is saved against all selected records.

Buttons

CANCEL

Button to exit the dialog box without saving your updates.

SAVE

Button to save the route leg status based on selected Route Status.

 

  • To approve LINE Booking leg, you need the Approve Line Booking Route system action and proper delegation of PCC Line with Approve Booking (LINE) role.

  • To approve PCL Booking route, you need the Approve PCL Booking Route system action with Approve Booking (PCL, Feeder) role.

  • To approve Feeder Booking route, you need the Approve Feeder Booking Route system action and proper delegation of Geographical/Location Hierarchy with the Approve Booking (PCL, Feeder) role.

During Booking creation, the status appears as Not Approved for all the transport modes. Each of the leg needs to be approved by the respective Approver. After approval, route status changes either to Approved or Rejected.

Points to remember for Line, PCL, and FeederPoints to remember for Line, PCL, and Feeder

For PCL and LINE

  • Voyage ControllerVoyage ControllerWho is Voyage Controller? A person or persons or organization who execute Schedule Planning and Space Control of a Voyage of a vessel. with the required role and delegation approves/rejects LINE transport mode, while the Area ManagerArea ManagerWho is Area Manager? A person or persons or organization who execute Area administration and sales. with the required role and delegation approves/rejects PCL transport mode. Based on the approval, the Route status may change either to Approved or Rejected.

  • These transport modes can be approved from this screen for a particular Booking or from the LINE(s) & PCL Mass Approval (OPBKW04) screen for multiple Bookings. Same role and task delegation is required in both cases.

For FEEDER

  • If the corresponding Auto Approval Required check box in Feeder Service (OPBKW09) is selected, PCC.NET automatically marks the status as Approved. Otherwise, Area ManagerArea ManagerWho is Area Manager? A person or persons or organization who execute Area administration and sales. with the required role and delegation approves Feeder transport mode.

  • Based on the approval from this screen for a particular Booking or the Feeder Mass Approval/Arrangement (OPBKW05) screen for multiple Bookings, PCC.NET changes the Route status to either Approved, Arranged, or Rejected.

The drop-down list values are defined in the Code Definition (ADCMW02) screen (domain= RT_STATUS, for development usage only, by PCC.NET Administrative users).

Buttons

COST

Button to enter associated feeder or PCL costs using the Feeder/PCL CostFeeder/PCL Cost dialog box. This is optional.

Field

Description

Currency

Currency of the cost. This field has the Auto-Complete feature, which helps you to populate the relevant currency as you type.

Cost

Feeder or PCL costs. You can enter values up to the currency precision value but it will be displayed as the saved values up to 2 digits after decimal point.

Buttons

CANCEL

Button to close the dialog box.

OK

Button to accept the cost.

Applicable only for PCL and Feeder Categories.

Button to delete the leg. In PCC.NET, you can delete only the last leg of the route.

ADD LEG

Button to add a new itinerary row.

In edit mode, you cannot add a leg between existing legs. You must always add route after the last leg.

Cargo Details panel

This panel contains all cargo related information.

  • Click in the Cargo Details panel to open the Edit Cargo dialog box and edit the corresponding record.

  • When you create a Booking from Contract, PCC.NET automatically populates the cargo details from it in this panel. For non-Generic Models, you can edit these cargo details by clicking except the Cargo Type, Make and Model and some conditional fields. But, for Generic Models, PCC.NET allows to update all details in cargo (except Seq.) for all types of Contract. But Rate in the Revenue should be kept same as the initial rate for the Generic Model based on following logiclogic.

    • If the newly-selected Model does not exist in the same Contract number -> LP/DP, PCC.NET does not change the Rate for that the Generic Model.

    • If the newly-selected Model exists in the same Contract number -> LP/DP, Rate automatically gets changed from the Generic Model rate to rate as per the newly-selected model.

  • You must add the Units (of PCC cargo) and UM to save the Booking.

  • For each cargo, at least one default L-W-H pattern cargo details is automatically retrieved from the corresponding cargo of Model Code (not Model Description), Length, Width, Height, Unit Weight, No. of Units, Total Weight and Total Measure (CBM). You can add or modify the L-W-H pattern Cargo details entry against each cargo. PCC.NET checks if at least one L-W-H pattern cargo details entry against each Make/Model irrespective of it’s type (Actual/Generic) is present.

  • You can delete any cargo but at least one cargo item must be present. On deletion of a cargo, corresponding L-W-H pattern all cargo detail entries also get deleted automatically.

  • The sum of Units of all Models present in Cargo Details dialog box must equal the No of Units entered in the Edit Cargo dialog box.

  • If Cargo Units are updated in Booking, the Booking status remains unchanged irrespective of its status.

  • The HS Code, Length, Width, Height, Bump to Bump, Mirr to Mirr, UM, and Cargo Hand fields are Auto-populated from the Model Master (RFMKW02) screen based on the corresponding Model code.

  • You can associate different VINs (Vehicle Identification Number) with the current Booking, provided those are not already associated with any other live Booking/shipment. If VINs are added to multiple B/Ls created from a Single Booking, then those VINs are also added to the associated Booking automatically. If any VIN is deleted from B/L, the particular VIN associated with the corresponding Booking also gets deleted automatically.

  • You can add cargo to the Booking from the associated Contract using ADD CARGO FROM CONTRACT, which fetches the cargo from the Contract. By default, already added cargo in the current Booking is shown auto-selected in the Cargo From Contract dialog box, which you cannot deselect. But you can add cargoes to Booking that are present in the corresponding Contract under the current Port pair.

  • While adding new cargo from Contract, it is mandatory to enter the No of Units along with its UM against each cargo to be newly added to the Booking.

  • If any Load Port (LP)/Discharge Port (DP) pair of a Contract has been deleted, during Add Cargo from Contract action, PCC.NET retrieves the Cargoes not present in the Booking, including FMC information (if present), ignoring the deletion of the associated LP/DP pair.

  • In case ETD of the first Load Port is available in the Booking and any of the FMC in Contract Revenue is expired with respect to the ETD of the first Load Port, a warning message “FMC document in contract is expired. Do you want to bring FMC information from Contract to Booking?”, on your acceptance the cargo is added from the Contract and those expired FMCs are set in Booking Revenue. Otherwise the cargo gets added without setting those FMCs in Booking Revenue.

  • Key Notes for EDI Bookings:

    • An EDI Booking may contain default cargo data (in Generic Models), which you might update to match any non-Generic cargo of the Contract you want to associate. PCC.NET keeps the existing Length, Width, Height, and Weight values and does not overwrite those values with the corresponding new values of the newly-selected Generic Model. You can edit them manually if needed.

    • Cargo Type can be edited for EDI Bookings.

    • You can select one or more VINs to update the Make/Model information and keep the Length, Width, Height and Weight values as blank, only the Make/Model values get applied on the selected VINs; the existing Length, Width, Height and Weight values present on the selected VINs remain unchanged.

Copy mode:

All details are populated from the source Booking No.

Total

A summary of the following cargo attributes is displayed on top of this panel: Total Cargo Count, Total Unit Count, Total Pieces Count, Total Package Count, Total Weight, Total Freight Weight, Total Measure and Total Freight Measure.

<Serial No.>

Sequential number of the record.

This field is available only in the Cargo panel.

Cargo Type

Type of the CargoType of the Cargo. Auto-populated during Booking creation from the Contract.

The following are the cargo types:

  • Car: This is small vehicles that can carry passengers.

  • H&H (or High and Heavy vehicle): H&H mainly stands for heavy trucks, construction equipment, agricultural machinery and cargo that cannot self-propel.

  • HSV (or High sided vehicle): A motor vehicle such as a truck that is tall in relation to its width.

  • Truck: Goods service vehicles transport goods.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for EDI Bookings.

HS Code

Denotes the World Customs Organization (WCO) defined Harmonized Code (HS code) for the commodity. It is a coding for identification and classification of imported and exported goods, for the purpose of compiling trade statistics and determining customs tariff. Every commodity that enters or crosses international borders have to be declared to customs by means of this code. This helps in standardizing the commodity codes worldwide.

Auto-populated during Booking creation based on the corresponding Model number and Read-only.

Make

The name of the vehicle manufacturing company. Auto-populated during Booking creation from the Contract.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. You can modify this value using the Auto-Complete feature, which helps to populate the relevant Make based on the selection of Cargo Type.

Make and Model are often used together to identify a particular vehicle. A vehicle’s complete identification and name is made by the Make and its Model.

Model

The corresponding Model name of the cargo. Auto-populated during Booking creation from the Contract.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. You can modify this value using the Auto-Complete feature, which helps to populate the relevant Model based on your selection of Make

Notes:

  • In EDI Bookings, a warning message is displayed when you change the default value to a non-generic Model, based on your selection of Make. 

Units

Number of units of PCC Cargo.

View mode (Cargo Details panel)

This information appears as Read-only.

Add/Edit mode (Edit Cargo dialog box)

Name of this field appears as No. of Units in the Edit Cargo dialog box. You can enter/edit this value in the Edit Cargo dialog box. Required to save a Booking as Draft.

Notes:

  • During save, PCC.NET checks whether this Unit equals to sum of the unit values provided within Cargo Details.
  • This information is populated from the Contract entered while creating the Booking.
  • In EDI Bookings, a warning message is displayed when you save the changes made in Number of Units while changing the default EDI Make or Model. 

UM

Unit of measurement of the cargo unit. This information is populated from the Contract entered while creating the Booking. You can make the necessary changes.

View mode (Cargo Details panel)

This information appears as Read-only.

Add/Edit mode (Edit Cargo dialog box)

You can enter/edit this value. Required to save a Booking as Draft.

Length

Length of the PCC Cargo. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only. PCC.NET shows the saved values up to 1 digit after decimal point.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. In such case, you can enter values up to 1 digit after decimal point.

Width

Width of the PCC Cargo. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only. PCC.NET shows the saved values up to 1 digit after decimal point.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. In such case, you can enter values up to 1 digit after decimal point.

Height

Height of the PCC Cargo. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only. PCC.NET shows the saved values up to 1 digit after decimal point.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. In such case, you can enter values up to 1 digit after decimal point.

Bump to Bump

The distance between the front side bumper of a vehicle and the backside bumper of another vehicle associated with the corresponding Booking. Auto-populated during Booking creation based on the corresponding Model number.

Edit mode (Edit Cargo dialog box)

You can change this value for any kind of Make/Model that is used for the current Booking. You can enter values up to 1 digit after decimal point.

This field is available only in the Edit Cargo dialog box.

Mirr to Mirr

The distance between the left side mirror of a vehicle and the right side mirror of another vehicle associated with the corresponding Booking. Auto-populated during Booking creation based on the corresponding Model number.

Edit mode (Edit Cargo dialog box)

You can change this value for any kind of Make/Model that is used for the current Booking. You can enter values up to 1 digit after decimal point. Name of this field appears as Mirror to Mirror in the Edit Cargo dialog box.

This field is available only in the Edit Cargo dialog box.

UM

Unit of measurement of the cargo Length, Width, Height, Bump to Bump, and Mirr to Mirr. Default value is CM. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model.

Cargo Handling

The mode of handling the cargo to load or discharge from a vessel. Auto-populated during Booking creation based on the corresponding Model number.

The available options in the drop-down list are:

  • Cars

  • Load with Fork Lift

  • Mafi

  • Self Driven

  • Tracked

  • Towable

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this field for any Make/Model used in the Booking.

Unit Weight

Weight of one unit of car. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this field for any Make/Model used in the Booking. You can enter values up to three digits after decimal point. PCC.NET shows the saved values up to three digits after decimal point.

Total Weight

Weight of all units of the cargo. Total Weight = Weight of one unit of car of the corresponding Model Number in the Model Master (RFMKW02) screen multiplied by the number of units of the car. This field shows values up to 3 digits after decimal point. Read-only.

This field is available only in the Edit Cargo dialog box.

Freight Weight

Weight of all units of the cargo. This field accepts a value with a maximum of three decimal places.

Total Weight = Weight of one unit of car of the corresponding Model Number in the Model Master (RFMKW02) multiplied by number of units of the car.

View mode (Cargo Details panel)

This information appears as Read-only. PCC.NET shows the saved values up to 3 digits after decimal point.

Edit mode (Edit Cargo dialog box)

You can edit this field for any Make/Model used in the Booking. PCC.NET uses this weight for Revenue calculation if the Basis is WA (Weight at Actual). You can enter values up to three digits after decimal point. Minimum value can be zero.

UM

Unit of measurement of the cargo weight. Auto-populated during Booking creation based on the corresponding Model number. Default value is KG.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model.

Unit Measure (CBM)

Volume of one unit of car. PCC.NET shows the saved values up to 3 digits after decimal point. Auto-populated during Booking creation based on the Length, Width and Height of the corresponding Model number. Read-only.

This field is available only in Edit Cargo dialog box.

Total Measure (CBM)

Total volume of the cargo. PCC.NET shows the saved values up to 3 digits after decimal point. Auto-populated during Booking creation based on the corresponding Model number and Read-only.

Total Volume = Volume of one unit of car of the corresponding Model Number in the Model Master (RFMKW02) screen multiplied by the number of units of car.

This field is available only in Edit Cargo dialog box.

Freight Measure (CBM)

Volume of all units of the cargo in cubic meter.

Total Volume = Volume of one unit of car fetched from corresponding Model Number in the Model Master (RFMKW02) multiplied by the number of units of the car. Default value is Total Volume.

Default value is Total Volume.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this field for any Make/Model used in the Booking. PCC.NET uses this weight for revenue calculation if the Basis is MA (Measure at Actual). You can enter values up to 3 digits after decimal point. PCC.NET shows the saved values up to 3 digits after decimal point. Minimum value can be zero.

Remarks

Space to provide remarks about the vehicle. You can enter a maximum of 4000 characters.

This field is available only in Edit Cargo dialog box.

  

Buttons

Button to open Edit CargoEdit Cargo dialog box to edit the corresponding record.

Field

Description

Edit Cargo

Cargo Type

Type of the CargoType of the Cargo. Auto-populated during Booking creation from the Contract.

The following are the cargo types:

  • Car: This is small vehicles that can carry passengers.

  • H&H (or High and Heavy vehicle): H&H mainly stands for heavy trucks, construction equipment, agricultural machinery and cargo that cannot self-propel.

  • HSV (or High sided vehicle): A motor vehicle such as a truck that is tall in relation to its width.

  • Truck: Goods service vehicles transport goods.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for EDI Bookings.

HS Code

Denotes the World Customs Organization (WCO) defined Harmonized Code (HS code) for the commodity. It is a coding for identification and classification of imported and exported goods, for the purpose of compiling trade statistics and determining customs tariff. Every commodity that enters or crosses international borders have to be declared to customs by means of this code. This helps in standardizing the commodity codes worldwide.

Auto-populated during Booking creation based on the corresponding Model number and Read-only.

Make

The name of the vehicle manufacturing company. Auto-populated during Booking creation from the Contract.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. You can modify this value using the Auto-Complete feature, which helps to populate the relevant Make based on the selection of Cargo Type.

Make and Model are often used together to identify a particular vehicle. A vehicle’s complete identification and name is made by the Make and its Model.

Model

The corresponding Model name of the cargo. Auto-populated during Booking creation from the Contract.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. You can modify this value using the Auto-Complete feature, which helps to populate the relevant Model based on your selection of Make

Notes:

  • In EDI Bookings, a warning message is displayed when you change the default value to a non-generic Model, based on your selection of Make. 

Units

Number of units of PCC Cargo.

View mode (Cargo Details panel)

This information appears as Read-only.

Add/Edit mode (Edit Cargo dialog box)

Name of this field appears as No. of Units in the Edit Cargo dialog box. You can enter/edit this value in the Edit Cargo dialog box. Required to save a Booking as Draft.

Notes:

  • During save, PCC.NET checks whether this Unit equals to sum of the unit values provided within Cargo Details.
  • This information is populated from the Contract entered while creating the Booking.
  • In EDI Bookings, a warning message is displayed when you save the changes made in Number of Units while changing the default EDI Make or Model. 

UM

Unit of measurement of the cargo unit. This information is populated from the Contract entered while creating the Booking. You can make the necessary changes.

View mode (Cargo Details panel)

This information appears as Read-only.

Add/Edit mode (Edit Cargo dialog box)

You can enter/edit this value. Required to save a Booking as Draft.

Length

Length of the PCC Cargo. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only. PCC.NET shows the saved values up to 1 digit after decimal point.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. In such case, you can enter values up to 1 digit after decimal point.

Width

Width of the PCC Cargo. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only. PCC.NET shows the saved values up to 1 digit after decimal point.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. In such case, you can enter values up to 1 digit after decimal point.

Height

Height of the PCC Cargo. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only. PCC.NET shows the saved values up to 1 digit after decimal point.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model. In such case, you can enter values up to 1 digit after decimal point.

Bump to Bump

The distance between the front side bumper of a vehicle and the backside bumper of another vehicle associated with the corresponding Booking. Auto-populated during Booking creation based on the corresponding Model number.

Edit mode (Edit Cargo dialog box)

You can change this value for any kind of Make/Model that is used for the current Booking. You can enter values up to 1 digit after decimal point.

This field is available only in the Edit Cargo dialog box.

Mirr to Mirr

The distance between the left side mirror of a vehicle and the right side mirror of another vehicle associated with the corresponding Booking. Auto-populated during Booking creation based on the corresponding Model number.

Edit mode (Edit Cargo dialog box)

You can change this value for any kind of Make/Model that is used for the current Booking. You can enter values up to 1 digit after decimal point. Name of this field appears as Mirror to Mirror in the Edit Cargo dialog box.

This field is available only in the Edit Cargo dialog box.

UM

Unit of measurement of the cargo Length, Width, Height, Bump to Bump, and Mirr to Mirr. Default value is CM. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model.

Cargo Handling

The mode of handling the cargo to load or discharge from a vessel. Auto-populated during Booking creation based on the corresponding Model number.

The available options in the drop-down list are:

  • Cars

  • Load with Fork Lift

  • Mafi

  • Self Driven

  • Tracked

  • Towable

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this field for any Make/Model used in the Booking.

Unit Weight

Weight of one unit of car. Auto-populated during Booking creation based on the corresponding Model number.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this field for any Make/Model used in the Booking. You can enter values up to three digits after decimal point. PCC.NET shows the saved values up to three digits after decimal point.

Total Weight

Weight of all units of the cargo. Total Weight = Weight of one unit of car of the corresponding Model Number in the Model Master (RFMKW02) screen multiplied by the number of units of the car. This field shows values up to 3 digits after decimal point. Read-only.

This field is available only in the Edit Cargo dialog box.

Freight Weight

Weight of all units of the cargo. This field accepts a value with a maximum of three decimal places.

Total Weight = Weight of one unit of car of the corresponding Model Number in the Model Master (RFMKW02) multiplied by number of units of the car.

View mode (Cargo Details panel)

This information appears as Read-only. PCC.NET shows the saved values up to 3 digits after decimal point.

Edit mode (Edit Cargo dialog box)

You can edit this field for any Make/Model used in the Booking. PCC.NET uses this weight for Revenue calculation if the Basis is WA (Weight at Actual). You can enter values up to three digits after decimal point. Minimum value can be zero.

UM

Unit of measurement of the cargo weight. Auto-populated during Booking creation based on the corresponding Model number. Default value is KG.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this value only for Generic Model.

Unit Measure (CBM)

Volume of one unit of car. PCC.NET shows the saved values up to 3 digits after decimal point. Auto-populated during Booking creation based on the Length, Width and Height of the corresponding Model number. Read-only.

This field is available only in Edit Cargo dialog box.

Total Measure (CBM)

Total volume of the cargo. PCC.NET shows the saved values up to 3 digits after decimal point. Auto-populated during Booking creation based on the corresponding Model number and Read-only.

Total Volume = Volume of one unit of car of the corresponding Model Number in the Model Master (RFMKW02) screen multiplied by the number of units of car.

This field is available only in Edit Cargo dialog box.

Freight Measure (CBM)

Volume of all units of the cargo in cubic meter.

Total Volume = Volume of one unit of car fetched from corresponding Model Number in the Model Master (RFMKW02) multiplied by the number of units of the car. Default value is Total Volume.

Default value is Total Volume.

View mode (Cargo Details panel)

This information appears as Read-only.

Edit mode (Edit Cargo dialog box)

You can edit this field for any Make/Model used in the Booking. PCC.NET uses this weight for revenue calculation if the Basis is MA (Measure at Actual). You can enter values up to 3 digits after decimal point. PCC.NET shows the saved values up to 3 digits after decimal point. Minimum value can be zero.

Remarks

Space to provide remarks about the vehicle. You can enter a maximum of 4000 characters.

This field is available only in Edit Cargo dialog box.

Buttons

CANCEL

Button to cancel the entries or changes you have made.

OK

Button to update Cargo related changes. Before accepting it, PCC.NET checks, and makes sure that Cargo units/total weight/measure equals the summary of units/weight/measure entered in the Cargo Details, respectively.

Notes:

  • Auto-adjustment of Cargo Details for Single Cargo Entry:

    • If you change the Model name in the Edit Cargo dialog box and there is a single entry against a Cargo in the Cargo Details dialog box, PCC.NET auto updates the respective Model Description, Length, Width, Height, Unit Weight and Unit values in the Cargo Details dialog box. Measure and Weight of the cargo details are then calculated based on the updated cargo details entered. However, if there are multiple cargo entries, you have to manually modify the details in the respective panels of the Cargo Details dialog box, as well.

    • If you update any cargo attribute other than the Model name in the Edit Cargo dialog box and there is a single entry against the Cargo details, its Model Description remains unchanged in the Cargo Details dialog box. However:

      • For a Generic model, PCC.NET automatically updates values changed in the Edit Cargo dialog box (Length, Width, Height, Unit Weight, No of Units) in the corresponding fields present in the Cargo Details dialog box. The Measure and Weight of cargo are then calculated, based on the Cargo detail values entered.
      • For a Non-Generic model, PCC.NET automatically updates the values (No of Units, Unit Weight) in the Edit Cargo dialog box in the corresponding fields (Units, Unit Weight) in the Cargo Details dialog box.
  • Manual Adjustment of Cargo Details for Multiple Cargo Entries:

    • If there are multiple entries of Cargo in the Edit Cargo dialog box, and you change any of its details, PCC.NET does not auto adjust its corresponding values in the Cargo Details. You must manually update all values, in such a case.

CARGO DETAILS

Button to enter Cargo wise L-W-H pattern details. The Cargo DetailsCargo Details dialog box opens.

 

Field

Description

Cargo Details

Model Description

L-W-H pattern wise Model Description. Required.

This field allows a maximum entry of 150 characters.

Length

Length of the Cargo Model. Required.

You can enter values up to 1 digit after decimal point. PCC.NET shows the saved values up to 1 digit after decimal point.

In case of any Non-Generic model, if you modify any of the L-W-H values in the Cargo Details dialog box, there is always a chance of Cargo measure discrepancy between entries made in the Cargo Details dialog box, and the Edit Cargo dialog box.

Width

Width of the Cargo Model. Required.

You can enter values up to 1 digit after decimal point. PCC.NET shows the saved values up to 1 digit after decimal point.

In case of any Non-Generic model, if you modify any of the L-W-H values in the Cargo Details dialog box, there is always a chance of Cargo measure discrepancy between entries made in the Cargo Details dialog box, and the Edit Cargo dialog box.

Height

Height of the Cargo Model. Required.

You can enter values up to 1 digit after decimal point. PCC.NET shows the saved values up to 1 digit after decimal point.

In case of any Non-Generic model, if you modify any of the L-W-H values in the Cargo Details dialog box, there is always a chance of Cargo measure discrepancy between entries made in the Cargo Details dialog box, and the Edit Cargo dialog box.

Unit Weight

Weight of one unit of the Cargo Model. Required.

You can enter values up to 3 digits after decimal point. PCC.NET shows the saved values up to 3 digits after decimal point.

Units

Number of units of the Cargo Model. Required.

PCC.NET checks that sum total of units of all cargo Models present in this dialog box is same as the unit entered in Edit Cargo dialog box.

Measure (CBM)

Measure = Volume of one unit of the Model multiplied with no of units of car.(Volume of one Unit multiplied by No. of Units)

PCC.NET calculates the volume of one Unit first, and then multiply it with number of units.

Volume of one Unit = Length * Width * Height /1000000 (rounding off up to 3digits after decimal point)

  • This field remains disabled.

  • PCC.NET will show the saved values up to 3 digits after decimal point.

Weight

Total Weight = Weight of one unit of the multiplied with no of units of car. ( Weight of one Unit multiplied by the number of Units)

  • This field remains disabled.

  • PCC.NET will show the saved values up to 3 digits after decimal point.

Total

PCC.NET calculates and displays the total number of cargo units entered and summation of its measures and weights in the respective column.

Buttons

ADD

Click this button to add a blank row at the end of the Cargo Details grid for entering a new Cargo wise L-W-H pattern details.

Click this icon for deleting the corresponding Cargo wise L-W-H pattern details row item.

CANCEL

Button to cancel the changes you have made.

OK

Click this button to save Cargo detail information for the corresponding Cargo entries made, that is multiple or single entries. Based on the entries made, PCC.NET performs the following:

  • For Single Cargo details entry:

    • For Generic model, the Length, Width, Height, No of Units, and Unit Weight are updated in the Edit Cargo dialog box. Accordingly, the Total Measure (CBM), Freight Measure (CBM), Total Weight, and Freight Weight fields are finally calculated.

    • For non-Generic model, the Unit Weight and No of Units are updated in the Edit Cargo dialog box. Accordingly, the Total Measure (CBM), Freight Measure (CBM), Total Weight, and Freight Weight fields are finally calculated.

  • For Multiple Cargo detail entries:

    • PCC.NET checks the sum of Units of all Models present in this dialog box, is equal to the No of Units entered in the Edit Cargo dialog box.

    • PCC.NET updates the Total Weight, Freight Weight values in the Edit Cargo dialog box, using the total value of Weights of all Models present in the Cargo Details panel of the current dialog box.

    • PCC.NET also updates the Total Measure (CBM), Freight Measure (CBM) values in the Edit Cargo dialog box, using the total value of Measures of all Models present in the Cargo Details panel of the current dialog box.

CHOOSE FILE TO UPLOAD

Button to select an Excel file containing Cargo details (maximum 1000 records) in a predefined XLSX/XLSM format for refreshing/replacing the data within the Cargo Details grid.

Before uploading, PCC.NET checks for the following details:

  • Details are provided as per the specified format.

  • Values for Model Description, Length, Width, Height, Unit Weight, Units are provided.

  • Values for Length, Width, Height, Unit Weight, Units are all numeric.

How to update Cargo Details in Macro-Enabled File

Before opening the Cargo Details dialog box, you must enter the Make/Model and Number of Units in the Edit Cargo dialog box.

PCC.NET populates the remaining details either from Contract or Model Master based on the Make/Model used in the Booking.

Button to copy generic Make and Model information. When you copy generic Make and Model; all details including revenue information of the cargo are copied.

You can later change the generic Make/Model to actual Make/Model. But the Rate in the Revenue panels must remain unchanged for that Generic Model based on the following logic:

  • If newly-selected model does not exist in the same Contract Number-> LP/DP, PCC.NET does not change the Rate automatically for that the Generic Model.

  • If newly-selected model exists in the same Contract Number-> LP/DP, PCC.NET changes the Rate automatically for the Generic Model as per the newly-selected model.

Button to delete the corresponding cargo in the Booking. Minimum one cargo must be present in the Booking.

You need to manually delete a cargo which is not present within the latest revision of the currently selected Contract.

VIN ASSOCIATION

Button to associate VINs with the Booking using the Associate VIN dialog box.

Vehicle Identification Number, commonly abbreviated to VIN, is a unique serial number used by the automotive industry to identify individual motor vehicles. VINs can consist up to 17 characters.

Copy mode

When you click this button, PCC.NET displays an error message. Once the Booking data is saved and new Booking number is generated. you can proceed with associate VIN operations again.

 

VIN TRACKING

Button to open the VIN Tracking (OPBKW08) screen that displays the tracking information of the current Booking.

You need to have the "Create Booking" or"View Booking without Revenue" role with "VIN Tracking" system action to perform this activity.

Copy mode:

When you click this button, PCC.NET displays an error message. Once the Booking data is saved and new Booking number is generated. you can proceed with VIN tracking again.

ADD CARGO FROM CONTRACT

Button to add cargo information to the Booking from the Contract using the Cargo From ContractCargo From Contract dialog box. The dialog box displays all the cargoes associated with latest revision of the current Contract (restricted by Customer, Contract and Port pair of the current Booking) with their associated charges.

Field

Description

Search Panel

You can search particular Make/Model from all the available cargoes of the latest revision of the currently-associated Contract (for the particular Customer, Contract and Port pair of the current Booking).

Booking Number

Current Booking number.

Contract Number

Associated Contract number of the current Booking.

Load Port

First Load Port of the cargo.

Discharge Port

Last Discharge Port of the cargo.

Make

Identification name of the car manufacturer. This field has the Auto-Complete feature, which helps to populate the relevant Make name as you type.

Model

Model name of the Cargo. This field has the Auto-Complete feature, which helps to populate the relevant Model name as you type.

SEARCH

Button to search for cargoes.

Cargo Panel...

By default, the cargoes selected while creating the Booking are shown as disabled and auto-selected both in the Cargo and Cargo & Revenue panels. You can add any other cargo in the Cargo panel from available list.

Cargo Type

Type of the cargoType of the cargo associated with the selected Contract.

The following are the cargo types:

  • Car: This is small vehicles that can carry passengers.

  • H&H (or High and Heavy vehicle): H&H mainly stands for heavy trucks, construction equipment, agricultural machinery and cargo that cannot self-propel.

  • HSV (or High sided vehicle): A motor vehicle such as a truck that is tall in relation to its width.

  • Truck: Goods service vehicles transport goods.

Cargo Seq.

Cargo sequence number.

Make

The name of the vehicle manufacturing company.

Model

The corresponding Model name of the cargo.

No. of Units

Number of units of PCC Cargo.

It is mandatory to enter the No of Units along with its UM against each cargo to be newly added to the Booking.

UM

Unit of measurement of the cargo unit.

It is mandatory to enter the No of Units along with its UM against each cargo to be newly added to the Booking.

Length

Length of the PCC Cargo as defined in the Model Master (RFMKW02) screen.

Height

Height of the PCC Cargo as defined in the Model Master (RFMKW02) screen.

UM

Unit of Measurement for measuring lengths.

Unit Weight

Weight of a single cargo as per Model Master (RFMKW02) screen.

UM

Unit of Measurement of the cargo weight.

Cargo & Revenue panel

  • PCC.NET fetches all the cargo details associated with the latest revision of the current Contract (for the particular Customer, Contract and Port pair of the current Booking) with their associated charges.

  • By default, the cargo details added in the current Booking appear auto-selected, but you can add any other cargo from the available list of cargoes belonging to the Contract.

  • You can select only those cargo details to Booking, which are present in the corresponding Contract.

  • When you select single/multiple new cargos having multiple charges under it, the Add Revenue for Additional CargoAdd Revenue for Additional Cargo dialog box appears for selection of revenue against the newly added cargo details.

    • This dialog box does not show the already existing cargo details in the Booking. It only shows the new cargo details along with the applicable charges (sorted in the same way as it appears under the Booking Revenue Details panel).

    • All revenues against all new selected cargo details remain selected by default but you can select or deselect the revenues selectively before finally accepting the ones selected in the Booking Revenue.

    • This dialog box excludes all revenues against the selected cargo(s) for which Effective To is earlier than the current system date.

    • If any PT basis charge is selected:

      • You can select dependent applicable charges against the PT basis charge by clicking adjacent to the Basis field. On clicking , the Applicable Charges in ContractApplicable Charges in Contract dialog box appears, displaying all other changes against the same make/model and currency as that of the PT basis charge but all applicable dependent charges against that PT basis charge as setup in Contract remains selected initially. It also displays the already saved dependent charges from the latest revision of Contract against that charge. You can deselect all or some of these charges if required. On clicking OK in the dialog box, all the selected applicable charges gets associated against the PT Basis charge. Before associating, PCC.NET ensures that at least one dependent charge as specified in the corresponding Contract or any other change present under the same Make/Model is selected by you along with that PT basis charge.

      • If the corresponding PT basis charge has dependent applicable charges specified in the Contract and you have not selected any of the applicable charges, an error is shown asking you to select at least one Contract specified or any other applicable charge present under the same make/model along with that PT basis charge.

<Select all check box>

Check box to select the records.

  • If you select the check box in the column header, all records are selected at the same time that can be added to the Booking on clicking OK.

  • If you select the check box corresponding to a record, so that on clicking OK the particular record can be added to the Booking.

When you select a row for adding a cargo, PCC.NET automatically selects all the rows for the particular cargo having different charges. After selection of the cargo, if you click OK, all the selected cargo details and the associated latest rates from the Contract are added to the Booking.

Cargo Seq

Cargo sequence number. It helps to identify the sequence associated with Booking cargo in case of multiple generic Make and Model.

Cargo Type

Type of the cargo associated with current Contract.

Make

Identification name of the car manufacturer associated with current Contract.

Model

Model name of the cargo associated with current Contract.

Charges

Charges associated with current Contract.

Basis

Basis for calculation of the charge.

Rate

Charge rate associated with the charge.

P/C

P for prepaid charges, C for collect charges.

Currency

Charge currency applicable to the rate.

Buttons

CANCEL

Button to close the dialog box.

OK

Button to add the selected records to the Booking.

Revenue Details panel

Panel to define revenue information of a Booking.

This panel is editable only if you have the Create Booking role and Update Booking system action privilege. You cannot update revenue information if you are assigned with the Update Booking Doc Entry Office role type along with Update Booking Without Revenue system action and delegation as Doc Entry Office.

  • To edit a record, as you click , the corresponding row becomes editable and toggles to , which allows you to save the updated record.  allows you come out of the Edit mode.

  • When you create a Booking from Contract, all revenue charges for a particular Port pair and selected Make/Model are retrieved in the Booking from the latest revision of the Contract. A privileged Booking user is able to add Supplementary charges and update some existing revenue information in Booking. Only Freight Collection Office, Invoicing Office and Payer fields are editable in the Booking when a charge is retrieved from Contract and the charge basis does not fall among PT or RT. Other charges from Contract cannot be changed in Booking.

    • For the charges with basis as PT and having dependent charges against that PT basis charge saved in Contract, while creating a Booking, PCC.NET checks if at least one Applicable Charge is available in the Contract, calculates, and populates the amount in the Booking for a given port-pair combination.

    • For the changes with basis as RT, you can change the value of cargo UM to RT when you want to put Rated At value as per your desired value, otherwise Rated At value gets automatically calculated, hence is disabled.

  • For EDI Bookings, the Revenue Details panel initially appears blank. You need to select the Contract Number to retrieve the latest rates from the Contract for all the Makes and Models in the Booking.

  • In Booking, you can add only additional Supplementary charges, provided those are not present under the latest version of the Contract.

  • If you have deleted a Supplementary charge in the Booking that is present in the associated Contract and then try to add it again to the Booking, PCC.NET restricts to add that Supplementary charge. You must click REFRESH RATE FROM CONTRACT and add the required Supplementary charge.

  • To modify any rate of Contractual charge, you need to update the Contract first and apply the new rates using REFRESH RATE FROM CONTRACT. You may need to refresh the rate after re-selecting Contract number while switching between Broker and Broker customer.

  • While performing a Refresh Rate from Contract, when expired charge(s) are present against the ATD (if available)/ETD at the first Load Port for a particular Vessel/Voyage, PCC.NET automatically dis-associates the charge from the associated Booking Revenue. You are not required to remove the expired charge(s) additionally. When the ATD (if available)/ETD at the first Load Port is not between the Effective From and Effective To dates of the Contract, the Revenue charge(s) are considered as expired.

  • If any Load Port (LP)/Discharge Port (DP) pair of a Contract has been deleted, during Refresh Rate from Contract action, when Booking is not rolled over or first LP/last DP did not change, PCC.NET ignores the deletion of LP/DP pair and retrieves the new charges from the Contract that are missing in the Booking, the latest rates of the existing revenues in Booking, and FMC information, if present. But after Booking Rollover, PCC.NET restricts you to refresh the rate if the first LP or last DP of the Booking has changed and the current port pair of the Booking is already deleted from the associated Contract. In such a case, it displays an error message stating that the current port pair is not present in the Contract; you must add the port pair in the Contract.

  • If overlapping rates are populated from Contract, you should delete the duplicate charges with same charge codes.

  • PCC.NET verifies if the charge/rate is same as per Make and Model of the corresponding latest revision of the Contract. If there is any mismatch, it restricts you from saving the PCC Booking.

  • When you change the Payment Term (P/C) value or Freight Collection Office value in Booking, PCC.NET tries to find a unique Rate based on the Charge, Basis, Payment Term and Freight Collection Office, and automatically set it.

  • At least one revenue (OFR) must be there for each Make and Model in Booking.

  • You can add a charge multiple times with different rates for a cargo. Also, you may add a supplementary charge multiple times with different rates when you add it in Booking without associating it with any Make/Model.

  • If a Booking contains multiple OFR charges, they must all be in same currency values.

  • Rate can be zero for both Contractual and Supplementary changes, that is amount can be zero for any charges.

  • Booking Payer must be active in PCC.NET.

  • At the time of saving the Booking, PCC.NET checks the Contract charges in the Booking. If all Contract revenues (except, OFR) for one charge code against a Cargo are removed in the Booking Revenue, a warning message appears asking your confirmation whether you want to proceed without those revenues. On confirmation, PCC.NET proceeds to save the Booking, otherwise not.

  • During saving the Booking, PCC.NET also checks if the currency in the Booking Revenue has been deleted and if the date of currency becoming obsolete is later than the system date. If this validation fails at any Booking status, you cannot save the Booking.

  • Logic to change the Payment Method (Prepaid or Collect) against all charges retrieved in Booking from Contract.Logic to change the Payment Method (Prepaid or Collect) against all charges retrieved in Booking from Contract.

    You can change the Payment Method (Prepaid or Collect) of all the charges retrieved in Booking from Contract. PCC.NET validates the Payment Method (Prepaid or Collect), Rate and Freight Collection Office values selected in the Booking against the same values present in the latest revision of the Contract, and accordingly allows you to update any or specific Payment Method (Prepaid or Collect) value in Booking against a Charge.

    Following is the logic of the above validation done during saving the revenue information in Booking:

    Conditions when you can update any Payment Method (P/C) in Booking against a Charge:

    You can update the payment mode (Prepaid/Collect) of a charge in a Booking which may differ from that defined in the associated Contract, if:

    • The Freight Collection Office is not specified in the Booking, or the specified Charge and its Freight Collection Office do not exist in the latest revision of the Contract.

    • The Charge and its Freight Collection Office selected in the Booking is specified in the latest revision of the Contract and the charge is defined with single Payment Method (either Prepaid or Collect) in Contract.

    Condition when you can update only a specific Payment Method (P/C) as per Contract in Booking against a Charge:

    You must update the particular payment mode (Prepaid/Collect) of a charge in a Booking as defined in the associated Contract, if:

    • The Charge and its Freight Collection Office selected in the Booking exists in the latest revision of the Contract and that Charge is defined with both the Payment Methods (Prepaid or Collect) in Contract.

    Notes:

    • In each case, PCC.Net makes sure that the selected Rate in Booking matches with the Make/Model, Charge, Basis, Freight Collection Office and Payment Method of the Contract’s latest revision.
    • The Revenue payment method (P/C) values are defaulted from the Contract during creation of the Revenue for the first time in Booking. While refreshing Rate from Contract in Booking, PCC.NET neither checks if the (P/C) value has been changed in Contract, nor replaces that updated value from Contract.

     

Copy mode:

All details are populated from the source Booking No.

<Serial No.>

Sequential number of the record.

Charge

Charge code for the charge as classified for the shipping business. Read-only if the charge is retrieved from Contract.

In PCC.NET, two types of charges are applicable:

  • Contractual Charge: This charge is populated from the corresponding Contract in the Booking Revenue. You cannot add or update such charges manually in the Booking, except its Freight Collection Office, Invoicing Office, and Payer information. If there is any change in the Contract revenue, it needs to be reflected in the corresponding Booking also. Change in the  Revenue information of a Contract can be inherited in the corresponding Booking using REFRESH RATES FROM CONTRACT. However, this is applicable only to those charges/rates that have changed in the Contract for the particular Make and Model associated with the Booking, and whose effective dates in the Contract are same as or earlier than the ETD of the first Mother/PCL vessel associated with the Booking leg.

  • Supplementary Charge: This charge is not registered in the corresponding Contract and you can add manually in Booking Revenue. However, if any Supplementary charge is registered in the Contract, it cannot be added/updated manually in the Booking using ADD REVENUE.

PCC.NET retrieves all Contractual charges from Contract in these fields, which you cannot edit. But you can add various supplementary charge codes by clicking ADD REVENUE. This field has the Auto-Complete feature, which helps you to populate the relevant charge as you type.

While viewing Revenue, Charge Description is displayed as a tooltip while hovering over the selected Charge code.

Make/Model

Make/Model information for the corresponding charge. This information must be present in corresponding Contract. In case of Contractual charges this field is Read-only. But for supplementary charges added in Booking, this value can be optionally selected.

This field has the Auto-Complete feature, which helps you to populate the relevant Make/Model from the selected Contract as you type.

Basis

Drop-down list to select the basis for calculation. Following are the available options while adding a record:

  • LM - Lane Meter

  • MA - Actual measure basis

  • PB - Per Bill

  • WA - Actual weight basis

  • PT - Percentage basis

  • PU - Per Unit basis

  • RT - Revenue Ton

  • WS - Wt Actual (Short ton)

Notes:

  • The drop-down list values are defined in the Code Definition (ADCMW02) screen (domain= BKG_BASCODE, for development usage only, by PCC.NET Administrative users).
  • While viewing Revenue, Basis description is displayed as a tooltip when you hover over the selected Basis code.

Rated At

Freighted quantity/value. Read-only except for the Contractual/Supplementary charges where Basis is PT/RT.

  • In case of the basis PT, during Booking creation from Contract, PCC.NET retrieves the default dependent applicable charges from the Contract. PCC.NET checks if at least one applicable charge is available in the Contract, calculates, and populates the amount in the Booking for a given port-pair combination. The calculation is done based on the Rated At value of the corresponding Charge as the sum of a percentage of the Applicable Charges associated with it. Applicable charge(s) having same Make/Model as the PT basis charge, as selected in the corresponding Contract against that charge are populated. You (Booking user) can add supplementary dependent applicable charges against a PT basis charge and de-select the dependent applicable Contractual charges from this screen.

Notes:

  • Dependent charges for the PT charge are populated from the Contract only during Booking creation from the Contract and adding a new cargo from the Contract. Afterwards, during Refresh rate from Contract, the dependent changes are not modified in the Booking if the dependent charge gets changed in new revision of the Contract; only the newly-updated rate from the latest revision of the corresponding Contract are retrieved.
  • More concepts on Applicable Charges for PT basis.More concepts on Applicable Charges for PT basis.

    1. In the Revenue Details panel, select the Charge, Maker/Model, Basis (as PT) and Currency.
    2. Click in the Rated At field . The Applicable Charges in ContractApplicable Charges in Contract dialog box appears.

    • By clicking adjacent to the Rated At column, you can view/select the other charges as the applicable charges of the current Booking revenue on which percentage (PT) basis will be applied in the Applicable Charges in Contract dialog box. In case of Contractual PT Basis charges, PCC.NET displays the Contract-specific applicable charges for that PT basis charge from latest revision of Contract against the same Make/Model as that of the PT basis charge in the Header of the dialog box.
    • If a charge with Basis as Percentage (PT) exists in a Contract, while creating Booking from that Contract, a revenue record is created for that charge with selected dependent applicable charges and Rate value as percentage mentioned in the Contract.
    • Initially, the Rated At value field remains as zero since cargo units are not available, once cargo units become available it gets auto calculated based on the cargo units and dependent applicable charges.
    • PCC.NET calculates the Rated At value based on the selected dependent/applicable charges. In this case, you are allowed to adjust the Rated At value to any desired value. PCC.NET considers values up to 4 digits after decimal point and also will round off Rated At value up to 4 digits after decimal point. PCC.NET shows the saved values up to 4 digits after decimal point.
    • While saving the Booking, PCC.NET validates whether you have selected applicable charge(s) for the PT basis charge or not.
    1. Click OK after updating/selecting the check box against the corresponding Charge(s) displayed in the dialog box.
  • In case of the basis RT, this value remains Read-only till the UM value is also set to RT. When UM value is also set to RT, Rated At becomes editable so that you can adjust its value as desired. PCC.NET allows to enter values and rounds off Rated At value up to 4 digits after decimal point. It also shows the saved values up to 4 digits after decimal point. More on charge with Basis as Revenue Ton (RT) More on charge with Basis as Revenue Ton (RT)
    • If a charge with basis as Revenue Ton (RT) exists in a Contract, while creating a revenue record against it, PCC.NET determines the greater value between Freight Measure (M3) and Freight Weight (KG)/1000 (rounding off up to three decimal points).

    • If Freight Weight (KG)/1000 (rounding off up to three decimal points) is more than Freight Measure, PCC.NET assigns the Freight Weight/1000 (rounding off up to three decimal points) in Rated At field and default UM is KT, so Per also becomes KT. In this case, UM can have two values - KT and RT, so you can choose either of them. According to your choice, PCC.NET auto-updates Per to KT if UM is KT and per to RT’ if UM is RT.

    • If Freight Measure is more than Freight Weight (KG)/1000, PCC.NET assigns the Freight Measure in Rated At field and default UM will be M3, so Per becomes M3. In this case UM can have two values - M3 and RT, so you can choose either of them. According to your choice, PCC.NET will auto-change Per to M3 if UM is M3 and to RT if UM is RT.

    • If Freight Measure equals to Freight Weight (KG)/1000, PCC.NET assigns the Freight Measure in Rated At field and default UM will be RT, so Per becomes RT. In this case UM can have three values - RT, M3 and KT, so you can choose any of them. According to your choice, PCC.NET auto-update Per to M3 if UM is M3; to KT if UM is KT and to RT if UM is RT.

    • If Basis is RT and UM is RT, the Rated At becomes independent of change of Cargo value and gets enabled so that you can edit the Rated At value manually.

    • If Cargo information is changed, Rated At is also re-calculated as per the above specifications.

  • If a charge with basis as Short Ton (WS) exists in a Contract, while creating a revenue record against it, PCC.NET assigns the Freight Weight/1000 multiplied by (1000 / 907.18474) in Rated At field and default UM is ST, so ‘Per’ also become ST. That is, Rated At (Short Ton) = (Freight Weight (KG)/1000) * (1000 / 907.18474).

Rated At value is rounded off up to 3 decimal points and displayed up to 4 decimal points.

For example: (value=123.55555 is displayed as 123.5560, and value=123.5544 is displayed as 123.5540).

  • If a charge with basis as Lane Meter (LM) exists in a Contract, while creating a revenue record against it, PCC.NET assigns the Length of the Unit/100 multiplied by (Number of Units) in Rated At field and default UM will be ‘ME’, so ‘Per’ also becomes ‘ME’. i.e. Rated At (Lane Meter) = (Length of the unit (cm)/100) * (Number of units).

Rated At value is rounded off up to 4 decimal points and is displayed up to 4 decimal points.

For example: (value=123.55555 is displayed as 123.5556, value=123.55554 is displayed as 123.5555 and value=123.554 displayed as 123.5540)

ExampleExample

  • If the Basis is PU, it indicates the number of Units.

  • If the Basis is WA, it indicates the actual weight (Net weight, if net weight is specified in commodity, otherwise gross weight).

  • If the Basis is PB (Per B/L), the value in this field can be 1 only.

Rated At is calculated based on the Basis value as mentioned below:

Basis

Description

Per

UM

Rated At

WA

Weight Actual

KT

KT

Freight Weight/1000

MA

Measure Actual

M3

M3

Freight Measure

PU

Per Unit

UN

UN

Cargo count

PT

Percentage

RV

RV

Calculated based on other charges

PB

Per Bill

B/L

B/L

1

RT

Revenue Ton

KT/M3/RT

KT/M3/RT

Greater value between Freight Weight/1000 (rounding off up to 3 decimal points) and Freight Measure

WS

Short Ton

ST

ST

(Freight Weight (KG) / 1000) * (1000 / 907.18474)

(rounding off up to 4 decimal points and displayed up to 4 decimal points)

LM

Lane Meter

ME

ME

(Length of the unit (cm) /100) * "Number of units"

(rounding off up to 4 decimal points and displayed up to 4 decimal points)

During entering Supplementary Charge in Booking, if the charge is entered without associating it with any Make/Model and Basis is selected as Weight Actual (WA)/Measure Actual (MA), PCC.NET considers the sum of Freight Weights/Freight Measure of all Make/Models present within the Booking as the default value of Rated At corresponding to that charge. In case of Basis PT/RT, PCC.NET allows you to modify the default value of Rated At, too.

UM

Drop-down list to select the unit of measure for Rated At.

Rate

Charge rate applicable on the Rated At value. PCC.NET multiplies it with Rated At to get the Amount for this charge.

For the charges retrieved in Booking from the Contract, a Search icon appears adjacent to this field. The Rate SelectionRate Selection pop-up appears with all the available Rates against the existing Make/Model, Charge and Basis combination from the latest revision of the Contract. You can select any of the available Rates from the pop-up. On selection of a Rate from the pop-up, the corresponding Currency and Rate gets added to the Revenue. This pop-up is not available for the charges which were added locally in Booking (not present in Contract); you need to enter values in the Rate text box directly.

For Generic Model cargoes, you must enter a rate for the Generic Model in Contract. After creating a Booking, you can change the Make and Model in the Cargo panel from the Model Master (RFMKW02) screen.

However, the Rate for that cargo must remain unchanged for that Generic Model based on the following logic:

  • If newly-selected Model does not exist in the same Contract number ->LP/DP, PCC.NET does not change the Rate for that the Generic Model.

  • If newly-selected Model exist in the same Contract number ->LP/DP, the Rate automatically gets changed from the Generic Model rate to rate as per the newly -selected model.

  • The minimum value for Rate is -99999999.9999, and the maximum is 999999999.9999. Any value entered must fit in this range.

  • For Charges with Basis as PT, Rate should not be more than or equal to 1 (that is, Rate is less than 100%) except for CAF. For CAF Rate should not be more than 2 (Rate should be less 200%).

You can enter values up to 4 digits after decimal point and the Rated At value is rounded off up to 4 digits after decimal point. PCC.NET shows the saved values up to 4 digits after decimal point.

When you change the Payment Term (P/C) value or Freight Collection Office value in Booking, PCC.NET tries to find a unique Rate based on the Charge, Basis, Payment Term and Freight Collection Office, and automatically set it.

Currency

Charge currency applicable to the rate, for example, USD (US dollars). This field has the Auto-Complete feature, which helps you to populate the relevant currency as you type.

Notes:

  • The currencies displayed in the list are registered in the Currency (RFCSW02) screen.
  • Multiple Currency is not allowed for OFR.

P/C

Drop-down list to select the payment method to indicate whether the revenue is prepaid or collect type. Available values are P, which means Prepaid and C, which means Collect.

  • Logic to change the Payment Method (Prepaid or Collect) against all charges retrieved in Booking from Contract.Logic to change the Payment Method (Prepaid or Collect) against all charges retrieved in Booking from Contract.

    You can change the Payment Method (Prepaid or Collect) of all the charges retrieved in Booking from Contract. PCC.NET validates the Payment Method (Prepaid or Collect), Rate and Freight Collection Office values selected in the Booking against the same values present in the latest revision of the Contract, and accordingly allows you to update any or specific Payment Method (Prepaid or Collect) value in Booking against a Charge.

    Following is the logic of the above validation done during saving the revenue information in Booking:

    Conditions when you can update any Payment Method (P/C) in Booking against a Charge:

    You can update the payment mode (Prepaid/Collect) of a charge in a Booking which may differ from that defined in the associated Contract, if:

    • The Freight Collection Office is not specified in the Booking, or the specified Charge and its Freight Collection Office do not exist in the latest revision of the Contract.

    • The Charge and its Freight Collection Office selected in the Booking is specified in the latest revision of the Contract and the charge is defined with single Payment Method (either Prepaid or Collect) in Contract.

    Condition when you can update only a specific Payment Method (P/C) as per Contract in Booking against a Charge:

    You must update the particular payment mode (Prepaid/Collect) of a charge in a Booking as defined in the associated Contract, if:

    • The Charge and its Freight Collection Office selected in the Booking exists in the latest revision of the Contract and that Charge is defined with both the Payment Methods (Prepaid or Collect) in Contract.

    Notes:

    • In each case, PCC.Net makes sure that the selected Rate in Booking matches with the Make/Model, Charge, Basis, Freight Collection Office and Payment Method of the Contract’s latest revision.
    • The Revenue payment method (P/C) values are defaulted from the Contract during creation of the Revenue for the first time in Booking. While refreshing Rate from Contract in Booking, PCC.NET neither checks if the (P/C) value has been changed in Contract, nor replaces that updated value from Contract.

     

Amount

PCC.NET automatically calculates this amount by multiplying the value of Rate with Rated At. Read-only.

Amount is rounded off up to the precision value of currency but shows the saved values up to two digits after decimal point.

Freight Collection Office

Organization name of the freight collection office of the charge. By default, PCC.NET populates this field from Contract; if unavailable, it populates from the Location Master (RFLCW10) screen with respect to the Booking Load Port. You can update this field. You can enter either the six-character organization code or the organization name. This field has the Auto-Complete feature, which helps you to populate the relevant organization as you type.

Invoicing Office

The organization where the invoice for the corresponding charge is created.

  • By default, PCC.NET populates this value from Contract. If it is unavailable in contract, PCC.NET populates it from Location Master with respect to Booking Load Port. You can update this field.

  • If you (as Invoice Office user) add this organization, you can enter either the six-character organization code or the organization name. This field has the Auto-Complete feature, which helps you to populate the relevant organization as you type. After selection, the full organization name is displayed.

Payer

Payer is a customer who pays the charges in the invoice. By default, PCC.NET populates this value from Contract. However, you can add or edit this values. This field has the Auto-Complete feature, which helps you to populate the relevant payer as you type at least three characters.

You may select the Dummy Customer (2nd Hand Car (9999996)) in Collect Transaction as Payer.

Buttons

Button to open the corresponding record in edit mode in the record row. As you click this button, the corresponding row becomes editable and toggles to , which is used to save the updated record.

Notes:

  • You can edit all information of the Supplementary charges. For the contractual charges, you can update only the Freight Collection Office, Invoicing Office, and Payer fields.
  • To modify any rate you have to modify the Contract before using the rate or you click REFRESH RATE FROM CONTRACT for switching the rate between Broker and Broker Customer by switching the Contract number you need to click REFRESH RATE FROM CONTRACT.

You cannot modify revenue if you are assigned with the Update Booking Doc Entry Office role type along with Update Booking Without Revenue system action and delegation as Doc Entry Office.

Button to delete the corresponding charges in Booking.

Notes:

  • If you delete a supplementary charge in booking which is already present in associated contract and try to add it into booking, PCC.NET restricts you to add that supplementary charge. In order to add that charge again into booking, you must click REFRESH RATE FROM CONTRACT and add the required supplementary charge.
  • While editing a row, this button toggles to which is used to cancel editing.

REFRESH RATE FROM CONTRACT

Button to refresh and populate the rates from the latest version of the corresponding Service Contract, in case there are any changes in Contract revenue after the Booking creation, using the Refresh Rate from ContractRefresh Rate from Contract dialog box. This dialog box shows you all cargo details used for current Booking, for the concerned Load Port and Discharge Port along with the refreshed rates from Contract. Click OK in the dialog box to update all the refreshed rates in the Booking Revenue.

Field

Description

Booking Details panel

Booking Number

Current Booking number.

Contract Number

Associated Contract number of the current Booking.

Load Port

First Load Port of the cargo.

Discharge Port

Last Discharge Port of the cargo.

Cargo & Revenue panel

  • PCC.NET fetches all the cargo details associated with the latest revision of the current Contract (for the particular Customer, Contract and Port pair of the current Booking) with their associated charges.

  • By default, the cargo details added in the current Booking appear auto-selected, but you can add any other cargo from the available list of cargoes belonging to the Contract.

  • You can select only those cargo details to Booking, which are present in the corresponding Contract.

  • When you select single/multiple new cargos having multiple charges under it, the Add Revenue for Additional CargoAdd Revenue for Additional Cargo dialog box appears for selection of revenue against the newly added cargo details.

    • This dialog box does not show the already existing cargo details in the Booking. It only shows the new cargo details along with the applicable charges (sorted in the same way as it appears under the Booking Revenue Details panel).

    • All revenues against all new selected cargo details remain selected by default but you can select or deselect the revenues selectively before finally accepting the ones selected in the Booking Revenue.

    • This dialog box excludes all revenues against the selected cargo(s) for which Effective To is earlier than the current system date.

    • If any PT basis charge is selected:

      • You can select dependent applicable charges against the PT basis charge by clicking adjacent to the Basis field. On clicking , the Applicable Charges in ContractApplicable Charges in Contract dialog box appears, displaying all other changes against the same make/model and currency as that of the PT basis charge but all applicable dependent charges against that PT basis charge as setup in Contract remains selected initially. It also displays the already saved dependent charges from the latest revision of Contract against that charge. You can deselect all or some of these charges if required. On clicking OK in the dialog box, all the selected applicable charges gets associated against the PT Basis charge. Before associating, PCC.NET ensures that at least one dependent charge as specified in the corresponding Contract or any other change present under the same Make/Model is selected by you along with that PT basis charge.

      • If the corresponding PT basis charge has dependent applicable charges specified in the Contract and you have not selected any of the applicable charges, an error is shown asking you to select at least one Contract specified or any other applicable charge present under the same make/model along with that PT basis charge.

<Select all check box>

Check box to select the records.

  • If you select the check box in the column header, all records are selected at the same time that can be added to the Booking on clicking OK.

  • If you select the check box corresponding to a record, so that on clicking OK the particular record can be added to the Booking.

When you select a row for adding a cargo, PCC.NET automatically selects all the rows for the particular cargo having different charges. After selection of the cargo, if you click OK, all the selected cargo details and the associated latest rates from the Contract are added to the Booking.

Cargo Seq

Cargo sequence number. It helps to identify the sequence associated with Booking cargo in case of multiple generic Make and Model.

Cargo Type

Type of the cargo associated with current Contract.

Make

Identification name of the car manufacturer associated with current Contract.

Model

Model name of the cargo associated with current Contract.

Charges

Charges associated with current Contract.

Basis

Basis for calculation of the charge.

Rate

Charge rate associated with the charge.

P/C

P for prepaid charges, C for collect charges.

Currency

Charge currency applicable to the rate.

Buttons

CANCEL

Button to close the dialog box.

OK

Button to add the selected records to the Booking.

During Booking creation, Revenue information, both Contractual and Supplementary, are inherited from the corresponding Contract. For Contractual charges retrieved in the Booking, only the Freight Collection Office, Invoicing Office, and Payer information can be updated. If there is any change in the Contract revenue after the Booking creation, it must reflect in the corresponding Booking also. The latest rates of the Contract can be inherited in the Booking using REFRESH RATE FROM CONTRACT. The modified revenue details of the Contract linked with the corresponding Booking for the concerned Load Port and Discharge Port can be updated by virtue of this feature. This is applicable to both Contractual and Supplementary charges in the Contract.

Rates from the Contract that are populated in the dialog box and refreshed:

  • The rates that have changed in the Contract for the particular Make and Model associated with the Booking.

  • The rates whose effective date in the Contract are same as or earlier than the ETD of the first Mother/PCL vessel associated with the Booking leg.

  • If a charge with basis PT gets refreshed from the Contract, it retrieves only the updated Rate from the latest revision of the corresponding Contract; the dependent applicable charges are not changed during this operation.

The discrepancy between Contract revenue and Booking revenue is displayed in Blue color.

  • If the whole record appears in Blue, it indicates that a new revenue charge is added in the Contract.
  • If only the Rate field appears in Blue, it indicates that the revenue charge is updated in the Contract.

This button is not applicable if you are assigned with the Update Booking Doc Entry Office role type along with Update Booking Without Revenue system action and delegation as Doc Entry Office.

FREIGHT SUMMARY

Button to view the total Prepaid and total Collect charges currency wise in the Freight SummaryFreight Summary pop-up.

This button is not applicable if you are assigned with the Update Booking Doc Entry Office role type along with Update Booking Without Revenue system action and delegation as Doc Entry Office.

ADD REVENUE

Button to add new blank row to add Supplementary charges to the Booking. You can enter the revenue details and click to save the entry.

This button is not applicable if you are assigned with the Update Booking Doc Entry Office role type along with Update Booking Without Revenue system action and delegation as Doc Entry Office.

Remarks & Terms panel

Copy mode:

All details are populated from the source Booking No.

Booking Remarks

Additional remarks for the Booking. This field initially populates the default value from the Contract (Remarks for Booking Remarks field) while creating the Booking from Contract. You can keep its default value or can enter any other additional Booking remarks.

You can enter a maximum of 4000 characters.

Freight Remarks

Additional freight-related remarks for the Booking. This field initially populates the default value from the Contract (Remarks for Freight Remarks field) while creating the Booking from Contract. You can keep its default value or can enter any other additional freight remarks.

You can enter a maximum of 4000 characters.

Term

Drop-down list displaying the terms for the cargo. These are used by the PL reports. This is a read-only value auto-populated from Contract. Probable values are:

  • BT: Berth Term. Indicates cargo to be shipped under rate that includes cost from end of ship’s tackle at load port to end of ship’s tackle at discharge port.

  • FIFO: Free in/Free out. Indicates carrier is not responsible for the cost of loading and unloading goods onto/from the vessel.

  • LIFO: Liner in/Free out. Indicates freight rate includes charges for loading of cargo on the vessel at the port of origin but not for its unloading at the port of destination.

  • FILO: Free in/Liner out. Indicates freight rate includes carriage and the cost of unloading as per the custom of the port. Free in liner out rate excludes the cost of loading and (where required) the cost of stowage and lashing.

Customs Clearance Number

Customs Clearance number is a number issued by the Australian or New Zealand Customs to identify each cargo to be exported from Australia or New Zealand. Required if the From Location (LP) is in Australia or New Zealand.

BL As Arranged

Check box to select if the B/L contains Freight.

Buttons

GENERATE BCN (SHORT)

Button to generate the short version of Booking Confirmation Notice (BCN). You can send this report to the Customer and MOL Sales Person after the Booking is Accepted or Reconciled. If required, you can also send it when the Booking is in Requested status. The customer can be either Shipper and/or Initiator and/or Forwarder (if present) of the Booking. The intended user group can be Sales & Customer Service and Voyage Controller.

This version is sent for Asia Pacific region as a confirmation of Booking. The Generalized Report Submission (RPGRW01) screen appears when you click this button allowing you to generate the report on the basis of Booking number. Once submitted, you can search through Vessel, Voyage Number, Voyage Name, PCC-LINE, Booking number, Customer type/Code.

  • You can e-mail, print or download the report on request when a Booking is confirmed.

  • The report contains Booking Numbers and other information using which the customer can proceed to create Shipping Instructions.

    Report Column

    Description

     

    Customer Name

    Name of the Shipper or Initiator.  This column shows the Shipper name, if available. If not, the name of the Initiator is displayed.

    Vessel/Voyage

    If you search with only Booking number, the column shows the first leg of the Booking route of either line or PCL voyage name. If youl search with vessel-voyage-customer, then it will show the first leg of Booking route of either line or PCL voyage name. Feeder is not considered.

    L/Port

    The first Port of Loading for the first leg in the Booking Route.

    L/Port ETA

    ETA of the first load port of either PCL or Line of the Booking. The Date format is populated based on the country of the logged-in user’s organization.

    L/Port ETD

    ETD of the first load port of either PCL or Line of the Booking. The Date format is populated based on the country of the logged-in user’s organization.

    D/Port

    Discharge Port is the last Port of discharge for the last leg in the Booking Route.

    D/Port ETA

    ETA of last discharge port of either PCL or Line of the Booking.

    Cut Off Date

    This column will be left blank in report irrespective of the delivery mode. You must enter the date.

    Make

    Make of the cargo. This column may display multiple records if the Booking contains multiple Makes.

    Unit

    Number of cargo. This column may display multiple records if the Booking contains different numbers of the Make.

    DIMs per unit (m)

    Length, width and height of the cargo per unit in meter.

    Weight Per Unit (kg)

    Unit weight of the cargo (in Kg). This may generate multiple records if the Booking contains unit weights of the cargo.

    BKG NO.

    Booking number you have selected.

  • All routes in the Booking must be approved or arranged before a Booking is deemed to be accepted for BCN issuance. BCN is generated both for Firmed and Intended Voyage and Booking status is Requested, Accepted or Reconciled.

  • BCN issuance is not applicable for Space-Checking Bookings.

GENERATE BCN (LONG)

Button to generate the long version of Booking Confirmation Notice (BCN). You can send this report to the Customer and MOL Sales Person when the Booking is Accepted or Reconciled. If required, you can also send it when the Booking is in Requested status. The customer can be either Shipper and/or Initiator and/or Forwarder (if present) of the Booking. The intended user group can be Sales and Customer Service and Voyage Controller.

The Long version of BCN is meant for Atlantic region. The Generalized Report Submission (RPGRW01) screen appears when you click this button allowing you to generate the report on the basis of the Booking number. Once submitted, you can search through Vessel, Voyage Number, Voyage Name, PCC-LINE, Booking number, Customer type/Code.

  • You can e-mail, print or download the report on request when a Booking is confirmed.

  • The report contains Booking Numbers and other information using which the customer can proceed to create Shipping Instructions.

    Report Column

    Description

     

    Quote/Contract No.

    Contract Number associated with the Booking.

    MOL Booking Reference/No.

    Booking number.

    Vessel

    If you search with only Booking number, the first leg of the Booking route of either Line or PCL vessel name is printed. If you search with vessel, voyage and customer, the first leg of booking route of either line or PCL vessel name is printed. Feeders are not considered.

    Voyage

    If you search with only Booking number, the voyage of first leg of Booking route of either Line or PCL vessel is printed. If you search with vessel, voyage and customer, the voyage code of first leg of Booking route of either Line or PCL vessel name is printed. Feeders are not considered.

    Cut-Off Date

    This field will be blank in report. You must enter the date manually. Blank "Cut Off date" will be sent to the customer if delivery mode is e-mail. Current user can download or print the report output and enter in "Cut off" date.

    Load Port

    The first Port of Loading for the first leg of either PCL or Line in the Booking Route. This is same as place of receipt for PCC.

    Load Port ETD

    ETD of first load port of either PCL or Line of the Booking. Date format will be as retrieved against country of Freight Collection Office associated with the logged-in user.

    T/S Details

    This shows the complete Booking route including PCL/Line/Feeder.

    Discharge Port

    Last Port of discharge for the last leg of either PCL or Line in the Booking Route. This will be same as place of delivery for PCC.

    Discharge Port ETA

    This will ETA of last discharge port of either PCL or Line of the Booking. Date format will be as retrieved against country of Freight Collection Office associated with the logged-in user.

    Cargo Descriptio

    There could be multiples of these within a Booking, effectively one line per make/model.

    No. of Unit

    Number of cargo. This may generate multiple records if the Booking contains different numbers of the make.

    Length, Width, Height Per Unit

    Length, Width, Height per unit of the cargo.

    Weight Per Unit

    This will be unit weight of the cargo. This may generate multiple records if the Booking contains unit weights of the cargo.

    Rate

    This may also be multiple within each cargo (make, model, line).

    Currency

    This may also be multiple within each cargo (make, model, line).

    Charge Type

    This may also be multiple within each cargo (make, model, line).

    Rate Basis

    This may also be multiple within each cargo (make, model, line).

    Freight Term

    Booking Revenue; P indicates Prepaid, C indicates Collect; This may also be multiple within each cargo (make, model, line).

    Invoice Customer

    This may also be multiple within each cargo (make, model, line).

    Shipment Terms

    Booking shipment term.

    B/L Place of Issue

    Place where the B/L is issued as retrieved from Booking Documentation Issue Office.

    B/L Terms & Conditions

    B/L Terms and Conditions.

    Waybill Terms & Conditions

    Waybill Terms and Conditions.

    High & Heavy Terms & Conditions

    High & Heavy Terms and Conditions.

    Used Vehicles Terms & Conditions

    Used Vehicles Terms and Conditions.

    Break Bulk Terms & Conditions

    Break Bulk Terms and Conditions.

  • All routes in the Booking must be approved or arranged before a Booking is deemed to be accepted for BCN issuance. BCN is generated both for Firmed and Intended voyage and Booking status is Requested, Accepted or Reconciled.

  • BCN issuance is not applicable for Space-Checking Bookings.

In PCC.NET, Booking Confirmation Notice (BCN) is generated to provide response to the customer who has made Bookings with MOL.

This button is not applicable if you are assigned with the Update Booking Doc Entry Office role type along with Update Booking Without Revenue system action and delegation as Doc Entry Office.

FMC FILING

Button to provide the FMC Filing details for Bookings having Load Port or Discharge Port belonging to the port of US territories using the FMC DetailsFMC Details dialog box. It displays all cargo associated with current Booking and all revenues and their FMC information associated with current Booking.

Field

Description

Shipment Details pane...

Booking No

Booking number for which FMC filing is being done.

Shipper (BKG)

Shipper associated with the Booking.

Shipper (Doc)

Shipper associated with the Bill of Lading.

Sail Date

Vessel's Actual Time of Departure (ATD) from the US bound port.

If ATD of the Voyage at Load port is unavailable, PCC.NET uses the Estimated Time of Departure (ETD).

POD

Port of Discharge. US bound Discharge Port.

POL

Port of Loading. US bound Load Port.

FMC References pane

Pending for Approval

Check box to indicate that the particular Booking is awaiting approval from FMC.

By selecting it, you can postpone the actual FMC filing of a Booking of U.S. bound shipment until its B/L is ready for invoice issuance. You can request, accept, and reconcile a U.S. bound Booking without associating FMC for this Booking but cannot change the status of its B/L to Ready for Iss/Inv until the actual FMC documents are associated with the Booking.

When you try to select this check box, PCC.NET checks if there is any revenue having valid FMC Filing Number under any of the cargoes. If present, a warning message appears stating that FMC Filing information is already entered for the associated revenue, and asking your confirmation to remove them.

  • On your denial, this check box remains deselected.

  • In case, no revenue exists with FMC filling number, or you confirm to remove the FMC information, PCC.NET does the following:

    • disables Space Chatter Filling number and clears its content.

    • disables Cargo Details pane and Exempt FMC check box and deselects the check box.

    • disables FMC Filing against Revenue pane and clears all FMC data from each revenue.

Space Charter Filing No.

Space Charter Out Agreement Number. It can be entered only when the Pending for Approval check box is deselected.

This field has the Auto-Complete feature, which helps you to populate the relevant FMC Filing Number as you type. The number is selected from FMC Document Entry screen. The description of the filing number appears as a tooltip when you hover over this field. 

As soon as you enter the Space charter filing Number, PCC.NET checks if there is any revenue with valid FMC Filing number under any of these cargoes. If so, a warning message appears stating that FMC Filing information is already entered for the associated revenue, and asking your confirmation to remove them.

  • On your denial, Space Charter Filing number becomes blank again.

  • In case, no revenue exists with FMC filling number, or you confirm to remove the FMC information, PCC.NET does the following:

    • disable Cargo Details pane and Exempt FMC check box and deselect the check box.

    • disable FMC Filing against Revenue pane and clears all FMC data from each revenue.

Operator

Vessel Operator. Read-only.

This information in this pane is retrieved from FMC Document Details (OPBKW24) screen.

Effective date

Effective date of FMC filing. Read-only.

This information in this pane is retrieved from FMC Document Details (OPBKW24) screen.

Expiry date

Expiry date of FMC filing. Read-only.

This information in this pane is retrieved from FMC Document Details (OPBKW24) screen.

Cargo Details pane

All information in this pane is populated from the Cargo panel of Booking.

Cargo Type

Description of the cargo type associated with the Booking.

Make

Identification name of the car manufacturer for each cargo item. Make associated with the corresponding Booking based on the cargo sequence. It is the identification code of the automobile manufacturer along with the name.

Model

Model Name of the Cargo.

Units

Number of units shipped in the Booking.

Exempt FMC

Check box, if selected, indicates FMC is not required for the particular cargo and corresponding Revenue.

As soon as you select this check box, PCC.NET checks if there is any revenue with valid FMC Filing number under any of these cargoes. If so, a warning message appears stating that FMC Filing information is already entered for the associated revenue, and asking your confirmation to remove them.

  • On your denial, Exempt FMC remains deselected.

  • In case, no revenue exists with FMC filling number, or you confirm to remove the FMC information, PCC.NET disables FMC Filing against Revenue pane and clears all FMC data from each revenue.

FMC Filing Against Revenue pane

Make/Model

Description for Make and Model.

Payer

Payer associated with the particular revenue item.

Charge

Charge type.

Basis

Basis for calculation.

Rate

Charge rate associated with current revenue item.

Currency

Charge currency applicable to the rate.

Amount

PCC.NET automatically calculated this amount by multiplying the value of Rate with Rated At.

Type

Type of FMC Filing. Select a value from the drop-down list:

  • Tariff (TLI)

  • Service Contract

  • Rule

  • Space Charter Agreement

FMC Filing #

FMC Filing number of corresponding FMC Type. This field has the Auto-Complete feature, which helps you to populate the relevant FMC Filing Number as you type. PCC.NET retrieves this value from FMC Document Details (OPBKW24) screen.

The description of the filing number appears as a tooltip when you hover over this field. 

Not applicable to Pending for Approval Type.

FMC Customer

Associated Customer of corresponding FMC Filing number.

Not applicable to Pending for Approval Type.

FMC Effective date

Effective date of corresponding FMC Filing number.

Not applicable to Pending for Approval Type.

FMC Expiry date

Expiry date of corresponding FMC Filing number.

Not applicable to Pending for Approval Type.

CANCEL

Button to close the dialog box.

OK

Button to associate FMC details with the current Booking. Before associating the FMC details, PCC.NET checks that any of the following four conditions is satisfied and displays corresponding relevant error message in case of discrepancy:

  • FMC filing information is marked as Pending for Approval.

OR,

  • Space Charter Filing No. is entered.

OR,

  • All cargoes of the current Booking are marked as Exempt FMC.

OR,

  • If any cargo is not marked as Exempt FMC, all revenues present in the Revenue Details panel under that particular cargo should have valid FMC filling numbers associated with them.

PCC.NET also checks the following conditions and displays relevant warning messages requiring your acceptance if any of the conditions fails. PCC.NET associates the FMC document with the current Booking only after you accept. 

  • If Departs On (ETD) of the first port of Booking is before or on the Effective Date of FMC Filing, PCC.NET displays a warning that associated FMC file is not yet effective for the first port ETD.

  • If Departs On (ETD) of the first port of Booking is after or on the Expiry Date of FMC Filing, PCC.NET displays a warning that the associated FMC file has expired for the first port ETD.

  • If the day count between Expiry Date of FMC Filing and Departs On (ETD) of the first port of Booking is within 10 days, PCC.NET displays a warning that expiry date of FMC Filing is getting close.

The first port ETD is Departs On (ETD) of first leg sequence of Route of the Booking. This first port ETD is shown in the FMC Details dialog box as the Sail Date.

 

You can enter FMC filing information for both Contractual and Supplementary charges as per certain conditionscertain conditions.

To update the FMC details in a Booking, any of the following information must be provided in the FMC Details dialog box:

  1. To indicate that FMC filing is not yet complete for the Booking and postpone the filing, select the Pending for Approval check box in the FMC References pane.
  2. If the above step is not feasible, provide either of the following information at Port-pair/Cargo/Revenue level:
  1. Enter either the Space Charter Filing No. for the Port-pair in the FMC References pane.

                Or,

  1. Select Exempt FMC check box for all cargoes of the current Bookings in the Cargo Details panel.

If any cargo is not selected as Exempt FMC, all revenues present in the Revenue Details panel for that particular cargo should have valid FMC filing numbers associated with them.

 

Notes:

  • FMC filing is applicable and required only for Bookings having Origin/Destination in US territory. For these cases, Bookings does not change from Draft to Requested or from Requested to Accepted status unless the FMC Details is completed.

  • You can postpone the actual FMC filing of a Booking of U.S. bound shipment until its B/L is ready for invoice issuance. In this regard, you need to select Pending for Approval check box in the dialog box.

  • If there is any Supplementary charge which is not associated with any Make/Model, PCC.NET does not check for FMC information against it.

  • FMC Information Defaulted from Contract (if available)FMC Information Defaulted from Contract (if available)

    FMC information can be added to a Contract having Origin/Destination in US territory, but is not mandatory. If available, the information is populated in the corresponding Booking during:

    • Create Booking from Contract

    • Add Cargo from Contract

    • Add Revenue in Booking by Refresh Rate From Contract

    While creating Booking from Contract, PCC.NET retrieves and default FMC-related information for the newly-added cargoes in the Booking as per the following logic. Once defaulted from Contract, Booking user can change the FMC Filing type and FMC Number in Booking. FMC information is eventually defaulted from Booking in B/L.

    • FMC information retrieved during creating a Booking from Contract

      While creating a Booking, if FMC information is already entered in the corresponding Contract (having Origin/Destination in the US territory), that information gets automatically populated in the FMC Details dialog box of the corresponding Booking.

      • If the FMC information is entered at Port-pair level of a Contract, the information gets populated in the FMC References pane of the FMC Details dialog box.

      • If the FMC information is entered at Make Model level of a Contract, the Exempt FMC check box gets selected in the Cargo Details panel of the FMC Details dialog box.

      • If the FMC information is entered at Revenue level of a Contract, the information gets populated in the FMC Filing Against Revenue panel of the FMC Details dialog box.

      Notes:

      • If the FMC information entered in a Contract is an expired one, while creating a Booking from the Contract, PCC.NET displays an warning message ("600036-CON-Contract contains expired FMC information. Do you want to proceed with expired FMC?") asking user whether to apply expired FMC information in the Booking. You need to confirm in the message to apply the FMC details in that Booking.

      • During Booking creation PCC.NET checks if Space Charter Agreement Number entered in the Contract is not deleted from the FMC Document Details (OPBKW07) screen. If that Space Charter Agreement Number is deleted from FMC Document Details (OPBKW07) screen, PCC.NET ignores the Space Charter Agreement Number and creates the Booking without any FMC information.

      • While updating the FMC information in a Booking, if the FMC information is already entered in the Revenue level, and you try to select the Exempt FMC check box, PCC.NET displays an warning message,"There are already FMC Filing information entered with associated revenue. Do you want to remove them?". You need to confirm the deletion in the message.

      • While updating the FMC information in a Booking, if you clear the Exempt FMC check box and add FMC information against only one Revenue, while saving, PCC.NET displays an error message "300062-BKG-Required FMC filing details for cargo seq.1 and Revenue seq. 2".

      FMC information retrieved during Refresh Rate from Contract after Rollover

      • If Rollover does not change First LP or Last DP, there is no impact on FMC details retrieved during Refresh Rate from Contract.

      • 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.

      FMC information retrieved during Refresh Rate from Contract (without Rollover)

      • If the Contract has FMC information at the Revenue level, during the Refresh Rate from Contract process, the same is selected against that Booking Revenue.

      • If Booking has Space Charter Agreement number in the FMC Reference pane of the FMC Details dialog box, Contract-specific FMC information is ignored.

      FMC information retrieved during adding Cargo from Contract

      • If the Contract has FMC information at the port-pair level, FMC information present for the newly-added cargos in the Contract does not get displayed in the Booking.

      • If the Contract has FMC information at the Cargo or Revenue level, FMC information gets retrieved in the Booking.

      Notes:

      • During Add Cargo from Booking, PCC.NET checks if Space Charter Agreement Number is available in the FMC Reference pane of the FMC Details dialog box. If any Space Charter Agreement Number is entered in the Booking, FMC information does not get retrieved in the Booking.
      • During Add Cargo from Contract, PCC.NET checks if Space Charter Agreement Number entered in the Contract is active in the FMC Document Details (OPBKW07) screen. If that Space Charter Agreement Number is deleted from FMC Document Details (OPBKW07) screen, PCC.NET ignores Space Charter Agreement Number.
      • If the FMC information is an expired one with respect to the ETD of the first load port, PCC.NET displays warning message.

Copy mode:

All details are populated from the source Booking No.

CANCEL

Button to close the Create/Update Booking (OPBKW02) screen and navigate to the Search Booking (OPBKW01) screen. If there is any change in the Booking, a warning message appears when you click this button asking you to confirm the cancellation.

SAVE

Button to save the changes you make in the Booking.

Create/Edit mode:

When you click this button, Add Transaction LogAdd Transaction Log dialog box is displayed to specify the changes you made in the Booking, so that PCC.NET can save the log entry in the Booking log.

PCC.NET considers the booking to be Used Car Booking if commodity code for any associated Cargo falls within list of domain items defined in the Code Definition (ADCMW02) screen (domain=USED_CAR_CMD_DOMAIN), for example, N07. In rest of the cases, PCC.NET considers it as New Car Booking.

Copy mode:

When you click this button, a new Booking number is generated.

Notes:

  • Mandatory information required to save a Booking and change its statuses
  • Conditions to accept a Booking
  • How PCC.NET checks for duplicate BookingsHow PCC.NET checks for duplicate Bookings

    Duplicate Booking check is done during following status changes when a similar kind of Booking exists in Requested, Accepted, and Reconciled status:

    • Draft to Requested: When you complete entering all Booking information and try to change the Booking status by clicking SAVE.

    • Accepted to Requested: For example, when you change Cargo, Voyage or Route information in a Booking in Accepted status.

    • Requested to Requested: For example, when you change Booking data keeping its status unchanged to Requested.

    It checks for duplicate Bookings based on following Booking parameters:

    • LP-DP

    • Make/Model

    • Units (along with Unit of Measurement)

    • All Customers (Initiator, Shipper, Forwarder and Consignee)

    When PCC.NET finds duplicate Bookings, it displays a warning message with the option to proceed on your confirmation.

  • Validations that PCC.NET checks internally while you save a BookingValidations that PCC.NET checks internally while you save a Booking

    PCC.NET checks the following validations when you try to save the Booking and display errors if they fail:

    • Booking date must be before or on the date of ATD/ETD at the first Load Port (applicable for PCL/Line transport modes)

    • Customer (Initiator, Shipper, Forwarder, Consignee) in a Booking information must not have been deleted.

    • Doc Entry Office and Doc Issuing Office must not have been deleted.

    • For the first leg of Route From Location (LP) must be same as the Load Port (PR). Similarly, for the last leg of Route To Location (DP) must be same as the Discharge Port (PD).

    • Location set as From Location (LP) or To Location (DP) must not be Inactive and not deleted from the selected voyage (if any).

    • ATA/ETA value for the Arrives on Port should be later than the ATD/ETD of the Departs on Port.

    • From Location (LP) and To Location (DP) has not been deleted from the selected voyage.

    FMC Details-related Checks:

    Before associating the FMC details, PCC.NET checks the following conditions and displays relevant warning messages requiring your acceptance if any of the following fails. PCC.NET associate the FMC document with the current Booking only after you accept the warning.

    • If Departs On (ETD) of the first port of Booking is before or on the Effective Date of FMC Filing, PCC.NET displays a warning that associated FMC file is not yet effective for the first port ETD.

    • If Departs On (ETD) of the first port of Booking is after or on the Expiry Date of FMC Filing, PCC.NET displays a warning that the associated FMC file has expired for the first port ETD.

    • If the day count between Expiry Date of FMC Filing and Departs On (ETD) of the first port of Booking is within 10 days, PCC.NET displays a warning that expiry date of FMC Filing is getting close.

    The first port ETD is Departs On (ETD) of first leg sequence of Route of the Booking. This first port ETD is shown in the FMC Details dialog box as the Sail Date.

Return