ER WMS 044-013: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
!Parameter Name !! Config Level !! Setting Value !! Result | !Parameter Name !! Config Level !! Setting Value !! Result | ||
|- | |- | ||
|ALAA | |ALAA (Allocation Advanced Auditing) | ||
| | |Owner | ||
|X (Extended) | |X (Extended) | ||
|Extended auditing –– extra audit records written | |Extended auditing –– extra audit records written | ||
|- | |- | ||
| | | | ||
| | | | ||
|Y | |Y | ||
|Standard auditing – no change | |Standard auditing – no change | ||
Revision as of 13:01, 13 December 2023
EMERGENCY RELEASE - WMS 810
RELNOTE ER044-013
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks |
|---|---|---|---|---|---|---|
| DP_WMS_ALLOC.sql | WMS allocation | 4.210 | 02787573 | - | 3 | We have not been able to replicate issue - when testing, allocation has been choosing the expected pallet.
So have added new ALAA (Allocation Advanced Auditing) value of 'X' (Extended). This works exactly the same way the existing 'Y' works, but writes in the PAT auditing logs the exact plsql queries run by allocation to select values. |
| New Parameters | |||
|---|---|---|---|
| Parameter Name | Config Level | Setting Value | Result |
| ALAA (Allocation Advanced Auditing) | Owner | X (Extended) | Extended auditing –– extra audit records written |
| Y | Standard auditing – no change | ||
| Any other value | No auditing - no change | ||
