Bookshelf v7.7: Troubleshooting Import Processing Failures

EIM is designed to import large volumes of data. Most failures are caused by data errors. It is usually faster and easier to correct the data errors and resubmit the corrected rows as part of a subsequent batch than to reprocess an entire batch. EIM does not stop when failures occur.

Failures can occur at several steps during the EIM Import Process; each type of failure has a different cause. See the causes listed in Table 14.

This section provides guidelines for resolving import processing problems. To resolve the problem, look for it in the list of Symptoms/Error Messages in Table 14.

Table 14. Resolving Import Processing Problems
Symptom/Error Message	Diagnostic Steps/Cause	Solution
Step 4 Failures	Step 4 processes foreign keys and bounded picklists. A row fails this step if the foreign key developed from values in the EIM table columns does not correspond to an existing row in the target Siebel database table. For example, a Step 4 failure on ACCNT_NAME indicates that the value in the ACCNT_NAME column of that row did not correspond to an existing name (S_ORG_EXT.NAME) or synonym name (S_ORG_SYN.NAME).	Correct the data errors and resubmit the corrected rows as part of a subsequent batch.
Step 6 Failures	Step 6 failures generally indicate invalid user key values. For example, a contact with a NULL value for the LAST_NAME column will fail because this is a required user key. All user keys are required except MID_NAME for contacts (S_CONTACT.MID_NAME) and LOC (location) for accounts (S_ORG_EXT.LOC).	Correct the data errors and resubmit the corrected rows as part of a subsequent batch.
Step 7 Failures	Step 7 evaluates the foreign key relative to the data being imported (whereas Step 4 evaluates it relative to existing data). If the foreign key references a table that is imported from the same EIM table, Step 7 resolves foreign keys into the data to be imported.	Correct the data errors and resubmit the corrected rows as part of a subsequent batch.
Step 8 and Step 9 Failures	Failures for Step 8 and Step 9 indicate columns that have NULL values for fields that are required but are not part of the user key.	Correct the data errors and resubmit the corrected rows as part of a subsequent batch.
Data not visible after import	If you find that, after an EIM import, the data is not visible in some views or applets, it is probably because values required for a particular view or applet to display imported data may not have been imported. For example, the Sales Order Line Items applet's product picklist will only display products with S_PROD_INT.SALES_SRVC_FLG value set to N.	To determine which values need to be imported for a particular view or applet, do a client-side spooling and check the SQL conditions when selecting the record.
Unable to edit quotes after import	Users are unable to edit their quotes after importing quote information.	Make sure that the APPROVED_FLG field is set to N or left blank for each quote. Setting APPROVED_FLG to Y makes the quote read only and not editable by the user.