| Manual changes to cluster dataThe cluster status determines the changes that you can manually
insert in freight order clusters and cluster lines. Clustered After a freight order cluster is generated, you can manually
change the cluster header information in the following fields: Carrier This field shows the carrier that LN found during the
clustering process, or that was entered for the freight order lines related to
the current cluster. You can change the carrier in this field if you want to
subcontract the cluster to a carrier other than the one found by LN or entered on the
corresponding freight order lines. This field is empty if LN cannot find a suitable
carrier, or if no carrier was entered manually on the freight order lines from
which the cluster was generated. In such cases, you can manually enter a
carrier. This also applies to binding carriers. A binding carrier is a carrier
entered on a freight order line that LN cannot override during the load building or
clustering process. To insert a binding carrier, enter a carrier and select the Carrier Binding check box in the Freight Order Lines (fmfoc2101m000) session. Transport means group This field shows the transport means group that LN found during the
clustering process, or that was entered for the freight order lines related to
the current cluster. You can change the transport means group in this field if
you want the cluster to be transported by means of a transport means group
other than the one found by LN or entered on the corresponding freight
order lines. This field is empty if LN cannot find a suitable transport means
group, or if no transport means group was entered manually on the freight order
lines from which the cluster was generated. In such cases, you can manually
enter a transport means group. Planned load date The default value in this field is taken from the freight order
lines related to the cluster. If a different date is known from the carrier,
you can enter the new date in this field. Planned unload date The default value in this field is taken from the freight order
lines related to the cluster. If a different date is known from the carrier,
you can enter the new date in this field. Planned distance The planned distance is taken from the freight order lines
related to the cluster. If a different distance is known from the carrier, you
can enter the new distance in this field. Estimated freight costs The estimated freight costs are calculated during the
clustering process, if freight rates are maintained for the carrier selected or
entered for the cluster. If required, you can manually change the estimated
freight costs, or recalculate the estimated freight costs. To recalculate the
freight costs, click the relevant option on the appropriate menu. Calculate additional cost option You can select or clear this check box for clusters with the Clustered status. For example, if you calculated the additional costs, but later on agree
with the carrier not to pay any additional costs, you can clear this check box
and recalculate the freight costs. Freight all kinds If the carrier is changed, changing this field might also be
required. Freight all kinds is a special freight cost rating agreement with the
carrier. If the carrier and the transport requestor agree on rating according
to Freight all kinds, the official freight classes of the items will be
substituted by the Freight all kinds agreement. In LN, Freight All Kinds is defined as special freight
class. Carrier pro number If the carrier is changed, changing this field might also be
required. The Carrier PRO Number is the number given by the carrier
to identify the load. The carrier uses this number to track the
load. Calculate tax You can select this option if tax must be calculated. Changing
the setting of this check box might be required if a different carrier is
selected. Tax country Changing the setting of this check box might be required if a
different carrier is selected. Cluster text In this field, you can add some general information about the
cluster.
To change cluster line information For a cluster line, you can change the following
information: Planned load date of the line, not the header The default value in this field is taken from the freight
order lines related to the cluster. If a different date is known from the
carrier, you can enter the new date in this field. Planned unload date of the line, not the header The default value in this field is taken from the freight
order lines related to the cluster. If a different date is known from the
carrier, you can enter the new date in this field. Actual load date If the freight order line related to the cluster line has a
warehousing order line, the actual load date is filled by Warehousing with
the actual shipping or receipt date. If the freight order line related to the
cluster line has no warehousing order line, the actual load date is filled with
the date on which the status of the cluster line was changed to Shipped or Completed in the Confirm Delivery / Receipt (fmlbd3252m000) session. You can also manually enter a date,
or change the date generated by LN. Actual unload date If the freight order line related to the cluster line has a
warehousing order line, the actual unload date is filled by Warehousing with
the actual shipping or receipt date. If the freight order line related to the
cluster line has no warehousing order line, the actual load date is filled with
the date on which the status of the cluster line was changed to Shipped or Completed in the Confirm Delivery / Receipt (fmlbd3252m000) session. You can also manually enter a date,
or change the date generated by LN. Shipped quantity If the freight order line related to the cluster line has a
warehousing order line, the shipped quantity is filled by Warehousing with
the shipped or received quantity. If the freight order line related to the
cluster line has no warehousing order line, the shipped quantity is filled with
the planned quantity. You can also manually enter a quantity, or change the
quantity generated by LN. Delivered quantity If the freight order line related to the cluster line has a
warehousing order line, the delivered quantity is filled by Warehousing with
the shipped or received quantity. If the freight order line related to the
cluster line has no warehousing order line, the shipped quantity is filled with
the planned quantity. You can also manually enter a quantity, or change the
quantity generated by LN. Damaged quantity Usually, this quantity is filled when the goods have been
delivered and any information on damaged goods is known from the carrier. Shipped capacity The shipped capacity is derived from the shipped
quantity. Delivered capacity The delivered capacity is derived from the shipped
quantity. Planned additional rate quantities The additional rate quantity for the item before
transportation has taken place. The default value in this field is taken from
the freight order line related to the cluster line. Shipped additional rate quantities As a rule, you must enter this figure when the shipped
quantity is known from the carrier. If the freight order line related to the
cluster line has a warehousing order line, the shipped additional rate quantity
is filled by Warehousing with the shipped or received quantity. If the freight order
line related to the cluster line has no warehousing order line, the shipped
additional rate quantity is filled with the planned quantity. You can also
manually enter a quantity, or change the quantity generated by LN. The Recalculate for Invoice Amount check box Estimated freight costs For example, if no freight rates are maintained for a
particular carrier, you might want to enter freight costs manually. To change freight order line information You cannot change freight order line information such as
planned quantity and capacity, service level, or delivery terms, on the freight
order cluster or cluster line. This type of change is made on the corresponding
freight order line or originating order line.
To add lines to a cluster To add freight order lines to a cluster with the Clustered status, you must cluster the new freight order lines first. Freight order lines
whose properties match those of the cluster lines of the cluster will be added
to the cluster. For freight order lines whose properties do not match, a new
cluster is generated. You can manually add additional cost lines to a cluster. Delete clusters and cluster lines You can delete individual cluster lines from a cluster, or the
entire freight order cluster including all cluster lines. Freight order lines
corresponding to cluster lines that are deleted can be clustered again. Actual When you decide to make a cluster Actual,
most of the cluster data are definite and changes are less likely to be made,
except for information such as actually shipped quantities and capacities or
actual costs. Nevertheless, in the interest of caution, ERP enables you to
manually change the same data for Actual clusters as for Clustered clusters. For a cluster that has the Actual status, you cannot rerun the clustering process to add freight order lines. If
you want to add cluster lines to an Actual cluster, you must use the Undo Actualize option to set the cluster’s status
back to Clustered and then rerun the clustering process. However,
if the Actual cluster includes lines that have the Shipped or Completed status, you cannot use the Undo Actualize option. In such cases, you must
generate a new cluster for the new freight order lines. If a cluster status is reverted to Clustered, the cluster lines for the component items of a
Bill of Materials (BOM) are removed from the cluster line. Subcontracted If a cluster has the Subcontracted status, you can no longer change the
cluster, the cluster lines, the corresponding freight order lines, or the
originating order lines, except for the actual data. The actual data constitute
the following information: - Actual distance
- Shipped quantities
- Delivered quantities
- Damaged quantities
- Actual load and unload dates
- Actual freight costs (these are updated when the invoice from
the carrier is approved in the Accounts Payable module of Financials.)
You can also set Subcontracted cluster lines to Ignored.
For further information, see Ignore cluster lines. | |