sapnote_0000602260

26.10.2012 Page 1 of 6

SAP Note 602260 - Procedure for reconstructing data forBW

Note Language: English Version: 7 Validity: Valid Since 27.07.2004

Summary

SymptomYou want to reconstruct document data for an initialization of the BusinessInformation Warehouse or for a full upload.

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

Other termsCustomizing 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, DeltaInit, initialization

Reason and Prerequisites

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

o 02 - Purchase

o 03 - Inventory Controlling

o 04 - Production

o 05 - Quality management

o 08 - Transportation

o 11 - SD sales

o 12 - SU shipping

o 13 - SD billing

o 17 - Plant maintenance

o 18 - Customer service

o 40 - Retailing

o 45 - Agency business

1. Ensure that the reconstruction tables of the application for which thedata is to be built are empty.

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

26.10.2012 Page 2 of 6


set-up tables.

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

Possible reason: The reconstruction programs write data additivelyinto the set-up tables. If a document is entered twice from thereconstruction, it also appears twice in the set-up table. Therefore,the reconstruction tables may contain the same data from your currentreconstruction and from previous reconstruction runs (for example,tests). If this data is loaded into BW, you will usually see multiplevalues in the queries (exception: Key figures in an ODS object whoseupdate 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. Inparticular, you must deactivate the start of the RMBWV3nn updatereport.It is not sufficient to simply lock individual transactions (forexample, VA01, VA02 for application 11) because transactions fromother R/3 areas may also have an influence on the documents belongingto the application affected by the reconstruction.

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

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

Possible reason:Documents were posted during the reconstruction.

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

Example: Document 4711, quantity 15Data in the PSA: ROCANCEL DOCUMENT QUANTITY ' ' 4711 15 delta, new record ' ' 4711 15 reconstructionQuery result: 4711 30

Documents that are changed during the reconstruction run displayincorrect values in BW because the logic of the before and afterimages no longer match.

Example: Document 4712, quantity 10, is changed to 12.Data in the PSA:

26.10.2012 Page 3 of 6


ROCANCEL DOCUMENT QUANTITY X 4712 10- delta, before image ' ' 4712 12 delta, image anus ' ' 4712 12 reconstructionQuery result: 4712 14

3. Before you start the reconstruction, make sure that data is no longerwaiting 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-specificupdate report RMBWV3nn (nn = application number) directly intransaction SE38/SA38 .

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

Possible reason:The reconstruction ignores the data in the update queues. Anewly-created document is in the update queue awaiting transmissioninto the delta queue. However, the reconstruction also processes thisdocument because its data is already in the document tables.Therefore, you can use the delta initialization or full upload to loadthe same document from the reconstruction and with the first deltaafter 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 thedelta queue RSA7. You must delete the transferred data from the PSA,it must not be updated into the data targets. If you delete the deltainitialization from BW, this step is superfluous because the entiredelta queue is also deleted when the initialization is deleted.

Typical error scenario:After you perform the reconstruction and restart the update, you findduplicate 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 thedelta queues. An updated document is in the delta queue awaitingtransmission into BW. However, the reconstruction processes thisdocument because its data is already contained in the document tables.Therefore, you can use the delta initialization or full upload to loadthe same document from the reconstruction and with the first deltaafter the reconstruction into BW.

26.10.2012 Page 4 of 6


5. Now start the reconstruction for the desired application.

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

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

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

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

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

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

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

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

With "Delta queued" and "unserialized V3 update", documents canalready be edited again during the runtime of the initializationrequest. The data is then collected in the update queue (LBWQ orSM13). However, under NO circumstances should you run the RMBWV3nnupdate report before successfully completing the initializationrequestWith "Delta direct", the initialization request must be successfullyclosed.

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

26.10.2012 Page 5 of 6


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

If, instead of "Delta initialization with data transfer", you use the"Delta initialization without data transfer" with the upload ofreconstruction data by full upload, the use of ODS objects is subject toother restrictions. For more information, see note 689964.

Header DataRelease Status: Released for CustomerReleased on: 27.07.2004 08:35:55Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: BW-BCT Business Content and Extractors

Secondary Components:BW-BCT-LO-LIS Logistics Information SystemBW-BCT-QM Quality ManagementBW-BCT-ISR Retail and Consumer ProductsBW-BCT-SD-SLS SalesBW-BCT-SD-BIL BillingBW-BCT-MM-IM Inventory ManagementBW-BCT-MM-PUR PurchaseBW-BCT-PP-PP Production PlanningBW-BCT-LE-SHP ShippingBW-BCT-LE-TRA Transport

The Note is release-independent

Related Notes

Number Short Text762951 Organization of structure changes in the LBWE761554 Netweaver: Reorganization terminates with message M2 630753654 How can downtime be reduced for setup table update739863 Repairing data in BW691721 Restoring lost data from a delta request689964 ODS object: Switching from a full to delta upload586221 SIS: Reorganiztn takes longer after implementation of 500729

26.10.2012 Page 6 of 6


Number Short Text565035 SIS: Reorganization terminates - RSQL error 13546285 Performance improvement LIS and BW setup524515 SIS/BW: Performance improvement during reorg from archives500729 SIS/BW: Improved performance during reorganization437672 LBWE: Performance for setup of extract structures436393 Performance improvement for filling the setup tables