Update mode changed directly from delta -> Note long text Notifications MCEX 167 1.

Diagnosis You changed the update mode to "Delta Direct". Note that a significantly high amount of entries is created in the B delta !ueue "see the B #elta $ueue Maintenance%. Procedure &t might 'e necessary to load data more fre!uently than once a day into the B system "'ut not more often than once an hour%. (lso note the follo)ing special features )hen setting up the #ata*ources the B system+ for

(,ter the set-up run in the ./01 system2 at least one successful initiali3ation re!uest for each #ata*ource needs to happen 'efore you can ma4e document changes. .ther)ise2 delta information is irretrie5a'ly lost. Important+ Before transporting the customi3ing re!uests for changing the update mode in other systems2 you must chec4 to see that no more entries e6ist in the !ueue MCEX78. &t is possi'le to chec4 the target system in the logistics !ueue o5er5ie) "transaction /B $%.

9. You ha5e changed the update mode to " Delta queued". Procedure *chedule a periodical :o' " ;sing the "<o' Control" function in the /ogistic E6traction Coc4pit% that regularly transports !ueue data for application 78 into the B #elta $ueue for the respecti5e #atasource. 0his :o' must run hourly.

Diagnosis

You ha5e changed the update mode to " Unserialized V3 Update". Note that )ith this mode2 the delta records currently do not arri5e in the same se!uence in the B system as they )ere created in the ./01 system. 0his can lead to pro'lems2 especially if you use .#* o':ects. Important+ Before transporting the customi3ing re!uests for changing the update mode in other systems2 you must chec4 to see that there are no more entries in the system in the !ueue MCEX78. &t is possi'le to chec4 the target system in the logistics !ueue o5er5ie) "transaction /B $%.

Update acti ated

You ha5e acti5ated the e6traction of an e6traction structure. By setting the =8 update to acti5e for the affected application2 update entries that contain "collecti5e processing" modules are created for e5ery document change. 0hese cannot 'e processed automatically either immediately or later2 as is possi'le for a =1 or =9 update. You ha5e to start the process for these update entries e6plicitly. ,or logistics e6traction2 you can set the time that you )ant to 'egin the e6plicit start-up using the function "<o' control". &f changes are made to the (B(1 dictionary o':ects used in the update module 'et)een the time of creating an update entry and the =8 update process2 the update entries can no longer 'e updated and an update termination ensues. &n this situation you can only delete the update entry. 0he data 'elonging to it is lost. &f you chose the update mode >$ueued #elta> for the affected application2 )hene5er a document change is made2 entries are generated in an e6traction !ueue. 0hese entries are not processed automatically. You ha5e to e6plicitly trigger processing of these entries in the e6traction !ueue. ,or logistics e6traction2 you can set the time point for this e6plicit start-up using the <o' Control function.

&f changes are made to the (B(1 dictionary o':ects used in the module 'et)een the time )hen an entry is generated in an e6traction !ueue and the processing of this entry2 this !ueue entry can no longer 'e processed2 and causes a runtime error. &f this happens2 you can only delete the !ueue entry - the data that 'elongs to it has 'een lost.