EIM System Columns for S_ACTIVITY_ATT
(Doc ID 543053.1)
Last updated on FEBRUARY 05, 2021
Applies to:Siebel Enterprise Integration Manager - Version 126.96.36.199  and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 188.8.131.52 
Database: Oracle 184.108.40.206
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP-UX 11.11
This document was previously published as Siebel SR 38-3318267593.
***Checked for relevance on 19-Jan-2015***
We are migrating Action Attachment files from a Siebel 6.3 system to Siebel 7.8, as part of a Siebel version upgrade via a system re-implementation (as opposed to a Siebel Upgrade via the standard Siebel Upgrade).
We will do this by copying attachment files from \\siebfile folder in 6.3 to the ..\input folder on the 7.8 server file system, and then running the appropriate EIM task, after transferring rows from the S_ACTIVITY_ATT in 6.3 to EIM_ACT_DTL in 7.8.
However the only columns I can see in the vanilla EIM mapping to EIM_ACT_DTL are for the columns COMMENTS, FILE_EXT, FILE_NAME, FILE_SRC_TYPE and MAIL_ATT_TYPE_CD, and we only use the middle three of these in the 6.3 implementation. This is fine.
However, there are a number of other (system?) columns in S_ACTIVITY_ATT, most of which are flags, which are populated in our 6.3 database, and which I am worried about losing if we just migrate the above three columns. I have seen the following 2 Docs:
Unable to perform EIM load into S_ACCNT_ATT (Doc ID 491796.1)
EIM_ACCNT_DTL has missing mapping for S_ACCNT_ATT table. (Doc ID 526942.1)
which outline how to extend the EIM_ACT_DTL table with extension columns to migrate into some of these columns, and we can do this no problem.
However, in order to identify which columns we need to migrate, and to get a better understanding of how things work in both 6.3 and 7.8, would you
(a) outline for us the purpose of the following columns in S_ACTIVITY_ATT in 6.3,
(b) whether we need to target them for migration (i.e. are any of them automatically populated during the EIM import process) and
(c) perhaps give an indication if they have changed purpose in 7.8:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document