TM_<MATCH_TYPE_ID>

For each match type, one Match Type view is created dynamically when the match type is successfully approved. This view contains all the transactions across all data sources within the match type.

Details

The view name follows the format TM_<MATCH_TYPE_ID> (for example, TM_POtoINV). It contains fixed, system-defined, attributes and data source attributes from all data sources within the match type.

Object type: VIEW

Columns

Name	Data Type	Length	Precision	Scale	Null Allowed	Comments
SOURCE	VARCHAR2	13			No	Text ID of the data source
TRANS_ID	NUMBER		18	0	No	Unique transaction ID
RECON_ID	NUMBER		18	0	Yes	Reconciliation ID. Primary key to TM_RECON.
MATCH_PROC_ID	NUMBER		18	0	Yes	Match process Id
JOB_ID	NUMBER		18	0	Yes	Import Job ID
MATCH_ID	NUMBER		18	0	Yes	Match Id
MATCH_STATUS_ENUM	NUMBER		2	0	Yes	Match status (same as TM_MATCH MATCH_STATUS_ENUM)
EXPORT_JOURNAL_STATUS	NUMBER		18	0	Yes	Export journal status: 0= closed, Null=open
EXPORT_JOURNAL_JOB_ID	NUMBER		18	0	Yes	Export Journal Job ID
IS_EDITED_TRANS	NUMBER		1	0	Yes	Is transaction edited: 1=Yes
<DATA_SOURCE_ATTRIBUTE_ID>_<first_letter_of_DATA_SOURCE_ATTRIBUTE_TYPE>						Other user-defined attributes in the Match Type view. From each data source, TM_DATA_SOURCE_ATTRIB.DATA_SOURCE_ATTRIB_ID is used to form the name of this column. Column name follows the format <DATA_SOURCE_ATTRIBUTE_ID>_<first_letter_of_DATA_SOURCE_ATTRIBUTE_TYPE>. See Table 5-1 below for details about the first letter used for the data source attribute type and its examples.

Table 6-1 Data Type Suffixes for Column Names Derived from Data Source Attribute IDs

Data Type	Suffix	Example
Text	_T	POS_memo_T
Date	_D	Pickup_date_D
Number	_N	Amount_N
Integer	_I	Invoice_I
List	_L	Store_L
Yes/No	_Y	Credit_Y