Blank.
CSA Agreement ID 639 – 648 10 A/N CSM-1187 Agreement Number generated by the USPS
Presort Labeling List Effective Date 649 – 656 8* N CSM-1189 YYYYMMDD (cannot be all zeros)
For containers created with a CSA, use CSA effective date.
“00010101” will be the “non-value” when date is not applicable.
Last Used Labeling List Effective Date 657 – 664 8* N CSM-1190 YYYYMMDD (cannot be all zeros)
For containers created with a CSA, use CSA effective date.
“00010101” will be the “non-value” when date is not applicable. For the initial presort, this will have the same value as Presort Labeling List Effective Date field.
Presort City-State Publication Date 665 – 672 8* N CSM-1191 YYYYMMDD (cannot be all zeros)
Use “01” for day if only Year and Month provided. “00010101” will be the “non-value” when date is not applicable.
Last Used City-State Publication Date 673 – 680 8* N CSM-1192 YYYYMMDD (cannot be all zeros)
Use “01” for day if only Year and Month provided. “00010101” will be the “non-value” when the date is not applicable. For the initial presort, this will have the same value as Presort City-State Publication Date.
Presort Zone Chart Matrix Publication Date 681 – 688 8* N CSM-1193 YYYYMMDD (cannot be all zeros)
“00010101” will be the “non-value” when date is not applicable.
Last Used Zone Chart Matrix Publication Date 689 – 696 8* N CSM-1194 YYYYMMDD (cannot be all zeros) “00010101” will be the “non-value” when the date is not applicable. For the initial presort, this will have the same value as Presort Zone Chart Matrix Publication Date.
Last Used Mail Direction Publication Date 697 – 704 8* N CSM-1195 YYYYMMDD (cannot be all zeros) “00010101” will be the “non-value” when the date is not applicable.
CONTAINER SUMMARY RECORD, continued
Field Name Position Length Data
Type
Field Code Description
Supplemental Physical Container ID 705 – 710 6 N CSM-1196 (use CSM-1006 of Physical Parent record)
This field can be used in two ways, both of which are optional. The first definition is meant for use in logical tray scenarios or overflow scenarios, where the field can be used to describe the relationship between a physical tray and its physical parent container. The second definition is meant for use with logical bundle-based mailings, where the field can be used to describe the relationship between logical trays when bundles of mail are relocated. These two models of usage do not conflict with each other because the first definition can only be used for a physical or sibling tray, and the second definition can only be used for a logical tray. If neither of these usage models applies for your mailing, the field should remain blank in your CSM records.
Definition 1:
(For linkage between physical trays and physical parent containers, use CSM-1006 of the physical parent container on which the physical tray resides)
Container ID of the Physical Parent Container in which this physical tray or sibling tray resides, if such relationship exists.
Blank if no such relationship.
This is an optional field and can be used to associate either a physical or a sibling handling unit to the actual container that it is on but only under specific
circumstances:
When the container it is on is a sibling to either a logical or physical master container.
When the container that it is on is a physical container that has at least one sibling (as in an overflow scenario).
The child-to-parent container relationship established through the use of the Parent Container Reference ID must also be used to link the master handling unit (not the sibling) to a parent. It is only through that relationship that pieces can be
associated to logical container groups or physical containers with siblings.
Note, when used, this describes which handling units are on which containers and does not provide any indication of which mail pieces are in which handling units or on which containers.
Definition 2:
This definition is for FCM MLOCR bundle-based preparation.
(For linkage between logical trays when using bundle-based mail and some mail bundles are relocated between two different logical trays, use CSM-1106 of the logical tray into which mail is being relocated)
CONTAINER SUMMARY RECORD, continued
Field Name Position Length Data
Type
Field Code Description
Container ID of another logical tray into which some mail from this logical tray has been relocated, if such relationship exists.
Blank if no such relationship.
This is an optional field and can be used to associate a logical tray to another logical tray when some mail has been relocated within a bundle-based mailing. The purpose is to identify such related trays in order to assist with the verification of a mailing.
Note, when used, this describes relocation for an indeterminate quantity of mail, and does not provide any indication of which mail pieces are relocated into the other logical tray. Unless the original logical tray record ceases to exist because all of its mail is relocated into a different logical tray, the tallying for the quantity of mail will remain with the original logical tray, and relocated mail does not add to the accumulated amount in the target logical tray for the following fields:
Number of Copies (CSM-1120)
Number of Pieces (CSM-1121)
Total Weight (CSM-1122)
Container Gross Weight (CSM-1137)
Note also that this means a target logical tray which receives such relocations may possibly have values of zero for the aforementioned fields, if it exists solely for the purpose of receiving such relocations.
Accept Misshipped 711 - 711 1 A/N CSM-1188 Y= Yes Blank=No; USPS field for eInduction misshipped processing support.
eInduction Misshipped Container Payer CRID
712 – 723 12 A/N CSM-1197 USPS ID, when provided - precedes any eInduction invoicing default rules for other eInduction USPS Ids, such as
Carrier/Transporter, eDoc Submitter
CSM Record Status 724 – 724 1* A/N CSM-2000 O, D, I, U
O = Original, D = Delete, I = Insert, U = Update
Reserve 725 – 767 43 A/N CSM-1134
Closing Character 768 - 768 1* CSM-9999 Must be "#" sign