Quantcast
Channel: SCN : All Content - SAP S/4HANA
Viewing all 882 articles
Browse latest View live

Getting Started with S/4 HANA Embedded Analytics

$
0
0

As you continue with your journey towards Digital Transformation and analyze the innovative S/4 HANA solution, I would like to present how in this journey you could leverage the benefits of the embedded analytics, one of the cornerstone of our new product. In this blog I would briefly touch upon how embedded analytics adds value to your digital enterprise, explaining the evolution of the embedded analytics architecture and the components which makes up the “Embedded Analytics” Solution.

 

Digital Transformation is stretching the limits of the existing enterprise systems and almost bringing it to the point of breaking. Order volumes and transactions handled in enterprise systems are increasing at least by factor of 10, as companies are reinventing their B2B models to B2B2C and would like to serve more customers directly. As organizations start to serve more customers directly we are set to see an exponential rise in the number of transactions which are processed daily in the enterprise systems. While order volumes are on the rise, the cycle times required to serve this order is compressed. Customers are pushing for lower the cycle times and this becomes critical in a global supply chain when the components are sourced across multiple geographies.

 

As companies are dealing with an increasingly complex supply chain which becomes more diverse with time, the rising demand of the customers and the intense competition now makes it imperative that we have systems which can be “Live”. We need insights instantaneously so that most optimal decision is possible at the right time with the right context and in real time. This becomes difficult to achieve with the current architecture of the enterprise systems where we have artificial separation between the transactional systems and the analytical systems.  Analytics today needs to be integrated with the moment of truth or at the point of transaction. No longer is it viable or competitive to maintain separate systems for transaction and analytics. We need to have the analytics embedded in the transactions and be able to react to any insight with an action in the transactional system at real time. Combining all these trends we see the genesis of the “Embedded Analytics”.

 

Embedded Analytics has its origins in two dominant themes namely the Fiori User Experience and the merging of the transactional system (OLTP) and the analytical (OLAP) systems. The central theme of any analytical application in S/4HANA begins with the context of the persona or the role of the end user. Continuing our simplification journey with user experience for the end user, we bring all the relevant information and the context required by the role in a personalized, visual and a responsive Launchpad.

 

In case you are interested in the further details, I would like to direct your attention to recording of TechEd presentation hosted by S/4HANA Embedded Analytics Product team.  (Embedded Analytics)


So how does the embedded analytics differ from the traditional analytics? For starters we have a role based Fiori Launchpad for the end user where the user is able to view his transactional and the analytical apps that are most frequently used and is able to seamlessly navigate between transactional and an analytical system which comes from a single repository. The role based access provides the user with the relevant context for decision making and finally the end user would be able to complete the Insight to Action, from one system in real time without the need for data replication.

 

In the figure below you would find KPI tiles which are available in a Fiori Launchpad, which in a visual manner would highlight the threshold breaches, current performance and an up to date view of the business in real time. From this I could analyze further the details in a drill down application of my choice and finally take an action resulting in the resolution of the issue.

 

I2A.png

Taking a step further I would like to detail the multiple use cases which are part of S/4 HANA Embedded Analytics. The enabler of the embedded analytics is the Virtual Data Model realized in S/4 HANA by Core Data Services. The CDS views could be consumed by the generic BI clients or you could use consume them via Smart Business KPI Modeler to develop Analytical applications based on oData protocol. Integration with the BW is also available and CDS view forms an integral part of the search.

 

usecases.png

 

In the figure below you would see the high level logical model for the embedded analytics. The virtual data model concept is realized by the CDS (Core Data Service) views which are built in the ABAP layer. The CDS views be exposed as the oData which can be rendered in a browser. Modeling tools like Smart Business allows consumption of the oData exposed by the CDS views and generation of KPI tiles and drill down application adhering to the Fiori design principles in a codeless manner. Also the CDS views can be consumed by the InA protocol for the BI suite of products. Additionally if you need to create a custom analytical application you could make use of the oData exposed via the CDS views.     

 

HLArc.png

 

 

To address the need of the end user, key user involved in the modeling of KPIs and drilldown and the power users SAP provides a number of tools as part of the S/4 HANA Embedded Analytics. For the end user SAP provides the SAP Smart Business Cockpits with predefined content for roles in Finance and Logistics and an array of multi-dimensional reports and analytical Fiori Apps.  For the key users tools like Query Browser and KPI Modeler allows the configuration of the KPIs, Reports and Drill-down Application. Additionally tools like Query Designer and ABAP on Eclipse helps in the modelling and extension of the CDS Views.  The list of analytical application available with S/4 HANA is available in the Fiori Reference App. The picture below indicates integration of the S/4 Hana Embedded Analytics with the other tools in SAP Analytics portfolio.  If you would like to look deeper into the S/4 Analytics integration with SAP BW I would strongly recommend to go through these 2 insightful blogs on SCN  Integration of S/4 Hana and SAP BW  and Unified Solution SAP S/4HANA and SAP BW.

 

 

Component View.png

Finally I would suggest to view the Hana Academy YouTube Playlist Hana Academy for CDS Views which contains information on how to get started with CDS and various consumption options. I hope this blog and the associated links would help you to get started with the S/4 HANA embedded analytics. I look forward to your comments and queries.  In a later blog I would explain the details of S/4 HANA embedded analytics architecture and associated components in more details.


Migration from 1503 to 1511 with Retail activated business function

$
0
0

Hello,

 

I have question regarding migration to 1511, if this possible migrate from 1503 to 1511 with activated EA-RET (Retail) business function?


I found post:

SAP S/4HANA, on-premise edition 1511 FPS2: Remarks regarding Business Functions

 

In this post and related SAP note in "ALWAYS OFF in SAP S/4HANA" list we have - EA-RET. And we have next note:

 

Note 1:
In this constellation it is not possible to convert this system and start a conversion program with the target of productive use. If the intention is a proof of concept to experience SAP S/4HANA it is possible to convert the system by applying a workaround in a non-productive testing environment.


If this meant that we can activate  EA-RET on 1503 and then during migration all data will be deleted in EA-RET?

BRF+ Connectivy issue

$
0
0

Hi all,

 

When executing Tcode BRF+, the following error message appears.

 

Please guide through the configuration steps.

 

BRF+ error.jpg

 

Thanks,


JF

SAP Business Partner Concept Sensible Fields

$
0
0

Hi experts,

 

I want to use sensitive fields with business partners. Apparently this function got lost in S/4 HANA according to the simplification list.

 

Is it possible to maintain sensitive with business partners? If so please tell me the IMG path where I can find it. I cannot use the old functionality within Financial Accounting (New) because SAP can disable it at anytime (according to the simplification list).

 

If there is nothing like sensitive fields, I think I have to create a workflow...

 

Thanks a lot! 

MIGO No CO document item found for original doc. item MKPF

$
0
0

Hi all,

 

When posting a goods receipt in MIGO the following error message appears when trying to save the goods receipt document.

 

MIGO-Error.PNG

 

Any ideas of what may be causing this error message?

 

Thanks

 

JF

SAP HANA Migration

$
0
0

Hi All,

 

I'am new to HANA, i have lot of doubts in HANA. We are planing to change our system (ECC6 EHP 7 -Sybase ASE) to HANA. I know the Database migration is possible, but we are planing the Netweaver 7.40 to S4 HANA. Is it possible..... What are the prerequisites  for the migration.

 

If it work fine, the entire system will change in appearance is it ?

HANA Studio & HANA Client will using for login...

 

Can you help me, i'am new in HANA, know about HANA DB, but not S4 HANA.

 

Awaiting for your valuable Replays,

 

Thanks and Regards,

Sajmal

Customer / Vendor Accounts Groups Link to Business Partner Groups (1511)

$
0
0

Hi experts,

 

within S4/HANA 1511 all "old" customer and vendor transactions are replaced by the transaction "BP".

 

The number range that is used for creating a business partner is maintained within the Business Partner customizing tree. Nevertheless, if you create a business partner within the business partner role "FI Customer" the system also creates a new Customer using the number range "01" maintained within the "Accounts Receivable / Accounts Payble" custmomizing tree (Financial Accounting (New)).

 

The system always uses the number range "01" for creating a new customer in the FI-number-range. If you delete the number range "01" within FI, the system breaks down if you try to create a new customer afterwards.

 

Is the connection between the Business Partner (role "FI Customer") and the FI-Customer-number-range hard coded or is it possible to use different FI-Customer-number-ranges for creating Business Partner (role FI-Customer)?

 

Thanks a lot!

S/4 HANA business process

$
0
0

Hi Everybody ,

 

i am looking for some documents describing or comparing between S/4 HANA system and Normal ERP EHP8 from business process perspective ,

at least the Delta Business process "BP provided by S/4 HANA and not exist in Normal ERP and vise versa " , or SAP guide for All BP could be implemented for  each of them

 

thank you

Ahmed


Standard Reports available in SAP S/4 HANA

$
0
0

Hi Guys,

 

I was given a job of finding out about the Standard Reports which are available in SAP S/4 HANA. Is there such a document that highlights or gives a list of the standard reports being offered in the new release?

 

I am aware of T-codes SAP1 and SAP 2. This method of exploring 1 by 1 will take forever.

 

With changes in Tables and structures, are the previous available reports updated accordingly?

Extensibility of S/4HANA – Helpful Links

$
0
0

In this document, I am collecting helpful links around extensibility of S/4HANA.

 

New (May 2016)

  • Update link to documentation for S/4HANA Cloud 1605
  • New Youtube link on "Adapting the User Interface of SAP Fiori Apps at Runtime"

 

 

1. SAP® S/4HANA Extensibility for Customers and Partners

http://www.sap.com/bin/sapcom/en_us/downloadasset.2015-07-jul-08-12.sap-s4hana--extensibility-for-customers-and-partners…

White Paper, June 2015, 30 pages

 

2. The Key User Extensibility Tools of S/4 HANA

A blog post that provides an overview on the key user Key User Extensibility Tools of S/4 HANA

Last updated January 2015, 8 pages

 

3. Feature Description Extensibility Tools of S/4 HANA - The official user assistance documents

 

Inside the user assistance documents, see the video with a tour on the available extensibility tools. It shows the apps for creating new custom fields, new custom logic (ABAP in the cloud) and for transporting the extensibility content from you D/Q to the P environment.

 

Fiori Extensibility Documentation: Extensibility - SAP Library

In the Fiori Appl Library (Fiori Apps Library) you can find the information on the extensibility for Fiori apps. Open the App Details and go to Implementation Information, Extensibility.

 

 

4. Online Sessions and Webinars


The Key User Extensibility Tools of S/4 HANA

SAP Mentor Monday Webinars 2016, February 2016, 1h Session Replay

Includes demos of the Fiori apps for Business Logic (Web-based Editor with Restricted ABAP), Query Designer, Custom Business Objects, Fiori UI Flexibility, Custom Fields (demos starting at 18:00)


Extensibility Concepts for S/4HANA

Recorded TechEd Session, October 2015, 1h Session Replay


5. Youtube videos and other external links

 

 

 

 

 

... to be continued

Incoming Payment Records are cleared by "ALE_extern"

$
0
0

Hi All ,

 

I have created a incoming payment through SE37 and i am able to successfully post the same . But after posting, the AUGBL column in ACDOCA table,it is stamped as 'ALE_extern" . I don't know why AUGBL column marked as "'ALE_extern". Please guide me the steps to populate the AUGBL column with proper clearing document no .

 

Thanks

S4HANA with S4CORE: Material Ledger Deep Dive after Simplifications

$
0
0

To be honest, new code line and simplifications brought by S4CORE scared me alot, on the finance and Inventory modules side, there are many major changes including database changes.

 

So I have decided to realize Inventory postings and to see what will happen. Basically my scenerio has two materials to cover both standard price control and moving avarage price.

 

If everything goes succesfully, I will see CKM3N will run for the material name S4CORE STANDARD PRICE and I'll see that compatibility layer works.

 

1. Create Materials: I have created two materials :

 

S4CORE_ML_SARHAN_10.jpg

I decided to create another one with standard price because on the Material Ledger side on the database level there are minor changes like :

 

In table CKMLCR the attributes PVPRS and SALKV are not updated anymore for materials with price control “Standard”. (we'll check this as well)  In table MLCR the attributes SALKV, SALKV_OLD and PVPRS_OLD are not updated anymore for materials with price control “Standard”.

 

S4CORE_ML_SARHAN_20.jpg

As it is mentioned in the Simplication Document: MM-IM simplification makes it obligatory to use the Material Ledger in all SAP S/4HANA systems. When a system is converted to SAP S/4HANA the Material Ledger will be activated if not active already.

 

I have activated Material Ledger, otherwise system does not let you create any Accounting related view. Meanwhile I have run all the tests on a fresh installed S4HANA 1511 system.

 

2. Goods Receipt by using MIGO:

 

I have completed all the required customizing steps to post an inventory document, I have decided to use movement type 561 Init.entry of stBal.Here are the documents. Nothing was different, if you are happy with TC MIGO. Here are the created documents listed by TC MB51

 

S4CORE_ML_SARHAN_30.jpg

3. Check Created Material and Financial Documents

 

I have tried to use TC MB03 however it is obsolote in S4HANA 1511, system redirects to MIGO, here are the documents that are created:

 

S4CORE_ML_SARHAN_40.jpg

The most important document is Material ledger document. Let's deep dive a little bit more. In the simplification document:

 

Before S/4HANA, the inventory valuation tables xBEW(H) - tables: EBEW, EBEWH, MBEW, MBEWH, OBEW, OBEWH, QBEW, QBEWH - contain transactional as well as master data attributes


With S/4HANA, the inventory valuation tables do still exist as DDIC definition as well as database object. However, they will only be used to store material master data attributes. The transactional fields LBKUM, SALK3 and SALKV will be retrieved from the Material Ledger. Hence, those fields are not updated anymore in the original xBEWH(H) tables. As a consequence, the above mentioned tables need to be updated less often, which leads to a higher throughput due to less database locks.


For compatibility reasons there are Core Data Service (CDS) Views assigned as proxy objects to all those tables ensuring that each read access to one of the mentioned tables still returns the data as before. The CDS views consist of database joins in order to retrieve both master data from the original xBEW(H) table and transactional data from Material Ledger tables.

 

Let's pick up MBEW to check the current status in S4CORE of S4HANA:

 

With the help of TC Se11 I have seen that MBEW is still there but uses a proxy object called MBV_MBEW.

 

S4CORE_ML_SARHAN_80.jpg

 

Data provided by using this DDL source, let's see how: we need to use a program called : RUTDDLSSHOW2, so I have sun the program for DDL source MBV_MBEW.


Here is the definition :

 

S4CORE_ML_SARHAN_90.jpg

It is a little bit long but the important information is visible. There is an other view called Mbv_Mbew_Case : 'MBEW case for ML integration', once we go deeper we'll find the source called Mbv_Mbew_Basis: 'MBEW basis for ML integration'. In the deep deep detail we have seen that data is provided from ML tables: CKMLPP, CKMLCR as it is told in Simplification document:

 

S4CORE_ML_SARHAN_100.jpg

Now it is time to check this statement In table CKMLCR the attributes PVPRS and SALKV are not updated anymore for materials with price control “Standard”.

 

S4CORE_ML_SARHAN_110.jpg

Yes it is not updated for Standard.

 

 

Last table that I want to go deeper is MLHD data, Contents of tables MLIT, MLPP, MLPPF, MLCR, MLCRF, MLCD, CKMI1, BSIM are now stored in ACDOCA. MLHD data is stored in BKPF For materials that are not relevant for actual costing (xBEW-MLAST = '2') no ML update documents (MLHD-VGART = 'UP') are persisted anymore in the ML document tables MLHD, MLIT, MLPP, MLCR and MLCD. Instead those update document data are being reconstructed by read access compatibility views based on ACDOCA. Hence attributes from ML data model, relevant for a pure inventory subledger functionality, are part of table ACDOCA.


This is made by this DDL source: V_MLHD_UNION:


@AbapCatalog.sqlViewName: 'V_MLHD_UNION'

@ClientDependent: true

@AbapCatalog.compiler.compareFilter: true

@EndUserText.label: 'Helper View for MLHD Compatibility View'

define view V_Mlhd_Union_Ddl as

 

 

 

 

//-----------------------------------------------------------------------------------------------------

//  Part 1: Read all original ML documents directly from MLHD

//-----------------------------------------------------------------------------------------------------

    

  select from mlhd as hd

 

    {

        hd.belnr      as belnr,

        hd.kjahr      as kjahr,

        hd.vgart      as vgart,

        hd.awtyp      as awtyp,

        hd.awref      as awref,

        hd.aworg      as aworg,

        hd.awsys      as awsys,

        hd.storno     as storno,

        hd.umbew      as umbew,

        hd.bldat      as bldat,

        hd.cpudt      as cpudt,

        hd.cputm      as cputm,

        hd.usnam      as usnam,

        hd.tcode      as tcode,

        hd.glvor      as glvor,

        hd.logsys     as logsys,

        hd.pvers      as pvers,

        hd.xcobl_cons as xcobl_cons,

        hd.bktxt      as bktxt,

        hd.kongr      as kongr

 

 

        //Extensibility Pattern for Generation additional fields

        //<$VJ>

        //<$JOINS>

        //<$VJ>

    }

 

union all

 

 

//-----------------------------------------------------------------------------------------------------------------

//  Part 2: Add now all UP-parts, but only for non-actual costing materials (MLAST = 2)

//          and only if there are postings in BSX lines

//

//          The rule is:

//          Non actual cost materials with transaction type UP (Material Ledger Update) have

//          no items in the original ML-document any longer

//          Therefore we have to reconstruct these from the ACDOCA

//          But we reconstruct only the BSX fieldgroup for the non-actual cost materials

//          e.g.: Debit/Credit (MR22) for a 2,S material:

//          The UP part is: PRD <--> UMB, as this is an S-material we have no BSX line but a PRD line

//          and hence we will not reconstruct the MLHD, MLIT

//-----------------------------------------------------------------------------------------------------------------

  select from  acdoca as it

         left outer join finsc_ledger as ledger on  ledger.rldnr    = it.rldnr

                                                and ledger.xleading = 'X'

                                                and ledger.appl     = 'FI'

         left outer join bkpf as bkpf on  bkpf.bukrs = it.rbukrs

                                      and bkpf.belnr = it.belnr

                                      and bkpf.gjahr = it.gjahr

                                

//       Connect ADOCA entry with probably existing MLHD (UP entry) for using MLHD-BELNR as BELNR of CompatView                                   

         left outer join mlhd as mlhd on  mlhd.awtyp = it.awtyp

                                      and mlhd.awsys = it.awsys

                                      and mlhd.aworg = it.aworg

                                      and mlhd.awref = it.awref

                                      and mlhd.vgart = 'UP'

  {

//      if an MLHD-entry has been posted use its document number, otherwise use the CO_BELNR from ACDOCA

        key case

          when mlhd.belnr is null then concat( substring(it.co_belnr, 1,8), '00')

          else mlhd.belnr

        end as belnr,

        key cast(substring(bkpf.cpudt, 1, 4) as abap.numc( 4 ) ) as kjahr,

  

        'UP'            as vgart,

        it.awtyp        as awtyp,

        it.awref        as awref,

        it.aworg        as aworg,

        it.awsys        as awsys,

        ' '             as storno,

        ' '             as umbew,

        it.bldat        as bldat,

        bkpf.cpudt      as cpudt,

        bkpf.cputm      as cputm,

        it.usnam        as usnam,

        bkpf.tcode      as tcode,

        bkpf.glvor      as glvor,

        it.logsyso      as logsys,

        '    '          as pvers,

        ' '             as xcobl_cons,

        bkpf.bktxt      as bktxt,

        '   '           as kongr

 

 

        //Extensibility Pattern for Generation additional fields

        //<$VF>

        //<$FIELDS>

        //<$VF>

}

//      take only postings materials with ML active and MLAST = 2

//      actual costing materials (MLAST = 3) are contained in part 1      

        where it.matnr <> ''

        and   it.mlast =  '2'

  

//      only BSX postings are relevant

        and  it.ktosl = 'BSX'

          

//      Ignore ACDOCA records of price change transaction:

//      For the compatview of all ML documents: Price Change ML Docuemnts are taken from part 1 of the union (MLHD) directly

//      Because MR21 (price change) has only one ML document with VGART = PC

//      while MR22 (debit/creadit) has two ML documents (VGART = PC => Unition Part 1 ) and (VGART = UP; AWTYP = PRCHG => Union Part 2)

//      And same logic for MR23 like MR21, because also MR23 has only one ML document, it is its own Prima Nota like MR21

//      MR21  ==> BTTYPE = RMPR

//      MR23  ==> BTTYPE = RMBK 

        and it.bttype <> 'RMPR'

        and it.bttype <> 'RMBK'     

    

//      List of all prima nota categories that are ML relevant          

        and ( it.awtyp = 'RMRP'  or

              it.awtyp = 'BKPF'  or

              it.awtyp = 'WBRK'  or

              it.awtyp = 'MKPF'  or

              it.awtyp = 'AUAK'  or

              it.awtyp = 'PRCHG' or

              it.awtyp = 'MLDUV' )

                   

//      take all fields of the select clause in the group by    

        group by mlhd.belnr, it.co_belnr, it.awtyp, it.awref, it.aworg, it.awsys, it.xreversing,

                 it.bldat,bkpf.cpudt,bkpf.cputm,it.usnam,bkpf.tcode,bkpf.glvor,it.logsyso,bkpf.bktxt

 

4. Run CKM3N

 

Despite all changes happened in Material Ledger, CKM3N runs without any problem and issue, this is great. Compatible layer works for ML..

S4CORE_ML_SARHAN_120.jpg

In order to reflect all actions I have consumed 5 peices to a costcenter by using Movement Type 201.

 

Conclusion

 

SAP is re-designing Financial and Logistics, S4CORE contains all these changes: new code line and new database structure. But Congrats to SAP that all these changes are runs smoothly and existing  transactions (I have tested limited scope, but covers some important cases)  runs as they run before, despite all these simplifications.

 

These deep dive sessions will be continued...

 

Cheers,

 

Sarhan.

SAP S/4 HANA Migration

$
0
0

Hi All,

 

We are planing to migrate our ECC6 EHP 7 Sybase  Windows 2012/R2 system to S/4 HANA.

 

Please help me to which is the best solution and how to migrate.....?

 

Awaiting for your replay.

 

Thanks and Regards,

Sajmal TS

Error KPI Modeler Apps in S/4 HANA 1511

$
0
0

Hi Experts,

 

I activted the KPI Modeler Apps in s4Hana 1511 box but it shows the error that 'Could not open app. Try again later.'



kpi.PNG

 

Kindly provide me valid inputs.

 

Regards,

Vishnu

Vendor Rebate/Settlement Management

$
0
0

Standard SAP vendor rebate is now migrated under Settlement Management in S4 HANA. Unfortunately wasen't able to find any documentation about the business process flow/ config on how vendor rebate is handled in Settlement Management.

 

Anyone has worked in this new functionality?

 

regards

 

Prashant


purchasing cycle reports

$
0
0

Hi, I would appreciate if anyone can guide me about how to capture/monitor and extract complete procurement cycle reports.

 

1. Outstanding PR.

2. Number of PR against RFQs have been made.

3. Number of PR against PO have been made.

4. Number of PO against GR/non valuated and valuated have been made.

5. Number of GR against invoices have been parked.

6. Number of Parked invoices against payment has been made / cheque has been prepared.

 

Platform: SAP HANA 1511

 

Appreciate help.

 

Thank you.


Khurram Siraj

Wrong Still to be delivered

$
0
0

Hi,
Report ME2N showing wrong values on still to be delivered column.

 

At actual still to be delivered quantity is 1500 but report showing total ordered quantity of purchase order which is 126000.

 

Please see attachments.

 

We are using SAP S4HANA 1511 SP1

 

Regards,

Khurram Siraj

SUM1.0 SP16 does not work correctly

$
0
0

Hi experts,

 

I want to convert to SAP S/4HANA on-premise edition 1511.

 

Currently conversion phase, following error occured when I run SUM1.0 SP16.


Could you tell me any solutions?

 

1.I downloaded SUM1.0 SP16 and started SUM with following command.

   cd/usr/sap/<SID>/SUM./STARTUP confighostagent<SID>

 

2.Then opened Web browser with following URL.

   https://<hostname>:1129/lmsl/sumabap/<SID>/doc/sluigui

 

3. In the dialogbox, I entered the usename<sid>adm and password, but it did not proceed to the next screen due to error.

 

   "File not found" "Fire fox can't find the file at https://<hostname>:1129/lmsl/sumabap/<SID>/doc/sluigui/index.html"

  

    I tried the SP15, but it was same.

 

    Minimum condition of the browser has been cleared.

 

 

 

Best regards,

SEKI

Regarding real time monitoring for storage consumed by info providers in HANA DB

$
0
0

Hi,

 

We have copied our production environment (ORA DB, BW7.4) to Test environment (HANA DB).

 

Our main goal is to check on test environment below parameters:

 

1) Storage space occupied by info providers e.g. info cubes. - As our existing BIA infrastructure; where our Info cubes are hosted is almost full so we need to have an alternative for the same. As of now for drawing the comparison we need to get the real time data access on HANA instance in the variation in size of info cubes whenever a data load occurs. With this we can say that in ORA DB data load use to consume e.g. 10MB space and in HANA DB it consumes on 1MB space something like that.

 

2) Performance of data access via BEx Queries - For the moment we are using RSRT and selecting some options in Execute and Debug e.g. Display Statistics, Do not use Cache etc. Is it correct way to measure BEx query performance on HANA instance?

 

3) Other test cases - What could be other test cases that we can do from developer perspective before we move our ORA DB to HANA DB?

 

Thank you already for having a look at it.

 

Best Regards,

Rachit Kumar Rastogi

SSCR Developer Key

$
0
0

Hi,

 

I've got just install a new system S/4 Hana 1511, it's fine but ?ve got a question about development user. I've already entered a valid sap license key and I try to create first bap custom report... and the system doesn't ask the developer key... so, does S/4 Hana wouldn't ask developer key?

 

Thank you.

Viewing all 882 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>