Categories Hand Held App Releases

Tasks and Stops on Release Requests

Master Terminal has the ability to apply stops and to do tasks to cargo items.
If the cargo item is configured to be able to split and merge, so that it can be stored in multiple locations; when a stop or task is applied to the cargo it is added to the cargo across the terminal in all locations. This functionality is unchanged.
An enhancement has been made to Master Terminal to allow stops and tasks to be applied to part of a cargo item in 1 location. This ability is configured as part of a job that is initiated with a release request.
It is now possible on a release request to specify which stops and tasks are to be applied to each release request detail line.
In hand held apps that are initiated by specifying a release request these new stops and tasks can be completed.
When used in this way the stops are call ‘stop actions’ and the tasks as called ‘task actions’.
EDI – Release Request Multi Line
In the EDI User Defined ‘Release Request Multi Line format the Request Detail  new option ‘Stops To Apply’ this is a space separated list of stop codes.

New line type ‘Tasks To Apply’.
The Tasks To Apply Line type has the todo task code and a remark to apply, plus the release request detail line Id that the task line is for.
One Tasks To Apply line for each todo task.
Each release request detail line has its own set of stops and tasks.

On each release request detail line you can  maintain the stops and tasks to be used in the job.
During operations the Maintain Actions Applied right click allows you to complete and remove stops and tasks. It also allows the desk user to add cargo items to the job:

Enter the release request ID and the break down shows how many stops and tasks there are:
Enter the other details and click NEXT.
Select/scan in normal way. On the Chosen sheet see the items and whether they have outstanding stops and tasks (AS = Action Stops, AT = Action Tasks), AS and AT are translatable.
NOTE: In the  release request screen the thumbnail has been updated with the staged items:
NOTE: On the cargo item transactions are created showing the stop or task action and how much it was for:
To complete stops and tasks click Actions button:
The save button saves the sheet that is on top i.e. stops or tasks.
Only outstanding stops or tasks are shown.
Select which stops to apply to which cargo items and for how much.
The stops and tasks have a filter, the tasks show the remarks:
Enter the Release Request details as normal, click NEXT.
Load the items by selecting or scanning. On the LOADED sheet any cargo items with stop and task actions outstanding are shown. Click the ACTIONS button to complete stop actions and task actions.

If outstanding stop actions or task actions a warning is shown:
Stop and task actions can be maintained by the desk at any time, using the Maintain Actions Applied…
Jade Report Writer
There are 4 new transaction classes that represent stop action add and complete plus task action add and complete. These all  have additional information on them to identify the booking/release request and their detail item and the amount of the action (quantity, volume/weight).
Under AllTransactions:
For ‘task adds’ use the CM_TaskAddDocAction class.
This also has all the normal todo task transaction information.
For ‘task completes’ use the CM_TaskCompleteDocAction class.
This also has all the normal todo task transaction information.
For ‘stop adds’ use the CM_StopAddDocAction class.
This also has all the normal stop transaction information.
For ‘stop completes’ use the CM_StopClearedDocAction class.
This also has all the normal stop transaction information.


The same transactions can be queried in the Item Selector in Cargo transaction mode.
Stop and Document Actions on Release Requests is available in Master Terminal

Leave a Reply

Your email address will not be published. Required fields are marked *