This time-triggered transaction is used to create waves for a shipment group. This is similar to the Create Wave time-triggered transaction, except that this transaction is Task Q based and called for a specific Task Q Request.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Transaction Name | Create Wave For a Shipment Group |
Transaction ID | CREATE_WAVE_FOR_SHIPMENT_GROUP |
Base Process Type | Outbound Picking |
Base Document Type | Outbound Picking |
Abstract Transaction | No |
APIs Called | manageWave() |
User Exits Called | com.yantra.wms.japi.ue.WMSBeforeCreateWaveUE
|
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 Q 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. |
RedetermineShipmentGroup | Optional. Valid values are "Y" and "N". If left blank, this
value defaults to Y.
|
ForShipmentsModifiedBefore | Optional.
Enter the time (in hours) before which the shipments
that are in the "Sent To Node" status must be modified for shipment
group redetermination. You can also enter a fractional value. If left blank, this value defaults to 0 (zero) hours. |
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:
Parameter | Description |
---|---|
NumberOfWavesCreated | Number of waves created. |
NumberOfWavesDeleted | Number of waves deleted. Waves that are in created status can be deleted and recreated if there are more shipments for that shipment group. |
NumberOfShipmentLinesAssignedWaves | Number of shipment lines assigned waves. |
NumberOfShipmentLinesReassignedWaves | Number of shipment lines belonging to deleted waves. |
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.
This transaction raises events specified by the manageWave() API in the Sterling Selling and Fulfillment Foundation: Javadocs.