This is a Task Q based time-triggered transaction, which works off a wave. It creates pick tasks for the shipment lines included in the wave.
This time-triggered transaction should be used to release a wave.
In the yfs.properties_wms_ext.in file, use the yfs.releaseWave.pickalgorithm property to select the algorithm to use to determine pick locations for the release wave transaction. For more information about the algorithms supported by the Sterling Warehouse Management System, see Section 7.2.1.4, "Algorithms Used to Determine Pick Locations".
In the yfs.properties_wms_ext.in file, the value of the yfs.releaseWave.pickalgorithm property provided out-of-the-box is set to blank.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Transaction Name | Release Wave |
Transaction ID | RELEASE_WAVE.4001 |
Base Process Type | Outbound Picking |
Base Document Type | Outbound Picking |
Abstract Transaction | No |
APIs Called | releaseWave() |
User Exits Called | com.yantra.wms.japi.ue.WMSOverridePickLocationAssignmentUE |
The following are the criteria parameters for this transaction:
Parameter | Description |
---|---|
Action | Required. Triggers the transaction. If left blank, it defaults to Get, the only valid value. |
Number of Records To Buffer | Optional. Number of records to retrieve and process at one time. If left blank or specified as 0 (zero), it defaults to 5000. |
Next Task Queue Interval | Optional. Specifies in hours how long a failed task should be suspended before it is considered for reprocessing. Defaults to 5 hours. |
Node | Required. The warehouse management ship node for which records are being processed. |
AgentCriteriaGroup | Optional. Used to classify nodes. This value can be accepted
by WMS time-triggered transactions that only perform their tasks on
the nodes with a matching node transactional velocity value. Valid values are: LOW, HIGH, and any additional values defined by the Hub from Sterling Application Platform > System Administration > Agent Criteria Groups. |
ColonyID | Required in a multischema deployment where a table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumberOfShipmentsInException | Number of Shipments for which tasks could not be created for the Entire Quantity. |
NumberOfTasksCreated | Number of tasks created. |
For this transaction the pending job count is the number of records available to be processed by the transaction with the AVAILABLE_DATE value less than or equal to (<=) the current date value in the YFS_Task_Q table.
The following events are raised by this time-triggered transaction:
Transaction/Event | Key Data | Data Published | Template Support? |
---|---|---|---|
ON_SUCCESS | wave_dbd.txt | WMS_RELEASE_WAVE.ON_SUCCESS.xml | Yes |