2016 Jul 30 10:34 PM
Hi ,
I came across the below statement in one of the sample ABAP codes. I could not understand the bind variable @
how is this bind variable @ different to traditional work area target?
DATA ls_bupa_reminder TYPE ty_bupa_figure.
SELECT bp_id,
company_name
FROM snwd_bpa
INTO (@ls_bupa_reminder-bupa_id, @ls_bupa_reminder-company_name)
. "#EC CI_NOWHERE
Thanks
Vardhan
2016 Jul 31 4:00 AM
It activates the "strict mode", as of 7.40, it's all explained here: ABAP Keyword Documentation - Open SQL - Release-Dependent Syntax Check Modes. New powerful constructs are allowed, and it allows distinguishing between table field names and data object names, and the Open SQL is required to be a little bit more SQL-like. In your case, it is only required because of the comma between bp_id and company_name, but we could still write it the old way (without @ and without the comma).
2016 Jul 31 4:00 AM
It activates the "strict mode", as of 7.40, it's all explained here: ABAP Keyword Documentation - Open SQL - Release-Dependent Syntax Check Modes. New powerful constructs are allowed, and it allows distinguishing between table field names and data object names, and the Open SQL is required to be a little bit more SQL-like. In your case, it is only required because of the comma between bp_id and company_name, but we could still write it the old way (without @ and without the comma).
2016 Jul 31 7:28 AM
Thanks Sandra.
As I understood we may need it to access CDS views, DDL views created in ABAP Core Data Services.
Vardhan