Re: Debugging stored procedure: 'Edit Source Lookup Path' (and source not found)
Christian,attached you find a PPT with screenshots of the 3 procedures (ztest2->MY_HANA_PROCEDURE->ztest). To open please rename from: Debugging stored procedure.pptx.txtto: Debugging stored...
View ArticleClik here to view.
Re: Debugging stored procedure: 'Edit Source Lookup Path' (and source not found)
Sorry I oversaw your request for the screenshot, but here it is:
View ArticleRe: Debugging stored procedure: 'Edit Source Lookup Path' (and source not found)
Shipra,what is the "Debug Configuration settings in the stored proc" that you are referring to? Thanks
View ArticleClik here to view.
External View: No data preview
Hi Experts. I just created an External View following the steps on link: How to Consume HANA View in ABAP Using External View and Open SQL The problem is that when I choose "Open Data Preview" on the...
View ArticleRe: External View: No data preview
Hi Leandro, By referring to your attached screen shot, i looks like the data you have in HANA E66 for client 800.However, you have created ABAP project NWH with client 001.I believe that is reason...
View ArticleRe: External View: No data preview
Hi Vaibhav, thanks for your quick respose! You are right, it was a MANDT issue. I created another Calc.View without MANDT field and it worked. But now I have another question: In this case, when I...
View ArticleRe: External View: No data preview
Hi Leandro, In my opinion, you can configure MANDT field value during replication configuration.Pls have a look at this video. https://www.youtube.com/watch?v=sqfsGkQ2TzQ Hope this helps.Best...
View ArticleRe: AMDP call to Procedure: "SQLScript message: insufficient privilege: Not...
Hi,please check if all necessary authorizations have been granted to SAP<SID> using report RS_AMDP_SICK. Is the procedure you want to execute in the catalog, i.e. "_SYS_BIC" schema? Otherwise,...
View ArticleRe: External View: No data preview
Hi Leandro, The details you mentioned here is SAP CTR specific and you don't need to map mandant as the nature of CTR is support multi mandant information. Also the external view you are creating may...
View ArticleRe: External View: No data preview
Hi Da Ros! Indeed, the External Views already exists, I've tried to found these E.V. a time ago, but now with your tip to select SYNONYMS table, now I understood the naming relation between the...
View ArticleRe: External View: No data preview
Hi Leandro, Hmmm I understood your point. For SE16 you can't access such data specially as the TDF client have no obligation to follow the ECC replicated client.You only have the option with a custom...
View ArticleClik here to view.
Exists in CDS view
HiI wonder if the Exists condition can be used in the CDS view (WHERE EXISTS (SELECT * FROM .... ) .I actually never managed to used subqueries in any cds view so I wonder if this is a limitation for...
View ArticleRe: Exists in CDS view
Dear Christelle,Can you explain little bit more the context where you want to check the existence?Best regardsSundar
View ArticleClik here to view.
Cx_salv_db_table_not_supported
Dear Gurus We are currently implementing SAP ecc6 ehp7 on HANA. I have created the view by using the following @AbapCatalog.sqlViewName: 'z_cds_purch'define view ZCDSV_DWMQHY_PURCH as select from mseg...
View ArticleRe: Cx_salv_db_table_not_supported
Hi Arun,you have to use another factory method, i.e. cl_salv_gui_table_ida=>create_for_cds_view('ZCDSV_DWMQHY_PURCH'). An alternative (but not recommended) approach would be to use the SQLViewname,...
View ArticleRe: Cx_salv_db_table_not_supported
Hi Jasmin Thanks for the reply. it got solved. Thanks and RegardsArun Kumar Menon.
View ArticleInvalid GUI input data: window dimension
Dear gurus I am getting this error when i am writing this code. cl_salv_gui_table_ida=>create_for_cds_view( 'ZCDSV_DWMQHY_PURCH' ) Searched a lt but could not get any similar kind of error. I am...
View ArticleRe: Invalid GUI input data: window dimension
A SAPGUI update might help, see also the discussion http://scn.sap.com/thread/3550486 and the SAP note mentioned there
View Article