DBA Data[Home] [Help] [Dependency Information]


TABLE: HR.HR_KI_INTEGRATIONS

Object Details
Object Name: HR_KI_INTEGRATIONS
Object Type: TABLE
Owner: HR
Subobject Name:
Status: VALID


This table lists the available integrations and trading partner transaction to be used per integration


Storage Details
Tablespace: TablespaceAPPS_TS_SEED
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
HR_KI_INTEGRATIONS_PK NORMAL UNIQUE TablespaceAPPS_TS_SEED ColumnINTEGRATION_ID
Columns
Name Datatype Length Mandatory Comments
INTEGRATION_ID NUMBER (15) Yes Integration identifier
INTEGRATION_KEY VARCHAR2 (100) Yes Internal developer name for Integration
PARTY_TYPE VARCHAR2 (240)
Type of trading partner,for example Supplier,Customer,Bank.
PARTY_NAME VARCHAR2 (360)
Name of party
PARTY_SITE_NAME VARCHAR2 (904)
Party site name
TRANSACTION_TYPE VARCHAR2 (100)
Product short name for the base Oracle Application associated with the transaction
TRANSACTION_SUBTYPE VARCHAR2 (100)
Code for a particular transaction within the application specified by the Transaction Type
STANDARD_CODE VARCHAR2 (30)
XML standard to be used for transaction
EXT_TRANS_TYPE VARCHAR2 (100)
External identifier for the XML message
EXT_TRANS_SUBTYPE VARCHAR2 (100)
Secondary external identifier for the XML message
TRANS_DIRECTION VARCHAR2 (20)
Indicates if the message is inbound or outbound
URL VARCHAR2 (2000)
URL for Integration to which user is redirected
SYNCHED VARCHAR2 (1) Yes Synched with ECX or SSO schema
EXT_APPLICATION_ID NUMBER (15)
External Application Identifier
APPLICATION_NAME VARCHAR2 (80)
External Application Name
APPLICATION_TYPE VARCHAR2 (80)
Application Type
APPLICATION_URL VARCHAR2 (1000)
Application URL
LOGOUT_URL VARCHAR2 (1000)
URL to logout
USER_FIELD VARCHAR2 (80)
Name of user field
PASSWORD_FIELD VARCHAR2 (80)
Name of password field
AUTHENTICATION_NEEDED VARCHAR2 (80)
Type of authentication
FIELD_NAME1 VARCHAR2 (80)
Name of field1
FIELD_VALUE1 VARCHAR2 (1000)
Value of field1
FIELD_NAME2 VARCHAR2 (80)
Name of field 2
FIELD_VALUE2 VARCHAR2 (1000)
Value of field 2
FIELD_NAME3 VARCHAR2 (80)
Name of field3
FIELD_VALUE3 VARCHAR2 (1000)
Value of field 3
FIELD_NAME4 VARCHAR2 (80)
Name of field4
FIELD_VALUE4 VARCHAR2 (1000)
Value of field4
FIELD_NAME5 VARCHAR2 (80)
Name of field5
FIELD_VALUE5 VARCHAR2 (1000)
Value of field5
FIELD_NAME6 VARCHAR2 (80)
Name of field6
FIELD_VALUE6 VARCHAR2 (1000)
Value of field 6
FIELD_NAME7 VARCHAR2 (80)
Name of field 7
FIELD_VALUE7 VARCHAR2 (1000)
Value of field 7
FIELD_NAME8 VARCHAR2 (80)
Name of field8
FIELD_VALUE8 VARCHAR2 (1000)
Value of field8
FIELD_NAME9 VARCHAR2 (80)
Name of field 9
FIELD_VALUE9 VARCHAR2 (1000)
Value of field9
LAST_UPDATE_DATE DATE
Yes Standard Who column
LAST_UPDATED_BY NUMBER (15) Yes Standard Who column
LAST_UPDATE_LOGIN NUMBER (15)
Standard Who column
CREATED_BY NUMBER (15) Yes Standard Who column
CREATION_DATE DATE
Yes Standard Who column
OBJECT_VERSION_NUMBER NUMBER (9) Yes This column is used for locking purposes. A way to implement Optimistic Locking
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT INTEGRATION_ID
,      INTEGRATION_KEY
,      PARTY_TYPE
,      PARTY_NAME
,      PARTY_SITE_NAME
,      TRANSACTION_TYPE
,      TRANSACTION_SUBTYPE
,      STANDARD_CODE
,      EXT_TRANS_TYPE
,      EXT_TRANS_SUBTYPE
,      TRANS_DIRECTION
,      URL
,      SYNCHED
,      EXT_APPLICATION_ID
,      APPLICATION_NAME
,      APPLICATION_TYPE
,      APPLICATION_URL
,      LOGOUT_URL
,      USER_FIELD
,      PASSWORD_FIELD
,      AUTHENTICATION_NEEDED
,      FIELD_NAME1
,      FIELD_VALUE1
,      FIELD_NAME2
,      FIELD_VALUE2
,      FIELD_NAME3
,      FIELD_VALUE3
,      FIELD_NAME4
,      FIELD_VALUE4
,      FIELD_NAME5
,      FIELD_VALUE5
,      FIELD_NAME6
,      FIELD_VALUE6
,      FIELD_NAME7
,      FIELD_VALUE7
,      FIELD_NAME8
,      FIELD_VALUE8
,      FIELD_NAME9
,      FIELD_VALUE9
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_LOGIN
,      CREATED_BY
,      CREATION_DATE
,      OBJECT_VERSION_NUMBER
FROM HR.HR_KI_INTEGRATIONS;

Dependencies

[top of page]

HR.HR_KI_INTEGRATIONS does not reference any database object

HR.HR_KI_INTEGRATIONS is referenced by following:

SchemaAPPS
SynonymHR_KI_INTEGRATIONS
TriggerHR_KI_INTEGRATIONS_WHO
SchemaPUBLIC
SynonymHR_KI_INTEGRATIONS