[Christopher Collins]

More information. We have discovered that the BULK PLAN is not taking into account the FAKs that have been entered on the rate offerings. When you go to CHANGE SERVICE PROVIDER the system then takes into account the FAK and that is where the cost change comes into play and the correct costs are then displayed on the shipment.

I can see in the BULK PLAN where the FAK is not being taken into account. The extract is below:

rateQualityGID: null [batch]
RateEngineDetails flexCommodityProfileGID: null [batch - 2]
RateEngineDetails flexCommodityQualifierGID: null [batch - 2]
RateEngineDetails weightBreakProfileGID: null [batch - 2]
RateEngineDetails isDiscount: true [batch - 2]
RateEngineDetails isBase: false [batch - 2]
RateEngineDetails baseRateOfferingGID: CZAR_0199 [batch - 2]
RateEngineDetails stopsIncludedInRate: 0 [batch - 2]
RateEngineDetails regionGroupGid: null [batch - 2]
RateEngineDetails REShipment: <fake> [batch - 2]
RateEngineDetails distance: null [batch - 2]
RateEngineDetails weight: 377.0 LB [batch - 2]
RateEngineDetails volume: 0.0 CUFT [batch - 2]
RateEngineDetails type: TRANSPORT [batch - 2]
RateEngineDetails Shipment:


Here is the log from the CHANGE SERVICE PROVIDER:

shipUnitSpeciGID: null
flexCommodityCode: 55.0
flexCommodityQualifierGID: NMFC_CLASS
ShipUnitLine:
sShipUnitGid: 001
sShipUnitLineNo: 1
weight: 377.0 LB
volume: 0.0 CUFT
trackingTag1: null
trackingTag2: null
trackingTag3: null
trackingTag4: null
orLineGid: 001
orderReleaseGid: 001
orderBaseGid: null
packagingUnitGid: null
packagingUnitCount: 0
itemPackageCount: 1
declaredValue: 0.0 USD
packagedItemGid: PALLETS
hazmatItemGid: null
receivedWeight: null
receivedVolume: null
receivedItemPackageCount: 0.0