Hi Experts,
I have couple of questions:
1. What is SAP suite on HANA? By googling i found out that this is related to OS/DB migration. Can anyone elaborate on this.
2. What will be the role and scope of ABAP in this migration? Is this related to the code optimization and performance analysis which we need to consider?
If you have migrated already let me know the outline of the key activities involved.
Thanks & Regards,
Veena
Hi Gurus,
I have a couple of questions..
1 Is there any alternative for ROW_NUMBER,RANK and DENSE_RANK functions in CDS view .I know that it will be supported by CDS table functions where AMDP procedures can be called within CDS . But we are currently on 7.4
2 How can I pass parameters to CDS views dynamically in open SQL .The CDS view name and parameter name is also dynamic
Regards
Arshad
Hello,
I am creating DB procedure proxies dynamically within ABAP using side car approach where in HANA is our secondry DB , as suggested in thread
Execute Procedure with input parameters as table from ABAP
but when i try to create a proxy i get message . Database type TIMESTAMP cannot be mapped onto ABAP type.
Thanks in Advance for you help.
Hello (^o^)/ I develop ABAP CDS (My Onpremise DevSystem(S/4 HANA EM 1511 FPS01)). I made "define CDS View(exsample:Table VBAP)". But, it is not displayed by the item of the template(Master Detail,Worklist,smarttemplate) of WebIDE. I want to know the mapping method of the template of WebIDE. How can I display a value for pull-down of MasterDetail of WebIDE if I encode ABAP CDS (e.g. :SalesOrder(VBAK&VBAP join)? regards, Hiroshi
Dear Experts,
We are planning to activate BUD index on MSEG table . However the DB status = 'O' Do not create on database?
What does that mean, are we not allowed to activate BUD index on database?
Can we still go ahead and activate non-unique index?
Thanks,
HI. I have not seen "ABAP CDS Developer Guide".
( "ABAP CDS Development user Guide".)
This guide is written that page.
"ABPA CDS Developer Guide"??
What is this?
And I find "ABAP CDS Developer Guide" in "CDS Annotations for Metadata-Driven UIs" .
http://scn.sap.com/docs/DOC-69643
Where is this Guide Now?
(SAP Internal file??)
Please tell me anyone!
Regards,
Hiroshi
Hi,
as I didn't find it in the HANA developer guide/Google/Portal search:
is it possible to use the 'order by' clause in the define view statement?
Like :
define view xy as select from db_table ORDER BY field?
thanks and Kind Regards,
Tibor
Hi Experts,
is there a possibility to use a subquery in a join clause of 2 tables in an ABAP CDS View similar to:
select * from table1 inner join table2 on table1.field1 in ( select mapping_field2 from mapping_table where mapping_field1 = table2.field2 );
"field1" of "table1" should not directly match "field2" of "table2" but should be connected via a mapping table (with potentially multiple hits for "field2" in "table2").
The Keyword "IN" used for subqueries in most SQL Languages does apparently not exists in the ABAP CDS Syntax.
Any help appreciated.
Regards
Tobias
Hello Gurus,
I am SAP ABAP certified Consultant i have 1.2 year exp in ABAP , I want to go for SAP ABAP ON HANA certification. Can you please share some information regarding this ?
I would like to know the exam code relevant for SAP ABAP ON HANA certification. I would be good if there are some study materials for the same code. please tell me this certification is good for me at this level.
Thanks in advance.
Regard,
Sima.
I was working on couple of LIVE views (ex."_SYS_BIC"."sap.hba.ecc/WorkCenterCapacity"). I converted this into external view and while trying to consume it in CDS view it's showing an generic error ( ‘An error occurred while creating view <ZXXXX> in the database.’).
Few more scenarios I tried:
1. While using DDIC view in CDS, it's working.
2. While converting customized HANA view to external view, I can consume the same external view to CDS without any error.
3. Even encapsulating Live view into HANA view and using that converted ext view to CDS- throwing same generic error.
Not sure what is the special about those external view converted from LIVE view directly or indirectly.
Any suggestion/comment will be really appropriated.
Hi All,
I have installed SAP HANA S/4 1511 CORE (Back end server) on Linux SUSE Power PPE 64-bit with SAP_BASIS version as 750. and SP is 00. I am in process of update the SP using SUM16. But when I am executing command ./STARTUP confighostagent <SID> and log in in chrome with user id <SID>adm and its password, it is giving error as below :
Internal Server Error
Operation [id=8676251155141EE5BEDCF9ABA942DF8B] terminated with errors : 127 (null)
I have upgraded the hostagent 7.21 to patch 12. But still getting the above error.
Can anyone please help.
Thanks,
Sarang.
Dear all,
I'm getting error as 'Unhandled event loop exception' during activating Attribute/Calculation view in SAP HANA Studio.
Could you please help me to resolve this issue ?
Error is coming as follows(attached file also):
java.lang.NoSuchFieldError: CONNECTION_STATUS_KEY
at com.sap.ndb.studio.dwb.tools.core.internal.destination.SapSystemDestination.getState(SapSystemDestination.java:159)
at com.sap.ndb.studio.dwb.tools.core.internal.destination.SapSystemDestination.ensureLogon(SapSystemDestination.java:253)
at com.sap.ndb.studio.dwb.tools.changetracking.providers.DestinationInfoProvider$DestinationInfo.<init>(DestinationInfoProvider.java:42)
at com.sap.ndb.studio.dwb.tools.changetracking.providers.DestinationInfoProvider.<init>(DestinationInfoProvider.java:149)
at com.sap.ndb.studio.dwb.tools.changetracking.providers.DestinationInfoProvider.getInstance(DestinationInfoProvider.java:158)
at com.sap.ndb.studio.dwb.tools.changetracking.providers.ChangeTrackingProvider.getChangeInfo(ChangeTrackingProvider.java:70)
at com.sap.ndb.studio.modeler.actions.ActivateAction.singleObjectActivationFromEditor(ActivateAction.java:719)
at com.sap.ndb.studio.modeler.actions.ActivateAction$3$1.run(ActivateAction.java:562)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187)
at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4734)
at com.sap.ndb.studio.modeler.actions.ActivateAction$3.run(ActivateAction.java:557)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
eclipse.buildId=unknown
java.version=1.8.0_20
java.vendor=SAP AG
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86_64
Hello All,
In the Smart Filter Bar, I set the property enableBasicSearch = "true". It means that the search filed should be available, and this search field is still a part of filter bar rather an independent UI element.
If I do nothing but only set the property enableBasicSearch as true, I try to use it to filter but get empty filter result. How I can make this search field work well? Does CDS view need specific annotation, or I need to implement it in UI?
Thanks a lot.
Regards,
Emily
My requirement:
I have a Z config table which stores email addresses along with other stuff. I am writing a new method which queries that table to see if it contains a specific email address.
Problem:
If the email address I am querying contains upper case characters, I get wrong results.
Current process:
I select all the email addresses into an internal table, loop through and convert both to upper case and compare.
Question:
Is there a way to do code push down (ie) getting HANA to do all the hard work? I want to write something like SELECT SINGLE @ABAP_TRUE FROM.... I don't want to read all the email addresses and transfer them to application server. All I need is a YES or NO.
In continuation to previous blog Core Data Services in ABAP in this blog I will show how to create CDS Views and step by step procedure to generate OData service using CDS Views.
There are 3 different ways you can expose CDS views as OData service:
First way is supported from SAP ABAP NW 7.40 SP5, Second and third ways are supported from SAP ABAP NW 7.50 and above. For first two ways SAP NW Gateway is used and for third type without use of SAP NW Gateway odata services can be created using annotations. Gateway is used only to add the service created using annotations.
In this blog I am going to show type one i.e how to generate OData service using import DDIC structure using SEGW service builder transaction.
How to Create CDS View:
Firstly as a prerequisite ABAP Development tools(ADT) needs to be installed in Eclipse to create CDS Views.
On installation of ADT in eclipse open ABAP perspective as shown below:
After opening ABAP perspective, In project explorer right click in the context menu select New->ABAP Project. A popup appears asks for ABAP system details which you need to add to create CDS views. Details like System-ID, Username, Password has to be given and click on OK to add the system to eclipse. Note that ABAP system which you add should support SAP ABAP NW 7.40 package. find the attachment for how to add ABAP system to eclipse.
Once after adding the ABAP system project explorer looks like below:
Expand $TMP package, Select and right click on Dictionary folder in the context menu to create DDL source ABAP Repository Object
Select DDL source, click on next and give below details to create sample CDS view:
Without clicking on finish, on click on next CDS view ask for transport:
since CDS view is create in local object no transport is required, click on next then sample templates are populated to select:
You can use any of the template as shown above to create CDS view. Template helps you to create different types of CDS views with syntax auto populated on selecting the type of view. Here I am creating simple CDS view so I select define view template and click on finish.
In the define view template core annotations are populated with basic syntax to create view, define the view as below:
Here I defined sql view name as 'CDS_DDL_SAMPLE1' and selected data from "snwd_so" sales order data source with some columns. After defining the view, Activate the view as shown above. On Activation two objects are created:
1. CDS Database View (CDS_DDL_SAMPLE1)
2. CDS entity. (ZCDS_SAMPLE1)
CDS Database view can be accessed using SE11 ABAP Dictionary as shown below:
Give CDS Database View name as shown above and click on display.
DDL SQL view is created in ABAP Dictionary. Here you can identify MANDT field in the view definition though we didnt mention it explicitly while defining the view. CDS views are default client dependent no need to mention client field while defining the view.
Right click on CDS View created to preview the data as shown below:
Generate OData service using CDS View:
Go to SEGW transaction. Create project as shown below:
Give project details as below:
Save project in local object. Expand project node, right click on data model->import->DDIC structure:
Create entity type by importing ABAP structure. Here give CDS Dabase view 'CDS_DDL_SAMPLE1', select create default entity set flag and click on next:
follow the wizard where you select parameters and key fields respectively:
click on finish, then entity, entity set and corresponding properties are created. Expand node service implementation right click on SalesOrderSet->Map to Data Source
Here you map your CDS Database view(CDS_DDL_SAMPLE1) and CDS enity(ZCDS_SAMPLE1). on click on map to data source popup populates to select CDS business entity:
select type as business entity and give CDS entity ZCDS_SAMPLE1 as Name:
click on OK.
click on OK. Drag and drop properties to map fields or click on generate mapping to automatically map the fields.
After mapping done save the changes and click on generate icon as shown below to generate run time artifacts.
In model and service definition you can find DPC, MPC classes and technical service name of odata service:
click on ok and save the objects in local object;
after saving run time artifacts are generated. Expand node Service maintenance select gateway, click on register button to register the service.
add the service to local object:
click on OK. Now service is registered you can find status as green as shown below and click on Gateway client button to access the service:
Odata service in gateway client:
Use OData parameter $metadata to view the metadata of service:
on using odata parameter $metadata you can find the properties and entities of CDS view exposed as odata service.
This is how you create CDS view and expose the same as odata service using import DDIC structure by mapping CDS Database View and CDS entity using SEGW service builder transaction.
Hope you find this blog helpful.
In my next blogs I will try to touch other ways to expose cds view as odata service.
Your suggestions, feedback, comments on this blog are most welcome.
Authors: Sunil Kumar
Company: TATA Power Delhi Distribution Ltd
Key Objectives -
1. Enhanced customer experience - by bringing down the overall installation processing time
2. Integration of data at various segregated layers like - AMR, GIS, SAP ISU, BW HANA
3. Reduction in the efforts put in by NEG teams by involving in manual activities to extract and analyses data for asset utilization.
4. Lay down foundation for proactively augmenting the network, assets even prior to request from applicants.
End User Situation:
1. When NEG gets the case from CMG for checking the technical feasibility against the applied load by applicant, they extract data manually from various sources like, AMR, GIS, SAP and work manually to derive the network and asset utilization.
2. Manual working often lead to errors and thereby lead to delay in processing of the applicant's request for new connection installation.
Analysis:
SAP HANA is used for big data processing (sourced from various sources like - AMR, GIS, etc) and a unique integration is developed to transport processed data from HANA to SAP.
NEW INNOVATION......
A unique data flow mechanism was developed to transport data from HANA to SAP ISU, as against the standard and usual scenario of data flow
from SAP to HANA database. So in this scenario HANA became the 'Destination' as well as a 'source'. The data from different sources were sent to HANA and all System Based Technical Feasibility for Consumer New Connection Process on BW-HANA the complex business logics were developed in HANA instead of SAP for utilizing the HANA processing capabilities and the processed data was sourced from HANA to its final destination in SAP.
The EUREKA:
To create a system based provision which could bring the network/ asset (DT) utilization data from various sources to a single point and based on system based algorithms the technical feasibility may be derived from an available network against the additional load growth applied from the same network.
How to develop?
1. First we have modeled the process for DT peak load.
2. Design the SQL calculation view in HANA Studio as below
3. Developed Virtual provider using this calculation view as:
4. Pull the data from this virtual provider in ECC ISU system using with RFC function module as RSDRI_INFOPROV_READ_RFC.
CALL FUNCTION 'RSDRI_INFOPROV_READ_RFC'
DESTINATION 'CLIENT'
EXPORTING
I_INFOPROV = 'ZDM_VP01'
I_REFERENCE_DATE = SY-DATUM
I_AUTHORITY_CHECK = RSDRC_C_AUTHCHK-READ
TABLES
I_T_SFC = G_T_SFC
I_T_SFK = G_T_SFK
I_T_RANGE = G_T_RANGE
E_T_RFCDATA = G_T_RFCDATA
E_T_RFCDATAV = G_T_RFCDATAV
E_T_FIELD = G_T_FIELD
EXCEPTIONS
ILLEGAL_INPUT = 1
ILLEGAL_INPUT_SFC = 2
ILLEGAL_INPUT_SFK = 3
ILLEGAL_INPUT_RANGE = 4
ILLEGAL_INPUT_TABLESEL = 5
NO_AUTHORIZATION = 6
GENERATION_ERROR = 8
ILLEGAL_DOWNLOAD = 9
ILLEGAL_TABLENAME = 10
DATA_OVERFLOW = 12
OTHERS = 13.
5. Developed Module pool entry screen for end user as:
Control Project Closer:
A new unique landscape worked out during brainstorming
session.
As the requirement involved huge data from various different
landscape, so an efficient and optimized runtime processing was a big
challenge.
Control Project Closer:
A new unique landscape worked out during brainstorming session.
As the requirement involved huge data from various different landscape, so an efficient and optimized runtime processing was a big challenge.
Benefits:
1. Availability of data from various sources to one location for ease of working by involved groups
2. Enhanced data integrity as various system based algorithms will help highlight any data discrepancy among various different sources
3. An advanced step towards 'Ease of Doing Business' for enhanced Customer Experience (by over all reduction in process cycle time)
4. Enhanced IT user experience (ease in working through IT system based automation)
5. Utilization of Advanced SAP HANA technology for this process (First time such landscape modeling has been used in TPDDL scenario)
Hi Experts,
we are developing a program using ADBC for accessing hana secondary db connection. How i can find the current hana db secondary connection name in the abap program via code i.e any class or FM or table to get the hana dbcon name instead of hardcoding? we can see the conenction name from the hdbc tcode.
Also, in future after we change HANA as primary db, do we have to scrap this program or can we just comment the code for getting the db connection name and the rest will work without any issue?
Thanks for the help in advance.
Ram
Hello,
I'm using the new ALV 'cl_salv_gui_table_ida' combined with a Core Data Service. I've activated the toolbar text search and enabled the search for a plenty of columns:
go_alv_display->field_catalog( )->enable_text_search( 'NAME1' ).
go_alv_display->field_catalog( )->enable_text_search( 'ORT01' ).
go_alv_display->field_catalog( )->enable_text_search( 'PSTLZ' ).
go_alv_display->field_catalog( )->enable_text_search( 'INFNR' ).
go_alv_display->field_catalog( )->enable_text_search( 'LIFNR' ).
go_alv_display->field_catalog( )->enable_text_search( 'LIFNR_2' ).
go_alv_display->field_catalog( )->enable_text_search( 'MAKTX' ).
go_alv_display->field_catalog( )->enable_text_search( 'SMTP_ADDR' ).
go_alv_display->field_catalog( )->enable_text_search( 'ORT02' ).
The search is working for the fields NAME01, ORT01, PSTLZ, MAKTX, ORT02, The other columns don't work in the search.
I've checked the coding and found out that the search_scope is just filled with the working columns.
Class: CL_SADL_ABQI
Method: _GET_SEARCH_SCOPE
But I couldn't find the coding where the scope is filled.
Thx for your help!
Frank
In this series of blogs I try to have a look on SAP S/4HANA from an different angle. The point of view of somebody who needs either to adjust existing code for S/4 or enhance functionality of S/4 to meet business needs.
In my first part I try to explain what is the main difference between R/3, SAP ERP and S/4.
As you can see from the picture above R/3 was upgraded, extended and renamed to eventually SAP ERP. With upgrades from R/3 to the next version SAP mostly added/enhanced functionality and mostly kept all other functionalities as before. This allowed custom ABAP programs to continue to run with no or may be small adjustments.
SAP S/4HANA is SAP's next generation Business Suite, but it is not another new version of R/3. It is a new code line. Let's have a look what this means.
The last time SAP made a product announcement like S/4 was 1992, when R/3 was introduced as next generation after R/2. It was a new code line on a different hard- and software architecture. R/2 was for Mainframe computers and R/3 for Micro Computers on Unix and later Windows NT.
SAP kept of course many things from R/2, like some tables, fields etc. Some R/2 ABAP code was converted to R/3. But with new technologies it was time for a fresh new start. In R/3 functionality was extended, re-designed or retired. In short SAP kept the best and made house cleaning where necessary. The new technologies allowed SAP to make R/3 a better product, not only an upgrade with more functionality.
Here we are again, we have a new better product with SAP S/4HANA. It is like the step from R/2 to R/3. So after 23 years SAP does house cleaning and redesign. Because SAP has now new technologies that it can make a better ERP product on technologies like SAP HANA on multi core CPU and large RAM memory.
As redundant data tables or field (including aggregates) are mostly eliminated, the ABAP code that maintains the aggregates and redundancies are removed, too. Furthermore unused or redundant functionality is retired. The goal is to unifying functionality by the principle of one, i.e. having only one functionality for the same task. Some data types are are extended like the material number. Some ABAP processing is replaced by SQL on HANA, because it works directly on the data with automated parallel execution by HANA.
SAP S/4HANA is compatible to SAP ERP where possible and where it makes sense. Most of the BAPI's, tables, table field names and some of its ABAP code is still there.
If you liked what you read, please like it, rate it and/or add your additional comments and questions below.
Key Objectives -
End User Situation:
Analysis:
SAP HANA is used for big data processing (sourced from
various sources like - AMR, GIS, etc) and a unique integration is developed to
transport processed data from HANA to SAP.
NEW INNOVATION......
A unique data flow mechanism was developed to transport data
from HANA to SAP ISU, as against the standard and usual scenario of data flow
from SAP to HANA database. So in this scenario HANA became the 'Destination' as
well as a 'source'.
The data from different sources were sent to HANA and all
the complex business logics were developed in HANA instead of SAP for utilizing
the HANA processing capabilities and the processed data was sourced from HANA
to its final destination in SAP.
The EUREKA:
To create a system based provision which could bring the
network/ asset (DT) utilization data from various sources to a single point and
based on system based algorithms the technical feasibility may be derived from
an available network against the additional load growth applied from the same
network.
How to develop?
3. Developed Virtual provider using this calculation view as:
4. Pull the data from this virtual provider in ECC ISU system using with RFC function module as RSDRI_INFOPROV_READ_RFC
5. Developed Module pool entry screen for end user as:
Control Project Closer:
A new unique landscape worked out during brainstorming
session.
As the requirement involved huge data from various different
landscape, so an efficient and optimized runtime processing was a big
challenge.
Benefits: