Friday, September 29, 2017

SAP EM Knowledge Bites 8 - The history of SAP EM

In our last blog we highlighted the issues that SAP EM resolves and what benefits it provides. Now lets talk about how we got to SAP EM release 9.2…
SAP EM began it’s journey way back in 2000 but the 1st official release was made in 2004 and that’s where we will pick up the story…

Wednesday, September 27, 2017

SAP EM Knowledge Bites 7 - The benefits of SAP EM (benefits)

In our previous blog we listed out the issues that face the Supply Chain. In this blog we’ll go through how SAP EM can be leveraged to address these issues.
How does SAP EM address the challenges mentioned in part 1 of the blog series?
Visibility: SAP EM provides maximum visibility across the supply chain network.  This visibility allows for the detection of deviations in the demand and supply of goods and services.

Tuesday, September 26, 2017

SAP Change Control Practices and Digital Transformation

According to Gartner’s 2017 CEO survey, the number 2 strategic priority for CEO’s is technology related business change. Not surprising when 47% the same group of CEO's indicated they are experiencing pressure from their Boards to make progress in digital. Digital transformation is the order of the day.

Monday, September 25, 2017

SAP EM Knowledge Bites 6 - The benefits of SAP EM (issues)

In our previous blog we described the differences between events and messages and now it’s time to take our new-found EM knowledge and relate it back to the advantages that SAP EM can provide.
The benefits of SAP EM are dependent on the specific challenges an organization faces. This blog describes common challenges that we face today and the 2nd part of the blog will show how SAP EM can be leveraged to address this issues.

Friday, September 22, 2017

SAP EM knowledge Bites 5 - Events vs. Messages

In our last blog we discussed the different types of events that SAP EM deals with. Now it’s time to delve a little deeper and look in to event messages as they relate to events. SAP EM makes the distinction between events and event messages. The difference is subtle yet very significant and compelling.
An event is the recording of “something that occurs in a certain place during a particular interval of time”.   An example of an event would be a post goods issue (PGI) occurring in Warehouse A at 3:00 PM (See No. 4 in Figure 1).  A plan for the event is stored in SAP EM, and the event is measured against this plan.  ‘The Plan’ states: ‘the PGI event should happen at Warehouse A between 2:00 PM and 4:00 PM’ (See No. 1 in Figure 1).  In this example, the event is considered a regular event.

Thursday, September 21, 2017

Webinar: Cybersecurity: What You Need to Know to Stay Safe in the Cloud

Wednesday, October 4, 2017 | 8am PDT / 11am EDT / 4pm BST / 5pm CEST
Strategic business demands are compelling companies to embrace the cloud and business networks. As businesses move to a cloud environment, information security becomes increasingly central to their overall risk management initiatives.

Please join this webinar to learn about SAP Ariba’s holistic, multidimensional approach to support best practices and security controls to help protect the integrity, confidentiality, and availability of your information. We’ll share our security principles, including:
  • Guarding your data against external and internal risks
  • High availability, monitoring, and business continuity
  • Effective risk management
Speaker: Lakshmi Hanspal, Chief Security Officer, SAP Ariba

Wednesday, September 20, 2017

SAP EM Knowledge Bites 4 - Describing SAP EM Events

In our previous blog we discussed the differences between SAP EM and Document Flow. Now it’s time to start to dive in to the details of SAP Event Management and whereas could we start, other than to describe an event?

Events can be divided into two different types (actual vs. planned), which can then be grouped into four categories. Actual Event vs. Planned Event

Monday, September 18, 2017

SAP EM Tip: Sample code for coding your own rule set activities

Here is the code snippets but the full document with all the table details is located for download here.

SAP EM Knowledge Bites 3 - SAP EM as compared to Document Flow

In our previous blog we described where SAP EM fitted in to the SAP solution stack. In this blog we discuss the differences between document flow and SAP EM. We often get asked what the difference is or we hear the following “SAP EM is just glorified document flow”…
SAP EM is often utilized in conjunction with SAP Document Flow.  Document flow shows the transactions related to the business document, as they are being created by the SAP system.  A typical document flow for an order-to-cash scenario will progress as follows: Sales Order -> Delivery -> PGI -> Billing Document -> Accounting Document.  Although SAP EM can easily provide the same view to the applicable business process using document flow, it allows for a few subtler, yet powerful differences.

Saturday, September 16, 2017

SAP EM Knowledge Bites 2 - SAP EM as part of the Extended Supply Chain

In our first blog, We spelled out what SAP Event Management covers, what it is and what it is not. (Read here) It’s now time to look at SAP EM and see where it fits in to the bigger picture.

Where does SAP EM fit in to SAP’s overall solution landscape

Over the years SAP has moved the SAP EM solution across many vertical and horizontal solutions.  Originally written as a component of the Railcar Management System, SAP EM was called Supply Chain Event Management (SCEM).  SCEM was adapted to a generic solution and became an add-on component that other solutions could use.  Also known as SAP’s Track and Trace solution, it was a part of the “Supply Chain Integrity” stack.

Thursday, September 14, 2017

SAP EM TIP: Post-Processing Activity in Rule Set

With SAP EM 9.2 SP06 a new activity type “Post Processing Activity” has been introduced. It can be used to execute certain activities once instead of multiple times when processing event messages.

Only one post processing activity can be assigned to each rule set and it will be executed exactly once after rule set processing is done. This allows the EM developer to trigger follow-up activities in a mass enabled way instead of triggering the single action possibly multiple times during rule set processing. To make this work rule set activities which are executed during the rule set processing have to collect all data that is necessary for the post processing activity instead of triggering the actions itself. Check in this SAP document to see how to do it: Post Processing Activity to boost performance of EM – TM integration

Wednesday, September 13, 2017

SAP Further Expands SAP® Vehicles Network with New Connected Fueling and Payment Options

SAP SE today announced new agreements with Deutsche Tamoil and Q1 that will add hundreds of new fueling locations across Germany to the SAP® Vehicles Network solution. Other agreements with PACE and Tantalum will add new automated payment options for fueling and parking. SAP also showcased new integration scenarios with TripIt® from Concur, the world's highest-rated travel-organizing app, and automated payment options with Parken+ and Apple Pay to create seamless, connected travel experiences. The announcements were made at IAA New Mobility World,  taking place Sept. 14–17 in Frankfurt, Germany, and Mobile World Congress Americas, taking place Sept. 12–14 in San Francisco, California. - Read full release at NewsWire

Monday, September 11, 2017

SAP Process Observer - What is it and how does it relate to other similar tools like SAP EM?

Process Observer is a component of SAP’s Business Suite foundation layer. Broadly speaking it can be used to monitor SAP Business Suite processes like OTC (Order to cash) and PTP (Procure to pay).

Wednesday, September 6, 2017

Check out SAP Blockchain community

Check out the SAP Blockchain posts at the SAP Blockchain Google + community.

ABAP Example: Creating an event in SAP EM using a BAPI call

You can use SAP Event Management to manage the statuses of your business processes. To communicate with EM you need to send it events. There are several ways of sending events to EM including via IDoc, BAPI call, RFC call and XML call. 
The syntax for sending an event using the BAPI /SAPTRX/BAPI_EH_ADDEVENTMSG_02 is described in detail below. In addition to showing you how to call the BAPI it also shows how to call the BAPI using a a qRFC leveraging a specific outbound queue name.

Here is the extract of ABAP code dealing with calling /SAPTRX/BAPI_EH_ADDEVENTMSG_02:

Tuesday, September 5, 2017

Developing your own Fiori apps for SAP Event Management

SAP Web IDE version 1.13 includes the SAP Event Management plugin which enables developers to generate their own transactional SAP Fiori apps for SAP Event Management.
Read the detailed developer guide SAP Web IDE plugin for SAP Event Management.


  • SAP Event Management 9.2 SP 4 and above
  • SAP Fiori for Event Management 1.0 or above
  • SAP Web IDE 1.13 or above

Monday, September 4, 2017

A comprehensive list of questions to ask when designing a SAP Event Management solution

If you are contemplating implementing SAP Event Management, you will need to be prepared to answer a series of questions to be able to establish a design that caters to your needs. These list of questions should help guide your JAD whiteboard session. No substitution from standing up there and guiding the discussion with questions that need answering -> that ultimately lead to a solid, scalable and efficient solution design.
The following list of questions is a comprehensive list of what needs to be asked…

Saturday, September 2, 2017

SAP point-of-sale systems were totally hackable with $25 kit

Researchers able to hijack server and steal card details

Point-of-Sale systems from SAP had a vulnerability that allowed them to be hacked using a $25 Raspberry Pi or similar device, according to research unveiled at the Hack in the Box conference in Singapore last week.

Critical vulnerabilities in SAP's POS – since resolved – created a means for hackers not only to steal customers' card data but to gain unfettered control over the server, enabling them to change prices of goods with the help of a simple device, according to ERPScan.

SAP developed a patch after being alerted to the problem by ERPScan in April, allowing the enterprise app security specialists to go public with their discovery last week.

The root cause of the problem was that pre-patch SAP POS Xpress Server systems failed to perform any authentication checks for critical functionality that requires user identity. As a result, administrative and other privileged functions could be accessed without any authentication.
Read the full article at The Register.