Difference between revisions of "Scanning and Importing PODs into Platinum"
From Catalyst
| Line 1: | Line 1: | ||
| − | |||
| − | |||
== Summary == | == Summary == | ||
The following article explains the Scanning and Bulk importing of POD's to Platinum. | The following article explains the Scanning and Bulk importing of POD's to Platinum. | ||
| − | == | + | == More Information == |
The procedure for importing POD’s into Platinum is as follows: | The procedure for importing POD’s into Platinum is as follows: | ||
*'''1.''' Go to '''"Logistics Management”''' -> '''“Planning screen”''' | *'''1.''' Go to '''"Logistics Management”''' -> '''“Planning screen”''' | ||
| − | Bring up a date that includes a ticket you need to scan POD’s for or this can be done from the actual ticket entry screen either while the ticket is being produced or after via the planning screen | + | Bring up a date that includes a ticket you need to scan POD’s for or this can be done from the actual ticket entry screen either while the ticket is being produced or after via the planning screen. |
| − | *'''2.''' Arrow | + | *'''2.''' {{KeyPress|Arrow down}} to the correct Ticket and press {{Button|F9}} to print the ticket header page and repeat for all the tickets you have POD’s for. |
*'''3.''' Organize your POD’s putting the relevant ticket header page first before the following POD pages. | *'''3.''' Organize your POD’s putting the relevant ticket header page first before the following POD pages. | ||
| − | *'''4.''' Move to the scanning PC (if not already there) and | + | *'''4.''' Move to the scanning PC (if not already there) and open Docscan Pro. |
| − | *'''5.''' Using the | + | *'''5.''' Using the {{DataPrompt|Browse}} box on the left make sure the {{DataPrompt|INBOX}} folder is selected for the relevant SXCO folder. |
*'''6.''' Load scanner with your organized POD’s. | *'''6.''' Load scanner with your organized POD’s. | ||
| − | *'''7.''' Press | + | *'''7.''' Press the button at the top of Docscan or press {{Button|F9}} to start the scan process. |
| − | *'''8.''' | + | *'''8.''' You will see a {{DataPrompt|Scanning Options}} screen. Make sure there is a tick in {{DataPrompt|Use Template}}, select {{DataValue|Platinum COLOR A4}} and click {{Button|Scan}}. |
| − | *'''9.''' Once this is complete your '''INBOX''' should be full of .Tif files that have names referring to ticket numbers | + | *'''9.''' Once this is complete your '''INBOX''' should be full of .Tif files that have names referring to ticket numbers which have been read from the bar codes on the Header pages. If these bar codes have not been read correctly (this can happen if the header page has not been read correctly (for example if the header page has been put in the scanner the wrong way round) you will find the file name will be the date of the scan rather than the Ticket Number and will have to be scanned again. Once you have checked for this, exit Docscan. |
| − | *'''10.''' Select | + | *'''10.''' Select "{{TI}}" -> "Maintenance Options" -> "Bulk import of Scanned Documents". |
| − | *'''11.''' A timer will appear and after | + | *'''11.''' A timer will appear and after a minute or so, the prompt should change and you will see all the docs stored in the '''INBOX''' appear – this is moving them to the relevant location and applying them to the relevant tickets for viewing in Platinum. |
| − | *'''12.''' Any images that are | + | *'''12.''' Any images that are left in the '''INBOX''' folder will be images that do not have a file name that relates to a valid ticket number and this should be investigated and steps '''7''' to '''12''' should be repeated. |
== See also == | == See also == | ||
*[[Entering Logistics Management Jobs]] | *[[Entering Logistics Management Jobs]] | ||
| − | {{KB_Tags|POD, Proof Of Delivery, Proof, Delivery, Deliveries, Docscan, Solarsys}} | + | {{KB_Tags|POD, Proof Of Delivery, Proof, Delivery, Deliveries, Docscan, Solarsys, scanning, Scan}} |
{{KB_TI}} {{ZN_Admin}} | {{KB_TI}} {{ZN_Admin}} | ||
Revision as of 14:57, 29 December 2009
Summary
The following article explains the Scanning and Bulk importing of POD's to Platinum.
More Information
The procedure for importing POD’s into Platinum is as follows:
- 1. Go to "Logistics Management” -> “Planning screen”
Bring up a date that includes a ticket you need to scan POD’s for or this can be done from the actual ticket entry screen either while the ticket is being produced or after via the planning screen.
- 2. <Arrow down> to the correct Ticket and press [F9] to print the ticket header page and repeat for all the tickets you have POD’s for.
- 3. Organize your POD’s putting the relevant ticket header page first before the following POD pages.
- 4. Move to the scanning PC (if not already there) and open Docscan Pro.
- 5. Using the "Browse" box on the left make sure the "INBOX" folder is selected for the relevant SXCO folder.
- 6. Load scanner with your organized POD’s.
- 7. Press the button at the top of Docscan or press [F9] to start the scan process.
- 8. You will see a "Scanning Options" screen. Make sure there is a tick in "Use Template", select 'Platinum COLOR A4' and click [Scan].
- 9. Once this is complete your INBOX should be full of .Tif files that have names referring to ticket numbers which have been read from the bar codes on the Header pages. If these bar codes have not been read correctly (this can happen if the header page has not been read correctly (for example if the header page has been put in the scanner the wrong way round) you will find the file name will be the date of the scan rather than the Ticket Number and will have to be scanned again. Once you have checked for this, exit Docscan.
- 10. Select "Logistics Management" -> "Maintenance Options" -> "Bulk import of Scanned Documents".
- 11. A timer will appear and after a minute or so, the prompt should change and you will see all the docs stored in the INBOX appear – this is moving them to the relevant location and applying them to the relevant tickets for viewing in Platinum.
- 12. Any images that are left in the INBOX folder will be images that do not have a file name that relates to a valid ticket number and this should be investigated and steps 7 to 12 should be repeated.
See also
