A sort plan is used to sort shipments into compartments. These can be sorting compartments of a sorting machine or sorting shelves.
The sort plan defines the criteria that apply to the corresponding items for each sort compartment.
The sorting plan has a name and a remark. These can be freely chosen. However, the name can give hints about the use of the sort plan (e.g. 'Coarse sort plan A').
Sort criteria are specified for sort trays, which should apply to the items for the corresponding tray.
The sort criteria are specified in the form of <criterion name>="<value>" or <criterion name>= REGEX("<value>").
Multiple sort criteria can be listed separated by semicolons. All sorting criteria for a subject are linked AND.
| Criterion |
Value |
Comment |
| Sorting by district |
|
|
| Bez-UPOC |
UPOC District |
Active counties only
DB: district.strUPOC |
| Bez-Name |
District Designation/Name |
Active counties only
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 billing |
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 |
|
|
| Bez-Ort-SI |
DistrictCity SortInfo |
DB: DistrictCity.strSortInfo |
| Sorting by district-street |
|
|
| Bez-Str-SI |
DistrictStreet SortInfo |
DB: DistrictStrasse.strSortInfo |
| Bez-Str-ZI |
DistrictRoad DeliveryInfo |
DB: DistrictStrasse.strDeliveryInfo |
Sorting by district House number range
(only outgoing mail/AZD) |
|
|
| Bez-HausNr-SI |
|
DB: DistrictNoArea.strSortInfo |
| Bez-HausNr-ZI |
|
DB: DistrictNoArea.strDeliveryInfo |
| District house number distribution |
|
DB: DistrictNoArea.eDivision |
| Bez-HausNr-From |
|
DB: DistrictNoArea.lFrom |
| Bez-HausNr-Bis |
|
DB: DistrictNrArea.lTo |
| Bez-HausNr-Von-Zusatz |
|
DB: DistrictNoArea.strHouseNoAdditionFrom |
| Bez-HausNr-Bis-Addition |
|
DB: DistrictNrArea.strHouseNrAdditionTo |
Sorting by district IHS
(only incoming mail/IHS) |
|
|
| 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 |
District group SortInfo |
DB: District group.strSortInfo |
| Sorting by depot |
|
|
| Depot UPOC |
UPOC depot |
DB: Depot.strUPOC |
| Depot name |
Depot designation/name |
DB: Depot.strDesignation |
| Depot-Bem |
Depot description/comment |
DB: Depot.strDescription |
| Depot-SI |
Depot SortInfo |
DB: Depot.strSortInfo |
| Sorting by transshipment point (DepotHub) |
|
|
| Hub-UPOC |
UPOC transhipment centre |
DB: DepotHub.strUPOC |
| Hub name |
Terminal Name |
DB: DepotHub.strName |
| Hub-Bem |
Transshipment point Remark |
DB: DepotHub.strRemark |
| Hub-SI |
SortInfo transshipment point |
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: Delivery tour group.strUPOC |
| ATG name |
Delivery tour group name/designation |
DB: DeliveryTourGroup.strDistrict |
| ATG-Bem |
Delivery tour group Comment |
DB: DeliveryTourGroup.strBem |
| Sorting according to delivery route |
|
|
| AT-UPOC |
Delivery tour UPOC |
DB: Delivery tour.strUPOC |
| AT name |
Auslierfertour Name/Tour |
DB: Delivery tour.strReference |
| AT-Bem |
Auslierfertour Remark |
DB: Delivery tour.strBem |
| AT-SI |
Delivery tour SortInfo |
DB: Delivery Route.strSortInfo |
| Sorting according to the sequence of unloading points in the delivery round |
|
|
| AT-DropLoc-Order |
|
DeliveryTourDropLocation |
| Sorting according to delivery organization |
|
|
| ZO-UPOC |
UPOC delivery organization |
DB: Delivery organization.strUPOC |
| ZO name |
Delivery organisation Designation |
DB: Delivery organization.strDistrict |
| ZO-Bem |
Delivery organisation Description/comment |
DB: Delivery organization.strBem |
| ZO-SI |
SortInfo delivery organization |
DB: Delivery organization.strSortInfo |
| Sort by country |
|
|
| Land UPOC |
|
DB: Country.strUPOC |
| Country ISO code |
|
DB: Country.strISOCode |
| Country name |
|
DB: Country.strCountry |
| Sort by location |
|
|
| Location-UPOC |
|
DB: Place.strUPOC |
| City-PLZ |
|
DB: City.strPLZ |
| City-Name |
|
DB: Place.strPlace |
| Sorting by district |
|
|
| Local Area UPOC |
|
District.strUPOC |
| District name |
|
District.strDistrict |
| Sort by street |
|
|
| Str-UPOC |
|
Street.strUPOC |
| Str name |
|
street.strstreet |
| Str-ZI |
|
Street.strDeliveryInfo |
| Sort 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 according to consignment format |
|
|
| Item Format Name |
|
ShipmentFormat.strDesignation |
| 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 according to shipment weight |
|
|
| Item-Weight-Min |
Minimum weight of the consignment in grams |
|
| Item Weight Max |
Maximum weight of the consignment in grams |
|
| Sorting according to cost unit |
|
|
| KG name |
Customer group Designation/name |
All cost objects in the customer group
DB: Customer group.strReference |
| KKS-UPOC |
Cost object (customer/cost center) UPOC |
Only active cost objects
DB: KKS.strUPOC |
| KKS-Func |
FAFunction Designation |
DB: FAFunction.strReference |
| KU-No |
Customer number |
Only active customers
DB: CustomerCostCentreView.strCustomerNo |
| KU name |
Customer Name1 |
Only active customers
DB: CustomerCostCentreView.strCustomerName1 |
| KS-No |
Cost center number |
Only active cost centers
DB: CustomerCostCenterView.strKsNr |
| KS name |
Cost center Name1 |
Only active cost centers
DB: CustomerCostCenterView.strKsName1 |
| Sorting by recipient person |
|
|
| Person-UPOC |
Person UPOC |
Only active persons
DB: Person.strUPOC |
| Sorting by article |
|
|
| Article-UPOC |
Article UPOC |
Only active articles
DB: Article.strUPOC |
| Sorting by AlternativeCode |
|
|
| AlternativeCode |
Alternate consignment code |
The captured value is always interpreted as Case Insensitive Regex!
Accordingly, the regex syntax must be observed (e.g. escape character).
DB: SBB.strAlternativeCode |
| Sorting by order identifier |
|
|
| OrderIdent |
Order identifier of the consignment |
The captured value is always interpreted as Case Insensitive Regex !
Accordingly, the regex syntax must be observed (e.g. escape character).
DB: ShipmentDet.strOrderIdentifier |
Sort criteria can also contain regular expressions (RegEx), which can be used to create very complex and flexible sort plans.
A RegEx expression is specified with the function name RegEx("...").
Example: All districts where the name starts with
begins with 'ABC':
Function trays are used for a specific function depending on the application. A function tray is identified by a name. The name is specified by the application. In a sort plan, all function trays that the application requires must be defined. Otherwise the sort plan cannot be loaded.
| Function tray |
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 probably captured a valid image, but the data expected according to ImageParser could not be read. |
| No-Sort |
CxLetterScan Sort |
No valid sort bin was found.
A unique shipment was found in the database, but there is no sort bin for its shipment data that meets the appropriate criteria. |
| No-alternative code |
CxLetterScan Capture
CxLetterScan R-Scan
CxLetterScan Scanner |
No valid alternate code was detected on the shipment. |
| No-OrderIdent |
CxLetterScan Capture
CxLetterScan R-Scan |
No valid job identifier was detected 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 the cost object. |
| No-Sender |
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 does not exist in the database. |
| No-Article |
CxLetterScan Capture |
No article was found for the shipment. |
Link compartments were used to automatically generate coarse sort plans (1st sort run) based on fine sort plans (nth sort run).
A fine sort plan is given to a link box. CodX PostOffice automatically determines all sort criteria of all sort trays of the fine sort plan
of the fine sort run and assigns them to the sort bin of the coarse sort plan. Fine sort plans can in turn contain link trays. These are also
automatically includes them in the coarse sort plan. However, there must not be any circular links (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 sort plans are not automatically copied to the coarse sort plan. However, the coarse sort plan must contain all functional compartments of all fine sort plans. Otherwise, generation is terminated with an error.