Skip to main content

YCLASSICAL_JOINING

By
*&---------------------------------------------------------------------* *& 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
Post a Comment

SAP had released a two versions for BPC 10.1; they are BPC 10.1 Classic and BPC 10.1 Embedded

Image
By
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.
/wp-content/uploads/2015/11/img_5637d1a5a9056_823992.png

Let’s look some of the differences between the Classic and Embedded versions from a configuration perspective:

1. Master and transactional data objects

ClassicEmbedded
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. Characteristics are used for master data, and data providers like Info Cube, multi providers, and so on are used for transactional data
2. Data loads

ClassicEmbedded
Master and Transactional data must be loaded to the BPC system. Source data can be loaded either from SAP Business Warehouse (BW) or from other external systems, such as flat files.Unlike the classic version, the embedded version uses the SAP Business Warehouse (BW) system directly, so we don’t need to add another layer of data loads for our project implementations.
3. Custom scripts

ClassicEmbedded
In addition to using the predefined scripts provided by SAP (e.g., Copy and Allocations), we can develop custom code to perform calculations using the Logic Script component.This version also provides a few predefined functions, but custom code must be developed using the FOX (Formula Extension) component.
4. Template development

ClassicEmbedded
Input schedules and reports are developed using the EPM Excel Interface. Schedules are used to develop templates which allow users to view and save data to the BPC system, whereas reports are used only to view and analyze data.BEX Query designer is used to developed schedules and reports. The resulting templates are accessed from BPC’s EPM Excel interface and presented to business users.
5. Security

ClassicEmbedded
This version uses both SAP BW and BPC system for security configuration. Users are created in the BW system, then granted permissions for objects and data via BPC.Most security features are configured in the SAP BW system directly, including creating users and granting permissions for objects. Data access can be configured in both the BW and BPC systems.

Comments

Post a Comment

Popular posts from this blog

How to Create SAP ABAP Query Using SQ01 Step by Step Guide

By
How to Create SAP ABAP Query Using SQ01 Step by Step. You can create ABAP query objects ,if they are not exist in the SAP system. You can create SAP query without  ABAP programming knowledge. ABAP Query provides users with a variety of ways to define and create different types of  reports , such as  Basic Lists ,  Stats , and  Sorted Lists . ABAP query consists of four elements: Queries InfoSets Groups Translation query Queries The query component is used by end users for Queries. You can create queries, change and queries executed. Transaction  SQ01. Trnslation component / QUERY Many texts to define queries, InfoSets and user groups are generated. These texts are displayed in the language we choose to access the SAP system. We can compare the text or languages ​​that use this component. InfoSets InfoSets are the views of the Special Data Sources. An InfoSet Describes the fields of a data source that can be reported in the query. An InfoSet can be assig
Post a Comment
More

BADI in SAP ABAP Step by Step

By
BADI in SAP ABAP Step by Step BAdI Acronym of Business Add Ins As a customer outsider, it helps BAdI to improve SAP functionality. Why is BADI? Unlike previous improvement methods, BADI continues the approach aimed at re-use objectives. BADI can be used in a number of times that these standard evaluation techniques can only be used once. For example, if you are upgrading a custom project, you can not map the extension on other custom projects. In order to overcome this disadvantage, SAP provided a new evaluation technique called BADI. Code of transaction for BADI definition: SE18 When you create a BAdI definition, you create a class interface automatically and you can define the methods in the interface. The application of the methods can be made in SE19 transactions. When created BAD, they are generated automatically: An interface with 'IF_EX_' is inserted between the first and second characters of the BAdi name Class classified as 'CL_EX_' inserted betwee
Post a Comment
More

BDC Recording in SAP ABAP

By
BDC Recording in SAP ABAP Here ,I explained The Steps to record any  Transaction (Example: VA01) to create BDC(Batch Data Communication) Program. Step 1  Execute transaction  SHDB  . Step 2  Enter  name  for recording  Step 3  Enter  transaction  to be executed Step 4  The transaction will now be executed, simply enter the values in the screen fields which you want to record.  Step 5  Once you have finished the recording and selected the  save  button or exit the transaction you  Creating an ABAP program Using a BDC recording   Go to SHDB Transaction Code and Click on New Recording. Give the Record name and Transaction code and click on Start New Recording Button. Now enter the Bank country and Key Now enter the Bank name ,City ,country and street.  Now Save the Recording . Now select the created record and click on Program. Now give the program title and select radio button transfer from recording. Now give the program title and click on
Post a Comment
More