Request Batch Completion is a time-triggered transaction that completes a batch after completing its tasks.
The yfs.confirmbatch.online property in the yfs.properties_wms_ext.in file is used to set this time-triggered transaction to work in online or offline mode.
The mode of operation (online or offline) is
decided
on the basis of a property defined in the yfs.properties_wms_ext.in file:
yfs.confirmbatch.online
= Y/N
The default out-of-the-box shipped property causes the Request Batch Completion transaction to run in online mode.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Transaction Name | Request Batch Completion |
Transaction ID | REQ_BATCH_COMPLETION |
Base Document Type | General |
Base Process Type | Task Execution |
Abstract Transaction | No |
APIs Called | registerBatchCompletion()
|
User Exits Called | None |
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. |
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 |
---|---|
NumberOfBatchesCompleted | Number of batches completed. |
NumberOfTasksCompleted | Number of tasks completed. |
For this transaction the pending job count is the number of batches and their tasks that can be completed.
The following events are raised by this time-triggered transaction:
Transaction/Event | Key Data | Data Published | Template Support? |
---|---|---|---|
BATCH_COMPLETION_REQUESTED | batch_dbd.txt | YCP_REQ_BATCH_COMPLETION.BATCH_COMPLETION_REQUESTED.xml | Yes |