WMS - User contributions [en-gb]

File:DynEmail9.PNG

2010-11-16T15:31:23Z

Duttont:

Dynamic Email Setup

2010-11-16T15:27:27Z

Duttont:

=Dynamic Email Notifications=

This functionality allows email to be sent to various parties, allowing for notifications under the following conditions:

•Despatch Confirmation: this will email the customer.

•Short Receipt: this will email the supplier or owner.

•Short Allocation: this will email the owner.

== Setup: ==

=== System Setup: ===

The system is required to be configured to forward emails via a email server. This server must accept SMTP connections. A parameter needs to be added to the registry of the system containing the IP address of the email server. This parameter is added under the description of ‘EmailServer’ and data is set to the IP address of the server.

[[image:DynEmail1.PNG]]

[[image:DynEmail2.PNG]]

== Email Setup: ==

To use this functionality the following three groups will need email address’s setup; Customers, Suppliers, and Owners.

==== Customers Email: ====

Customers requiring emails must be setup in the ‘Customer Wizard’ menu. Once the required customer is found change the ‘Email Required’ field to ‘Yes’.

[[image:DynEmail3.PNG]]

Also the owner of the product must be set to run the despatch email: OBS_DESP, within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image:DynEmail4.PNG]]

Now any customer who has an email address associated with an order will be emailed upon dispatch, providing the setup is complete. Please note that the orders FTA must have the email address populated otherwise this function will not be able to send the despatch confirmation.

==== Suppliers Email: ====

This can be added to a supplier within the ‘Supplier Wizard’ screen, under the ‘Buyer Address’ tab.

[[image:DynEmail5.PNG]]

In addition the owner must have the short allocation procude set up and a be setup to run the SHORT_RECPT procedure within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image:DynEmail6.PNG]]

==== Owners Email: ====

This can be added to an owner as a default email within the ‘Owner Maintenance’ menu.

[[image:DynEmail7.PNG]]

=== Dynamic Email Setup: ===

Emails can be setup within the ‘Email Maintenance’ menu. This screen allows users to Add New email templates. Templates are dependent on the template description. The following template descriptions can be used:

•SHORT_RECPT – For short receipt emails

•OBS_DESP – For Despatch Confirmations

•OBS-SHALL – For Short Allocation emails

[[image:DynEmail8.PNG]]

‘Email title’ field must be added, this will complete the subject of the email. The ‘Email From Address’ field will be the email that the message is send from.
The ‘Message Type’ field controls in which scenarios the email will be sent. The available scenarios are as follows:

•Despatch

•Short Receipt

•Short Allocation

The ‘Test Email To Address’ field and ‘Test’ button can be used to forward emails to a specified address for testing purposes.
The ‘Email Body’ field allows users to specific a email, either as plain text or as HTML. Tags can be entered into this field allowing for dynamic data to be inserted into the email.
The following tags can be entered for short receipts:

•[SUPPLIER_NAME]

•[OWNER_NAME]

•[WAREHOUSE_NAME]

•[GRN_NO]

•[ADVICE_NOTE_NO]

•[CONTAINER_NO]

•[RECEIPT_DATE]

The following tags can be entered for short allocation:

•[ORDER_NUM]

•[ORDER_REF]

•[CUST_PO_ REF]

•[CUST_CODE]

•[CUST_NAME]

•[DATE]

The following tags can be entered for despatch confirmation:

•[NAME]

•[ORD_NUM]

•[ORD_DESC]

•[DESPDATE]

•[TRACK_START]

•[TRACKINGREF]

•[TRACK_END]

•[DEL NAME]

•[DEL ADDR1]

•[DEL ADDR2]

•[DEL ADDR3]

•[DEL POST]

•<nowiki></nowiki> (These tags can be used to produce a table of all items and quantities of the order, the following HTML code is recommended for use:

<nowiki><table width="90%" border="0">
<col align="left" />
<col align="left" />
<col align="right" />
<tr>
<th>Item Code</th>
<th>Description</th>
<th>Qty</th>
</tr>


</table></nowiki>

Once setup emails will be automatically triggered dependant on the defined ‘Email Type’.

== Usage: ==

As mentioned previously once setup emails will be automatically sent based on the following conditions:
•An order is dispatched to a customer who has the ‘email required’ field set to ‘Yes’ and has a email associated with the order.

•An order is short received for a supplier/owner who has a email setup.

•An order is short allocated for a owner who has a email setup.

=== Resending ===

The 'Email Maintenance' menu also has a tab for resending emails. To use this select the report you wish to resend, then select the 'Email Re-Send' tab.

This will then present the user with a set of ranges to enter, for example a range of order numbers. Once the user clicks resend this will send the emails that are associated with the range of values again.

[[image:DynEmail9.PNG]]

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>v0.1</center>
| <center>16/11/10</center>
| <center>User Guide</center>
| User Guide
| <center>LSM</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Dynamic Email Setup

2010-11-16T10:05:45Z

Duttont:

=Dynamic Email Notifications=

This functionality allows email to be sent to various parties, allowing for notifications under the following conditions:

•Despatch Confirmation: this will email the customer.

•Short Receipt: this will email the supplier or owner.

•Short Allocation: this will email the owner.

== Setup: ==

=== System Setup: ===

The system is required to be configured to forward emails via a email server. This server must accept SMTP connections. A parameter needs to be added to the registry of the system containing the IP address of the email server. This parameter is added under the description of ‘EmailServer’ and data is set to the IP address of the server.

[[image:DynEmail1.PNG]]

[[image:DynEmail2.PNG]]

== Email Setup: ==

To use this functionality the following three groups will need email address’s setup; Customers, Suppliers, and Owners.

==== Customers Email: ====

Customers requiring emails must be setup in the ‘Customer Wizard’ menu. Once the required customer is found change the ‘Email Required’ field to ‘Yes’.

[[image:DynEmail3.PNG]]

Also the owner of the product must be set to run the despatch email: OBS_DESP, within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image:DynEmail4.PNG]]

Now any customer who has an email address associated with an order will be emailed upon dispatch, providing the setup is complete. Please note that the orders FTA must have the email address populated otherwise this function will not be able to send the despatch confirmation.

==== Suppliers Email: ====

This can be added to a supplier within the ‘Supplier Wizard’ screen, under the ‘Buyer Address’ tab.

[[image:DynEmail5.PNG]]

In addition the owner must have the short allocation procude set up and a be setup to run the SHORT_RECPT procedure within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image:DynEmail6.PNG]]

==== Owners Email: ====

This can be added to an owner as a default email within the ‘Owner Maintenance’ menu.

[[image:DynEmail7.PNG]]

=== Dynamic Email Setup: ===

Emails can be setup within the ‘Email Maintenance’ menu. This screen allows users to Add New email templates. Templates are dependent on the template description. The following template descriptions can be used:

•SHORT_RECPT – For short receipt emails

•OBS_DESP – For Despatch Confirmations

•OBS-SHALL – For Short Allocation emails

[[image:DynEmail8.PNG]]

‘Email title’ field must be added, this will complete the subject of the email. The ‘Email From Address’ field will be the email that the message is send from.
The ‘Message Type’ field controls in which scenarios the email will be sent. The available scenarios are as follows:

•Despatch

•Short Receipt

•Short Allocation

The ‘Test Email To Address’ field and ‘Test’ button can be used to forward emails to a specified address for testing purposes.
The ‘Email Body’ field allows users to specific a email, either as plain text or as HTML. Tags can be entered into this field allowing for dynamic data to be inserted into the email.
The following tags can be entered for short receipts:

•[SUPPLIER_NAME]

•[OWNER_NAME]

•[WAREHOUSE_NAME]

•[GRN_NO]

•[ADVICE_NOTE_NO]

•[CONTAINER_NO]

•[RECEIPT_DATE]

The following tags can be entered for short allocation:

•[ORDER_NUM]

•[ORDER_REF]

•[CUST_PO_ REF]

•[CUST_CODE]

•[CUST_NAME]

•[DATE]

The following tags can be entered for despatch confirmation:

•[NAME]

•[ORD_NUM]

•[ORD_DESC]

•[DESPDATE]

•[TRACK_START]

•[TRACKINGREF]

•[TRACK_END]

•[DEL NAME]

•[DEL ADDR1]

•[DEL ADDR2]

•[DEL ADDR3]

•[DEL POST]

•<nowiki></nowiki> (These tags can be used to produce a table of all items and quantities of the order, the following HTML code is recommended for use:

<nowiki><table width="90%" border="0">
<col align="left" />
<col align="left" />
<col align="right" />
<tr>
<th>Item Code</th>
<th>Description</th>
<th>Qty</th>
</tr>


</table></nowiki>

Once setup emails will be automatically triggered dependant on the defined ‘Email Type’.

== Usage: ==

As mentioned previously once setup emails will be automatically sent based on the following conditions:
•An order is dispatched to a customer who has the ‘email required’ field set to ‘Yes’ and has a email associated with the order.

•An order is short received for a supplier/owner who has a email setup.

•An order is short allocated for a owner who has a email setup.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>v0.1</center>
| <center>16/11/10</center>
| <center>User Guide</center>
| User Guide
| <center>LSM</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Dynamic Email Setup

2010-11-16T10:04:32Z

Duttont:

=Dynamic Email Notifications=

This functionality allows email to be sent to various parties, allowing for notifications under the following conditions:

•Despatch Confirmation: this will email the customer.

•Short Receipt: this will email the supplier or owner.

•Short Allocation: this will email the owner.

== Setup: ==

=== System Setup: ===

The system is required to be configured to forward emails via a email server. This server must accept SMTP connections. A parameter needs to be added to the registry of the system containing the IP address of the email server. This parameter is added under the description of ‘EmailServer’ and data is set to the IP address of the server.

[[image|DynEmail1.PNG]]

[[image|DynEmail2.PNG]]

== Email Setup: ==

To use this functionality the following three groups will need email address’s setup; Customers, Suppliers, and Owners.

==== Customers Email: ====

Customers requiring emails must be setup in the ‘Customer Wizard’ menu. Once the required customer is found change the ‘Email Required’ field to ‘Yes’.

[[image|DynEmail3.PNG]]

Also the owner of the product must be set to run the despatch email: OBS_DESP, within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|DynEmail4.PNG]]

Now any customer who has an email address associated with an order will be emailed upon dispatch, providing the setup is complete. Please note that the orders FTA must have the email address populated otherwise this function will not be able to send the despatch confirmation.

==== Suppliers Email: ====

This can be added to a supplier within the ‘Supplier Wizard’ screen, under the ‘Buyer Address’ tab.

[[image|DynEmail5.PNG]]

In addition the owner must have the short allocation procude set up and a be setup to run the SHORT_RECPT procedure within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|DynEmail6.PNG]]

==== Owners Email: ====

This can be added to an owner as a default email within the ‘Owner Maintenance’ menu.

[[image|DynEmail7.PNG]]

=== Dynamic Email Setup: ===

Emails can be setup within the ‘Email Maintenance’ menu. This screen allows users to Add New email templates. Templates are dependent on the template description. The following template descriptions can be used:

•SHORT_RECPT – For short receipt emails

•OBS_DESP – For Despatch Confirmations

•OBS-SHALL – For Short Allocation emails

[[image|DynEmail8.PNG]]

‘Email title’ field must be added, this will complete the subject of the email. The ‘Email From Address’ field will be the email that the message is send from.
The ‘Message Type’ field controls in which scenarios the email will be sent. The available scenarios are as follows:

•Despatch

•Short Receipt

•Short Allocation

The ‘Test Email To Address’ field and ‘Test’ button can be used to forward emails to a specified address for testing purposes.
The ‘Email Body’ field allows users to specific a email, either as plain text or as HTML. Tags can be entered into this field allowing for dynamic data to be inserted into the email.
The following tags can be entered for short receipts:

•[SUPPLIER_NAME]

•[OWNER_NAME]

•[WAREHOUSE_NAME]

•[GRN_NO]

•[ADVICE_NOTE_NO]

•[CONTAINER_NO]

•[RECEIPT_DATE]

The following tags can be entered for short allocation:

•[ORDER_NUM]

•[ORDER_REF]

•[CUST_PO_ REF]

•[CUST_CODE]

•[CUST_NAME]

•[DATE]

The following tags can be entered for despatch confirmation:

•[NAME]

•[ORD_NUM]

•[ORD_DESC]

•[DESPDATE]

•[TRACK_START]

•[TRACKINGREF]

•[TRACK_END]

•[DEL NAME]

•[DEL ADDR1]

•[DEL ADDR2]

•[DEL ADDR3]

•[DEL POST]

•<nowiki></nowiki> (These tags can be used to produce a table of all items and quantities of the order, the following HTML code is recommended for use:

<nowiki><table width="90%" border="0">
<col align="left" />
<col align="left" />
<col align="right" />
<tr>
<th>Item Code</th>
<th>Description</th>
<th>Qty</th>
</tr>


</table></nowiki>

Once setup emails will be automatically triggered dependant on the defined ‘Email Type’.

== Usage: ==

As mentioned previously once setup emails will be automatically sent based on the following conditions:
•An order is dispatched to a customer who has the ‘email required’ field set to ‘Yes’ and has a email associated with the order.

•An order is short received for a supplier/owner who has a email setup.

•An order is short allocated for a owner who has a email setup.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>v0.1</center>
| <center>16/11/10</center>
| <center>User Guide</center>
| User Guide
| <center>LSM</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

File:DynEmail8.PNG

2010-11-16T10:03:22Z

Duttont:

File:DynEmail7.PNG

2010-11-16T10:03:14Z

Duttont:

File:DynEmail6.PNG

2010-11-16T10:03:06Z

Duttont:

File:DynEmail5.PNG

2010-11-16T10:03:00Z

Duttont:

File:DynEmail4.PNG

2010-11-16T10:02:54Z

Duttont:

File:DynEmail3.PNG

2010-11-16T10:02:47Z

Duttont:

File:DynEmail2.PNG

2010-11-16T10:02:41Z

Duttont:

File:DynEmail1.PNG

2010-11-16T10:02:34Z

Duttont:

Dynamic Email Setup

2010-11-16T09:58:44Z

Duttont:

=Dynamic Email Notifications=

This functionality allows email to be sent to various parties, allowing for notifications under the following conditions:

•Despatch Confirmation: this will email the customer.

•Short Receipt: this will email the supplier or owner.

•Short Allocation: this will email the owner.

== Setup: ==

=== System Setup: ===

The system is required to be configured to forward emails via a email server. This server must accept SMTP connections. A parameter needs to be added to the registry of the system containing the IP address of the email server. This parameter is added under the description of ‘EmailServer’ and data is set to the IP address of the server.

[[image|dynEmail1.PNG]]

[[image|dynEmail2.PNG]]

== Email Setup: ==

To use this functionality the following three groups will need email address’s setup; Customers, Suppliers, and Owners.

==== Customers Email: ====

Customers requiring emails must be setup in the ‘Customer Wizard’ menu. Once the required customer is found change the ‘Email Required’ field to ‘Yes’.

[[image|dynEmail3.PNG]]

Also the owner of the product must be set to run the despatch email: OBS_DESP, within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail4.PNG]]

Now any customer who has an email address associated with an order will be emailed upon dispatch, providing the setup is complete. Please note that the orders FTA must have the email address populated otherwise this function will not be able to send the despatch confirmation.

==== Suppliers Email: ====

This can be added to a supplier within the ‘Supplier Wizard’ screen, under the ‘Buyer Address’ tab.

[[image|dynEmail5.PNG]]

In addition the owner must have the short allocation procude set up and a be setup to run the SHORT_RECPT procedure within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail6.PNG]]

==== Owners Email: ====

This can be added to an owner as a default email within the ‘Owner Maintenance’ menu.

[[image|dynEmail7.PNG]]

=== Dynamic Email Setup: ===

Emails can be setup within the ‘Email Maintenance’ menu. This screen allows users to Add New email templates. Templates are dependent on the template description. The following template descriptions can be used:

•SHORT_RECPT – For short receipt emails

•OBS_DESP – For Despatch Confirmations

•OBS-SHALL – For Short Allocation emails

[[image|dynEmail8.PNG]]

‘Email title’ field must be added, this will complete the subject of the email. The ‘Email From Address’ field will be the email that the message is send from.
The ‘Message Type’ field controls in which scenarios the email will be sent. The available scenarios are as follows:

•Despatch

•Short Receipt

•Short Allocation

The ‘Test Email To Address’ field and ‘Test’ button can be used to forward emails to a specified address for testing purposes.
The ‘Email Body’ field allows users to specific a email, either as plain text or as HTML. Tags can be entered into this field allowing for dynamic data to be inserted into the email.
The following tags can be entered for short receipts:

•[SUPPLIER_NAME]

•[OWNER_NAME]

•[WAREHOUSE_NAME]

•[GRN_NO]

•[ADVICE_NOTE_NO]

•[CONTAINER_NO]

•[RECEIPT_DATE]

The following tags can be entered for short allocation:

•[ORDER_NUM]

•[ORDER_REF]

•[CUST_PO_ REF]

•[CUST_CODE]

•[CUST_NAME]

•[DATE]

The following tags can be entered for despatch confirmation:

•[NAME]

•[ORD_NUM]

•[ORD_DESC]

•[DESPDATE]

•[TRACK_START]

•[TRACKINGREF]

•[TRACK_END]

•[DEL NAME]

•[DEL ADDR1]

•[DEL ADDR2]

•[DEL ADDR3]

•[DEL POST]

•<nowiki></nowiki> (These tags can be used to produce a table of all items and quantities of the order, the following HTML code is recommended for use:

<nowiki><table width="90%" border="0">
<col align="left" />
<col align="left" />
<col align="right" />
<tr>
<th>Item Code</th>
<th>Description</th>
<th>Qty</th>
</tr>


</table></nowiki>

Once setup emails will be automatically triggered dependant on the defined ‘Email Type’.

== Usage: ==

As mentioned previously once setup emails will be automatically sent based on the following conditions:
•An order is dispatched to a customer who has the ‘email required’ field set to ‘Yes’ and has a email associated with the order.

•An order is short received for a supplier/owner who has a email setup.

•An order is short allocated for a owner who has a email setup.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>v0.1</center>
| <center>16/11/10</center>
| <center>User Guide</center>
| User Guide
| <center>LSM</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Dynamic Email Setup

2010-11-16T09:58:14Z

Duttont:

=Dynamic Email Notifications=

This functionality allows email to be sent to various parties, allowing for notifications under the following conditions:

•Despatch Confirmation: this will email the customer.

•Short Receipt: this will email the supplier or owner.

•Short Allocation: this will email the owner.

== Setup: ==

=== System Setup: ===

The system is required to be configured to forward emails via a email server. This server must accept SMTP connections. A parameter needs to be added to the registry of the system containing the IP address of the email server. This parameter is added under the description of ‘EmailServer’ and data is set to the IP address of the server.

[[image|dynEmail1.PNG]]

[[image|dynEmail2.PNG]]

== Email Setup: ==

To use this functionality the following three groups will need email address’s setup; Customers, Suppliers, and Owners.

==== Customers Email: ====

Customers requiring emails must be setup in the ‘Customer Wizard’ menu. Once the required customer is found change the ‘Email Required’ field to ‘Yes’.

[[image|dynEmail3.PNG]]

Also the owner of the product must be set to run the despatch email: OBS_DESP, within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail4.PNG]]

Now any customer who has an email address associated with an order will be emailed upon dispatch, providing the setup is complete. Please note that the orders FTA must have the email address populated otherwise this function will not be able to send the despatch confirmation.

==== Suppliers Email: ====

This can be added to a supplier within the ‘Supplier Wizard’ screen, under the ‘Buyer Address’ tab.

[[image|dynEmail5.PNG]]

In addition the owner must have the short allocation procude set up and a be setup to run the SHORT_RECPT procedure within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail6.PNG]]

==== Owners Email: ====

This can be added to an owner as a default email within the ‘Owner Maintenance’ menu.

[[image|dynEmail7.PNG]]

=== Dynamic Email Setup: ===

Emails can be setup within the ‘Email Maintenance’ menu. This screen allows users to Add New email templates. Templates are dependent on the template description. The following template descriptions can be used:
•SHORT_RECPT – For short receipt emails
•OBS_DESP – For Despatch Confirmations
•OBS-SHALL – For Short Allocation emails

[[image|dynEmail8.PNG]]

‘Email title’ field must be added, this will complete the subject of the email. The ‘Email From Address’ field will be the email that the message is send from.
The ‘Message Type’ field controls in which scenarios the email will be sent. The available scenarios are as follows:
•Despatch
•Short Receipt
•Short Allocation
The ‘Test Email To Address’ field and ‘Test’ button can be used to forward emails to a specified address for testing purposes.
The ‘Email Body’ field allows users to specific a email, either as plain text or as HTML. Tags can be entered into this field allowing for dynamic data to be inserted into the email.
The following tags can be entered for short receipts:

•[SUPPLIER_NAME]

•[OWNER_NAME]

•[WAREHOUSE_NAME]

•[GRN_NO]

•[ADVICE_NOTE_NO]

•[CONTAINER_NO]

•[RECEIPT_DATE]

The following tags can be entered for short allocation:

•[ORDER_NUM]

•[ORDER_REF]

•[CUST_PO_ REF]

•[CUST_CODE]

•[CUST_NAME]

•[DATE]

The following tags can be entered for despatch confirmation:

•[NAME]

•[ORD_NUM]

•[ORD_DESC]

•[DESPDATE]

•[TRACK_START]

•[TRACKINGREF]

•[TRACK_END]

•[DEL NAME]

•[DEL ADDR1]

•[DEL ADDR2]

•[DEL ADDR3]

•[DEL POST]

•<nowiki></nowiki> (These tags can be used to produce a table of all items and quantities of the order, the following HTML code is recommended for use:

<nowiki><table width="90%" border="0">
<col align="left" />
<col align="left" />
<col align="right" />
<tr>
<th>Item Code</th>
<th>Description</th>
<th>Qty</th>
</tr>


</table></nowiki>

Once setup emails will be automatically triggered dependant on the defined ‘Email Type’.

== Usage: ==

As mentioned previously once setup emails will be automatically sent based on the following conditions:
•An order is dispatched to a customer who has the ‘email required’ field set to ‘Yes’ and has a email associated with the order.

•An order is short received for a supplier/owner who has a email setup.

•An order is short allocated for a owner who has a email setup.

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>v0.1</center>
| <center>16/11/10</center>
| <center>User Guide</center>
| User Guide
| <center>LSM</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Dynamic Email Setup

2010-11-16T09:57:49Z

Duttont:

=Dynamic Email Notifications=

This functionality allows email to be sent to various parties, allowing for notifications under the following conditions:

•Despatch Confirmation: this will email the customer.

•Short Receipt: this will email the supplier or owner.

•Short Allocation: this will email the owner.

== Setup: ==

=== System Setup: ===

The system is required to be configured to forward emails via a email server. This server must accept SMTP connections. A parameter needs to be added to the registry of the system containing the IP address of the email server. This parameter is added under the description of ‘EmailServer’ and data is set to the IP address of the server.

[[image|dynEmail1.PNG]]

[[image|dynEmail2.PNG]]

== Email Setup: ==

To use this functionality the following three groups will need email address’s setup; Customers, Suppliers, and Owners.

==== Customers Email: ====

Customers requiring emails must be setup in the ‘Customer Wizard’ menu. Once the required customer is found change the ‘Email Required’ field to ‘Yes’.

[[image|dynEmail3.PNG]]

Also the owner of the product must be set to run the despatch email: OBS_DESP, within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail4.PNG]]

Now any customer who has an email address associated with an order will be emailed upon dispatch, providing the setup is complete. Please note that the orders FTA must have the email address populated otherwise this function will not be able to send the despatch confirmation.

==== Suppliers Email: ====

This can be added to a supplier within the ‘Supplier Wizard’ screen, under the ‘Buyer Address’ tab.

[[image|dynEmail5.PNG]]

In addition the owner must have the short allocation procude set up and a be setup to run the SHORT_RECPT procedure within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail6.PNG]]

==== Owners Email: ====

This can be added to an owner as a default email within the ‘Owner Maintenance’ menu.

[[image|dynEmail7.PNG]]

=== Dynamic Email Setup: ===

Emails can be setup within the ‘Email Maintenance’ menu. This screen allows users to Add New email templates. Templates are dependent on the template description. The following template descriptions can be used:
•SHORT_RECPT – For short receipt emails
•OBS_DESP – For Despatch Confirmations
•OBS-SHALL – For Short Allocation emails

[[image|dynEmail8.PNG]]

‘Email title’ field must be added, this will complete the subject of the email. The ‘Email From Address’ field will be the email that the message is send from.
The ‘Message Type’ field controls in which scenarios the email will be sent. The available scenarios are as follows:
•Despatch
•Short Receipt
•Short Allocation
The ‘Test Email To Address’ field and ‘Test’ button can be used to forward emails to a specified address for testing purposes.
The ‘Email Body’ field allows users to specific a email, either as plain text or as HTML. Tags can be entered into this field allowing for dynamic data to be inserted into the email.
The following tags can be entered for short receipts:

•[SUPPLIER_NAME]

•[OWNER_NAME]

•[WAREHOUSE_NAME]

•[GRN_NO]

•[ADVICE_NOTE_NO]

•[CONTAINER_NO]

•[RECEIPT_DATE]

The following tags can be entered for short allocation:

•[ORDER_NUM]

•[ORDER_REF]

•[CUST_PO_ REF]

•[CUST_CODE]

•[CUST_NAME]

•[DATE]

The following tags can be entered for despatch confirmation:

•[NAME]

•[ORD_NUM]

•[ORD_DESC]

•[DESPDATE]

•[TRACK_START]

•[TRACKINGREF]

•[TRACK_END]

•[DEL NAME]

•[DEL ADDR1]

•[DEL ADDR2]

•[DEL ADDR3]

•[DEL POST]

•<nowiki></nowiki> (These tags can be used to produce a table of all items and quantities of the order, the following HTML code is recommended for use:

<nowiki><table width="90%" border="0">
<col align="left" />
<col align="left" />
<col align="right" />
<tr>
<th>Item Code</th>
<th>Description</th>
<th>Qty</th>
</tr>


</table></nowiki>

Once setup emails will be automatically triggered dependant on the defined ‘Email Type’.

== Usage: ==

As mentioned previously once setup emails will be automatically sent based on the following conditions:
•An order is dispatched to a customer who has the ‘email required’ field set to ‘Yes’ and has a email associated with the order.

•An order is short received for a supplier/owner who has a email setup.

•An order is short allocated for a owner who has a email setup.

=References=

{| Border="1"
| <center>'''Ref No'''</center>
| <center>'''Document Title & ID'''</center>
| <center>'''Version'''</center>
| <center>'''Date'''</center>

|-
| Test Ref
| Test Document.doc
| <center>Test Version</center>
| <center>Test Date</center>
|}

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>v0.1</center>
| <center>16/11/10</center>
| <center>User Guide</center>
| User Guide
| <center>LSM</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Dynamic Email Setup

2010-11-16T09:56:37Z

Duttont:

=Dynamic Email Notifications=

This functionality allows email to be sent to various parties, allowing for notifications under the following conditions:

•Despatch Confirmation: this will email the customer.

•Short Receipt: this will email the supplier or owner.

•Short Allocation: this will email the owner.

== Setup: ==

=== System Setup: ===

The system is required to be configured to forward emails via a email server. This server must accept SMTP connections. A parameter needs to be added to the registry of the system containing the IP address of the email server. This parameter is added under the description of ‘EmailServer’ and data is set to the IP address of the server.

[[image|dynEmail1.PNG]]

[[image|dynEmail2.PNG]]

== Email Setup: ==

To use this functionality the following three groups will need email address’s setup; Customers, Suppliers, and Owners.

==== Customers Email: ====

Customers requiring emails must be setup in the ‘Customer Wizard’ menu. Once the required customer is found change the ‘Email Required’ field to ‘Yes’.

[[image|dynEmail3.PNG]]

Also the owner of the product must be set to run the despatch email: OBS_DESP, within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail4.PNG]]

Now any customer who has an email address associated with an order will be emailed upon dispatch, providing the setup is complete. Please note that the orders FTA must have the email address populated otherwise this function will not be able to send the despatch confirmation.

==== Suppliers Email: ====

This can be added to a supplier within the ‘Supplier Wizard’ screen, under the ‘Buyer Address’ tab.

[[image|dynEmail5.PNG]]

In addition the owner must have the short allocation procude set up and a be setup to run the SHORT_RECPT procedure within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail6.PNG]]

==== Owners Email: ====

This can be added to an owner as a default email within the ‘Owner Maintenance’ menu.

[[image|dynEmail7.PNG]]

=== Dynamic Email Setup: ===

Emails can be setup within the ‘Email Maintenance’ menu. This screen allows users to Add New email templates. Templates are dependent on the template description. The following template descriptions can be used:
•SHORT_RECPT – For short receipt emails
•OBS_DESP – For Despatch Confirmations
•OBS-SHALL – For Short Allocation emails

[[image|dynEmail8.PNG]]

‘Email title’ field must be added, this will complete the subject of the email. The ‘Email From Address’ field will be the email that the message is send from.
The ‘Message Type’ field controls in which scenarios the email will be sent. The available scenarios are as follows:
•Despatch
•Short Receipt
•Short Allocation
The ‘Test Email To Address’ field and ‘Test’ button can be used to forward emails to a specified address for testing purposes.
The ‘Email Body’ field allows users to specific a email, either as plain text or as HTML. Tags can be entered into this field allowing for dynamic data to be inserted into the email.
The following tags can be entered for short receipts:

•[SUPPLIER_NAME]

•[OWNER_NAME]

•[WAREHOUSE_NAME]

•[GRN_NO]

•[ADVICE_NOTE_NO]

•[CONTAINER_NO]

•[RECEIPT_DATE]

The following tags can be entered for short allocation:

•[ORDER_NUM]

•[ORDER_REF]

•[CUST_PO_ REF]

•[CUST_CODE]

•[CUST_NAME]

•[DATE]

The following tags can be entered for despatch confirmation:

•[NAME]

•[ORD_NUM]

•[ORD_DESC]

•[DESPDATE]

•[TRACK_START]

•[TRACKINGREF]

•[TRACK_END]

•[DEL NAME]

•[DEL ADDR1]

•[DEL ADDR2]

•[DEL ADDR3]

•[DEL POST]

•<nowiki></nowiki> (These tags can be used to produce a table of all items and quantities of the order, the following HTML code is recommended for use:

<nowiki><table width="90%" border="0">
<col align="left" />
<col align="left" />
<col align="right" />
<tr>
<th>Item Code</th>
<th>Description</th>
<th>Qty</th>
</tr>


</table></nowiki>

Once setup emails will be automatically triggered dependant on the defined ‘Email Type’.

== Usage: ==

As mentioned previously once setup emails will be automatically sent based on the following conditions:
•An order is dispatched to a customer who has the ‘email required’ field set to ‘Yes’ and has a email associated with the order.

•An order is short received for a supplier/owner who has a email setup.

•An order is short allocated for a owner who has a email setup.

=References=

{| Border="1"
| <center>'''Ref No'''</center>
| <center>'''Document Title & ID'''</center>
| <center>'''Version'''</center>
| <center>'''Date'''</center>

|-
| Test Ref
| Test Document.doc
| <center>Test Version</center>
| <center>Test Date</center>
|}

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Test Version</center>
| <center>Test Date</center>
| <center>Test Status</center>
| Test Reason
| <center>Test Intitals</center>

|-
| <center>Test Version</center>
| <center>Test Date</center>
| <center>Test Status</center>
| Test Reason
| <center>Test Intitals</center>
|}

=Authorised By=

{| Border="1"
| '''''Test Name'''''
| Test Title
|

|-
| '''''Test Name'''''
| Test Title
|

|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Dynamic Email Setup

2010-11-16T09:56:15Z

Duttont: New page: =Dynamic Email Notifications= This functionality allows email to be sent to various parties, allowing for notifications under the following conditions: •Despatch Confirmation: this will...

=Dynamic Email Notifications=

This functionality allows email to be sent to various parties, allowing for notifications under the following conditions:
•Despatch Confirmation: this will email the customer.
•Short Receipt: this will email the supplier or owner.
•Short Allocation: this will email the owner.

== Setup: ==
Sample Text

=== System Setup: ===

The system is required to be configured to forward emails via a email server. This server must accept SMTP connections. A parameter needs to be added to the registry of the system containing the IP address of the email server. This parameter is added under the description of ‘EmailServer’ and data is set to the IP address of the server.

[[image|dynEmail1.PNG]]

[[image|dynEmail2.PNG]]

== Email Setup: ==

To use this functionality the following three groups will need email address’s setup; Customers, Suppliers, and Owners.

==== Customers Email: ====

Customers requiring emails must be setup in the ‘Customer Wizard’ menu. Once the required customer is found change the ‘Email Required’ field to ‘Yes’.

[[image|dynEmail3.PNG]]

Also the owner of the product must be set to run the despatch email: OBS_DESP, within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail4.PNG]]

Now any customer who has an email address associated with an order will be emailed upon dispatch, providing the setup is complete. Please note that the orders FTA must have the email address populated otherwise this function will not be able to send the despatch confirmation.

==== Suppliers Email: ====

This can be added to a supplier within the ‘Supplier Wizard’ screen, under the ‘Buyer Address’ tab.

[[image|dynEmail5.PNG]]

In addition the owner must have the short allocation procude set up and a be setup to run the SHORT_RECPT procedure within the ‘Owner Maintainence’ menu under the ‘Format’ tab.

[[image|dynEmail6.PNG]]

==== Owners Email: ====

This can be added to an owner as a default email within the ‘Owner Maintenance’ menu.

[[image|dynEmail7.PNG]]

=== Dynamic Email Setup: ===

Emails can be setup within the ‘Email Maintenance’ menu. This screen allows users to Add New email templates. Templates are dependent on the template description. The following template descriptions can be used:
•SHORT_RECPT – For short receipt emails
•OBS_DESP – For Despatch Confirmations
•OBS-SHALL – For Short Allocation emails

[[image|dynEmail8.PNG]]

‘Email title’ field must be added, this will complete the subject of the email. The ‘Email From Address’ field will be the email that the message is send from.
The ‘Message Type’ field controls in which scenarios the email will be sent. The available scenarios are as follows:
•Despatch
•Short Receipt
•Short Allocation
The ‘Test Email To Address’ field and ‘Test’ button can be used to forward emails to a specified address for testing purposes.
The ‘Email Body’ field allows users to specific a email, either as plain text or as HTML. Tags can be entered into this field allowing for dynamic data to be inserted into the email.
The following tags can be entered for short receipts:

•[SUPPLIER_NAME]

•[OWNER_NAME]

•[WAREHOUSE_NAME]

•[GRN_NO]

•[ADVICE_NOTE_NO]

•[CONTAINER_NO]

•[RECEIPT_DATE]

The following tags can be entered for short allocation:

•[ORDER_NUM]

•[ORDER_REF]

•[CUST_PO_ REF]

•[CUST_CODE]

•[CUST_NAME]

•[DATE]

The following tags can be entered for despatch confirmation:

•[NAME]

•[ORD_NUM]

•[ORD_DESC]

•[DESPDATE]

•[TRACK_START]

•[TRACKINGREF]

•[TRACK_END]

•[DEL NAME]

•[DEL ADDR1]

•[DEL ADDR2]

•[DEL ADDR3]

•[DEL POST]

•<nowiki></nowiki> (These tags can be used to produce a table of all items and quantities of the order, the following HTML code is recommended for use:

<nowiki><table width="90%" border="0">
<col align="left" />
<col align="left" />
<col align="right" />
<tr>
<th>Item Code</th>
<th>Description</th>
<th>Qty</th>
</tr>


</table></nowiki>

Once setup emails will be automatically triggered dependant on the defined ‘Email Type’.

== Usage: ==

As mentioned previously once setup emails will be automatically sent based on the following conditions:
•An order is dispatched to a customer who has the ‘email required’ field set to ‘Yes’ and has a email associated with the order.

•An order is short received for a supplier/owner who has a email setup.

•An order is short allocated for a owner who has a email setup.

=References=

{| Border="1"
| <center>'''Ref No'''</center>
| <center>'''Document Title & ID'''</center>
| <center>'''Version'''</center>
| <center>'''Date'''</center>

|-
| Test Ref
| Test Document.doc
| <center>Test Version</center>
| <center>Test Date</center>
|}

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Test Version</center>
| <center>Test Date</center>
| <center>Test Status</center>
| Test Reason
| <center>Test Intitals</center>

|-
| <center>Test Version</center>
| <center>Test Date</center>
| <center>Test Status</center>
| Test Reason
| <center>Test Intitals</center>
|}

=Authorised By=

{| Border="1"
| '''''Test Name'''''
| Test Title
|

|-
| '''''Test Name'''''
| Test Title
|

|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

Main Page

2010-11-16T09:38:47Z

Duttont:

===WMS Quick Guides===
----
<ul>
<li>[[Quick Standing Data Maintenance]]</li>
<li>[[Quick WMS Processing]]</li>
</ul>

=== WMS Process Guides ===
----
<ul>
<li>[[EDI Setup and Processing]]</li>
<li>[[WMS Processing]]</li>
<li>[[WMS Enquiries]]</li>
<li>[[WMS Reports]]</li>
</ul>

=== WMS Setup Guides ===
----

<ul>

<li>[[System Navigation Guide]]</li>

<li>[[Company Set Up]]</li>
<li>[[Warehouse Set Up]]</li>
<li>[[Owner Set Up]]</li>
<li>[[Partner Set Up]]</li>
<li>[[Stock Set Up]]</li>

<li>[[Menu Maintenance]]</li>
<li>[[WMS/RDT Control Maintenance]]</li>
<li>[[Owner Invoicing]]</li>

<li>[[Creating default damage and quarantine locations]]</li>
<li>[[How to Hold Stock]]</li>
<li>[[Dynamic Email Setup]]</li>
</ul>

<ul>
<li>[[FAQ]]</li>
<ul>

=== WMS Programs ===
----
<ul>
<li>[[Program Listing]]</li>
</ul>

=== Releases ===
----
<ul>
<li>[[Recent Releases]]</li>
</ul>

Main Page

2010-11-10T14:54:24Z

Duttont: /* WMS Programs */

===WMS Quick Guides===
----
<ul>
<li>[[Quick Standing Data Maintenance]]</li>
<li>[[Quick WMS Processing]]</li>
</ul>

=== WMS Process Guides ===
----
<ul>
<li>[[EDI Setup and Processing]]</li>
<li>[[WMS Processing]]</li>
<li>[[WMS Enquiries]]</li>
<li>[[WMS Reports]]</li>
</ul>

=== WMS Setup Guides ===
----

<ul>

<li>[[System Navigation Guide]]</li>

<li>[[Company Set Up]]</li>
<li>[[Warehouse Set Up]]</li>
<li>[[Owner Set Up]]</li>
<li>[[Partner Set Up]]</li>
<li>[[Stock Set Up]]</li>

<li>[[Menu Maintenance]]</li>
<li>[[WMS/RDT Control Maintenance]]</li>
<li>[[Owner Invoicing]]</li>

<li>[[Creating default damage and quarantine locations]]</li>
<li>[[How to Hold Stock]]</li>

</ul>

<ul>
<li>[[FAQ]]</li>
<ul>

=== WMS Programs ===
----
<ul>
<li>[[Program Listing]]</li>
</ul>

=== Releases ===
----
<ul>
<li>[[Recent Releases]]</li>
</ul>

Main Page

2010-11-10T14:54:05Z

Duttont: /* WMS Quick Guides */

===WMS Quick Guides===
----
<ul>
<li>[[Quick Standing Data Maintenance]]</li>
<li>[[Quick WMS Processing]]</li>
</ul>

=== WMS Process Guides ===
----
<ul>
<li>[[EDI Setup and Processing]]</li>
<li>[[WMS Processing]]</li>
<li>[[WMS Enquiries]]</li>
<li>[[WMS Reports]]</li>
</ul>

=== WMS Setup Guides ===
----

<ul>

<li>[[System Navigation Guide]]</li>

<li>[[Company Set Up]]</li>
<li>[[Warehouse Set Up]]</li>
<li>[[Owner Set Up]]</li>
<li>[[Partner Set Up]]</li>
<li>[[Stock Set Up]]</li>

<li>[[Menu Maintenance]]</li>
<li>[[WMS/RDT Control Maintenance]]</li>
<li>[[Owner Invoicing]]</li>

<li>[[Creating default damage and quarantine locations]]</li>
<li>[[How to Hold Stock]]</li>

</ul>

<ul>
<li>[[FAQ]]</li>
<ul>

=== WMS Programs ===
----
<ul>
<li>[[Program Listing]]</li>
</ul>

=== Releases ===
----
<ul>
<li>[[Recent Releases]]</li>
</ul>

Stock Movement Request

2010-11-10T14:51:09Z

Duttont:

<br\>

=='''Stock Movements – Stock Movement Request'''==
<br\>

The Stock Movements Request screen is used to move stock around within the warehouse.

The Stock Movements Request screen is located in the Stock Movements folder.

The following document covers how to move full and part pallets. Part pallets are referred to as ‘Stock Movements’.

'''Full Pallet Movement'''
<br\>

[[Image:WHS0700SIG.PNG]]
<br\>

Click in the Pallet radio button (see screen shot below).
<br\>

[[Image:WHS0700SIG1.PNG]]
<br\>

Press the ‘Cancel Query’ button.
<br\>

[[Image:WHS0700SIG2.PNG]]
<br\>

An audit number has now been produced (see screen shot above).

Click in the Owner code field (see screen shot above).
<br\>

[[Image:WHS0700SIG3.PNG]]
<br\>

The Owner Code field will be automatically filled with the default owner set up for the user.
Stock Code – Enter the stock code you wish to move. Alternatively, use the list of values to select from.

Pallet ID – Enter the pallet ID that you wish to move.

From Location – This will be populated automatically with the location that the pallet is currently stored in.

To Location – If auto-putaway is switched on, the system will automatically suggest a new location. This can be deleted and you can select your own by either manually typing it in, or by using the list of values.
<br\>

[[Image:WHS0700SIG4.PNG]]
<br\>

Press the Accept/Confirm button when have entered the required data (see above screen shot).

Press the ‘Print’ button (see screen shot below)
<br\>

[[Image:WHS0700SIG5.PNG]]
<br\>

A pop up box will now be displayed.
<br\>

[[Image:WHS0700SIG6.PNG]]
<br\>

You can change whether you wish Pallet Labels and a Driver Summary along with the formats of the prints.

The output manager box will now be displayed. Press the screen icon and then click the OK button.
<br\>

[[Image:WHS0700SIG7.PNG]]
<br\>

The movement report will now print.
<br\>

[[Image:WHS0700SIG8.PNG]]
<br\>

[[Image:WHS0700SIG9.PNG]]
<br\>

There are 3 fields that need to be completed before the movement can be confirmed.

Driver – An employee code must be entered. The list of values can be used to display all valid employees.

Checker - An employee code must be entered. The list of values can be used to display all valid employees.

Date/Time – A date and time can be manually entered or if you tab across the field, the system will default to today’s date and time.

Once all the data has been entered, press the ‘Confirm’ button to complete the movement (see screen shot below).
<br\>

[[Image:WHS0700SIG10.PNG]]
<br\>

A message will be displayed stating that the movement has been confirmed.
<br\>

[[Image:WHS0700SIG11.PNG]]
<br\>

'''Stock Movement'''
<br\>

Click in the ‘Stock’ radio button (see screen shot below).
<br\>

[[Image:WHS0700SIG12.PNG]]
<br\>

Press the ‘Cancel Query’ button.
<br\>

[[Image:WHS0700SIG13.PNG]]
<br\>

An audit number has now been produced (see screen shot above).

The screen is very similar to the pallet movement option, however, here you can specify the number of cases or units to move.

The Owner Code field will be automatically filled with the default owner set up for the user.

Stock Code – Enter the stock code you wish to move. Alternatively, use the list of values to select from.

Pallet ID – Enter the pallet ID that you wish to move.

From Location – This will be populated automatically with the location that the pallet is currently stored in.

Cases – Enter the number of cases that you wish to move.

Units - Enter the number of units that you wish to move.

To Location – If auto-putaway is switched on, the system will automatically suggest a new location. This can be deleted and you can select your own by either manually typing it in, or by using the list of values.
<br\>

[[Image:WHS0700SIG14.PNG]]
<br\>

When you click in the ‘To Location’ field a pop-up box will be displayed. You need to choose one of the options:
<br\>

[[Image:WHS0700SIG15.PNG]]
<br\>

In this instance we will use an existing pallet that already contains the same stock. Click the ‘Confirm’ button when you have selected your choice.
<br\>

[[Image:WHS0700SIG16.PNG]]
<br\>

The ‘Pallet Id To’ field will be automatically populated with the pallet id that is currently stored in the location you selected.

Press the Accept/Confirm button when have entered the required data (see above screen shot).
<br\>

[[Image:WHS0700SIG17.PNG]]
<br\>

Press the ‘Print’ button (see screen shot below)
<br\>

[[Image:WHS0700SIG18.PNG]]
<br\>

A pop up box will now be displayed.
<br\>

[[Image:WHS0700SIG19.PNG]]
<br\>

You can change whether you wish Pallet Labels and a Driver Summary along with the formats of the prints.

The output manager box will now be displayed. Press the screen icon and then click the OK button.
<br\>

[[Image:WHS0700SIG20.PNG]]
<br\>

The movement report will now print.
<br\>

[[Image:WHS0700SIG21.PNG]]
<br\>

There are 3 fields that need to be completed before the movement can be confirmed.

Driver – An employee code must be entered. The list of values can be used to display all valid employees.

Checker - An employee code must be entered. The list of values can be used to display all valid employees.

Date/Time – A date and time can be manually entered or if you tab across the field, the system will default to today’s date and time.

Once all the data has been entered, press the ‘Confirm’ button to complete the movement (see screen shot below).
<br\>

[[Image:WHS0700SIG22.PNG]]
<br\>

Once the movement is confirmed a message will be displayed.
<br\>

[[Image:WHS0700SIG23.PNG]]
<br\>

=Document History=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>Version 1</center>
| <center>10/11/2010</center>
| <center>Released</center>
|
| <center>LBW</center>
|}

Copyright OBS Logistics © 2008

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

File:WHS0700SIG23.PNG

2010-11-10T14:49:14Z

Duttont:

File:WHS0700SIG22.PNG

2010-11-10T14:48:55Z

Duttont:

File:WHS0700SIG21.PNG

2010-11-10T14:48:40Z

Duttont:

File:WHS0700SIG20.PNG

2010-11-10T14:48:12Z

Duttont:

File:WHS0700SIG19.PNG

2010-11-10T14:47:33Z

Duttont:

File:WHS0700SIG18.PNG

2010-11-10T14:46:47Z

Duttont:

File:WHS0700SIG17.PNG

2010-11-10T14:46:31Z

Duttont:

File:WHS0700SIG16.PNG

2010-11-10T14:46:10Z

Duttont:

File:WHS0700SIG15.PNG

2010-11-10T14:45:53Z

Duttont:

File:WHS0700SIG14.PNG

2010-11-10T14:45:35Z

Duttont:

File:WHS0700SIG13.PNG

2010-11-10T14:45:16Z

Duttont:

File:WHS0700SIG12.PNG

2010-11-10T14:44:54Z

Duttont:

File:WHS0700SIG11.PNG

2010-11-10T14:44:42Z

Duttont: uploaded a new version of "Image:WHS0700SIG11.PNG"

File:WHS0700SIG11.PNG

2010-11-10T14:44:02Z

Duttont:

File:WHS0700SIG10.PNG

2010-11-10T14:43:43Z

Duttont:

File:WHS0700SIG9.PNG

2010-11-10T14:43:24Z

Duttont:

File:WHS0700SIG8.PNG

2010-11-10T14:43:05Z

Duttont:

File:WHS0700SIG7.PNG

2010-11-10T14:42:46Z

Duttont:

File:WHS0700SIG6.PNG

2010-11-10T14:42:29Z

Duttont:

File:WHS0700SIG5.PNG

2010-11-10T14:42:11Z

Duttont:

File:WHS0700SIG4.PNG

2010-11-10T14:41:49Z

Duttont:

File:WHS0700SIG3.PNG

2010-11-10T14:41:13Z

Duttont:

File:WHS0700SIG2.PNG

2010-11-10T14:40:48Z

Duttont:

File:WHS0700SIG1.PNG

2010-11-10T14:40:33Z

Duttont:

File:WHS0700SIG.PNG

2010-11-10T14:40:19Z

Duttont:

Stock Movement Request

2010-11-10T14:38:22Z

Duttont: New page: <br\> =='''Stock Movements – Stock Movement Request'''== <br\> The Stock Movements Request screen is used to move stock around within the warehouse. The Stock Movements Request scr...

File:WHS0630SIG16.PNG

2010-11-10T14:01:23Z

Duttont:

File:WHS0630SIG14.PNG

2010-11-10T14:00:18Z

Duttont:

File:WHS0630SIG21.PNG

2010-11-10T13:58:17Z

Duttont: