CMK_CONFIG_IMPORT

Details

Schema: FUSION
Object owner: CMK
Object type: TABLE
Tablespace: FUSION_TS_TX_DATA

Primary Key

Name	Columns
CMK_CONFIG_IMPORT_DOCS_PK	IMPORT_DOC_ID

Columns

Name	Datatype	Length	Precision	Not-null	Comments
IMPORT_DOC_ID	NUMBER		18	Yes	Primary Key of Configuration Import Documents.
IMPORT_PARTNER_ID	NUMBER		18		Foreign Key to Configuration Import Partners.
IMPORT_BATCH_ID	VARCHAR2	256			The batch in which the recored is imported
IMPORT_PARTNER_LINE_NUM	VARCHAR2	256			A unique number to identify the partner line. This is required because in the case of OSN B2B import it is possible that multiple TPs have the same value specified for the SENDER_ID (i.e. there may be multiple B2B TPs that have the same SENDER_ID value), and each of these reference a different site). Basically, there may be many records with the same TP value in this table, but different PARTNER KEY TYPE/ KEY1. We need something to uniquely identify a row in this table, and use this to cross reference docs associated with the TP. The OSN B2B import will have to generate this, and specify the same value in the CMK_CONFIG_IMPORT_DOC table. This is not required if the TP - Application Partner relationship is 1-1), so AR import will not need to specify this.
PARTNER_ID	VARCHAR2	100			Added to denormalize, to handle spreadsheet imports
ID_TYPE	VARCHAR2	100			Added to denormalize, to handle spreadsheet imports
MESSAGING_STANDARD	VARCHAR2	100			Will not have a valuer for AR and OSN, because Service Provider is identified
VERSION	VARCHAR2	100			Will not have a valuer for AR and OSN, because Service Provider is identified
MESSAGE_TYPE	VARCHAR2	256			Will not have a valuer for AR and OSN, because Service Provider is identified
MESSAGE_SUBTYPE	VARCHAR2	512			Will not have a valuer for AR and OSN, because Service Provider is identified
DOCUMENT_NAME	VARCHAR2	256			Will always have a value
DIRECTION	VARCHAR2	100			Derive and populate as necessary based on document name
BUSINESS_PROCESS	VARCHAR2	512			Populated by Import
IMPORT_DEL_METHOD_ID	NUMBER		18		Foreign Key to Configuration Import Delivery Method.
DELIVERY_METHOD_NAME	VARCHAR2	256			Added to denormalize, to handle spreadsheet imports
EXT_PARTNER_DOC_STATUS	VARCHAR2	100			Status of import e.g. SUCCESS, FAILED
EXT_PTNR_DOC_FAIL_REASON	VARCHAR2	1024			Reason for import failure - e.g. Partner Message already exists
APP_PARTNER_DOC_STATUS	VARCHAR2	100			Status of import e.g. SUCCESS, FAILED
APP_PTNR_DOC_FAIL_REASON	VARCHAR2	1024			Reason for import failure - e.g. Partner Message already exists
APPL_PARTNER_DOC_ID	NUMBER		18		Logical Foreign Key value of Application Partner Document when record process completes with success or existing application partner document.
EXTERNAL_PTNR_DOC_ID	NUMBER		18		Logical Foreign Key value of External Partner Document when record process completes with success or existing External partner document.
PARTNER_MESSAGE_ID	NUMBER		18		Logical Foreign Key value of External Partner Message when record process completes with success or existing External partner message.
CREATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who created the row.
CREATION_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the creation of the row.
LAST_UPDATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who last updated the row.
LAST_UPDATE_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the last update of the row.
LAST_UPDATE_LOGIN	VARCHAR2	32			Who column: indicates the session login associated to the user who last updated the row.
OBJECT_VERSION_NUMBER	NUMBER		9	Yes	Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.

Indexes

Index	Uniqueness	Tablespace	Columns
CMK_CONFIG_IMPORT_DOCS_U1	Unique	FUSION_TS_TX_IDX	IMPORT_DOC_ID