SAP TUTORIALS

*&---------------------------------------------------------------------* *& Report  YINTERACTIVE_REPORT *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yinteractive_report1  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   60                               LINE - COUNT   255                               MESSAGE - ID  zsan....

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...

ABAP/4 DEVELOPMENT STANDARDS These slides covers Object naming standards, ABAP/4 Programming standards and procedures. These programming standards are intended to aid ABAP/4 programming in the SAP R/3 software development. Naming standards SAP provides their clients with a separate name space for their custom development so that during an upgrade no custom development will be lost (see OSS note 16466).Generally speaking, customer defined objects have to start with a ‘Y’ or ‘Z’.  Naming standards SAP provides their clients with a separate name space for their custom development so that during an upgrade no custom development will be lost (see OSS note 16466). Generally speaking, customer defined objects have to start with a ‘Y’ or ‘Z’.  Following, we will define the standards for the use in this Project. Program The following program naming conventions have to be followed for creating ABAP/4 programs, functions, includes and reports.  Refer to Maintai...