jump to navigation

602260 – Procedure for reconstructing data for BW August 14, 2008

Posted by Ajay in Uncategorized.
trackback

Summary

Symptom
You want to reconstruct document data for an initialization of the Business Information Warehouse or for a full upload.

This note gives recommendations on the steps you should take to reconstruct this data. First read this note in full to gain an overview of the process.

Other terms
Customizing Cockpit, LBWE, OLI1BW, OLI2BW, OLI3BW, OLI4BW, OLI7BW, OLI8BW, OLI9BW, ORISBW, VTBW, VIFBW, OLIFBW, OLIZBW, OLIIBW, OLIABW, OLIQBW, SM13, V3, RSA7, LBWQ, SMQ1, Delta queued, LO application, BW, Request, Delta Init, initialization

Solution
The following steps apply to reconstructing data from the following R/3 components:

  • 02 – Purchase
  • 03 – Inventory Controlling
  • 04 – Production
  • 05 – Quality management
  • 08 – Transportation
  • 11 – SD sales
  • 12 – SU shipping
  • 13 – SD billing
  • 17 – Plant maintenance
  • 18 – Customer service
  • 40 – Retailing
  • 45 – Agency business
    1. Ensure that the reconstruction tables of the application for which the data is to be built are empty.

To do this, execute transaction LBWG for the relevant application, for example, application 11 for SD sales documents.
LBWG deletes the data of all set-up tables for all active DataSources for the selected application. It is not possible to delete individual set-up tables.

Typical error scenario:
After the reconstruction, you find documents repeatedly in BW.

Possible reason: The reconstruction programs write data additively into the set-up tables. If a document is entered twice from the reconstruction, it also appears twice in the set-up table. Therefore, the reconstruction tables may contain the same data from your current reconstruction and from previous reconstruction runs (for example, tests). If this data is loaded into BW, you will usually see multiple values in the queries (exception: Key figures in an ODS object whose update is at “overwrite”).

    2. The reconstruction must occur during posting-free periods.
    For this purpose, lock all end users (and, if necessary, system users) and terminate all scheduled jobs that could affect the application. In particular, you must deactivate the start of the RMBWV3nn update report.
    It is not sufficient to simply lock individual transactions (for example, VA01, VA02 for application 11) because transactions from other R/3 areas may also have an influence on the documents belonging to the application affected by the reconstruction.

This restriction also applies if you only want to set up a selected number of documents again, for example to subsequently load documents into BW using full upload. Then you should carefully consider in advance whether these documents could be changed during the recompilation run. If this is the case, the reconstruction must also occur in an update-free period.

Typical error scenario:
Data for individual documents from the period of the reconstruction run is incorrect in BW.

Possible reason:
Documents were posted during the reconstruction.

Documents created during the reconstruction run then exist in the reconstruction tables as well as in the update queues. This results in the creation of duplicate data in BW.

Example: Document 4711, quantity 15
Data in the PSA:
ROCANCEL DOCUMENT QUANTITY
‘ ‘ 4711 15 delta, new record
‘ ‘ 4711 15 reconstruction
Query result:
4711 30

Documents that are changed during the reconstruction run display incorrect values in BW because the logic of the before and after images no longer match.

Example: Document 4712, quantity 10, is changed to 12.
Data in the PSA:
ROCANCEL DOCUMENT QUANTITY
X 4712 10- delta, before image
‘ ‘ 4712 12 delta, image anus
‘ ‘ 4712 12 reconstruction
Query result:
4712 14

    3. Before you start the reconstruction, make sure that data is no longer waiting to be updated.

Depending on the selected update method, check the following queues:

    • SM13 – serialized or unserialized V3 update
    • LBWQ – Delta queued (available as of plug-in 2002.1)

If necessary, start updating the data from the Customizing Cockpit (transaction LBWE) or start the corresponding application-specific update report RMBWV3nn (nn = application number) directly in transaction SE38/SA38 .

Typical error scenario:
After you perform the reconstruction and restart the update, you find duplicate documents in BW.

Possible reason:
The reconstruction ignores the data in the update queues. A newly-created document is in the update queue awaiting transmission into the delta queue. However, the reconstruction also processes this document because its data is already in the document tables. Therefore, you can use the delta initialization or full upload to load the same document from the reconstruction and with the first delta after the reconstruction into BW.

    4. Then load the delta data from R/3 into BW, so that the delta queue (transaction RSA7) no longer contains any data.
    In the case of a complete reconstruction, this upload only clears the delta queue RSA7. You must delete the transferred data from the PSA, it must not be updated into the data targets. If you delete the delta initialization from BW, this step is superfluous because the entire delta queue is also deleted when the initialization is deleted.

Typical error scenario:
After you perform the reconstruction and restart the update, you find duplicate documents in BW.

Possible reason:
The same as point 2; there, the document is in the update queue, here, it is in the delta queue. The reconstruction also ignores data in the delta queues. An updated document is in the delta queue awaiting transmission into BW. However, the reconstruction processes this document because its data is already contained in the document tables. Therefore, you can use the delta initialization or full upload to load the same document from the reconstruction and with the first delta after the reconstruction into BW.

    5. Now start the reconstruction for the desired application.

Note that the system only fills those reconstruction tables whose DataSources were activated in the Customizing Cockpit (LBWE).
Additional information:
Note 436393 provides useful tips on how to accelerate the reconstruction.

    6. If you are carrying out a complete reconstruction, delete the contents of the corresponding data targets in your BW (cubes and ODS objects).

Note also that downstream data targets that have a new data target to be built as a source (key word: DataMart) must also be deleted. Due to the individuality of the data model in BW, we cannot provide general recommendations for the procedure.

    7. If these steps are completed, use an Init request (delta initialization with data transfer) or a full upload to load the data from the reconstruction into BW.

If you use “Delta initialization with data transfer”, note that the initialization of the delta queue was only correctly performed for the relevant DataSource if this request is “green” and if the corresponding queue in transaction RSA7 has a green traffic light. Depending on the dataset and the data model used in BW, this operation may take several hours. Only after it is complete can you restart the update, that is, you can run the RMBWV3nn update report again.

Typical error scenario:
Document data from time of the delta initialization request is missing from BW.

Possible reason:
The RMBWV3nn update report was not deactivated. As a result, data from the update queue LBWQ or SM13 can be read while the data of the initialization request is being uploaded. However, since no delta queue (yet) exists in RSA7, there is no target for this data and it is lost.

    8. The time at which you can release document processing again for your end users after the reconstruction depends on your process configuration.

With “Delta queued” and “unserialized V3 update”, documents can already be edited again during the runtime of the initialization request. The data is then collected in the update queue (LBWQ or SM13). However, under NO circumstances should you run the RMBWV3nn update report before successfully completing the initialization request
With “Delta direct”, the initialization request must be successfully closed.

Additional information:
You may have to reconstruct individual documents or document groups and transfer them to BW again. In this case, you should carry out the steps described in the same way.

With this type of selective reconstruction of individual documents or, for example, specific organizational units, you must ensure that any existing data in BW is selectively deleted.

If, instead of “Delta initialization with data transfer”, you use the “Delta initialization without data transfer” with the upload of reconstruction data by full upload, the use of ODS objects is subject to other restrictions. For more information, see note 689964.

Header Data

Advertisements

Comments»

No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: