Kernel BADI is implemented using GET BADI and CALL BADI statement. So to find it we can search for these 2 statements in the package level or tcode level. We can use tcode CODE_SCANNER to speed up the search.
"@ObjectModel.foreignKey.association:’_AssicationName’: This Annotation is used for Value Help from association based on the Key Field.
@ObjectModel.text.element: [‘Fieldname’]: This annotation is used for Value Help for Key field to display the Text also. E.g field name is Customer Name for Customer Number.
@Consumption.valueHelp: This Annotation is used for Value Help from Associations.
@Consumption.valueHelpDefinition: This Annotation Used for Value Help from another CDS view or Value Help CDS."
@ObjectModel.text.element: [‘Fieldname’]: This annotation is used for Value Help for Key field to display the Text also. E.g field name is Customer Name for Customer Number.
@Consumption.valueHelp: This Annotation is used for Value Help from Associations.
@Consumption.valueHelpDefinition: This Annotation Used for Value Help from another CDS view or Value Help CDS."
Association is conceptually Adhoc join or Join on demand. It helps us to achieve better performance and better navigation. Very useful from Fiori apps perspective.
Status 51(document not posted), 53(posted sucessfully),02(Failed to transfer data to port),03(Data transfer to port OK),41(Application document generated in the target system)
Host variable(data from the application server) also know as Escape variable is used in new age Open SQL for inline declaration. It imposes strict code check while doing syntax check in the editor.
"Use of Order BY cluase while selecting data from tables.
Use of Inline declaration.
Use of Inner join on tables compared to For all entries. Use of data calculation related functions while selecting the data to reduce further roundtrip from DB.
All cluster and some pooled tables are converted to transparent tables in HANA. Hence queries on Cluster/pooled tables returns results sorted by primary keys is no more true here. Any custom coding which accesses physical table cluster/pool has to be changed so that the program reads from tables directly"
Use of Inline declaration.
Use of Inner join on tables compared to For all entries. Use of data calculation related functions while selecting the data to reduce further roundtrip from DB.
All cluster and some pooled tables are converted to transparent tables in HANA. Hence queries on Cluster/pooled tables returns results sorted by primary keys is no more true here. Any custom coding which accesses physical table cluster/pool has to be changed so that the program reads from tables directly"
There might not be any need of indexes and secondary indexes in S/4 HANA as the whole table fields act like the index. But standard sap tables are delivered with indexes and we can define and use secondary indexes as well.
Yes it is supported in S4 HANA.
"If reusability is not the concern then we can go ahead with Open SQL only.
If reusability is needed then CDS is very useful also it can further be used in Odata & Fiori.
AMDP is useful when we want to have some very complex logic which requires looping and all also the need is to use SQL Script then we can go ahead with AMDP. But now with the birth of CDS table function we can use AMDP inside CDS."
If reusability is needed then CDS is very useful also it can further be used in Odata & Fiori.
AMDP is useful when we want to have some very complex logic which requires looping and all also the need is to use SQL Script then we can go ahead with AMDP. But now with the birth of CDS table function we can use AMDP inside CDS."
BDC deals with the Screen so in future if the BDC related screens are changed by SAP as part of upgrade then BDC might stop working correctly.