KB19102: In MicroStrategy Enterprise Manager, document names associated to document jobs are seen as ‘DELETED DOCUMENT’

SYMPTOM:
When users run the following report to list document job IDs and associated document names, the document names associated to some document jobs are retrieved as 'DELETED DOCUMENT' instead of displaying the actual document name.
 

 
It is noted that the document associated with the document job is existent in the metadata.
 
Querying the Statistics tables for document executions shows that the document GUIDs associated with all document jobs are correctly recorded.
 
CAUSE:
The cause for this behavior is that, there is no entry for the document (that is listed as DELETED DOCUMENT) in the lookup table for documents IS_DOC. During the dataload, objects are first populated into the lookup tables and then, fact tables are populated by getting data from the Statistics tables and the lookup tables. Because of the missing data in the IS_DOC table, the IS_DOC_FACT table does not have the correct document name. The IS_DOC_ID column in the fact table incorrectly gets populated as '-1', which refers to a DELETED DOCUMENT in the IS_DOC lookup table.
 
Lookup tables are also populated at the time of dataload, but only those objects which have a modification date that falls in the dataload time window are migrated.
 
ACTION:
Users can implement any of the steps below to resolve this issue:
 
Method A:

1. Identify the modification date of the document in question (i.e. the document which is seen as deleted document).
2. Through the Enterprise Manager console, run a custom time window dataload such that the modification date is included in this window. This step will populate the IS_DOC table with the required document data.
   
   Note: For more information about the custom time window dataload, refer to the following knowledge base document:
   KB6400-75x-0263: What are the "Custom Time Window" and "WH Data Deletion" buttons in the Strategy Enterprise Manager Console?
    
3. If users need to modify the data in the IS_DOC_FACT table with the correct document IDs, a custom time window dataload must to be run such that it includes the timeframe in which incorrect document names are seen in the IS_DOC_FACT table. If step3 is not implemented, document names will not be seen correctly for documents that were executed in the past, but will be recorded correctly for all data that gets transferred after step 2 is implemented.

OR
 
Method B:

1. Modify the description or any other component of the document to change the modification date/timestamp of the document to the current time.
2. A scheduled dataload or a manual dataload will move the document data into the IS_DOC table, as the modification date of the document will fall into the dataload window.
3. Dataloads following the above step will have the correct document name associated to document executions that are newly transferred into the IS_DOC_FACT table. To correct the data for document executions that are already in the fact table, step 3 from method A should be implemented.