Purpose

 Configuration
 

The LI execution during POD entry can be activated via the property statis.li.
 

The following should, however, be noted:
 

1. First, all shipments are saved (POD codes).
    

2. Next, the LI with the library status processing (STATUS) is accessed for each shipment.
    

3. An erroneous logic interpreter (LI) return does NOT cause a cancellation; the LI is still accessed for the remaining shipments.
    

4. Finally, a list of the shipments for which the LI has been accessed is displayed indicating whether or not the access was successful.

Note: previously, the status PR was created via a package before LI execution. In the default workflow, however, the status PRs are only created during the workflow as this defines the downstream procedure for this status. When executing the LI, this means that no further PRs are created and the data is transmitted to the LI. During this process, the call for row 0 is added. To nevertheless create an old workflow  the value 2 is used for the LI execution of the package. 

Further properties

The following properties are available for status entry purposes:

• statis.allowed=1: enables the status entry

• sdgauswahl.stati.lauids= AB,ZU,XSD: status codes for selection purposes

• For selection purposes: the codes of all the selected status codes can be sought in the Code field.

• For search purposes: the LBASE Package spod.get_max_pod_code([SDGID],‘List of codes’) is used here

• sdganzeige.statushistory=1: should the status history be displayed in the shipment details?

• sdg_statushistory.azaid=9202: display mode for the status history (valid display mode ID (with AZA_FRMID 1902=pseudo mask for internet status history)

• sdg_statushistory.ordid=???: sorting for status history (with which ORD_FRMID 1902=pseudo mask for internet status history)

• sdg_statushistory.unterschrift=1: display signature in the status history (icon in first column and the display mode must contain the column pod_unterschrift).

• sdg_statushistory.searchdays=12: number of days that are considered in the status history.

• statis.li=1: LI execution after saving

• zustellung.reine_quittung=10: (i.e. group 10) determination of which groups of POCIDs (POD_POGID) should apply.

• zustellung.abweichung=90,40:  (i.e. groups 90,40) determination of which POCIDs should mirror themselves.

• status.lauid =XSD: defines the status code for the entry

Note: if you use the property status.lauid to enter status codes other than  ZU please note that you must also integrate these into the workflow - for example by creating a separate display mode.

Note on separate display modes

In the Shipment - selection mask, the configuration sdgauswahl.stati.lauids is used and the following is also stored in the WHERE:

AND Spod.get_max_pod_code(sdg_sdgid,'AB,ZU')= '012'

AND '40' IN ( SELECT DISTINCT pog_pogid FROM spog_pocgrp, SPOC_T_PODCODE WHERE poc_pocid = Spod.get_max_pod_code(sdg_sdgid,'AB,ZU') AND poc_pogid = pog_pogid ) …

By using the restriction in the SQL statement spod.get_max_pod_code(sdg_sdgid,'ZU'), only the type ZU is considered in the table through the default display mode 467. Irrespective of the selection criteria, only the maximum POD code of the delivery is displayed in the final row, for example.

You should therefore consider every code that is stored in a separate display mode in the property status.lauid.

Example: …,spod.get_max_pod_code(sdg_sdgid,'ZU,AB,XSD')

You can display the maximum POD code for the own type as follows:

Example: …case when spod.get_max_pod(sdg_sdgid,'XSD') is not null

then 'XSD- '|| (select pod_code from SPOD_POD

where pod_sdgid = sdg_sdgid

and pod_lafid = spod.get_max_pod(sdg_sdgid,'XSD'))

else '' end pod_code_last…

Configuration