Resolve Transaction Management shows positive and negative transactions for the same transaction in DFWorks

Product Feature: Transaction Management

Operating System: Windows Server 2003/Windows Server 2008

Database: Oracle 9i/Oracle 11g

Configuration: Postage Accounting 


When a user goes into DFWorks Transaction Management and edits a transaction and saves it, they notice that the transaction is listed twice, a postive and a negative value transaction.


The problem is due to an inserter that reports mailpiece weight in grams (g) instead of ounces (oz). The "weight units" is stored in PAM_XDATA in the WEIGHTUNITS column. But there is no corresponding column in PAM_METER_HISTORY, which is used for Adjustment records. 

When the PAM Browse Transaction function tries to show rows from both tables and includes a "weight units" column in the report it has to fake the value for Adjustment records and always uses "oz". The difference in units between the original data and the Adjustment record prevents the rows from being combined together in the output. So you get one row with -1060 pieces and one with +1060 pieces instead of a single row with 0 pieces. 


This issue needs to be fixed in the DC model on the inserter or the MSM. The weight units needs to be changed from grams to ounces. This change should be performed by a PB service CSR.

UPDATED: April 20, 2017

Contact Us