CMK_CONFIG_IMPORT_PARTNERS
This table stores Associated Trading Partner with Application Partner details.
Details
-
Schema: FUSION
-
Object owner: CMK
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Primary Key
Name | Columns |
---|---|
CMK_CONFIG_IMP_PARTNER_PK |
IMPORT_PARTNER_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
IMPORT_PARTNER_ID | NUMBER | 18 | Yes | Primary key of the configuration import partner. | |
USER_DEFINED | VARCHAR2 | 1 | Flag to indicate whether the service provider was created by the user or not. | ||
IMPORT_BATCH_ID | VARCHAR2 | 256 | The Batch in which a particular record is uploaded | ||
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. | ||
IMPORT_TYPE | VARCHAR2 | 100 | Import Type can be b2bimport or osn import. this column signifies that | ||
PARTNER_ID | VARCHAR2 | 100 | Value will always be Name if import type is B2B import, always be B2BSITECODE if import type is OSN Migration.. Trading Partner Identification Imported by B2B or OSN or AR Import. | ||
ID_TYPE | VARCHAR2 | 100 | If import type is B2B import, value will always be "Name", in case of OSN, will always be B2BSiteCode. Trading Partner Identification Type imported by B2B Import or OSN Import of AR Import. | ||
OSN_PARTNER_ID | VARCHAR2 | 256 | OSN_PARTNER_ID | ||
OSN_PARTNER_ID_TYPE | VARCHAR2 | 256 | OSN_PARTNER_ID_TYPE | ||
SERVICE_PROVIDER_NAME | VARCHAR2 | 256 | Will always be null for B2B import, will always be OracleSuplierNetwork for OSN Migration | ||
PROCESSED_STATUS | VARCHAR2 | 100 | Status of processed record imported by the user | ||
EXT_PARTNER_STATUS | VARCHAR2 | 100 | Status of import e.g. SUCCESS, FAILED. | ||
EXT_PARTNER_FAIL_REASON | VARCHAR2 | 3072 | Reason for import failure - e.g. Partner already exists. | ||
PARTNER_KEY_TYPE | VARCHAR2 | 100 | Set by import based on the document | ||
PARTNER_KEY1 | VARCHAR2 | 256 | Set for OSN Migration and Customer Account Setup when record is inserted (applicable keys). Set by user if import type is B2B Import. | ||
PARTNER_KEY2 | VARCHAR2 | 256 | Set for OSN Migration and Customer Account Setup when record is inserted (applicable keys). Set by user if import type is B2B Import. | ||
PARTNER_KEY3 | VARCHAR2 | 512 | Set for OSN Migration and Customer Account Setup when record is inserted (applicable keys). Set by user if import type is B2B Import. | ||
PARTNER_KEY4 | VARCHAR2 | 512 | Set for OSN Migration and Customer Account Setup when record is inserted (applicable keys). Set by user if import type is B2B Import. | ||
PARTNER_KEY5 | VARCHAR2 | 512 | Set for OSN Migration and Customer Account Setup when record is inserted (applicable keys). Set by user if import type is B2B Import. | ||
PARTNER_KEY6 | VARCHAR2 | 256 | Set for OSN Migration and Customer Account Setup when record is inserted (applicable keys). Set by user if import type is B2B Import. | ||
APP_PARTNER_STATUS | VARCHAR2 | 100 | Status of CMK import e.g. SUCCESS, FAILED | ||
APP_PARTNER_FAIL_REASON | VARCHAR2 | 3072 | Reason for CMK import failure - e.g. Partner already exists | ||
APPL_PARTNER_ID | NUMBER | 18 | Logical Foreign Key value of Application Partner when record process completes with success or existing application partner. | ||
EXTERNAL_PARTNER_ID | NUMBER | 18 | Logical Foreign Key value of External Partner when record process completes with success or existing external partner. | ||
IMPORT_DATETIME | TIMESTAMP | Import Data Time stores timestamp of import record. | |||
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_IMP_PARTNERS_N1 | Non Unique | FUSION_TS_TX_IDX | IMPORT_BATCH_ID, PARTNER_ID, ID_TYPE, SERVICE_PROVIDER_NAME, PARTNER_KEY_TYPE, PARTNER_KEY1 |
CMK_CONFIG_IMP_PARTNERS_U1 | Unique | FUSION_TS_TX_IDX | IMPORT_PARTNER_ID |