HANA based BW Transformation - SAP Notes

Torsten_ · ‎06-09-2016

2462279 A1 SAP Notes

Last change on 02/14/2018

This blog provides an overview of the most important SAP notes regarding the topic BW transformation and HANA processing mode. This blog is part of the blog series HANA based BW Transformation.

From today (02/14/2018) we are collecting all new SAP notes in the consulting SAP Note:

2603241 - Overview and summary of the most important SAP Notes in the context of BW transformations ...

This SAP Note provides an Excel spreadsheet with all SAP Notes for BW 7.50 and BW/4.

The Excel spreadsheet can be used to filter SAP Notes related to a specific Release / SP.

We do not maintain the below list further on!

-------------------------------------------------------------------------------------------------------------------------------------

BW 7.40

BW 7.50

BW/4 HANA

Data Packaging

Cross-Release Notes

Special Notes (not general mandatory)

Consulting Notes

HANA Notes

A1.0 General Notes

2057542 - Recommendation: Usage of HANA-based Transformations

2230080 - Consulting: DTP: Out of memory situation during 'SAP HANA Execution' and the 'Request by R...

2329819 - SAP HANA execution in DTPs (Data Transfer Processes) - Optimizations (Added on 09/21/2016)

A1.1 BW 7.40

A1.2 BW 7.50

A1.2.1 Additional notes (BW 7.40 and 7.50)

2365543 - Error in Transformation and missing checks (Added on 09/20/2016)

2368206 - Error in Transformation with expert script (Added on 09/20/2016)

2357761 - 740 SP16: Incorrect aggregation behavior for Cube like ADSOs updated using Expert Routine/... (Added on 09/21/2016)

2376725 - 750SP6: Deletion of AMDP script does not delete the AMDP class (Added on 10/12/2016)

2353551 - SAP BW 7.50 (SP06) Transport of Transformation does not work (Added on 10/12/2016)

2326847 - SAP BW (ABAP) 7.50 (SP05) error when you activate a transformation with script (Added on 10/12/2016)

2365713 - 750SP6: Minor problems in Transformations with HANA Scripts (Added on 10/12/2016)

2366567 - Transitive attributes in Transformation (Added on 10/12/2016)

2374635 - SAP BW / SAP BW/4HANA wrong messages on execution check; missing checks (Added on 10/12/2016)

2404315 - SAP BW / SAP BW/4HANA (ABAP): check for runtime not work correct (Added on 03/31/2016)

2365508 - SAP HANA based currency conversion: High accuracy (Added on 11/15/2016)

2412904 - InfoObject time columnview does not exist, if the InfoObject is not flagged as InfoProvide... (Added on 03/15/2017)

2442579 - 750SP8: Errors during after import of Transformation with Individual AMDP scripts (Added on 03/15/2017)

2359959 - Delete table RSDHA_009B_TMP entries (Added on 03/29/2017)

2436433 - DTP execution does not allow mixed scenarios (Added on 04/11/2017)

2487617 - 740SP18: Ambiguous mapping for Units and Currencies in transformation having currency/unit... (Added on 06/27/2017)

2401080 - 74017:Changing Batch manager settings of a DTP Creates a new HANA Transformation (Added on 07/24/2017)

2453778 - 750SP8: Error during import of Transformations having AMDP Scripts (Added on 07/24/2017)

2410814 - 750SP7: Error in import of DTP having corresponding Transformation as HANA Exper Script (Added on 07/24/2017)

2398869 - 750SP7: Transformation with Invalid Runtime Status can be activated (Added on 07/24/2017)

2392032 - 750SP7: Error in import of transformation with AMDP scripts (Added on 07/24/2017)

A1.3 BW/4 HANA

A1.3.1 Additional notes (BW/4 HANA)

2484713 - Error during transport - changes in routines are not transferred (Added on 06/09/2017)

2491221 - ABAP routines (expert routines) are not handled correctly (Added on 06/21/2017)

2488772 - BW/41.0 SP5: Transport of Individual routines/formula doesn't work (Added on 06/14/2017)

2270825 - ADSO: Incorrect definition of reporting and extraction views (Added on 06/29/2017)

2480967 - Remodeling/dump during import (Added on 06/29/2017)

A1.4 Cross-Release Notes

2504644 - 740SP18: Incorrect aggregation behavior for Cube like ADSOs with fields updated using Expe...

2516952 - 750SP11: SAP HANA Execution: Invalid column index error when loading XL Texts using AMDP S...

2423215 - SAP HANA Processing: Non Supported Formulas in HANA Transformations

2505554 – Further Conversion Exits for SAP HANA-Sourcesystem

2530574 - 750SP10: SAP HANA Execution: Transport of transformation which can be executed in HANA end...

2534347 - 750SP10:SAP HANA Execution: Problems in Transformation with Target as Text of Charateristi...

2554846 - 750SP11: ABAP Runtime errors happen during generation of BW Calculation Scenario

2554952 - 750SP11:SAP Hana Execution: Error in push down of transformation when field PERIV in sourc...

2555107 - SAP HANA Execution: Support XXL Attributes in ADSO

2558465 - SAP HANA Execution: Check Availability

2565655 - SAP HANA Execution: Use of XXL InfoObject as target field within a transformation

2462861 - Data Packaging API for DTP Extraction with packaged/parallel processing: Corrections for N...

2511520 - Wrong Data in DTP Extraction with packaged/parallel processing

2502376 - DTP Extraction on ADSO or HANA DataSource terminates with SQL Error b...

2462279 - Packaging API - Sort order for DTP Semantic groups ignored

2564586 - SAP HANA Execution: Enhancing error handling for DTP execution - II (Added on 11/22/2017)

2561897 - SAP HANA Execution: DTP execution uses conversion exit based on source mapping (Added on 11/22/2017)

2563203 - 750SP11: SAP Hana Execution: DTP not HANA Execution Enabled (Added on 11/22/2017)

2416745 - Check of Transformation result in invalid runtime (Added on 01/08/2018)

2569553 - Missing Records when Extracting from DataStore Objects or HANA DataSources (Added on 01/10/2018)

2588204 - SAP HANA Execution: Key figure aggregation with AMDP scripts (Added on 01/12/2018)

2588183 - 750SP12: SAP Hana Execution: Transformation from CHAR to NUMC gets wrong results in hana e... (Added on 01/12/2018)

2601945 - SAP Hana Execution: No records inserted into the target when target is database table with... (Added on 02/09/2018)

A1.5 Data Packaging

Former Member · ‎06-09-2016

Hi Torsten,

nice collection of notes (although I haven't checked only a bunch so far and the one for 7.5 SP4 is of course not yet available :wink: ).

Some of the links seem to point to only internal SAP servers (containing wdf.sap.corp).

Maybe you could adjust them either to the "old" links like "http://service.sap.com/sap/support/notes/2342343" or the new links (used in the Support Launchpad) like "https://launchpad.support.sap.com/#notes/2342343/E"?

with kind regards,

Philipp

Torsten_ · ‎06-10-2016

Hi,

thx for the hint.

I'd adjusted the list.

Torsten

former_member38077 · ‎10-01-2018

Hey Torsten,
a quick question whether the following scenario is supported:

We created a CDS view with input parameter like the one hereafter on ERP side:

@AbapCatalog.sqlViewName: 'ZBIPPORPTRTE'
@AbapCatalog.compiler.CompareFilter: true
@AccessControl.authorizationCheck: #NOT_REQUIRED
@EndUserText.label: 'TEST'

@Analytics: { dataCategory: #DIMENSION, dataExtraction.enabled: true }

define view ZBI_PPOR_I_TEST
with parameters p_aufnr:abap.char( 12 )
as select from afpo

{
// Key
key afpo.aufnr,
key afpo.posnr,

afpo.matnr,
afpo.kdauf,
afpo.kdpos,
afpo.projn,
afpo.verid,
afpo.berid,
afpo.pwerk,
afpo.plnum,
afpo.wemng,
$parameters.p_aufnr as p_test

} where afpo.aufnr = $parameters.p_aufnr ;

Now on BW side we created a a DTP which makes use of the input parameter in the DTP filter.

Unfortunately it does not work: We ' re getting following messages:

The parser produced the error: "ZBI_PPOR_I_TEST" is a database entity with parameters, but a "(" ismissing after the name.

Message no. SODQ666

The parser produced the error: "ZBI_PPOR_I_TEST" is a database entity with parameters, but a "(" ismissing after the name.

Message no. SODQ666

Any idea? We are running the CDS views for extraction and trying to push down filter as far as possible

Regards, Thomas

Torsten_ · ‎10-02-2018

Hi,

I’m not sure if I get your question right.

Do you using the CDS view as source within a DataSource and try to pass the CDS view parameter by using the DTP filter, right?

Did you created an incident for the issue?

I'm not sure which release/SP you are running. Did you checked this SAP note:

2495379 - ABAP CDS extraction and parameter

This note must be implemented in both system (source and BW)!

Torsten

former_member38077 · ‎10-02-2018

Hey Torsten,

thanks for the quick reply.

->Do you using the CDS view as source within a DataSource and try to pass the CDS view üarameter by using the DTP filter, right?

Yes, thats right. Basically our VDM consists of several CDS views. We 're trying to push down the filter as far as possible. This is why we gave it parameters a try.

BW is on 75 P12.

Is there any other suitable approach to filter the data as early as possible? Our perception is that regular DTP filters (which are offered by the datasource) are working on the full set of data. With other words: data is fully collected then filtered then extracted. This approach has of course some obvious drawbacks,

Regards, Thomas

j_aguirrefdez · ‎07-25-2019

Hi Thomas,

Maybe a bit late for your needs, but I have used a similar approach. I think the point is that you will have to use infopackage instead of the DTP. The parameter in the CDS creates a new entry for the filter that is mandatory and it's not displayed in DTP.

Regards,

Jorge.

hennie_misc · ‎03-01-2021

Hi Torsten,

thank you for this whole blog series. It is very useful.

I have a question relating to AMDP classes within HANA-Transformations. We located our business logic written in sql script within in one ABAP/AMDP class and call its methods from the actual generic ampd-method created by the transformation framework.

However when we make adjustments to the logic within our class the calculation scenario of transformation/DTP does not get updated/reactivated automatically (at least on qa/production). It is therefore necessary to activate transformation(s) and dtp(s) manually after importing the adjusted amdp-class.

Is there a valid reason for this behavior or is it worth opening an OSS?

Kind regards,

Henrik

Torsten_ · ‎03-01-2021

Hi,

I'm not sure if I understand your issue correct.

You've a own AMDP class (CL_CUSTOMER) and you'd implemented your business logic in a method (BUSINESS_LOGIC)within this class.

Means you've a database procedure called CL_CUSTOMER=>BUSINESS_LOGIC.

And in one AMDP method of the transformation (may be start routine /BIC/..._A=>GLOBAL_START) you call this method.

So far I'm right?

Within the CalcScenario of the transformation we are calling a database procedure (/BIC/..._A=>GLOBAL_START).

Up to now I don't see a reason why the CalcScenarion or the database procedure related to the transformation must be regenerated if you adjust your method!? That's only necessary fi the interface of the method is be changed.

I think an OSS message makes communication easier 😉
If you post the message number here, I'll have a look

Torsten

hennie_misc · ‎03-01-2021

Hi Torsten,

thanks for your quick reply.

It seems you've understood the issue. Only we implemented multiple field routines and have also used several infosources.

I will ask BASIS to open an OSS and let you know.

Thanks

Henrik

nublik · ‎10-13-2021

Hi Torsten,

We have a very serious problem, and we have installed and updated our BW on Hana to the maximum allowed, the error that appears is the following: "Analysis process can not be embedded in a transformation RSDHA056"

The problem is that a transformation that we had already created stopped working and it worked perfectly, a year ago we were able to create a normal and typical transformation created from RSA1 in SAP GUI from a HAAP to the attribute of an infoobject.

this normal and typical transformation that if it worked, stopped working suddenly, and now we get this error RSDHA056.

We have made the necessary updates in OS, kernel.
We have applied the latest SAP notes that correspond to our system. And nothing has worked, do you have any idea why we get this error?

I hope you can help us.

Thank you.

info about , that was created and is active

Evidence about that this DTP was executed , with HAAP source to populate an attribute of 0MATERIAL, and worked fine