1 2 3 4 Previous Next

SAP Event Management

51 Posts

The latest support package SP05 has been released for SAP EM 9.2 on 20th of January 2016. With this support package SAP EM 9.2 is released for integration with SAP S/4 HANA, on-premise edition - more information is provided by note 2238445 .


Additionally the support package contains




Cheers, Daniel

The latest support package SP04 has been released for SAP EM 9.2 on 2nd of October 2015. The support package contains




Cheers, Daniel

In this blog I will explain how to build the Generic EM WebUI profiles to hide the profile items using BRF+.

BRF+ Scenarios for EM Web interface transactions:

BRF+ custom controls are useful when the single EHT and AOT used in multiple business contracts.

Using BRF+ decision table EM webUI  selection, display and event message  profile items can be hidden dynamically. With this new design multiple EM WebUI profile generation is not required. Accordingly the unused configured fields can be removed dynamically, when it is exposed to various external partners and used by various business entities.

How to build BRF+ application for EM WebUI interface transactions?

Why BRF+ , Why not EM filter profile ?

Standard EM filter profile determines the event handler components that are to be displayed to the user, but not to remove the empty configured fields (filtered) being displayed in EM webUI.

Designing Selection profile control using BRF+

Step1: Design the generic DDIC structure using selection profile and security role

            Structure components: User Profile Identifier

                                                  Selection Profile

                                                  Configured Field

                                                   Role Name

           Output : result indicator

Step 2: Design the BRF+ data object using the structure defined in step1 .

Step3: Build BRFplus selection profile decision table using the objects defined in step 1

BRF Decision table elements = selection profile DDIC structure

Result object = Yes/No field indicator

Step 4: Create the BRF plus function object with top expression as decision table and output as  result indicator.

Step5: Create the decision table entries as shown below


Create entries  with user profile, selection profile, configured field , user role and maintain the relevancy indicator.

Step 6: Create enhancement in FM /SAPTRX/UC_GET_USERPROFILE and apply the below steps to validate the selection profile items when it is triggered by user WebUI  selection.

  1. Get BRF plus function
  2. Set the BRF+ function context, then pass the input variables such as user profile, selection profile, configured field and user role.
  3. Process the BRF+ function.
  4. Retrieve the BRFplus function result
  5. Delete the entries from et_selection_profile_items when the BRF result indicator is true.


Designing display profile control using BRF+

Execute all the steps (mentioned above) for selection profile; and replace the  selection profile with Display profile (/SAPTRX/UCDPID).

Decision table view


Designing Event Reporting Message profile control using BRF+

Similarly follow the steps as of selection profile, replace the selection profile with event message Profile (/SAPTRX/UCEVTRID) and configured field with event code (/SAPTRX/EVENT_CODE).

Decision table view  



Alternatively above mentioned BRF+ solution can also be achieved using custom SPRO configuration enabled with user role mapping. DDIC DB view is required between AGR_USERS and newly created custom table. This view can be used in FM /SAPTRX/UC_GET_USERPROFILE enhancement by applying the same logic.

Note: DDBV (Dynamic Database View) can be used in BRFplus, if EM is running on HANA environment.

Using  BRF+ decision table TM AOT extractor functions can also be generic in future along with the addition of few configuration elements and  key/org data maintained  in the BRF+ application. 


How to use BRF+ in TM/EM integration and event propagation

BRF+ decision tables can be used in TM/ECC EM data extractors using document type/KDS with single AOT/EHT integration as follows:

  • Control/system Parameter extraction
  • Expected Event generation 
  • Tracking Id generation
  • Custom event propagation and event copy  

SAP provides the ability to create alerts (emails) through the Alert Framework. Other modules, like SAP Event Management, integrate with the Alert Framework in order to send notifications on exceptions uncovered in the process.


The text that is maintained in the Alert Category definition (tx: ALRTCATDEF) is either static or mapped in from the called system (e.g. SAP EM).




At times we need to have the ability to manipulate the resulting mapped text. To do this you can use BAdI ALERT_MODIFY_TEXT. Note that the BAdI requires filter values relating to your Alert Category Class. See values for my scenario below.


The method to implement is called MODIFY_LONG_TEXT


Scenario: We need to replace the uppercaps with Lowercaps for TORONTO...

Sample code:

DATA: lv_line TYPE soli.
*IP_LANGU         TYPE SYLANGU              Language
*IO_ALERT         TYPE REF TO CL_ALERT      Alert
*IP_APPL_GUID     TYPE GUID_32              Application GUID
LOOP AT ct_long_text INTO lv_line.

IF lv_line CS 'TORONTO'.
REPLACE 'TORONTO' IN lv_line WITH 'Toronto'.
MODIFY ct_long_text FROM lv_line INDEX sy-tabix.


And the result is:


We recently encountered a situation that after an install of SAP EM on an SNC server the SAP Event Management node was missing in the IMG structure (t-code SPRO). A work-around using transaction SIMGH is doable but the permanent fix is shown below...

SAP provided OSS note 2197261 (SPRO Use another SAP Reference IMG) to address this issue.

  1. Create, activate and execute report ZSLA_SHOW_REFERENCE_IMGS
  2. Follow the instructions mentioned in the report
  3. Copy the content of the clipboard into a text file
  4. Start transaction SCUSSEQUENCE
  5. Choose Hierarchy type SAP Reference IMG
  6. Press icon Change (F6)
  7. Enter an ID, which is different to SAP_----- for example Z_IMG
  8. Enter Switch to another IMG in field Description
  9. Enter the 32 digit GUID which came from the field TREE_ID into field Structure GUID (Copied to clipboard in report ZSLA_SHOW_REFERENCE_IMGS)
  10. Press icon Save (Ctrl+S)
  11. Save the changes in package BECU
*& Shows different SAP Reference IMG and delivers the
*& corresponding Structure GUID

DATA rc type i.

WRITE: 'Double-click on the TREE_ID to open the different SAP Reference IMG´s' COLOR 2.
WRITE: 'If you have found the correct SAP Reference IMG, leave the reference ' COLOR 2.
WRITE: 'IMG with Back (F3), and leave the report with Back (F3)' COLOR 2.
WRITE: 'Now you can find the correct reference IMG TREE_ID in your clipboard' COLOR 2.
WRITE: /, 6(20) 'ID' COLOR 5,
                    26(20) 'REPLACES' COLOR 5,
                    46(32) 'TREE_ID' COLOR 5.

* Dataloop at SCUS_HIER_TABLE.
                  26(20) SCUS_HIER_TABLE-REPLACES COLOR 3,
                    46(32) SCUS_HIER_TABLE-TREE_ID COLOR 2.

               LANGUAGE = SY-LANGU.

* Paste SCUS_HIER_TABLE_CHOOSEN to clipboard
       RC = rc
       CNTL_ERROR = 1
       ERROR_NO_GUI = 2
       others = 4.
    IF SY-SUBRC <> 0.

SAP Process Observer for Built-In Processes (POB) allows organizations to monitor and optimize core processes based on SAP Business Suite’s built-in business object events. It's been around quite a while - Since 2011, I believe. The functionality it provides is somewhat close to SAP Event Management but there are major differences in functionality and also in the scope of the process that each covers. Comment on the blog if you want more details on the differences. Below is a set of documents that are available on SCN that will help guide you through understanding what POB is and how to put it in...

I created a poll in 2014 to see what versions of SAP EM were the most popular - See poll here.


I thought I would just call out the results and let those who are interested see what is going on.

sap em versions used.JPG


Poll highlights:

  • 124 total votes
  • SAP EM 7.X has over 50% of the install base
  • SAP EM 9.1 and 9.2 have subsequently been released and also now have good adoption
  • There are still a more than insignificant number running on 4.x or less! Not quite sure why because the UI in releases 7 and 9 are substantially better.


After this posting I'll edit the Poll to include 9.1 and 9.2 so we can start capturing those stats. Leave a comment if you have further suggestions on useful data to collate...

As this question comes up now more often here a short overview when EM is released on HANA:


EM 9.0 is available for HANA with SP03 on Netweaver 7.40 stack.


You find this information in note:

1826531 - Add-on compatibility of SAP NetWeaver 7.4 - ABAP


EM 9.2 is released from the beginning for HANA.

Alongside with SAP Event Management 9.2 the first Fiori app 'Freight Order Visibility' has been released in 2014. This app leverages the EM OData service, which has been introduced with SAP EM 9.2. The app has been designed to be used for the freight order tracking scenario based on event handler type ODT40_TO. While the EM OData service already highly supports extensibility, the 'Freight Order Visibility' app is bound to the supported ODT40_TO scenario and with only very limited possibilities for enhancements. Therefore it has been not a simple task to create Fiori apps for custom tracking scenarios. In fact, such apps had to be developed from scratch - until now. This gap has now been closed with the release of the SAP Web IDE 1.13.

SAP Web IDE 1.13 includes a new plug-in for SAP Event Management 9.2. This leverages the EM OData service as well and allows you to generate a Fiori app by using the template 'Transactional App for SAP Event Management'. Please check out the details in the guide on 'How to Generate your own Transactional Fiori Apps'.


If you have questions or feedback regarding this topic, let us know!

SAP Web IDE version 1.13 will include 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

Summary of steps needed

Step 1: Configure the Back-end System

  • 1. Activate the EM OData Service
  • 2. Configure the EM OData Service
  • 3. Test the Configuration of the EM OData Service

Step 2: Generate a New Fiori App

Step 3: Modify the Generated Fiori App to Enable Non - Standard Functionality (Optional)

  • 1. Change the Attributes in the Detail area
  • 2. Logic to sync two Timezone Combo boxes

Step 4: Set Up the ABAP Front - End Server

  • 1. The ABAP Front - End Server
  • 2. Define Semantic Objects
  • 3. Customize Your SAP Fiori Launchpad

Read the detailed developer guide on SAP Web IDE plugin for SAP Event Management.

The healthcare, life sciences and pharmaceutical sectors face a lot of challenges in their manufacturing, operations and supply chain management processes. The US Food and Drugs Administration insist that companies implement track and trace systems to improve the security of prescription drugs to customers. Counterfeit drugs are major problem and accounted for $75 billion in revenue in 2010 according to the National Association of Boards of Pharmacy.  Implementing electronic track and trace for prescription drugs with serialization will reduce the counterfeit products over a period of time.


Serialization or Unique identification helps us to identify who manufactured the product, which wholesaler has sold to retailers or hospitals and to which customer it has been prescribed.  The implementation of serialization and track and trace provides the ability to track and trace the lifecycle of the drugs in the system end-to-end.  The US Food and Drugs Administration sets some standards to ensure safe manufacturing and distribution of prescription drugs. The US Food and Drug Administration requires an e-pedigree electronic document which documents the full history of particular or entire batches that are manufactured and then prescribed to patients.  The e-pedigree helps to prevent the prescription drug from being misbranded, sold after expiry, counterfeited, diverted, stolen and/or contaminated. All manufacturers, wholesalers, repackagers, OEM’s and pharmacies must comply with the e-pedigree requirements and submit prescription drug information, source and destination, how and when it was prescribed to a customer, to the e-pedigree system.


How does a track and trace system improve security?


A track and trace system improves security by:

  • Knowing the life cycle of the prescription drug, from where it is manufactured, who is repackaging it, who is distributing, when it is prescribed and when it is sold
  • Meeting accurate regulatory and compliance requirement questions such as “What, Where, When and Who”
  • Locating prescription drug batches and precisely where they are distributed
  • Enabling the option to recall a particular batch or entire batches which are reported as having a product/batch failure or having not met standards
  • Identify if the prescribed drug is counterfeit, stolen, contaminated etc.
  • Know about the multi-container packaging item level details


How does track and trace work?


Track and trace works in the following ways:


  1. Generate and apply unique serialization number for manufactured drugs.
  2. Capture unique serialization number and store in centralized database (distributed or non-distributed).
  3. Update serialization data in EPCIS centralized database.
  4. Wholesalers, Repackagers and Pharmacies can have the ability to validate the serialization when they perform transactions.
  5. Each time a transaction for serialized drugs is carried out, the transaction drug history is updated in the e-pedigree system.


What is EPCIS (Electronic Product Code Information Services?

EPCIS is a GS1 standard that enables companies to capture, update and share information about the products end-to-end in the supply chain life cycle.

Serialization and Track and Trace 1.jpg

The following links provide details of different manufacturers of track and trace and serialization software


Why implement SAP track and trace solution?

The following are strong reasons for implementing the SAP track and trace solution:


  • Mapped to EPC Global compliance and standards
  • Captures uniquely identified objects EPC, IUID, etc.
  • Seamless integration with other SAP and non-SAP systems
  • Track and Trace end-to-end lifecycle of supply chain management
  • Enables prescribed drugs tracking and authentication at serialized level, item level, batch level and GTIN level
  • Track and trace carton box, pallet and container level
  • Enables tracking of historical and multi-level hierarchy data of prescribed drugs
  • Identify batch failures, recall and notify relevant drug stock holders to return back to wholesalers or manufactures
  • Seamless integration with SAP Event Management to monitor, and provide alert and notification services


You can watch as Youtube video on following link Why Serialization and Track & Trace are important in today’s Healthcare, Lifesciences, and Pharmaceutical sectors?


Chat/connect with me to know how to implement Serialization and Track & Trace for your clients effectively and efficiently.

Evolution of Quality Management


Today we will discuss quality management. This is not a new evolution; it has existed since 1924, when Walter A Stewart created a structured statistical method for production quality control and his methods became the foundation of quality control today. Later, Dr. W. Edwards-Deming applied new statistical methods using Stewart’s ideas that he mastered and finalized and which became well known to the quality management world.


The single word: “quality” has changed the economy of countries over periods of time. Post World War II, the Japanese economy was in very bad shape. Their determination towards achieving “Quality” helped to improve their reputation and the economy over a few decades. Dr. W. Edwards-Deming taught the Japanese fourteen principles. These principles are now the foundation of Japanese success in quality. If you ask anyone in the world, they will make the stereotype that “Japan” means “Quality”. Due to the high level of quality, Japanese products take a big piece of revenue from around the world, especially in the car market.

My personal experience with Japanese - I had the opportunity to work with a Japanese team for one of our esteemed clients on SAP Quality Management implementation project. I was amazed about their knowledge and 100% expectation on the quality side of system details, documentation, business processes, process flows, testing and their hierarchical way of working.

Quality Standards


Today, quality becomes an inevitable requirement for all products, so a quality standard has become an integral part of all companies. There are many quality standards like ISO, Six Sigma, Kaizen, QFD, TQM, Toyota Production system etc. that exist to help companies maintain quality compliance. People today are more concerned about health and safety issues, and the quality standard companies help to protect the people, processes and technology. Using and consuming poor quality products results in deep pocket experiences or sometimes worse, can result in fatalities.


Enterprise Resource Planning System


Quality management is an integral part of one of the modules in enterprise resource planning (ERP) systems. If the client is in the business of manufacturing, then there is no other option but to implement a quality management module. The ERP system provides quality planning, quality assurance, quality control and quality improvement in their manufacturing or business processes. Some companies use a quality management module to capture exceptions in their processes such as incorrect order submission, incorrect claims, missing shipments, downgraded products, missing SLA, monitoring team notifications etc. So quality management can be considered a versatile system and it can be adapted and used in many areas.


SAP Quality Management


SAP ERP delivers its own quality management module to integrate and run QM functions across product life cycle and supply chain. Quality management has 20 elements integrated into the SAP ERP system adhering to the ISO 9000 quality standard, so you can use QM alone or conjunction with following modules SD, MM, PM, PP, PS, CO and HR.


The main scope of Quality Management in SAP ERP:

  • Quality Engineering
  • Quality Assurance and Control
  • Quality Improvement
  • Audit Management

Quality Management Components in SAP ERP


  • Quality Planning
  • Quality Inspection
  • Quality Control
  • Quality Certificates
  • Quality Notifications

Though it has many functions and required components, the real time visibility and proactive approach model are not implemented yet in SAP Quality Management.

Real time visibility and proactive approach using SAP Event Management for SAP Quality Management

Using SAP EM for SAP QM, it is possible to implement visibility and a proactive approach such as the following examples:


  • Trigger alert via Email, SMS or Fax, when Inspection lot is created
  • Trigger alert via Email, SMS or Fax, when quality notification is created
  • Trigger alert via Email, SMS or Fax for partial /full usage decision is made
  • Send an automatic alert to inspection team, when product samples are arrived at quality labs
  • Send an automatic alert to the 3PL warehouse team to move stock into restricted use, when stock is moved into blocked stock
  • Report to the relevant team if the usage decision is not taking place by specified time
  • Alert the relevant team when specific product groups have been made auto usage decision
  • Alert the quality team when high end products are sitting more days in quality/blocked stocks
  • Trigger a workflow, when an inspection lot created for specific customer material samples greater than 10%
  • Automatically move a particular batch or all the batches, when a usage decision fails
  • Trigger an email to the quality inspection team, when a specific inspection type is created
  • Cancel all purchase orders of a vendor, when a customer returns a product more times than a threshold and alert the purchasing and sales team
  • Notify relevant partners to approve or reject when quality notifications are overdue
  • Alert quality labs when certain DEFECTS are found in products
  • Report failures accurately due to customers mishandling, quality of vendors, internal production problems, particular ingredients or products causing an issue and perform analytical reporting through SAP BI.


SAP Event Management delivers standard business process types for SAP Quality Management


The following standard business process types are delivered through SAP EM for SAP QM:


  • EPL_INSPLOT – Quality Inspection Lot
  • EPL_NOTIF – Quality Notification


Chat/connect with me how to implement SAP Event Management on SAP Quality Management for exceptions, continuous improvement, submit COA documents, sample failures, recall management, track and trace in shop floor, GS1 GLN location identification shop floor/quality inspection area, track and trace serialized products (hierarchy and using GTIN), track and trace lot/batch (using GS1 GTIN), track and trace multi-packing (mixed packing, overpacking, partial packing (using GS1 SSCC), inspection characteristic routing, engineering change etc.

Welcome. Recently, I have come across a couple of queries posted on forums and have been involved in various discussions about Container Tracking. I was fortunate enough to have the opportunity to work with a great team on implementing a new SAP Event Management “Container Shipment Tracking” system end-to-end during a particular project engagement. We normally read whitepapers and have discussions about ships, trucks and rail tracking scenarios, however the tracking of cargo containers seems to be a different challenge altogether. If you ask a shipping container company or global logistics providers or 4PL or 3PL, they advise that: “Container tracking is complex and inevitable in today’s global supply chain intermodal scenario”. Before we get into much detail on this topic, I would like to give you some insight on “How containerisation has emerged and how in today’s world, cargo movements heavily depend on containerization?”


Container Evolution


In the earlier days of shipping, wooden boxes, wooden drums, barrels, sacks and so on were used to transport cargo. Transportation of goods was a major challenge due to the non-standard requirements for specific handling of various pieces of equipment, increased loading and unloading time, complex transportation etc. In 1955, Malcom Mclean realised the major challenges in handling cargo from one place to another, and took this as an opportunity to develop a new type of cargo box. He started to work with engineer Keith Tantlinger on a solution to handle the cargo more efficiently and securely. Keith came up with an idea to move cargo in a box-type container, and Malcom then developed this idea further and later his design became globally accepted as the standardized container we are familiar with today. Although we see many different versions and models of these containers, the two geniuses were responsible for ensuring that cargo could be moved safely and securely across the world in box-type containers.


Containerization changed Transportation and Port facilities


Nowadays, you can see that ports, rails, trucks and ships have been designed largely according to the specification of cargo box-type containers. Cargo ships are primarily suited to stacking containers and offer facilities to load and unload containers. Railway cars cater for single and double container stacking. Container trucks are designed to hold single and double containers, and ports usually have their own container terminal facility with modern handling equipment to load and unload the containers.  Most ports have built-in container terminal facilities to handle cargo containers enabling the loading or offloading to or from ships, trains and trucks, efficiently and effectively.


"Did you know that one double stack container railcar could replace 300 trucks?"


The port of Shanghai is in the first place in the world to handle 33.62 million TEUs (Twenty-foot equivalent units) of cargo and the port of Singapore sits in second place, handling 32.63 million TEUs of cargo in 2013 as per Forbes Top 10 World Container Ports. Singapore is like a hub and the majority of cargos handled in this port are transhipment containers that are further stacked and then shipped to other Asian and western countries. The handling and tracking of these containers presents a major challenge to the port-based container terminal facilities. There are separate sets of processes executed in the major ports across the world to avoid inconsistencies during loading and unloading onto ships, trucks and railways.


"Did you know that every year approximately 500 million containers move across the globe?"


The BBC Box Project


Under normal circumstances, you would never see the same container twice when loading the goods for a shipment, and it’s highly feasible to assume that we may never see the same container in our lifetime. Let’s consider how a container moves around the world. Our immediate thought goes to the “BBC Box Project” – started because someone had a similar thought to us and created this project to track and trace a container. In 2008, the BBC started this project with the plan to track a container for more than a year. This intermodal container tracking project lasted crossed 50000 miles, where the box tracking started in Southampton, UK and finally ended at the same place having been shipped around the world.  An interesting factor here is that the same driver Lee Harfield loaded and unloaded the container in the port of Southampton. You can view the entire route map that the BBC box container traveled.


"Did you know that a container might travel more than 12 countries in a year?"


Container Tracking Challenges


Tracking containers presents a huge challenge for container shipping companies, logistic providers, ports, trucks and warehouses. The following items can be considered standard questions, challenges and issues that might be presented when trying to track the container.


  • Is the container a Full Container Load (FCL) or Less Container Load (LCL)?
  • Is the container being used correctly according to the contents?
  • Is the container requested to be dry or refrigerated?
  • Has the wrong container been sent to the warehouse?
  • Has an empty container been requested for repositioning following a full container being shipped?
  • Is a container sitting in the port or warehouse more than the requested or accepted date?
  • Is a reefer container (refrigerated - temperature controlled) requiring any special attention especially relating to overall temperature?
  • Are containers lost in sea due to natural causes or have they been stolen?
  • Have any containers loaded onto a vessel met with an accident?
  • Has the container loaded onto a truck met with an accident or been affected natural causes?
  • Has the container seal been broken during transit or transhipments?
  • Is the container Gate-In early or has it arrived late at port?
  • Is container still at the port without having been loaded onto a booked vessel?
  • Does the container contain any hazardous materials?
  • Does the container meet the standard of Environmental Protection policy – for example does it require fumigation?
  • Has the container been checked in and/or checked out on the requested date by the clients?
  • Have unloaded containers been requested for pickup or reloaded onto other consignments?
  • Is there a container shortage in a specific country, port, place, warehouse etc.?
  • Has a loaned container been returned or extended on agreed time?
  • Has container damage notification been sent to the logistic providers or container shipping company?
  • Have any port authorities requested container examining or scanning?
  • Is the container missing the bill of lading?
  • And so on…


All of the above challenges and scenarios can be addressed by the SAP Event Management Track and Trace solution.


How SAP Event Management can help with container tracking?


The following are benefits of how SAP Event Management can help with container tracking:


  • The SAP Event Management track and trace solution enables tracking of returnable items end to end
  • The ability to track and trace container number, container booking reference (CBR), seal number, bill of lading, carrier name, order number etc.
  • Provides a single portal view for all reported, expected, unreported, overdue and unexpected container tracking events
  • The ability to search and track a vessel, voyage, latest location, last reported container event etc.
  • Trigger an alert to the relevant team when a container is lost or damaged
  • Track the container route position with SAP Visual Business Geo-Map Integration
  • Publish dashboard granular details or a detailed view about containers through SAP Business Intelligence
  • Report events from Non-SAP systems where carriers, freight forwarders or shippers use different systems
  • Seamless container ocean booking events, including loading, vessel departure, vessel arrival, unloading and container cancellation
  • RFID-enable the container tracking process
  • Manage the loading and unloading of returnable transport items
  • Track and trace a container ID is one of the parameters in the delivery process in SAP Event Management
  • Track and trace a container ID as a separate tracking id in SAP Event Management
  • Track and trace containers as a separate tracking scenario in SAP Event Management
  • Container ID and SCAC code validation on reported events
  • Customer-specific or port-specific container seal number validation on reported events
  • Temperature controlled containers can have custom validation and trigger alerts to relevant teams in the event of unexpected events
  • Vessel and voyage mismatch validation on reported events for loaded containers and trigger an alert to the relevant team
  • Track and trace Less Container Load (LCL) and scenarios such as consolidation of orders

I have written an article on ERPGenie.COM on this topic - Read the full article here. Here is a short excerpt from the article:


"Most organizations deal with the shipment of goods in to and out of their premises. With the increasing demand for a better customer experience it is a challenge to provide a high level of customer service when parts of your supply chain fall somewhat out of your “sphere of influence”. Sure, through contractual obligations, you can try and force your suppliers and carriers to behave in a certain way but as the old saying goes “stuff happens!”. If the supply chain breaks down outside of your 4 walls, are you aware of it? Do you have enough time between when you find out about the issue and the time needed to correct it? Do these issues in the supply chain cause disruption and potentially lead to lost customers and sales? The key to remedying this issue was discussed back in the 1990’s and was termed Supply Chain Event Management – Give me the ability to monitor the events occurring THROUGHOUT my supply chain as and when they occur – Let me measure these events against what I had expected to occur and if it differs in any way let me know so that I can take proactive measures to correct it.SAP was a part of the “think tank” that came up with the term “Supply Chain Event Management” and created the product SAP Event Management to provide us with this functionality. It went in to General Availability in 2004 so has been around rather a long time… In this article I want to describe how SAP Event Management forms the back-bone of your Track and Trace requirements and specifically focus on the outbound logistics scenario."


" - TRACK refers to providing me the status of my goods that I am tracking at this point in time – It allows me to answers such questions as: Who has my goods now? Where are my goods? What status are my goods in? When will my goods arrive? Is the person currently in possession of my goods allowed to be in possession of them?

- TRACE refers to providing me with the historical view of my goods in terms of where they have been, who has handled them, what statuses they have gone through and so forth – It allows me to answer such questions as: Where were my goods manufactured? Who has handled these products to date? Have my goods ever gone in to an “exception” status? Were are the people that worked with my goods authorized and allowed to do so? "


Read the full article here.

Allow me to introduce you to air freight and how SAP Event Management can help in the scenario where air freight is used as a shipping method.


Air freight returns large revenues and is second only to water-based shipping. In 2010, net revenues of 67 billion US dollars were expected in air cargo and the airlines themselves were expected to carry 51.6 million tonnes of cargo in 2013. Cargo is an important revenue source for many airline companies. Cargo amounts to 13% of the total air traffic revenue globally. Some passenger airlines carry cargo in the lower hold below the passenger deck, and others are dedicated cargo airlines. In many intermodal and multimodal transportation scenarios, the goods are shipped in trucks, then in ships and then in trucks again to reach the destination country. Some niche products, such as those with a short shelf life, high value products, urgent deliveries etc. are shipped via air cargo to reach their destination within a day or two.


The routes flown are typically handled by single or multiple airlines to reach the destination airport. After customs clearance, the goods are transported by truck for delivery to the customer. Air cargo presents many challenges, and includes multiple stages and hubs, different loading requirements, different customs requirements in international airports, multiple handling costs, customs duties and the arranging of third party transportation after customs clearance in the destination country.



What is Unit Load Devices (ULD)?


Goods in air cargo are loaded and carried on various pallets and in containers known as Unit Load Devices (ULD). These Unit Load Devices are specially designed for air cargo to enable safe and simple methods to store, load, transport, and unload the goods. ULD specifications feature different sizes based on the attributes and characteristics of goods that they will hold. If goods are sent weighing 100 kg, the ULD does not only hold the goods of one customer, but also carries other goods. Until the air cargo company updated the data on their website, goods tracking does not show details such as goods stuck in customs clearance, lying in the first or a hub terminal, reached the destination airport and so on. Therefore there is a reliance on both the air cargo company, and accurate data.



Baggage Reclaim scenario


You may have unfortunately experienced the familiar scenario of your personal baggage going missing. When you contact the airlines, they would have told you that they are trying to track the baggage and hopefully the result of their tracking is that you receive the bag after 5 or10 or 20 days. But sometimes it is possible that you never receive the baggage. In this case, the airlines say that they are unable to trace your baggage and you receive financial recompense for the lost baggage. These scenarios happen quite often with airline cargo due to the lack of track and trace availability of personal baggage or goods. The sender of goods has to rely on purely on the freight forwarder or a third party update with a tracking number or airway bill number.



Stages/Milestones in Air Cargo


The below are the stages through which goods pass through in air cargo.


  1. Air carrier booking request
  2. Air carrier booking confirmation or rejection
  3. Air carrier booking cancellation
  4. Air carrier booking reschedule request
  5. Collection from shipper
  6. Receipt at forwarding warehouse
  7. Print air waybill (AWB)
  8. Air cargo gate-In (Airline warehouse)
  9. Air cargo custom declaration submitted
  10. Air cargo custom declaration accepted
  11. Air cargo custom declaration rejected or resubmitted
  12. Air cargo shipped on board
  13. Air cargo departed departure airport
  14. Arrival at the 1st airport
  15. Departure from 1st airport
  16. Arrival at destination airport
  17. Arrival at destination airline warehouse
  18. Notification to freight forwarder
  19. Freight forwarder submit customs document
  20. Dispatch to freight forwarder or 3rd party warehouse
  21. Deliver to customer (Proof of delivery, or POD)


Wow! These many events occur in air cargo when we send goods to a customer. If anything unexpected happens in-between these events, the customer may never know what has happened to a particular air waybill until they request the information from freight forwarder or 3rd party logistics. When proactive shipment monitoring has not been enabled it can lead to deadlines being missed, costly fines and customer dissatisfaction due to the goods not being delivered on scheduled or guaranteed dates.



SAP Event Management


SAP Event Management solves most of these issues we have discussed. It can automatically monitor planned routes, dates and milestones.


Upon completion of each milestone, the reported event updates in the system when the freight forwarder, carrier, shipper or consignee sends the data to SAP Event Management. Any unexpected delays or processes overdue can trigger an alert, email or SMS to the relevant team to address the issue immediately.


Customs declarations can also be submitted on time to track-and-trace the events that are happening on time, and if there are any deviations, then it is possible to trigger an alert to the customs documentation team to take immediate action in order to bring the shipment back on schedule.


If second or third stage milestone flights have been cancelled due to bad weather conditions then SAP Event Management will alert the shipping teams to secure new cargo space on the next available flight.


Here are some other high-level examples of what is possible with SAP Event Management:


  • Adjusting subsequent milestones when there is an unexpected event or delay on reported events
  • Track and trace the end-to-end route through SAP Visual Business Geo Map Integration for a shipment.
  • Extract the causes of delays and unexpected issues data in SAP Business Intelligence and publish it to key stakeholders
  • Monitor shipment performance and report frequent causes of delays in air cargo
  • Proactively manage exceptions and alert each milestone to the relevant teams


Filter Blog

By author: By date:
By tag: