SAP TUTORIALS

ABAP Code Inspector Tool The Code Inspector is a tool for checking static ABAP coding and DDIC objects . It helps developers to adhere to programming standards and guidelines by creating messages on less-than-optimal coding. The Code Inspector offers various possibilities to define object sets and to combine multiple single checks in so-called "check variants". Single object checks from the Development Workbench You can check a single object with the Code Inspector from the ABAP Editor (transaction SE38), the Function Builder (transaction SE37), the Class Builder (transaction SE24), or the ABAP Data Dictionary (transaction SE11). To do this, choose <object> > Check > Code Inspector from the menu, where <object> can be a program, function module, class, or table. Checks on transport objects from the Transport Organizer You can invoke the Code Inspector from within the Transport Organizer (transaction SE09) to check objects in a transport reques...

What is SAP HANA? The main features of SAP HANA are given below: SAP HANA is a combination of software and hardware innovation to process huge amount of real time data. Based on multi core architecture in distributed system environment. Based on row and column type of data-storage in database. Advantages of SAP HANA Used extensively in Memory Computing Engine to process and analyze massive amount of real time data. It reduces cost of ownership, increases application performance, enables new applications to run on real time environment that were not possible before. It is written in C , supports and runs on only one Operating System Suse Linux Enterprise Server 11 SP1/2. Today, most successful companies respond quickly to market changes and new opportunities. A key to this is the effective and efficient use of data and information by analyst and managers. HANA overcomes the limitations mentioned below: Due to increase in "Data Volume", it is a challenge f...

SAP had released a two versions for BPC 10.1; they are BPC 10.1 Classic and BPC 10.1 Embedded. The Classic version can be considered an extension of previous versions in the BPC family, and can be used to implement both planning and consolidations solutions. The Embedded version utilizes Integrated Planning and BPC features, and is designed for planning only. Integrated Planning (IP) is a planning tool introduced by SAP before BPC came into effect. Let’s look some of the differences between the Classic and Embedded versions from a configuration perspective: 1. Master and transactional data objects Classic Embedded This version utilizes BPC objects i.e., Dimensions for master data and Models for transactional data. When data is saved in BPC, it will be stored in the SAP BW system under the namespace /CPMB. This method is similar to that used in earlier versions of BPC. This version uses the SAP Business Warehouse (BW) system and its objects directly. Characteri...