Author: admin

The SAP Activate: SAP Activate Methodology for SAP Ariba – Project Management Workstream is live and was released Tuesday, November 28th. We are excited to bring this new solution specific implementation roadmap to the SAP Roadmap Viewer for project teams, customers, and partners to use during their SAP deployments. The roadmap’s purpose is to guide teams through the SAP Ariba deployment Project Management Workstream which can be found in the Prepare through the Deploy Phases of the SAP Ariba Roadmap.

The SAP Activate Methodology innovative adoption framework is comprised of six phases taking the project team from Discover through Run in a detailed Agile project set up. The Project Management Workstream for the SAP Activate Methodology for SAP Ariba is only found in four of the six phases: Prepare, Explore, Realize, and Deploy.

The purpose of the Project Management Workstream is to formally recognize that a new project exists and to initiate the work on the project. During this time the project sponsor and project manager work to align stakeholders ­ such as clients, customers, and SAP management ­ around a project and its scope, provide updated information for planning, and obtain a commitment to proceed forward with the project.

As part of the initiation activities the project manager conducts a handover from pre-project phase, creates a project charter document, scope statement document and establishes the project governance that ensures proper management process for the project. This ensures alignment between the SAP System Integrator, the customer’s project team, the partner’s team, the company’s strategic direction, and the satisfaction of operational requirements.

Key topics for the SAP Activate: Implement and Configure SAP Ariba – Project Management Workstream roadmap include:

* Guided content for teams to use for a guided step-by-step approach for each of the four phases that the Product Management Workstream can be found
* A comprehensive description of deliverables and tasks by phase for SAP Ariba – Project Management Workstream
* Helpful accelerators associated with each one of the project deliverables

The breakdown of the Project Management Workstream deliverables per phase are as follows:

You can find past blog posts in the SAP Communities space with tag #sapactivate, as well as in the SAP Activate Methodology Jam group (request access here), a community of 21k members already actively engaged in SAP’s Implementation Roadmaps for Cloud, On Premise, and Hybrid environments.

If this topic series interests you, check out our e-book SAP S/4HANA Cloud: Implementation with SAP Activate which is available from SAP PRESS. Let us know your thoughts and feedback either in the comments or join our Jam Group. http://bit.ly/2D8fxWw #SAP #SAPCloud #AI

It is a very common requirement to define attribute for a dimension when using BPC as a planning solution. In BPC standard model, we just need to add a new field in web admin, and value maintenance is also very straightforward.

How can we do that for virtual master data in BPC optimized for S/4 HANA, which is based on BPC Embedded model?

As the name indicates, the master data of “virtual master data” is not physically saved in BW but S/4.  For example, master data of GL Account comes from SKA1 table. If the attribute you need is not defined in this table, then no related information could be provided from S/4 side.

We can’t change the structure of SKA1 to add some planning specific fields, so we need to create a new table to hold that attribute information. Below is the steps needed.

Firstly, create a new table for store the extra master data information. Make sure the key fields of host master data table is included in this new table. For example, if we’ll add attributes for GL Account, then following fields should be included:

Once the table is ready, next step is to set up a join between main master data with this attribute table. Generally left outer join should be used so even no content is maintained in attribute table, the master data table could be output.

Next step is to set all the attributes from attribute table to OUTPUT in HANA view.

Once the modelling at HANA side is done, we could start to define InfoObject in BW, just like the traditional way to add a new attribute for existing InfoObject.

Last step is to set up mapping between the InfoObject and field we expose in HANA view.

  http://bit.ly/2D8fha0 #SAP #SAPCloud #AI

ICYMI: Welcome to the second in a multi-part series of blog posts about creating Eclipse Vert.x applications with Infinispan. In the previous blog post, we have seen how to create a REST API. The purpose of this tutorial is to showcase how to create a PUSH API implemented with Vert.x and using Infinispan as a server.

All the code of this tutorial is available in this GitHub repository. The backend is a Java project using Maven, so all the needed dependencies can be found in the pom.xml. The front is a super simple react application. https://goo.gl/DUVVmY #DataIntegration #ML