Release 24.1.2 – Notes – Version 3

The PostalOne! 24.1.2 Release was deployed August 15, 2012 to introduce software upgrades to the system.  Upgrades to the Service Performance system were deployed on August 22, 2012.
This is Version 3 of the notes and has been updated from Version 2; changes are identified in Appendix A.
These Release Notes provide the contents of this release and its effect on the following areas.

1.	Mailers (External)
1.1	Service Performance Changes (Deploys August 22, 2010)
1.1.1	General
1.1.1.1	Start-the-Clock
1.1.2	Microstrategy Reports
1.1.2.1	Container Visibility
1.1.3	FAST
1.1.3.1	CSA
1.1.3.2	Appointments
1.1.4	Mail.dat
1.2	Accounts
1.1.1	Balance & Fees
1.3	Mail & Transport
1.3.1	Electronic Data Exchange
1.3.1.1	Mail.dat
1.3.1.1.1	Mail.dat Processing
1.3.1.1.2	Mail.dat Postage Statements
1.3.1.2	Mail.XML
1.3.1.2.1	Mail.XML Processing
1.3.1.3	Test Environment for Mailers (TEM)
1.3.2	Dashboard
1.3.2.1	Job Detail
1.3.2.1.1	eDocumentation Reports
1.4	Track & Report
1.4.1	Full-Service Reports
1.4.1.1	Full-service Data Quality reports
1.5	Manage Electronic Verification Activity (eVS)
1.5.1	Processing
1.6	Manage Electronic Return Activity (PRS)
1.6.1	Samples
Appendix A – Changes to Version 1

1.	
Mailers (External)
PostalOne! Release 24.1.2 was deployed on August 15, 2010 to introduce software upgrades to the system.  Those upgrades included changes to Mail.dat postage statements and qualification reports for all container types and correct unit weights, surcharge application to Standard Mail parcel mailing, and single piece files with multiple segments.  Changes were made for performance improvements within the system.
Changes to Service Performance will be deployed on August 22, 2010.  The release notes related to those changes are identified in section 1.1 of this document.
The following items were included in PostalOne! Release 24.1.2 and are of interest to external users of PostalOne!
1.1	Service Performance Changes (Deploys August 22, 2010)
1.1.1	General
The system has been updated to allow a job to only be imported once into the system. Previously, a defect sometimes duplicated jobs and/or pieces if connection, database, or system issues prevented the initial creation of records from completing successfully. 61178
The system received some minor performance improvements that should display data updates earlier as automatically-scheduled backend tasks complete faster. 62087
1.1.1.1	Start-the-Clock
Start-the-clock calculations have been updated to include the date as well as the time when determining lateness of container induction scans. Previously, a defect marked containers as late incorrectly for a small number of scenarios. 61397
1.1.2	Microstrategy Reports
When a mailing has been reversed and resubmitted, the resulting information in Microstrategy reports now displays only those errors applicable to the resubmission. Previously, a defect sometimes failed to remove the errors associated with the original submission and both sets of errors displayed on reports. This impacts all users with access to Microstrategy reports. 61018 
The summary count on Microstrategy Mail Quality Reports is now updated based on daily error status as errors are activated and deactivated during post-eDocumentation processing for Facility Access Shipment Tracking (FAST) appointments and Customer Supplier Agreement (CSA) verifications. Previously, these counts did not update daily, causing summary counts to be incorrect. This impacts all users with access to Microstrategy reports. 60959
1.1.2.1	Container Visibility
Container visibility information now includes container scan information for mailings claiming a Sectional Center Facility (SCF) as the origin entry point. This repairs a defect that prevented some container scan information from being associated with the origin facility of the mailing, resulting in missing Full-Service Container Visibility feedback for mailings processed at such facilities. 61010
1.1.3	FAST
1.1.3.1	CSA
Container errors are no longer generated for mailers when CSA data matches eDocumentation data. Previously, error records were not updated to inactive status when CSA and eDocumentation data matched. 61176
1.1.3.2	Appointments
Appointment validation now uses the FAST Recurring Appointment ID field to determine if a mailer-transported appointment matches an existing recurring appointment from the .CSM Reservation Number field. Previously, one-time appointments were sometimes erroneously linked to CSA recurring appointments. 61177
1.1.4	Mail.dat
For mailings with data submitted using Mail.dat files, validation now compares the Container Destination ZIP Code from the .CSM file with the CSA Label To field, and then the CSA Container Destination ZIP Code. Previously, the CSA Label To field was not part of the matching process, causing mailings missing a ZIP Code in the CSA Container Destination ZIP Code field to not be associated with the appropriate .CSM data. 61219
1.2	Accounts
1.1.1	Balance & Fees
This release implemented minor performance improvements for permit balance inquiries and reporting. 62134 
1.3	Mail & Transport
1.3.1	Electronic Data Exchange
Users participating in electronic data exchange with the US Postal Service should reference the Postal Service Mail.dat Technical Specification and Postal Service Mail.XML Technical Specification for Postage Payment and Reporting (eDoc).
1.3.1.1	Mail.dat
The changes in the following sections apply to customers participating in electronic data exchange using Mail.dat as a means of electronic submission: 
1.3.1.1.1	Mail.dat Processing
a.	General
For Standard Mail® parcel mailings submitted using Mail.dat files, the PostalOne! system now correctly applies the non-barcoded surcharge only when applicable. Previously, some Standard Mail parcel mailings received the surcharge in error. 60963
Mailers can now submit Mail.dat files with multiple segments that claim Rate Category “S” (Single Piece) and piece weights of .8125 or greater. Previously, validation failed all such files. For more information on Mail.dat, see the Postal Service Mail.dat Technical Specification. 61427
b.	Uploads
Mail.dat processing also received a performance enhancement that allows the system to process large numbers of MPU / Component Relationship (.MCR) files in a single job. Previously, sending a Parcel Services Bound Printed Matter job with more than 200,000 MCR records in a single job caused significant performance degradation.  62959
c.	Validations
Postage statements and qualification reports generated from Mail.dat® files now include information for all container types. Previously, containers submitted using Container Summary (.CSM) files were not included in container counts if the container types were any of the following: A, B, C, D, G, H, R, U, V, W, or Z. 59930
1.3.1.1.2	Mail.dat Postage Statements
Known Issue:	Postage statements submitted using Mail.dat® files now display the correct unit weight on the postage statement. Previously, a defect displayed the wrong unit weight for all non-Periodicals postage statements submitted using Mail.dat files, although postage calculations were correct and used accurate weights. 60214
Resolution:	This issue will be corrected in Release 24.1.3, scheduled for deployment on September 19, 2010.

1.3.1.2	Mail.XML
The changes in the following sections apply to customers participating in electronic data exchange using Mail.XML as a means of electronic submission: 
1.3.1.2.1	Mail.XML Processing
a.	General
This release introduced Mail.XML performance improvements to allow mailers to request or “pull” eDocumentation data quality information in a timely manner; previously, data was not immediately available after submission for mailers to pull.  62126
1.3.1.3	Test Environment for Mailers (TEM)
The TEM environment now automatically includes fees paid in Production. Previously, this feature was disabled as a defect prevented fees from populating if special characters existed in fields close to the field size limit. This change impacts all users in the Test Environment for Mailers (TEM). 59527
1.3.2	Dashboard
1.3.2.1	Job Detail
1.3.2.1.1	eDocumentation Reports
Postage statements and qualification reports generated from Mail.dat® files now include information for all container types. Previously, containers submitted using Container Summary (.CSM) files were not included in container counts if the container types were any of the following: A, B, C, D, G, H, R, U, V, W, or Z. 59930
1.4	Track & Report
1.4.1	Full-Service Reports
1.4.1.1	Full-service Data Quality reports
This release introduced Mail.XML performance improvements to allow mailers to request or “pull” eDocumentation data quality information in a timely manner; previously, data was not immediately available after submission for mailers to pull.  62126
1.5	Manage Electronic Verification Activity (eVS)
1.5.1	Processing
This release implemented minor performance improvements for electronic Verification System (eVS) processing and permit balance inquiries and reporting. 62134
1.6	Manage Electronic Return Activity (PRS)
1.6.1	Samples
Postage Adjustment Factor (PAF) calculations now reconcile any Parcel Return Service (PRS) samples received late in the appropriate month. Previously, if mailers used an “exception” label to account for pieces with labels that could not be scanned, the pieces would be assigned to the wrong month and required manual reconciliation. This change only impacts users submitting or processing PRS mailings. 60972

NOTE:  If you have any questions or need any assistance regarding the PostalOne!® system please contact our PostalOne!® Help Desk at 1 – 800 – 522 – 9085.
Appendix A – Changes to Version 1

The following table represents the changes from the previous version of release notes for PostalOne! Release 24.1.2. 

Section	Change Type	Change	
1.3.1.1.2
Mail.dat Postage Statement	Remove	Removed the following release note; the fix was not deployed:
Postage statements submitted using Mail.dat® files now display the correct unit weight on the postage statement. Previously, a defect displayed the wrong unit weight for all non-Periodicals postage statements submitted using Mail.dat files, although postage calculations were correct and used accurate weights. 60214
	
1.3.1.1.2
Mail.dat Postage Statement	Add	Known Issue added as a result of ETR 60214 not deployed:
Known Issue:	Postage statements submitted using Mail.dat® files now display the correct unit weight on the postage statement. Previously, a defect displayed the wrong unit weight for all non-Periodicals postage statements submitted using Mail.dat files, although postage calculations were correct and used accurate weights. 60214
Resolution:	This issue will be corrected in Release 24.1.3 as ETR 64386, scheduled for deployment on September 19, 2010.