SAP ABAP Programming Made Easy - Theory & FAQs

Creating HANA views (Attribute, Analytic and Calculation) involve creating HANA artifacts in the HANA database layer (from SAP HANA Modeler Perspective). These views are then consumed in our ABAP reports either through ADBC, or external views. Hence it is a BOTTOM-UP approach. Such Bottom-Up approach is not recommended because of the difficulty in creating and transporting the HANA artifacts (through Delivery Unites). In case any underlying HANA artifact is not included in the transport (via Delivery Unit and Transport Container), then there will not be any errors at the time of releasing the Transport. For this reason, SAP recommended TOP-DOWN approach. The TOP-DOWN approach is equivalent to creation of HANA views, is CDS (Core Data Services) Views. These are created from ABAP perspective, can be saved directly in a TR and consumed in ABAP reports through open SQL. Creating CDS Views: In the following example, we will create a CDS view that takes as input the Client, a Target

SAP HANA supports SQL as a means to define, read, and manipulate data. On top of SQL, many technologies introduce higher-level models to add semantics and ease consumption, such as OData EDM models, the semantic layer in the BI platform, JPA and enterprise objects in Java, and the business objects frameworks in ABAP. These higher-level models share many commonalities, but are usually specific to their technology. This prevents their re-use across stacks and increases effort for application developers. To address this, SAP introduces a set of domain-specific languages and services, called CDS, for defining and consuming semantically rich data models. The Core data Services (CDS) views are collection of below three domain specific languages and services for consuming semantically rich data models. Data Definition Language (DDL):  The DDL part of CDS can be considered an enhancement of SQL that allows you to define semantically rich database tables and views, often referred to as

The procedure looks like:- Step-by-Step Procedure Step -1 Create and implement a SAP HANA Procedure with Input and Output Parameters Start the SAP HANA Studio and go the Modeler perspective a. Start the SAP HANA Studio and open the Modeler perspective. Select menu entry Window > Open perspective > Others…, choose  from the appearing dialog box and press OK. The procedure looks like:- Step-by-Step Procedure Step -1 Create and implement a SAP HANA Procedure with Input and Output Parameters Start the SAP HANA Studio and go the Modeler perspective a. Start the SAP HANA Studio and open the Modeler perspective. Select menu entry Window > Open perspective > Others…, choose  from the appearing dialog box and press OK. b. Optional:   First create a new package (e.g. demo) for your demo objects under package systemlocal.private which is located under the Content folder. Now create a new database procedure by right-clicking on package s

IN HANA Migration Project i.e. when Clients or customers are migrating from ECC to HANA, we often face a problem on a few tables that are not directly accessible anymore. Here we show a simple solution to select data from CDS view in ECC system. One can only see the CDS view in display mode in ECC system. CDS view can be edited only via Eclipse tool. Before HANA DDIC Table (Tcode : SE11)  Program (SE38):  The below program  as shown below is selecting data from DDIC table GLTO Ater HANA In SAP HANA, the same DDIC table GTL0 has been transformed to SQL view, where it is selecting data from V_GLTO_INT2 view, this view has been generated while activating V_GLT0 CDS view in ADT Eclipse (you can find the code of this CDS view at last). Double click on the DDL Source GLT0_DDL , it will take you to the source code of the CDS View One cannot edit the CDS view in ECC, this can only be edited using ADT in Eclipse, as it has been created in ADT. Now the program wi

SAP Business Suite on HANA(BsOH), powered by SAP HANA brings together OLTP and OLAP worlds into a single in-memory platform, and helps Suite of Applications like ERP, CRM and SCM to manage their Business processes with improved Performance. It helps Customers to quickly Optimize, Execute, and Align their business and IT strategies and also gives unique ability to allow real-time reporting, and analysis across their end-to-end business processes. The Underlying HANA Platform helps to provide these innovations without disruption. Because of its in-memory approach, SAP HANA enables both hardware and software innovations which are unparalleled, replacing traditional databases in many spheres of business world! On the hardware side, SAP HANA facilitates Multi-Core Architecture (8×8 core CPU per blade), huge parallel scaling with several blades, 64 bit address space – 6 TB in current servers, data throughput as high as 100 GB/s, cost effectiveness and so on. On the software side, SA

SAP HANA ( H igh-performance  AN alytical  A ppliance) is an in-memory database engine from SAP that is used to analyze large data sets in real time that reside entirely in memory. Very crudely it is a Database System which totally changes the DBMS methodology and it can be deployable on premises or over cloud. HANA is the first system to let you to perform real-time online analytical processing (OLAP) analysis on an online transaction processing (OLTP) data structure. As a result, you can address today’s demand for real-time business insights by creating business applications that previously were neither feasible nor cost-effective. GOALS: Enable New Application and Optimize Existing Application. High Performance and Scalability. Hybrid Data Management System. Compatible with Standard DBMS feature. Support for Text analysis, indexing and search. Cloud support and application isolation. Executing application logic inside the data layer. FEATURES: HANA usage full cap

High-Performance Analytic Appliance (HANA) is an In-Memory Database from SAP to store data and analyze large volumes of non aggregated transactional data in Real-time with unprecedented performance ideal for decision support & predictive analysis. The In-Memory Computing Engine is a next generation innovation that uses cache-conscious data-structures and algorithms leveraging hardware innovation as well as SAP software technology innovations. It is ideal for Real-time OLTP and OLAP in one appliance i.e. E-2-E solution from Transactional to high performance Analytics. SAP HANA can also be used as a secondary database to accelerate analytics on existing applications. Hardware Innovations - Leading to HANA In real world we have so many varieties of data sources, e.g. Unstructured Data, Operational Data Stores, Data Marts, Data Warehouses, Online Analytical Stores, etc. To do analytics or information mining from this Big Data at real time we come across the hurdles like Late

Please find the list of all the available BADI's that can be used for SAP Concur Integration. Enhancement Spots BADI Description ES_AP_CTE_DETERMINATION_EXIT BADI_AP_CTE_DET_REQUIREMENT Condition Technique Determination Requirement ES_CTE_FIN_COBJ_DATA BADI_CTE_FIN_COBJ_DATA_CHANGE Change Cost Object Data BADI_CTE_FIN_COBJ_FILL_LEVEL Customer-Specific Hierarchy Level for Concur List ES_CTE_FIN_INV_POSTING_DATA BADI_CTE_FIN_POST_IV_ADD_DATA Invoice FIN Posting Document: Map additional data BADI_CTE_FIN_POST_IV_ADJUST_FI Adjust whole FIN Document BADI_CTE_FIN_POST_IV_DOC_CHG Invoice FIN Posting document: Small changes BADI_CTE_FIN_POST_IV_ROUNDING Adjust Amount Fields According to Decimal Places of Deviatin ES_CTE_FIN_POSTING_DATA BADI_CTE_FIN_POST_ADJUST_DOC Change Posting Data BADI_CTE_FIN_POST_DATA_CHANGE Enhance Incoming Posting Data from Concur BADI_CTE_FIN_POST_DOC_CHANGES Minor Field Changes BADI_CTE_FIN_POST_ROUNDING Adjust Amount Fields According to Decim

One cannot debug F110 transaction logic directly as it gets triggered in background. Let’s take an example for better understanding. Example:  Identify the Segments for IDOC creation for Bank data. EXIT_SAPLIEDP_902 is the user exit to add/modify segments in PEXR2002 IDoc, if the contents differs for each payment document number processed in the IDoc. This user exit is called at the end of processing for each payment document.  For Example,  one can use it for manipulating the PAYEXT IDoc before it is sent to the banks for clearing the payment to the vendors. To debug this user exit, first you need to set and save the parameters in F110 transaction. Step By Step For Parameter’s Creation: 1. Parameter:   Fill vendor details also as per your requirement. 2. Free Selection:  Nothing to be selected. 3. Additional Log:  Fill vendor data as per the requirement. 4. Printout / Data Medium:  Here program RFF0EDI1 is the main program to debug F110. Here we need to give