Sorting plan detail

A sorting plan is used to sort consignments into compartments. These can be sorting compartments of a sorting machine or sorting shelves. The sorting plan defines the criteria that apply to the corresponding consignments for each sorting compartment.

Sorting plan

The sorting plan has a name and a comment. These can be chosen freely. However, the name can indicate the use of the sort plan (e.g. 'Rough sort plan A')

Subjects

There are three types of subjects:

  • Sorting compartment
    Defines the criteria that a consignment must meet in order to be sorted into a compartment

  • Functional compartment
    Defines a compartment to which a consignment is ejected if a specific error occurs

  • Link compartment
    Integrates fine sorting plans into the sorting plan

Operation

  • Add
    A new empty compartment assignment is inserted below the selected line.
    If no line is selected, the new assignment is inserted at the end of the list.

  • Delete
    All selected assignments are deleted after confirmation.
    ATTENTION: The deletion cannot be undone!

  • Copy
    A copy of the selected compartment assignment is inserted below it.

  • Insert
    A new compartment assignment with an identical compartment number is inserted above the selected line.
    If no row is selected, the new assignment is inserted at the end of the list.
    All assignments with compartment numbers greater than the new compartment are incremented by one (1) until a gap is found in the compartment numbering.
    ATTENTION: This action cannot be undone!

  • Reorder
    All compartment assignments are reordered without gaps starting with 1.
    Existing compartment assignments with the same compartment number and the same compartment type are given identical new compartment numbers.
    ATTENTION: This action cannot be undone!

Sorting compartment

Sorting criteria are specified for sorting compartments, which should apply to the consignments for the corresponding compartment. The sorting criteria are specified in the form of <criterion name>="<value>" or <criterion name>= REGEX("<value>").

Several sorting criteria can be listed separately with a semicolon. All sorting criteria for a compartment are AND-linked.

If several sorting criteria apply to a sorting compartment(OR link), simply add another line with the same compartment number and the corresponding sorting criteria.

Examples: Reference-UPOC = "2599981500"; Depot name = REGEX("HPL.*")

Sorting criteria

The following sorting criteria are available:

Criterion Value Remark
Sorting by district
Bez-UPOC UPOC district Active districts only
DB: District.strUPOC
Reference name District Designation/Name Only active districts
DB: District.strDesignation
Bez-Bem District Description/comment DB: District.strDescription
Bez-SI District SortInfo DB: District.strSortInfo
Sorting by service provider zone
Bez-Zone-Sort-UPOC UPOC of the service provider zone for sorting DB: DLZone.strUPOC
Bez-Zone-Fact-UPOC UPOC of the service provider zone for invoicing DB: DLZone.strUPOC
Sorting by service provider
Bez-DL-Sort-UPOC UPOC of the service provider for sorting DB: Client.strUPOC
Bez-DL-Fact-UPOC UPOC of the service provider for invoicing DB: Client.strUPOC
Sorting by district-location
Reference-location-SI DistrictCity SortInfo DB: DistrictCity.strSortInfo
Sort by district-street
Bez-Str-SI DistrictStrasse SortInfo DB: DistrictStrasse.strSortInfo
Bez-Str-ZI DistrictStrasse DeliveryInfo DB: DistrictStrasse.strDeliveryInfo
Sorting by district House number area
(outgoing mail/AZD only)
District House No. SI DB: DistrictNoArea.strSortInfo
District House No. ZI DB: DistrictNoArea.strDeliveryInfo
District house number allocation DB: DistrictNoArea.eDivision
District-HouseNo-From DB: DistrictNoArea.lFrom
District-HouseNo-To DB: DistrictNoArea.lTo
District-HouseNo-From-Addition DB: DistrictNoArea.strHouseNoAdditionalFrom
Bez-HausNr-Bis addition DB: DistrictNoArea.strHouseNoAdditionalTo
Sorting by district-IHS
(incoming mail/IHS only)
Bez-LU-SI District IHS SortInfo DB: DistrictIHS.strSortInfo
Bez-LU-ZI District-IHSDeliveryInfo DB: DistrictIHS.strDeliveryInfo
Sorting by district group
BG-UPOC UPOC district group DB: District group.strUPOC
BG name District group Name/Designation DB: District group.strDesignation
BG-SI SortInfo district group DB: District group.strSortInfo
Sorting by depot
Depot UPOC Depot UPOC DB: Depot.strUPOC
Depot name Depot designation/name DB: Depot.strDesignation
Depot notion Depot Description/comment DB: Depot.strDescription
Depot-SI SortInfo depot DB: Depot.strSortInfo
Sorting by transshipment location (DepotHub)
Hub-UPOC Transhipment point UPOC DB: DepotHub.strUPOC
Hub name Transhipment point Name DB: DepotHub.strName
Hub notion Transhipment point Remark DB: DepotHub.strRemark
Hub-SI SortInfo transshipment center DB: DepotHub.strSortInfo
Sorting by unloading point (DropLocation)
DropLoc-UPOC Unloading point UPOC DB: DropLocation.strUPOC
DropLoc name Unloading point Designation/name DB: DropLocation.strName
Sorting by delivery tour group
ATG-UPOC Delivery tour group UPOC DB: DeliveryRouteGroup.strUPOC
ATG name Delivery tour group name/description DB: DeliveryRouteGroup.strBez
ATG-Bem Delivery tour group Comment DB: DeliveryRouteGroup.strBem
Sorting by delivery route
AT-UPOC UPOC delivery tour DB: Delivery tour.strUPOC
AT name Auslierfertour Name/Tour DB: Delivery route.strBez
AT-Bem Delivery tour Remark DB: Delivery route.strBem
AT-SI SortInfo delivery tour DB: Delivery route.strSortInfo
Sorting by sequence of unloading points in delivery route
AT-DropLoc-Order DeliveryDropLocation
Sorting by delivery organization
ZO-UPOC Delivery organization UPOC DB: Delivery organization.strUPOC
ZO name Delivery organization Designation DB: Delivery organization.strBez
ZO-Bem Delivery organization Description/comment DB: Delivery organization.strBem
ZO-SI Delivery organization SortInfo DB: Delivery organization.strSortInfo
Sorting by country
Land UPOC DB: Land.strUPOC
Country ISO code DB: Country.strISOCode
Country name DB: Land.strLand
Sort by location
Location-UPOC DB: Place.strUPOC
City-PLZ DB: City.strPLZ
Place name DB: Place.strPlace
Sorting by district
District UPOC District.strUPOC
District name district.strDistrict
Sort by street
Str-UPOC Street.strUPOC
Str-Name Street.strStrasse
Str-ZI Street.strDeliveryInfo
Sorting by house
House UPOC House.strUPOC
House no. House.strHouseNo
House-ZI House.strDeliveryInfo
Sorting by logistics unit
LU-UPOC LogisticUnit.strUPOC
LU name LogisticUnit.strName
LU-Bem LogisticUnit.strRemark
LU-SI LogisticUnit.strSortInfo
Sorting by shipment format
Item format name ShipmentFormat.strLabel
Item-Format-Width-Min Minimum width of the consignment in mm
Item-Format-Width-Max Maximum width of the consignment in mm
Item-Format-Length-Min Minimum length of the consignment in mm
Item-Format-Length-Max Maximum length of the consignment in mm
Item-Format-Height-Min Minimum height/thickness of the consignment in mm
Item-Format-Height-Max Maximum height/thickness of the consignment in mm
Sorting by consignment weight
Item-Weight-Min Minimum weight of the shipment in grams
Item-Weight-Max Maximum weight of the shipment in grams
Sorting by cost unit
KG name Customer group Designation/name All cost units in the customer group
DB: Customer group.strBez
KKS-UPOC Cost unit (customer/cost center) UPOC Only active cost units
DB: KKS.strUPOC
KKS-Func FAFunction Designation DB: FAFunction.strBez
KU no. Customer number Only active customers
DB: CustomerCostCenterView.strCustomerNo
KU name Customer Name1 Only active customers
DB: CustomerCostCenterView.strCustomerName1
KS no. Cost center number Only active cost centers
DB: CustomerCostCenterView.strCostCenterNo
KS name Cost center Name1 Only active cost centers
DB: CustomerCostCenterView.strKsName1
Sort by recipient person
Person-UPOC Person UPOC Only active persons
DB: Person.strUPOC
Sort by article
Article-UPOC Article UPOC Only active articles
DB: Article.strUPOC
Sort by alternative code
AlternativeCode Alternative code of the shipment DB: SBB.strAlternativCode
Sorting by order identifier
OrderIdent Order identification of the shipment DB: ShipmentDet.strOrder ID
Sorting by SBB-Custfield
SBB-CF<name>
<name>: Name of the SBB-Custfield
Value of the SBB custfield defined in <name>
Restrictions:
- Only SBB-Custfields of type "String" are supported!
- The function is only available if the technical license LIC_F_SP_EDITOR_SBB_CF is available!

Capitalization is not taken into account.

RegEx expressions

Sort criteria can also contain regular expressions (RegEx).
This allows very complex and flexible sorting plans to be created.
A regex expression is specified with the criterion =RegEx("...").
RexEx are always evaluated case insensitively, note the regex syntax!

Example: All districts where the name begins with 'ABC':

Ref-Name=RegEx("ABC\w+")

Functional compartment

Functional compartments are used for a specific function depending on the application. A function compartment is identified by a name. The name is specified by the application. All function trays required by the application must be defined in a sort plan. Otherwise the sort plan cannot be loaded.

The following functional compartments are available:

Functional compartment Application Description
General error CxLetterScan Capture
CxLetterScan R-Scan
CxLetterScan Sort
A general, unspecified error has occurred.
No-Read CxLetterScan Capture
CxLetterScan R-Scan
CxLetterScan Sort
The expected data of the transmission could not be read. The camera may have captured a valid image, but the data expected according to the ImageParser could not be read.
No-Sort CxLetterScan Sort No valid sorting compartment was found.
A unique shipment was found in the database, but there is no sorting compartment for its shipment data that meets the corresponding criteria.
No-alternative code CxLetterScan Capture
CxLetterScan R-Scan
CxLetterScan Scanner
No valid alternative code was recognized on the shipment.
No-OrderIdent CxLetterScan Capture
CxLetterScan R-Scan
No valid order ID was recognized on the shipment.
No-Receiver CxLetterScan Capture
CxLetterScan R-Scan
No correct recipient could be determined.
No-Customer CxLetterScan Capture
CxLetterScan R-Scan
No customer or cost center could be determined as a cost object.
No-transmitter CxLetterScan R-Scan No correct sender could be determined.
No-Franking CxLetterScan R-Scan The franking value could not be determined.
No-ItemData CxLetterScan Sort No data was found for the shipment in the database, the shipment is not available in the database.
No-Article CxLetterScan Capture No article was found for this shipment.

Capitalization is not taken into account.

Link compartment

Link trays were used for the automatic generation of coarse sorting plans (1st sorting run) based on fine sorting plans (nth sorting run).

A fine sorting plan is specified for a link tray. CodX PostOffice automatically determines all sorting criteria of all sorting trays of the fine sorting run and assigns them to the sorting tray of the coarse sorting plan. Fine sorting plans can in turn contain link trays. These are also automatically included in the coarse sort plan. However, there must be no circular references (sort plan A with link compartment on sort plan B / sort plan B with link compartment on sort plan A).

The functional compartments of fine sorting plans are not automatically transferred to the coarse sorting plan. However, the coarse sort plan must contain all the functional compartments of all the fine sort plans. Otherwise the generation is aborted with an error.

See also:



CodX Software CodX Software AG
Sinserstrasse 47
6330 Cham
Switzerland
support
http://support.codx.ch
CxSpickel