#sap bpc definition

[iqonlinetraining]

SAP BPC Introduction - Terminologies & Applications of SAP BPC

SAP BPC Introduction:

SAP BPC stands for SAP Business Planning and Consolidation (BPC). It is a tool that supports all operational and financial activities in an organization. SAP BPC coordinates in automating and streamlining business forecast, planning, and consolidation activities in an organization.

There are two types of migration that was supported by SAP BPC. They are as follows:

·         SAP Netweaver and

·         Microsoft Excel

BPC with Microsoft version enables to perform modeling, application maintenance, importing data and applying transformations, creating scripts, etc. It provides the user with an Enterprise Power Management (EPM) solution, a collaborative tool with the robust and readily accepted environment.

It also provides support for existing Microsoft functionality and various enhancement features like drag and drop report builder etc.

SAP BPC Key Benefits:

Following are the key benefits of SAP BPC −

·         It permits the user to take the right decisions for the business by supporting what-if analysis and it lets to perform scenario-based planning.

·         It also permits to collaborate data and thus increase accuracy in business planning and accountability.

·         It allows in aligning the plans with strategic desires and that results in lowering the cycle time.

·         There is an option available to choose the version of SAP Netweaver or Microsoft Platform.

SAP BPC - Terminologies

·         Environment − It is described as the starting point for growing any software or version. It changed into referred to as Application sets or AppSet in older versions of BPC.

·         Dimensions − Marking a dimension as a comfy is possible. By granting read and write access to the users who use the model, they can access the data.

·         Properties − This terminology is used to provide additional information to the dimension.

·         Dimension Members − Each dimension member file indicates master, textual content and hierarchy data associated with the keys of dimension.

·         Model − To meet the Business Planning and Consolidation requirement of an organization, you need to build a version in an environment that is defined as a series of numerous dimensions.

·         Data Manager Package − Data Manager Package is required to execute common tasks in BPC.

·         Business Rules − To manipulate operations in distinctive international locations, exclusive set of business policies are required. BPC consists of the rule-based table to satisfy a few requirements for enterprise planning and consolidation. Various regulations may be set related to enterprise making plans and consolidation like - forex translation, balance convey forward, intercompany removal, and statistical validation, and so on.

·         Logic Scripts − This is described as a hard and fast of SQL or MDX programming shape to carry out a few customize capabilities for flexibility and manage statistics models. When a few particular necessities are not completed using business guidelines that can be met by the use of Logic Scripts.

·         User − A user is defined as an individual. The user uses the application in an Appset.

·         Team − Group of users based on user roles is defined as a team.

·         Task − Tasks are nothing but the activities that are performed in SAP BPC system.

Applications of SAP BPC

An Application in BPC machine is described as a multi-dimensional records version used in EPM. Few examples of Applications are - Operation, Legal or Finance group.

There are two types of applications in BPC system - Reporting and Non-Reporting.

·         Reporting applications are used for analysis cause and you can skip inputs from the users.

·         Non-Reporting programs are used to include reference facts like foreign money rates, bring forward balances, etc.

[the-steve-me]

Is ABAP from SAP worth studying today?

Yes, it is worth learning when used in the context of other applications like ABAP for HANA, ABAP for S4HANA, ABAP for BW, ABAP for BPC, ABAP for CRM, etc. ... Learning itself won't harm, but make sure you use it as a stepping stone and with experience jump to more advanced applications.

you will definitely get a good pay package. Moreover, just being good at programming does not help a consultant to excel in ABAP as it is very essential to have sound functional knowledge. After working for 10 -12 years as an ABAP consultant, one can perform less coding and more design/architectural/lead jobs.

What is the future of SAP ABAP?

ABAP is considered an important part of SAP, which is the most robust and reliable platform for business application development. ABAP has been a component of SAP and has helped in the coding of many legacy systems, that can't be redone in Java so easily

[craigbrownphd-blog-blog]

Step by step creation of Environment, Models and Dimensions in BPC

Hi all, Today I will discuss about three basics and very core concepts of BPC, and then will share some definition and step by step process to create all these three objects, this document is for those who are beginner in BPC. * Environment * Dimension * Model Environment * Environment can be defined as the base components which doesn’t contain physical data. It can be considered as INFOAREA from BW perspective, which acts as a folder. * Environment can’t be created by our own, we have to take copy from existing environment only. * SAP provides one standard environment which is called as “ENVIRONMENTSHELL”. * As an example, we can consider MouriTech as one environment NOTE: – It is highly recommended not to do modification and changes directly to “ENVIRONMENTSHELL”.   Steps to create Environment in BPC. * Logon to BPC with username and password.     2) In Library folder, go to bottom(Right) of the page in which existing name of the Environment is displayed which is always delivered by SAP, like ENVIRONMENT: ENVIRONMET_COMPANYNAME, or in most of case termed as ENVIRONMENTSHELL   3) Single click on Environment will bring one popup screen for you, then go to manage all environment, here we can get list of Environment which is delivered by SAP along with the list of Environment which is being copied by user. 4)To create copy from standard Environment, simply click on the SAP delivered Environment, when you will click on the Environment, “COPY” icon will get enable, click on “COPY”, a popup will appear which ask you for ENIRONMENT ID: and description. Provide check marks to copy a)Data in Models b) Web Documents c) Document to the newly created Environment as per your requirements.   NOTE: Copying Environment will take some time to copy. MODELS Models :- A model is built inside an Environment , It is collection of several dimensions and are designed to meet the planning and consolidation requirements of an organization, For instance in a company, we might have model for “ANALYTICS” , “TECHNICAL”, “HR” etc. It can be compared with InfoCube in BW terminology. * Model will be used to store transaction data. * There are two types of models * Standard Model 2)      Embedded Model STANDARD MODEL : This model is designed by SAP to provide a protected area for customers who to plan and consolidate in their own department without wanting to share or coordinate the resources with other Business Warehouse community users. It has protected namespace starting with  “/CPMB/” EMBEDDED MODEL : This model is different from Standard model and includes data access to all community users. In short, you can say that in embedded model, any number of InfoProviders can be assigned to a single BPC model/application.     Steps to create Standard Model 1)      After login into BPC application   2) Go to Administration page.   3) Click on Models and you will get list of all standard and Embedded models which is being already created, to create a new model click on new.   4) Provide name and description of the model click on next.   5) Under source model, click on blank model , since we are creating this for first time and do not want to copy from the existing models then click on next.     6)Now choose standard radio button from the list, in data entry mode we have default entry as Periodic for standard models. Click on next. 7) In this step, choose all mandatory dimensions which are A,C,E,T along with dimensions you wish to add in your model, click on next   8) Now in copy from you will find blank, since we started from blank model, click on next. 9)      In the final step review and create, we can see name of the model with their dimensions, click on create, you will get a message “Model has been created. You can close the window” 10) You can see your model created in the model list. DIMENSIONS: It is used to store master data. In BW language it can be compared with Infoobject. SAP has given ten dimension type (9- standard,1-user defined) Steps to create Dimension 1) After login into BPC application 2)Go to Administration page. 3) Click on dimensions and you will get list of all dimensions which is being already created, to create a new dimension click on new. 4)Provide your Dimension ID and description 5) Once created, it will show structure of dimension which is automatically created by system with some specific properties and can’t be changed. The system generated properties will be highlighted in light blue list of rows. 6) Here you can add new dimensions and also can create hierarchies for the existing dimensions, in this case I have created one hierarchies with dimension  GL_ACCOUNT 7) You can give referential integrity if you want to give reference with the existing dimension, in my case I have chosen none. 8) Click on save to create your dimension 9) Here in dimension list, you can see your dimension created   To understand relation between Environment, models and dimensions in simple language, see below diagram.     NOTE- one dimension can be reused in multiple models but all these models belongs to same environment only.     http://bit.ly/2pjO0Nv #SAP #SAPCloud #AI

[hireindianpvtltd]

Fwd: Urgent requirements of below positions

New Post has been published on https://www.hireindian.in/fwd-urgent-requirements-of-below-positions-28/

Fwd: Urgent requirements of below positions

Please find the Job description below, if you are available and interested, please send us your word copy of your resume with following detail to vendor@vinsysinfo.com or please call me on 703-594-5490 to discuss more about this position.

SAP BPC Developer——–>Universal City CA K2 Support Analyst——–>Farmington, CT Senior Developer———>RTP, NC K2 Support Lead——–>Farmington, CT Senior Analyst——->West Point, PA STARLIMS Test Lead——–>Kankakee, IL or King of Prussia, PA Oracle OPA Developer———->Winooski, VT

    Job Description Apply

Job title: SAP BPC Developer

Location: Universal City CA

Duration: 8 -12 months

  Job description:

Develop, enhance and support:  

Custom BADI’s associated with BPC

HANA views and AMDP for BPC, BW and Analysis for Office

Employ techniques to optimize code performance and efficiency

Perform data and system analysis tasks, in order to troubleshoot errors and user questions

Understand business processes and requirements by engaging with business partners at enterprise and division levels

Participate in business requirement definition sessions

Craft adaptable, comprehensive and feasible solutions by creating necessary blueprint documents for technical specifications

Collaborate with peers in the Coe to apply best practices to integrate between SAP applications (ERP, HANA, BW and BPC)

Continually identify ways to improve support and decrease unnecessary support calls. Identify improvements to applications, processes, and business logic to meet user needs

Proficient with SAP HANA View development including usage of SQL, AMDP and ABAP

Experience with data integration into SAP BPC (Standard version 10.x) including BADI and Data Manager Package development

Apply Job

Job Title: K2 Support Analyst

Location: Farmington, CT

Duration: contract

Work Authorization: USC/GC/H1

Mandatory skills: K2 Blackpearl, REX

  Job Description:

Triage the issues/defects (high level) and communicate with development team if there is no workaround/solution to resolve the ticket.

Provide necessary information / logs (on demand) to development team to fix the issues.

Do root cause analysis.

Communicate the status of the issues / defects.

Hand off the current tickets to next person in shift

Expertise in K2 Blackpearl with REX of 5 years,

Knowledge of MS SharePoint and MS SQL an added advantage, experience in application support

Apply Job

Job title: Senior Developer

Location: RTP, NC

Duration: 8 months

  Mandatory Skills: REST/SOAP Web services development with Track wise

   Job description:

5+ years of experiences in Track wise and web services  development

Lead the development for Track wise system including but not limited to go-live coordination/planning, routine infrastructure maintenance outages, break-fixes and complex enhancements.

Implement configuration changes, Perform technical tasks, software installations, environment refreshes, backups, performance measurement for Track Wise application.

Create/modify crystal reports based on business needs.

Create and modify web services using REST/SOAP

Prepare test cases/scripts, execute them and coordinate with IT Quality (Computer System Validation) group for reviews and approvals.

Prepare and follow business documentation, work instructions, SOPs and knowledge management information for applications supported.

Document application changes and configuration in appropriate change control and change management systems

Apply Job

Job Title: K2 Support Lead

Location: Farmington, CT

Duration: Contract

  Mandatory skills: K2 Blackpearl, REX

  Job Description:

User role administration

Communicate any down time with stake holders

Clarify the issues from end users / workflow status by communicating with development team

Coordinate with Sr. developers in delivery team to close the issues within SLA.

Updating the KEDB.

Suggest ways to reduce the defects as per RCA

Application health check

Communicating various status with stake holders

Participating in DR exercise, capacity planning, auditing etc.

Triaging the issues/tickets & coordinating with development teamExpertise in K2 Blackpearl with around 7 years of REX, Working knowledge of MS SharePoint, MS SQL, experience in application support, Monitoring and Capacity planning

Apply Job

Job title: Senior Analyst        

Location: West Point, PA

Duration: 1 Year

  Mandatory Skills: Lab ware LIMS, LIMS Basic, Lab ware Static Data Building, PL/SQL

  Job description:

Experience with Lab ware LIMS implementation, especially Lab ware 7.

Experience with Static data building.

Extensive Experience with GxP SDLC process. 

Apply Job

Job Title: STARLIMS Test Lead    

Location: Kankakee, IL or King of Prussia, PA  

Duration: 6 Months + 

  Mandatory Skills: STARLIMS

  Job description:

8 to 10 years of experience in the field of testing and Quality Assurance and must have played the role of a test lead for at least 5+ years.

Experience using test management tool, HP ALM and GxP validation approval workflows (either paper or electronic) is a must.

Experience as a tester or test lead in field of Laboratory Information Management Systems (LIMS) applications. Experience in Abbott STARLIMS application is desirable.

Experience with system/functional testing, integrations testing, data migration testing and UAT coordination. Experience in test script creation and testing in a validated environment.

Experience leading test automation in projects. Experience creating and executing test automation scripts is desirable.

Experience working in a cross-functional collaborative environment with teams spread globally across time zones

Strong understanding of 21 CFR part 11, GAMP and standard Good Documentation Practices (GDP) for GxP projects.

Apply Job

Job Title: Oracle OPA Developer

Location: Winooski, VT

Duration: 6 months

Experience:8+ Years

Mandatory skills: Oracle OPA, OPM, Webservices.

  Job Description:

Oracle OPA Developer Resource will be working with Optum State Government Solutions on State of Vermont OFE Migration and Oracle Software stack upgrade projects.

TOP REQUIREMENTS:

Oracle OPA, OPM, Webservices.

 What experience will set candidates apart from one another?

Oracle OPA 11g to 12C migration experience and 12C OPA exposure.

INFO: OPA developer supporting the VT OFE migration and additional Oracle upgrade CR project. This resource will be the OPA developer for 12C implementation and migration from the current DMZ environment version 11.1.1.7 to OFE enclave, which includes upgrading Oracle OPA application to 12C and associated integration. This position requires 8+ years Oracle OPA application development and configuration experience and extensive OPA integration experience. This resource will be responsible for providing senior-level technical troubleshooting on complex issues requiring rapid resolution related to Oracle OPA applications and environments during the migration and upgrade. This resource will be responsible for custom code migrations, OPA configurations, SW version updates, and application component integrations and external partner integrations as required for the move to the new OFE enclave.

Required Qualifications:

Analyze business requirements and transform them to OPA rules

Coordinate with business team to gather detailed understanding of business requirements and raise clarifications if needed

Design and document the technical design and to be able to demonstrate technical design to appropriate stakeholder for review.

Implement rules, screens, test scripts in OPM and unit test the functionality in OPM

Test the complete business requirement end-to-end by integrating OPA with external systems

Perform necessary support to issues reported on production environment if needed

Upgrade the current 10.4 OPA rulebase system to the latest Cloud Version 12

Must have skills:

Hands-on experience in implementing OPA Rules for different business scenarios

Well-versed with authoring OPA rules in both Word and Excel

Good Knowledge of cross-entity reasoning/referencing (scoping functions in OPA)

Good knowledge of Temporal Based Reasoning and implementation of rules using TBR

Should be able to create and manage Screens and Screen flows

Writing test scripts in OPM

Testing and debugging rules in Oracle Determinations Server and Oracle Web Determinations

Should have excellent written and oral COMMUNICATION skills

Must have strong analytical and design capabilities to be able to transform business requirements into fully functional rules and to design a system with high quality and performance

Prior experience with working on the latest OPA Cloud Version (12)

Nice to have skills:

Knowledge of Assess and Interview web service calls to be able to integrate OPA with external systems

Experience in healthcare domain

Apply Job

  Thanks, Steve Hunt Talent Acquisition Team – North America Vinsys Information Technology Inc SBA 8(a) Certified, MBE/DBE/EDGE Certified Virginia Department of Minority Business Enterprise(SWAM) 703-594-5490 www.vinsysinfo.com

    To unsubscribe from future emails or to update your email preferences click here .

[sanuchete-blog]

SAP BPC Training - What You Need To Learn

In the current business earth the people looking to stay used should adjust to change rapidly and often be increasing their knowledge. It can also be important to be updated on the normal techniques, standards and applications. The sap is the first choice on the planet in giving company software to aid companies in development and putting value to their business. Present in around 120 companies global SAP solutions international companies in addition to small to medium, sized regional businesses. Using the prospect to master drain will be the best expense you may make in your career marketability. The sap is definitely an composition for Systems, Programs and Services and products in data processing. The SAP Company Suite computer software is designed to allow companies to get better perspective across all areas of their company with the added advantage of being able to respond easily with complete information.

That provides mobility and effectiveness to company operations leading to the capacity to lower prices and optimize performance. The SAP Business Room is made up of five purposes, the primary being SAP ECC. Customer Relationship Management (CRM), Item Lifecycle Management (PLM), Offer Chain Management (SCM) and Company Relationship Management (SRM) are all the main Organization Suite. SAP could be discovered in segments to create it quicker to upgrade your information on unique parts first. As an example, if your focus is Customer Relationship Management you can examine the CRM element before seeking any areas. Self-study instruments can be found online to permit'at your speed'understanding and mix hands-on practice with classroom theory. You'll find movie education and online scholar help to help you around locations that may be causing you problems. Training your self, SAP can be achieved in a variety of ways. Sites offer tools, exercise time and online support.

Reference manuals are available to master every facet of SAP, many with a computer-based source to permit you to be guided detailed when needed. Several publications can have areas that focus on and explain common issues which can be often encountered as well. Still another essential method to find in just about any SAP teaching books. Self-learning SAP may benefit you by allowing you to refine the places you find difficult and give attention to the area's most important to you. You are able to easier concentrate on parts many relevant, even if they corner into still another module or modules. This enables your learning how to be more unique to your needs and better targeted to match you. Different areas of great interest for many who are understanding SAP independently would be the SDN and SUGEN.

The SAP Creator Network (SDN) is a consumer centered community of business analysts, developers, consultants and integrators that reveal their information through the utilization of instruction products, websites, conversation boards and a complex library. The SAP Person Group Executive System (SUGEN) allows people to share information and methods across many SAP consumer groups. You will find other user-based towns like the two in the list above, made to help people at all degrees of experience, which will be especially helpful to someone understanding the procedures themselves. The experts who make an effort and foresight to master sap not only increase their value as a member of staff but open new job trails for themselves. The worker of today should be much more centered on creating themselves useful to incorporate value for their company.

[craigbrownphd-blog-blog]

Step by step creation of Environment, Models and Dimensions in BPC

Hi all, Today I will discuss about three basics and very core concepts of BPC, and then will share some definition and step by step process to create all these three objects, this document is for those who are beginner in BPC. * Environment * Dimension * Model Environment * Environment can be defined as the base components which doesn’t contain physical data. It can be considered as INFOAREA from BW perspective, which acts as a folder. * Environment can’t be created by our own, we have to take copy from existing environment only. * SAP provides one standard environment which is called as “ENVIRONMENTSHELL”. * As an example, we can consider MouriTech as one environment NOTE: – It is highly recommended not to do modification and changes directly to “ENVIRONMENTSHELL”.   Steps to create Environment in BPC. * Logon to BPC with username and password.     2) In Library folder, go to bottom(Right) of the page in which existing name of the Environment is displayed which is always delivered by SAP, like ENVIRONMENT: ENVIRONMET_COMPANYNAME, or in most of case termed as ENVIRONMENTSHELL   3) Single click on Environment will bring one popup screen for you, then go to manage all environment, here we can get list of Environment which is delivered by SAP along with the list of Environment which is being copied by user. 4)To create copy from standard Environment, simply click on the SAP delivered Environment, when you will click on the Environment, “COPY” icon will get enable, click on “COPY”, a popup will appear which ask you for ENIRONMENT ID: and description. Provide check marks to copy a)Data in Models b) Web Documents c) Document to the newly created Environment as per your requirements.   NOTE: Copying Environment will take some time to copy. MODELS Models :- A model is built inside an Environment , It is collection of several dimensions and are designed to meet the planning and consolidation requirements of an organization, For instance in a company, we might have model for “ANALYTICS” , “TECHNICAL”, “HR” etc. It can be compared with InfoCube in BW terminology. * Model will be used to store transaction data. * There are two types of models * Standard Model 2)      Embedded Model STANDARD MODEL : This model is designed by SAP to provide a protected area for customers who to plan and consolidate in their own department without wanting to share or coordinate the resources with other Business Warehouse community users. It has protected namespace starting with  “/CPMB/” EMBEDDED MODEL : This model is different from Standard model and includes data access to all community users. In short, you can say that in embedded model, any number of InfoProviders can be assigned to a single BPC model/application.     Steps to create Standard Model 1)      After login into BPC application   2) Go to Administration page.   3) Click on Models and you will get list of all standard and Embedded models which is being already created, to create a new model click on new.   4) Provide name and description of the model click on next.   5) Under source model, click on blank model , since we are creating this for first time and do not want to copy from the existing models then click on next.     6)Now choose standard radio button from the list, in data entry mode we have default entry as Periodic for standard models. Click on next. 7) In this step, choose all mandatory dimensions which are A,C,E,T along with dimensions you wish to add in your model, click on next   8) Now in copy from you will find blank, since we started from blank model, click on next. 9)      In the final step review and create, we can see name of the model with their dimensions, click on create, you will get a message “Model has been created. You can close the window” 10) You can see your model created in the model list. DIMENSIONS: It is used to store master data. In BW language it can be compared with Infoobject. SAP has given ten dimension type (9- standard,1-user defined) Steps to create Dimension 1) After login into BPC application 2)Go to Administration page. 3) Click on dimensions and you will get list of all dimensions which is being already created, to create a new dimension click on new. 4)Provide your Dimension ID and description 5) Once created, it will show structure of dimension which is automatically created by system with some specific properties and can’t be changed. The system generated properties will be highlighted in light blue list of rows. 6) Here you can add new dimensions and also can create hierarchies for the existing dimensions, in this case I have created one hierarchies with dimension  GL_ACCOUNT 7) You can give referential integrity if you want to give reference with the existing dimension, in my case I have chosen none. 8) Click on save to create your dimension 9) Here in dimension list, you can see your dimension created   To understand relation between Environment, models and dimensions in simple language, see below diagram.     NOTE- one dimension can be reused in multiple models but all these models belongs to same environment only.     http://bit.ly/2FzyfMp #SAP #SAPCloud #AI

[craigbrownphd-blog-blog]

Step by step creation of Environment, Models and Dimensions in BPC

Hi all, Today I will discuss about three basics and very core concepts of BPC, and then will share some definition and step by step process to create all these three objects, this document is for those who are beginner in BPC. * Environment * Dimension * Model Environment * Environment can be defined as the base components which doesn’t contain physical data. It can be considered as INFOAREA from BW perspective, which acts as a folder. * Environment can’t be created by our own, we have to take copy from existing environment only. * SAP provides one standard environment which is called as “ENVIRONMENTSHELL”. * As an example, we can consider MouriTech as one environment NOTE: – It is highly recommended not to do modification and changes directly to “ENVIRONMENTSHELL”.   Steps to create Environment in BPC. * Logon to BPC with username and password.     2) In Library folder, go to bottom(Right) of the page in which existing name of the Environment is displayed which is always delivered by SAP, like ENVIRONMENT: ENVIRONMET_COMPANYNAME, or in most of case termed as ENVIRONMENTSHELL   3) Single click on Environment will bring one popup screen for you, then go to manage all environment, here we can get list of Environment which is delivered by SAP along with the list of Environment which is being copied by user. 4)To create copy from standard Environment, simply click on the SAP delivered Environment, when you will click on the Environment, “COPY” icon will get enable, click on “COPY”, a popup will appear which ask you for ENIRONMENT ID: and description. Provide check marks to copy a)Data in Models b) Web Documents c) Document to the newly created Environment as per your requirements.   NOTE: Copying Environment will take some time to copy. MODELS Models :- A model is built inside an Environment , It is collection of several dimensions and are designed to meet the planning and consolidation requirements of an organization, For instance in a company, we might have model for “ANALYTICS” , “TECHNICAL”, “HR” etc. It can be compared with InfoCube in BW terminology. * Model will be used to store transaction data. * There are two types of models * Standard Model 2)      Embedded Model STANDARD MODEL : This model is designed by SAP to provide a protected area for customers who to plan and consolidate in their own department without wanting to share or coordinate the resources with other Business Warehouse community users. It has protected namespace starting with  “/CPMB/” EMBEDDED MODEL : This model is different from Standard model and includes data access to all community users. In short, you can say that in embedded model, any number of InfoProviders can be assigned to a single BPC model/application.     Steps to create Standard Model 1)      After login into BPC application   2) Go to Administration page.   3) Click on Models and you will get list of all standard and Embedded models which is being already created, to create a new model click on new.   4) Provide name and description of the model click on next.   5) Under source model, click on blank model , since we are creating this for first time and do not want to copy from the existing models then click on next.     6)Now choose standard radio button from the list, in data entry mode we have default entry as Periodic for standard models. Click on next. 7) In this step, choose all mandatory dimensions which are A,C,E,T along with dimensions you wish to add in your model, click on next   8) Now in copy from you will find blank, since we started from blank model, click on next. 9)      In the final step review and create, we can see name of the model with their dimensions, click on create, you will get a message “Model has been created. You can close the window” 10) You can see your model created in the model list. DIMENSIONS: It is used to store master data. In BW language it can be compared with Infoobject. SAP has given ten dimension type (9- standard,1-user defined) Steps to create Dimension 1) After login into BPC application 2)Go to Administration page. 3) Click on dimensions and you will get list of all dimensions which is being already created, to create a new dimension click on new. 4)Provide your Dimension ID and description 5) Once created, it will show structure of dimension which is automatically created by system with some specific properties and can’t be changed. The system generated properties will be highlighted in light blue list of rows. 6) Here you can add new dimensions and also can create hierarchies for the existing dimensions, in this case I have created one hierarchies with dimension  GL_ACCOUNT 7) You can give referential integrity if you want to give reference with the existing dimension, in my case I have chosen none. 8) Click on save to create your dimension 9) Here in dimension list, you can see your dimension created   To understand relation between Environment, models and dimensions in simple language, see below diagram.     NOTE- one dimension can be reused in multiple models but all these models belongs to same environment only.     http://bit.ly/2oYGqay #SAP #SAPCloud #AI

[craigbrownphd-blog-blog]

Characteristic Relationship editor in BW Modeling Tools

Before getting started, a brief introduction about myself : I am a quality specialist working on the Quality and validation of the products like SAP BW/4HANA and BW modeling tools.I work specifically in the BW integrated Planning Area. Most of us are excited about exploring the new functionalities provided by SAP BW Modeling tools. With the Version 1.18 of SAP BW Modeling tools we have a new editor with respect to the BW Integrated Planning topic which is the Characteristic Relationship editor.   The following blog post will help the readers discover new functionality which is specific to BW Integrated planning community and as a whole to the BW/4HANA product community. please refer to the below link in case if you want to know what is a characteristic relationship in SAP BW integrated Planning : https://help.sap.com/viewer/0ecf5244825c4742a7b062a89d11c2ac/7.5.7/en-US/4cb82d6b54182102e10000000a42189e.html This blog shows the steps on how to create a Characteristic relationship using the brand new editor in BW modeling tools. Please, not that this Editor is only available for the BW projects created on BW/4HANA systems. Prerequisite: SAP BW Modelling tools version should be of 1.18 and above. Steps to Create a characteristic relationship in the BW modeling tools: * Connect to BW Modelling tools and login to the respective system in the BW project(BW/4HANA project with BPC add-on enabled).   * Choose an infoarea which has plannable infoproviders.Open any planning enabled infoprovider (Any plan enabled Cube like ADSO or DSO like ADSO ), Please note that we can only create Characteristic relationship on top of the above-mentioned providers. * Later right click on the provider in the project explorer screen. You will be able to choose the option to ‘Open Characteristic Relation’.   * The characteristic Relation editor will be opened in the right side pan. The General settings tab will look something like in the below screenshot:   * In the General settings, You can change the values for the Key Date. If the scenario is to save the plan data, we can provide the planning sequence name for the save of planned data.And also the aggregation level name for reading the changed data. The use of these options is similar to those in the RSPLAN transaction for Characteristic Relationship in BW system. Please refer to the below document in case if you want to know more about using the central settings options in the Characteristic Relationship. https://help.sap.com/viewer/0ecf5244825c4742a7b062a89d11c2ac/7.5.7/en-US/478dc648db0741359f726481d4309dcd.html * In the Characteristic Relations tab, choose the type of Characteristic relation you wish to create.This can be done clicking on the corresponding type of Add option (say Add attribute for attribute type Characteristic Relationship, Add exit for Exit type Characteristic Relationship etc).   * For example, let’s create Attribute type Characteristic Relationship. So click on Add Attribute (please note that the infoobjects selected have the attribute relation i.e.. one infoobject should be added as the attribute of another).Add the base infoobject for which attribute is defined.   * Once we have added the base infoobject , Now in the Used characteristics tab we add the attribute infoobjects of the base infoobjects.     * Once the infoobjects are added for the attribute type of Characteristic Relationship. Click the checkbox to make the Characteristic Relationship active.Check the Characteristic Relationship for consistency, it should be consistent with respect to the definition. If any inconsistency found, please correct the errors and check again.   * Save the Characteristic Relationship. And the created Characteristic Relationship can be used to generate valid combinations during the execution of planning functions. The procedure is the same for the creation of other types of Characteristic Relationships like Hierarchy, DSO, and Exit. Based on the type of the Characteristic Relationship, the relevant options are to be checked in the editor.   This is the way in which we can use the new Eclipse-based editor to create the characteristic relationships without the need to go back to the RSPLAN transaction in the backend BW/4HANA system. Feel free to post your questions or comments if any.   Thanks & Best Regards, Tharun. http://bit.ly/2Bnu7vK #SAP #SAPCloud #AI

[craigbrownphd-blog-blog]

Characteristic Relationship editor in BW Modeling Tools

Before getting started, a brief introduction about myself : I am a quality specialist working on the Quality and validation of the products like SAP BW/4HANA and BW modeling tools.I work specifically in the BW integrated Planning Area. Most of us are excited about exploring the new functionalities provided by SAP BW Modeling tools. With the Version 1.18 of SAP BW Modeling tools we have a new editor with respect to the BW Integrated Planning topic which is the Characteristic Relationship editor.   The following blog post will help the readers discover new functionality which is specific to BW Integrated planning community and as a whole to the BW/4HANA product community. please refer to the below link in case if you want to know what is a characteristic relationship in SAP BW integrated Planning : https://help.sap.com/viewer/0ecf5244825c4742a7b062a89d11c2ac/7.5.7/en-US/4cb82d6b54182102e10000000a42189e.html This blog shows the steps on how to create a Characteristic relationship using the brand new editor in BW modeling tools. Please, not that this Editor is only available for the BW projects created on BW/4HANA systems. Prerequisite: SAP BW Modelling tools version should be of 1.18 and above. Steps to Create a characteristic relationship in the BW modeling tools: * Connect to BW Modelling tools and login to the respective system in the BW project(BW/4HANA project with BPC add-on enabled).   * Choose an infoarea which has plannable infoproviders.Open any planning enabled infoprovider (Any plan enabled Cube like ADSO or DSO like ADSO ), Please note that we can only create Characteristic relationship on top of the above-mentioned providers. * Later right click on the provider in the project explorer screen. You will be able to choose the option to ‘Open Characteristic Relation’.   * The characteristic Relation editor will be opened in the right side pan. The General settings tab will look something like in the below screenshot:   * In the General settings, You can change the values for the Key Date. If the scenario is to save the plan data, we can provide the planning sequence name for the save of planned data.And also the aggregation level name for reading the changed data. The use of these options is similar to those in the RSPLAN transaction for Characteristic Relationship in BW system. Please refer to the below document in case if you want to know more about using the central settings options in the Characteristic Relationship. https://help.sap.com/viewer/0ecf5244825c4742a7b062a89d11c2ac/7.5.7/en-US/478dc648db0741359f726481d4309dcd.html * In the Characteristic Relations tab, choose the type of Characteristic relation you wish to create.This can be done clicking on the corresponding type of Add option (say Add attribute for attribute type Characteristic Relationship, Add exit for Exit type Characteristic Relationship etc).   * For example, let’s create Attribute type Characteristic Relationship. So click on Add Attribute (please note that the infoobjects selected have the attribute relation i.e.. one infoobject should be added as the attribute of another).Add the base infoobject for which attribute is defined.   * Once we have added the base infoobject , Now in the Used characteristics tab we add the attribute infoobjects of the base infoobjects.     * Once the infoobjects are added for the attribute type of Characteristic Relationship. Click the checkbox to make the Characteristic Relationship active.Check the Characteristic Relationship for consistency, it should be consistent with respect to the definition. If any inconsistency found, please correct the errors and check again.   * Save the Characteristic Relationship. And the created Characteristic Relationship can be used to generate valid combinations during the execution of planning functions. The procedure is the same for the creation of other types of Characteristic Relationships like Hierarchy, DSO, and Exit. Based on the type of the Characteristic Relationship, the relevant options are to be checked in the editor.   This is the way in which we can use the new Eclipse-based editor to create the characteristic relationships without the need to go back to the RSPLAN transaction in the backend BW/4HANA system. Feel free to post your questions or comments if any.   Thanks & Best Regards, Tharun. http://bit.ly/2EQ5ZBz #SAP #SAPCloud #AI

[craigbrownphd-blog-blog]

Characteristic Relationship editor in BW Modeling Tools

Before getting started, a brief introduction about myself : I am a quality specialist working on the Quality and validation of the products like SAP BW/4HANA and BW modeling tools.I work specifically in the BW integrated Planning Area. Most of us are excited about exploring the new functionalities provided by SAP BW Modeling tools. With the Version 1.18 of SAP BW Modeling tools we have a new editor with respect to the BW Integrated Planning topic which is the Characteristic Relationship editor.   The following blog post will help the readers discover new functionality which is specific to BW Integrated planning community and as a whole to the BW/4HANA product community. please refer to the below link in case if you want to know what is a characteristic relationship in SAP BW integrated Planning : https://help.sap.com/viewer/0ecf5244825c4742a7b062a89d11c2ac/7.5.7/en-US/4cb82d6b54182102e10000000a42189e.html This blog shows the steps on how to create a Characteristic relationship using the brand new editor in BW modeling tools. Please, not that this Editor is only available for the BW projects created on BW/4HANA systems. Prerequisite: SAP BW Modelling tools version should be of 1.18 and above. Steps to Create a characteristic relationship in the BW modeling tools: * Connect to BW Modelling tools and login to the respective system in the BW project(BW/4HANA project with BPC add-on enabled).   * Choose an infoarea which has plannable infoproviders.Open any planning enabled infoprovider (Any plan enabled Cube like ADSO or DSO like ADSO ), Please note that we can only create Characteristic relationship on top of the above-mentioned providers. * Later right click on the provider in the project explorer screen. You will be able to choose the option to ‘Open Characteristic Relation’.   * The characteristic Relation editor will be opened in the right side pan. The General settings tab will look something like in the below screenshot:   * In the General settings, You can change the values for the Key Date. If the scenario is to save the plan data, we can provide the planning sequence name for the save of planned data.And also the aggregation level name for reading the changed data. The use of these options is similar to those in the RSPLAN transaction for Characteristic Relationship in BW system. Please refer to the below document in case if you want to know more about using the central settings options in the Characteristic Relationship. https://help.sap.com/viewer/0ecf5244825c4742a7b062a89d11c2ac/7.5.7/en-US/478dc648db0741359f726481d4309dcd.html * In the Characteristic Relations tab, choose the type of Characteristic relation you wish to create.This can be done clicking on the corresponding type of Add option (say Add attribute for attribute type Characteristic Relationship, Add exit for Exit type Characteristic Relationship etc).   * For example, let’s create Attribute type Characteristic Relationship. So click on Add Attribute (please note that the infoobjects selected have the attribute relation i.e.. one infoobject should be added as the attribute of another).Add the base infoobject for which attribute is defined.   * Once we have added the base infoobject , Now in the Used characteristics tab we add the attribute infoobjects of the base infoobjects.     * Once the infoobjects are added for the attribute type of Characteristic Relationship. Click the checkbox to make the Characteristic Relationship active.Check the Characteristic Relationship for consistency, it should be consistent with respect to the definition. If any inconsistency found, please correct the errors and check again.   * Save the Characteristic Relationship. And the created Characteristic Relationship can be used to generate valid combinations during the execution of planning functions. The procedure is the same for the creation of other types of Characteristic Relationships like Hierarchy, DSO, and Exit. Based on the type of the Characteristic Relationship, the relevant options are to be checked in the editor.   This is the way in which we can use the new Eclipse-based editor to create the characteristic relationships without the need to go back to the RSPLAN transaction in the backend BW/4HANA system. Feel free to post your questions or comments if any.   Thanks & Best Regards, Tharun. http://bit.ly/2EHnwvy #SAP #SAPCloud #AI