Defining the Output Files

Output File Types and Formats

1-PASS Prep (1PP) can generate multiple output files for different purposes. The field mapping conventions are the same as the input files. You can map the same field in the output fields as the input file but there are some additional fields that would be required. The Record_Type value defines the purpose of the file you are generating. The Header=’true’ parameter will add a header record to the export file with field names in it.

<Output_File File_Format='Delimited' Delimiter=',' Record_Type='USPS_Split' Header='true'>>
<File_Name>toUSPS.csv</File_Name>

File types

Piece – the output file is used to produce the commingle mail.

USPS_Split – this output file format is for use in a presort program.

Job_Start – this is job level info like counts.

Job_End – this is job level info obtained during the process.

Form Types

Forms/Job_Summary.form – allows you the ability to specify the file name of the summary report. It should be a .txt file.

The combination of these forms is used to create tray labels:

• One Up Tray Labels, when creating pallets

  • Forms/one_up_start.form

  • Forms/tray_tag.form

  • Forms/endpdf.form

• One Up Tray Labels, no pallets

  • Forms/one_up_start.form

  • Forms/ tray_tag _no_pallet.form

  • Forms/endpdf.form

• Two Up Tray Labels, when creating pallets

  • Forms/two_up_start.form

  • Forms/ tray_tag.form

  • Forms/endpdf.form

• Two Up Tray Labels, no pallets

  • Forms/two_up_start.form

  • Forms/ tray_tag _no_pallet.form

  • Forms/endpdf.form

The combination of these three forms are used to creates the pallet placards:

• Forms/pallet_placard_start.form

• Forms/pallet_placard.form

• Forms/endpdf.form

Specific Output Fields Available

Container_Destination – this is your commingler’s sort scheme which is very important. This will be populated even if you do not opt to create physical trays.

Container_Number – if you have opted to create trays, this is the tray number. You could print this on an OEL or Keyline on the mail piece to help production put the right pieces in the right trays if you wish.

Parent_Container_Destination – this is the pallet’s sort scheme, but it can be “Mixed” if there is not enough mail to create a minimum pallet with mail from a single sort scheme.

Parent_Container_Number - If you have palletization enabled, this is the pallet number. This is printed on the tray tags, but if you want, you could print this along with the container number in an OEL or Keyline to help production.

Parent_Container_Content_Line - this variable will have the pallet content for all pallet types. If 5-digit trays are being made there will be a 5D placeholder. A list of bins will follow. For example, 5D,20-24 would mean that the pallet contains 5-digit trays and that the pallet also contains trays for bins 20 through 24.

Piece_IMB_Text - this is the 25, 29 or 31 digit IMB.

Piece_IMB_Barcode - this is the “TADF” encoded version of the IMB that some printers require to print the barcode.

Tray_Break_Mark - this is what was defined as the end of tray break mark. It is usually printed in the address block of the mail piece to help the production staff put the right pieces in the right trays.

Pallet_Break_Mark - this is what was defined as the end of pallet break mark. It is usually printed in the address block of the mail piece to help the production staff put the right pieces in the right trays.

Output_Record_Number - in addition to providing your original sequence number, we have added this output record number to indicate the sort scheme order to keep pieces in their proper order, if it is necessary to break apart the output file for production purposes.

Summary File Output Fields

Some of the output files created by 1PP report information at a summarized level and cannot contain fields that only have data at the piece level. For example, the ‘Parent_Container’ record type in an output file will list pallets that were created. These are typically the “Parent” fields reported in that output file.

<Output_File File_Format='Delimited' Delimiter=',' Record_Type='Parent_Container' Header='true' >
      <File_Name>pallet_rpt.csv</File_Name>
     <Field Name='Parent_Container_Number' Column='1' />
      <Field Name='Parent_Container_Destination' Column='+1' />
      <Field Name='Parent_Container_Destination_Line' Column='+1' />
      <Field Name='Subcontainer_Count' Column='+1' />
      <Field Name='Parent_Container_Pieces' Column='+1' />
      <Field Name='Parent_Container_Weight' Column='+1' />
</Output_File>

<Output_File File_Format='Delimited' Delimiter=',' Record_Type='Container' Header='true' >
     <File_Name>tray_rpt.csv</File_Name>
     <Field Name='Container_Number' Column='+1' />
      <Field Name='Container_Destination' Column='+1' />
      <Field Name='Container_Destination_Line' Column='+1' />
      <Field Name='Container_Pieces' Column='+1' />
      <Field Name='Container_Weight' Column='+1' />
 </Output_File>

User Defined Header Fields

Carry forward from the section about User Defined Header Fields, any user defined header indicated in the Header_Name of the input file, must also be defined as a Header_Name in the output file. If not, 1PP will revert the headers back to the 1PP field names.

<Field Name="ZIP_Code" Header_Name="OUT_ZIP5"  Column = "+1" />
<Field Name="Plus4" Header_Name="OUT_ZIP4"  Column = "+1" />
<Field Name="Delivery_Point" Header_Name="OUT_DELIVERYPOINT"  Column = "+1" /> 

Continue Sample Parameter XML File