*&---------------------------------------------------------------------* *& Report YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT yclassical_joining NO STANDARD PAGE HEADING LINE - SIZE 110 LINE - COUNT 255 MESSAGE - ID zsan. ** T Y P E D E C L A R A T I O N ** TYPES : BEGIN OF ty_mara, matnr TYPE matnr, ernam TYPE ernam, pstat TYPE pstat_d, END OF ty_mara, BEGIN OF ty_makt, matnr TYPE matnr, spras TYPE spras, maktx TYPE maktx, END OF ty_makt, BEGIN OF ty_final, matnr TYPE matnr, ernam TYPE ernam, pstat TYPE pstat_d, maktx TY
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