Note - Displaying signatures

Purpose

In the status entry process for shipments, signatures can be stored, for example through LBASE Scan OnTour, and displayed in the status history.

Amendments

In the master data, the default display mode for the status history (mask 1902, display mode ID 586) must be expanded to include the column pod_unterschrift (from the table spod_pod). Without this expansion, the signature cannot be displayed. The property can also be used to define the display mode in LBASE Online as follows:

  • sdg_statushistory.azaid=586

  • sdg_statushistory.ordid=522

Example: expanded display mode

SELECT sdg_sdgid, lau_kbez, pod_code, poc_bez, to_char(pod_datum,'DD.MM.RR HH24 MI') pod_datum_ch, pod_name, pod_bemerkung, pod_unterschrift

FROM pod_pod,ssdg_sendung,spoc_podcode,slaf_leistanf,slau_untertyp

WHERE sdg_sdgid=pod_sdgid and pod_code=poc_pocid and sdg_sdgid=laf_sdgid and laf_lafid=pod_lafid and laf_latid=lau_latid and laf_lauid=lau_lauid and laf_latid='ST' and laf_lauid in ('ZU','AB') and poc_lauid=lau_lauid

Activation

To activate the signature display, the property sdg_statushistory.unterschrift=1 must be set. You can then view this in the status table or in LBASE.

Note: dangerous goods and customs goods handling attributes can also be integrated into the signature display.