We are not reporting using navigational attribute. But it shows updated records for other materials. The issue is only with one material.
We checked that there is no SID for that particular material in the table. Though it is automatically generated but not sure why it's blank for this material. What shall we do now?
If you're not reporting on navigational attributes and you don't completely reload your InfoCube, you won't see the updated material group (which is quite obvious actually).
In your case the material group was filled with it's value at the time of loading, not with the most recent one from the master data.
Have a look here if you don't understand the difference between using a characteristic in a dimension or using a navigational attribute.
I have the following challenge: block the report execution in the reporting tools Bex, AAO, Lumira,... but not in web application designer for some queries with confidential data. Or to force that these queries only can be executed with an specific web template or an specific bex workbook.
I don't know an standard procedure for that (via roles and authorizations) but maybe it will be possible to distinguish what tool tries to execute the query via system variable.
Do you know how to do it or any brilliant idea that helps me?
Thanks in advance for you help.
BR, Jónatan.
Hello Hasan,
SAP Note 1142930 explains that "in transaction SBIW, you can specify a particular server using the 'Maintain Control Parameters for Data Transfer' Customizing activity (table ROIDOCPRMS)" at the source system side. Furthermore, you can optionally restrict the extraction job to a certain server group after implementing the code from SAP Note 1488762.
Regards,
Roger
Hello All,
I would like to ask your inputs regarding the matter of BIREQ* job.
We have process chain which runs in System A. It has loading step, in which the source system is the System B.
It triggers BIREQ* in system B.
My question is if it is possible, to set in which server in System B will the job BIREQ* is to be executed when it triggered.
Thanks lots.
Process Chain --> attributes --> Background server.
Isn't this just for the BW-application server? I don't think this allows you to control the application server in the source system...
you're completely right.... went to fast there...
M.
I don't think you have updates rules are supported in 7.4, better you migrate old flow to 7.0 and try try with transformation.
-
Regards,
Mgande
Hello Jajah,
Coincidentally, I answered this question yesterday. SAP Note 1142930 explains that "in transaction SBIW, you can specify a particular server using the 'Maintain Control Parameters for Data Transfer' Customizing activity (table ROIDOCPRMS)" at the source system side. Furthermore, you can optionally restrict the extraction job to a certain server group after implementing the code from SAP Note 1488762.
Regards,
Roger
I'm fairly new to BW and was doing a mock exercise.
I started created a DSO - added couple of characteristics and a time characterstic. Then I tried deleting the DSO but it gave me an error log.
Could not instantiate BW object for external SAP HANA view and
Error when deleting object DataStore Object (classic) BWSALES
Can someone advise how do I delete it?
Hi,
Please share all details of the error log. Especially the error message(s) with long text, message class and message number are important.
On which system release and SP level are you working?
Is the BW system on HANA? And if yes, do you work with the new Ecplise-based BW Modeling Tools or the classic RSA1 in the BW backend?
Best regards,
Sander
hi,
please activated the transformation and activate .
best regards
suresh neerukattu
Hi Experts,
I have a question reg the Query Designer.
We have 2 versions of Query DEsigner - 7.2 and 7.3. I believe that queries created in 7.2 can be changed and saved in 7.3. But once saved in 7.3, the changes cannot be made in 7.2.
Similarly, a query created in 7.3 cannot be changed and saved in 7.2.
So, now my question, I have to create a Y query(copy query) from Z query. Can I do this in any version? If I save the query in 7.3, will it affect the Z query(assuming it is in 7.2)?
Regards,
Yamini P
Hi Yamini,
You can do the copy and save(Y query) it any version 7.2 or 7.3.
that doesn't effect your source(Z query).
if you saved(Y Query)in 7.2 then that can be reopen in 7.3.
Thanks
Hello Hari T,
Can you share screen print of DTP selections, It should have option to exclude values (not equal) in its selection screen.
And check is your target has only one source or multiple with same data ?
-
Regards,
Mgande
use RSRV tcode
- all combined tests,
- select master data.
- give infoobject click on f8 r correct error option in application tool bar
Dear community,
I'm on BW 7.31 and I'm wondering if anyone can share their experience with DTPs filtering navigational attributes from a source Info Cube and using a Startroutine?
I found only old topics like: https://scn.sap.com/thread/2120352
It leads to Note: http://service.sap.com/sap/support/notes/1145673 saying that from 7.30 onwards it should work again.
Problem:
I had a DTP already using 2 navi attributes as filter, which worked fine before.
Now, I changed the DTP by
- including one aditional regular cube field as filter
- including a start routine.
Previously, the DTP selected ~ 12 Mio. records (15 minutes)
Now, it selects ~ 60 Mio records (which are in the cube, in total, it takes 2 hours now).
By adding one more restriction, it cannot be possible to get more records out of the source as before! But it happens...
Can anyone confirm if the issue is still the startroutine, as described in the note from Jan. 2013?
If you use a start routine, this means that the system extracts all the navigation attributes of the InfoProvider
I will try deleting the Startroutine again, and put the coding to the end routine... and let you know...
However, I would like to know, if SAP did not correct the bug as promised earlier?
Any feedback appreciated.
BR, Martin