Auto Accept Variance is a time-triggered transaction that is called to automatically accept variance obtained from the results of a count request. This transaction runs off Task Q. The Task Q uses CountRequestKey as Data key. Once CountRequestKey is obtained, the transaction resolves the variances for this count request.
Depending on the Variance Quantity, inventory is either increased or decreased in the system to match up with physical inventory. Audits are written for the inventory adjustments performed during auto acceptance of variance.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | AUTO_ACCEPT_VARIANCE |
Base Document Type | Count |
Base Process Type | Count Execution |
Abstract Transaction | No |
APIs Called | None |
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. |
ReasonCode | Optional. The reason code is mandatory for accepting variance and adjusting inventory. Reason codes are associated to unique accounting bin location. When inventory adjustment happens in a location, corresponding bin adjustments also happen. |
ReasonText | Optional. The Reason Text is provided to give purpose the inventory is adjustment. Some of the reasons are like Theft/Damage etc. The system does not perform any validations for the reason text. Whatever the user provides is updated. |
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 |
---|---|
NumCountRequestsForWhichVarianceAccepted | Statistics for number of count requests for which variance has been accepted. |
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 | count_dbd.txt | WMS_AUTO_ACCEPT_VARIANCE.ON_SUCCESS.xml | Yes |