Quantcast
Channel: SAP BW Powered by SAP HANA
Viewing all 146 articles
Browse latest View live

0EPM_CONT_DELV on B4/HANA not ready

$
0
0

For anyone out there, wishing to install and explore the EPM Demo on B4/HANA, take a quick look below

This pertains to the SAP B4/HANA 1.0 [Developer Edition] in the SAP CAL

I have not had a chance yet to test on other versions

FYI: This story does not have a happy ending

In short, I found 4 missing InfoObjects that will fail the complete activation, and give errors

If you get to the end in your efforts, and can find a way around, do let me know

 

What's in the box

Eclipse

Neon with BW Tools v1.15.2

Untitled2.png

Active InfoAreas

Untitled4.png

Active DataSources

Untitled5.png

BW

no BWDEVELOPER user, have to use user DEVELOPER

In eclipse use the Project "BW_A4H_001_developer_en_1"

no RSA1 - Modelling option, have to use Eclipse

SYSTEM->STATUS

Untitled7.png

License will run out after three months, and can be extended through the usual way

Example of transaction no longer support - RSD1

Untitled9.png

INSTALL BI CONTENT 0EPM_CONT_DELV

RSOR - BI Content

Choose Source System, and continue to find 0EPM_CONT_DELV - currently installed (not activated)

Untitled11.png

When collected for installing you may see the following immediate errors

Untitled12.png

This is due to the following InfoObjects not existing anywhere in the system

0D_NW_PCURR

0D_NW_PUNI

0D_NW_PRCUR

0D_NW_STUNI

 

They are required for some other 0EPM_CONT_DELV InfoObjects

 

"install", without need to change any further options

Untitled13.png

4 minutes later

Untitled14.png

Errors have occurred

 

New InfoAreas, i.e. 0EPM_CONT_DELV, under 0BWTCT, now visible in Eclipse

15.png

Under Key Figures, see the outcome of the missing InfoObjects

16.png

Amongst the objects which erred is Key Figures 0EPM_GAMT. It depends upon one of the missing InfoObjects, 0D_NW_PCURR, and is why the error occurred

17.png

The next task is to create new custom InfoObjects, for substitution the missing ones.

ZDNWPCURR will replace 0D_NW_PCURR Order Currency

ZDNWPUNI will replace 0D_NW_PUNI Order Unit

ZDNWPCUR will replace 0D_NW_PRCUR Product Currency

ZDNWSTUNI will replace 0D_NW_STUNI Standard Unit of Measure

 

In Eclipse, create a new InfoArea to organize custom objects

r/click over the BW Repository InfoArea area, and choose, New -> InfoArea, and create

18png.png

r/click over the new InfoArea, and choose New -> InfoObject… and create

19.png

Create InfoObject Unit ZDNWPCURR and Activate

20.png

21.png

IMPORTANT, due to a bug, try this

In BW, navigate to RSOSM– “Use BW Search on SAP HANA”, enter the InfoObject name, and execute the search.

22.png

If nothing is found, perform these steps.

In Eclipse, under the InfoObjects Dictionary area, change the Unit Type from the existing “Currency” to “Unit”, Activate, and back to “Currency”, and Activate.

23.png

In BW, perform the search again, and it should be found.

24.png

Continue on with the remaining InfoObjects

Create InfoObject Unit ZDNWPUNI and Activate

25.png

Create InfoObject Unit ZDNWPCUR and Activate

27.png

Create InfoObject Unit ZDNWSTUNI and Activate

29.png

 

 

Refresh the InfoArea, and all should be visible

31.png

 

Adjust Key Figures

Now substitute the missing InfoObjects with our custom InfoObjects for all the following Key Figures

32.png

 

0EPM_GAMT

 

Change  InfoObject 0D_NW_PCURR

33.png

 

To InfoObject ZDNWPCURR, and Activate

 

 

 

 

Do this for the remaining InfoObjects, taking care of the correct substitution

 

0EPM_NAMT use currency ZDNWPCURR

0EPM_PQTY use unit ZDNWPUNI

0EPM_PRICE use currency ZDNWPCUR

0EPM_TAMT use currency ZDNWPCURR

 

Adjust Characteristic

 

Also, the InfoObject Characteristic 0EPM_PRID requires adjusting

 

35.png

 

Attribute 0D_NW_PRCUR requires substituting for ZDNWPRCUR

Attribute 0D_NW_STUNI requires substituting for ZDNWSTUNI

Activation should resulting in the following

38.png

 

 

INSTALL TAKE 2 - BI CONTENT 0EPM_CONT_DELV

RSOR - BI Content

Collect the 0EPM_CONT_DELV once again, do not change, tick, or check anything, and "Install"

Fewer error messages, but an observation identifies the same missing objects are still getting in the way

A quick check will reveal the previously erred Key Figures are still ok, as you would expect, and have not been overwritten

42.png

 

In RSOR, I tried to activate, just the advanced DSO InfoArea 0EPM_ADSOS

Same errors occured

 

Then I tried to install an individual ADSO 0EPM_ADSO1

I did not receive the previous InfoObject errors, which I thought was promising46.png

However, I was not able to see the objects in eclipse, to fix up or otherwise, so that pretty much leaves me out of options.

47.png

 

 

Previously, RSA1 -> Modelling, would be used to inspect the Object in error, for a possible fix or cause analysis. However, with eclipse, I cannot see the object, so it’s the end of my story, for now.

 

 

If you have had the same experience, do share, as I am sure there would be many out there, just like me, keen to see this working, so we can explore further.

 

 

Thanks

Glen


0EPM_CONT_DELV on B4/HANA not quite ready

$
0
0

For anyone out there, wishing to install and explore the EPM Demo on B4/HANA, take a quick look below

This pertains to the SAP B4/HANA 1.0 [Developer Edition] in the SAP CAL

I have not had a chance yet to test on other versions

FYI: This story does not have a happy ending

In short, I found 4 missing InfoObjects that will fail the complete activation, and give errors

If you get to the end in your efforts, and can find a way around, do let me know

 

What's in the box

Eclipse

Neon with BW Tools v1.15.2

Untitled2.png

Active InfoAreas

Untitled4.png

Active DataSources

Untitled5.png

BW

no BWDEVELOPER user, have to use user DEVELOPER

In eclipse use the Project "BW_A4H_001_developer_en_1"

no RSA1 - Modelling option, have to use Eclipse

SYSTEM->STATUS

Untitled7.png

License will run out after three months, and can be extended through the usual way

Example of transaction no longer support - RSD1

Untitled9.png

INSTALL BI CONTENT 0EPM_CONT_DELV

RSOR - BI Content

Choose Source System, and continue to find 0EPM_CONT_DELV - currently installed (not activated)

Untitled11.png

When collected for installing you may see the following immediate errors

Untitled12.png

This is due to the following InfoObjects not existing anywhere in the system

0D_NW_PCURR

0D_NW_PUNI

0D_NW_PRCUR

0D_NW_STUNI

 

They are required for some other 0EPM_CONT_DELV InfoObjects

 

"install", without need to change any further options

Untitled13.png

4 minutes later

Untitled14.png

Errors have occurred

 

New InfoAreas, i.e. 0EPM_CONT_DELV, under 0BWTCT, now visible in Eclipse

15.png

Under Key Figures, see the outcome of the missing InfoObjects

16.png

Amongst the objects which erred is Key Figures 0EPM_GAMT. It depends upon one of the missing InfoObjects, 0D_NW_PCURR, and is why the error occurred

17.png

The next task is to create new custom InfoObjects, for substitution the missing ones.

ZDNWPCURR will replace 0D_NW_PCURR Order Currency

ZDNWPUNI will replace 0D_NW_PUNI Order Unit

ZDNWPCUR will replace 0D_NW_PRCUR Product Currency

ZDNWSTUNI will replace 0D_NW_STUNI Standard Unit of Measure

 

In Eclipse, create a new InfoArea to organize custom objects

r/click over the BW Repository InfoArea area, and choose, New -> InfoArea, and create

18png.png

r/click over the new InfoArea, and choose New -> InfoObject… and create

19.png

Create InfoObject Unit ZDNWPCURR and Activate

20.png

21.png

IMPORTANT, due to a bug, try this

In BW, navigate to RSOSM– “Use BW Search on SAP HANA”, enter the InfoObject name, and execute the search.

22.png

If nothing is found, perform these steps.

In Eclipse, under the InfoObjects Dictionary area, change the Unit Type from the existing “Currency” to “Unit”, Activate, and back to “Currency”, and Activate.

23.png

In BW, perform the search again, and it should be found.

24.png

Continue on with the remaining InfoObjects

Create InfoObject Unit ZDNWPUNI and Activate

25.png

Create InfoObject Unit ZDNWPCUR and Activate

27.png

Create InfoObject Unit ZDNWSTUNI and Activate

29.png

 

 

Refresh the InfoArea, and all should be visible

31.png

 

Adjust Key Figures

Now substitute the missing InfoObjects with our custom InfoObjects for all the following Key Figures

32.png

 

0EPM_GAMT

 

Change  InfoObject 0D_NW_PCURR

33.png

 

To InfoObject ZDNWPCURR, and Activate

 

Do this for the remaining InfoObjects, taking care of the correct substitution

 

0EPM_NAMT use currency ZDNWPCURR

0EPM_PQTY use unit ZDNWPUNI

0EPM_PRICE use currency ZDNWPCUR

0EPM_TAMT use currency ZDNWPCURR

 

 

Adjust Characteristic

 

Also, the InfoObject Characteristic 0EPM_PRID requires adjusting

 

35.png

 

Attribute 0D_NW_PRCUR requires substituting for ZDNWPRCUR

Attribute 0D_NW_STUNI requires substituting for ZDNWSTUNI

Activation should resulting in the following

38.png

 

 

INSTALL TAKE 2 - BI CONTENT 0EPM_CONT_DELV

RSOR - BI Content

Collect the 0EPM_CONT_DELV once again, do not change, tick, or check anything, and "Install"

Fewer error messages, but an observation identifies the same missing objects are still getting in the way

A quick check will reveal the previously erred Key Figures are still ok, as you would expect, and have not been overwritten

42.png

 

In RSOR, I tried to activate, just the advanced DSO InfoArea 0EPM_ADSOS

Same errors occured

 

Then I tried to install an individual ADSO 0EPM_ADSO1

I did not receive the previous InfoObject errors, which I thought was promising46.png

However, I was not able to see the objects in eclipse, to fix up or otherwise, so that pretty much leaves me out of options.

47.png

 

 

Previously, RSA1 -> Modelling, would be used to inspect the Object in error, for a possible fix or cause analysis. However, with eclipse, I cannot see the object, so it’s the end of my story, for now.

 

 

If you have had the same experience, do share, as I am sure there would be many out there, just like me, keen to see this working, so we can explore further.

 

 

Thanks

Glen

Open ODS View - How to Solve the Error - Fail to create scenario: [2950] User is not authorized

$
0
0

Hi All,

 

Good Day !!!!!!

 

 

Problem Statement - Open ODS View Authorization Error:

 

When we create ODS View on top of tables from external schema,

We might face "Insufficient Privilege" (Error: Fail to create scenario: [2950] User is not authorized) error during activation. 

In this blog, I have explained the cause and solution for this issue with one example.



System Details:


Assume BW application (DW1) is running on HANA database (HD1).

temp.PNG

From BW view,

"SAPDW1" schema will be considered as SAP BW schema and

"HDBUSER_1" schema (native HANA DB schema) will be considered as external schema.

 

 

System Version:

 

The version of the systems, which I used for below example.

 

BW:                                   7.40 SP11

HANA:                               1.0 SP10

Eclipse Modelling Tools:       1.13.3

 

 

Open ODS View Creation:


I am going to create ODS View "ZMS_ODS" on top of table "SALES" which is from "HDBUSER_1" schema.


Steps:


1. In eclipse, modelling perspective, connect SAP HANA system.


2. Navigate to "BW Modelling Tools" perspective and connect SAP BW system.


3. From BW system, attach SAP HANA system


4. Then create ODS View from BW system.

     Select "Semantics Type" as Facts

     Select "Source Type" as Database Table or View

     Type "DB Object" as  HDBUSER_1

     Type "DB Object Name" as SALES and

     Click "Finish"

      temp.PNG


5. Select "CUSTOMER_ID" and "PRODUCT_ID" as "Key Fields" and

    Select "ACTUAL_SALES" as "Key Figure".

    Check field properties (description, aggregation...), then activate the ODS View.

     temp.PNG

 

 

Problem Description:

 

Activation of ODS View will throw the error.

"column store error: fail to create scenario [2950] user is not authorized"

 

temp.PNG

 

 

Cause and Solution:

 

ODS View is BW object and It will interact with HANA DB using SAP<SID> user.

 

So, If we create ODS view on top of external table,

SELECT privilege on this external table should be granted to SAP<SID> user.

Our case, select privilege on "HDBUSER_1"."SALES" (external table) should be granted to "SAPDW1" (BW user).

 

The below SQL has to be executed to solve ODS View authorization issue.

GRANTSELECTONSCHEMA"HDBUSER_1"TO"SAPDW1"

 

After required privileges granted to BW user, Open ODS View is activated successfully.

created ODS view screenshot from "Eclipse Modelling Tools" and "SAP Logon GUI" have been attached below.

 

temp.PNG

 

Eclipse Modelling ToolsSAP Logon GUI
temp.PNGtemp.PNG

 

 

Data Preview of ODS View:

 

I checked the ODS View data from SAP BW system. It shows the data correctly.

 

SAP HANA: Table ("HDBUSER_1"."SALES")SAP BW: Open ODS View (ZMS_ODS)
temp.PNG

temp.PNG

 

Best Regards,

Muthuram

HANA Memory Consumption by BW Objects

$
0
0

Hi All,

 

Good Day !!!!!

 

We know M_CS_TABLES, M_TABLES to monitor about HANA RAM memory consumption by table wise.

But We can't find the information such as How much HANA Memory occupied by BW objects - Info Objects, DSO, Info cube, PSA, Change log.

 

This blog helps to identify HANA memory consumption by BW objects - Info Objects, DSO, Info cube, PSA, Change log.


1. Open the attached SQL document - HANA_MEMORY_CONSUMPTION_BY_BW_OBJECTS.sql


2. In the SQL statement, One small change has to be done. Replace String - SAPSID with your BW SCHEMA in all the places.

    Example:

     If your BW Schema is SAPBW1,

     When "SCHEMA_NAME" = 'SAPSID' --> When "SCHEMA_NAME" = 'SAPBW1'

   from"SAPSID"."RSTSODS" -->   from"SAPBW1"."RSTSODS"


3. Execute the SQL statement and User Defined Function - HANA_MEMORY_CONSUMPTION_BY_BW_OBJECTS will be created on User Schema.


4. Call UDF Function and It will show HANA Memory occupied by BW objects - Info Objects, DSO, Info cube, PSA, Change log

    Select * from"<User_Schema>"."HANA_MEMORY_CONSUMPTION_BY_BW_OBJECTS" ()

     temp.PNG

    

 

It will help us to monitor HANA Memory occupied by all BW objects and to take decisions like PSA_Cleanup and Changlog_Cleanup.

 

The SQL further can be enhanced like calculating

1. ADSO Memory consumption,

2. Info Objects Memory Consumption by types Master Data, Text, Hierarchy

 

Regards,

Muthuram

0IC_C03 Data Load Steps in BW on HANA

$
0
0

Steps to load 0IC_C03 - Material Stocks/Movements InfoCube in BW on HANA

 

 

1. In a small down time interval lock/stop all users/postings in ECC at that time.

         Eg: The day is 09-23-2016 @ 11:00:00 AM).

 

2. STOP V3 JOB’s for 2LIS_03_* DataSources in ECC.

 

3. Clear Setup tables, RSA7, SMQ1 in ECC and InfoCube data in BW.

 

4. Execute Tcode MCNB in ECC, under Data destination Info tab, select 2LIS_03_BX DataSource.

 

5. Under Data source Info select All Stock Including - non valuated stocks).

 

6. At the same time (parallel) use Tcode OLI1BW in ECC and give the Posting date range from 01-09-2016 to 23-09-2016. This is

   for 2LIS_03_BF Load.

 

7. And also you can perform another activity, use Tcode OLIZBW in ECC and give the Company code and Posting date range from

   01-09-2016 to 23-09-2016. This is for 2LIS_03_UM Load.

 

   If you have multiple company code, repeat the step 6 for all company codes using the same Posting date range selection.

 

   Note:

 

   Step 5 and Step 6 can also perform once the 2LIS_03_BX data load is completed, but to save and utilize ECC down time, we can

   do in parallel. It depends on person to person and project to project and also the length of ECC down time.

 

 

8. Once Step 3 job is completed in ECC then load the data to BW till PSA using InfoPackage using “Generate Initial Status”

   under Update Tab. This is for 2LIS_03_BX Load.

 

9. Once the PSA load is success then load data to 0IC_C03 Cube using DTP, before loading data, check the “Extraction” tab in

   DTP, under Extraction tab Extraction Mode = “Initial Non-Cumulative for non-Cumulative values”.

 

    Set this option in DTP and load the data into InfoCube.

 

10. No compression is required because it’s HANA, you can’t find “Marker update” option in 0IC_C03 InfoCube.

 

11. Quickly you can validate the data by comparing data using Tcodes in ECC MB52 or MB5B and simple BEx report.

 

12. Once Step 5 job is completed in ECC then load the data to BW till PSA using InfoPackage using “Initialize Delta Process, with       Data Transfer” under Update Tab. This is for 2LIS_03_BF Load.

 

13. Once the PSA load is success then load data to 0IC_C03 Cube using DTP, before loading data, check the “Update” tab in DTP, under     Parameters of the InfoCube tab, CHECK “Historical Transactions” for history loads, because we are loading history data from         1st September 2016 to 23rd September 2016 to set the DELTA pointer in ECC.

 

    No compression is required because it’s HANA.

 

    Note:

   

    Once you load all history data, then UN-CHECK this option for delta loads.

    Once Step 6 job is completed in ECC then load the data to BW till PSA using InfoPackage using “Initialize Delta Process, with       Data Transfer” under Update Tab. This is for 2LIS_03_UM Load.

 

14. Once the PSA load is success then load data to 0IC_C03 Cube using DTP, before loading data, check the “Update” tab in DTP, under     Parameters of the InfoCube tab, CHECK “Historical Transactions” for history loads, because we are loading history data from         1st September 2016 to 23rd September 2016 to set the DELTA pointer in ECC.

 

    No compression is required because it’s HANA.

 

    Note:

    Once you load all history data, then UN-CHECK this option for delta loads. 

 

15. Once data loads are completed then check the BW Data with MB5B/MB51/MB52 Tcodes in ECC, it will match.

 

16. To perform all the above steps in small ECC down time period, you must practice these steps in Quality/Test system prior

    to implement in Production system to avoid confusion and get confidence. And also validate the data in Quality/test system

    using different BEx report in BW and MB5B/MB51/MB52 Tcodes in ECC.

 

17. Once Delta Pointer is set in ECC then load all history data using the above steps or you can start delta loads,

    I prefer first load all history data in weekends and then continue DELTA loads.

 

18. After all history loads are done then schedule V3 jobs for 2LIS_03_* DataSources using LBWE Tcode in ECC and continue

    DELTA Loads in BW.

 

    Note:

 

    UN-CHECK “Historical Transactions” option in DTP for BF and UM DataSource delta loads.

SAP S/4HANA & SAP BW Data Integration via ODP-ABAP CDS Views

$
0
0

Hi All,

 

Have a Good Day !!!!!!!!

 

ABAP CDS Views, which is S/4 HANA New and Advanced Modeling Object.

So many SAP documents and SCN links are available about

What is ABAP CDS  View?, How to create it?, It's Features and Benefits.

I have listed few links below for reference which will be useful to understand above things.

 

http://help.sap.com/hana/SAP_HANA_Core_Data_Services_CDS_Reference_en.pdf

 

https://help.sap.com/abapdocu_750/en/abenddic_cds_views.htm

 

http://scn.sap.com/community/abap/eclipse/blog/2014/02/04/new-data-modeling-features-in-abap-for-hana

 

https://wiki.scn.sap.com/wiki/display/ABAP/CDS+-+Core+Data+Services

 

 

In S/4 HANA, We have Embedded BW also and We can use it Operational Reporting.


But We need one complete analytical suite in the following scenarios

i.       Multiple ECC Systems

         (Example: Separate ECC Systems for America, Europe and Asia Pacific)

ii.      If we have Data from Non-SAP Applications and Multiple Source Systems

          (BODS, 3rd Party Databases - Oracle, DB2, Teradata, MSSQL, ....)

iii.     To Maintain Historical Data

iv.     Extensive Analytical Reporting Usage

v.      Implement Planning Functions


For this above scenarios,

S/4 HANA System and BW on HANA - Both system needed in Enterprise Landscape.

temp.PNG

(Ref: Open SAP - BW 7.5 Powered by HANA Course)


CDS views are Integration between S/4 HANA system and BW system.

There are two options available for BW and S/4 HANA Integration.


i.     Virtual data integration:  

          Create Open ODS Views (BW) directly on top of CDS views (S/4 HANA)

ii.    ETL load:

          Extract data from SAP S/4HANA to SAP BW using CDS Views via ODP source system type.


In this blog,

I am going to explain about how to integrate BW and S/4 HANA systems by "ETL load" method.

 

In S/4 HANA Source System, In-built ABAP CDS View are there for almost all the functionalities.

I have taken Simple ABAP CDS View Model - IMATTYPE (Material Type), Which have 7 records.

In this Integration exercise, This CDS View Output has to be extracted to BW on HANA system.

 

 

 

Steps Involved in ETL Load - Extraction Process:

 

1.      Data Flow diagram,

          which is explaining Extraction process between S/4 HANA system and BW on HANA System:

         temp.PNG

 

2.           Create New Source System (Source S/4 HANA) Under "ODP-ABAP CDS Views".

               In Connection Parameter, In Target Host Field,

               Enter S/4 HANA Application Server Host Name and Instance Number.

               In Log on Security - Enter S/4 HANA User Name and Password and Check the Connection.

               After Successful Connection, Save it.

               New Connection will be created and will be displayed under ODP - ABAP CDS Views.      

               temp.PNG

                        

3.          In Data Sources Node, Create New Data Source on top of S/4 HANA CDS View – IMATTYPE

             Enter "IMATTYPE" in Operation Data Provider field and select the Type as Master Data Attr.

             Provide Data Source Name as "ZABAP_CDS_EXTRACT_01" and create and Activate it.

              temp.PNG

                 Data Source "Material Type ABAP CDS View Extraction (ZABAP_CDS_EXTRACT_01)":

               temp.PNG

 

4.           Load the data to this data source using Usual Info package execution.

              Verify the data in Data source against S/4 HANA CDS View output.

  

Source S/4 HANA - CDS View OutputTarget BW - Data Source Output
                         temp.PNGtemp.PNG

.              

 

 

My Observations:

 

Few of My Observations from this Exercise,

 

i.            We can customize Existing ABAP CDS Views and create New CDS Views in S/4 HANA.

              This CDS Views also could be extracted same as above method.

 

ii.           In Source System, ABAP CDS views can be exposed to Bex Query and

              Operation Reporting will be created on top of BEx.

              Reference:http://scn.sap.com/community/bw-hana/blog/2016/02/10/expose-cds-views-to-sap-bw-bex-query-designer#comment-699890

 

iii.           In Virtual Data Integration (BW - S/4 HANA) Method,

               Two Systems are connected via HANA-HANA Smart Data Access (SDA) Connectivity.

               This ODP - ABAP CDS View Extraction is based on NetWeaver RFC Connectivity.

 

iv.          In this ETL Load BW-S/4 HANA Integration (ODP - ABAP CDS View Extraction),  

              In Info Package, Only "Full Load" Option is available. "Delta Load" Option is not available.

 

 

Thanks & Regards,

Muthuram

Viewing all 146 articles
Browse latest View live