Execute Count Program Time-Triggered Transaction

Execute Count Program is a time-triggered transaction that is called to create count requests.

Note: If you run the Execute Count Program time-triggered transaction more than once in a day, the system does not create additional count requests. You can create additional count requests using the Invoke Count Service screen in the Application Consoles. For more information about invoking count service, see the Sterling Selling and Fulfillment Foundation: Warehouse Management System User Guide.

Count Request Generation

You can create count requests at item level, location level and item-classification level.

Cycle count for classifications and performing count at item level

This time-triggered transaction uses the following logic (for each count program condition) to determine the number of count requests that need to be generated for items:

Cycle count for classifications and performing count at classification level

When a count program specifies that the count should be performed at the classification level, the count request and count tasks are generated for the classifications per se, and not for the items. Thus, the count requests are usually not generated daily, but after an interval of days.

While generating count requests, the time-triggered transaction uses the following logic (for each count program condition) to determine if the count request for the classification should be generated on that day:

Cycle count for classifications and performing count at location level

This time-triggered transaction uses the following logic (for each count program condition) to determine the number of count requests to be generated for locations:

Attributes

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

Table 1. Execute Count-Program Attributes
Attribute Value
Transaction Name Execute Count Program
Transaction ID EXECUTE_COUNT_PROGRAM
Base Document Type Count
Base Process Type Count Execution
Abstract Transaction No
APIs Called None
User Exits Called None

Criteria Parameters

The following are the criteria parameters for this transaction:

Table 2. Execute Count Program 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.
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.

Node Optional. Node for which the Execute Count Program needs to be run. If not passed, all nodes are monitored.
Enterprise Code Optional. Enterprise for which the Execute Count Program needs to be run. If not passed, all enterprises are monitored.
CountProgramName Optional. Count Program Name for which the Execute Count Program needs to be run. If not passed, all count programs are monitored.
ColonyID Required in a multischema deployment where a table may exist in multiple schemas. Runs the agent for the colony.

Statistics Tracked

The following statistics are tracked for this transaction:

Table 3. Execute Count-Program Statistics
Statistic Name Description
NumCountProgramsExecuted Number of count programs executed.
NumCountRequestsCreated Number of count requests created for the count program.

Pending Job Count

For this transaction the pending job count is the number of count programs for the node, whose EFFECTIVE_FROM_DATE value less than or equal to (<=) and EFFECTIVE_TO_DATE value greater than or equal to (>=) the current date value.

Events Raised

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

Table 4. Events Raised by the Execute Count-Program Transaction
Transaction/Event Key Data Data Published Template Support?
NO_REQUESTS_CREATED count_dbd.txt WMS_EXECUTE_COUNT_PROGRAM.NO_REQUEST_CREATED.xml Yes
ON_SUCCESS count_dbd.txt WMS_EXECUTE_COUNT_PROGRAM.ON_SUCCESS.xml Yes