Purpose

This standard search is suitable for conducting comprehensive searches for transport orders as all the details of a shipment are available.

Note: please note that the information for all the fields is not necessarily stored in the shipments.

Example: it is only expedient to search for a barcode if scanners are used in the business unit in question.

Example

Tips & tricks

Tip: ID searches with % are supported. This enables you to only enter part of an ID.

Example: %-345

Tip: for text fields such as Name, ZIP and City, inputting the start of a text suffices.

Example: ‘Dorn’ for ‘Dornbirn’

Note: the application operator can configure as many query definitions as desired for the display mode (such as detailed lists, tables, total statistics).

Fields

Display mode

Type of shipment: the selection options include outbound shipment A shipment is an order that involves the transportation of goods from a shipper's address (shipper) to a consignee's address (consignee). The order can also relate to other services, such as customs clearance without transportation or goods storage, and pass through several organization units. During the initial entry process, a shipment number is assigned, which remains the same throughout the entire workflow. On handover, a change of responsibility occurs and a copy of the shipment (shipment version) is therefore created. A shipment can be split into several shipments to create a shipment group.s, inbound shipments or customer orders.

Display mode The display mode describes how the search result should be displayed and is stored in the LBASE Client.: selection of a display mode.

Sorting The sorting defines the sort order of the results.: selection of one of the sortings stored .

Example: by shipment ID, by date

Address

Note: please note that the address is interpreted on the basis of the shipment type:

- Outbound shipments: searches for the consignee address

- Inbound shipments: searches for the shipper address

- Customer orders: searches for the consignee and the shipper

Name 1, ZIP, City, Country: any search strings can be entered or selected in these fields.

Tip: for text fields such as Name, ZIP and City, inputting the start of a text suffices.

Example: "Dorn" for "Dornbirn"

Shipment data

Searchstring: restriction to the search string that has been created during the shipment entry process.

Marks/No.:  restriction to the customer-specific name for the piece.

Example:delivery address, pcs no., item number or reference number

Bar code: restriction to the scanned barcode.

Reference: restriction to a stored reference number.

Example: customer's order number, consignee's order number

Text consignee: restriction to the additional information for the consignee

Tip: this information can be found on the delivery note.

Entry status

These settings are used as the basis for searching for shipments with the selected entry status:

• incomplete: the shipment is still being entered.

• complete: the shipment entry is complete and the check for completeness was successful.

• settled positive: the shipment has been successfully finished/delivered.

• settled negative: the shipment has not been successfully finished.

• unconfirmed: no shipment check has yet been conducted.

ID

Shipment ID: restriction to a specific shipment ID.

Trip ID: restriction to a specific route/trip ID.

Route name: restriction to the description of the route.

Filter: filters can be applied. However, these have to be defined in the LBASE Client.

Note: the filters have to be stored in the LBASE Client.

Product code: selection of a stored product.

Example: Guaranteed Saturday delivery, special collection and guaranteed 12 o'clock delivery

You have two options for storing the codes for the product:

1. In the LBASE Client via the menu path Master data / Tables of shipments / Product codes

2. The product code is defined through the creation of custom properties in the LBaseOnline configurator

Note: the LBASE Client product codes are only used if no definition has been created in LBASE Online

Order no.: entry of an order number. Searches with the %-sign are supported.

Area

Date from/to: restriction to the date of entry of the shipment

Delivery date from/to: restriction to the delivery date stored for the shipment

Pickup date from/to: restriction to the pickup date stored for the shipment

Weight from/to:  restriction to shipments with a specific total weight.

B/L-Number/Date: restrictions through the bill of lading date (first field) and number (second field) of an overseas shipment.

Note: in the LBASE Online configurator, you can hide the field B/L-Number/Date using the property sdg_uebersee.hidden.

Additions

Last POD status:  several properties are available to you for the status: see LI POD entry. In the selection, the configuration sdgauswahl.stati.lauids is used.

Additional attributes: for the shipment selection and edit masks, shipment description rows and route selection mask, an endless number of additional attributes can be stored as a list. The value corresponds to the ID of the additional attribute from the menu path Master data / System administration / Attributes. The following properties are available:

• Shipment edit: sdgedit.za=X_DUMMY,X_DUMMY2,...

• Shipment description row: sdbedit.za=X_DUMMY,X_DUMMY2,...

• Shipment selection: SdgAuswahlNew.za.za=X_DUMMY,X_DUMMY2,...

• Route selection: FarAuswahlNew.za=X_DUMMY,X_DUMMY2,...

Functions

Search | Excel output | XML export |  Reset