Hi,
Please check the SCN community under http://scn.sap.com/community/abap/hana and/or the courses provided on https://open.sap.com.
There are a lot of documents and videoa available to train yourself.
best regards,
Ingo
Hi,
Please check the SCN community under http://scn.sap.com/community/abap/hana and/or the courses provided on https://open.sap.com.
There are a lot of documents and videoa available to train yourself.
best regards,
Ingo
Dear Experts,
Do we have sap delivered CDS Views? (Like SAP HANA Live Views?)
If so, can you please share the link to download?
Thanks in advance!
Your help is much appreciated.
Regards,
Adlin
Hi,
you're on the right path, the solution is
case when ekbe_mseg.belnr is null
then '@S_LEDR@'
else '@S_LEDG@'
end as icon
Best regards,
Simon
Hi Simon,
It worked. Thank you. The CDS View was activated successfully, but the editor does not seem to recognize the sintax. Is it normal?
Best Regards,
Luís Martins
Hi SDNites,
I have a scenario in which multiple puchase rquisitions are converted to PO and then this PO needs to be released based on release strategy and when the squenece is completed, we have to copy the qty field from PO line item to custom made quantty field (again at EKPO).
In the scenario mentioned above PR is created to PO properly (written custom code in user exit of PO save EXIT_SAPMM06E_012). When PO is being released I have written a code in user exit EXIT_SAPLEBND_002 which is being triggered and during debugging I can see the custom qty. being updated but in reality it is not.
Also if I try to make any random change in PO before releasing and then release it the custom qty. field gets populated correctly.
Can you please guide me what could be the reason of above behaviour.
Regards,
Abhi
Dear experts,
in the end I implemented a new custom code inspector check, which checks if the select was done into a standard table, if key fields were selected, and if no sorting or order by was used for it.
I hope it helps the others.
Hi All,
I am writing an AMDP method with multiple selects into it. The execution gives a dump with SQL Database error code 339.
Below is the code for the calling Program :
TABLES: mseg.
SELECT-OPTIONS: s_matnr FOR mseg-matnr,
s_pspnr FOR mseg-mat_pspnr,
s_werks FOR mseg-werks.
START-OF-SELECTION.
DATA : lo_amdp TYPE REF TO zamdp.
DATA : gt_416 TYPE zamdp=>gtt_quan,
gt_415 TYPE zamdp=>gtt_quan,
gt_qbew TYPE zamdp=>gtt_quan,
gt_28x TYPE zamdp=>gtt_quan,
gt_usnam TYPE zamdp=>gtt_usnam.
CREATE OBJECT lo_amdp.
DATA : lt_seltab TYPE if_shdb_def=>tt_named_dref,
lv_where TYPE string,
lst_seltab TYPE if_shdb_def=>ts_named_dref.
lst_seltab-name = 'MATNR'.
GET REFERENCE OF s_matnr[] INTO lst_seltab-dref.
APPEND lst_seltab TO lt_seltab.
CLEAR lst_seltab.
lst_seltab-name = 'MAT_PSPNR'.
GET REFERENCE OF s_pspnr[] INTO lst_seltab-dref.
APPEND lst_seltab TO lt_seltab.
cl_shdb_seltab=>combine_seltabs( EXPORTING it_named_seltabs = lt_seltab
RECEIVING rv_where = lv_where ).
CALL METHOD Zamdp=>meth_mseg_quan(
EXPORTING
im_where = lv_where
IMPORTING
ex_416 = gt_416
gt_415 = gt_415
gt_qbew = gt_qbew
gt_28x = gt_28x ).
cl_demo_output=>display_data( EXPORTING value = gt_416 ).
The AMDP Code is as attached.
I am not getting what exactly needs to be done to resolve the issue.
Thanks & Regards
Srinivas Rao
We are looking to migrate our underlying database to SAP HANA for which we want our system to be HANA ready with respect to custom ABAP code .
Can someone help me with specific guidelines/ rules/checklist one need to follow for developing ABAP custom code or correct existing custom developments when the underlying DB is HANA .
Hello Raksha,
post ABAP custom code adaption for SAP HANA – The efficient way gives you a good overview regarding ABAP custom code adaption for HANA.
Regards,
Florian
Hi Folks,
We have the requirement to change the instance no. of HANA database. Currently we have 00 instance no. and now we want to change it to 01. I have referred link help.sap.com (attached for your reference) which shows the steps to perform the activity with the help of hdblcm but I need some detail document for better understanding. Please let me now if this activity is feasible and the location of required document to execute it.
Thanks
Hi,
I have SAP HANA standalone system and also installed ABAP system on top of same HANA system.
In some cases where joins to be done from tables with huge data, we are persisting those tables by using AMDP procedure in the ABAP system in background scheduling mode.
Now I'm trying to update 10 tables within the same AMDP. In that 5 tables got updated successfully but the remaining tables didn't.
Can anyone suggest how to maintain LUW for AMDP procedure like Update Function Module in classical ABAP updates.
Regards,
Ramana.
Hello,
1. Always define Raising clause in AMDP defination.
Ex.
CLASS-METHODS : update_data
IMPORTING
VALUE(ip_tmstart) TYPE char16
RAISING cx_amdp_error.
2.Catch exceptions during calling AMDP method so you can understand what is exact error occurring.
Ex.
TRY.
CALL METHOD zcl_test=>update_data
EXPORTING
ip_tmstart= lv_tmstart.
CATCH cx_amdp_error INTO DATA(lx_amdp_error).
--here you can get long text
ENDTRY.
Now you will get exact error message in exception lx_amdp_error.
Still you are unable to understand the error , you can go with AMDP debugging.....
-Amol S
How is possible to create a transaction in ABAP in a method from an object.
Refer to this for more details: begin-of-transaction in ABAP Objects
Hi Amol
Thanks for the inputs. The exception gives the same information as that of the dump details.
Anyway, I was able to resolve myself. If you check in my AMDP, there is a table called GT_USNAM where I am using SUBSTR function in the ON condition for joining 2 tables. There I had compared the SUBSTR with INT value instead it should be character and hence the right side operand should be in quotes.
I am marking your reply as helpful . Thanks ! Cheers !
Hi Ramana,
Did you try to debug the AMDP ? can you please send me the copy of your AMDP on srinivas1984@gmail.com
Thanks & Regards
Srinivas Rao.
Hi Srinivas,
Have you tried below exception, you can get exact SQL error text message. It might be helpful....
CATCH cx_amdp_dbproc_create_failed INTO DATA(lt_amdp_error).
lw_text = lt_amdp_error->sql_message.
ENDTRY.
-Amol S
Hello Experts :
I have a requirement with text search functionality on some group of custom tables.(BOPF tables).
Text search is based on wild card and should be case insensitive as well.
The output of this result must be consumed in ABAP for further use. To model this requirment i am looking for a help.
as i read some blogs and documents , we have a two options to build this
create a CDS view and consume this views in AMDP procedures in ABAP report . But i am looking for other any options though
hana studio build the graphical hana views and can consume in store procedures? creating store procedure proxies and call
the procedure in abap report.i am looking for wildcard case insensitive search functionality on this views . so how can i proceed?
Please suggest best optimal solution for this .
Appreciate your answer.
Regards
Vinuta
Hello Florian,
I went through the mentioned blog. If my understanding is correct, it seems the work effort for ABAP custom code adaption for SAP HANA can only be assessed after we migrated to SAP HANA environment. Is there any way that we would like the work effort can be done before the migration started. The info will be important for project timeline preparation.
Thanks and Best Regards
Tarmizee
Dear Experts,
today we got a few ABAP short dumps:
SQL error "SQL code: -10811" occurred while accessing table "Z079_CV_LOG".
Database error text: "SQL message: Numeric overflow for parameter/column (32)
source type DECIMAL, target type UCS2 (LE), value
'0.974204418927118174949782384017408E25'"
An exception has occurred which is explained in more detail below. The
exception is assigned to class 'CX_SY_OPEN_SQL_DB' and was not caught in
procedure
"READ_Z079_CV_LOG" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated this
exception, the current program was terminated.
The reason for the exception is:
Database error text: SQL message: Numeric overflow for parameter/column (32)
source type DECIMAL, target type UCS2 (LE), value
'0.974204418927118174949782384017408E25'
Return value of the database layer: "SQL dbsl rc: 99"
It is very strange because the select is very simple, there is no SUM or any possibility to value conversion. It has to put all fields into structure of the same type as DB table. The table Z079_CV_LOG is a transparent table.
data LS_Z079_CV_LOG TYPE Z079_CV_LOG.
SELECT SINGLE *
INTO ls_z079_cv_log
FROM z079_cv_log
WHERE cv_type = iv_cv_type
AND key_ref = iv_key_ref.
When I try to reproduce the error, everything is ok. There is no strange values in the table shown in SE16N nor in Hana Studio.
We work on HANA DB version 1.00.097.03.1443520413
The column no. 32 in the table is of type Decimal 9,5:
Have you heard about such problem?
Best regards
Rafal