Configuring Siebel eBusiness Applications > Configuring EIM Interfaces >
EIM Object Specifications
The topics in this section detail objects specifications that EIM uses. EIM Interface Table EIM Interface Table Columns Generic EIM Interface Table Columns for EIM Processing EIM Interface Table Columns for Processing a Mapping to a Specified Table EIM Interface Table Columns for Foreign Key Processing EIM Interface Table Columns for Foreign Keys EIM Interface Table Column for Each Attribute on the Target Table EIM Table Mapping Objects Based on the Target Table Attribute Mapping objects for Each EIM Interface Column Generated Foreign Key Mapping for Each Foreign Key Column on the Target Table Foreign Key Mapping Columns for each Foreign Key Mapping object For detailed information about EIM, see Siebel Enterprise Integration Manager Administration Guide. EIM Interface Table
EIM interface table object specifications are summarized in Table 18.
Table 18. EIM Interface Table Object Specifications
|
|
Target Table |
Selected by the developer |
EIM Delete Proc Column |
T_DELETED_ROW_ID |
EIM Export Proc Column |
T_EXPORTED_ROW_ID |
EIM Merge Proc Column |
T_MERGED_ROW_ID |
EIM Interface Table Columns
EIM Interface Table Column specifications are covered in Table 19.
Table 19. System Columns on the EIM Interface Table
|
|
|
|
|
CONFLICT_ID |
Varchar |
15 |
System |
FALSE |
CREATED |
Date Time |
7 |
System |
FALSE |
CREATED_BY |
Varchar |
15 |
System |
FALSE |
IF_ROW_BATCH_NUM |
Number |
22 |
System |
FALSE |
IF_ROW_MERGE_ID |
Varchar |
15 |
System |
FALSE |
IF_ROW_STAT |
Varchar |
30 |
System |
FALSE |
IF_ROW_STAT_NUM |
Number |
22 |
System |
FALSE |
LAST_UPD |
Date Time |
7 |
System |
FALSE |
LAST_UPD_BY |
Varchar |
15 |
System |
FALSE |
MODIFICATION_NUM |
Number |
22 |
System |
FALSE |
ROW_ID |
Varchar |
15 |
System |
FALSE |
Generic EIM Interface Table Columns for EIM Processing
For each EIM Table Interface, the columns shown in Table 20 are created to facilitate processing. You cannot change the values of these columns.
Table 20. Generic EIM Interface Table Columns for EIM Processing
|
|
|
|
|
|
T_DELETED_ROW_ID |
Varchar |
15 |
Data (Private) |
Deleted ROW_ID from base table |
TRUE |
T_EXPORTED_ROW_ID |
Varchar |
15 |
Data (Private) |
Exported ROW_ID from target table |
TRUE |
T_MERGED_ROW_ID |
Varchar |
15 |
Data (Private) |
Merged into ROW_ID from target table |
TRUE |
EIM Interface Table Columns for Processing a Mapping to a Specified Table
There are five of these columns for each EIM Table Mapping object, with the properties listed in Table 21.
Table 21. EIM Interface Table Columns for Processing a Particular Mapping
|
|
Name |
Derived from the name of the target table: "T_"+ [EIM Table Mapping Name without the "CX_"]+ "_"+ [Process-specific suffix] |
Physical Type |
Depends on the process to which the column is related |
Length |
Depends on the process to which the column is related |
Type |
Depends on the process to which the column is related |
User Name |
Name of the EIM Table Mapping object for which the column is being created |
EIM Processing Column |
TRUE |
For example, if the target table selected by the user is CX_SEC_LEV, an EIM Table Mapping object is created. The following four column objects are generated, with the corresponding default properties (Table 22):
Table 22. EIM Interface Table Columns for Processing a Mapping to CX_SEC_LEV
|
|
|
|
|
|
T_SEC_LEV_EXS |
Character |
1 |
IFMGR: Exists |
CX_SEC_LEV |
TRUE |
T_SEC_LEV_RID |
Varchar |
15 |
IFMGR: ROW_ID |
CX_SEC_LEV |
TRUE |
T_SEC_LEV_STA |
Number |
22 |
IFMGR: Status |
CX_SEC_LEV |
TRUE |
T_SEC_LEV_UNQ |
Character |
1 |
IFMGR: Unique |
CX_SEC_LEV |
TRUE |
EIM Interface Table Columns for Foreign Key Processing
A column is created for each foreign key on the relevant EIM Table Mapping object (that is, the target table). These columns have the properties listed in Table 23.
Table 23. EIM Interface Table Columns for Foreign Key Processing
|
|
Name |
Derived from the target table name and the corresponding foreign key column on the target table in the following format: [Target Table name (with the "CX" prefix replaced by "T")]+[Target table foreign key column] |
Type |
Set to IFMGR: Fkey |
Physical Type |
Physical type of foreign key column on Target Table (typically Varchar) |
Length |
Length of foreign key column on Target Table (typically 15) |
User Name |
[Target Table (or EIM Table Mapping) name]+"."+[Foreign key column name] |
For example, if CX_SEC_LEV contains foreign key columns called OPTY_ID and ACCNT_ID to the S_OPTY and S_ORG_EXT tables, respectively, the following EIM Table Columns are generated as shown in Table 24.
Table 24. EIM Interface Table Columns for Processing Foreign Keys in CX_SEC_LEV
|
|
|
|
|
T_SEC_LEV_OPTY_ID |
Varchar |
15 |
IFMGR: Fkey |
CX_SEC_LEV.OPTY_ID |
T_SEC_LEV_ACCNT_ID |
Varchar |
15 |
IFMGR: Fkey |
CX_SEC_LEV.ACCNT_ID |
EIM Interface Table Columns for Foreign Keys
A separate foreign key column will be created for each U1 user key column on the foreign key tables. The columns have the following properties listed in Table 25.
Table 25. EIM Interface Table Columns for Foreign Keys
|
|
Name |
[First four letters of foreign key table name without the "S_" prefix, trimmed to remove any trailing "_"characters] + "_"+[foreign key column name on target table] |
Physical Type |
Physical type of the user key column on the target table (typically Varchar) |
Length |
Length of these columns will correspond to the length of user key columns upon which they are based (typically 15) |
Type |
Data (Public) |
Continuing with the CX_SEC_LEV example the columns would have the properties listed in Table 26.
Table 26. EIM Interface Table Columns for CX_SEC_LEV Foreign Keys
|
|
|
OPTY_BU_ID |
Varchar |
Data (Public) |
OPTY_NAME |
Varchar |
Data (Public) |
OPTY_PR_DEPT_OU_ID |
Varchar |
Data (Public) |
ORG_BU_ID |
Varchar |
Data (Public) |
ORG_NAME |
Varchar |
Data (Public) |
ORG_LOC |
Varchar |
Data (Public) |
NOTE: Depending on the base column type, corresponding EIM columns are generated accordingly.
EIM Interface Table Column for Each Attribute on the Target Table
Attribute columns on the target table are those of type Data (Public) that have a null Foreign Key Table property. These EIM interface table columns will have the properties listed in Table 27.
Table 27. EIM Interface Table Columns for Each Attribute on the Target Table
|
|
Name |
[Prefix entered—for example, CON or ACCNT]+"_"+[name of the corresponding column in the target table] |
Physical Type |
Data (Public) |
Length |
Length of corresponding column in the target table |
User Name |
Name of corresponding column in the target table |
For example, if you enter a prefix of SECL and have the following attribute columns in CX_SEC_LEV: NAME (Varchar 100), DESC_TEXT (Varchar 250), and AUTO_UPDATE (Char 1), the following EIM interface table columns are generated as shown in Table 28.
Table 28. EIM Interface Table Columns for Each Attribute on CX_SEC_LEV
|
|
|
|
|
SECL_NAME |
Varchar |
100 |
Data (Public) |
Security Level Name |
SECL_DESC_TEXT |
Varchar |
250 |
Data (Public) |
Security Level Description |
SECL_AUTO_UPDATE |
Char |
1 |
Data (Public) |
Auto Update Flag |
EIM Table Mapping Objects Based on the Target Table
The name and destination columns will be set to the name of the target table. The processing column properties will correspond to those that have been automatically generated. For examples, see Table 29.
Table 29. EIM Table Mapping Objects Based on the Target Table
|
|
Name |
CX_SEC_LEV |
Destination Table |
CS_SEC_LEV |
EIM Exists Proc Column |
T_SEC_LEV_EXS |
EIM Row Id Proc Column |
T_SEC_LEV_RID |
EIM Status Proc Column |
T_SEC_LEV_STA |
EIM Unique Proc Column |
T_SEC_LEV_UNQ |
Attribute Mapping objects for Each EIM Interface Column Generated
Attribute Mapping objects should have the property values listed in Table 30 for each EIM interface column generated:
Table 30. Attribute Mapping Objects for Each EIM Interface Column
|
|
Name |
Attribute column on target table |
Interface Table Data Column |
Name of corresponding EIM interface table column generated (Table 28) |
Base Table Attribute Column |
Name of attribute column on target table |
Foreign Key Mapping for Each Foreign Key Column on the Target Table
A separate Foreign Key Mapping object is created for each foreign key mapping column on the target table. The properties listed in Table 31 are set for each.
Table 31. Foreign Key Mapping for Each Foreign Key Column on a Target Table
|
|
Name |
Name of the user key column |
Foreign Key Column |
Name of the user key column |
User Key |
Name of the U1 user key of the foreign key table |
EIM Foreign Key Proc Column |
Corresponding EIM interface table column for foreign key processing: "T_"+[Target table name without "CX_" prefix] +"_"+[user key column name] |
Continuing with the CX_SEC_LEV example, Table 32 shows the foreign key mapping.
Table 32. Foreign Key Mapping for Each Foreign Key Column on CX_SEC_LEV
|
|
|
EIM Foreign Key Proc Column |
OPTY_ID |
OPTY_ID |
S_OPTY_U1 |
T_SEC_LEV_OPTY_ID |
ACCNT_ID |
ACCNT_ID |
S_ORG_EXT_U1 |
T_SEC_LEV_ACCNT_ID |
Foreign Key Mapping Columns for each Foreign Key Mapping object
A separate Foreign Key Mapping Column object is created for each user key column in the user key specified for the parent Foreign Key Mapping object (Table 31). The following properties are set for each foreign key mapping column (Table 33):
Table 33. Foreign Key Mapping Columns for Each Foreign Key Mapping Object
|
|
Name |
Name of the Foreign Key Mapping Column. |
Interface Data Column |
EIM interface table column to which the user key column on the target table should be mapped. This EIM interface table column is generated according to the specifications in Table 25. |
User Key Attribute |
Name of the corresponding user key column that belongs to the user key specified in Table 31. |
Continuing with the CX_SEC_LEV example, Table 34 shows the foreign key mapping.
Table 34. Foreign Key Mapping Columns for CX_SEC_LEV
|
|
|
OPTY_BU_ID |
OPTY_BU_ID |
BU_ID |
OPTY_NAME |
OPTY_NAME |
NAME |
OPTY_PR_DEPT_OU_ID |
OPTY_PR_DEPT_OU_ID |
PR_DEPT_OU_ID |
ORG_BU_ID |
ORG_BU_ID |
BU_ID |
ORG_NAME |
ORG_NAME |
NAME |
ORG_LOC |
ORG_LOC |
LOC |
|