QAD 2017 Enterprise Edition > User Guides > Sales > Shipping > Creating Scanned Shipping Documents
  
Creating Scanned Shipping Documents
Use Shipper Gateway (7.9.22) to import records scanned by a bar-code reader. The records represent containers, pre-shippers, shippers, or items. The data can come from an ASCII-formatted file or be output from a UNIX process.
Shipper Gateway provides two options for the normal shipment flow from pre-shipper to shipper:
Verify shipment contents to determine whether they match the pre-shipper or stage list.
Verify shipment contents and create shippers from the scanned information. In this case, you do not need to use a pre-shipper. Instead, scan in the shipment information and create the shipper from that data. This method can satisfy some customer requirements to create shippers and ASNs electronically, rather than manually.
Each line of an inbound Shipper Gateway document file represents a line on the shipper and correspond to a single abs_mstr record. Since a typical shipper (type S) may include containers (type C) and items (type I), the fields required for a particular line vary.
Format for Shipper Gateway Files lists each field in the abs_mstr record and indicates whether it applies to shipper, container, item, or receiver lines.
The following rules apply to the document format:
Separate each record (line) with a hard carriage return.
Specify a value for each field listed in Format for Shipper Gateway Files.
When a value is not applicable or optional, enter a hyphen. This tells the system to use the default value or blank.
Surround a field with quotation marks unless it accepts only integer or decimal data.
The following example represents a file that loads shipper (S), container (C), and item (I) records in abs_mstr. The system ignores fields containing the hyphen placeholders. In this example, the item is listed on SO11898.
"S" - - "crmsite" "1207-3" - - - - "crm1207" - - - - - - - - - - - - - - - -
"C" "crmsite" "crmloc" "crmsite" "1207C-3" "crm1207cnt" - - 1.00 - - - "S1207-3" - "EA" 135.00 "LB" - - 35.00 "LB" - - - - -
"I" "crmsite" "crmloc" "crmsite" - "crm1207sg" - - 10.0 - "SO11898" 1 "C1207C-3" - "EA" 100.00 "LB" - - 100.00 "LB" - - - - -
Enter values in the following fields to import scanned information:
Process/File
Enter Process if you want the system to look for an executable program or script, start it as a separate process, and read its standard output. Enter File if you want the system to look for, open, and read an ASCII file. The Process option can be used only with UNIX systems. See Format for Shipper Gateway Files for detailed format requirements of Shipper Gateway documents.
Filename
Enter the name of the file or process to derive data from. If a process, it must exist in your PROPATH and be an executable program. If a file, it must be in ASCII format.
Load Multiple Containers
Enter Yes to enable the system to add multiple containers to the shipper during import when the quantity specified for a container line is not equal to 1.
When the field is No, the system adds a single container regardless of the quantity specified.
Verify Only
Enter Yes to verify that the shipment contents match the pre-shipper or stage list.
Enter No to verify shipment contents and also create shippers from the scanned information. The system stores the records it reads into the database.

Format for Shipper Gateway Files
 
Seq
Field
Applies to Record Type
Description
1
Type
C
S
I
R
Must be C (Container), S (Shipper), I (Item), or R (Receiver).
2
Site
C
I
Must be a valid site code.
3
Location
C
I
Optional. If supplied, must be a valid location at the specified site.
4
Ship-from
C
S
I
R
Must be a valid site code and must be supplied with records that have a Parent ID.
5
ID
C
S
R
Must be unique in combination with Ship-From. Do not supply a prefix letter.
6
Item
C
I
Must be a valid item number.
7
Lot/serial
C
I
The lot or serial number for the item.
8
Reference
C
I
The reference number for the item.
9
Quantity
C
I
The item quantity.
10
Ship-to
S
R
Must be a valid ship-to address code.
11
Order Number
I
Must be a valid sales order number unless the item is from a receiver. Then, specify a valid purchase order number.
12
Line
I
Must be a valid sales order line number unless the item is from a receiver. Then, specify a valid purchase order line number.
13
Parent ID
C
I
The parent record ID number, including the S or C prefix.
14
Customer PO
I
The customer’s purchase order number.
15
Quantity UM
C
I
Must be a valid unit of measure code.
16
Gross Weight
C
S
I
R
For type I, enter the item’s gross weight. The system derives the tare weight from the difference between the gross and net weights.
For type S, R, and C, this field is ignored. The system calculates type S and C gross weights during processing.
17
Weight UM
C
S
I
R
The UM associated with Gross Weight.
18
Volume
C
S
I
R
The volume for the record.
19
Volume UM
C
S
I
R
The UM associated with Volume.
20
Weight
C
S
I
R
For type I, enter the item’s net weight.
For type S, R, and C, enter the tare weight. This weight is rolled up during the processing of the shipper lines and containers.
21
Ship Via
S
R
The carrier to use for the shipper.
22
FOB
S
R
The FOB point for the shipper.
23
Carrier Reference
S
R
The ID of the carrier for the shipper.
24
Transportation Mode
S
R
The method of delivery for the shipper.
25
Vehicle Reference
S
R
The ID of the vehicle for the shipper.
26
Kanban
C
I
The Kanban number for the shipper.
27
Customer Job
I
The customer job of the item.
28
Customer Sequence
I
The customer sequence of the item.
29
Customer Dock
I
The customer dock where the part is to be delivered.
30
Customer Linefeed
I
The customer line feed location where the part is to be delivered.
31
Sequence Status
I
The indicator for sequences with special statuses, such as prototype.
32
Customer Ref
C
I
The customer reference for the item.
33
Model Year
C
I
The model year of the item.
34
Consigned Return
C
S
I
R
Yes or No, depending whether shipment is returning consigned items.