VERIFIED SOLUTION i

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

Product affected: MailStream Plus™, all versions, all platforms

Issue

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

Mail.dat version 19-1 :
CPT-1110   Component - Class
The Postal Class of this Mail Piece Unit within Mail.dat.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
X = Alt Del
P = Pub Rate

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

Use of the PA INF or RP INF with the subkeyword PMTPM# only directly populates MPA-1103 (Permit Number), 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# 4321
*...+....1....+....2....+....3....+....4

Resolution

UPDATED: August 21, 2019
When testing a ML TYP 2 F job without the PA/ INF or 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.