Chapter Two: FSMS Transaction Coding
92 FedEx Ship Manager
®
Server User Guide, Version 7.6
Coding Guidelines
To help you create your shipping transactions using FSMS, we have provided these coding guidelines for:
• Transaction formatting
• Required field numbers
• Shipment level vs. package level fields
• Multiple occurrence fields
• Field editing guidelines
• Reply transaction fields 2 and 3 (error code and error message text)
• Reply transaction fields 557, 558, and 559 (error type code, error code, and error message)
These guidelines should be reviewed before you begin any transaction coding.
Transaction Formatting
The transaction records are null terminated strings that do not contain carriage returns or line feeds. The
strings consist of field-related pairs separated by a comma. Each pair consists of the:
• Field ID number
• Field value enclosed in double quotation marks
For example, if you are coding field 15 (Recipient City) and you want to assign “Memphis” as the value,
the transaction string for this field is formatted as:
15,”Memphis”
Required Fields
Some fields are required in all transactions. Other fields are required under specific conditions, and still
others are optional. Required fields are denoted in the FSMS TCR in bold and are listed as Required.
Fields conditionally required are marked with an asterisk (*) next to the requirement field (for example:
Required*). Optional fields are listed as Optional.
The following is a sample table entry from the FSMS TCR for each of these field requirement types.
Field indicators:
• E = Express
• G = Ground
• A superscript S indicates the field is to be used at the shipment level for a single transaction MPS or
to be included in an Open Ship Create transaction.
• Required indicates a mandatory field.
• Required* indicates a ‘required if’ condition.
To Next Page
Loading...