This Task Q based time-triggered transaction is used to assign lanes. This time-triggered transaction should be used in scenarios where we need to balance the load on the lanes by distributing the shipments across the various lanes that are available for use.
The Assign Lane time-triggered transaction works off a Wave, and assigns lanes to all shipments in the Wave that have not yet been assigned a lane. Depending on the configuration, it assigns lanes based on SortByShipment and SortByCarrier.
If any dedicated lanes have been configured, then this time-triggered transaction assigns the dedicated lanes to the shipments that satisfy the criteria configured for the dedicated locations. After assigning the dedicated lanes, if there are still shipments which do not have any lanes assigned, then these shipments are assigned to any non-dedicated locations in a round-robin fashion.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Transaction Name | Assign Lanes |
Transaction ID | ASSIGN_LANE.4001 |
Base Process Type | Outbound Picking |
Base Document Type | Outbound Picking |
Abstract Transaction | No |
APIs Called | None |
User Exits Called | com.yantra.wms.japi.ue.WMSOverrideAssignLaneUE |
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 |
---|---|
NumShipments | Number of shipments for which lanes have been assigned. |
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_ASSIGN_LANE.ON_SUCCESS.xml | Yes |
HAS_EXCEPTIONS | WMS_ASSIGN_LANE.HAS_EXCEPTIONS.xml | Yes |