Scan Extract File 2.0 Layout
The Scan Extract File 2.0 record layout from Publication 199 Version 35, July 2, 2026: 1 record and 107 fields, in the order the file holds them.
Detail Record
107 fields, pages 425–438, 3 unchecked
PositionFieldFormat
- Description
- Version Number of the Extract
- Content rules
- Always 020
- Max Length
- 3
- Page
- Publication 199, page 425
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 425
- Description
- Tracking barcode number used on package. Will include routing information and Package Identification Code (PIC) when concatenated IMpb is printed on the label. If mailpiece is over- labeled, will contain over-labeled number.
- Content rules
- See Appendix J, Table 1 for the barcode construct formats.
- Max Length
- 34
- Page
- Publication 199, page 425
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 425
- Description
- Unique number assigned to identify the electronic file.
- Example
- ‘9275012345678912 34567 8’
- Content rules
- Taken from the Shipping Services File Header Record when the manifest file has been posted. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 34
- Page
- Publication 199, page 425
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 425
- Description
- Mailer ID number unique to this mailer as shown in the Postal Service database. Six- or Nine-digit MID.
- Example
- 912345678 or 612345
- Content rules
- Taken from the Electronic File Number when the manifest file has been posted. Daily Unmanifested – Mailer ID is populated
- Max Length
- 9
- Page
- Publication 199, page 425
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 425
- Description
- Mailer name associated with Mailer ID.
- Example
- ‘ABC Company’
- Content rules
- Mailer Name associated with the Mailer ID in the Electronic File Number. Daily Unmanifested – Mailer Name is populated
- Max Length
- 20
- Page
- Publication 199, page 425
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 425
- Description
- Destination ZIP Code.
- Example
- 33511
- Content rules
- Taken from the Shipping Services File Detail Record when the manifest file has been posted. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 5
- Page
- Publication 199, page 425
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 425
- Description
- Destination ZIP +4
- Example
- 1857
- Content rules
- Taken from the Shipping Services File Detail Record when the manifest file has been posted. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 4
- Page
- Publication 199, page 426
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 426
- Description
- Scan facility ZIP Code.
- Example
- 21201
- Content rules
- If scan event, 5-digit ZIP Code of facility. If manifest event, entry facility ZIP Code.
- Max Length
- 5
- Page
- Publication 199, page 426
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 426
- Description
- Name of Postal Service facility or city/state where event happened.
- Example
- ‘Baltimore, MD’
- Content rules
- The maximum allowable bytes for city is 28. The remaining bytes are used for the comma and the 2-digit alpha abbreviation for state or country. For domestic events, i.e., events with a Domestic Indicator of ‘Y’ in the Event Code Ref table, PTR defines the city/state event: 28 characters for city, 1 for comma, 2 for state alpha abbreviation. If the Scanning Facility ZIP Code is invalid, the description in this field will state “UNKNOWN”. PTR determines whether to display the city and/or state based on the Event Script Rule table. For international events, i.e., events with a Domestic Indicator of ‘N’ in the Event Code Ref table, PTR will populate the Scanning Facility Name using the below logic, deviating from Publication 91: For each event, PTR retrieves the display attributes for city and country from the Event Script Rule table to determine if the city and/or country are displayable. If the attribute for display has a ‘Y,’ PTR retrieves the value for the Event City and/or Event Country for the event. The values are then concatenated into the proper format based on the below rules. The format for international events: ‘CITY, COUNTRY CODE’ when city and country both have displayable values. ‘CITY’ when city has a displayable value, but country does not have a value or is not displayable. ‘COUNTRY CODE’ when the country has a displayable value, but city does not have a value or is not displayable. Null when no value is available for city or country or both are not displayable.
- Max Length
- 31
- Page
- Publication 199, page 426
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 427
- Description
- Code for tracking event.
- Example
- ‘01’
- Max Length
- 2
- Page
- Publication 199, page 427
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 427
- Description
- Name of tracking event corresponding to Event Code.
- Example
- Event description: ‘DELIVERED’ In the event of a duplicate: ‘DUPLICATE 1 DELIVERED’
- Content rules
- See Appendix G-4: Event Codes. The event name may be preceded by “DUPLICATE nn” when information about duplicate items with the same tracking number is provided in the scan.
- Max Length
- 40
- Page
- Publication 199, page 427
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 427
- Description
- Date of tracking event.
- Example
- 20090515
- Content rules
- YYYYMMDD
- Max Length
- 8
- Page
- Publication 199, page 427
Unchecked: a cell isn’t in the page’s text, or a second reading of the page doesn’t agree with the row.
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 427
- Description
- Time of tracking event.
- Example
- 1315
- Content rules
- HHMM
- Max Length
- 4
- Page
- Publication 199, page 427
Unchecked: a cell isn’t in the page’s text, or a second reading of the page doesn’t agree with the row.
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 427
- Description
- Mail Owner Mailer ID.
- Example
- 941233312
- Content rules
- Taken from the Shipping Services File Detail Record when the manifest has been posted. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 9
- Page
- Publication 199, page 428
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 428
- Description
- Used for customer internal identification purposes.
- Example
- ‘1223ABC’
- Content rules
- Taken from the Shipping Services File Detail Record when the manifest has been posted. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 30
- Page
- Publication 199, page 428
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 428
- Description
- Two character standardized IMM International country code.
- Example
- ‘GB’
- Content rules
- International mail only. Taken from the Shipping Services File Detail Record when the manifest has been posted. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 2
- Page
- Publication 199, page 428
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 428
- Description
- Name of Recipient for Signature Confirmation and Priority Mail Express service.
- Example
- ‘DOE J’
- Content rules
- Taken from the scanner/POS when mailpiece is delivered (signed for). Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 20
- Page
- Publication 199, page 428
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 428
- Content rules
- Taken from the Shipping Services File Detail Record Original Tracking Number field. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 34
- Page
- Publication 199, page 428
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 428
- Description
- Unit of measurement for mailpiece: 1 – LBS 2 – OZ 3 – KILOS
- Example
- 1
- Content rules
- Taken from the Shipping Services File Detail Record and included only when the Postal Service captures the weight of the mailpiece, when the manifest has been posted. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 1
- Page
- Publication 199, page 429
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 429
- Description
- Mailpiece weight. In unit of measure and significant to 4 decimal positions.
- Example
- Value is 00143250 for 14.3.
- Content rules
- Taken from the Shipping Services File Detail Record when the manifest has been posted. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 9
- Page
- Publication 199, page 429
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 429
- Description
- Service Guarantee Delivery Date
- Example
- 20090515
- Content rules
- Format: YYYYMMDD The Service Guarantee Delivery Date field shall be provided for Priority Mail Express, PMG, and GXG. The Service Guarantee Delivery Date field shall be populated for the first ‘TM’ (Shipping Acceptance), ‘OA’ (Origin Acceptance) or ‘03’ (Accept or Pickup) event for the Priority Mail Express, PMG, and GXG mailpieces. The Service Guarantee Delivery Date shall be updated with the best acceptance if the ‘TM’ (Shipping Acceptance), ‘OA’ (Origin Acceptance) or ‘03’ (Accept or Pickup) event is lower than the event associated with the current Service Guarantee Delivery Date according to the order of precedence. Field is populated with null when PTR provides the event data before the manifest has been received or the event was manually released from SDC Hold.
- Max Length
- 8
- Page
- Publication 199, page 429
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 429
- Description
- Service Guarantee Delivery Time
- Example
- 1315
- Content rules
- Format: HHMM The Service Guarantee Delivery Time field shall be provided for Priority Mail Express, PMG, and GXG. The Service Guarantee Delivery Time field shall be populated for the first ‘TM’ (Shipping Acceptance), ‘OA’ (Origin Acceptance) or ‘03’ (Accept or Pickup) event for the Priority Mail Express, PMG, and GXG mailpieces. The Service Guarantee Delivery Time shall be updated with the best acceptance if the ‘TM’ (Shipping Acceptance), ‘OA’ (Origin Acceptance) or ‘03’ (Accept or Pickup) event is lower than the event associated with the current Service Guarantee Delivery Time according to the order of precedence. Field is populated with null when PTR provides the event data before the manifest has been received or the event was manually released from SDC Hold.
- Max Length
- 4
- Page
- Publication 199, page 430
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 430
- Description
- MID of company that manages the mailing of this shipment. This would be a different company other than the consolidator. Six or Nine Digit Mailer ID.
- Example
- 941233312
- Content rules
- Taken from the Shipping Services File Detail Record 1. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 9
- Page
- Publication 199, page 430
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 430
- Description
- The Expected Delivery Date for the mailpiece.
- Example
- 20090515
- Content rules
- Format : YYYYMMDD
- Max Length
- 8
- Page
- Publication 199, page 430
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 430
- Description
- Indicates whether the Delivery Date has been modified from a previously provided date
- Example
- ‘1’
- Content rules
- When the Expected Delivery Date field is first populated or the Expected Delivery Date is updated and the new Expected Delivery Date is the same as the original value of the Scheduled Delivery Date, the Delivery Date Modification Indicator shall store ‘1’ (i.e., the delivery will be on time) to the Delivery Date Modification Indicator associated with the event. If the Expected Delivery Date is updated, and the new Expected Delivery Date is less than the original value of the Scheduled Delivery Date, the Delivery Date Modification Indicator field shall store ‘2’ (i.e., the delivery will be early) to the Delivery Date Modification Indicator associated with the event. If the Expected Delivery Date is updated, and the new Scheduled Delivery Date is greater than the original value of the Scheduled Delivery Date, the Delivery Date Modification Indicator shall be store ‘3’ (i.e., the delivery will be late) to the Delivery Date Modification Indicator associated with the event. Field is populated with null when PTR provides the event data before the manifest has been received or the event was manually released from SDC Hold.
- Max Length
- 1
- Page
- Publication 199, page 431
Unchecked: a cell isn’t in the page’s text, or a second reading of the page doesn’t agree with the row.
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 431
- Description
- Predicted date of delivery.
- Content rules
- FOR FUTURE USE Format : YYYYMMDD The Predicted Delivery Date information will only be provided if the customer’s Predicted Delivery Date Indicator equals “Y” and the Predicted Delivery Date value is not equal to the Expected Delivery Date value at the mailpiece level. For instance, if both the PDD and the SDD are 09/25/13, the PDD is not included in the file. However, if the SDD is 09/24/13 and the PDD is 09/25/13, then include the PDD in the file.] Field is populated with zeroes when PTR provides the event data before the manifest has been received.
- Max Length
- 8
- Page
- Publication 199, page 432
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 432
- Description
- Start the clock date.
- Content rules
- FOR FUTURE USE Format : YYYYMMDD The Start the Clock Date information will only be provided if the customer’s start the clock date indicator equals “Y” and the event is a start the clock event. Field is populated with zeroes when PTR provides the event data before the manifest has been received or the event was manually released from SDC Hold.
- Max Length
- 8
- Page
- Publication 199, page 432
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 432
- Description
- Indicates if the Start the Clock Date has been modified. Future Values: ‘Y’ ‘N’ space
- Content rules
- FOR FUTURE USE Value is always null
- Max Length
- 1
- Page
- Publication 199, page 432
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 432
- Description
- Barcode on container. This may be a valid IMpb, IM Container Barcode, IM Tray Barcode, or a Trailer Placard Barcode.
- Example
- ‘2220101271234567 89912 345’
- Content rules
- Taken from the Shipping Services File Detail Record. Provided only for scans on customer containers (O&D, 99M, and 24-digit IMCB) and the mailpieces within those containers. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 34
- Page
- Publication 199, page 433
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 433
- Description
- Describes type of container for Container ID 1.
- Example
- SK
- Content rules
- Taken from the Shipping Services File Detail Record. Provided only for scans on customer containers (O&D, 99M, and 24-digit IMCB) and the mailpieces within those containers. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 2
- Page
- Publication 199, page 433
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 433
- Description
- Barcode on container. This may be a valid IMpb, IM Container Barcode, IM Tray Barcode, or a Trailer Placard Barcode.
- Example
- ‘99N1234567890000 12345 678’
- Content rules
- Taken from the Shipping Services File Detail Record. Provided only for scans on customer containers (O&D, 99M, and 24-digit IMcb) and the mailpieces within those containers. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 34
- Page
- Publication 199, page 433
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 433
- Description
- Describes type of container for Container ID 2
- Example
- ‘PT’
- Content rules
- Taken from the Shipping Services File Detail Record. Provided only for scans on customer containers (O&D, 99M, and 24-digit IMcb) and the mailpieces within those containers. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 2
- Page
- Publication 199, page 433
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 433
- Description
- Barcode on container. This may be a valid IMpb, IM Container Barcode, IM Tray Barcode, or a Trailer Placard Barcode.
- Example
- ‘99T123456789123’
- Content rules
- Taken from the Shipping Services File Detail Record. Provided only for scans on customer containers (O&D, 99M, and 24-digit IMcb) and the mailpieces within those containers. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 34
- Page
- Publication 199, page 434
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 434
- Description
- Describes type of container for Container ID 3
- Example
- ‘BL’
- Content rules
- Taken from the Shipping Services File Detail Record. Provided only for scans on customer containers (O&D, 99M, and 24-digit IMcb) and the mailpieces within those containers. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 2
- Page
- Publication 199, page 434
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 434
- Description
- Foreign country postal code.
- Example
- ‘A0A9A0’
- Content rules
- Taken from the Shipping Services File Detail Record. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 11
- Page
- Publication 199, page 434
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 434
- Description
- Delivery address in the destination address or Standardized Address.
- Example
- ‘123 MAIN ST’
- Content rules
- Delivery Address is not extracted if event ZIP Code is different from manifest destination ZIP Code. Extracted for 01 (‘Delivered’), 43 (‘Picked Up’), and MA (‘Electronic Shipping Info Received’) scan events. Not extracted for 01 or 43 scan events if recalled/package intercept (‘44’), forwarded (’06’), refused (‘04’), or returned (‘09’) scan events exist for the mailpiece. Not extracted if 31 (‘Return to Sender / Not Picked Up’), 32 (‘Dead Mail / Disposed by Post Office’), or 33 (‘Dead Mail / Sent to Recovery Center’) scan events exist for the mailpiece. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 48
- Page
- Publication 199, page 435
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 435
- Description
- Customer’s internal reference number.
- Content rules
- Taken from the Shipping Services File Detail Record. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 30
- Page
- Publication 199, page 435
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 435
- Description
- Address correction service code and option.
- Content rules
- Taken from the Shipping Services File Detail Record. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 3
- Page
- Publication 199, page 435
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 435
- Description
- 6 or 9 digit Mailer ID or a 7 digit alphanumeric code.
- Content rules
- Taken from the Shipping Services File Detail Record. Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 9
- Page
- Publication 199, page 435
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 435
- Description
- Package status.
- Example
- eSOL
- Content rules
- Format: eSOL Field is populated with “eSOL” when electronic signature online has been received.
- Max Length
- 10
- Page
- Publication 199, page 436
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 436
- Description
- Identifier of facility.
- Content rules
- FOR FUTURE USE Value is always null
- Max Length
- 16
- Page
- Publication 199, page 436
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 436
- Description
- Type of Facility.
- Content rules
- FOR FUTURE USE Value is always null
- Max Length
- 20
- Page
- Publication 199, page 436
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 436
- Description
- GMT Time Format.
- Example
- 10:23:00
- Content rules
- Format: HH:MM:SS Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 8
- Page
- Publication 199, page 436
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 436
- Description
- GMT Offset.
- Content rules
- Field is populated with null when PTR provides the event data before the manifest has been received.
- Max Length
- 8
- Page
- Publication 199, page 436
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 436
- Description
- Latitude.
- Example
- +-xx.xxxxxxxx
- Content rules
- FOR FUTURE USE The GPS Latitude information will only be provided if the GPS Info Received Indicator equals “Y”. Defaults to null, when the information is not provided.
- Max Length
- 12
- Page
- Publication 199, page 436
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 436
- Description
- Longitude.
- Example
- +-xx.xxxxxxxx
- Content rules
- FOR FUTURE USE The GPS Longitude information will only be provided if the GPS Info Received Indicator equals “Y”. Defaults to null, when the information is not provided.
- Max Length
- 12
- Page
- Publication 199, page 436
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 436
- Description
- IMpb Compliance Report Code Possible Values: 16 – OK 17 – BQ 18 – MQ 19 – AQ 20 – PC 21 – KO 22 - K1 32—BQ, MQ 33- BQ, AQ 34 – MQ, AQ 50 – BQ, MQ, AQ
- Example
- 4
- Content rules
- - Field is populated for every MA, Shipping Partner, and/or physical Scan Event - Field is populated with spaces when not the “MA” event, Shipping Partner, and/or Physical Scan Event See Appendix J, Table 16
- Max Length
- 2
- Page
- Publication 199, page 437
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 437
- Description
- Indicates if the delivery address information is the original address as provided in the shipping services file, if the delivery address has been standardized or if the delivery address information is invalid address. ‘01’ – Delivery Address from Shipping Services File. ‘02’ – Delivery Address has been standardized. ‘03’ – Delivery Address is an invalid Address.
- Example
- 01
- Max Length
- 2
- Page
- Publication 199, page 437
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 437
- Description
- The date the “MA” event was created.
- Example
- 20130308
- Content rules
- FOR FUTURE USE YYYYMMDD If the Event Code = “MA” then posting date will be provide. If the Event Code is not equal to “MA” then this field will be null.
- Max Length
- 8
- Page
- Publication 199, page 437
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 437
- Description
- The time the “MA” event was created.
- Example
- 1315
- Content rules
- FOR FUTURE USE HHMM If the Event Code = “MA” then posting time will be provide. If the Event Code is not equal to “MA” then this field will be null.
- Max Length
- 4
- Page
- Publication 199, page 437
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 437
- Description
- Barcode Input Method
- Example
- S
- Content rules
- If the event comes from one of the following sources: IMDAS (handheld scanners), Surface Visibility or POS then filed will be populated. Field will be null if the source is not IMDAS, Surface Visibility or POS. C-Container Generated F-Firm Book G-System Generated K-Keyed M-Manually Entered S-Scanned T-System Generated U-POS entry 0-Scanned 1-Keyed 2-Manually Entered 4-Invalid Symbology R-Registered Mail Generated MA-Manifest Generated SP-Shipping Partner Generated
- Max Length
- 2
- Page
- Publication 199, page 438
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 438
- Description
- Start the Clock Time
- Content rules
- FOR FUTURE USE HHMMxx - where xx is AM if the time is 12:00:00 AM (Midnight) through 11:59:59AM and PM if the time is 12:00:00 PM (Noon) through 11:59:59 PM The Start the Clock Time information will only be provided if the customer’s start the clock time indicator equals “Y” and the event is a start the clock event. Field is populated with zeroes when PTR provides the event data before the manifest has been received or the event was manually released from SDC Hold.
- Max Length
- 6
- Page
- Publication 199, page 438
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 438
- Description
- Filler for future use.
- Content rules
- Value is always null.
- Max Length
- 71
- Page
- Publication 199, page 438
- Description
- Pipe delimiter
- Example
- |
- Content rules
- |
- Max Length
- 1
- Page
- Publication 199, page 438
- Description
- Carriage Return Line Feed
- Max Length
- 2
- Page
- Publication 199, page 438