What values must be populated for PARTY_TYPE_CD, PARTY_UID and ROOT_PARTY_FLG columns in S_PARTY table using EIM
PARTY_TYPE_CD, PARTY_UID, ROOT_PARTY_FLG are the required columns in S_PARTY table which have to populated while doing an import of party records(like contact, position, etc.) using Enterprise Integration Manager (EIM). The following are the description of these columns and the possible values it can hold:
PARTY_TYPE_CD is used to indicate what type of party data is being imported. It can have the following values:
Person - For Contact, User, Employee or Partner
Organization - For Organization, Division or Account
No custom values are allowed for PARTY_TYPE_CD column. It must contain one of the above mentioned values.
PARTY_UID is defaulted through the Upgrade and Application (UI) to the ROW_ID of the party record (for example Contact, Position, etc.) that is being created. But the value for this column should be maintained by the customer. As long as users are able to maintain the PARTY_UID, there is no requirement that this should be identical with the ROW_ID.
In case of EIM, the PARTY_UID gets populated with the value specified in the Interface Table for this column. It may have a calculated value that has more logic for the customer (like combination of email and some other data) and that's why it is defined as VARCHAR100.
ROOT_PARTY_FLG was added to support performance for Oracle. A query can use either
1. WHERE ROOT_PARTY_FLG='Y' or
2. WHERE PAR_PARTY_ID is NULL
to get top level Positions, Organizations or Access Groups. Oracle cannot use an indexed access path for option 2 because there are no index entries for NULL, so ROOT_PARTY_FLG was added.
ROOT_PARTY_FLG is set to 'Y' for top level Positions, Organizations and Access Groups as it applies only to these Party sub-types. It is set to 'N' for other party subtypes.
Readers who viewed this page, also viewed:
- Real time Siebel EIM (Enterprise Integration Manager) Interview Questions – Part 1 (78.6%)
- How to Resolve Siebel EIM Errors (64.3%)
- How should users relate two PARTY Objects (example: Accounts and Contacts) in Siebel when importing data using Enterprise Integration Manager (57.1%)
- How should EXPORT MATCHES and DELETE MATCHES be used in Siebel? (57.1%)
- Overcoming the Fears that Inhibit Alliances (50.0%)
- Is it possible to set up individual user locales? (50.0%)
- The Complexities of Management (50.0%)
- Overview of Siebel Enterprise Integration Manager (EIM) (50.0%)
- Balancing the Constraints and Demands of being a Manager (50.0%)
- Navigating through complexities of Managing People (50.0%)