Maybe I'm not quite getting what you want to do, but to me this reads like you want to look into PERCENTILE functions:

with base as (select part_no, cnt,

                    (select sum(cnt) from part_cnts) tot_cnt,

                     round(( cnt/((select sum(cnt) from part_cnts)/100)),2) perc_of_tot_cnt,

                     sum(cnt) over (order by cnt desc) cumm_sum

              from part_cnts

              order by cnt desc)

select part_no, cnt, tot_cnt, perc_of_tot_cnt, cumm_sum,

      round(percentile_cont (0.8) within group (order by cumm_sum asc) over() ,2 )thres_08,

      round(percentile_cont (0.95) within group (order by cumm_sum asc) over(),2) thres_095,

    case

    when percentile_cont (0.8) within group (order by cumm_sum asc) over() >= cumm_sum then

        'FAST'

    when percentile_cont (0.95) within group (order by cumm_sum asc) over() >= cumm_sum  then

        'MEDIUM'

    else 'SLOW'

    end  grp

from base

order by cnt desc;

See infos here SAP HANA Academy - SQL Functions: PERCENTILE_CONT and PERCENTILE_DISC - YouTube and here http://help.sap.com/saphelp_hanaplatform/helpdata/en/20/a353327519101495dfd0a87060a0d3/content.htm.

This approach doesn't use the percentage calculation for the classification (but I left it in for you to compare). The idea here is to first do a cummulative sum on the cnts and to calculate the threshold values for your desired percentages (aka percentiles).

Now, all you've got to do is to check whether the thresholds are met and assign the class.

Hi Guys i have resolved this issue of getting categories on a transaction see my attached document

1. Step 1

Use function module CRM_ORDER_READ to get the subject table (ET_SUBJECT). Get the ASP_ID and CAT_ID from et_subject table

2. Step 2

Loop through the internal table and get the ASP_ID and CAT_ID

3. Step 3

Once you have ASP_ID and CAT_ID call this class Cl_CRM_ML_CATEGORY_UTIL=>GET_CAT_KIDS_ALL passing ASP_ID and CAT_ID and get the table et_cat

4. Step 4

Once you get CAT_GUID and ASP_GUID then call class cl_crm_ml_category_util=>get_selected_category_tree

Table et_cat_level will have all categories on the transaction and ev_selected_level you will get the number of categories on the transaction.

Hello Jean-Luc

I was wrong when i said that i have on the same network a cluster of 2 BI servers (production) wich communicate with the same ldap server and do not have the same behaviour at all ; these 2 servers make ldap update every hour.

I will soon try a tcp.keep.alive to try to bypass a loss of activity that a firewall could diagnose and close connection.

Raoul

Hi,

I am unable to understand the question correctly.

How does it help if you have the data in excel but dont want to expot it anywhere? Keeping the data in internal table would be better.

What exactly the requirement is here?

Thanks

Hi Lyne,

If you want to change database fields, then best way is to go in Set Datasource Location and map old fields with new datasource fields.  This will change all your report fields wherever it was placed.

Also you can rename formula names and that will reflect in all places.

Otherwise :

You need to right click on each field and say find in formulas then go in each formula and replace with new one.

Thanks,

Sastry

We recently observed ONLY SOME of the IDOCS in status 64 not getting executed automatically,

we also checked the configuration (WE20) where trigger immediately is already set.

However on manually executing the affected IDOC's they are executed successfully.

We also noticed some dump entry created in ST22 which says

Error Analysis:

During background processing, the system attempted to send a screen to a                     

     user.                                                                                       

    Current screen: "SAPMSSY0 " 0120.                                                            

    Additional system information:                                                               

    "currently running as cpic server" 

How to correct the error:

If the error occurred in your own ABAP program or in an SAP                                  

    program you modified, try to remove the error.                                               

    If the error occurs in a non-modified SAP program, you may be able to                       

    find an interim solution in an SAP Note.                                                     

    If you have access to SAP Notes, carry out a search with the following                       

    keywords:                                                                                    

    "DYNPRO_SEND_IN_BACKGROUND" " "                                                              

    "SAPLKKBL" or "LKKBLU01"                                                                     

    "K_KKB_LIST_DISPLAY"

Can anybody provide us feed backs on how to resolve this issue?

Thanks in advance!

Thanks for the update Monika.  I've resolved our issue, it was related to the pisuper account password expiring and the password was needing to be reset, updated it to be a technical user non expiring and connection was established.  I didn't notice it until looking into the logs. After changing this I was able to connect to the services registry.

Thanks,

Nate

Not a problem. Warnings can be ignored as long as if your not using field i_def_ex.

Personnally, if you're increasing the page size, then a change from 2k to 4k isn't much of a change.

I've experimented and found (in my experience) that the best size will be dependent on your SAN or disk - but 8k, 16k or 32k would be better.

On some EMC SAN I found 16k pages optimal, and on others 32k pages were optimal.

Check the page size of your disk/SAN and either make it the same size as that or half the size.

Some might say that having larger pages will increase locking on allpages tables. Whilst that sounds true in theory, in practice I didn't notice anything. A physical page read is about 1000x slower than a memory page read - so if you're doing disk reads -you really want them to be quick and get as much data as fast as you can.

We went from 2k pages to 16k pages and possibly we should have gone for 32k pages (which is the page size of the SAN).

Yes - to load a 2k dump you'll need a 2k server. Its not great - but perhaps a VM could help here

We're not fully on Sybase 16 yet - but can't see much change (apart from a few new features) from 15.7. But its early days.

If you're coming from 15.5 then we found these issues (as part of going to 15.7)

It has the threading model - which (in my experience) needs some configuration experimentation to get right .

It also needs a lot more procedure cache (and I mean a LOT more) - this really hurt us. See the postings on this - Simons traceflag setting really saved us!!

Hi, Stephen

Sorry for the length of the message, but I attach rfc trace for confirmation. I find no call for the subject Q.

Fri Jul 08 18:29:12 CEST 2016 - start RfcWizardIntegrationClass

        Fri Jul 08 18:29:12 CEST 2016 - end /NAKISA/OC_EMPLOYEE_INFO 232ms

    Fri Jul 08 18:29:12 CEST 2016 - end RfcWizardIntegrationClass 249ms

Fri Jul 08 18:29:12 CEST 2016 - end Data call 249ms

Fri Jul 08 18:29:12 CEST 2016 - start Data call

    Fri Jul 08 18:29:12 CEST 2016 - start Rfc_Read_Table

        Fri Jul 08 18:29:12 CEST 2016 - end /NAKISA/RFC_READ_TABLE 37ms

    Fri Jul 08 18:29:12 CEST 2016 - end Rfc_Read_Table 42ms

Fri Jul 08 18:29:12 CEST 2016 - end Data call 50ms

Fri Jul 08 18:29:20 CEST 2016 - start refresh (SAP Data: 291 ms) (RFC: 269 ms)

Fri Jul 08 18:29:20 CEST 2016 - end refresh 3ms

Fri Jul 08 18:29:21 CEST 2016 - start loadorgchartdirectory

Fri Jul 08 18:29:21 CEST 2016 - end loadorgchartdirectory 7ms

Fri Jul 08 18:29:21 CEST 2016 - start initialize

Fri Jul 08 18:29:21 CEST 2016 - end initialize 6ms

Fri Jul 08 18:29:21 CEST 2016 - start refresh

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

        Fri Jul 08 18:29:21 CEST 2016 - end /NAKISA/OC_OU_STRUCTURE 117ms

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 134ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 134ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

        Fri Jul 08 18:29:21 CEST 2016 - end /NAKISA/OC_OU_STRUCTURE 29ms

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 45ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 45ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

        Fri Jul 08 18:29:21 CEST 2016 - end /NAKISA/OC_OU_STRUCTURE 88ms

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 103ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 104ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 12ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 13ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 13ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 13ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 12ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 13ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 13ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 13ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 13ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 13ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 12ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 13ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 13ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 13ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 12ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 12ms

Fri Jul 08 18:29:21 CEST 2016 - start Data call

    Fri Jul 08 18:29:21 CEST 2016 - start RfcWizardIntegrationClass

    Fri Jul 08 18:29:21 CEST 2016 - end RfcWizardIntegrationClass 12ms

Fri Jul 08 18:29:21 CEST 2016 - end Data call 13ms

Fri Jul 08 18:29:21 CEST 2016 - end refresh 912ms (SAP Data: 394 ms) (RFC: 234 ms)

Fri Jul 08 18:29:29 CEST 2016 - start setorgchartdirectory

Fri Jul 08 18:29:29 CEST 2016 - start Data call

    Fri Jul 08 18:29:29 CEST 2016 - start HrociWizardIntegrationClass

        Fri Jul 08 18:29:29 CEST 2016 - end HRMSS_GET_ORGSTRUCTURE_AS_XML 239ms

        Fri Jul 08 18:29:29 CEST 2016 - end HRMSS_GET_ORGSTRUCTURE_AS_XML 91ms

    Fri Jul 08 18:29:29 CEST 2016 - end HrociWizardIntegrationClass 355ms

Fri Jul 08 18:29:29 CEST 2016 - end Data call 355ms

Fri Jul 08 18:29:29 CEST 2016 - start Data call

    Fri Jul 08 18:29:29 CEST 2016 - start HrociWizardIntegrationClass

    Fri Jul 08 18:29:29 CEST 2016 - end HrociWizardIntegrationClass 2ms

Fri Jul 08 18:29:29 CEST 2016 - end Data call 2ms

Fri Jul 08 18:29:29 CEST 2016 - start Data call

    Fri Jul 08 18:29:29 CEST 2016 - start HrociWizardIntegrationClass

        Fri Jul 08 18:29:29 CEST 2016 - end HRMSS_GET_ORGSTRUCTURE_AS_XML 171ms

    Fri Jul 08 18:29:29 CEST 2016 - end HrociWizardIntegrationClass 188ms

Fri Jul 08 18:29:29 CEST 2016 - end Data call 188ms

Fri Jul 08 18:29:29 CEST 2016 - start Data call

    Fri Jul 08 18:29:29 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:30 CEST 2016 - end /NAKISA/RFC_CHART 57ms

        Fri Jul 08 18:29:30 CEST 2016 - end /NAKISA/RFC_CHART 60ms

        Fri Jul 08 18:29:30 CEST 2016 - end /NAKISA/RFC_REPORT 401ms

    Fri Jul 08 18:29:30 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 1023ms

Fri Jul 08 18:29:30 CEST 2016 - end Data call 1023ms

Fri Jul 08 18:29:30 CEST 2016 - start Data call

    Fri Jul 08 18:29:30 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:30 CEST 2016 - end /NAKISA/RFC_CHART 55ms

        Fri Jul 08 18:29:30 CEST 2016 - end /NAKISA/RFC_CHART 54ms

        Fri Jul 08 18:29:31 CEST 2016 - end /NAKISA/RFC_REPORT 342ms

    Fri Jul 08 18:29:31 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 474ms

Fri Jul 08 18:29:31 CEST 2016 - end Data call 475ms

Fri Jul 08 18:29:31 CEST 2016 - start Data call

    Fri Jul 08 18:29:31 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:31 CEST 2016 - end /NAKISA/RFC_CHART 53ms

        Fri Jul 08 18:29:31 CEST 2016 - end /NAKISA/RFC_CHART 61ms

        Fri Jul 08 18:29:31 CEST 2016 - end /NAKISA/RFC_REPORT 359ms

    Fri Jul 08 18:29:31 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 497ms

Fri Jul 08 18:29:31 CEST 2016 - end Data call 497ms

Fri Jul 08 18:29:31 CEST 2016 - start Data call

    Fri Jul 08 18:29:31 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:31 CEST 2016 - end /NAKISA/RFC_CHART 53ms

        Fri Jul 08 18:29:31 CEST 2016 - end /NAKISA/RFC_CHART 52ms

        Fri Jul 08 18:29:32 CEST 2016 - end /NAKISA/RFC_REPORT 335ms

    Fri Jul 08 18:29:32 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 464ms

Fri Jul 08 18:29:32 CEST 2016 - end Data call 465ms

Fri Jul 08 18:29:32 CEST 2016 - start Data call

    Fri Jul 08 18:29:32 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:32 CEST 2016 - end /NAKISA/RFC_CHART 54ms

        Fri Jul 08 18:29:32 CEST 2016 - end /NAKISA/RFC_CHART 49ms

        Fri Jul 08 18:29:32 CEST 2016 - end /NAKISA/RFC_REPORT 356ms

    Fri Jul 08 18:29:32 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 484ms

Fri Jul 08 18:29:32 CEST 2016 - end Data call 484ms

Fri Jul 08 18:29:32 CEST 2016 - start Data call

    Fri Jul 08 18:29:32 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:32 CEST 2016 - end /NAKISA/RFC_CHART 62ms

        Fri Jul 08 18:29:32 CEST 2016 - end /NAKISA/RFC_CHART 54ms

        Fri Jul 08 18:29:33 CEST 2016 - end /NAKISA/RFC_REPORT 332ms

    Fri Jul 08 18:29:33 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 472ms

Fri Jul 08 18:29:33 CEST 2016 - end Data call 472ms

Fri Jul 08 18:29:33 CEST 2016 - start Data call

    Fri Jul 08 18:29:33 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:33 CEST 2016 - end /NAKISA/RFC_CHART 53ms

        Fri Jul 08 18:29:33 CEST 2016 - end /NAKISA/RFC_CHART 53ms

        Fri Jul 08 18:29:33 CEST 2016 - end /NAKISA/RFC_REPORT 313ms

    Fri Jul 08 18:29:33 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 500ms

Fri Jul 08 18:29:33 CEST 2016 - end Data call 500ms

Fri Jul 08 18:29:33 CEST 2016 - start Data call

    Fri Jul 08 18:29:33 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:33 CEST 2016 - end /NAKISA/RFC_CHART 69ms

        Fri Jul 08 18:29:34 CEST 2016 - end /NAKISA/RFC_CHART 55ms

        Fri Jul 08 18:29:34 CEST 2016 - end /NAKISA/RFC_REPORT 343ms

    Fri Jul 08 18:29:34 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 490ms

Fri Jul 08 18:29:34 CEST 2016 - end Data call 491ms

Fri Jul 08 18:29:34 CEST 2016 - start Data call

    Fri Jul 08 18:29:34 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:34 CEST 2016 - end /NAKISA/RFC_CHART 53ms

        Fri Jul 08 18:29:34 CEST 2016 - end /NAKISA/RFC_CHART 52ms

        Fri Jul 08 18:29:34 CEST 2016 - end /NAKISA/RFC_REPORT 338ms

    Fri Jul 08 18:29:34 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 464ms

Fri Jul 08 18:29:34 CEST 2016 - end Data call 465ms

Fri Jul 08 18:29:34 CEST 2016 - end setorgchartdirectory 5704ms (SAP Data: 5413 ms) (RFC: 4619 ms)

Fri Jul 08 18:29:39 CEST 2016 - start expandgroup

Fri Jul 08 18:29:39 CEST 2016 - start Data call

    Fri Jul 08 18:29:39 CEST 2016 - start HrociWizardIntegrationClass

        Fri Jul 08 18:29:39 CEST 2016 - end HRMSS_GET_ORGSTRUCTURE_AS_XML 166ms

    Fri Jul 08 18:29:39 CEST 2016 - end HrociWizardIntegrationClass 176ms

Fri Jul 08 18:29:39 CEST 2016 - end Data call 177ms

Fri Jul 08 18:29:39 CEST 2016 - start Data call

    Fri Jul 08 18:29:39 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:39 CEST 2016 - end /NAKISA/RFC_CHART 55ms

        Fri Jul 08 18:29:39 CEST 2016 - end /NAKISA/RFC_CHART 52ms

        Fri Jul 08 18:29:39 CEST 2016 - end /NAKISA/RFC_REPORT 349ms

    Fri Jul 08 18:29:39 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 479ms

Fri Jul 08 18:29:39 CEST 2016 - end Data call 480ms

Fri Jul 08 18:29:39 CEST 2016 - end expandgroup 731ms (SAP Data: 655 ms) (RFC: 622 ms)

Fri Jul 08 18:29:41 CEST 2016 - start expandgroup

Fri Jul 08 18:29:41 CEST 2016 - start Data call

    Fri Jul 08 18:29:41 CEST 2016 - start HrociWizardIntegrationClass

        Fri Jul 08 18:29:41 CEST 2016 - end HRMSS_GET_ORGSTRUCTURE_AS_XML 79ms

    Fri Jul 08 18:29:41 CEST 2016 - end HrociWizardIntegrationClass 82ms

Fri Jul 08 18:29:41 CEST 2016 - end Data call 82ms

Fri Jul 08 18:29:41 CEST 2016 - start Data call

    Fri Jul 08 18:29:41 CEST 2016 - start BAPI_SAP_OTFProcessor_Chart

        Fri Jul 08 18:29:41 CEST 2016 - end /NAKISA/RFC_CHART 59ms

        Fri Jul 08 18:29:41 CEST 2016 - end /NAKISA/RFC_CHART 53ms

        Fri Jul 08 18:29:42 CEST 2016 - end /NAKISA/RFC_REPORT 353ms

    Fri Jul 08 18:29:42 CEST 2016 - end BAPI_SAP_OTFProcessor_Chart 491ms

Fri Jul 08 18:29:42 CEST 2016 - end Data call 491ms

Fri Jul 08 18:29:42 CEST 2016 - end expandgroup 677ms (SAP Data: 573 ms) (RFC: 544 ms)

Fri Jul 08 18:29:45 CEST 2016 - start chartviewdetails

Fri Jul 08 18:29:45 CEST 2016 - start Data call

    Fri Jul 08 18:29:45 CEST 2016 - start HrociWizardDetailsIntegrationClass

        Fri Jul 08 18:29:45 CEST 2016 - end HRMSS_GET_ORGSTRUCTURE_AS_XML 103ms

        Fri Jul 08 18:29:45 CEST 2016 - end HRMSS_GET_ORGSTRUCTURE_AS_XML 72ms

    Fri Jul 08 18:29:45 CEST 2016 - end HrociWizardDetailsIntegrationClass 181ms

Fri Jul 08 18:29:45 CEST 2016 - end Data call 181ms

Fri Jul 08 18:29:45 CEST 2016 - end chartviewdetails 255ms (SAP Data: 181 ms) (RFC: 175 ms)

Folks, kindly refrain from using "text speak", this is a professional website (see ROE document and this blog).

@OP - you might want to post the screenshots or some code samples. Sorry but your text is very difficult to understand. Some words seem to be missing and I'm actually quite confused what exactly are you referring to as "matchcode". I really admire Sandra's and Max's superior translation abilities.

Hi SAP's gurus

I know that versión of SAP Portal (EP), I can find out in System Information or htt://<server>:<port>/sap/monitoring/ComponentInfo

But, list of components, what is the component name for SAP Portal?

I need to know the version & path level about my SAP Portal.

I'd appreciate with your help.

Best Regards,

Victor Carmona

Agree with what you've said.

Users are not able to create index on the global temporary tables. It looks like they can but they have no effect. Only the create table statement is used for the underlying temp table.

So

create global temporary table xxx ( i int primary key )

will create an index that can be used.

We're only aiming to use where we would have used @table variables and more usefully in C# Connection Pools.

Note: I renamed a global temporary table and soon afterwards the server crashed - not sure if the 2 things are connected - so will try this again.

Amit,

For a DR/HA/backup IQ site, you will need SF (standby/failover) licenses.  If IQ was bought from SAP those should be included.  If you purchased IQ from Sybase then the SF licenses are fee based.

Internal to IQ, a DR site can be created by simply using the BACKUP and RESTORE commands.  You would BACKUP the IQ primary, copy/ftp the files to the DR site, then perform a RESTORE.  This can be will full or incremental backups.

Most customers leverage something we call Nonstop IQ.  In this model, we leverage storage level replication to maintain the primary and secondary IQ sites.

In any scenario, the secondary site is not up and running.  There are some situations where we can start the secondary site to performa some actions, but this is very rare and requires intimate knowledge of the  underlying storage and its replication technology.  Some storage systems would overwrite the copy while others would fork a temporary copy and remove it once the task was done.

The SF licenses only allow for the secondary site to be used when the primary site is down.  If you want to use both sites for queries, then they would both require production licenses.

There is no need to maintain licenses in the manner you describe.  When the secondary site comes online, it will use the SF licenses.  The production licenses are still tied to the primary systems.  If you wish to move the production instance back from the secondary to the primary site, the licenses are in place.  If the primary site is down and must be completely rebuilt, simply check in the licenses and check them out for the new primary site.  This would be a rare occurrence, though.

Mark

Hi Terence,

Ok the V_T365 looks fine.

How can I find the notifications categories defined (or how can I enter them)?

What are the next steps?

Thanks in advance,

Laura

hi Abhilash,

What’s new - starting with Crystal Server 2016:

•No longer sold by version (shows up as just “Crystal Server” on the price list)

•Windows and Linux version are delivered in the same license (previously separate)

•Now sold in block sizes of 1 User and 5 Sessions only

•Client tools are now included with the User license option - one Crystal Reports (CR), one Crystal Reports for Enterprise (CR4E), one Dashboard Design (DD) per User

•Crystal Reports, Dashboard Design, and Explorer are now supported with User and Session licenses (previously only CR was supported with Sessions)

•Lumira supported with User and Session licenses (previously only with User licenses)

•Publishing is included with User and Session licenses (previously separate or tiered)

•User maximum still at 100 Users, maximum sessions reduced from 250 to 50

Hi

I was more expecting something like

But my feeling is that your container is not filled correctly.

Can you please make a screen shot of your container ?Specially the table USLIST

Cheers

Stephane

Hi

You'll have to use the parenthesis

(

MaintenanceOrder.Order type = PM01  OR

MaintenanceOrder.Order type = PM02  OR

MaintenanceOrder.Order type = PM03 

)                                                                       AND

MaintenanceOrder.Plant         = 5122

Cheers

Stephane

Hi Mistry,

Thanks for being response. Actually I would like to say that, suppose I create condition types like following:

• Condition Type for Base Price: ZK10
• Condition Type for Material Discount: ZK11
• Condition Type for Customer discount: ZK12

Normally we do create condition table & Access Sequence for every condition type individually. My question is If I create a single Access Sequence and under that if I assign my 3 condition table that I created for condition type then how those condition table will relate to my Condition type? Suppose:

• Table 670: Created for Base Price
• Table 671:Created for Material Discount
• Table 672: Customer Discount

Now all the above table suppose I assigned in a Acc.Seq. ZBAS. So how system will find that Condition Table 670 is for condition type ZK10 i.e. Base Price.

SAP BusinessObjects Design Studio

Release 1.6 SP1 Patch 2 (Version: 16.1.2)

Source: Relational database, thru UNX

my Initial Application settings:

All my Datasources have "load in script" set to True. Merge Prompts is set to False. Force Prompts on startup is also set to false.

I have a territory prompt that loads a dropdown prompt and  i capture the first value of the dropdown and pass it as a setvariablevalueExt to remaining report queries. [ my territory prompt dropdown has values like "AUS - ABC - 1234"]

1. I wanted to avoid "setvariablevalueExt" and use "setFilter" but if i do so (say, my tables have huge data) and try to create queries without any filters and include all columns required to be filtered into select. Now if i try to "edit initial view" or load a chart, it takes too much time and many times, it errors out or times out. hence i added prompts and tried to set them using "setvariablevalueExt". Is there a workaround or a better way of doing this.

2. my on load script:

// hide prompts panel

DIALOG_CONTAINER.setVisible(false);

// load Territory prompt Query and initialize Territory Prompt

APPLICATION.loadDataSources(DS_TERRITORY);

DROPDOWN_TERRITORY.setItems(DS_TERRITORY.getMemberList("_eaHEdbh0EeWuS70gbqxHFA", MemberPresentation.TEXT, MemberDisplay.TEXT, 800));

// capture the first territory value

var firstTerritoryValue = DROPDOWN_TERRITORY.getSelectedValue();

// load data sources

APPLICATION.loadDataSources([DS_PRD_KPIS, DS_PRD_TREEMAP]);

// setting Variables

DS_PRD_TREEMAP.setVariableValueExt("pmSelect Territory", firstTerritoryValue);

DS_PRD_KPIS.setVariableValueExt("pmSelect Territory", firstTerritoryValue);

// Set KPI Values

var gro_prd = DS_PRD_KPIS.getData("_ObIFgc7sEeWmlZgk6MSEDA", {}).value;KPI_GRW_PRD.setText(Convert.floatToString(gro_prd,"#,###"));

var decln_prd = DS_PRD_KPIS.getData("_Oa7RMc7sEeWmlZgk6MSEDA", {}).value;KPI_DECLN_PRD.setText(Convert.floatToString(decln_prd,"#,###"));

This seems to work fine without any script errors. Even though I'm loading 2 datasources i'm populating only 2 text items to keep things simple.

I have a popup container having territory prompt. After loading the initial screen, i click on prompts show button and change territory value and click "OK" button.

My "OK" button script:

// capture the selected territory value

var TerritoryValue = DROPDOWN_TERRITORY.getSelectedValue();

// setting Variables

DS_PRD_KPIS.setVariableValueExt("pmSelect Territory", TerritoryValue);

DS_PRD_TREEMAP.setVariableValueExt("pmSelect Territory", TerritoryValue);

// Set KPI Values

var gro_prd = DS_PRD_KPIS.getData("_ObIFgc7sEeWmlZgk6MSEDA", {}).value;KPI_GRW_PRD.setText(Convert.floatToString(gro_prd,"#,###"));

var decln_prd = DS_PRD_KPIS.getData("_Oa7RMc7sEeWmlZgk6MSEDA", {}).value;KPI_DECLN_PRD.setText(Convert.floatToString(decln_prd,"#,###"));

Now this mostly doesn't work bust strangely works sometimes. Mostly i get a prompt pop up window asking to select territory prompt values (screenshots attached).

I have referred below posts and followed the same steps w.r.t. setting variables and passing prompt selections but still i'm getting errors:

post 1: Things to be noted to improve performance of SAP Design Studio Application

http://scn.sap.com/community/businessobjects-design-studio/blog/2015/05/19/things-that-to-be-noted-to-improve-performance-of-sap-design-studio-application

Improving Initial Load of Dashboard:: Suggests to avoid setvariablevalueExt but if do so, how will i set "edit initial view". This never loads for me due to data size of the tables. I can limit the data only by adding prompts but then i will end up using setvariablevalueExt method to filter latter on.

post 2: Optimize the performance of your SAP BusinessObjects Design Studio solutions – tips and tricks

http://scn.sap.com/community/businessobjects-design-studio/blog/2013/11/29/optimize-the-performance-of-your-sap-businessobjects-design-studio-solutions-tips-and-tricks

followed the suggestions for this post:

“Load in Script” = True

DS_1.loadDataSource();

DS_1.SetVariableValue  method to set variable value captured from dropdown prompt

post 3: Difference in execution logic of setVariableValue

http://scn.sap.com/thread/3917915

This post helped but still having issues in my application and thus need help.

Followed option A mentioned in this post excluding DS_2.reloadData() method. Only change in my application is setVariableValue method doesnt work (application crashes) but when setVariableValueExt is used, it runs fine though the filtering sometimes works and sometimes not.

post 4: How to set Filter default display value as selected value

http://scn.sap.com/thread/3421890

This post was also helpful as it clears some questions I had.

This post mostly explains cascading promtps and use of setFilter. I almost truncated by tables so as to contain < 1000 rows from 20M and tried "setFilter" method instead of using variables and that works fine. But I cannot reduce data in tables everytime i need to add queries or change any initial settings.

Thanks,

Srikanth