Chapter Two: FSMS Transaction Coding
FedEx Ship Manager
®
Server User Guide, Version 7.6 95
Multiple Occurrence Fields
Multiple occurrence fields may be used several times within a single transaction. Each occurrence may
have a different value. Using multiple occurrence fields eliminates the need to code the same field over
and over simply because the input values change.
The format for a multiple occurrence field is X-#. This format means that:
• X = The field number that is to be used multiple times
• – = Dash is used as a separator
• # = The number of the occurrence. The maximum number of field occurrences is 999 unless
otherwise noted within a specific transaction’s format. If you use more than 500 occurrences, please
contact your FedEx Customer Support Representative.
For example, field 1670 (Package Weight) is a multiple occurrence field. If the first package in an MPS
shipment weighs 2 pounds, the second weighs 3 pounds, and a third package weighs 5 pounds, field
1670 is used as follows:
1670-1,”200”1670-2,”300”1670-3,”500”
This entry allows three different packages to be entered using the same field number with an occurrence
indicator. You may choose to eliminate the dash and the number value for the first occurrence field in any
transaction. In the example above, the first package could have been represented as 1670, “200” or
1670-1, “200”.
NOTE:
Field 1670 has two implied decimals. In the above example, 200 is 2 pounds.
NOTE:
When coding a multiple occurrence field, do not use any leading zeros. For example, one
occurrence is coded as “X-1”; 25 occurrences of the field are coded as “X-25”; 999 occurrences
of the field are coded as “X-999”.
Field Editing Guidelines
When editing fields within an FSMS transaction, the following editing rules apply to all transaction types:
1. Field values must be left justified within double quotation marks (“”).
2. Blank spaces between fields are not allowed. For example, you may format field 12 (Recipient
Contact Name) as Bob Shipper, with a space. However, when you add field 13 (Recipient Address
1) to the transaction string, there must be no spaces between the end of field 12 and the beginning of
field 13.
In addition to these two global transaction rules, the following field types have specific editing rules:
• Date fields
• Numeric fields
• Alphanumeric fields
• Postal Codes
• Weights
• Printer ID fields
To Next Page
Loading...