Question:
SEM practitioners,
Is there a way that we can load data( via BW approach) directly to a transactional cube without switching the cube to a basic.
Appreciate any expereiences people may have faced in this area.
Regards
McGallin
Answer:
The only way i can think of is taking a normal infocube, populate it with data and then use this FM SAP_CONVERT_TO_TRANSACTIONAL
to convert it to a transactional infocube.There is one more FM called SAP_CONVERT_NORMAL_TRANS , which brings it back to a normal cube.
i hope this helps your requirement.
V
Answer:
You do not want to use the FM SAP_CONVERT_TO_TRANSACTIONAL SAP_CONVERT_NORMAL_TRANS to load the cube since it physically converts the cube from transactional cube to basic cube.
What you want to do is use the the FMs
RSAPO_SWITCH_BATCH_TO_TRANS
RSAPO_SWITCH_TRANS_TO_BATCH
which switches the transaction cube fro batch mode to transaction mode only and in batch mode you can load the cube. If you need it with a scheduled job, put the FMs in ABAP programs and put it in a process chain before and after the load.
Hope this helps, Mary
Answer:
Mary my diagnosis was wrong, however i think the requirement i doubt would be fulfilled with the FM's you are proposing.
what mcgallin wants is not to switch the cube to basic, but to load data while it is in transactional cube status, which is practically not possible.
but it would be interesting to know if this is possible.
V
Answer:
McGallin,
there's an answer to this on http://www.semexpert.com.
Regards,
SEMexpert.com
Answer:
For those who want a quick overview of the solution, but have no access to OSS here is the summary:
Vamsh
Method:Create an implementation called 'Z_RSSEM_REQUEST_COPY' for BADI definition BW_SCHEDULER (Transaction SE19). Call function
module RSSEM_REQUEST_COPY_ALL in method 'USER_EXIT' of this BADI:
CALL FUNCTION 'RSSEM_REQUEST_COPY_ALL'
EXPORTING
I_RNR = RNR
I_TSTATUS = TSTATUS
I_WRITE_TO_CUBE = WRITE_TO_CUBE
I_TYP = TYP.
In table RSSEM_REQUESTCOP, maintain the assignment between source InfoCube and target InfoCube.
When you schedule the InfoPackage, select check box 'Execute Business Add-In' under 'Postprocessing'.
When the data is loaded, the system now automatically generates a background job (named 'REQUEST_COPY') for each target InfoCube that you have entered in table RSSEM_REQUESTCOP. This job contains a step, in which report RSSEM_REQUEST_COPY is executed. The generated variant for this report includes the request number, the source InfoCube and the target InfoCube. If you do not want to start the update into the transactional InfoCube automatically, you can also start report RSSEM_REQUEST_COPY manually.
Answer:
Hi Vamsh,
Thanks for the OSS notes information. It really helps people like me who don't have access to OSS notes.
I created 'Z_RSSEM_REQUEST_COPY' implementation for BADI definition BW_SCHEDULER using Transaction SE19. After creating when i tried to save it, it was asking for access key. I don't have any access key and so i couldn't continue.
Could you give me any suggestions.
Regards,
R
Answer:
Are you on a IDES or a some sort of brand new system? The access key popup comes because of any changes to standard objects which SAP monitors. My advise is dont touch the standard objects, create a copy of the std obj and use them.
or ask your basis guy to register you as a developer in the system.
Answer:
Hi Vamsh,
I am working on IDES SEM 3.1. I will try to see if i can create a copy of the original implementation or not.
Regards,
R