SAP Netweaver Business Intelligence BI / BW

Symptom

If you change an extraction structure in the Customizing Cockpit (transaction LBWE) by importing a support package or a transport or by carrying out an upgrade, if this had already been activated for update for a certain time, various errors may occur:
The initialization of data that was created before the change no longer works (CONNE_IMPORT_WRONG_COMP_LENG).Delta requests terminate (CONNE_IMPORT_WRONG_COMP_LENG).The V3 update is no longer processed.The update from the extraction queue (update mode “Delta Queued”, as of PI(-A) 2002.1) is no longer processed.The log terminates (CONNE_IMPORT_WRONG_COMP_TYPE).

The same symptoms may be caused by a change to one of the LIS communication structures assigned to the application (such as MCMSEG or MCBEST for application 03) or, in individual cases, to other application tables also, or to one of the other extraction structures or DataSources belonging to the application (for application 11, for example).
The activation of a DataSource that was previously not used, for example, may also cause problems in an extraction structure that belongs to another DataSource (which belongs to the same application).
Furthermore, in individual cases, a change to an extraction structure may also have a negative effect on the update of another extraction structure (that belongs to the same application).

Other terms

LBWE, CONNE_IMPORT_WRONG_COMP_LENG, CONNE_IMPORT_WRONG_COMP_TYPE
IMPORT_ALIGNMENT_MISMATCH, CONNE_IMPORT*, IMPORT, V3, SM13, update
MCEX_UPDATE_02, MCEX_UPDATE_03, MCEX_UPDATE_04, MCEX_UPDATE_05
MCEX_UPDATE_05_1, MCEX_UPDATE_08, MCEX_UPDATE_11, MCEX_UPDATE_12
MCEX_UPDATE_13, MCEX_UPDATE_17, MCEX_UPDATE_17_1, MCEX_UPDATE_18
MCEX_UPDATE_18_1, MCEX_UPDATE_40, MCEX_UPDATE_43, MCEX_UPDATE_44
MCEX_UPDATE_45, MCEX_UPDATE_45_1, MCEX_BW_LO_API

Reason and Prerequisites

When you change a structure, the data that is stored in the old form of the structure may no longer be interpreted correctly.
Since changes to extraction structures (or other update-relevant structures) and to basic data definitions can also be made during an R/3 upgrade or a plug-in upgrade and (in very rare cases) when you import an R/3 standard or plug-in Support Package, the precautions described below should also be taken beforehand.

Solution

You must carry out the following steps before a change to a structure:
1. Make sure that you carry out the following steps at a time when no updates are performed, so that no data is lost.2. Start the update collective run directly from the Customizing Cockpit. Up to PI(-A) 2001.2 , this collective run concerns only the V3 update. As of PI(-A) 2002.1, depending on the configuration of the update mode of the application, the collective run concerns either the V3 update or the update from the extraction queue (”Delta Queued”, see Note 505700).3. Load all the data of the relevant DataSource into the BW System.

You can then make the change.
After making a change, you may no longer be able to use statistical data that was already set up. If such data still exists, you must delete it (transaction LBWG).
We recommend in particular that you upload the data immediately after a setup and (after checking in BW) delete it from the setup tables.
Furthermore, the update log (transaction LBWF) can no longer be read. In this case, you must post a document, so that the last log entry is overwritten. This log entry then has the correct new format of the extraction structure.
As of PI 2000.2, the program RMCEXDELETELOG is provided, which you can use to delete log entries.
Note the following:
The program RMCEXDELETELOG is available in the current PI 2000.1 patch. However, no success message is displayed.
You can also import the program from the SAPSERV hosts. It can be found in the directory /general/R3server/abap/note.0328181. However, only German texts have been maintained.
If you forget to execute the update collective run before a change, the only option you have is to delete the records that still exist. This means that this data is lost.
To do this,
in the case of V3 update methods, navigate to the update overview (transaction SM13), select the records (user *, V2 executed, restrict date), and select Update records -> Delete -> All records. Do not forget to deactivate the flag “Only incorrect”.in the case of the update method “Delta Queued” (as of PI(-A) 2002.1), navigate to the logistics queue overview (transaction LBWQ). Select the queues for the relevant applications one after the other (MCEXnn, nn = number of the logistics application, see transaction LBWE), and choose the display function. Choose the display function again to list all the entries in the queue. Then select and delete all of the entries that had been saved before the structure change. In case of a very large number of entries in a queue, it may be necessary to delete the entire contents of the queue. This can be done on the initial screen of transaction LBWQ.