Conditions and Exceptions

Navigation:  Manifest > Auto Entry Generation >

Conditions and Exceptions

Previous pageReturn to chapter overviewNext page

 

Conditions:

Identify the shipment for generating the local charges.

Program checks for shipment type and checks the route pairs based on various parameters.

By matching, the BL will be identified for which local charges are applicable.

 

Step 1: Identify the manifest which is applicable for fixed charges by checking the manifest status.

Step 2: Check for the key parameters match between Fixed charge master and Manifest information.

Combinations to check :

 

1. Based on customer specific:

(export - refer shipper cbtl key, import refer consignee cbtl key from party details)

Category + Activity + carrier + (POR + POL + POD + POF) + Customer

Category + Activity + carrier + (POR + POL + POD) + customer

Category + Activity + carrier + (POL + POD + POF) + customer

Category + Activity + carrier + (POL + POD) + customer

 

2. Without customer condition:

Category + Activity + carrier + (POR + POL + POD + POF)

Category + Activity + carrier + (POR + POL + POD)

Category + Activity + carrier + (POL + POD + POF)

Category + Activity + carrier + (POL + POD)

Category + Activity + (POL + POD)

 

Primary conditions:

 

If the above combinations are not matching, the default combination has to be checked as below.

Shipment type - export  è Category + Activity (bl type) + POL

Shipment type - Import  è Category + Activity (bl type) + POD

 

Note: If activity is selected as BOTH means, it is applicable for Import as well as Export.

 

Note: Kindly refer detailed examples provided in attached excel. Kindly ensure those cases are taken care

 

Step 3: Once the shipment (BL) is identified, check which charges are to be applied.

 

Step 4: Match the below parameters with the manifest container block.

Basis Type + COC - SOC + Hazardous Flag + OG flag + Commodity

Basis Type + COC - SOC + Hazardous Flag + OG flag

 

Basis type means respective container type combination has to be checked.

If basis type is defined as No basis, then one record will get inserted in the manifest charges.

If basis type is defined as other than NO BASIS, (20DVFCL for example) then records will get inserted in the manifest charges based on total containers available in the manifest.

 

Step 5: Once the containers are matched, check the validity dates defined in the charge master.

Type: Import – Voyage ETA has to be present between valid from and valid to date defined in the Fixed charge master.

Type: Export – Voyage ETD has to be present between valid from and valid to date defined in the Fixed charge master.

 

Step 6: The charges will be inserted in the manifest rate details and the same will get synchronized with order rate details also.

 

Points to note:

 

Once the charges are identified, check the below and then update the charges.

 a) If the charge belongs to Local charge category, then additional new charge records need to be inserted only in Order rate table.

 b) If the charge does not belong to Local charge category, then additional new charge records need to be inserted in Order rate table as well as manifest rate table.

Refer category column in bl charge master= ‘Local charges’

 

In manifest rate table, only cost related columns will get updated. Whereas in order rate details, while updating check the below conditions:

a)If the corresponding charge has CARRIER updated in Fixed charge master, then both cost and selling rate column will get updated

 b) If the corresponding charge does not have CARRIER updated in Fixed charge master, then only selling rate column will get updated. Cost rate column will read as ZERO.