Tran Type Publication

Transactions can be kept in history records for a varying amount of time, depending on product and transaction type (such as “start”, “stop”, and “expire”). Product and transaction type also determine how many days transaction activity messages (such as “New Start”) should print on bundle tops. Naviga initially sets up all transaction types with 999 history retention days, 0 message print days (which means the transaction will print only on the first day), and a “*” in Product.

The table below lists all of the transaction types in Circulation.

TranType	TranType	TranType	TranType
1stInvoice	AutoRenew	GraceExport	Refund
1stRenewal	AvailRefund	GraceOwed	RefundExprt
2ndInvoice	BankPreNote	GracePaid	RefundWoff
2ndRenewal	BillingChg*	GraceWOff	RefundXfr
3rdInvoice	BonusDay*	MarketTerm	Renewal
3rdRenewal	CollectInvc	Message	Reroute*
4thInvoice	CollectXprt	MoveIn*	Restart*
4thRenewal	ComboChg	MoveOut*	ReverseDraw
5thInvoice	Complaint*	New Transfer	Shortage
5thRenewal	DayPass	Note	Start*
6thInvoice	DayPassUsage	NSFPayment*	StatusCard
6thRenewal	DelivSched*	Payment*	Stop*
7thInvoice	DrawChange	Placement	Suspend
7th Renewal	EndGrace	PrevDeliv	TempAddrEnd*
8thInvoice	EndGraceChg	PymtCancel*	TempAddress*
8thRenewal	Expire	PymtDecline	TransferIn
9thInvoice	ExpireAlert*	RateChange	TransferOut
9thRenewal	ExpireChnge	Rebill	Unsuspend
AutoNotice	GraceAccrual

* Transactions that apply to MESSAGE PRINT DAYS (i.e., you may enter the number of days that the transaction should print on the bundle top).

Note:

• History retention days for the Payment transaction type should remain at 999.

• You should never delete any of the Tran Type Publication records. This will impact Customer Service and Route Service transactions.

To modify a transaction type:

• Select Tran Type Publication from the Products menu to display the Tran Type Publication screen.

• Click the Modify icon () and enter information in the fields described in the table below (if you are specifying retention or message days for a specific publication, select Add).

Field	Type	What to enter
TRANSACTION TYPE	predefined	Enter the transaction type, such as “complaint”. You can press F2 to display valid transaction types.
PRODUCT	setup	Enter the product with which this transaction type is being defined, or type an asterisk (*) to indicate that all products have the same parameters.
HISTORY RETENTION DAYS	integer (9)	Enter the number of days transactions for this transaction type should be retained in history for reporting purposes. The default value is 999 days.
MESSAGE PRINT DAYS	integer (9)	Enter the number of days including the initial message date that transactions should be printed on the bundle top. For example, if you wanted a “start” message to display three times—on the day of the new start and two days after—you would enter “3” in this field. Messages that have already appeared on the bundle top on previous days will be printed under a “****Reminder****” heading.
SHOW ON WEB WEB DESCRIPTION ENTER ON WEB	yes/no open (30) yes/no	These fields are used by iServices Subscriber (a companion application). Indicate whether transactions of this transaction type should display in iServices always, never or based on an individual transaction’s reason code. If the transaction will be displayed, specify the label that should display for the transaction on the web. You can also control whether subscribers are allowed to enter certain transactions in iServices, such as complaints.
VALIDATE FOR DID NOT ORDER STOP	yes/no	This field enables payments, temp stops, and complaints to be validated against “did not order” stops. The validation process will locate payments, temp stops and complaints associated with the subscription within the start and perm stop date range. Warning messages will be generated during transactions processing if these transactions are found.

• Click OK to save your changes.