Create Count Task Time-Triggered Transaction

Create Count Task is a time-triggered transaction that is called to create tasks for a given count request. Tasks are created based on the count request criteria. A summary task is created for the count request criteria, and tasks are created with summary task as parent task. The transaction runs off Task Q.

The count request attributes are used to determine the task type from the Count Strategy, by using the best match algorithm.

A count task is created at a location level for the count request criteria. Additional attributes including specific item or pallet or case LPN may also be specified.

Attributes

The following are the attributes for this time-triggered transaction:

Table 1. Create Count Task Attributes
Attribute Value
Transaction Name Create Count Tasks
Transaction ID CREATE_COUNT_TASKS
Base Document Type Count
Base Process Type Count Execution
Abstract Transaction No
APIs Called createCountRequest()
User Exits Called None

Criteria Parameters

The following are the criteria parameters for this transaction:

Table 2. Create Count Task Criteria Parameters
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.
TaskGranularity Required. Granularity for which the Create Count Task needs to be run.

The valid values are REQUEST or VARIANCE. Typically, this is set to REQUEST for first count, and VARIANCE for the successive counts.

TaskGenerationLevel Required. Generation Level for which the Create Count Task needs to be run.

The valid values are ALL_LOCATIONS and LOCATIONS_WITH_VARIANCE. Typically, this is set to ALL_LOCATIONS for first count, and LOCATIONS_WITH_VARIANCE for successive counts.

Node Required. The warehouse management ship node for which records are being processed.
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.
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 > 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.
Note: There are no separate Time-triggered Transactions for Create Third Count Task and Create Variance Task.
Note: The Third Count Task and Variance Task is based on Create Count Task Time-Triggered Transaction.
Note: Typically for a Third Count Task or Variance Task, the TaskGranularity is set to VARIANCE, while the TaskGenerationLevel is set to LOCATIONS_WITH_VARIANCE.

Statistics Tracked

The following statistics are tracked for this transaction:

Table 3. Create Count Task Statistics
Statistic Name Description
NumCountTasksCreated Number of count tasks created.

Pending Job Count

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.

Events Raised

The following events are raised by this time-triggered transaction:

Table 4. Events Raised by the Create Count Task Transaction
Transaction/Event Key Data Data Published Template Support?
NO_REQUESTS_CREATED count_dbd.txt WMS_CREATE_COUNT_TASK.NO_REQUEST_CREATED.xml Yes
ON_SUCCESS count_dbd.txt WMS_CREATE_COUNT_TASK.ON_SUCCESS.xml Yes