Change basic into transactional cube?

[martin_lehmann4]

Hallo experts,

is it possible to switch an existing basic cube over to a transactional cube? The basic cube has aprox. 6,5 million sentences in its fact table. The querys and ETL programs should keep on running without problems.

Best regards

Martin Lehmann

[martin_lehmann4 · Accepted solution]

Thank you Claudio and Paolo,

one additional question: in OSS note 411725 "Questions regarding transactional InfoCubes" there are some advices to be considered when changing a basic into a transactional cube - is it the only effort we will have to insert the variable 0S_RQMRC into all queries? What are your experiences?

[Former Member · Accepted solution]

For me it's important what I said. Make a backup of your data!

Sometimes this FM/program does not works well and immediately!

After the execution of this program, make logoff-logon....!

[Former Member · Accepted solution]

Hi Martin,

The reason you need to include variable 0S_RQMRC into all queries, is because the data load requests in transactional infocubes do not close till the time the number of records loaded is 50,000 or it has been closed using a Program/FM available. As a result the request remains in yellow status.

But if you have included the above variable in your queries you would be able to see the data in the BEx reports even though the requests are in yellow status.

[Former Member]

Hi Martin,

Some information from SAP Service can guide you:

Conversion to transactional infocubes:

BW 2.0B Support Package 15 contains two programs that facilitate

conversion to transactional infocubes:

(a) The ABAP report SAP_CONVERT_TO_TRANSACTIONAL allows you to convert a non-transactional infocube to a transactional infocube. In this process, the BW repository is adjusted, together with the database layout. If the F-fact table of the infocube being converted contains many entries, the ABAP report should run in the background.

(b) The functional module RSAPO_CLOSE_TRANS_REQUEST adopts the name of a transactional infocube as input parameter and closes the current write request (cf. point (3) above) . This can be useful if, for example, you want to fill a data mart scenario from the transactional infocube. If you call this functional module before filling, the data sets for the current write request are also taken into account.

Hope it helps..

Best Regards,

DMK

*Assign points if it serves your purpose..

[martin_lehmann4]

Thank you guys for your detailled help! When we will convert our bacic cubes being considerd I don't know, but if so, I will share our experience with you...

[Former Member]

If the Basic InfoCube already contains transaction data from the production operation you still need, proceed as follows:

Execute the SAP_CONVERT_TO_TRANSACTIONAL ABAP report under the name of the corresponding InfoCube. You should schedule this report as a background job for InfoCubes with more than 10,000 data records. This is to avoid a potentially long run-time.

Regards

[Former Member]

Take a backup and after launch FM: "SAP_CONVERT_TO_TRANSACTIONAL".

Take a look to the OSS!

Hope this helps!