TEST: Difference between revisions

From Calidus HUB
No edit summary
No edit summary
Line 1: Line 1:
<!-- MEDIA LANDSCAPE YES -->  
<div class="noprint">
{{#vardefine:System|WMS}}
{{#vardefine:Client|JGB}}
{{ERHeader
{{#vardefine:ClientName|JB Global}}
|SystemVersion=WMS 810
{{#vardefine:System|''CALIDUS'' ePOD}}
|ERNumber=ER028-069
{{#vardefine:Doc_Title|JB Global POD Note Changes}}
}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|21st December 2018}}
{{#vardefine:Reference|354567}}
{{#vardefine:Year|2018}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=REQ {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}  


<!-- TOC -->
<div class="noprint">
=Requirements=


{{ERTableHeader}}
<!-- NEW PAGE -->
{{ERTableRow
{{Doc_Appendix
|DATA_WAREHOUSE_RULES_CONTROL_354196.sql
|Appendix=A
|Data Script
|Estimate=N
|4.1
|Glossary=EPOD
|354196
|Ref1=&nbsp;
|-
|RefV1=&nbsp;
|3
|RefDate1=&nbsp;
|Add new warehouse level rule value 'ENRP' (Enable next record in pack detail).
|REQ=0
 
|EST=0
If the rule is set to Yes and owner set to use single item packing, the screen will continue to automatically create a new detail record.
|FS=0
 
|TS=0
If rule is not set or set to any other value, the screen will revert to the old logic, and will not automatically create a new detail record.
|DEV=0
|
|ST=0
}}
|IMP=0
{{ERTableRow
|Client={{#var:Client}}
|DATA_WAREHOUSE_RULES_354196.sql
|Year={{#var:Year}}
|Data Script
|FSEST=N
|4.1
|Rev1=Barry Preece
|"
|Rev1Title=OBS Project Manager
|"
}}</div>
|"
[[Category:{{#var:Client}} REQ]]
|"
|"
}}
{{ERTableRow
|WHS1946.fmx
|Multi-Level Packing
|4.43
|"
|"
|"
|"
|"
}}
{{ERTableFooter}}
 
<table border="1px" width="100%">
<tr>
<td colspan="3" bgcolor="silver"><font size="2">'''Registry/Rules Settings'''</font></td>
</tr>
<tr>
<td bgcolor="silver"><font size="2">'''Path &amp; Name'''</font></td>
<td bgcolor="silver"><font size="2">'''Setting Value'''</font></td>
<td bgcolor="silver"><font size="2">'''Result'''</font></td>
</tr>
 
<tr>
<td>Warehouse level / 'ENRP'</td>
<td>Y</td>
<td>When user packs by single item packing and enters in a stock code, screen automatically creates new detail record</td>
</tr>
 
<tr>
<td>('Enable next record in pack detail')</td>
<td>Any other value or not set</td>
<td>When user packs by single item packing and enters in a stock code, screen does not automatically create a new detail record</td>
</tr>
 
</table>
 
 
<noinclude>
[[Category:{{#var:System}} ER]]
</noinclude>

Revision as of 18:10, 2 January 2019





Aptean Logo.png







JB Global

JB Global POD Note Changes


CALIDUS ePOD

21st December 2018 - 0.1
Reference: REQ 354567












































Requirements

Appendix A: Document References

A.1 References

Ref NoDocument Title & IDVersionDate
1   


A.2 Glossary

Term Definition
EPOD Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD.
CALIDUS eSERV The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system.
PDA The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android.
DAL Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it.
GPS Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device.
GPRS, 3G, HSDPA, Data Service All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet.


A.3 Authorised By


Barry Preece

OBS Project Manager
_____________________________