VERIFIED SOLUTION i

Why are the CPT-1110 and MPU-1111 getting populated with a 5 using MailStream Plus 8.3.0 or later in a Periodical job

Product Affected:  MailStream Plus™

Issue

Why are the CPT-1110 and MPU-1111 getting populated with a 5 using MailStream Plus™ (MSP) 8.3.0 in my Periodical job?

Mail.dat version 15-1 :
  • CPT-1110   Component - Class The Postal Class of this Mail Piece Unit within Mail.dat.
  • MPU-1111   Mail Piece Unit - Class The Postal Class of this Mail Piece Unit within Mail.dat.
  • 1 = First Class 2 = Periodicals 3 = Std Mail
  • 4 = Pkg Services 5 = Per Pending 9 = Other 
 
When importing the mail.dat files into PostalOne!,  the job is getting an error because the files have a '5' in these values (CPT-1110  and MPU-1111), but the mailing is not Periodicals Pending presort.

Cause

In MSP 8.2.0, CPT-1110 and MPU-1111 were part of the subkeyword  PMTPM#.

Starting in MSP 8.2.1, these 2 field codes were removed from being listed values in the subkeyword PMTPM#.  MSP now only populates MPA-1103, but it *affects* the value that will be posted into CPT-1110 and MPU-1111.
 
The presence of this parameter was causing the problem:
RP INF                     PMTPM# 5555
*...+....1....+....2....+....3....+....4

 

Resolution

UPDATED: March 19, 2019
When testing a ML TYP 2 F job without the RP INF with PMTPM# the value was 2 on the CPT-1110 and MPU-1111 field codes. 
Once the RP INF with PMTPM# was added MSP changed these to a 5.
 
The MSP documentation for the subkeyword PMTPM# says:
  • Not available for Periodicals except for Periodicals Pending. Numeric format. This field must be left justified (with no zero-padding). 

Resolution :  The RP INF or PA INF parameter with the subkeyword PMTPM# is not allowed to be used with MSP Periodical mailings that are not Periodical Pending.  Because the use of PMTPM# in a Periodicals mailing will automatically trigger a '5' to be put into CPT-1110 & MPU-1111.