SAP BW/HANA - Transaction RSPM_MONITOR (BW Process Monitor)

Hello,

You can use this transaction to see all BW processes of all statuses.
All the required selections are provided in this transaction

E.g., You can enter an ADSO and see all types requests performed on that ADSO such as data loads, Activations, deletions, selecting deletions, data remodeling requests. etc.,

SAP BW/HANA - Replicating or Removing BW Analysis Authorizations to HANA

Hello,

When you need to replicate or remove BW analysis authorizations to HANA.
You can simply run the below program with selections.
Enter the required details User IDs and List of BW Objects and execute the program.

RS2HANA_AUTH_RUN

SAP ABAP/HANA - Display DDL Source Codes in SAP GUI using ABAP Program

If you want to see the source code of DDL in SAP GUI without opening HANA Studio.

You can run this program. Eg. to see the source code of CDS view.

DEMO_SHOW_DDL_SOURCE

SAP HANA - Useful formulas for STRING operations

1. If you need a sub-string from starting of the value.

      leftstr("string value or field", < length of string >)

2. If you need a sub-string from ending of the value.

      rightstr("string value or field", < length of string >)

3. If you need a sub-string from the middle of the string.

     midstr("string value or field", < length of string >)

SAP - Finding Users list by using Role or Authorizations or profiles or any known data

You can use different reports available in SUIM transaction

SAP HANA - Transporting HANA objects using ABAP transport

Hello,

1. You can use transaction SCTS_HTA
2. Input or browse the Hana package and click on execute.
3. Choose the objects to transport and execute.
4. It will prompt to enter the Transport request details.
5. You can import the TR using STMS_IMPORT just like any other ABAP TR.

Thanks.

SAP HANA - Useful formulas for Date / Time / Month / Day / Year in Calculation View

Hi,

There is a function to extract desired parts from DATE and TIME.

Function name:

• component

Syntax:

• component(date, desired_value )

Usage:

• Value for desired_value argument may be int the range 1..6, the values mean year, month, day, hour, minute, second, respectively. 
• If a component is not set in the date, the component function returns a default value, 1 for the month or the day, 0 for other components. 
• You can also apply the component function to longdate and time types.

Examples :  You can use the below formulas.

• Today Date:   NOW( )
• Year from a Date:  COMPONENT ( NOW ( ) , 1 )

SAP BW - Not able to view output of Composite Provider - View or Procedure invalidated

This issue can be seen as below.

Whenever you encounter this type of issue, first you can try to create the index for composite provider records.

To create index, you can run program RSDDB_LOGINDEX_CREATE in SE38 for that composite provider.


Reason can be:

    1. These errors can be caused by inconsistencies persist in infoproviders.
    2. This is due to inconsistent column view or logical index in SAP HANA.


Thanks.

SAP BW - HANA - How to perform Delta Merge manually.

If you want to perform Delta Merge manually, You can use below ways.

   1. Using menu:  

1. In the Systems view, navigate to the table.
2. In the context menu of the table, choose Perform Delta Merge.
3. Choose OK.

   2. Using SQL: run the below SQL.

         MERGE DELTA OF '<table_name>'

To check the history of delta merge of a table... read more.

for more details on delta merge: http://sapway.com/WILLSYS/HANADB/deltamerge.pdf

SAP BW - Column store error: search error: [2750] indexMgr index not found

Column store error: search error: [2750] indexMgr index not found

you may face this while using calculation views as a data source in BW.

If you face this issue while running Infopackage, there can be an issue with index of any of the underlying source infoprovider.

Solution:

To create index, you can run program RSDDB_LOGINDEX_CREATE in SE38 for all composite providers which are used in source calculation view.


Reason can be:

    1. These errors can be caused by inconsistencies persist in infoproviders.
    2. This is due to inconsistent column view or logical index in SAP HANA.



Thanks.