Common use of Transaction Tables Clause in Contracts

Transaction Tables. The "Transaction Frequency" column shall contain the anticipated normal frequency of this transaction. Anticipated values are "D" for daily, "W" for weekly, "S" for semi- monthly, "M" for monthly, "Q" for quarterly, "A" for annually, "R" for on-request, "O" for other. Multiple indicators may be used for a transaction that has multiple processing cycles. 7.3.1 The "Transaction Source" column shall contain the origination source for the transaction. For transactions that come from the State, this column is already filled in with "TennCare". For transactions from the Trading Partner, "TP" may be used. For transactions created by a third party for the Trading Partner, enter the third party's name. 7.3.2 The "Trading partner access person" column shall contain the name(s) of all individuals listed on the Security Forms below who shall access the given transaction. 7.3.3 The blank transaction rows on the request form are for proprietary file formats. Each production file sent between the State and the Trading Partner shall be represented on this form. Trading Partners that have multiple sources for a given transaction should include the file format once for each source.

Transaction Tables. The "Transaction Frequency" column shall contain the anticipated normal frequency of this transaction. Anticipated values are "D" for daily, "W" for weekly, "S" for semi- monthlysemimonthly, "M" for monthly, "Q" for quarterly, "A" for annually, "R" for on-request, "O" for other. Multiple indicators may be used for a transaction that has multiple processing cycles. 7.3.1 The "Transaction Source" column shall contain the origination source for the transaction. For transactions that come from the State, this column is already filled in with "TennCare". For transactions from the Trading Partner, "TP" may be used. For transactions created by a third party for the Trading Partner, enter the third party's name. 7.3.2 The "Trading partner access person" column shall contain the name(s) of all individuals listed on the Security Forms below who shall access the given transaction. 7.3.3 The blank transaction rows on the request form are for proprietary file formats. Each production file sent between the State and the Trading Partner shall be represented on this form. Trading Partners that have multiple sources for a given transaction should include the file format once for each source.