SAP Event Management.pdf

SCM663 SAP Event Management SAP SCM

Date Training Center Instructors

Education Website

Participant Handbook Course Version: 95 Course Duration: 3 Day(s) Material Number: 50099725

An SAP course - use it to learn, reference it for work

Copyright Copyright © 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Trademarks •

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

•

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

•

ORACLE® is a registered trademark of ORACLE Corporation.

•

INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

•

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

•

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

•

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

•

JAVA® is a registered trademark of Sun Microsystems, Inc.

•

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

•

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Disclaimer THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

g2010927445

About This Handbook This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used. Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal and external.

2010

Example text

Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text

Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© 2010 SAP AG. All rights reserved.

iii

About This Handbook

SCM663

Icons in Body Text The following icons are used in this handbook. Icon

Meaning For more information, tips, or background

Note or further explanation of previous point Exception or caution Procedures

Indicates that the item is displayed in the instructor's presentation.

iv


2010

Contents Course Overview ......................................................... vii Course Goals ...........................................................vii Course Objectives .....................................................vii

Unit 1: Introduction........................................................ 1 Introduction ..............................................................2

Unit 2: Creating Events ................................................. 21 Creating Events ....................................................... 22

Unit 3: Event Notification and Status Retrieval ................... 41 Status Retrieval ....................................................... 42 Event Notification ..................................................... 48 Reaction to an Event ................................................. 83

Unit 4: Monitoring and Analysis...................................... 91 Monitoring and Analysis.............................................. 92

Unit 5: Visibility Processes ........................................... 103 Visibility Processes ..................................................104

Unit 6: Configuring the Application System ...................... 131 Configuring the Application System ...............................132 Configure Drilldown into Application Object ......................173 Generic Application Interface.......................................175

Unit 7: Creating Event Handlers – Configuration................ 183 Creating Event Handlers - Introduction ...........................184 Expected Events and Event Codes................................187 Tracking/Query IDs ..................................................200 Parameters ...........................................................206 Status..................................................................216 Event Handler Type..................................................221 Event Handler Sets ..................................................230 Maintaining the Event Handler .....................................236

Unit 8: Event Notification – Configuration ........................ 273 Event Notification - Configuration ..................................274

2010


v

Contents

SCM663

Unit 9: Reaction to Events – Configuration....................... 303 Reaction to Events - Introduction ..................................304 Rule Sets, Rules, Conditions and Activities ......................308 Informing and Alerts .................................................316 Follow-Up Activities..................................................324

Unit 10: Web Interface ................................................. 367 Web User Interface ..................................................368 Authorization and Filters ............................................396

Unit 11: Analytics ....................................................... 417 SAP BI Reporting from SAP EM ...................................418 Data Upload from SAP EM to SAP BI.............................430

Unit 12: Document Flow............................................... 439 Document Flow.......................................................440

Unit 13: SAP Object Event Repository............................. 479 SAP Object Event Repository ......................................480

Appendix 1: Additional Topics

vi

.................................... 507


2010

Course Overview Target Audience This course is intended for the following audiences: • •

Project team members responsible for the implementation of SAP Event Management SAP consultants and SAP partners

Course Prerequisites Required Knowledge •

None

Recommended Knowledge • • •

Knowledge of business processes related to the Event Management implementation Knowledge of SAP NetWeaver Business Intelligence Knowledge of the SAP Web Application Server 6.40

Course Goals This course will prepare you to: •

Course Objectives After completing this course, you will be able to: • • • •

2010

Explain the elements of SAP Event Management Send event notifications and perform status retrieval Configure the Fulfillment visibility process in the SAP ERP application system and SAP Event Management Configure the user interface, the Web Communication Layer


vii

Course Overview

viii

SCM663


2010

Unit 1 Introduction Unit Overview

Unit Objectives After completing this unit, you will be able to: • •

Define the SAP Event Management solution Explain an application for Supply Chain Event Management

Unit Contents Lesson: Introduction ...............................................................2

2010


1

Unit 1: Introduction

SCM663

Lesson: Introduction Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • •

Define the SAP Event Management solution Explain an application for Supply Chain Event Management

Business Example You are a member of the SAP Event Management project team at your company. Your first step is to understand the overall picture of SAP Event Management and how it can be used in your business.

Figure 1: Static Business Models are Challenged Traditional Supply Chains Evolving to Supply Networks

Business Drivers • • • •

2

Globalization leading to supply & demand volatility and risk Network complexity increases need for visibility Rising costs and shrinking margins Differentiation based on superior customer service


2010

SCM663

Lesson: Introduction

Figure 2: The Common Theme Responsiveness and Efficiency

The Challenges of Balancing Efficiency and Responsiveness: Build Flexibility in your supply networks. If there is one thing that we have learnt in these past couple of years, it is that the only thing that is constant is “change.” 2008 was about globalization, opportunity, innovation. Now were talking about recession, cost pressures, conserve. Need to emphasize Responsiveness (at the right cost). In the past, it was enough for a company to set up cost-effective, stable processes for their supply chain, which often left very little room for changes due to unforeseen events. Now, however, there is an increasing need for a company to put in place systems and processes that are able to flexibly respond to rapidly changing business conditions – this has increased chaotic or ad hoc processes throughout the network. For example, in 2008 the price of oil fluctuated both up and down by a factor of over 300% (check math). In January of 2008 we were all talking about the fact that the price of a barrel of crude oil had smashed through the $100 mark, and how this had significant impacts on the plans that had been made based on a $40 barrel of oil. “How can we afford the transportation costs? Why did I outsource to China? Do I need to re-optimize my logistics network? Fast forward 6 months and the price was at an all time high of near $150 and ” the sky was falling in. Today, the price has fallen again to levels around the Jan 2007 mark of $45. How do you plan for these dramatic changes?

2010


3


SCM663

The key is having not just the ability to react but the responsiveness and efficiency to constantly re-plan and re-align your activities based on the current business dynamics. The need to balance these two ideals – to intelligently sense and respond to changing market conditions and regulations - is why companies strive to be part of a responsive supply network.

Figure 3: Visibility is Key in Todays Complex Supply Networks

Figure 4: Positioning and Value – SAP Event Management

4


2010

SCM663


Figure 5: Business Problem & Drivers

What are the key business objectives our customers are challenged with today? They have to comply with regulations such as the US Bioterrorism act or the European food safety regulation. They still want to ensure customer satisfaction despite outsourcing some or even all of their supply chain activities. They want to reduce their costs by reducing uncertainties that lead to buffer inventory and buffer times and/or expensive fire-fighting. They want to reduce time to action by being able to recognize and react upon unplanned events in the supply chain and their effect. They want to manage by exception rather than monitoring processes that are running smoothly. They have to provide transparency – for themselves or for their business partners throughout the complete distributed process. And in the end, they want to control their and their business partners performance.

2010


5


SCM663

Figure 6: Definition of Supply Chain Event Management (SCEM)

Supply Chain Event Management was defined by AMR as an application supporting control processes for managing events within and between companies. As per this definition, this application supports the ability to monitor what is happening within the supply chain, to notify the right person in case of a delay or critical event, simulate activities, control your processes and eventually measure your supply chain activities so that you can adapt your business process and make it more effective and efficient.

Figure 7: SAP Event Management – Visibility, Track & Trace

Track planned vs. actual events at various levels.

6


2010

SCM663


Automated exception resolution by notification and workflow triggering. Extended process metrics and analytics for performance analysis and compliance. Pre-configured business scenarios.

Figure 8: Event Possibilities

Actual events refer to certain milestones in the process. Usually these milestones are planned with the help of an application and are stored within the ERP system, but you also may want to define additional milestones. If an actual event occurs within a given tolerance, you call it a regular event. Besides that an event that you expect to happen within a particular time frame can happen outside of that time frame. This is an early/late event and could cause a subsequent event to be rescheduled, or it could simply be recorded. An unexpected event is one that you don't plan, because you don't want it to happen. Still, it might have a big impact on your process. Fourth is an unreported event. Here, you expect an event to occur within a particular time frame, it is not reported. Something still needs to happen following this event whether or not it is reported, so you could set a time limit that sends a message or causes something to happen when the event is unreported in a certain time period. Supply Chain Event Management is dealing with all those different event types.

2010


7


SCM663

Figure 9: How Event Management Works

Figure 10: An Event Message – the Means to Report Relevant Observations

An event message can not only be received via various technologies, but one message can report various events. The event status tells what has happened and who has reported the event. The tracking ID identifies the object(s) that is/are affected. Other information within the message could include such things as the location, involved partners, estimated time, delivery status, subsequent status, load transfers, confirmation of a measurement result or text.

8


2010

SCM663


Figure 11: SAP Event Management: Understand, Adapt, Respond

These are the four corner stones of SCEM. They contribute to providing an adaptive solution, and will be explained more detailed on the next slides.

Figure 12: Providing the right information, to the right people, at the right time: Web UI

2010


9


SCM663

Figure 13: Notify

Notifying means that in case of an exceptional situation the respective stakeholders are informed with the help of an alert. This can be caused by... Alerting helps you to optimize reaction times and improve quality and finally customer satisfaction.

Figure 14: Notifying the Stakeholders

10


2010

SCM663


Notifying the stakeholders can be done in different ways – you can for example send an email, a short message or a fax, or simply post the alert to the universal work list. This functionality is provided by the alert framework coming with SAP NetWeaver.

Figure 15: Adjust

Adjusting means that – based on the findings – follow-up activities are triggered. This can be done in an exceptional case, when for example an arrival is rescheduled when a transportation delay occurs. Or also when simply the process needs to be adjusted to reality. You can...

Figure 16: Measure...

2010


11


SCM663

Measuring provides the data that is necessary to evaluate the efficiency of the monitored processes. SAP Event Management feeds statistical information into SAP NetWeaver Business Intelligence, which will automatically update KPIs delivered with the Business Content.

Figure 17: Analytics – Example

SAP Event Management can provide actual dates, times, quantities, etc., used for capturing Key Performance Indicators. For example, Perfect Order Fulfillment measures whether a customer received the exact quantity of what he ordered, on the date and time when he requested it.

12


2010

SCM663


Figure 18: SAP EM – Solution Overview

Our SCEM solution is more than just the SAP Event Management application back and forth integration with application systems (either SAP or non-SAP) as well as appropriately providing the information to all stakeholders, accessing data from within an enterprise portal and finally determining key performance indicators are also integral parts of this solution.

2010


13


SCM663

Figure 19: SAP EM – Integration with Application Systems

Integration with another SAP component is usually done with the SAP Event Management application interface, which comes with any SAP application system (PlugIn Basis). It allows you to define which application objects may be relevant for SAP EM, and to transfer an event to SAP EM when an application object is modified or deleted. The most important business objects are already technically-enabled. More advanced out-of-the-box integration is achieved with the help of so-called visibility processes which are covered in the next section

Figure 20: Visibility Processes

14


2010

SCM663



Visibility Processes allow us to add business content to the SAP EM tool. A Visibility Process is a template that makes SAP EM implementation easier for the customer. SAP provides pre-configured templates that a customer can either implement as is or adapt to his specific business process so that he does not need to start from scratch.

Figure 22: Visibility Processes in SAP Event Management

2010


15


SCM663

These are the standard visibility processes that are delivered with SAP EM 7.0.

Figure 23: Transportation Process – Example

Here you see an example of the transportation visibility process showing the multiple legs in a transportation process.

16


2010

SCM663


Figure 24: Value of SAP Event Management

2010


17


SCM663

Lesson Summary You should now be able to: • Define the SAP Event Management solution • Explain an application for Supply Chain Event Management

18


2010

SCM663

Unit Summary

Unit Summary You should now be able to: • Define the SAP Event Management solution • Explain an application for Supply Chain Event Management

2010


19

Unit Summary

20

SCM663


2010

Unit 2 Creating Events Unit Overview

Unit Objectives After completing this unit, you will be able to: • • •

Explain what an event handler is and why it is important Define events Generate an event handler and expected events

Unit Contents Lesson: Creating Events........................................................ 22 Exercise 1: Creation of an Event Handler................................ 29

2010


21

Unit 2: Creating Events

SCM663

Lesson: Creating Events Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • • •

Explain what an event handler is and why it is important Define events Generate an event handler and expected events

Business Example You want to track a shipment from your dock to final receipt at the customer’s dock. You have decided to use SAP Event Management to manage this process and provide visibility of the actual movement of the shipment.

Figure 25: Creating Events – Architectural Landscape

This illustration of the architectural landscape indicates which parts of the landscape come into play for creating events.

22


2010

SCM663

Lesson: Creating Events

At this point the legacy system or other SAP system determines whether or not an event handler is created, and is then created in SAP Event Management. Then the legacy system or other SAP system determines what the expected events will be and the timing of those events.

Figure 26: Business Process: Creating Events

This business process relates to the exercises. In the exercise, your customer has just ordered some pumps from you. To accommodate this order, you will need to create a sales order, create a delivery, and create a shipment. At the time the shipment is created, the event handler and expected events are created in SAP Event Management and an e-mail message could be sent to the customer. Once the shipment is planned, you will monitor the status of the activity from SAP Event Management. Next, as described in the unit on event notification and status retrieval, you will report events and monitor the status of the events that you have reported. At the end of the process, another e-mail could be sent to notify the customer of the status of the shipment.

2010


23


SCM663

Figure 27: Creating Event Handlers and Expected Events

Your business process first determines whether or not an event handler is created. Because you are processing documents in your application system, a check is made to see if an event handler should be created for that particular function. Data is gathered in the application system specific to the business process and configuration that you have defined to control the event process itself. Then, the event handler is created in SAP Event Management.

Figure 28: Event Handlers

An event handler generically represents a supply chain process, for example a purchasing process, a shipment process, or a manufacturing process.

24


2010

SCM663


The event handler consists of the relevant data, expected events or milestones and process information for a business process. An event handler is created following an action in the business process. An event handler is related to exactly one application object in a remote application system. An application object is defined in customizing and related to a business process. In the application object you define the event management relevance. For example, if you are creating shipment only for customer XYZ, then you define in your application object the condition: If customer = XYZ. An event handler can be changed, deleted and archived. To define event handlers in the SAP Event Management IMG, choose SAP Customizing Implementation Guide → Event Management → Event Handlers and Event Handler Data → Event Handlers.

Figure 29: Data of an Event Handler and an Event Handler Type

The event handler type is defined in customizing and tied to the business object type of an application Object Type. To define event handler types in the SAP Event Management IMG, choose SAP Customizing Implementation Guide → Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types. You can also use transaction code /SAPTRX/TSC0TT. In the event handler type, you describe the rule set, the status profile, the expected events profile, and the authorization profile. This means you define the rules for what happens when updates are received, the expected events, and the status attributes, for example, a container status or a shipment status.

2010


25


SCM663

The event handler type controls which expected events are generated and the status attributes, tracking IDs and any other parameters that correspond to those expected events.

Figure 30: Example for Training

In the exercises, the expected events that are to be generated include check-in, loading and carrier pick-up. The status attributes show the transportation status or delivery status, or could be another defined value as possible attributes for that event handler type. The tracking IDs are a delivery number and a shipment number. Parameters are the other data such as material number and other descriptive data that could be included.

26


2010

SCM663


Figure 31: Event Handler Sets

It is possible to have an event handler set where different business processes or different actions within a business process can start a new event handler. In the example shown in the illustration, when a customer order is received and entered into the SAP ERP system or a legacy system, the first event handler is created that tracks the customer order upon receipt. A second event handler is created at the time the delivery is created. The third set of expected events is created when the shipment is created. All of these event handlers are grouped together in an event handler set to represent one business process. Every event handler has its own data and the grouping allows us to view the data as one business process. To define event handler set profiles in the SAP Event Management IMG, choose SAP Customizing Implementation Guide → Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Set Profiles. You can also use transaction code /SAPTRX/TSC0ES.

2010


27


SCM663

Figure 32: Features of Expected Events and Profiles

The Expected Event Profile is a list of events that might possibly happen. This is the broadest possible list including any event that might possibly happen. You can define the sequence of expected events such that one event cannot take place before another event, for example, shipment cannot occur before production. You can have events created by other events and therefore not created by the application system. You can define dependencies of expected events when one event depends on another to determine an expected time or may be rescheduled because of another event that affects the supply chain. The Expected Events of the event handler is a list of the events that are actually expected to happen for this occurrence. When the expected events are generated, the dates are determined. Any changes to the expected events are maintained for data integrity. To define expected events in the SAP Event Management IMG, choose SAP Customizing Implementation Guide → Event Management → Event Handlers and Event Handler Data → Expected Events.

28


2010

SCM663


Exercise 1: Creation of an Event Handler Exercise Objectives After completing this exercise, you will be able to: • Demonstrate how a shipment scenario in SAP ECC creates an event handler in SAP Event Management

Business Example Your customer places an order for pumps. You have to create a delivery and a shipment. You will establish dates and times on the shipment, which will cause an event handler and expected events to be created in SAP Event Management.

Task 1: Create a shipment for your pumps. 1.

Create a standard sales order, based on data shown below: Field Name

Entry

Order Type

OR

Sales Organization

1000

Distribution Channel

10

Division

0

Sold-to Party

1280

PO Number

EM-02-##

Requested Delivery Date

Today + 2 business days

Material Number

P-102

Quantity Ordered

2

2.

Create the outbound delivery document from the sales order. In the delivery, enter the Pick Deadline of today’s date + two business days and the picking time at 1:00 a.m. This will become the expected time for the Picking Begin event.

3.

Note delivery number: ____________

4.

Create your shipment. Use the following data in the shipment creation process.

Continued on next page

2010


29


SCM663

Field Name

Entry

Transportation Planning Point

1000

Shipment Type

0002 – Collective Shipment Road*

Shipment Route

R00001

Shipping Condition

2

Planning Times Check-In Loading Start Loading End

Date

Time


8:00


9:00


10:00

When you save the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. 5.

Update the Shipment Stage information with the following dates and times: Shipment Stage Start End

Date

Time


11:00


22:00

When you save the shipment, these fields will be used to create the expected events Plant Departure and Customer Arrival. Note Shipment Number _____________

Task 2: Monitoring activity in SAP Event Management. Log into the SAP SCM/Event Management system and run the Event Handler List and view the event handler that was created by the shipment in the previous step. 1.


30


2010

SCM663


I.) II.) III.)

IV.)

Use event handler type LTL_DELIV. Enter your delivery number, including two leading zeros, in the Tracking ID field. Check the list of expected events. Are the changes to dates and times that you made in previous step reflected in the list of expected events? ____________ Check if the following status is set correctly: • •

V.)

2010

Delivery Status = On time Transportation Status = Not started

Check the info parameters, control parameters and IDs. This is all data associated with this event handler. In subsequent exercises, you will learn how this information is determined.


31


SCM663

Solution 1: Creation of an Event Handler Task 1: Create a shipment for your pumps. 1.


Entry

Order Type

OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-02-##


32


2010

SCM663


Field Name

Entry



Material Number

P-102

Quantity Ordered

2

a)

To see the basic shipment scenario and the corresponding event Handler creation in SAP Event Management, you start by creating a sales order, then a corresponding outbound delivery document. Then you will create a shipment document that contains your outbound delivery document. The shipment document represents the physical shipment to the customer. Create a standard sales order, based on data shown below:

2.

Field Name

Entry

Order Type

OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-02-##



Material Number

P-102

Quantity Ordered

2

b)

Log into the SAP ECC application system.

c)

Use transaction VA01 to create the sales order or from the menu choose Logistics → Sales and distribution → Sales → Order → Create.

d)

On the Initial Screen enter the order type, sales organization, distribution channel and division. Choose Enter.

e)

Choose Save.

Create the outbound delivery document from the sales order. In the delivery, enter the Pick Deadline of today’s date + two business days and the picking time at 1:00 a.m.


2010


33


SCM663

This will become the expected time for the Picking Begin event. a)

Use transaction VL01N or from the SAP menu choose: Logistics → Sales and Distribution → Shipping and Transportation → Outbound Delivery → Create → Single Document → with Reference to Sales Order

b)

Enter shipping point 1000. Enter the Selection Date as today + 2 business days. The sales order created in the previous exercise should appear in the Order field. Choose Enter.

3.

c)

On the Overview screen, select the Picking tab. Enter the pick date of today’s date + 2 business days. Enter 01:00 in the Time field.

d)

Choose Save.

Note delivery number: ____________ a)

4.

see task

Create your shipment. Use the following data in the shipment creation process. Field Name

Entry


1000

Shipment Type


Shipment Route

R00001

Shipping Condition

2

Planning Times Check-In Loading Start Loading End

Date

Time


8:00


9:00


10:00

When you save the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. Continued on next page

34


2010

SCM663


a)

To create the shipment document, use transaction VT01N or use the SAP menu path: Logistics → Sales and Distribution → Shipping and Transportation → Shipment → Create → Single Documents

b)

In the Initial Screen, enter the transportation planning point and shipment type. Note: Make sure you have the Expert options set in the Customizing of Local Layout Options so that you can see the display of the shipment type codes.

c)

Click Select Deliveries in the application toolbar.

d)

Scroll down the Select outbound deliveries dialog box to the W.ref.to box and enter your delivery document number in the Outbound Delivery field.

e)

Click the Execute icon at the lower-left corner of the Select outbound deliveries screen.

f)

On the Create: Shipments and Deliveries screen, click the icon (the mountain and sun) for overview of current shipment icon.

g)

Under the Processing tab on the upper portion of the screen, enter the shipment route and the shipping condition.

h)

In the Deadl. portion of the screen, choose Planning.

i)

Enter the planning data from the data table below. When you save the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. Planning Times

Date

Time

Check-In


8:00

Loading Start


9:00

Loading End


10:00

j)

Select the Stages tab.

k)

Select the button to the left of the stage that is displayed.

l)

Click the Stage details icon at the lower-left corner of the screen.

m)

Select the Dur.and distnce tab on the Details on Stage 0001 screen. Continued on next page

2010


35


n)

5.

SCM663

Update the shipment stage information with the following dates and times. When you save the shipment, these fields will be used to create the expected events Plant Departure and Customer Arrival.


Date

Time


11:00


22:00

When you save the shipment, these fields will be used to create the expected events Plant Departure and Customer Arrival. Note Shipment Number _____________ a)

Update the shipment stage information with the following dates and times. When you save the shipment, these fields will be used to create the expected events Plant Departure and Customer Arrival. Shipment Stage

Date

Time

Start


11:00

End


22:00

b)

Choose Copy at the bottom of the Details on Stage 0001 screen.

c)

Choose Save. Note Shipment Number _____________

Task 2: Monitoring activity in SAP Event Management. Log into the SAP SCM/Event Management system and run the Event Handler List and view the event handler that was created by the shipment in the previous step. 1.


36


2010

SCM663


I.) II.) III.)

IV.)

Use event handler type LTL_DELIV. Enter your delivery number, including two leading zeros, in the Tracking ID field. Check the list of expected events. Are the changes to dates and times that you made in previous step reflected in the list of expected events? ____________ Check if the following status is set correctly: • •

V.)

Delivery Status = On time Transportation Status = Not started

Check the info parameters, control parameters and IDs. This is all data associated with this event handler. In subsequent exercises, you will learn how this information is determined.

a)

Log into the SAP SCM/Event management system using the client number, user ID, and password provided by your instructor.

b)

Run the Event Handler List. SCM/EM: Event Management → Monitoring and Lists → Event Handler List In the selection screen, enter LTL_DELIV in the Event handler Type field. Enter your delivery number with two leading zeroes in the Tracking ID field. Choose Execute.

c)

d)

Select the Expected Events tab. Record the following: Picking Begin:

Date: _____________

Time:

_____________

Picking End:

Date: _____________

Time:

_____________

Loading Begin:

Date: _____________

Time:

_____________

Loading End:

Date: _____________

Time:

_____________

Select the Status Detail tab. Record the following: Continued on next page

2010


37


SCM663

Delivery Status: ___________________________________ Transportation Status: ___________________________________ e)

Go to the Event Handler Details by double-clicking on the Event Handler Overview icon. Record the following from the Header Data tab data: AO Type: ____________________________ Bus Proc Type: ____________________________ EH Type: ____________________________

f)

Select the System Parameters tab. Record the following: SHIP_TO_PARTY ____________________________ ROUTE ____________________________

g)

Select the Control Parameters tab. Record the following: SHIPMENT_TYPE: ____________________________ SHIPPING_CONDITION: ____________________________

h)

Select the Info Parameters tab. Record the following: SALES_ORDER_NO: ____________________________ CONFIRMED_DATE: ____________________________

38

i)

Choose Back.

j)

Choose Exit.


2010

SCM663


Lesson Summary You should now be able to: • Explain what an event handler is and why it is important • Define events • Generate an event handler and expected events

2010


39

Unit Summary

SCM663

Unit Summary You should now be able to: • Explain what an event handler is and why it is important • Define events • Generate an event handler and expected events

40


2010

Unit 3 Event Notification and Status Retrieval Unit Overview

Unit Objectives After completing this unit, you will be able to: • • • •

Display the different possibilities for status retrieval Explain the purpose of an actual event Explain the different possibilities for reporting events Explain the options that a company has to respond to an event

Unit Contents Lesson: Status Retrieval ........................................................ 42 Lesson: Event Notification ...................................................... 48 Exercise 2: Types of Actual Events ....................................... 63 Lesson: Reaction to an Event .................................................. 83

2010


41

Unit 3: Event Notification and Status Retrieval

SCM663

Lesson: Status Retrieval Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Display the different possibilities for status retrieval

Business Example You want to view the status of events after events have been reported.

Figure 33: Status Retrieval – Architectural Landscape

Now in the architectural landscape we look at what comes into play for retrieving events. At this point, multiple devices might be required to retrieve the status of an event handler. These devices might include a mobile device, a PDA or a Web browser. It is also possible to retrieve messages directly from SAP Event Management, or from another SAP system.

42


2010

SCM663

Lesson: Status Retrieval

Figure 34: Status Retrieval via the Web

It is also possible to retrieve the status of an event handler using the web as an interface. In this case as an example, an e-mail could be generated that would provide a link where you or your customer could go and check the status of a particular event handler. A Web User Interface allows you to view the event status, which comes directly from SAP Event Management.

Figure 35: Overview of new Web Interface

2010


43


SCM663

Figure 36: Drilldown into Application System

When you are viewing the event handler detail in SAP Event Management, you can display the original document from the SAP application system if the respective configuration is provided.

Figure 37: Event Handler List: Status Retrieval in SAP EM

It is also possible to check the status of an event handler from within SAP Event Management.

44


2010

SCM663


To access the event handler list, from the SAP Easy Access menu, choose Event Management → Monitoring and Lists → Event Handler List. You can also access this list with transaction code /SAPTRX/EH_LIST.

Figure 38: Embedded Status Reporting

In this example, we see a standard SAP document, a production order with an embedded tab containing the status data. This remote function call (RFC) can be called by the document program in the SAP ERP system to provide the visibility of the event handler right in the document that is concerned with this particular set of events. This BADI development is available with PI 2003.1. The plug-in works with the delivery and the production order.

2010


45


SCM663

Figure 39: Status Retrieval – Key Data

Whichever method of status retrieval you choose, the information that you receive is consistent. You will see the list of expected events and whatever actual events have been reported so far. You will also see some information parameters such as material number or order number and that type of information. You can see the actual dates and times and other information that has been posted and you can see the status of the event handler itself. In the web retrieval, you can configure which information you get.

46


2010

SCM663


Lesson Summary You should now be able to: • Display the different possibilities for status retrieval

2010


47


SCM663

Lesson: Event Notification Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • •

Explain the purpose of an actual event Explain the different possibilities for reporting events

Business Example Based on a shipment that has occurred from your company, you will report event completion for predefined milestones and unexpected events. Your company and partners report using various methods.

Figure 40: Event Notification – Architectural Landscape

This illustration of the architectural landscape indicates which parts of the landscape come into play for reporting events. At this point, multiple devices might be used or required to update SAP Event Management. It is also possible for the application system to provide the update to the event handler.

48


2010

SCM663

Lesson: Event Notification

Figure 41: Actual Events

Event handlers represent processes and inventories having life cycles, for example, production, shipment, serialized material starts and ends. Milestones include things such as agreements, carrier arrivals, departures, and other happenings that you would like to monitor. Against these milestones we match the actual events that are reported, for example, the scanning of barcodes for reporting goods receipts. A regular event is an actual event that happens in the range of time when we expect it. An overdue event is one that doesnt happen within the expected time and will be reported later. This information might be important for carrier performance, for example. An unexpected event is reported even though it was not expected. An unreported event refers to an expected event that is not reported.

2010


49


SCM663

Figure 42: Methods of Event Notification

There are many ways to communicate the actual events. Possible communication scenarios include updating with an online transaction, EDI/XML connection, PI, onboard devices, manual entry, offline PDAs, voice recognition, login with a web interface, or updating using an RF device.

Figure 43: Content of an Event Message

An event message can not only be received via various technologies, but one message can report various events. The event status tells what has happened and who has reported the event.

50


2010

SCM663


The tracking ID identifies the objects that are affected. Other information within the message could include such things as the location, involved partners, estimated time, delivery status, subsequent status, load transfers, confirmation of a measurement result, or text.

Figure 44: Event Notification via the Web

One possibility for receiving event messages is to use the Web front end. In this scenario, a user logs directly into the SAP Event Management system using a Web browser and the event handler is directly updated.

2010


51


SCM663

Figure 45: Event Notification Using EDI, XML or BAPI

It is also possible to report events using an EDI or XML connection. In the case of an XML update, PI receives the XML template and calls an RFC. In the case of EDI, an IDoc is called. A BAPI or RFC is called for adding the event message to SAP Event Management.

52


2010

SCM663


Figure 46: SAP Exchange Infrastructure and Web Services

SAP Process Integration (PI) is the SAP platform for process integration based on the exchange of XML messages. SAP PI provides a technical infrastructure for XML-based message exchange in order to connect SAP components with each other, as well as with non-SAP components. SAP PI delivers business-process and integration knowledge to the customer, in the form of predefined business scenarios and provides an integrated toolset for building new business scenarios by defining and maintaining all integration-relevant information or what is referred to as shared collaboration knowledge. SOAP, which stands for Simple Object Access Protocol, is an XML-based protocol that lets applications exchange information over HTTP.

2010


53


SCM663

Figure 47: Updating SAP EM from Tracking Service Providers

In this example, tracking service providers (TSPs) are connected to the SAP Exchange Infrastructure and communicate to SAP Event Management either via BAPI or RFC. The tracking service provider can send an URL info with an event message that is completed with the help of the entry done in the SAP SCM IMG under Event Management → Event Messages, Status Queries and Web Interface → URL Templates for Tracking ID Providers. This allows the user to navigate to the TSPs tracking information.

54


2010

SCM663


Figure 48: Event Notification Using Voice Recognition

Voice recognition is another option for reporting events. In this example, the voice server identifies the truck driver and sends a voice XML message that is received by SAP Event Management. SAP Event Management then receives the message and any follow-up activities are triggered automatically.

Figure 49: Reporting Events Using Radio Frequency Devices

Reporting events is also possible using radio frequency devices. Here it is possible to configure an RF transaction from the SAP Event Management system. This configurable transaction is shown as /N/SAPTRX/MI01 in the exercises. It can be set up to cause an update in the application system, but here, it is a stand-alone transaction. A second option using radio frequency (RF) would be to use your normal Warehouse Mobile Data Entry and RF tools and have those transactions trigger the update to the SAP Event Management system.

2010


55


SCM663

Figure 50: Reporting Events Using Application Systems

It is also possible to have events reported by the application system, whether that is a legacy system or an SAP system. In this example, the transaction is run as normal within the application, but there is a trigger to create an event message and send it via BAPI to SAP Event Management. For example, you book goods receipt in the application system and then you can have that action cause a message to SAP Event Management to update your event handler. In this case, it doesn't matter if the transaction is being run within SAP ERP on a desktop or an RF device. The reverse is also possible. An update in SAP Event Management can cause the goods receipt to happen.

56


2010

SCM663


Figure 51: Planned Measurements and Measurement Data

A table in SAP Event Management contains planned and actual measurement data. You can process measurement data that was transferred to SAP Event Management with event message PROCESS_MEASUREMENTS, which processes measurement data. You can check if the measurement is an expected event and if it was confirmed within the tolerance range with event message IS_MEASUREMENT_CONF. This event message asks if the event message confirmed an expected measurement result. You can check if the expected and reported measurement data can be compared with event message IS_MSRMNT_NOT_COMPAR. This event message asks if the event message could not be compared to the expected measurement result. You can check if the measurement is an expected measurement that has not yet been confirmed as being within the tolerance range with event message IS_MSRMNT_OUT_OF_TOL. This event message asks if the reported measurement result exceeded the expected measurement result.

2010


57


SCM663

Figure 52: Features – Internal Processing

It is possible to use an event message to dynamically create an event handler. It is also possible to manipulate events by adding new expected events or changing or deleting existing events.

Figure 53: Reporting Events by Entering Data Manually in SAP EM

It is also possible to report events manually by entering data directly into SAP Event Management. With this option, you enter the tracking code, tracking ID and the message content including actual date, time, reason codes, and so forth.

58


2010

SCM663


Use transaction /N/SAPTRX/MI02 to enter the data directly. There is no menu path for this transaction.

Figure 54: Event Processing (1/2)

When SAP Event Management receives an event message, the message is processed and SAP Event Management is responsible for the following steps: • • • •

2010

Storing the raw event data Validating the events Determining what to do with the event based on the event code, location, partner data Relating the message to the specific event handler to be updated


59


SCM663

Figure 55: Event Processing (2/2)

When an event message is received, SAP Event Management processes the event. First it maps the data from the message and validates the event. An internal code is obtained and the message is written to the database. There is then a rule set to check for what needs to happen next and trigger any follow-up tasks. The tasks are executed.

Figure 56: Event Codes and Mapping of Codes

60


2010

SCM663


External events are normally reported in a standard format such as ANSI X.25 or EDIFACT. It is possible to add the customer's own standard but ANSI and EDIFACT are delivered. External code sets can be defined in SAP Event Management. External codes are mapped to the internal codes. SAP Event Management then deals only with the internal code, which can be defined in configuration.

Figure 57: Event Handler Data – Event Notification

Event messages are sent to SAP Event Management. A message log is written and retained. If there is an error, SAP Event Management will process the error and maintain the log and retain the message. If there is no error, the messages are then reported to the event handler as updates. Once an event is received by the event handler, a rule set is invoked. Based on that rule set, other activities or actions can be started and possibly another event set is created. For example, e-mails or faxes could be sent.

2010


61


62


SCM663

2010

SCM663


Exercise 2: Types of Actual Events Exercise Objectives After completing this exercise, you will be able to: • Demonstrate an entire shipment scenario in SAP Event Management

Business Example Now that you have shipped your pumps, you will play the role of all three parties reporting events against this shipment: the supplier, the freight carrier, and the customer. Reporting against these events will update the expected events for this event handler. You will enter different event confirmation transactions to illustrate some of the reporting options available. The graphic below displays the roles and events. Note:

Figure 58: Roles and Events

Task: 1.

Supplier role


2010


63


SCM663

In SAP Event Management, go to the Event Handler List to review the expected events. Compare the expected events to the process steps shown in the graphic of roles and events. Do any events appear on the graphic above that do not appear on the event handler? Are there any event messages? Have any events been reported in the Event Date column? Leave this session open because you will refer back to it in this exercise. 2.

Open a new session and post event messages for the first three events listed for your shipment: picking begin, picking end and packing. The events are related to processes performed in your company, as the supplier. Use transaction /SAPTRX/MI02 , which is not available through the SAP Easy Access menu. Tracking Code Set: DLNR. Tracking Code ID: Your delivery number, including two leading zeroes, from the previous exercise. Picking Begin – Enter the same date and time in the ActEvtDate and Time fields, as you see in the Expected Event Date and Time fields. Picking End – Enter the same date and time in the ActEvtDate and Time fields, as you see in the Expected Event Date and Time fields. Packing – Enter the same date, but enter a time 30 minutes later than planned.

3.

Go back to the Event Handler List and refresh your screen. Check to see if the event handler has been updated. On the Expected Events tab, have the three events been posted? Are there any event messages? Do you have any error messages?

4.

Carrier Role Before logging into the Web Interface, you must assign the following tracking scenarios and Web transactions to your user ID in the SCM/EM IMG: Web. Int. Trans.

User Profile ID

Order Web

LTL_CARRIER

LTL_DELIV_CARRIER

Leave blank

LTL_CUSTOMER

LTL_DELIV_CUSTOMER

Leave blank


64


2010

SCM663


5.

Report the carrier arrival using the Web Interface. This is the Web browser. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search Log on with your user data of the SAP EM system. Choose tracking scenario Carrier’s Delivery and enter your shipment number. Choose Apply. Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click on Report All Expected Events. Select the Arrival Carrier record and enter the same date, time and time zone as you see in the Expected Event Date and Time fields. You must also select a valid Reason Code. Choose Send. Close the window. You will see the update immediately in the Web Interface. Go back to the Event Handler List in the SAP Event Management system and refresh your screen. Check to see if the event handler has been updated. Scroll to the right to see the text you entered.

6.

Supplier Role (Warehouse Forklift Operator) Again using transaction /SAPTRX/MI02 , report the Load Begin and Load End transactions. This transaction emulates input from a remote device, such as an RF device on a forklift. Enter transaction /n /SAPTRX/MI02 . Enter tracking code set DLNR. In the Tracking Code ID field, enter your delivery number, including two leading zeroes from the previous exercise. Click GO. For LoadBeg, enter the same date and time in the ActEvtDate and Time fields, as you see in the Expected Event Date and Time. For LoadEnd, enter the same date and time in the ActEvtDate and Time fields, as you see in the Expected Event Date and Time fields. Select the lines and send the updates.


2010


65


7.

SCM663

Go back to the Event Handler List using transaction /SAPTRX/EH_LIST and view how the event handler has been updated. Did the expected events change? Are there any new event messages? See Event Message tab. What is the status:

8.

Delivery Status:

____________________

Transportation Status:

____________________

Carrier Role Report the Plant Departure event using the Web Interface. Enter Carrier’s Delivery as the tracking scenario. Enter the shipment number, and choose Search. Select the Report Departure box and choose Continue. Enter the date, time, and time zone as you see in the Expected Event Date and Time and choose Send. Choose Send in the dialog box that appears. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search

9.


Delivery Status:

____________________


____________________

Did either of them change? 10. Carrier Role


66


2010

SCM663


Report a transportation delay using the Web Interface. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search 11. Go back to the session with the Event Handler List and view how the event handler has been updated. How does the delay appear on the Consolidated Events list? ______________________________________________________ ______________________________________________________ How does the delay appear on the Expected Event list? Explain: ______________________________________________________ ______________________________________________________ Is reason code shown on the Event Messages tab? Yes What is the delivery status? ______________________________________________________ 12. Carrier Role Report the carrier’s arrival at the customer via the Web Interface, and then check the status again. What is the status:

Delivery Status:

____________________


____________________

Did either of them change? __________________________ Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search


2010


67


SCM663

13. Report a transportation delay using the Web Interface. Enter Carrier’s Delivery as the tracking scenario. Enter the shipment number, and choose Apply. Check in the Event Handler List if the event is posted. 14. Customer Role Report the proof of delivery using the Web Interface. To change to the Customer role, select the tracking scenario to Customer's Delivery. Enter your purchase order number (field is case sensitive) and choose Search. Click on Send Event Messages and select Report Proof of Delivery. In the dialog box that appears, note the date and time. Choose Send. 15. Verify that the proof of delivery was sent to your event handler. Go back to the session with the Event Handler List and view how the event handler has been updated. Did the expected events change? ________________________ Are there any new event messages? ________________________ What is the status:

Delivery Status:

____________________


____________________

Did either of them change? ________________________

68


2010

SCM663


Solution 2: Types of Actual Events Task: 1.

Supplier role In SAP Event Management, go to the Event Handler List to review the expected events. Compare the expected events to the process steps shown in the graphic of roles and events. Do any events appear on the graphic above that do not appear on the event handler? Are there any event messages? Have any events been reported in the Event Date column? Leave this session open because you will refer back to it in this exercise.

2.

a)

In the SCM/EM SAP menu, choose Event Management → Monitoring and Lists → Event Handler List

b)

In the selection screen, enter LTL_DELIV in the Event Handler Type field.

c)

Enter your delivery number with two leading zeroes in the Tracking ID field.

d)

Choose Execute.

e)

Select the Expected Events tab and compare the list of expected events to the graphic of roles and events.

f)

Select the Event Messages tab. Are there any entries in the Reported Event Date and Time column?

Open a new session and post event messages for the first three events listed for your shipment: picking begin, picking end and packing. The events are related to processes performed in your company, as the supplier. Use transaction /SAPTRX/MI02 , which is not available through the SAP Easy Access menu. Tracking Code Set: DLNR. Tracking Code ID: Your delivery number, including two leading zeroes, from the previous exercise. Picking Begin – Enter the same date and time in the ActEvtDate and Time fields, as you see in the Expected Event Date and Time fields. Continued on next page

2010


69


SCM663

Picking End – Enter the same date and time in the ActEvtDate and Time fields, as you see in the Expected Event Date and Time fields. Packing – Enter the same date, but enter a time 30 minutes later than planned.

3.

a)

In the new session, enter /n/SAPTRX/MI02 in the Command field. Choose Enter.

b)

The Event Confirmation screen will be displayed. Enter DLNR in the Tracking ID Code Set field. Enter your delivery number with two leading zeroes, for example, 0080015102, in the Tracking ID Code ID field.

c)

Choose GO. The list of expected events will be displayed.

d)

Enter an actual picking begin date and time. Enter the same date and time in the ActEvtDate and ActEvtTime fields as you see in the ExpEvtDate/Time field.

e)

Enter an actual picking begin date and time. Enter the same date and time in the ActEvtDate and ActEvtTime fields as you see in the ExpEvtDate/Time field.

f)

Enter an actual packing begin date and time. Enter the same date in the ActEvtDate field, but enter a time 30 minutes later than planned in the Time field.

g)

Select the events PICKBEG, PICKEND, and PACKING.

h)

Choose Post selected messages.

i)

In the Message Posting Confirmation screen, choose Send.

j)

From the Event Confirmation screen, choose Exit.

Go back to the Event Handler List and refresh your screen. Check to see if the event handler has been updated. On the Expected Events tab, have the three events been posted? Are there any event messages? Do you have any error messages?

4.

a)

Select the session with the Event Handler List in the SCM/EM server.

b)

Select the Expected Events tab.

c)

Choose the Refresh icon. It’s the first icon on the left.

d)

Answer the questions listed above.

e)

To check for error messages, select the Error Messages tab.

Carrier Role Continued on next page

70


2010

SCM663


Before logging into the Web Interface, you must assign the following tracking scenarios and Web transactions to your user ID in the SCM/EM IMG: Web. Int. Trans.

User Profile ID

Order Web

LTL_CARRIER

LTL_DELIV_CARRIER

Leave blank

LTL_CUSTOMER

LTL_DELIV_CUSTOMER

Leave blank

a)

In the SCM/EM IMG navigate to SCM IMG: Event Management → Event messages, Status Queries, and Web Interface → Web Interface → Assign User Profiles and Web Interface Transactions to Users

5.

b)

Enter your user ID TZEM02-## in the User field, then choose Continue.

c)

In the Change View screen, choose New Entries.

d)

Enter the two Web Int. Trans. entries from the table above.

e)

Choose Enter and then Save.

f)

Choose Exit.

Report the carrier arrival using the Web Interface. This is the Web browser. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search Log on with your user data of the SAP EM system. Choose tracking scenario Carrier’s Delivery and enter your shipment number. Choose Apply. Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click on Report All Expected Events. Select the Arrival Carrier record and enter the same date, time and time zone as you see in the Expected Event Date and Time fields. You must also select a valid Reason Code. Choose Send. Close the window. You will see the update immediately in the Web Interface. Continued on next page

2010


71


SCM663

Go back to the Event Handler List in the SAP Event Management system and refresh your screen. Check to see if the event handler has been updated. Scroll to the right to see the text you entered. a)

Use the same logon data that you used to log in to the SCM/EM system. 1. 2. 3. 4.

Enter your user name. Enter your password. Select the language, if necessary. Click Log on.

b)

Select tracking scenario Carrier’s Delivery.

c)

Enter your shipment number from the exercise in Unit 2, “Creating Events”.

d)

Choose Apply.

e)

Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click on Report All Expected Events.

f)

Select the Arrival Carrier record and enter the same date, time and time zone in the Actual Event Date and Actual Event Time fields as you see in the Planned Event Date/Time field. You must also select a valid Reason Code. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field.

g)

Choose Send. Close the window. You will see the update immediately in the Web Interface.

h)

Close the Web Interface screen. Go back to the Event Handler List in the SAP Event Management system and refresh your screen. Check to see if the event handler has been updated. Scroll over to the right to see the text you entered.

6.

Supplier Role (Warehouse Forklift Operator) Again using transaction /SAPTRX/MI02 , report the Load Begin and Load End transactions. This transaction emulates input from a remote device, such as an RF device on a forklift. Enter transaction /n /SAPTRX/MI02 . Enter tracking code set DLNR. In the Tracking Code ID field, enter your delivery number, including two leading zeroes from the previous exercise. Click GO. Continued on next page

72


2010

SCM663


For LoadBeg, enter the same date and time in the ActEvtDate and Time fields, as you see in the Expected Event Date and Time. For LoadEnd, enter the same date and time in the ActEvtDate and Time fields, as you see in the Expected Event Date and Time fields. Select the lines and send the updates.

7.

a)

In the session enter /n/SAPTRX/MI02 in the Command field. Choose Enter.

b)

The Event Confirmation screen will be displayed. Enter DLNR in the Tracking ID Code Set field.

c)

Enter your delivery number with two leading zeroes, for example, 0080015102, in the Tracking ID Code ID field.

d)

Choose GO. The list of expected events will be displayed.

e)

Enter an actual loading begin date and time. Enter the same date and time in the ActEvtDate and Time fields as you see in the ExpEvtDate and Time fields.

f)

Enter an actual loading end date and time. Enter the same date and time in the ActEvtDate and Time fields as you see in the ExpEvtDate and Time fields.

g)

Select the events LOADBEG and LOADEND.

h)


i)

In the Message Posting Confirmation screen, choose Send.

j)

From the Event Confirmation screen, choose Exit.


Delivery Status:

____________________


____________________

a)


b)

Select the Expected Events tab.

c)

Select the Refresh icon. It’s the first icon on the left.

d)


e)

To check for error messages, select the Error Messages tab. Continued on next page

2010


73


8.

SCM663

Carrier Role Report the Plant Departure event using the Web Interface. Enter Carrier’s Delivery as the tracking scenario. Enter the shipment number, and choose Search. Select the Report Departure box and choose Continue. Enter the date, time, and time zone as you see in the Expected Event Date and Time and choose Send.


74


2010

SCM663


Choose Send in the dialog box that appears. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search a)



b)


c)


d)

Choose Apply.

e)

Click on Send Event Messages and select Report Departure. The Report Departure screen should appear.

f)

Enter the same date and time in the Actual Event Date and Actual Event Time fields as you see in the Planned Event Date/Time field in the Event Handler List. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field. Choose Send.

9.

g)

Close the Window. Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click Page Down until you see the Plant Departure event. Verify that your actual date is present. You will see the update immediately in the Web Interface.

h)

Close the Web Interface screen.

Go back to the Event Handler List using transaction /SAPTRX/EH_LIST and view how the event handler has been updated. Did the expected events change? Are there any new event messages? See Event Message tab. Continued on next page

2010


75


What is the status:

SCM663

Delivery Status:

____________________


____________________

Did either of them change? a)


b)

Select the Expected Events tab and answer the question above.

c)

Choose Refresh. It’s the first icon on the left.

d)

Select the Event Messages tab and answer the question above.

e)

To check the status messages, select the Status Detail tab.

f)


10. Carrier Role


76


2010

SCM663


Report a transportation delay using the Web Interface. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search a)



b)


c)

Enter your shipment number from the exercise in Unit 2, “Creating Events.”

d)

Choose Apply.

e)

Click on Send Event Messages and select Report Delay. The Report Delay screen should appear.

f)

Enter a date and time in the Actual Event Date and Actual Event Time fields that is several hours after the plant departure. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field.

g)

Select Weather-Related or other reason in the Reason Code field.

h)

Choose Send.

i)

Close the Window. Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click Page Down until you see the Unplanned Event – Delay event. Verify that your actual date is present. You will see the update immediately in the Web Interface.

j)


11. Go back to the session with the Event Handler List and view how the event handler has been updated. How does the delay appear on the Consolidated Events list? ______________________________________________________ Continued on next page

2010


77


SCM663

______________________________________________________ How does the delay appear on the Expected Event list? Explain: ______________________________________________________ ______________________________________________________ Is reason code shown on the Event Messages tab? Yes What is the delivery status? ______________________________________________________ a)


b)

Select the Consolidated Events tab.

c)

Choose Refresh. It’s the first icon on the left. Answer the question above.

d)


e)


f)


g)

Answer the question listed above.

12. Carrier Role Report the carrier’s arrival at the customer via the Web Interface, and then check the status again. What is the status:

Delivery Status:

____________________


____________________


78


2010

SCM663


Did either of them change? __________________________ Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search a)



b)


c)


d)

Choose Apply.

e)

Click on Send Event Messages and select Report Arrival. The Report Arrival screen should appear.

f)

Enter the same date and time in the Actual Event Date and Actual Event Time fields as you see in the Planned Event Date/Time field in the Event Handler List. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field

g)

Choose Send.

h)

Close the Window. Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click Page Down until you see the Arrival at Customer event. Verify that your actual date is present. You will see the update immediately in the Web Interface.

i)

Do not close the Window. You will now report the unloading event.

13. Report a transportation delay using the Web Interface. Enter Carrier’s Delivery as the tracking scenario. Enter the shipment number, and choose Apply.


2010


79


SCM663

Check in the Event Handler List if the event is posted. a)

Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click on Report All Expected Events.

b)

Select the Unloading record and enter the same date, time and time zone in the Actual Event Date and Actual Event Time fields as you see in the Planned Event Date/Time field. You must also select a valid Reason Code. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field.

c)

Choose Send. Close the window. You will see the update immediately in the Web Interface.

d)

Do not log off. You will now report the customer’s proof of delivery event.

14. Customer Role Report the proof of delivery using the Web Interface. To change to the Customer role, select the tracking scenario to Customer's Delivery. Enter your purchase order number (field is case sensitive) and choose Search. Click on Send Event Messages and select Report Proof of Delivery.


80


2010

SCM663


In the dialog box that appears, note the date and time. Choose Send. a)

Change the tracking scenario to Customer's Delivery.

b)

Enter the sales order number of the sales order created in Unit 2 in the Sales Order Number field.

c)

Choose Apply.

d)

Click on Send Event Messages and select Report Proof of Delivery. The Report Proof of Delivery screen should appear.

e)

In the Report Proof of Delivery screen, enter the same date and time in the Actual Event Date and Actual Event Time fields as you see in the Planned Event Date/Time field in the Event Handler List. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field.

f)

Choose Send.

g)

Close the Window. Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click Page Down until you see the Proof of Delivery event. Verify that your actual date is present. You will see the update immediately in the Web Interface.

h)


15. Verify that the proof of delivery was sent to your event handler. Go back to the session with the Event Handler List and view how the event handler has been updated. Did the expected events change? ________________________ Are there any new event messages? ________________________ What is the status:

Delivery Status:

____________________


____________________

Did either of them change? ________________________

2010

a)


b)


c)

Choose Refresh. It’s the first icon on the left.

d)


e)


f)



81


SCM663

Lesson Summary You should now be able to: • Explain the purpose of an actual event • Explain the different possibilities for reporting events

82


2010

SCM663

Lesson: Reaction to an Event

Lesson: Reaction to an Event Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain the options that a company has to respond to an event

Business Example The event notification will trigger actions in your company. You have defined some actions as automatic and others requiring manual intervention.

Figure 59: Follow-up Activities – Architectural Landscape

At this point in the architectural landscape, we are now concerned with what comes out of SAP Event Management for triggering follow-up activities to another SAP or legacy system.

2010


83


SCM663

Figure 60: Triggering Follow-up Activities

When a message is received or if a message is not reported to SAP Event Management in a specified period, SAP Event Management applies a rule set to that event to see what, if any, follow-up task should occur. SAP Event Management coordinates the reactions to the message or lack of message and triggers the alert or notification of the event or non-event. If necessary, SAP Event Management will call a subsequent function. SAP Event Management supplies the appropriate information to SAP BI for performance measurement. For example, in our demo scenario at the end of the process, the customer posts a confirmation POD. If that POD isnt received when its expected, we still need to invoice the customer so we could set it up such that if the event is not received within a specified time frame, SAP Event Management causes the billing process to start anyway, either by sending a message to a user or actually doing the billing.

Figure 61: Usage of the Alert Framework – Example

84


2010

SCM663


It is possible to link SAP Event Management to the Alert Framework. The Alert Framework may be a stand-alone SAP system, available in a Web Application Server. Here we have different possibilities to notify people, for example, via e-mail, text messaging (sms), publish and subscribe (where you can be notified for specific instances via the Alert Framework). To define the Alert Framework connection, in the SAP SCM IMG, choose Event Management → Reactions to Event Messages → Define Alert Framework Connection.

Figure 62: Connection to SAP APO Alert Monitor

In addition to the Alert Framework possibility, SAP Event Management can also send TPVS and PP/DS messages to the APO Alert Monitor.

2010


85


SCM663

Figure 63: Webflow Triggering – Example

It is also possible to trigger workflow activities from SAP Event Management to any workflow system.

Figure 64: Rule Set for Event Processing

The event handler checks a rule set, which contains a condition and a branch destination. The condition could be a Boolean expression or a plug-in function module. If the condition is true or false or it produces an error, then you can cause another rule to be evaluated. If no value is specified, the next rule in the rule set is performed. Within the task, you can have a specific multitask activity, which itself includes one or more function modules or event handler methods. An event handler method can update the event handler based on a function.

86


2010

SCM663


Figure 65: Rule Sets

Rule sets contain rules that are used to determine what needs to happen next. Because this event has happened, something else now needs to happen. To define rule sets, in the SAP SCM IMG, choose Event Management → Reactions to Event Messages → Define Rule Sets.

2010


87


SCM663

Lesson Summary You should now be able to: • Explain the options that a company has to respond to an event

88


2010

SCM663

Unit Summary

Unit Summary You should now be able to: • Display the different possibilities for status retrieval • Explain the purpose of an actual event • Explain the different possibilities for reporting events • Explain the options that a company has to respond to an event

2010


89

Unit Summary

90

SCM663


2010

Unit 4 Monitoring and Analysis Unit Overview

Unit Objectives After completing this unit, you will be able to: •

Explain the existing monitoring options within SAP Event Management, and how SAP Event Management and SAP Business Intelligence provide analytical information

Unit Contents Lesson: Monitoring and Analysis .............................................. 92

2010


91

Unit 4: Monitoring and Analysis

SCM663

Lesson: Monitoring and Analysis Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain the existing monitoring options within SAP Event Management, and how SAP Event Management and SAP Business Intelligence provide analytical information

Business Example You have requirements to monitor SAP Event Management activities on a daily basis, and analyze key performance indicators tied to your business processes on a long-term, strategic basis.

Figure 66: Monitoring and Reporting – Architectural Landscape

Now let's look at the system and data flow for monitoring and reporting. Daily operational monitoring occurs in SAP Event Management, and can also occur in the SAP application system.

92


2010

SCM663

Lesson: Monitoring and Analysis

Analytical reporting occurs in BI. Key performance indicators (KPIs) and collaborative performance indicators (CPIs) are updated by activities in SAP Event Management. It may be preferable to use SAP Event Management data instead of SAP ERP or Legacy system transactional data to update a KPI or CPI. An example would be if you measured vendor performance to a close tolerance in hours in a just-in-time environment. A delivery reported via an onboard device in a truck could provide more accurate real-time information than a goods receipt transaction, which may be logged at the end of a shift.

Figure 67: Expected Events Monitor and Overdue Event List

If an expected event has exceeded the date, the status is changed to overdue and the expected event monitor procedure is executed. To access the Expected Event Monitor in SAP SCM/EM, from the SAP Easy Access menu, choose Event Management → Administration → Processing Control → Expected Events Monitor. The transaction code is /SAPTRX/EE_MON. To access the Overdue Event List in SAP SCM/EM, from the SAP Easy Access menu, choose Event Management → Monitoring and Lists → Expected Event Overdue List. The transaction code is /SAPTRX/EE_OVD_LIST.

2010


93


SCM663

Figure 68: Event Handler List

The Event Handler List provides details about an event handler. The status of events, event and error messages and status details are all contained within the Event Handler List. To access the Event Handler List in SAP SCM/EM, from the SAP Easy Access menu, choose Event Management → Monitoring and Lists → Event Handler List. The transaction code is /SAPTRX/EH_LIST.

Figure 69: Event Message Processing Status List

94


2010

SCM663


The Event Message Processing Status List is used to check large uploads of EDI transactions. Green, yellow, and red indicators allow you to look at system-generated messages pointing to whether objects are processing correctly in SAP Event Management. These indicators reflect data errors, not business process issues. • • •

Green indicates that everything is OK. Yellow indicates that data is OK, but no event handler exists. Red indicates invalid data.

To access the Event Message Processing Status List in SAP SCM/EM, from the SAP Easy Access menu, choose Event Management → Monitoring and Lists → Event Message Processing Status List. The transaction code is /SAPTRX/EVM_STATUS.

Figure 70: Event Message Processing Error List

To access the Event Message Processing Error List in SAP SCM/EM, from the SAP Easy Access menu, choose Event Management → Monitoring and Lists → Event Message Processing Error List. The transaction code is /SAPTRX/ER_MS_LIST. This transaction is not in the SAP menu in SCM 5.0.

2010


95


SCM663

Figure 71: Monitoring Using iViews

It is also possible to monitor the process using iViews, which are part of the SAP Portal application.

Figure 72: iViews for SAP EM – Overview Architecture

From the user perspective, the iView is a miniapp that appears through a portal. The user logs on via a portal and the portal server communicates directly with SAP Event Management.

96


2010

SCM663


Figure 73: Integration with Document Flow

A net is built up to show which business objects are used in an SAP Event Management scenario. This leads to a hierarchical view of the whole scenario.

Figure 74: Supply Chain Operations Reference (SCOR) Model Processes

2010


97


SCM663

This generic illustration explains the Supply Chain Operations Reference Model process, which is referred to as SCOR. The SCOR level 3 process is a generic, industry-wide process defined by the Supply Chain Council. This example shows the delivery of a stocked product. There are similar processes for all planning, sourcing, manufacturing, delivery and return processes. Each process contains KPI metrics that are used for benchmarking purposes. Various SAP documents might correspond to elements in the SCOR level 3 process, and are also used for calculating KPIs. The event would also correlate to SCOR level 3 processes and metrics, but only key milestones. In the example in the illustration, some of the data used for calculating the KPI for perfect order fulfillment would come from the SAP R/3 system, but the carrier unloading event would provide the final data for the perfect order fulfillment KPI. This may have been decided to ensure that the data reported is truly real time, and not entered into the system hours after the truck was unloaded and left the dock. The end result is a more accurate KPI. The difference between KPIs and CPIs is that KPIs are industry metrics. CPIs or collaborative performance indicators are metrics that are defined between the collaborating companies.

Figure 75: Extracting Data for Upload to SAP BI

98


2010

SCM663


Data is extracted from SAP Event Management to SAP Business Intelligence according to a configured profile in SAP Event Management. When a user requests such a report, they are interacting with the SAP BI system.

2010


99


SCM663

Lesson Summary You should now be able to: • Explain the existing monitoring options within SAP Event Management, and how SAP Event Management and SAP Business Intelligence provide analytical information

100


2010

SCM663

Unit Summary

Unit Summary You should now be able to: • Explain the existing monitoring options within SAP Event Management, and how SAP Event Management and SAP Business Intelligence provide analytical information

2010


101

Unit Summary

102

SCM663


2010

Unit 5 Visibility Processes Unit Overview


Define the purpose of a visibility process Explain why SAP delivers preconfigured visibility processes with the mySAP Business Suite

Unit Contents Lesson: Visibility Processes ...................................................104

2010


103

Unit 5: Visibility Processes

SCM663

Lesson: Visibility Processes Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • •

Define the purpose of a visibility process Explain why SAP delivers preconfigured visibility processes with the mySAP Business Suite

Business Example You want to implement SAP Event Management using a preconfigured visibility process.


A visibility process consists of a preconfigured template to support a business process. To implement SAP Event Management, configuration has to be done in the SAP application system and in SAP Event Management. Visibility processes are delivered with standard configuration in both of these systems as well as the necessary extraction to support reporting in SAP Business Intelligence. The visibility process also includes the communication layer to support the Web processes.

104


2010

SCM663

Lesson: Visibility Processes

Figure 77: Visibility Process – Definition

A visibility scenario describes one complete business process. A visibility process describes a part of a business scenario. Multiple business processes can make one business scenario. Each business process contains the configuration settings for that business process. Business processes can be combined or enhanced within a project to make a complete business scenario.

Figure 78: Visibility Scenario Example

Here is an example of building one business scenario from existing processes. In this illustration, you can see how you can build a complete business process using existing processes as building blocks. You can enhance the delivered processes to include events that are not provided for within a delivered process.

2010


105


SCM663

Figure 79: Components of Visibility Processes

Every visibility process is delivered with a standard set of components including documentation and scenario-specific setup in both the SAP application system and SAP Event Management. Also included is the standard data extraction required for SAP Business Intelligence.

Figure 80: Visibility Processes in SAP Event Management

These are the standard visibility processes that are delivered with SAP EM 7.0.

106


2010

SCM663


Figure 81: Fulfillment Visibility

The Fulfillment Visibility process is also known as the Deliveries in LTL Shipment. In configuration, you see this as LTL_DELIV. This process describes the visibility along the fulfillment process from warehouse events through proof of delivery from the customer. The Fulfillment Visibility process monitors the delivery process and provides active tracking of the delivery for the customer. Events are reported from within the company as well as by business partners. Follow-up activities are triggered in the form of e-mails to the customer in case there is a delay. And SAP BI is updated so the business process can be analyzed.

Figure 82: Process for Procurement

2010


107


SCM663

The procurement process begins when a purchase order is created either from a requisition or without reference to any document. The purchase order is sent to the supplier and the supplier acknowledges whether they can fulfill the requirement. If the supplier cannot fulfill the requirement, an alert is sent to the buyer. When production is complete, the supplier creates an advanced shipping notification. It is possible to connect the Transportation Visibility or part of the Fulfillment Visibility process to track the carrier delivery. Events are also tracked through goods receipt, invoice and payment. The final step is the download of the data to SAP BI for analysis.

Figure 83: Planned Shipment Route, Carriers, and Customers

In this chart you can see the detailed steps that are defined as events in the fulfillment visibility scenario: from the arrival of the carrier to pick up the goods to the point of final destination. Each step along the way is visible to anyone who requires and has access to that information.

108


2010

SCM663


Figure 84: Analytics for Fulfillment Visibility

This shows an example of SAP BI Business Content as of SAP BI 3.1 that is related to the Fulfillment Visibility process. The business content can be used for more than the outbound fulfillment scenario. Benefits of integrating SAP Event Management with SAP BI are as follows: • •

Ability to evaluate the performance of processes that span the entire supply chain with no limitation to R/3 objects. Ability to obtain precise data because the source data is not limited to one particular system. Events can be reported through almost any device such as the Internet, telephone, an SAP system, or a third-party system.

Figure 85: Transportation Visibility

The Transportation Visibility process is similar to the Fulfillment Visibility process but concentrates solely on the transportation piece for international inbound and outbound shipments. The Transportation Visibility process covers international sea shipments including customs and road transportation. This visibility process also deals with complex transportation networks using transportation chains.

2010


109


SCM663

Figure 86: Example for International Sea Shipment

Here you see an example of the Transportation Visibility process showing the multiple legs in a transportation process.

110


2010

SCM663


Figure 87: Analytics for Transportation Visibility

Figure 88: Production Malfunction Visibility

The Production Malfunction Visibility process is used in production when the manufacturing process is interrupted due to a breakdown. This process covers events from the release of the manufacturing order through the goods receipt, closing the gap between planning and execution by notifying the planner in the event of a work center breakdown. This process includes production and plant maintenance-related information.

2010


111


SCM663

Figure 89: Production Malfunction Process

The Production Malfunction Visibility process begins when there is a machine breakdown within the production line. An alert is sent to SAP APO so a planner may then react to the situation by adjusting the schedule or using an alternate work center. The maintenance technician takes the notification in process and follows the necessary steps to resolve the problem.

Figure 90: Analytics for Production Malfunction Visibility

112


2010

SCM663


Figure 91: Procurement Visibility

The Procurement Visibility process covers events from purchase order creation through payment, including order acknowledgement, shipping notifications, goods receipt and invoice functions.

Figure 92: Process for Procurement

The procurement process begins when a purchase order is created either from a requisition or without reference to any document. The purchase order is sent to the supplier and the supplier acknowledges whether they can fulfill the requirement. If the supplier cannot fulfill the requirement, an alert is sent to the buyer. When production is complete, the supplier creates an advanced shipping notification. It is possible to connect the Transportation Visibility or part of the Fulfillment Visibility process to track the carrier delivery. Events are also tracked through goods receipt, invoice and payment. The final step is the download of the data to SAP BI for analysis.

2010


113


SCM663

Figure 93: Analytics for Procurement Visibility

Figure 94: RFID-Enabled Outbound and Inbound Visibility

The outbound and inbound visibility process aims to provide visibility across the entire delivery processing process, from the time an outbound delivery is created until the customer posts proof of delivery for his or her inbound delivery.

114


2010

SCM663


RFID-enabled outbound and inbound processing provides a generic solution to different industries. The SAP Auto-ID Infrastructure (AII) development enhances the efficiency and quality of outbound and inbound processing operations by enabling the following: • •

•

•

Automated hands-free goods issue/loading confirmation Verification of the items for which goods issue has been performed with the fulfillment requirements stipulated by the backend system in the form of a delivery document thus presenting a real-time quality control function over items issued at source Near instantaneous communication, at the EPC or electronic product code level, of pallet and case level information about goods issued to business partners and enterprise backend systems In conjunction with SAP Event Management, RFID-enabled outbound and inbound processing allows visibility at delivery and handling unit level both inside the company and between business partners such as supplier and customer.

Figure 95: RFID-Enabled Outbound/Inbound Visibility Process

2010


115


SCM663

Figure 96: Outbound/Inbound Delivery Process – Example

Outbound processing prepares goods for shipment to their destination and includes the following activities: • • • • • •

• •

Creating outbound deliveries Creating picking orders Picking activity Packing activity – This activity can be optionally enhanced by adding pallet and case level EPC information with the help of SAP Auto-ID Infrastructure. Staging Loading – This activity is enhanced through automated loading confirmation that can be performed after capturing the pallet and case level EPC information when passing the EPCs through an RFID scanning gate. Goods issue posting Sending advanced shipping notifications (ASNs) to business partners

Inbound processing covers the resulting receipt steps: • • • •

116

Creating inbound deliveries Unloading Goods receipt posting Sending a proof of delivery (POD) to the supplier


2010

SCM663


Figure 97: RFID-Enabled Outbound/Inbound Visibility – Detailed Overview

This illustration shows the different incidents that happen in the SAP ERP Central Component (ECC) or SAP Auto-ID Infrastructure system. If such an incident occurs, a relevant event message is sent to SAP Event Management.

Figure 98: Monitoring the Delivery Process

Different statuses are available for the monitoring process. Each status can have different values to get a quick overview of the whole process.

2010


117


SCM663

Figure 99: RFID-Enabled Returnable Transport Items Visibility

Returnable transport items (RTI) include plastic crates, pallets and roll containers, and industry-specific special transport items varying in size and value that are reused. These might circulate between specific locations or might be managed by a common RTI pool entity. Moreover, RTIs might move purely within the boundaries of a single physical site or between the locations of a larger individual site, or they might be exchanged or circulated between different locations across business partners or within one business entity. They might also circulate within a larger multicompany supply chain community with an RTI pool owner tracking their assets. This visibility process aims to enable the tracking of RTI cycles in locations across business partners.

118


2010

SCM663


Figure 100: RFID-Enabled Returnable Transport Items Visibility Process

GRAI stands for Global Returnable Asset Identifier.

Figure 101: Returnable Transport Items Process – Overview

2010


119


SCM663

This illustration shows an example of a returnable transport items process. The following event sequence describes a cycle: • • • • • • •

Pack (supplier) Load (supplier) Unload (OEM) Unpack all or specific child objects (OEM) Load (OEM) Unload (supplier) Confirm return (supplier)

At both the supplier site and the original equipment manufacturer (OEM), additional movement events are possible. This means that an RTI is simply taken to a different sublocation.

Figure 102: Seasonal Procurement Visibility Process

Seasonal procurement is a retail-specific process that requires the Seasonal Procurement Add-On. It comes with a tight integration with the retail procurement controlling workbench.

120


2010

SCM663


Figure 103: Example: Procurement Process Tracking

The Seasonal Procurement Visibility process looks at a purchasing process including transportation events, starting with the creation of a purchase order until the goods receipt at the customer.

Figure 104: Railcar Management - Tracking + Onsite Event Management (OSEM)

2010


121


SCM663

Figure 105: Visibility Processes: Integration with SAP TM

Figure 106: Interaction of SAP TM and SAP EM

122


2010

SCM663


Figure 107: SAP EM Access in SAP TM Application

Figure 108: SAP EM Web Access out of SAP TM Application

2010


123


SCM663

Figure 109: SAP EM Web Access – Selection Depending on Role and Scenario

Figure 110: Order Taking Visibility Process

Figure 111: Transportation Execution Visibility Process

124


2010

SCM663


Figure 112: Resource Visibility Process

Figure 113: Tendering Visibility Process

Figure 114: Visibility Processes: Integration with SAP SNC

2010


125


SCM663

Figure 115: Supply Network Visibility Processes: Purchase Order Collaboration

Figure 116: Supply Network Visibility Processes

126


2010

SCM663


Figure 117: Supply Network Visibility Processes: Responsive Replenishment


2010


127


SCM663


128


2010

SCM663


Lesson Summary You should now be able to: • Define the purpose of a visibility process • Explain why SAP delivers preconfigured visibility processes with the mySAP Business Suite

2010


129

Unit Summary

SCM663

Unit Summary You should now be able to: • Define the purpose of a visibility process • Explain why SAP delivers preconfigured visibility processes with the mySAP Business Suite

130


2010

Unit 6 Configuring the Application System Unit Overview

Unit Objectives After completing this unit, you will be able to: • • • • •

Configure the connection from an SAP application system to SAP Event Management Configure the system for relevance determination Create a list of expected events, parameters and tracking IDs Explain how the generic application interface works

Unit Contents Lesson: Configuring the Application System ................................132 Exercise 3: Configuring the Creation of Expected Events in the Application System .........................................................153 Lesson: Configure Drilldown into Application Object.......................173 Lesson: Generic Application Interface .......................................175

2010


131

Unit 6: Configuring the Application System

SCM663

Lesson: Configuring the Application System Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • • •

Configure the connection from an SAP application system to SAP Event Management Configure the system for relevance determination Create a list of expected events, parameters and tracking IDs

Business Example • •

You need to determine the milestones you wish to track and configure the system to support this. Where does my planned data come from?

Figure 120: Examining the Business Process (1/2)

Figure 121: Examining the Business Process (2/2)

132


2010

SCM663

Lesson: Configuring the Application System

Figure 122: Connecting SAP Systems - Architectural Landscape

Now in the architectural landscape we look at which parts of the landscape come into play for creating event handlers. At this point the legacy or other SAP system determines whether or not an event handler is created, and then the event handler is created in SAP Event Management. Then within SAP Event Management, the list of expected events is determined together with the expected dates and times of those events.

2010


133


SCM663

Figure 123: Application Objects: Examples

Examples of application objects are shipment, delivery, handling unit of delivery, or equipment. The application object type defines this character. You may, for example, distinguish between standard euro pallets and special pallets for shipping larger items and define different application object types for it.

Figure 124: Extracting Relevant Data from an SAP Application System

134


2010

SCM663


Your business process first determines whether or not an event handler is created. Because you are processing documents in your application system, there is a check to see if an event handler should be created for that particular function. Data is gathered in the application system specific to the business process and configuration that you have defined to control the event process itself. Then, the event handler is created in SAP Event Management.

Figure 125: Application Object Type - Definition

The application object type determines whether an object is relevant for SAP Event Management. If the object is relevant, then the application object type determines which data is sent over and when the data is sent, but the event handler is actually created in SAP Event Management. In the visibility scenario, you've seen the example for the Deliveries in LTL Shipment. In this scenario, an application object type is defined for the delivery. When the shipment is saved, the application object type tells what data to extract from the SAP ERP system to use for creating the event handler. Data is extracted for each delivery in the shipment.

2010


135


SCM663

Figure 126: Relation Between Application Object Type Instance and Event Handler

Figure 127: Customizing an Application Object Type

This illustration shows what you need to configure in the application system. The relevance condition tells whether or not the business object is relevant for an event handler to be created. The expected events function is used to set up the expected events or milestones for an application object.

136


2010

SCM663


Other functions can be set up to determine the control and info parameters for an application object. The tracking ID can be determined from a field or a function. The query ID is derived from a function. Object identification has two types of tables: the main table and the master table. The main table describes the actual application object, whereas the master table provides further contextual information for the application object. The business object key assembles a key for the business object from the business objects component fields. The business object might be used later to tell which event handlers were created for a business object.

Figure 128: Expected Events

2010


137


SCM663

Figure 129: Selecting Expected Events

As an example, the list that you see in the application system is taken from the planning data in the shipment using transaction VT02N OR VT03N and extracted using a program or function in the application system That list is passed to SAP Event Management where the profile is applied, and then the final list of expected events appears in the Event Handler List in SAP Event Management, with the expected dates and times.

Figure 130: Customizing Selection of Expected Events

138


2010

SCM663


The Generate From field in SAP Event Management defines the program in the application system that will determine the events to be included. To access the Expected Event Profile in customizing, follow these steps: •

• • •

In the SCM or EM IGM, choose Event Management → Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events. Select your Expected Event Profile and double-click on Update Profile Group. Select your Profile Group and double-click on Update Profile Item. Select your Profile Item and choose Details.

Figure 131: Assigning Expected Events Extractor to Application Object Type

These screenshots show where the Extractor function is written in the upper view using transaction /SAPTRX/ASC0TF and where it is applied to the application object type in the lower screen using transaction /SAPTRX/ASC0AO.

2010


139


SCM663

Figure 132: Selecting Parameters

Transaction /SAPTRX/ASC0TF can be used to access the application system programs that are used to extract the parameters. These parameters are mapped in the SAP Event Management using transaction /SAPTRX/SAPLPARDICT.

Figure 133: Customizing Selection of Parameters

These screenshots show the relationship between the SAP ERP application system program and the parameter mapping in SAP Event Management.

140


2010

SCM663


Figure 134: Assigning Parameter Extractors to AOT

This screenshot shows how you relate the functions for parameter extraction using transaction /SAPTRX/ASC0TF with the application object type using transaction /SAPTRX/ASC0AO.

Figure 135: Generating F4 Help for Expected Events and Parameters (1/2)

If you want to have F4 Help between the application system and SAP Event Management when you are doing configuration, you must first set the BPT process mode to Maintenance. This means no event handlers will be created at the moment.

2010


141


SCM663

In maintenance mode, when you save a document, for example, a shipment, in the application system, the list of expected events and parameters will be displayed. You can show this by switching to maintenance mode, then making a change to an existing shipment. When you save your entries, the system will display the expected events and parameters.

Figure 136: Generating F4 Help for Expected Events and Parameters (2/2)

It is also possible for F4 Help to be active between the two systems so that when you are in SAP Event Management and you press F4, you can get the table help from the application system. These screenshots show an example of using F4 help in SAP Event Management, and configuring it in SAP Event Management.

142


2010

SCM663


Figure 137: Selecting Tracking IDs

Identifying the tracking ID in the ERP application system can be done with simple customizing or by using a function module. The query IDs are derived from a function module. The screenshot on the right shows the Detail View from an Event Handler List. The tracking ID value is a direct takeover from the application system to SAP Event Management.

Figure 138: Customizing of Tracking IDs

2010


143


SCM663

This screenshot shows the tracking ID configuration in transaction /SAPTRX/ASC0AO. If the tracking ID method indicates the ID is determined by a field, then this customizing is sufficient.

Figure 139: Defining Extractors for Tracking and Query IDs

These screenshots show the association of the query ID extraction function in transaction /SAPTRX/ASC0TF with the application object type in transaction /SAPTRX/ASC0AO.

Figure 140: Business Object Key

144


2010

SCM663


Transaction /SAPTRX/ASEHVIEW is not in the SAP Menu structure.

Figure 141: Defining Extractor for Business Object Key

In the upper screenshot, you define the business object key extractor using transaction /SAPTRX/ASC0TF. In the lower screenshot, you assign that function to the application object type using transaction /SAPTRX/ASC0AO.

Figure 142: Relevance

2010


145


SCM663

You define the relevance in the application object type. Although many sales orders are being processed, you may not want to create event handlers for all of them. Maybe you want to create an event handler only if the route is from Europe to USA or the sub-contractor is 4563 or based on the internal quality process. You define in the application object type when the business object is relevant for SAP Event Management. In the exercise for this unit, you use shipment type 0002 for Collective Shipment – Road and the overall status “Planned.” Now you want to add the Shipping Conditions field. If this field is equal to your group number, then you will create an event handler.

Figure 143: Relevance Determination

Relevance can be determined either with a Boolean expression for a condition such as shipment type 0002 or with an interface function in SAP Event Management. If your decision for creating the event handler cannot be determined with the condition statement, then you can insert a function. Transaction /SAPTRX/ASC0AO is used for the application object type.

146


2010

SCM663


Figure 144: Condition Editor for AOT Relevance Conditions

This is a screenshot of the condition editor, inserted here for your reference. The SAP application system transaction is /SAPTRX/ASC0TC.

Figure 145: Business Process Types

When defining the business process type in the SAP Event Management, you specify the objects or business processes from the application system that are assigned to an event handler in the SAP Event Management and for which events should be processed.

2010


147


SCM663

The business process type must be identical in both the application system and the SAP Event Management. Transaction in the SAP ERP application system is /SAPTRX/ASC0TO. To access the Business Process Type table, in the SCM/EM IMG, choose Event Management → General Settings → Define Business Process Type.

Figure 146: Relationship Between BPT and AOT

The application object type is associated with the business process type. Many application object types can exist for one business process type. In the SAP application system, you assign the application object type to the business process type in transaction /SAPTRX/ASC0TO.

148


2010

SCM663


Figure 147: Creating Event Handlers with Conditions - Example

This is an example where the event handlers are created in SAP Event Management when the conditions are met in the application system. In this example, many objects are related to one shipment. It is possible for each object to create an event handler in SAP Event Management.

Figure 148: Customizing of Business Process Types

SAP delivers predefined business process types (BPTs), and it is possible to create new ones. Business process types are cross-client.

2010


149


SCM663

When a shipment is saved, a BADI identifies the business process type, which is passed to SAP Event Management and has to match with the business process type on that side. The table structures are filled in by BADI.

Figure 149: Main and Master Tables

Main and master tables are used to build IDs and parameter data. The main table represents the application object, for example, the shipment. The main table has the data required for creating the shipment. The master table contains additional information. Example of data in a main table about a shipment: • • •

Delivery 1 → EH1 Delivery 2 → EH2 Delivery 3... → EH...

The structure is built during the execution of the application object that is relevant for SAP Event Management.

150


2010

SCM663


Figure 150: Special Fields of an Application Object Type

Additional fields can be maintained in the application object type. Go to the General data tab in transaction /SAPTRX/ASC0AO and look at the fields in the Behavior box. • • •

• • •

2010

Relevance of AO: Indicates that an application object is relevant for SAP Event Management. Appl.Object Relevant for Queries: Indicates that the application object is used to retrieve status information from an event handler. Stop AO Determination: Indicates that application object determination does not continue for an application object if one application object type was determined as event management relevant for this application object. All other application object types for this application object are not determined. EH Deactivation Ind.: Indicates that an event handler for an application object is deleted (set indicator) if the application object is no longer relevant. Alt.BusProcType: Describes the type of business process or object that an event handler is referenced to. Error Mode: Defines the system behavior if errors occur during relevance determination.


151


SCM663

Figure 151: Process of Creating or Changing Event Handlers

Here we see the process of the application system whether an object in the application system is being changed or created. When the object is saved, the system checks the business process type and gets the application object type. The application object type indicates the relevance for that object. If that object is relevant, then the control parameters are built for all relevant application objects. A check is then made in SAP Event Management to see if the event handler already exists or if it needs to be created.

152


2010

SCM663


Exercise 3: Configuring the Creation of Expected Events in the Application System Exercise Objectives After completing this exercise, you will be able to: • Configure the ECC application system to create an event handler in the SAP Event Management system • Create a new parameter profile

Business Example In your business, when you ship product with the shipping condition = SS, where SS = 50 + ## in the ECC application system, you want to create an event handler for tracking the milestones that you have configured in SAP Event Management. In this exercise, we will configure the SAP ECC system so that an event handler is created when those conditions are met.

Task 1: Define the business process types. 1.

The business process type (BPT) determines the data that can be used in a business process. In our training example, the business process type ESC_SHIPMT is assigned to the business process SHIPMENT and is determined when the shipment is saved. The business process type is already configured, but you can look at it in the SAP ECC application system. In your ECC system, review the configuration of business process type ESC_SHIPMT and the available application tables.

Task 2: Define the application object type. The application object type (AOT) determines whether a business process is relevant for SAP Event Management, which means whether or not an event handler will be created for the process. The data to be extracted for creating the expected events, parameters, tracking IDs, and query IDs is also defined by the application object type. In this exercise, we will create a new application object type. 1.

Select business process type ESC_SHIPMT, then create a new application object type, Z##_LTL_DELIV by copying the LTL_DELIV application object type. Continued on next page

2010


153


SCM663

2.

Make sure that the flag EM Relevance of Appl. Obj. on the General tab is set.

3.

In the “Define EM Relevance Conditions” table, create the relevance conditions that determine when an event handler is created. Name the condition Z##_EM_CONDITION. An event handler should be created when the following conditions exist: 1. Shipment type = 0002 2. Shipping Conditions code = SS, where SS = 50 + ## 3. The Overall Transportation Status is greater than or equal to 1.

4.

Assign your new relevance condition to the new application object type, Z##_LTL_DELIV, that you created within business process type ESC_SHIPMT.

Task 3: In Unit 2, “Creating Events”, we discussed control, system and info parameters, and in that exercise we looked at them in configuration. In this unit, we will define a new mapping profile and then define a new application object type. 1.

Although the control, info and system parameters already exist, we need to define parameter mapping. First we need to create a mapping profile in the SCM/EM Event manager configuration. Create mapping profile Z##_LTL_DELIV with the description Z## Mapping Profile.

2.

Select the mapping profile you just created, and select Control Parameter Mapping from the dialog structure and create a new entry in the table using the values below. In the Parameter field, use the F4 icon to enter the application system information: Application System App. Obj. Type

T90CLNT090 (or ECC server assigned to the class) Z##_LTL_DELIV

Mapping Source: Parameter

DELIVERY_PRIORITY

Mapping Target and Method: Parameter Type

Control Parameter

Parameter

DELIVERY_PRIORITY

Mapping Mode

Direct Value Takeover Continued on next page

154


2010

SCM663


Repeat this procedure for the following control parameters: SHIPMENT_TYPE SHIPPING_CONDITION SHIPPING_TYPE SHIP_TO_PARTY_EMAIL 3.

Change the Parameter Type field from control to system parameter and enter the following system parameters: CARRIER ROUTE SHIPPING_POINT

4.

Select Info Parameter Mapping from the dialog structure on the left and create new entries from the data below. In the Parameter field, use the F4 icon to enter the application system information: Application System App. Obj. Type



DELIVERY_NO


Select Info Parameter

Parameter

DELIVERY_NO

Mapping Mode

Select Direct Value Takeover

Repeat this procedure for the following info parameters: PLANT PLANT_NAME PO_NO ROUTE_DESCRIPTION SALES_ORDER_NO Continued on next page

2010


155


SCM663

SALES_REPRESENTATIVE SHIPMENT_NO SHIP_TO_PARTY_CITY SHIP_TO_PARTY_COUNTRY SHIP_TO_PARTY_NAME SHIP_TO_PARTY_REGION SHIP_TO_PARTY_STREET 5.

Assign your new profile to the mapping area by selecting Assign Profile to Mapping Area from the dialog structure on the left. Select the entries for application object type LTL_DELIV and leave Application System blank and choose Copy As. Change the application system to T90CLNT090 (or the ECC server assigned to the class) and the application object type and map profile to Z##_LTL_DELIV.

Task 4: Test your configuration. 1.


Entry

Order Type

OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-06-##



Material Number

P-102

Quantity Ordered

2

Sales Order Number: ___________________ 2.

Create a delivery note for your sales order. In the delivery, enter the pick deadline of today’s date + 2 business days and the picking time at 1:00 a.m. This will become the expected time for the Picking Begin event.


156


2010

SCM663


Field Name

Entry

Shipping Point

1000

Selection Date

2 weeks from today

Sales Order Number

From prior step

Pick Deadline


Picking Time

1:00 a.m.

Delivery Number _______________ 3.

Create a shipment for your pumps. The shipment will create an event handler and expected events in SAP Event Management. Use the following data in the shipment creation process. Field Name

Entry


1000

Shipment Type


Shipment Route

R00001

Shipping Condition

SS, where SS = 50 + ##

Planning Times

Date

Time

Check-In

Today + 2 Business Days

8:00

Loading Start


9:00

Loading End


10:00

When you save the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. 4.


Date Today + 2 Business Days Today + 2 Business Days

Time 11:00 22:00

When you save the shipment, these fields will be used to create the expected events Plant Departure and Customer Arrival. Shipment Number: ____________________ Continued on next page

2010


157


5.

SCM663

Verify that an event handler was created in SAP Event Management. Also, verify that the event handler was generated based on your new application object type. Log into the SAP SCM/Event Management system and run the Event Handler List and view the event handler that was created by the shipment in the prior step. Use event handler type LTL_DELIV. Enter your delivery number, including two leading zeros, in the Tracking ID field. Check the list of expected events. Are the changes to dates and times that you made in this exercise reflected in the list of expected events?

158


2010

SCM663


Solution 3: Configuring the Creation of Expected Events in the Application System Task 1: Define the business process types. 1.

The business process type (BPT) determines the data that can be used in a business process. In our training example, the business process type ESC_SHIPMT is assigned to the business process SHIPMENT and is determined when the shipment is saved. The business process type is already configured, but you can look at it in the SAP ECC application system. In your ECC system, review the configuration of business process type ESC_SHIPMT and the available application tables. a)

In the ECC system, use transaction SPRO or go to the IMG and choose SAP Reference IMG.

b)

Choose Integration with Other mySAP.com Components → Event Management Interface → Define Application Interface → Define Business Process Types Note: You can also use transaction code /N/SAPTRX/ASC0TO to navigate to the business process type table.

c)

Select ESC_SHIPMT.

d)

From the dialog structure on the left side, select Define Available Application Tables.

e)

After reviewing the table, choose Back until you return to the IMG.


2010


159


SCM663

Task 2: Define the application object type. The application object type (AOT) determines whether a business process is relevant for SAP Event Management, which means whether or not an event handler will be created for the process. The data to be extracted for creating the expected events, parameters, tracking IDs, and query IDs is also defined by the application object type. In this exercise, we will create a new application object type. 1.

Select business process type ESC_SHIPMT, then create a new application object type, Z##_LTL_DELIV by copying the LTL_DELIV application object type. a)

In the SAP Application System IMG navigate to: Integration with Other mySAP.com Components → Event Management Interface → Define Application Interface → Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types Note: As an alternative, you can use transaction /n/SAPTRX/ASC0AO to navigate to this table.

b)

Select business process type ESC_SHIPMT and then select Define Application Object Types from the dialog structure.

c)

Select LTL_DELIV, then choose Copy as and then overwrite the Define Application Object Types field with your new application object type, Z##_LTL_DELIV. Change the description to Gr## Deliveries in LTL Shipment.

2.

3.

Make sure that the flag EM Relevance of Appl. Obj. on the General tab is set. a)

Choose Enter then Save.

b)

Choose Exit.

In the “Define EM Relevance Conditions” table, create the relevance conditions that determine when an event handler is created. Name the condition Z##_EM_CONDITION. An event handler should be created when the following conditions exist: 1. Shipment type = 0002 2. Shipping Conditions code = SS, where SS = 50 + ## 3. The Overall Transportation Status is greater than or equal to 1.


160


2010

SCM663


a)

In the SAP application system IMG, navigate to: Integration with Other mySAP.com Components → Event Management Interface → Define Application Interface → Define SAP EM Relevance Conditions Note: You can also use transaction code /N/SAPTRX/ASC0TC to navigate to this table.

b)

Choose New Entries and make the following entries: Field Name

Entry

Condition

Z##_EM_CONDITION

Main Table

VTTPVB

Master Tab

VTTKVB

Description

Shpmt Type “0002”,Overall Status>=Planned, ShpCond= SS, where SS = (50 + ##).

c)

Choose Enter.

d)

Choose Save.

e)

Select the line with the condition you just entered.

f)

Choose the Condition Editor icon. The system will display the Change Condition:Z##_EM_CONDITION screen.

g)

In the Expression 1 box, find the VTTKVB-Shipment type field and double-click.

h)

In the Constant field, enter 0002 and choose Enter.

i)

From the Operators box, select =.

j)

From the Logic box, choose And.

k)

In the Expression 1 box, find the VTTKVB-Overall status field and double-click.

l)

In the Constant field, enter 1 and choose Enter.

m)

From the Operators box, select the >= symbol for greater or equal.

n)

From the Logic box, choose And.

o)

In the Expression 1 box, find the VTTKVB-Shipping cond field and double-click.

p)

In the Constant field, enter SS, where SS = 50 + ##. Choose Enter.

q)

From the Operators box, select =.


2010


161


4.

SCM663

r)

Click Transfer condition. It’s the green check mark at the bottom of the Change Condition: Z##_EM_Condition screen.

s)

Choose Save.

t)

Choose Exit.

Assign your new relevance condition to the new application object type, Z##_LTL_DELIV, that you created within business process type ESC_SHIPMT. a)

In the SAP application system IMG, navigate to: Integration with Other mySAP.com Components → Event Management Interface → Define Application Interface → Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types Note: As an alternative, you can use transaction /N/SAPTRX/ASC0AO to navigate to this table.

b)

Select business process type ESC_SHIPMT and then select Define Application Object Types from the dialog structure.

c)

Select your application object type, Z##_LTL_DELIV. Then choose Details.

d)

Select the Event Mgmt. Relevance tab. Overtype the EM Rel. Condition field with your relevance condition, Z##_EM_CONDITION.

e)

Choose Save.

f)

Choose Exit.

Task 3: In Unit 2, “Creating Events”, we discussed control, system and info parameters, and in that exercise we looked at them in configuration. In this unit, we will define a new mapping profile and then define a new application object type. 1.

Although the control, info and system parameters already exist, we need to define parameter mapping. First we need to create a mapping profile in the SCM/EM Event manager configuration. Create mapping profile Z##_LTL_DELIV with the description Z## Mapping Profile. a)

In the SCM/EM IMG, choose Event Management → Event Handlers and Event Handler Data → Parameters → Define Parameter Mapping

b)

Choose New Entries.

c)

Enter the fields from the table above. Choose Enter.

d)

Choose Save. Continued on next page

162


2010

SCM663


2.

Select the mapping profile you just created, and select Control Parameter Mapping from the dialog structure and create a new entry in the table using the values below. In the Parameter field, use the F4 icon to enter the application system information: Application System App. Obj. Type



DELIVERY_PRIORITY


Control Parameter

Parameter

DELIVERY_PRIORITY

Mapping Mode

Direct Value Takeover

Repeat this procedure for the following control parameters:


2010


163


SCM663

SHIPMENT_TYPE SHIPPING_CONDITION SHIPPING_TYPE SHIP_TO_PARTY_EMAIL a)

Choose New Entries.

b)

In the Mapping Source box, in the Parameter field, click F4. In the dialog box that appears, enter the following data: Application System

T90CLNT090 (or ECC server assigned to the class)

App. Obj. Type

Z##_LTL_DELIV

c)

Choose Continue.

d)

From the Application Control Parameters dialog box, select DELIVERY_PRIORITY.

e)

In the Mapping Target and Method box, do the following: Parameter Type

Select Control Parameter

Parameter

Enter DELIVERY_PRIORITY

Mapping Mode


f)

Choose Next Entry.

g)

After the last field is entered, choose Save.

h)

Repeat steps b) through g) for the following control parameters: SHIPMENT_TYPE SHIPPING_CONDITION SHIPPING_TYPE SHIP_TO_PARTY_EMAIL

3.

Change the Parameter Type field from control to system parameter and enter the following system parameters: CARRIER ROUTE Continued on next page

164


2010

SCM663


SHIPPING_POINT a)

Repeat steps 2. b) through g) for the following system parameters but change the Parameter Type from control to system parameter. CARRIER ROUTE SHIPPING_POINT

4.

Select Info Parameter Mapping from the dialog structure on the left and create new entries from the data below. In the Parameter field, use the F4 icon to enter the application system information: Application System App. Obj. Type



DELIVERY_NO


Select Info Parameter

Parameter

DELIVERY_NO

Mapping Mode


Repeat this procedure for the following info parameters: PLANT PLANT_NAME PO_NO ROUTE_DESCRIPTION SALES_ORDER_NO SALES_REPRESENTATIVE SHIPMENT_NO SHIP_TO_PARTY_CITY SHIP_TO_PARTY_COUNTRY SHIP_TO_PARTY_NAME SHIP_TO_PARTY_REGION Continued on next page

2010


165


SCM663

SHIP_TO_PARTY_STREET a)

Choose New Entries.

b)

In the Mapping Source box, in the Parameter field click the F4 icon. In the dialog box that appears, enter the following data: Application System

T90CLNT090 (or ECC server assigned to the class)

App. Obj. Type

Z##_LTL_DELIV

c)

Choose Continue.

d)

From the Application Control parameters dialog box, select DELIVERY_NO.

e)

In the Mapping Target and Method box, do the following:

f)

Choose Next Entry.

g)

After the last field is entered, choose Save.

h)

Repeat steps b) through g) for the following info parameters: PLANT PLANT_NAME PO_NO ROUTE_DESCRIPTION SALES_ORDER_NO SALES_REPRESENTATIVE SHIPMENT_NO SHIP_TO_PARTY_CITY SHIP_TO_PARTY_COUNTRY SHIP_TO_PARTY_NAME SHIP_TO_PARTY_REGION SHIP_TO_PARTY_STREET

5.

Assign your new profile to the mapping area by selecting Assign Profile to Mapping Area from the dialog structure on the left. Select the entries for application object type LTL_DELIV and leave Application System blank


166


2010

SCM663


and choose Copy As. Change the application system to T90CLNT090 (or the ECC server assigned to the class) and the application object type and map profile to Z##_LTL_DELIV. a)

From the dialog structure on the left, select Assign Profile to Mapping Area.

b)

Select LTL_DELIV as the entry for application object type. Leave Appl.System blank.

c)

Choose Copy As.

d)

Change the Appl.System to T90CLNT090, or the ECC Server assigned to the class.

e)

Change the application object type to Z##_LTL_DELIV.

f)

Change the mapping profile to Z##_LTL_DELIV.

g)

Choose Enter.

h)

Choose Save.

i)

Choose Exit.

Task 4: Test your configuration. 1.


Entry

Order Type

OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-06-##



Material Number

P-102

Quantity Ordered

2


2010


167


SCM663

Sales Order Number: ___________________ a)

Log into the SAP ECC system.

b)

Use transaction VA01 to create the sales order or choose: Logistics → Sales and distribution → Sales → Order → Create

2.

c)

On the initial screen, enter the order type, sales organization, distribution channel and division. Choose Enter.

d)

On the overview screen, enter the sold-to party, PO number, requested delivery date, material number and quantity. Choose Enter.

e)

Choose Save.

Create a delivery note for your sales order. In the delivery, enter the pick deadline of today’s date + 2 business days and the picking time at 1:00 a.m. This will become the expected time for the Picking Begin event. Field Name

Entry

Shipping Point

1000

Selection Date

2 weeks from today

Sales Order Number

From prior step

Pick Deadline


Picking Time

1:00 a.m.

Delivery Number _______________ a)

Use transaction VL01N or choose from the SAP menu: Logistics → Sales and Distribution → Shipping and Transportation → Outbound Delivery → Create → Single Document → with Reference to Sales Order

3.

b)

Enter shipping point 1000. Enter the selection date as today + 2 business days. The sales order youcreated in the previous exercise should appear in the Order field. Choose Enter.

c)

On the overview screen, select the Picking tab. In the Pick/Date Time field, enter today’s date + 2 business days. Enter 01:00 in the Time field.

d)

Choose Save.

Create a shipment for your pumps. The shipment will create an event handler and expected events in SAP Event Management. Use the following data in the shipment creation process. Continued on next page

168


2010

SCM663


Field Name

Entry


1000

Shipment Type


Shipment Route

R00001

Shipping Condition

SS, where SS = 50 + ##

Planning Times

Date

Time

Check-In


8:00

Loading Start


9:00

Loading End


10:00

When you save the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. a)

To create the shipment document use transaction VT01N or from the SAP Easy Access menu, choose: Logistics → Sales and Distribution → Shipping and Transportation → Shipment → Create → Single Documents

b)

In the initial screen, enter the transportation planning point and shipment type. Note: Make sure you have the Expert options set in the Customizing of Local Layout Options so that you can see the display of the shipment type codes.

c)

Click the Select Deliveries button in the application toolbar.

d)


e)


f)

On the Create: Shipments and Deliveries screen, click the Overview of Current Shipment icon (the mountain and sun).

g)

Under the Processing tab in the upper portion of the screen, enter the shipment route and the shipping condition.

h)



2010


169


i)

4.

SCM663

Enter the planning data from the data table below. When you save the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. Planning Times

Date

Time

Check-In


8:00

Loading Start


9:00

Loading End


10:00

Update the Shipment Stage information with the following dates and times: Shipment Stage Start

Date Today + 2 Business Days

End


Time 11:00 22:00

When you save the shipment, these fields will be used to create the expected events Plant Departure and Customer Arrival. Shipment Number: ____________________ a)


b)


c)

Click the Stage details icon at the lower-left corner of the screen.

d)

Select the Dur.and distnce tab on the Details on Stage 0001 screen.

e)


Date

Time

Start


11:00

End


22:00

f)

Choose the Copy button at the bottom of the Details on Stage 0001 screen.

g)

Choose Save.


170


2010

SCM663


5.

Verify that an event handler was created in SAP Event Management. Also, verify that the event handler was generated based on your new application object type. Log into the SAP SCM/Event Management system and run the Event Handler List and view the event handler that was created by the shipment in the prior step. Use event handler type LTL_DELIV. Enter your delivery number, including two leading zeros, in the Tracking ID field. Check the list of expected events. Are the changes to dates and times that you made in this exercise reflected in the list of expected events? a)

Log into the SAP SCM/EM system using the client number, user ID, and password provided by your instructor.

b)

Run the Event Handler List. In the SCM/EM application system navigate to SAP Menu → Event Management → Monitoring and Lists → Event Handler List

c)

In the selection screen, enter LTL_DELIV in the Event handler Type field.

d)

Enter your delivery number with two leading zeroes in the Tracking ID field.

e)

Choose Execute.

f)

Select the Expected Events tab. Record the following: Picking Begin:

Date: _____________

Time: _____________

Picking End:

Date: _____________

Time: _____________

Loading Begin:

Date: _____________

Time: _____________

Loading End:

Date: _____________

Time: _____________

Check the application object type. Your Z##_LTL_DELIV should be the application object type for the event handler.

2010


171


SCM663

Lesson Summary You should now be able to: • Configure the connection from an SAP application system to SAP Event Management • Configure the system for relevance determination • Create a list of expected events, parameters and tracking IDs

172


2010

SCM663

Lesson: Configure Drilldown into Application Object

Lesson: Configure Drilldown into Application Object Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Business Example

Figure 152: Configure Drilldown into Application Object

When the user should be allowed to directly navigate to the underlying application document from SAP Event Management, this has to be configured per application object type. You have to provide either the BOR object and a display method or the database table. Prerequisites are that the RFC connection has to be configured properly and the link has to be underlined. To set up display of original documents from an SAP system, in the SCM/EM IMG, choose Event Management → Event Messages and Status Queries → Display Original Documents from an SAP System.

2010


173


SCM663

Lesson Summary You should now be able to: •

174


2010

SCM663

Lesson: Generic Application Interface

Lesson: Generic Application Interface Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain how the generic application interface works

Business Example You have a requirement to connect SAP systems to SAP Event Management.

Figure 153: SAP EM - Integration with Application Systems

Integration with another SAP component is usually done with the SAP Event Management application interface, which comes with any SAP application system (PlugIn Basis). It allows you to define which application objects may be relevant for SAP EM, and to transfer an event to SAP EM when an application object is modified or deleted. The most important business objects are already technically-enabled. More advanced out-of-the-box integration is achieved with the help of so-called visibility processes which are covered in the next section

2010


175


SCM663

Figure 154: The Generic Application Interface (AI) to SAP EM

Figure 155: Event Message Posting from Application System

As of SCM 4.0, the application interface has been extended so that if the application object is created, changed or deleted, you can transfer an event to SAP Event Management. You define event types in SAP ERP IMG under Integration with Other mySAP.com Components → Event Management Interface → Define Application Interface → Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types.

176


2010

SCM663


Figure 156: Connected Objects in SAP ERP and SAP APO

This is a list of connected objects in SAP ERP and SAP APO. Each of these objects is technically enabled, which means that a BADI or equivalent exists for the object.

Figure 157: Fulfillment Visibility - A Visibility Process Example

2010


177


SCM663

Figure 158: Technical Issues

Figure 159: Technical Components of the Application Interface

Figure 160: Distribution of Tasks in Event Handler Control

The application system and the SAP Event Management system are each responsible for specific tasks.

178


2010

SCM663


This list of tasks shows the application system responsibility and SAP Event Management responsibilities and is included here as a reference.

Figure 161: Application Interface Operation

Figure 162: Application Interface Status Tables

The status table may be used to access the logs and find out which application objects exist for a business object to retrieve data from SAP Event Management.

2010


179


SCM663

Lesson Summary You should now be able to: • Explain how the generic application interface works

180


2010

SCM663

Unit Summary

Unit Summary You should now be able to: • Configure the connection from an SAP application system to SAP Event Management • Configure the system for relevance determination • Create a list of expected events, parameters and tracking IDs • • Explain how the generic application interface works

2010


181

Unit Summary

182

SCM663


2010

Unit 7 Creating Event Handlers – Configuration Unit Overview

Unit Objectives After completing this unit, you will be able to: • • • • • • • • • •

Create an event handler using your own configuration Configure expected events Configure event codes Explain the purpose of tracking and query IDs Define three types of parameters, including the origin and how to use them Define status attribute types and status attribute profiles Assign the status to the event handler type or event handler set Define event handler type and event handler conditions Describe the purpose of an event handler set Describe how to change an event handler

Unit Contents Lesson: Creating Event Handlers - Introduction ............................184 Lesson: Expected Events and Event Codes ................................187 Lesson: Tracking/Query IDs...................................................200 Lesson: Parameters ............................................................206 Lesson: Status ..................................................................216 Lesson: Event Handler Type ..................................................221 Lesson: Event Handler Sets...................................................230 Lesson: Maintaining the Event Handler......................................236 Exercise 4: Configuring the Creation of Expected Events ............237

2010


183

Unit 7: Creating Event Handlers – Configuration

SCM663

Lesson: Creating Event Handlers - Introduction Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Create an event handler using your own configuration

Business Example

Figure 163: Defining Elements of Event Handlers (1/2)

These questions are not topic-specific, but will help to get the unit objectives across. The answers to these questions provide specific pieces of the event handler. For example, for question 1, when you define the list of events you want to manage, you are defining expected events and event codes. Each question relates to a topic in this unit.


184


2010

SCM663

Lesson: Creating Event Handlers - Introduction

Figure 165: Example of Status Retrieval

This screenshot shows you how the elements from the answers to the questions on the previous slides are used in the status retrieval on the Web. Each red box relates to a topic in this unit and one of the questions. Question #5 addresses under which conditions the event handler is generated in the first place, and question #6 addresses grouping together event handlers into sets. The last topic refers to maintenance of event handlers.

2010


185


SCM663

Lesson Summary You should now be able to: • Create an event handler using your own configuration

186


2010

SCM663

Lesson: Expected Events and Event Codes

Lesson: Expected Events and Event Codes Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • •

Configure expected events Configure event codes

Business Example What events do you want to manage using SAP Event Management? When you answer this question, you define the expected events and event codes.

Figure 166: List of Expected Events

The screenshot of the Event Handler Overview in SAP Event Management shows an example of a list of expected events and the dates when they are expected to occur. At this point, we are just talking about the event or the happening that we want to track and when it is expected to occur.

2010


187


SCM663

Figure 167: Expected Events - Definition

An expected event is something that you expect to happen such as a deadline or a project milestone. Examples of expected events include activities such as arrival at a customer site, the start of a production or purchase order, and arrival of a carrier at a hub. An event might either be sent from another system – for example, any SAP application component including SAP R/3 ECC, SAP CRM, SAP APO – or the event might be calculated directly in SAP Event Management, possibly calculated because of another event.

Figure 168: List of Expected Events - Flexible Definition

The expected events that are generated can vary for different carriers or different customers or different circumstances. This is determined by the business process.

188


2010

SCM663


Figure 169: Defining Event Codes

An event code defines the event so that SAP Event Management can process it. Any expected or unexpected event code must be configured in order to be processed by SAP Event Management. An unexpected event is defined in the list of event codes, but it is not listed in the expected events that are generated. An unexpected event code is used only in event notification. Event codes can be grouped together. For example, in tendering, you might group together tender to the service provider, answer from the service provider to the tender, tender accepted by the service provider, and tender rejected by the service provider. You group all four internal event codes in a group tender. Now you need only one definition for an expected event for the whole group, for example, send an e-mail if an event message for one of these four internal event codes is sent to SAP Event Management, instead of four definitions, one for each internal event code. To define internal event codes and event code groups, in the SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Codes → Event Codes → Define Internal Event Codes and Internal Event Code Groups.

2010


189


SCM663

Figure 170: Defining Status Icon Schema

A status icon schema allows you to assign a status icon for each extended status code for expected, unexpected, and consolidated events. To define status icons, in the SCM/EM IMG choose Event Management → Event Messages, Status Queries and Web Interface → Define Status Icons. To define internal event codes and event code groups, in the SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Codes → Event Codes → Define Internal Event Codes and Internal Event Code Groups.

Figure 171: Source and Calculation of Expected Events

190


2010

SCM663


This chart shows an example of how an expected event might be generated. In the Item# column, you see the sequence code for the sequence in which you expect this list of events to happen. Then you see the Event Code and Description. In the GenFrom (generate from) columns, you see the system name of the field and the name of the table field in the application system from which the event is generated. The calculation rule shows how an event can be generated if it is not sent from the application system, for example, PICKEND is derived from the PICKBEG + 2 hours. These are the things you need to decide about when you are configuring your event codes. What is it that you want to track and where will that information come from? This is then entered into configuration and becomes the expected event profile.

Figure 172: Customizing of Expected Event Profiles

This screenshot is from customizing the expected event profile. To define profiles for expected event: • •

2010

In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events. Choose your expected event and double-click on Update Profile Group on the left.


191


SCM663

Figure 173: Special Features of Expected Event Profiles

Within the expected event profile, it is possible to group together events that belong logically together. For tendering, for example, you might group together tender to the service provider, answer from the service provider to the tender, tender accepted by the service provider, and tender rejected by the service provider. You group all four internal event codes in a group tender. Now you need only one definition for an expected event for the whole group, for example, send an e-mail if an event message for one of these four internal event codes is sent to SAP Event Management, instead of four definitions, one for each internal event code. It is possible to repeat events. You could set up the termination event code so that one day after the final physical event is reported, the event handler is completed and deactivated, and then uploaded to SAP BI.

192


2010

SCM663


Figure 174: Expected Event Item View

This screenshot is an example of configuration of an expected event. This event is not sent from the application system. It will occur two hours after the event you will find in item# 1. To define profiles for expected events: • • • •

2010

In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events. Choose your expected event profile and double-click on Update Profile Group on the left. Select your profile group and double-click on Update Profile Item. Select one event code and choose Details.


193


SCM663

Figure 175: Expected Event Profile and List of Expected Events

The expected event profile is assigned to an event handler type and contains a list of events that might be expected, the sequence of those events and any dependencies. Additionally, the derivation of the dates and times for the expected events are included as well as check routines for partners and locations. The list of expected events is generated when a business process on the application side meets the requirement for generating an event handler. This list will then contain what is actually expected to happen for this particular business process including actual dates and times when those happenings are expected. This list of expected events exists for each event handler that is generated.

194


2010

SCM663


Figure 176: Assigning Expected Event Profile to EH Type

This screenshot shows where you assign the expected event profile to the event handler type. To define event handler types: • •

In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types. Select your event handler type and choose Details.

Figure 177: Activities and Functions for Expected Events

2010


195


SCM663

In the expected event profile, you configure update activities that control the Generate function and the EE Monitor activity. The Generate function identifies the event activity to be used to create the expected events for an event handler. If blank, the default expected event generate method GENERATE_EVENTS (class /SAPTRX/CL_EXPEV_GENERATOR ) is used to generate the expected events. The EE Monitor activity is a multi-task activity that is performed for an expected event when the expected event monitor program determines that an expected event date has passed without an event message being received. Note: As of SAP SCM 4.0, the former evaluate procedure is now included in the EE Monitor activity. When migrating from SAP Event Management 1.1 to SAP SCM 4.0, an XPRA routine is provided for this and other changes.

Figure 178: Assigning Functions and Activities to EE Profile

This screenshot shows where the Generate function and EE Monitor activity are assigned to the expected event profile. To define profiles for expected events: • •

196

In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events. Select your expected event profile and choose Details.


2010

SCM663


Figure 179: Population of Service Providers and Locations

The service provider is who sends an event. The location is where the event happens. This is where the information about the sending party for the event is programmed. The population of the Service Provider and Location is a check to make sure that the service provider and location sending the message is the one that is expected. To match the service provider and location data, the program matches the external code with the internal code. To set up the population function for service provider and location, in SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Expected Events → Define Functions for Expected Events.

Figure 180: Assigning Population Functions

2010


197


SCM663

These two screenshots indicate where you can create the Service Provider and Location functions and then where you relate those functions to the expected event profile item. To define profiles for expected events: •

• • •

The screenshot on the left is in SCM/EM customizing under Event Management → Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events. Choose Update Profile Groups from the dialog structure on the left. Select the group, then choose Update Profile Items from the dialog structure on the left. Double-click on any internal event code.

To define functions for expected events: •

•

198

The screenshot on the right is in SCM/EM customizing under Event Management → Event Handlers and Event Handler Data → Expected Events → Define Functions for Expected Events Choose from the dialog structure on the left Service Provider Matching, Location Matching, Service Provider Population, Location Population.


2010

SCM663


Lesson Summary You should now be able to: • Configure expected events • Configure event codes

2010


199


SCM663

Lesson: Tracking/Query IDs Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain the purpose of tracking and query IDs

Business Example How do you identify your event handler? When you answer this question, you identify the tracking or query ID.


These questions are not topic-specific, but will help to get the unit objectives across. The answers to these questions provide specific pieces of the event handler. For example, for question 1, when you define the list of events you want to manage, you are defining expected events and event codes. Each question relates to a topic in this unit.


200


2010

SCM663

Lesson: Tracking/Query IDs

Figure 183: Example of Status Retrieval

This screenshot shows you how the elements from the answers to the questions on the previous slides are used in the status retrieval on the Web. Each red box relates to a topic in this unit and one of the questions. Question #5 addresses under which conditions the event handler is generated in the first place, and question #6 addresses grouping together event handlers into sets. The last topic refers to maintenance of event handlers.

Figure 184: Tracking IDs

The tracking ID identifies one or more event handlers. It is used to find out which event handler or handlers to update when an event message is received.

2010


201


SCM663

The tracking ID consists of the tracking code set plus the tracking code ID, which gives the system the ability to distinguish between different objects with the same identification. Here you see the example of a container and a railcar having the same identification, but the combination with the code set helps to distinguish them. An event handler can have multiple tracking IDs. So it is possible to have more than one tracking ID for an event handler, for example, the vendor knows the purchase order, so they access the record with the PO number, and the carrier might know the container number or a shipment number, so they would access the record with that data.

Figure 185: Example of Tracking ID Use

Here is an example of the tracking code set together with the tracking code ID in transaction /SAPTRX/MI02. This transaction can be used as a method of event notification. This transaction is started by transaction code and is not found in the menu tree structure.

202


2010

SCM663


Figure 186: Query IDs

Query IDs are used to retrieve status information. Normally, the query ID is a document number from the application system. Typically, these numbers would be something like a purchase order number or shipment number. Query IDs are defined in the application system and do not need to be unique to one event handler.

Figure 187: Tracking/Query IDs in the Event Handler Details

This screenshot shows the use of the tracking ID and query ID in the EH_LIST transaction. The query ID is shown in the upper portion of the screen and the tracking ID together with the code set is shown at the lower edge of the screen.

2010


203


SCM663

Figure 188: URL Template for Transportation Service Provider

You can maintain a URL template for a Web hyperlink that leads the user directly to a transportation providers Internet page. This link is then provided within the event handler lists. Prerequisites are that the activities TRACKING_ID_SET and WEBLINK_SET are assigned to your rule set. To access the URL templates for tracking ID providers, in SCM/EM IMG choose SCM/EM : IMG: Event Management → Event Messages and Status Queries → URL Templates for Tracking ID Providers. You can also create new tracking IDs through event sending.

204


2010

SCM663


Lesson Summary You should now be able to: • Explain the purpose of tracking and query IDs

2010


205


SCM663

Lesson: Parameters Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Define three types of parameters, including the origin and how to use them

Business Example What additional information or data do you require? When you answer this question, you have defined the parameters.

Figure 189: Parameters in General

Parameters are variables of the objects and processes that are relevant to SAP Event Management. The parameters contain the information from the application system about an application object. They are defined and stored in SAP Event Management in the form of control, info and system parameters. In this way, SAP Event Management can use them independently of SAP ECC. All parameters have the features listed on the screen in common. A value set means a mapping parameter, for example, if one application system refers to the route as route A1, but another application system refers to it as Z5, although its the same route. In customizing, the parameter mapping is mapping mode V. Parameters are defined in SCM/EM customizing at: Event Management → Event Handlers and Event Handler Data → Parameters

206


2010

SCM663

Lesson: Parameters

Figure 190: Types of Parameters

You define control, info and system parameters in SAP Event Management, which contain information from the application system about an application object. SAP Event Management stores the parameters in a parameter dictionary, so that you can use the SAP Event Management independently of an SAP R/3 system. You use control parameters in SAP Event Management for control purposes, for example, to define conditions. You can define the following control parameters, for example, for a shipment: delivery priority, shipment type, shipment conditions and shipping type. Info parameters contain all additional information about an event handler, for example, the name of the carrier, location details, the confirmed date for a delivery. You can use info parameters for search and information queries in SAP Event Management. You can define the following info parameters for a shipment: carrier name and address, container ID, delivered quantity and material, sales order and contact person. By defining system parameters in SAP Event Management, you specify the field values for typical search queries. System parameters are special control parameters from the application system that allow you to make fast search queries using indexing. For example, you define the following as system parameters for a shipment: shipping point, transportation planning point, carrier, route, goods recipient and ordering party. You then start a search query to SAP Event Management for all shipments with carrier Smith on route A . You cannot change the system parameters because they are predefined by SAP.

2010


207


SCM663

Figure 191: Info Parameters: Example

Examples of info parameters include the following: customer number, purchase order number, batch number, material number, and material description.

Figure 192: Parameters in the Event Handler Details

These screenshots show examples of the different parameters in an actual event handler. To get to these details, you can use transaction /SAPTRX/EH_LIST. You used this detail view earlier to show the tracking and query IDs. Under the Control Data tab, you see the control parameters. Under the Info Data tab, you see the info parameters and under the Header extension, you see the system parameters.

208


2010

SCM663

Lesson: Parameters

Figure 193: Source of Parameters

The application system doesn't distinguish between control and system parameters. In the SAP landscape, the extraction of parameters is part of the application interface. SAP Event Management stores the parameters in a parameter dictionary so it can work independently of the application system.

Figure 194: Configuring Parameters

2010


209


SCM663

In customizing, you define the control, info and system parameters, then you define the parameter mapping. The next few slides show this process.

Figure 195: Control and Info Parameter Definition

This is the screenshot of the configuration for control and info parameters. Parameters are defined in SCM/EM customizing at: Event Management → Event Handlers and Event Handler Data → Parameters → Define Control, Info, and Rule Processing Parameters

Figure 196: System Parameter Definition

210


2010

SCM663

Lesson: Parameters

This is the screenshot of the configuration for system parameters. Parameters are defined in SCM/EM customizing at: Event Management → Event Handlers and Event Handler Data → Parameters → Define System Parameters

Figure 197: Mapping Parameters Using a Profile

Parameter names could be different in the different application systems with different values. In SAP Event Management, we unify them using a mapping profile. The mapping profile determines the event handler type if the event handler type contains a condition that builds on a control parameter. The mapping profile is assigned to an application system and an application object type. To define the mapping profile, in SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Parameters → Define Parameter Mapping.

Figure 198: Parameter Mapping

2010


211


SCM663

Again, because parameter names could be different in the different application systems with different values, in SAP Event Management, we unify them using a mapping profile. When event handlers are created, the value from the application system is populated to the event handler. The value from the application system can be populated directly to SAP Event Management, or it can be derived using the mapping function, or the value can be populated using default data. If there is an error in the mapping process, you can elect to skip the parameter, return an error, or assign a value. A typical source of errors is the missing assignment of the mapping profile to the application object type.

Figure 199: Define Parameter Mapping

Here you specify how the parameter is mapped from the application system to the SAP EM system and thus create a mapping profile. Then you assign the profile to the application object type.

Figure 200: Assign Profile to Mapping Area

212


2010

SCM663

Lesson: Parameters

This screenshot shows the assignment of the mapping profile to the mapping area. You see the assignment of the application system and the application object type to the mapping profile. To define the mapping profile, in SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Parameters → Define Parameter Mapping.

Figure 201: Parameter Mapping Functions

You can use activities to define a complex way of controlling the transfer of parameters from the application system to SAP Event Management in the case where direct value takeover or mapping table doesn't fit your requirements.

Figure 202: Assigning Parameter Mapping Functions

This screenshot shows where the function is assigned in the mapping profile.

2010


213


SCM663

To define the mapping profile, in SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Parameters→ Define Parameter Mapping.

214


2010

SCM663

Lesson: Parameters

Lesson Summary You should now be able to: • Define three types of parameters, including the origin and how to use them

2010


215


SCM663

Lesson: Status Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • •

Define status attribute types and status attribute profiles Assign the status to the event handler type or event handler set

Business Example What data do you need to get a quick overview of the status of an event handler or event handler set? When you answer this question, you identify the status.

Figure 203: Example for Status Retrieval

These screenshots show the status attributes of an event handler. The screenshot on the left shows transaction /SAPTRX/EH_LIST.

216


2010

SCM663

Lesson: Status

Figure 204: Status - Example

You define status attributes for an event handler, which you classify in status attribute types, for example, you classify status attribute type fill status with status attributes empty, half-full or full. The status is used to get an overview of the current situation of an event handler. You group one or more status attribute types in the status attribute profile, which you defined in the IMG activity Define Status Attribute Types. The status attribute code ID, for example, planned, delivered, delayed, forms the default value that the system assigns when creating the event handlers. To define status attribute profiles, in SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Status → Define Status Attribute Profiles. This is transaction /SAPTRX/SAPLSTPROF. To assign the status attribute profile: •

•

2010

Use transaction /SAPTRX/SAPLVTRKTYPE or in the SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types. Select your event handler type and choose Details.


217


SCM663

Figure 205: Defining Status Attributes

You must define the status attributes in customizing and you can assign an icon to illustrate the status attribute value.

Figure 206: Initial Status and Status Flow for Visibility Process

Here is an example of a use of the status attribute. For the event Creating Shipment, the status is not started on time. There is an expected event then in Plant Departure where the status changes to “in transit.” An unexpected event, a delay, occurs and the status is changed to “Delayed.” When the shipment arrives at the customer, the status is then changed to “Arrived.” These status settings are programmed using the event handler methods.

218


2010

SCM663

Lesson: Status

Figure 207: Status Attribute Profile

This screenshot shows where the status attribute profile is associated in configuration to the event handler type. To define event handler types: • •

2010



219


SCM663

Lesson Summary You should now be able to: • Define status attribute types and status attribute profiles • Assign the status to the event handler type or event handler set

220


2010

SCM663

Lesson: Event Handler Type

Lesson: Event Handler Type Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Define event handler type and event handler conditions

Business Example What, and under which conditions, does this event handler need to be created? When you answer this question, you define the event handler type and Conditions.

Figure 208: Event Handlers and Event Handler Types

2010


221


SCM663

Figure 209: Process Implementation - Example

Figure 210: Event Handler Type Definition

The event handler type determines the expected event list, the status attributes, follow-up activities, the BW extract, authorizations, and the system parameters.

222


2010

SCM663


Figure 211: Event Handler Type - Details

This screenshot shows how the different profiles are associated to the event handler type. To define event handler types: • •


Figure 212: Event Handler Type Determination

Each event handler type is assigned to a business process type.

2010


223


SCM663

The system checks all event handler types that belong to the business process type, sorted by priority, and determines whether an event handler needs to be created for that condition, for example, the Carrier = XYZ. The first event handler type that fulfills the condition is used to create an event handler.

Figure 213: Event Handler Type Priority

The Priority field is a numerical field that is used to build a ranking in the table of event handler types. This field influences which event handler type is evaluated first.

Figure 214: Unexpected Event Code Check

224


2010

SCM663


The unexpected event code check determines if the event code is checked after the system determines that an event message is reporting an unexpected event. You can maintain permitted event codes for unexpected events. If the indicator is set and the reported event code is not contained in the list of permitted event codes, event message processing is aborted and the event message is marked as irrelevant. Irrelevant event messages are neither displayed nor retrieved by BAPIs or business application programming interfaces.

Figure 215: Condition Editor for AOT Relevance Conditions

This screenshot shows the condition editor, and is inserted here for your reference. Transaction is /SAPTRX/ASC0TC.

2010


225


SCM663

Figure 216: Creating Event Handler Header Extensions

It is possible to create event handler header extensions to create database tables that allow you to efficiently store system parameters, which are then used for performance-critical queries. In the first step, you define the database table with system parameter fields. To assign the database table to the EH header extension: •

•

In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Extensions to Event Handler Header. Select your extension table ID and choose Details.

To assign the EH header extension to the EH type: • •

226



2010

SCM663


Figure 217: Activities and Functions for Event Handler Types

In the event that the system should modify data before the event handler is created or the database is saved, you can define activities that can be used in the EH definition. If the condition for determining the event handler is too complex, you could use an activity to create the event handler rather than depending on the condition. The illustration shows how SAP Event Management does the update. This procedure might be called before creating the event handler or after it is created, but before it is saved. Activities are assigned to the procedure.

2010


227


SCM663

Figure 218: Assigning Update Activities to EH Types

These screenshots show where you assign the EH procedure to the event handler type, how you assign the activity to the condition of the event handler type, and how you assign the function to the condition of the event handler set. Event handler procedure ID1 applies to changes before creating the event handler. Event handler procedure ID2 applies to changes after creating the event handler, but before saving it to the database. To assign the event handler procedure to the event handler type, in SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types.

228


2010

SCM663


Lesson Summary You should now be able to: • Define event handler type and event handler conditions

2010


229


SCM663

Lesson: Event Handler Sets Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Describe the purpose of an event handler set

Business Example To build a complete business process, which event handler types should be grouped together? When you answer this question, you have defined an event handler set.

Figure 219: Event Handler Set

Event handler sets are used to group together event handlers that logically belong together. Event handlers represent a certain process within the supply Chain. The event handler set forms a relationship between these related event handlers and is displayed to the user as a single entity. A status profile is available at the event handler set level. For example, a service provider wishes to track all deliveries of his shipment by tracking the same type of event handler or wants to receive all information on a purchasing process including its purchase order, production order and shipment by tracking different event handler types, one for production and one for shipping.

230


2010

SCM663

Lesson: Event Handler Sets

Figure 220: Event Handler Set and Relations

You define event handler sets using event handler set relations, which you assign to an event handler set profile. An event handler set relation defines the characteristics that two or more event handlers have in common and which the system uses to create the event handler set. It consists of an event handler set relation type and an event handler set relation code. The event handler set relation type specifies the type of relationship between event handlers belonging to an event handler set. You can form the set using control parameters, tracking ID code sets, or query ID code sets. If the event handler set relation code is identical, that is, in control parameter name, tracking ID code set name, and query ID code set name, the system creates an event handler set. For example, you want to form event handler sets for event handlers with an identical value for the control parameter PARCEL_SIZE. You select the event handler set relation type control parameter and the event handler set relation code PARCEL_SIZE. The system can form event handler sets from event handlers with different event handler types. To do this, you assign an event handler set profile to the corresponding event handler types. You assign the event handler set to at least one event handler type so that the system can form event handler sets.

2010


231


SCM663

Figure 221: Event Handler Sets - Setup (1)

In step 1, define the event handler set profile. In step 2, define the event handler set relation for the event handler set profile. In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Profiles for Event Handler Sets.

Figure 222: Event Handler Sets - Setup (2)

232


2010

SCM663


In step 3, define condition for the event handler set. In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Conditions for Event Handler Types and Event Handler Sets. •

•

The relevance of an object or process is checked in the application system by determining its application object type. By defining a condition for the event handler type or the event handler set, you specify whether an event handler or an event handler set is created in SAP Event Management for a relevant application object. For example, specify all overseas deliveries as relevant in the application system. In SAP Event Management, you specify the condition for the event handler type so that only the overseas deliveries are tracked. Event handlers containing all the data for the event handler are created in SAP Event Management for these overseas deliveries.

In step 4, assign the event handler set profile and condition to the event handler type. In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types.

Figure 223: Consolidation Profiles for EH Sets

SAP Event Management first sorts the events according to EH header fields and then according to event handler type. If you do not use an event consolidation profile, SAP Event Management sorts the events in ascending order according to the expected or actual date and times.

2010


233


SCM663

Figure 224: Consolidation Profiles for EH Sets

In step 1, define the consolidation profile. In SCM/EM IMG choose Event Management → Authorizations and Filters → Define Event Consolidation Profiles. In step 2, assign the consolidation profile to the EH set profile. In SCM/EM IMG choose Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Profiles for Event Handler Sets.

234


2010

SCM663


Lesson Summary You should now be able to: • Describe the purpose of an event handler set

2010


235


SCM663

Lesson: Maintaining the Event Handler Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Describe how to change an event handler

Business Example You need to be able to modify and delete event handlers as part of routine maintenance.

Figure 225: Changing an Event Handler

OO stands for object-oriented programming. Online documentation can be found at http://help.sap.com. For a list of delivered activities, see SAP Business Suite → SAP Supply Chain Management → SAP SCM 5.0 (English or German) → SAP Event Management (SAP EM) → SAP Event Management Infrastructure → Overview of Activities Delivered → Activity List Structure.

236


2010

SCM663

Lesson: Maintaining the Event Handler

Exercise 4: Configuring the Creation of Expected Events Exercise Objectives After completing this exercise, you will be able to: • Configure event codes • Create an expected event profile • Define parameters • Define a status profile • Create an event handler type • Create an event handler condition • Test your configuration

Business Example In this exercise we will configure the system to support the process you tested in the exercises in the prior units of this course. The business process is that for all outbound shipments where the Shipping Condition = SS, where SS = 50 + ## (your group number), you would like to track the following events: Picking Begin, Picking End, Packing, Carrier Arrival, Load Begin, Load End, Plant Departure, Arrival at Customer, Unload, Proof of Delivery. In the first part of the exercise, you want to define this list of events, event codes, parameters, status profile, event handler type, and event handler condition to support this business process.

2010


237


SCM663

Task 1: PART I: Configuring the Expected Event Profile You first need to create the event codes that will be used to track the events related to your shipping process. These events will be inserted into your expected event profile. The events that you want to track are: Picking Begin and Picking End Packing Arrival Carrier Loading Begin and Loading End Plant Departure Arrival Customer Unload and Proof of Delivery You also need to create the event code DELAYED for reporting Unexpected Events. 1.

To create the event codes, go to customizing in SAP Event Management and create your event codes as follows: Internal Event Code

Z##_PICKBEG

Description

Picking Begin

Internal Event Code

Z##_PICKEND

Description

Picking End

Internal Event Code

Z##_PACKING

Description

Packing

Internal Event Code

Z##_CARRARRIV

Description

Arrival Carrier

Internal Event Code

Z##_LOADBEG

Description

Loading Begin

Internal Event Code

Z##_LOADEND

Description

Loading End

Internal Event Code

Z##_PLANTDEP

Description

Plant Departure

Internal Event Code

Z##_CUSTARRIV

Description

Arrival at Customer Continued on next page

238


2010

SCM663


Internal Event Code

Z##_UNLOAD

Description

Unloading

Internal Event Code

Z##_POD

Description

Proof of delivery by customer

Internal Event Code

Z##_DELAYED

Description

Unplanned Event – Delayed

Task 2: Define an expected event profile. In the Expected Event Profile create the update profile groups entry. In this entry, enter the event codes you defined above with the related configuration settings. 1.

Create the expected events profile. Expected Event Profile

Z##_LTL_EXP_EVENTS

Description

Z## Expected Events Profile

2.

Create the update profile groups entry.

3.

Update the profile group with the event codes you created previously and with the configuration setting related to each event code. Item

1

Event Code

Z##_PICKBEG

Generated From

PICKING_BEGIN

Reprocess Expected Event

Select this option

Expected Event Date Date Rule

From Application System

Calculation Rule

Actual Event, Else Expected Date

Expected Event Functions Partner Function

Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check


2010


239


SCM663

Item

2

Event Code

Z##_PICKEND

Generated From

PICKING_BEGIN


Select this option


Relative to Unique Event

Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item Number

1

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

3

Event Code

Z##_PACKING

Generated From

PICKING_BEGIN


Select this option



Duration

2:15

Duration Sign

Add Duration

Group Number

10

Item Number

1

Calculation Rule



Select Do Not Set


240


2010

SCM663


Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

4

Event Code

Z##_CARRARRIV

Generated From

CHECK_IN


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

5

Event Code

Z##_LOADBEG

Generated From

LOADING_BEGIN


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check


2010


241


SCM663

Item

6

Event Code

Z##_LOADEND

Generated From

LOADING_END


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

7

Event Code

Z##_PLANTDEP

Generated From

LOADING_END


Select this option



Duration

00:15

Duration Sign

Add Duration

Group Number

10

Item Number

6

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check Continued on next page

242


2010

SCM663


Item

8

Event Code

Z##_CUSTARRIV

Generated From

ARRIVAL_CUSTOMER


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

9

Event Code

Z##_UNLOAD

Generated From

ARRIVAL_CUSTOMER


Select this option



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item Number

8

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location


2010


243


SCM663

Item

10

Event Code

Z##_POD

Generated From

ARRIVAL_CUSTOMER


Select this option



Duration

48:00

Duration Sign

Add Duration

Group Number

10

Item Number

8

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Task 3: PART II The control, system and info parameters were already created in customizing by the exercises in Unit 6, “Configuring the Application System”. You can review the configured parameters in customizing under Event Management → Event Handlers and Event Handler Data → Parameters. For this exercise we will use the parameter profiles as they are currently defined. 1.

Define status attribute profile.

2.

First, you need to define the status attributes for the delivery and transportation status as defined in the table below. Status Attribute Name

Z##_DEL_STATUS

Status Attribute Type

Definable Value

Description

Delivery Status


244


2010

SCM663


3.

Status Attribute Name

Z##_TP_STATUS


Definable Value

Description

Transportation Status

Enter the status attribute values from the table below. Status Attribute Name

Status Attr. Value

Description

Z##_DEL_STATUS

DELAYED

Delayed

ON_TIME

On Time

ARRIVED

Arrived

IN_TRANSIT

In Transit

NOT_STARTED

Not Started

Z##_TP_STATUS

You need to create the status attribute profile and then assign the attributes you created to the profile. Enter status attribute profile Z##_LTL_STATUS and description Status Profile for Delivery in LTL Shipment. for Z##. 4.

5.

Now you need to create the status attribute profile and then assign the attributes you created to the profile. In SCM/EM customizing, go to Event Management → Event Handlers and Event Handler Data → Status → Define Status Attribute Profiles. Choose New Entries. Status Attribute Profile

Z##_LTL_STATUS

Description

Status Profile for Delivery in LTL Shipment. for Z##

Select the new entry and enter the status attribute profile items. Status Attribute Name

Status Attribute Value

Z##_DEL_STATUS

ON_TIME

Z##_TP_STATUS

NOT_STARTED

Task 4: Create the event handler condition record that will determine when an event handler is created. Your event handler type will be chosen when the ECC shipment has the shipping condition = SS, where SS = 50 + ## (your group number). 1.

Create the event handler condition that will be assigned to the event handler type. This condition will determine if an event handler will be created for a delivery. Continued on next page

2010


245


Condition Description Shipping Condition (Control)

SCM663

Z##_SHIP_COND Shipping Condition for Z## SS (your shipping condition)

Task 5: Create the event handler type. 1.

Create the event handler type for the existing business process type for the shipment in SAP ECC and assign to it your expected events profile and your status attribute profile. Event Handler Type

Z##_EHT

Description

Event Handler Type for Z##

Business Process Type

ESC_SHPMT Shipment (SAP ECC)

Priority

1

Condition

Z##_SHIP_COND

Rule Set

LTL_RULES

Stat.Attr.Profile

Z##_LTL_STATUS

EE Profile

Z##_LTL_EXP_EVENTS

Ext.Table ID

DELIV_EXTENSION

BW Profile

DELIV_BW

Logs (EH Posting, Msg. Proc., Ext Update)

3 Verbose – Details of each process

Task 6: Test your configuration by creating a shipment. 1.

Create a standard sales order, based on data shown below: Order Type

OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-07-## Continued on next page

246


2010

SCM663


2.



Material Number

P-102

Quantity Ordered

3

Create the outbound delivery document from the sales order. In the delivery, enter the pick deadline of today’s date + 2 business days and the picking time at 7:00 a.m. This will become the expected time for the Picking Begin event. Note Delivery Number: ____________________

3.

Create your shipment. Use the following data in the shipment creation process. Transportation Planning Point

1000

Shipment Type


Shipment Route

R00001

Shipping Condition

SS (your shipping condition code) Date

Time

Check-In


11:00

Loading Start


11:15

Loading End


11:45

Shipment Completion


12:00

Shipment start


12:00

Shipment end


20:00

Planning Dates and Times

Shipment Stage

Date

Time

Start


12:00

End

Today + 2 business day

20:00

Note Shipment Number _____________ 4.

Verify that an event handler was created in SAP Event Management using your new event handler type. Log into the SAP SCM/Event Management system and run the Event Handler List and view the event handler that was created by the shipment in the previous step. Continued on next page

2010


247


SCM663

Use event handler type Z##_EHT. Check the list of expected events and verify that an event handler was created based on your new event handler type.

248


2010

SCM663


Solution 4: Configuring the Creation of Expected Events Task 1: PART I: Configuring the Expected Event Profile You first need to create the event codes that will be used to track the events related to your shipping process. These events will be inserted into your expected event profile. The events that you want to track are: Picking Begin and Picking End Packing Arrival Carrier Loading Begin and Loading End Plant Departure Arrival Customer Unload and Proof of Delivery You also need to create the event code DELAYED for reporting Unexpected Events. 1.

To create the event codes, go to customizing in SAP Event Management and create your event codes as follows: Internal Event Code

Z##_PICKBEG

Description

Picking Begin

Internal Event Code

Z##_PICKEND

Description

Picking End

Internal Event Code

Z##_PACKING

Description

Packing

Internal Event Code

Z##_CARRARRIV

Description

Arrival Carrier

Internal Event Code

Z##_LOADBEG

Description

Loading Begin

Internal Event Code

Z##_LOADEND

Description

Loading End

Internal Event Code

Z##_PLANTDEP Continued on next page

2010


249


SCM663

Description

Plant Departure

Internal Event Code

Z##_CUSTARRIV

Description

Arrival at Customer

Internal Event Code

Z##_UNLOAD

Description

Unloading

Internal Event Code

Z##_POD

Description

Proof of delivery by customer

Internal Event Code

Z##_DELAYED

Description

Unplanned Event – Delayed

a)

In the SCM system, use transaction SPRO to go to the IMG and choose SAP Reference IMG.

b)

Navigate to the table at: Event Management → Event Handlers and Event Handler Data → Codes → Event Codes → Define Internal Event Codes and Internal Event Code Groups

c)

Select New Entries.

d)

Enter the internal event code and description from the table above.

e)

Repeat step d) for all entries in the table above.

f)

Choose Save.

g)

Select Exit.

Task 2: Define an expected event profile. In the Expected Event Profile create the update profile groups entry. In this entry, enter the event codes you defined above with the related configuration settings. 1.

Create the expected events profile.


250


2010

SCM663


Expected Event Profile

Z##_LTL_EXP_EVENTS

Description


a)

Navigate to the table at: Event Management → Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events

b)

Select New Entries.

c)

Enter the Expected Event profile and description below.

d) 2.

Z##_LTL_EXP_EVENTS

Description


Choose Save.

Create the update profile groups entry. a)

Select Update Profile Groups from the dialog structure on the left. Select New Entries.

b)

Enter the data from the following table.

c) 3.

Expected Event Profile

Group

10

Gen

Select

Description

Z## All Expected Events for Delivery in LTL Shipment

Choose Save.

Update the profile group with the event codes you created previously and with the configuration setting related to each event code. Item

1

Event Code

Z##_PICKBEG

Generated From

PICKING_BEGIN


Select this option



Calculation Rule


Expected Event Functions Continued on next page

2010


251


SCM663

Partner Function

Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

2

Event Code

Z##_PICKEND

Generated From

PICKING_BEGIN


Select this option



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item Number

1

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

3

Event Code

Z##_PACKING

Generated From

PICKING_BEGIN


Select this option



Duration

2:15

Duration Sign

Add Duration

Group Number

10 Continued on next page

252


2010

SCM663


Item Number

1

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

4

Event Code

Z##_CARRARRIV

Generated From

CHECK_IN


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

5

Event Code

Z##_LOADBEG

Generated From

LOADING_BEGIN


Select this option



Calculation Rule



Select Do Not Set


2010


253


SCM663

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

6

Event Code

Z##_LOADEND

Generated From

LOADING_END


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

7

Event Code

Z##_PLANTDEP

Generated From

LOADING_END


Select this option



Duration

00:15

Duration Sign

Add Duration

Group Number

10

Item Number

6

Calculation Rule



Select Do Not Set Continued on next page

254


2010

SCM663


Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

8

Event Code

Z##_CUSTARRIV

Generated From

ARRIVAL_CUSTOMER


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

9

Event Code

Z##_UNLOAD

Generated From

ARRIVAL_CUSTOMER


Select this option



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item Number

8

Calculation Rule



Select Do Not Set Continued on next page

2010


255


SCM663

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

10

Event Code

Z##_POD

Generated From

ARRIVAL_CUSTOMER


Select this option



Duration

48:00

Duration Sign

Add Duration

Group Number

10

Item Number

8

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

a)

Select the group entry you just entered, then select Update Profile Items from the dialog structure on the left.

b)

Choose New Entries.

c)

Enter the item number from the table below.

d)

Enter the event code from the table below.

e)

Click F4 in the Generated From field.

f)

Enter T90CLNT090, or the application system code provided by your instructor, in the Applic. System field in the dialog box.

g)

Enter Z##_LTL_DELIV in the Appl. Obj. Type field in the dialog box. Choose Continue.


256


2010

SCM663


h)

Scroll through the EE Tag list until you find the expected event tag that corresponds to the event code you entered. Select the entry by double-clicking on it. Note: Make sure you select the tag with the correct language.

i)

Enter the remaining configuration settings from the table below.

j)

Choose Save.

k)

Click Next Entry icon to advance to the next entry.

l)

Repeat steps c) through k) for the remaining event codes in the table entries below.

m)

Choose Exit. Item

1

Event Code

Z##_PICKBEG

Generated From

PICKING_BEGIN


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

2

Event Code

Z##_PICKEND

Generated From

PICKING_BEGIN


Select this option



Duration

2:00

Duration Sign

Add Duration

Group Number


2010


257


SCM663

Item Number

1

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

3

Event Code

Z##_PACKING

Generated From

PICKING_BEGIN


Select this option



Duration

2:15

Duration Sign

Add Duration

Group Number

10

Item Number

1

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

4

Event Code

Z##_CARRARRIV

Generated From

CHECK_IN


258


2010

SCM663



Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

5

Event Code

Z##_LOADBEG

Generated From

LOADING_BEGIN


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

6

Event Code

Z##_LOADEND

Generated From

LOADING_END


2010


259



SCM663

Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

7

Event Code

Z##_PLANTDEP

Generated From

LOADING_END


Select this option



Duration

00:15

Duration Sign

Add Duration

Group Number

10

Item Number

6

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item


260


2010

SCM663


Event Code

Z##_CUSTARRIV

Generated From

ARRIVAL_CUSTOMER


Select this option



Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Item

9

Event Code

Z##_UNLOAD

Generated From

ARRIVAL_CUSTOMER


Select this option



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item Number

8

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location


2010


261


SCM663

Item

10

Event Code

Z##_POD

Generated From

ARRIVAL_CUSTOMER


Select this option



Duration

48:00

Duration Sign

Add Duration

Group Number

10

Item Number

8

Calculation Rule



Select Do Not Set

Check Partner

Select Do Not Check

Location Function

Select Do Not Set

Check Location

Select Do Not Check

Task 3: PART II The control, system and info parameters were already created in customizing by the exercises in Unit 6, “Configuring the Application System”. You can review the configured parameters in customizing under Event Management → Event Handlers and Event Handler Data → Parameters. For this exercise we will use the parameter profiles as they are currently defined. 1.

Define status attribute profile. a)

2.

see task

First, you need to define the status attributes for the delivery and transportation status as defined in the table below. Status Attribute Name

Z##_DEL_STATUS


Definable Value

Description

Delivery Status Continued on next page

262


2010

SCM663


3.

Status Attribute Name

Z##_TP_STATUS


Definable Value

Description

Transportation Status

a)

Navigate in the SCM/EM IMG to the table at: Event Management → Event Handlers and Event Handler Data → Status → Define Status Attributes

b)

Choose New Entries.

c)

Enter the status attributes from the table above.

d)

Choose Save.

Enter the status attribute values from the table below. Status Attribute Name

Status Attr. Value

Description

Z##_DEL_STATUS

DELAYED

Delayed

ON_TIME

On Time

ARRIVED

Arrived

IN_TRANSIT

In Transit

NOT_STARTED

Not Started

Z##_TP_STATUS

You need to create the status attribute profile and then assign the attributes you created to the profile. Enter status attribute profile Z##_LTL_STATUS and description Status Profile for Delivery in LTL Shipment. for Z##. a)

Select the status attribute name Z##_DEL_STATUS, then select Status Attribute Values from the dialog structure on the left.

b)

Choose New Entries.

c)

Enter the values from the table above for Z##_DEL_STATUS.

d)

Choose Enter, then Save.

e)

Select Status Attribute Names from the dialog structure on the left.

f)

Select the status attribute name Z##_TP_STATUS, then select Status Attribute Values from the dialog structure on the left.

g)

Choose New Entries.

h)

Enter the values from the table above for Z##_TP_STATUS.

i)


j)

Choose Back until you return to the IMG menu structure. Continued on next page

2010


263


4.

5.

SCM663

Now you need to create the status attribute profile and then assign the attributes you created to the profile. In SCM/EM customizing, go to Event Management → Event Handlers and Event Handler Data → Status → Define Status Attribute Profiles. Choose New Entries. Status Attribute Profile

Z##_LTL_STATUS

Description

Status Profile for Delivery in LTL Shipment. for Z##

a)

Navigate to the table at Event Management → Event Handlers and Event Handler Data → Status → Define Status Attribute Profiles

b)

Choose New Entries.

c)

Enter the status attribute profile and description from the table above.

d)


Select the new entry and enter the status attribute profile items. Status Attribute Name

Status Attribute Value

Z##_DEL_STATUS

ON_TIME

Z##_TP_STATUS

NOT_STARTED

a)

Select the Z##_LTL_STATUS entry in the table, then select Status Attribute Profile Items from the dialog structure on the left.

b)

Choose New Entries.

c)

Enter the status attribute names and values from the table above.

d)


e)

Choose Exit.

Task 4: Create the event handler condition record that will determine when an event handler is created. Your event handler type will be chosen when the ECC shipment has the shipping condition = SS, where SS = 50 + ## (your group number). 1.

Create the event handler condition that will be assigned to the event handler type. This condition will determine if an event handler will be created for a delivery.


264


2010

SCM663


Condition

Z##_SHIP_COND

Description

Shipping Condition for Z##

Shipping Condition (Control)

SS (your shipping condition)

a)

Navigate to the table at SCM/EM IMG: Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Conditions for Event Handler Types and Event Handler Sets.

b)

Select Event Handler Type Conditions from the dialog structure on the left.

c)

Choose New Entries.

d)

Enter the condition name and description from the table above.

e)


f)

Select Z##_SHIP_COND.

g)

Choose the Condition Editor icon from the application toolbar.

h)

In the Expression 1 box, scroll the entries and select Shipping Condition (Control) by double-clicking.

i)

Enter SS, your shipping condition code, in the Constant field, then choose Enter.

j)

Select “=” from the Operators box, then Enter.

k)

Select Transfer Condition (it’s the green check mark).

l)

Choose Save.

Task 5: Create the event handler type. 1.

Create the event handler type for the existing business process type for the shipment in SAP ECC and assign to it your expected events profile and your status attribute profile. Event Handler Type

Z##_EHT

Description

Event Handler Type for Z##

Business Process Type

ESC_SHPMT Shipment (SAP ECC)

Priority

1

Condition

Z##_SHIP_COND Continued on next page

2010


265


SCM663

Rule Set

LTL_RULES

Stat.Attr.Profile

Z##_LTL_STATUS

EE Profile

Z##_LTL_EXP_EVENTS

Ext.Table ID

DELIV_EXTENSION

BW Profile

DELIV_BW

Logs (EH Posting, Msg. Proc., Ext Update)

3 Verbose – Details of each process

a)

Navigate to the table at SCM/EM IMG: Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types

b)

Choose New Entries.

c)

Enter the data from the table above in the new event handler type entry.

d)


Task 6: Test your configuration by creating a shipment. 1.


OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-07-##


266


2010

SCM663




Material Number

P-102

Quantity Ordered

3

a)

Log into the SAP ECC system.

b)

Use transaction VA01 to create the sales order or choose: Logistics → Sales and Distribution → Sales → Order → Create

2.

c)

On the Initial Screen, enter the order type, sales organization, distribution channel and division. Choose Enter.

d)

On the Overview screen, enter the sold-to party, PO number, requested delivery date, material number and quantity. Choose Enter.

e)

Choose Save.

Create the outbound delivery document from the sales order. In the delivery, enter the pick deadline of today’s date + 2 business days and the picking time at 7:00 a.m. This will become the expected time for the Picking Begin event. Note Delivery Number: ____________________ a)

Use transaction VL01N, or choose from the SAP menu: Logistics → Sales and Distribution → Shipping and Transportation → Outbound Delivery → Create → Single Document → with Reference to Sales Order

3.

b)

Enter shipping point 1000. Enter the selection date as today + 2 business days. The sales order created in the previous exercise should appear in the Order field. Choose Enter.

c)

On the Overview screen, select the Picking tab. Enter the pick date of today’s date + 2 business days. Enter 07:00 in the Time field.

d)

Choose Save.

Create your shipment. Use the following data in the shipment creation process. Transportation Planning Point

1000

Shipment Type


Shipment Route

R00001

Shipping Condition

SS (your shipping condition code)


2010


267


SCM663

Date

Time

Check-In


11:00

Loading Start


11:15

Loading End


11:45

Shipment Completion


12:00

Shipment start


12:00

Shipment end


20:00


Shipment Stage

Date

Time

Start


12:00

End


20:00

Note Shipment Number _____________ a)

To create the shipment document use transaction VT01N or choose from the SAP menu: Logistics → Sales and Distribution → Shipping and Transportation → Shipment → Create → Single Documents

b)

In the Initial Screen, enter the transportation planning point and shipment type. Note: Make sure you have the Expert options set in the Customizing of Local Layout Options so that you can see the display of the shipment type codes.

c)

Select the Select Deliveries button in the application toolbar

d)


e)


f)

On the Create: Shipments and Deliveries screen, select the Overview of Current Shipment icon (the mountain and sun).

g)

Under the Processing tab in the upper section of the screen, enter the shipment route and the shipping condition.

h)



268


2010

SCM663


i)

4.

Enter the planning data from the data table below. When you save the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. Planning Dates and Times

Date

Time

Check-In


11:00

Loading Start


11:15

Loading End


11:45

Shipment Completion


12:00

Shipment start


12:00

Shipment end


20:00

j)


k)


l)

Choose the Stage details icon at the lower-left corner of the screen.

m)


n)


Date

Time

Start


12:00

End


20:00

o)

Select Copy at the bottom of the Details on Stage 0001 screen.

p)

Choose Save.

Verify that an event handler was created in SAP Event Management using your new event handler type. Log into the SAP SCM/Event Management system and run the Event Handler List and view the event handler that was created by the shipment in the previous step. Use event handler type Z##_EHT.


2010


269


SCM663

Check the list of expected events and verify that an event handler was created based on your new event handler type. a)

Log into the SAP SCM/Event Management system using the client number, user ID, and password provided by your instructor.

b)

Run the Event Handler List. SCM/EM: SAP Menu → Event Management → Monitoring and Lists → Event Handler List In the selection screen, enter Z##_EHT in the Event Handler Type field.

c)

Choose Execute.

d)

Select the Consolidated Events tab. Record the following:

e)

270

Picking Begin:

Date: _____________

Time: _____________

Picking End:

Date: _____________

Time: _____________

Loading Begin:

Date: _____________

Time: _____________

Loading End:

Date: _____________

Time: _____________

Select, by double-clicking, the expected events listed below and record the Int. EvtCd: Picking Begin:

________________________

Picking End:

________________________

Loading Begin:

________________________

Plant Departure:

________________________

Unloading:

________________________

f)

Select the Event Handler Detail Overview icon from the application toolbar.

g)

Select the Header Data tab. Record the following: AO Type:

________________________

EH Type:

________________________

Bus.Proc. Type:

________________________


2010

SCM663


Lesson Summary You should now be able to: • Describe how to change an event handler

2010


271

Unit Summary

SCM663

Unit Summary You should now be able to: • Create an event handler using your own configuration • Configure expected events • Configure event codes • Explain the purpose of tracking and query IDs • Define three types of parameters, including the origin and how to use them • Define status attribute types and status attribute profiles • Assign the status to the event handler type or event handler set • Define event handler type and event handler conditions • Describe the purpose of an event handler set • Describe how to change an event handler

272


2010

Unit 8 Event Notification – Configuration Unit Overview

Unit Objectives After completing this unit, you will be able to: • • •

Distinguish between internal and external messaging Configure mapping of events Configure layout of individual messages

Unit Contents Lesson: Event Notification - Configuration ..................................274 Exercise 5: Configure Layout of Individual Messages.................283

2010


273

Unit 8: Event Notification – Configuration

SCM663

Lesson: Event Notification - Configuration Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • • •

Distinguish between internal and external messaging Configure mapping of events Configure layout of individual messages

Business Example Which partner is communicating which event using what technology? You must determine where your data is coming from and determine how you will capture it to receive your actual event.

Figure 226: Event Notification - Roles

Event notification can be done by multiple people or functions whether internal or external to your physical system environment. Either way, SAP Event Management can receive information from sources to update the status of an event and cause a reaction.

274


2010

SCM663

Lesson: Event Notification - Configuration

Examples of internal notification include things such as when a production worker starts or completes an order, the transaction he or she runs causes an event handler to be created. It could also be a warehouse worker processing a goods issue or goods receipt or pick and pack function, or a buyer opening a purchase order, or possibly a quality manager rejecting a material. External notification examples could be the customer receiving product, a service provider updating when a product is shipped, or a subcontractor updating at the receipt of an order or shipment of materials.

Figure 227: Event Notification - Communication Channels

The previous slide shows the many different roles involved in event notification. This slide shows examples of the various communication channels and technologies available for event notification.

2010


275


SCM663

Figure 228: Example: Event Notification via The Web

This is an example of event notification via the Internet. In this example, the user logs onto SAP Event Management directly with a Web interface.

Figure 229: Example of Actual Date/Time

One result of the event notification is that the actual date and time are updated. Here you see the update on two separate screenshots: the query done from the Web communication layer and the Event Handler Overview in SAP Event Management available through transaction /SAPTRX/EH_LIST.

276


2010

SCM663


Figure 230: Notification: Using Event Codes

Event codes are used to decipher the event messages. You configure internal event codes and map them to external event codes if a partner wants to use his own code set. This screenshot shows the mapping of the external code to the internal code. To access this screen, in SCM/EM IMG choose: Event Management → Event Handlers and Event Handler Data → Codes → Event Codes → Define External Event Codes and How They Are Mapped.

Figure 231: Posting Event Messages in SAP EM

2010


277


SCM663

Starting with SAP Event Management 4.0, all event messages must be sent through remote function module /SAPTRX/BAPI_EH_ADDEVENTMSG_02. The BAPI is based on this function module. The IDoc and XI also call a remote function call to SAP Event Management with this function module.

Figure 232: Structure for Event Messages

The tracking ID enables SAP Event Management to find the right event handler to post the received message against. The event codes determine what event has taken place and should be updated for that event handler.

Figure 233: Measuring the Notification Compliance

278


2010

SCM663


When the message is received, SAP Event Management retains the date and time of the message. This information can be used in SAP BI to measure the reporting compliance of a partner.

Figure 234: Configuring Expected Message Date

2010


279


SCM663

The expected message date is calculated by the fields for date rule, duration, duration sign, group number, item number, calculation rule, tolerance, and tolerance rule: •

• • • •

• •

280

The Date Rule field indicates how the date will be set for the expected event message. By default, it is set based on the application system data in the milestone record that the expected event was generated from. It could also be associated with another expected event and set when the associated event is updated. For example, a response from the service provider is expected when a load is tendered so the expected event Response would be associated with the event Tender. The Duration field contains the duration that is added to or subtracted from the base date to calculate the expected date. The Duration Sign field indicates whether the value in the Duration field is to be added to or subtracted from the base date. The Group Number and Item Number fields identify the specific record to use as the basis for calculating the expected event message date. The Calculation Rule field indicates which date in the related expected event record is used as the basis for calculating the event message expected date. The expected event message duration is applied to this date to derive the expected event message date. The Tolerance field contains the duration used for calculating the earliest and latest expected event The Tolerance Rule indicates whether the duration in the Tolerance field is to be used to calculate the earliest or latest, or both the earliest and latest dates for the expected date.


2010

SCM663


Figure 235: Configuring Single Event Message Screen

In SAP Event Management, you can configure a transaction that can be used to update SAP Event Management directly with a radio frequency (RF) device without programming new screens. This transaction updates SAP EM directly. To access this transaction, in the SCM/EM IMG, choose: •

Event Management → Event Messages, Status Queries, and Web Interface → Define Layout for Individual Event Messages. Note: If you are using a text-based device, it is possible to use SAPConsole to provide the text to GUI translation.

Figure 236: Matching of Service Providers and Locations

When the event message is posted, SAP Event Management performs a match for the service provider and the location.

2010


281


SCM663

Figure 237: Assigning Matching Functions

To define the service provider and location matching under the configuration for activities for expected events: •

In SCM/EM IMG choose: SCM/EM : IMG: Event Management → Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events

• • •

Select your expected event profile and double-click Update Profile Groups on the left to select it. Select your profile group and double-click on Update Profile Items on the left. Select your expected event item and choose Details.

To assign the check partner and check location in the Expected Event Profile – Items, in SCM/EM IMG choose: •

282

Event Management → Event Handlers and Event Handler Data → Expected Events → Define Activities for Expected Events.


2010

SCM663


Exercise 5: Configure Layout of Individual Messages Exercise Objectives After completing this exercise, you will be able to: • Configure layout of individual messages • Report an event using configured transaction

Business Example In this exercise you will report events using an existing transaction, /SAPTRX/MI02, and then configure a new transaction that is available for reporting single events in SAP Event Management. You will then test your configuration by reporting a single event using that transaction against the event handler you created in the last exercise.

Task 1: You first need to configure the remaining fields in the Expected Event profile that were discussed in this unit. In the last exercise, you created the profile items for the Expected Event profile and you indicated the rules concerning the expected event date. Now you will configure the settings for the expected message date. 1.

In SCM/EM customizing, go to your expected event profile and then choose Update Profile Groups from the dialog structure on the left. For each of the expected events in your profile, update the Expected Message Date fields from the following tables. Set the expected event message date rules as follows: Event Code

Z##_PICKBEG

Expected Message Date Date Rule


Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

1

Calculation Rule

Expected Event Date


2010


283


Event Code

SCM663

Z##_PICKEND



Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

2

Calculation Rule

Expected Event Date

Event Code

Z##_PACKING



Duration

3:00

Duration Sign

Add Duration

Group Number

10

Item

3

Calculation Rule

Expected Event Date

Event Code

Z##_CARRARRIV



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

4

Calculation Rule

Expected Event Date

Event Code

Z##_LOADBEG



Duration

2:00

Duration Sign

Add Duration


284


2010

SCM663


Event Code

Z##_LOADBEG

Group Number

10

Item

5

Calculation Rule

Expected Event Date

Event Code

Z##_LOADEND



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

6

Calculation Rule

Expected Event Date

Event Code

Z##_PLANTDEP



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

7

Calculation Rule

Expected Event Date

Event Code

Z##_CUSTARRIV



Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

8

Calculation Rule

Expected Event Date


2010


285


Event Code

SCM663

Z##_UNLOAD



Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

9

Calculation Rule

Expected Event Date

Event Code

Z##_POD



Duration

24:00

Duration Sign

Add Duration

Group Number

10

Item

10

Calculation Rule

Expected Event Date

Task 2: Now, report events using an existing transaction. 1.

Use transaction /N/SAPTRX/MI02 and the following data to report the events listed below. Enter tracking code set DLNR and enter your delivery number with leading zeros from the previous exercise in the Tracking ID Code field. Choose Go.

2.

Report the following events: Picking Begin Picking End Packing Carrier Arrival


286


2010

SCM663


Load Begin Plant Departure Report the events on the dates and times expected. You may decide to enter these one at a time, or all at once. Check back to your Event Handler Overview to examine the result. 3.

Check the event messages in the Event Handler List.

Task 3: Now you want to report single events simulating a radio frequency device. You want to configure this transaction and then report an unexpected delay in the receipt to the customer. When you use this transaction, you want to enter the following data: Event Code Set, Event Code ID, Tracking ID Code Set, Tracking ID Code ID, Event Date, Event Time and Event Time Zone. You want to suppress all other fields. 1.

In SCM/EM customizing, create a layout profile using the data below and create the message table entries for the RF transaction. RF Event Message Profile

Z##_RF_PROFILE

Profile Description

RF Profile for ##

Default Field Attribute

Invisible, Inactive

EVTDAT Field Display Attribute

Visible, Input Allowed

Predefined Value

SY_DATLO

Cursor

Do not select

EVTID Field Display Attribute


Predefined Value

Z##_DELAYED

Cursor

Do not select

EVTTIM Field Display Attribute


Predefined Value

SY_TIMLO

Cursor

Do not select

EVTZON Field Continued on next page

2010


287


SCM663



Predefined Value

SY_ZONLO

Cursor

Do not select

TRXCOD Field Display Attribute


Predefined Value

DLNR

Cursor

Do not select

TRXID Field Display Attribute


Predefined Value Cursor

Select

Task 4: Create a new user group and assign the new RF message profile for your new user group. 1.

Create a new user group Z##_USER_GROUP with description User Group LTL Delivery.

2.

Now, assign your RF event message profile Z##_RF_PROFILE to your new user group.

3.

Now assign the user group in your user profile.

Task 5: Now test your configuration using the special RF transaction /N/SAPTRX/MI01 . Enter a delayed message using this transaction.

288

1.

Enter /n/SAPTRX/MI01 . This RF transaction is only accessible via transaction code.

2.

Check the Event Messages tab in the Event Handler List to see the posted delay message.


2010

SCM663


Solution 5: Configure Layout of Individual Messages Task 1: You first need to configure the remaining fields in the Expected Event profile that were discussed in this unit. In the last exercise, you created the profile items for the Expected Event profile and you indicated the rules concerning the expected event date. Now you will configure the settings for the expected message date. 1.

In SCM/EM customizing, go to your expected event profile and then choose Update Profile Groups from the dialog structure on the left. For each of the expected events in your profile, update the Expected Message Date fields from the following tables. Set the expected event message date rules as follows: Event Code

Z##_PICKBEG



Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

1

Calculation Rule

Expected Event Date

Event Code

Z##_PICKEND



Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

2

Calculation Rule

Expected Event Date

Event Code

Z##_PACKING


Relative to Unique Event Continued on next page

2010


289


SCM663

Event Code

Z##_PACKING

Duration

3:00

Duration Sign

Add Duration

Group Number

10

Item

3

Calculation Rule

Expected Event Date

Event Code

Z##_CARRARRIV



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

4

Calculation Rule

Expected Event Date

Event Code

Z##_LOADBEG



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

5

Calculation Rule

Expected Event Date

Event Code

Z##_LOADEND



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

6

Calculation Rule

Expected Event Date Continued on next page

290


2010

SCM663


Event Code

Z##_PLANTDEP



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

7

Calculation Rule

Expected Event Date

Event Code

Z##_CUSTARRIV



Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

8

Calculation Rule

Expected Event Date

Event Code

Z##_UNLOAD



Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

9

Calculation Rule

Expected Event Date

Event Code

Z##_POD



Duration

24:00

Duration Sign

Add Duration


2010


291


SCM663

Event Code

Z##_POD

Group Number

10

Item

10

Calculation Rule

Expected Event Date

a)

Navigate in SCM/IM IMG to: Event Management → Event Handlers and Event Handler Data → Expected Events → Define Profiles for Expected Events

b)

Select your expected event profile Z##_LTL_EXP_EVENTS, then select Update Profile Groups from the dialog structure on the left of the screen.

c)

Choose your group 10, and then select Update Profile Items from the dialog structure.

d)

Select all of the expected event items and choose Details.

e)

From the tables below, update each Expected Event with the configuration settings: Event Code

Z##_PICKBEG

Expected Message Date

f)

Date Rule


Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

1

Calculation Rule

Expected Event Date

Choose Next Entry or press F8 to advance to the next entry. Event Code

Z##_PICKEND



Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item


292


2010

SCM663


g)

Event Code

Z##_PICKEND

Calculation Rule

Expected Event Date


Z##_PACKING


h)

Date Rule


Duration

3:00

Duration Sign

Add Duration

Group Number

10

Item

3

Calculation Rule

Expected Event Date


Z##_CARRARRIV


i)

Date Rule


Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

4

Calculation Rule

Expected Event Date


Z##_LOADBEG



Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

5

Calculation Rule

Expected Event Date Continued on next page

2010


293


j)

SCM663


Z##_LOADEND


k)

Date Rule


Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

6

Calculation Rule

Expected Event Date


Z##_PLANTDEP


l)

Date Rule


Duration

2:00

Duration Sign

Add Duration

Group Number

10

Item

7

Calculation Rule

Expected Event Date


Z##_CUSTARRIV


m)

Date Rule


Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

8

Calculation Rule

Expected Event Date


Z##_UNLOAD Continued on next page

294


2010

SCM663


Event Code

Z##_UNLOAD


n)

Date Rule


Duration

1:00

Duration Sign

Add Duration

Group Number

10

Item

9

Calculation Rule

Expected Event Date


Z##_POD



Duration

24:00

Duration Sign

Add Duration

Group Number

10

Item

10

Calculation Rule

Expected Event Date

o)

Choose Save.

p)

Choose Exit.

Task 2: Now, report events using an existing transaction. 1.

Use transaction /N/SAPTRX/MI02 and the following data to report the events listed below. Enter tracking code set DLNR and enter your delivery number with leading zeros from the previous exercise in the Tracking ID Code field. Choose Go. a)

2.

see task

Report the following events:


2010


295


SCM663

Picking Begin Picking End Packing Carrier Arrival Load Begin Plant Departure Report the events on the dates and times expected. You may decide to enter these one at a time, or all at once. Check back to your Event Handler Overview to examine the result.

3.

a)

Enter /n/SAPTRX/MI02 in the Command field of the SAP SCM/EM system and choose Enter.

b)

Enter the tracking code set and tracking ID code, then choose Go.

c)

Enter the dates and times for each of the events above

d)

Select the events to which you posted dates and times.

e)


f)

On the Message Posting Confirmation screen, select Send.

g)

On the Event Confirmation screen, choose Exit.

Check the event messages in the Event Handler List. a)

In the SCM/EM System, navigate to Event Management → Monitoring and Lists → Event handler List

b)

Enter Z##_EHT in the Event Handler Type field and choose Execute.

c)

Select the Event Messages tab and review the posted messages.

Task 3: Now you want to report single events simulating a radio frequency device. You want to configure this transaction and then report an unexpected delay in the receipt to the customer. When you use this transaction, you want to enter the following data: Event Code Set, Event Code ID, Tracking ID Code Set, Tracking ID Code ID, Event Date, Event Time and Event Time Zone. You want to suppress all other fields. 1.

In SCM/EM customizing, create a layout profile using the data below and create the message table entries for the RF transaction.


296


2010

SCM663


RF Event Message Profile

Z##_RF_PROFILE

Profile Description

RF Profile for ##


Invisible, Inactive



Predefined Value

SY_DATLO

Cursor

Do not select



Predefined Value

Z##_DELAYED

Cursor

Do not select



Predefined Value

SY_TIMLO

Cursor

Do not select

EVTZON Field Display Attribute


Predefined Value

SY_ZONLO

Cursor

Do not select



Predefined Value

DLNR

Cursor

Do not select



Predefined Value Cursor a)

Select

In the SCM/EM IMG navigate to: Event Management → Event Messages, Status Queries and Web Interface → Define Layout for Individual Event Messages.

b)

Choose New Entries. Continued on next page

2010


297


c)

SCM663

Create an RF Event Message profile using the data below. RF Event Message Profile

Z##_RF_PROFILE

Profile Description

RF Profile for ##


Invisible, Inactive

d)

Select your new entry and select Message Tables from the dialog structure on the left. Choose New Entries.

e)

In the Used Message Tables area, select HEADER from the dropdown list.

f)

Select the entry you just created and then select Profile Details from the dialog structure on the left.

g)

Choose New Entries.

h)

Create an entry in the table for each of the fields below. EVTDAT Field Display Attribute


Predefined Value

SY_DATLO

Cursor

Do not select



Predefined Value

Z##_DELAYED

Cursor

Do not select



Predefined Value

SY_TIMLO

Cursor

Do not select

EVTZON Field Display Attribute


Predefined Value

SY_ZONLO

Cursor

Do not select



Predefined Value

DLNR Continued on next page

298


2010

SCM663


EVTDAT Field Cursor

Do not select



Predefined Value Cursor

Select

i)

Choose Enter twice through the message related to the cursor setting.

j)

Choose Save.

k)

Choose Back until you return to the RF Event Message Profiles screen.

Task 4: Create a new user group and assign the new RF message profile for your new user group. 1.

2.

3.

Create a new user group Z##_USER_GROUP with description User Group LTL Delivery. a)

Choose User Groups from the dialog structure on the left.

b)

Choose New Entries.

c)

Enter the data below in the User Group line.

Now, assign your RF event message profile Z##_RF_PROFILE to your new user group. a)

Double-click Assign Message Profiles to User Groups in the dialog structure on the left side.

b)

Choose New Entries and enter the name of your RF event message profile.

c)

Choose Enter and Save.

d)

Choose Exit.

Now assign the user group in your user profile. a)

Go to System → User Profile → Own Data.

b)

Select the Parameters tab.

c)

Enter USER_GROUP in the Parameter ID field.

d)

Enter Z##_USER_GROUP (in all caps) in the Parameter value field.

e)

Choose Enter and Save. Continued on next page

2010


299


SCM663

Task 5: Now test your configuration using the special RF transaction /N/SAPTRX/MI01 . Enter a delayed message using this transaction. 1.

2.

300

Enter /n/SAPTRX/MI01 . This RF transaction is only accessible via transaction code. a)

In the SCM/EM system, enter /n/SAPTRX/MI01 in the Command field. Choose Enter.

b)

Enter your RF profile Z##_RF_PROFILE in the Select Profile field, and choose Enter.

c)

In the Event Message Input screen, enter your delivery document number from the last exercise in the Tracking ID Code field with leading zeros

d)

Choose Go and Enter. This action will cause a delayed message in your event handler.

e)

Click the Exit-F9 button.

Check the Event Messages tab in the Event Handler List to see the posted delay message. a)

In the SCM/EM system navigate to Event Management → Monitoring and Lists → Event Handler List

b)

Enter Z##_EHT in the Event Handler Type field.

c)

Choose Execute.

d)

Select the Event Messages tab and see the delayed message.


2010

SCM663


Lesson Summary You should now be able to: • Distinguish between internal and external messaging • Configure mapping of events • Configure layout of individual messages

2010


301

Unit Summary

SCM663

Unit Summary You should now be able to: • Distinguish between internal and external messaging • Configure mapping of events • Configure layout of individual messages

302


2010

Unit 9 Reaction to Events – Configuration Unit Overview


Configure the system to define what happens after an event is posted Explain the connection of SAP Event Management to the Alert Framework Explain the connection of SAP Event Management to WebFlow

Unit Contents Lesson: Reaction to Events - Introduction...................................304 Lesson: Rule Sets, Rules, Conditions and Activities .......................308 Lesson: Informing and Alerts..................................................316 Lesson: Follow-Up Activities ..................................................324 Exercise 6: Rule Sets, Rules, Conditions and Procedures ...........327

2010


303

Unit 9: Reaction to Events – Configuration

SCM663

Lesson: Reaction to Events - Introduction Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Business Example Monitoring supply chain activities often requires different actions: • • •

Inform partners and systems about unplanned situations Trigger actions in SAP Event Management, for example, change event handler data Trigger actions in other systems, for example, update data in a purchasing document, trigger other processes such as rescheduling of planned data, and upload data to SAP Business Intelligence

Figure 238: Tools for Triggering Activities

304


2010

SCM663

Lesson: Reaction to Events - Introduction

Figure 239: Example When an Event Message is Posted

Here are some examples of what can happen when an event message is posted: • • • •

An existing event handler might be affected. All remaining dates and times in the expected event list might be rescheduled. An e-mail message could be sent to a customer or someone else within the supply chain. An invoice might be triggered in the application system.

Figure 240: Example When an Expected Event is Overdue

In the expected event profile, you define a rule set to be executed when an expected event is overdue.

2010


305


SCM663

A monitor in SAP Event Management checks for events that are expected but have not yet been received. These are overdue events. When an overdue event is detected, an alert can be raised in the application system or an activity can happen, for example, an e-mail can be sent to the appropriate contact.

306


2010

SCM663

Lesson: Reaction to Events - Introduction

Lesson Summary You should now be able to: •

2010


307


SCM663

Lesson: Rule Sets, Rules, Conditions and Activities Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Configure the system to define what happens after an event is posted

Business Example You must determine if an action needs to occur when an event message is posted.

Figure 241: Rule Sets

You define in Rule Sets how the system reacts to a reported event. Rule Sets are set up in SAP Event Management and assigned to the Event Handler Type. We can set up plug-in function modules that trigger other systems or methods that can be applied.

Figure 242: Rule Set Structure (1/2)

308


2010

SCM663

Lesson: Rule Sets, Rules, Conditions and Activities

The Rule Set is a set of rules that SAP EM evaluates when processing an event message. The rules processor evaluates the rules. The individual rule consists of a rule condition and an activity that is performed when the condition is true. The true and false rules determine the sequence in which the other rules of the rule set are evaluated.

Figure 243: Rule Set Structure (2/2)

Depending on whether the rule condition evaluation returns a TRUE or FALSE, SAP EM calls the activities that have been defined for the respective condition. The rule activity consists of one (single-task) or many (multi-task) activities that trigger the follow-up action (for example sending an email). The rule activity itself might be an event handler method, a function module or a multi-task activity. You can call several rule conditions within a rule by grouping several rule conditions in a set, which you call in the rule condition of the rule. You can call a BAPI within a function module and trigger activities in a remote system.

2010


309


SCM663

Figure 244: Process When an Event Message is Posted

When a message is received, the message is posted to SAP Event Management. SAP Event Management must locate the Event Handler and Event Handler Type. The rule set is connected to the Event Handler Type which calls the appropriate rule, finds the condition (set) and activity and finally executes the task.

Figure 245: Defining Rule Sets

This screen shot shows the customizing view for creating the rules. SCM/EM : IMG: Event Management → Reactions to Event Messages → Rules → Define Rule Sets.

310


2010

SCM663


Figure 246: Define Rule Condition

Define the rule condition. Conditions can also be put together in a condition set to allow more complex decisions. Later on, a condition set can be used like a condition.

Figure 247: Rule Details

Select Details to assign the rule conditions.

2010


311


SCM663

Figure 248: Metadata

To see the available meta data, place your cursor in an activity parameter field and select the Meta Data button. Activity metadata provides a means of passing dynamic application data as input parameters to Event Management activities. Enter one of the following enclosed by angle brackets (for example, ) in a parameter field of a single-task activity: The name of a required field from the Event Management activity interface structure, omitting the prefix I_EAI- , An event handler control parameter name preceded by CNTRL-, An event handler info parameter name preceded by INFO-, An event handler rule processing parameter name preceded by ACTIVITY- or afield from the ABAP system fields structure (SYST). Data is formatted by default for display. If the raw, internal data format is required (for example, to compare two dates), enter an exclamation mark in front of the parameter name (for example, ).

Figure 249: Follow-Up Activities

312


2010

SCM663


SAP EM enables Webflow for follow-up activities to occur. Webflow can be used to trigger the next sequence of activities.

Figure 250: WebFlow vs. SAP Event Management

Here you see some of the differences between Webflow and SAP Event Management. Supply Chain Performance Management (SPCM) provides metrics and reporting options that you can use as the basis for optimizing your supply chain.

Figure 251: Configuring WebFlow

2010


313


SCM663

The configuration of WebFlow looks the same as the interface to Alert Framework. In the rule set, we have a rule and an activity with tasks assigned. In the activities we have to have object type BOR.

Figure 252: Webflow Processing

This slide shows what happens when the event message is received.

Figure 253: List of Raised Events in Transaction SWEL

This transaction shows a list of raised events in the RFC destination system.

314


2010

SCM663


Lesson Summary You should now be able to: • Configure the system to define what happens after an event is posted

2010


315


SCM663

Lesson: Informing and Alerts Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain the connection of SAP Event Management to the Alert Framework


Who needs to be informed when an event notification takes place? You define who needs to be informed to react to normal, critical or unforeseen situations.

Figure 254: Alert Management Using the SAP Alert Framework

Alert management recognizes predefined critical situations and informs interested or responsible parties by sending them an alert without delay. Such critical situations may be an important customer terminating a contract or a budget being exceeded, for example. The alerts are delivered to the recipients in their alert inboxes, which are located in the enterprise portal. They can also be delivered using other channels, such as by Internet e-mail or to mobile devices. Alert management helps prevent delays in the processing of critical situations, because the time between discovering and processing such situations is reduced considerably.

316


2010

SCM663

Lesson: Informing and Alerts

Figure 255: Informing and Alerting Business Partners

The Alert Framework is provided as part of the SAP Web Application Server. The application must define its own alert categories and implement the triggering of the alert instances to realize alert management. Alerts can also be triggered by external alert providers. They are all sent to the alert inboxes of the alert recipients, but can additionally be sent by other channels, such as by Internet e-mail, text message (SMS), or to external alert systems. You must configure and schedule the processing of the alerts to meet your requirements.

2010


317


SCM663

Figure 256: Key Features of Alert Management

An application triggers an alert of a particular alert category based on an important or critical business or technical situation. The alert recipients are determined either by the application, by an administrator, or using a subscription procedure. An alert outlining the situation is delivered to the recipients without delay. The alert is delivered to the recipients in their alert inbox within the enterprise portal, and can also be delivered using other channels if the recipients have made the appropriate configuration. If the receipt of the alert is not confirmed by any of the recipients, the alert can be sent to an escalation recipient.

Figure 257: Setup of Alert Framework in SAP Event Management

318


2010

SCM663


In SAP Event Management, we use the rule set to set up the connection to the Alert Framework. You can define the rule that has a true procedure that is pre-defined. The procedure might have a task and an activity that is already there. You then need to set up a parameter ID for that activity. In the activity, you define the entry to customizing.

Figure 258: Assigning an Alert Category

You specify which alert category the system uses and how the container elements for this alert category are filled from SAP Event Management so you can use the Alert Framework for notification in certain situations, for example, if there is a delay or contamination. You can specify different alert categories for different critical situations. You assign the alert category within a processing step of a rule in the rule set. You use the activity parameter ID, which you have specified in this IMG activity, as the key. You can maintain a hyperlink, which you attach, for example, at the end of an e-mail. You can use the template for Customizing and adapt it to your own requirements. To define alert categories, in SCM/EM IMG choose: SCM/EM : IMG: Event Management → Reactions to Event Messages → Define Alert Framework Connection → Define Alert Categories.

2010


319


SCM663

Figure 259: Definition of Alert Container (1/2)

The alert container is a container for the exchange of application-specific variables, such as company code or material number, between the local systems or alert providers and the central alert server. The alert container is therefore the interface between the application that triggers the alert and the central Alert Framework.

Figure 260: Definition of Alert Container (2/2)

When you use application-specific variables in your container definition, you supply the values for these variables by writing them into the container as name-value pairs. These values are then interpreted by the Alert Framework on

320


2010

SCM663


the central system. The Alert Framework uses the alert container not only for the exchange of application-specific variables, but also for the exchange of internal information.

Figure 261: Example for Alert Inbox

When an alert is confirmed, it changes its status and will not be delivered, escalated, or displayed. Alerts are generally confirmed by recipients in their alert inbox. The alert inbox is implemented using ALERTINBOX, a Business Server Page application. However, if an alert is sent by Internet e-mail or text message, it is also possible to confirm it by sending an Internet e-mail or text message back to the SAP system. Alert management uses inbound processing for this.

Figure 262: System Landscape of Alert Management

2010


321


SCM663

Alert management can be run in the following modes: • • •

322

Local alert server (same system as local system) Central alert server (simultaneously for different SAP systems) Central alert server routing all alerts to an external partner product.


2010

SCM663


Lesson Summary You should now be able to: • Explain the connection of SAP Event Management to the Alert Framework

2010


323


SCM663

Lesson: Follow-Up Activities Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain the connection of SAP Event Management to WebFlow


Which action needs to be triggered when an actual event will be reported? You define what activities automatically need to start to react to normal, critical or unforeseen situations.

Figure 263: Follow-Up Activities

SAP EM enables Webflow for follow-up activities to occur. Webflow can be used to trigger the next sequence of activities.

324


2010

SCM663

Lesson: Follow-Up Activities

Figure 264: WebFlow vs. SAP Event Management

Here you see some of the differences between Webflow and SAP Event Management. Supply Chain Performance Management (SPCM) provides metrics and reporting options that you can use as the basis for optimizing your supply chain.

Figure 265: Configuring WebFlow

The configuration of WebFlow looks the same as the interface to Alert Framework. In the rule set, we have a rule and an activity with tasks assigned. In the activities we have to have object type BOR.

2010


325


SCM663

Figure 266: Webflow Processing

This slide shows what happens when the event message is received.

Figure 267: List of Raised Events in Transaction SWEL

This transaction shows a list of raised events in the RFC destination system.

326


2010

SCM663


Exercise 6: Rule Sets, Rules, Conditions and Procedures Exercise Objectives After completing this exercise, you will be able to: • Define rule sets • Define rule conditions • Define activities for rules • Define rule procedures

Business Example In this exercise we will configure the events that occur following the receipt of a message. For example, when the carrier arrives, or when the loading begins and ends, we want to update the shipment header. When the truck departs and arrives at the customer, we want to update the shipment stages. If the delivery is delayed, we need to send an email to the customer and we also need to reschedule any following events to account for the delay. In this exercise, you will configure the system to trigger these follow-up activities.

Task 1: Define Rule Sets 1.

Rules are executed when events are posted. The rule set contains all rules that are executed, depending on the conditions, when the event message for an event handler arrives. When an event message is received, the event handler type of the event handler is determined and the corresponding rule is found and executed. The table below provides an overview of the follow-up activities that we want to trigger: Reported Event

Status Changes in EH

Notification Updates

Arrival Carrier

Update shipment header

Loading Begin


Loading End

Update shipment header Continued on next page

2010


327


Reported Event Plant Departure

SCM663


Notification Updates Update shipment stage

Transportation Status = in transit

Arrival Customer

Update shipment stage

Transportation Status = arrived

Delayed

E-mail to customer

Deliver Status = delayed

2.

Reschedule all planned times for events following the delay

Define the rule set. Use the Copy As function to copy LTL_RULES to your new rule set as defined in the table below. Rule Set

Z##_LTL_RULES

Description

Z## Rule Set for LTL Delivery

Rules are stored within the rule set that triggers various activities. The rules that are used in the visibility process are defined in the following section. The individual rule consists of a rule condition and a rule activity that is executed based on the result of the evaluation. The rule activity consists of a single-task or multi-task activity that triggers event management activities, for example, sending an e-mail. The rule activity can be an event handler method, a function module or a multitask activity. Rule set Z##_LTL_RULES contains the following rules: • Process an event when it is reported (rule sequence 10) • Set the status of an event handler (rule sequence 20-40) • Send an e-mail to the customer (rule sequence 50) • Update the shipment in SAP ERP (rule sequence 60) • Update the shipment end date in SAP ERP (rule sequence 70) • Transfer data to SAP BW (rule sequence 80)

Task 2: Define Conditions 1.

A condition can be set for each rule. This condition is checked before the rule is executed. The events named above are only executed under the following conditions: Continued on next page

328


2010

SCM663


• If an event is reported: - Rule UPDATE_SHPM_GENERAL • If the event “Plant Departure” is reported: - Rule SET_STATUS_INTRANSIT • If the event “Delayed” is reported: - Rule SET_STATUS_DELAYED - Rule E-mail to customer • If the event “Arrival at Customer” is reported: - Rule SET_STATUS_ARRIVED - Rule UPDATE_SHPM_CUSTARR (if condition LAST_DELIV_FOUND also fulfilled) • If the Upload to BW events are reported: - Rule BW_UPLOAD 2.

The first step is to define the rule condition, and the second step is to assign that rule condition to the rule set. In this exercise we will create all of the rule conditions. Create the rule conditions based on the information in the table entries below. Condition

Z##_BWUPLOAD

Description

Event Code = “Upload to BW”

Condition Expression: Expression 1

Event Msg . Int. Event Code

Operator

=

Expression 2

BWUPLOAD

Condition

Z##_CUSTARRIV

Description

Event Code = “Arrival at Customer”



Operator

=

Expression 2

Z##_CUSTARRIV Continued on next page

2010


329


SCM663

Condition

Z##_DELAYED

Description

Event Code = “Delayed”



Operator

=

Expression 2

Z##_DELAYED

Condition

Z##_PLANTDEP

Description

Event Code = “Plant Departure”



Operator

=

Expression 2

Z##_PLANTDEP

Condition

Z##_GENERAL

Description

Event Code = “Arrival Carrier” to “Arrival at Customer”



Operator

=

Expression 2

Z##_CUSTARRIV

Logic

OR

Expression 1

Event Msg. . Int. Event Code

Operator

=

Expression 2

Z##_CARRARRIV

Logic

OR

Expression 1


Operator

=

Expression 2

Z##_LOADBEG

Logic

OR Continued on next page

330


2010

SCM663


3.

4.

Expression 1


Operator

=

Expression 2

Z##_LOADEND

Logic

OR

Expression 1


Operator

=

Expression 2

Z##_PLANTDEP

For the rule UPDATE_SHPM_GENERAL, create a rule condition set, consisting of the previously created condition rule Z##_CUSTARRIV and the example rule condition function LAST_DELIV_FOUND. Condition

Z##_SHIPMENT_ENDDATE

Description

If the Status for Each Delivery in the Shipment is “Arrival at Destination”

Condition Set Rule

AND

Condition Sequence

1

Condition

Z##_CUSTARRIV

Condition Sequence

2

Condition

LAST_DELIV_FOUND

An activity has been entered for the rule that checks whether Arrival at Customer has been reported for all deliveries in a shipment. When this is the case, the Shipment End field is updated in the SAP ERP shipment. We will not create an activity in this class, but you can view the rule procedures and rule conditions in customizing. Activity Functions:


2010


331


SCM663

Activity

Function Module/ Method Name

Activity Type

Description

ALERT_CREATE

/SAPTRX/CREATE_ALERT

Function Module

Integration of Alert Framework

BW_UPLOAD

/SAPTRX/BW_EXTRACTION2

Function Module

Upload Business Information Warehouse

Function /SAPSHIPModule MENT_DATE_UP- TRX/SET_ACT_SHIPMENT_DDL DATE

Update Actual Dates in the SAP ERP Shipment

Function /SAPTRX/SET_SHIP- Module MENT_ENDDATE

Update Actual Shipment End Date in the SAP ERP Shipment

SHIPMT_ENDDATE_UPDATE

Now, review some activity methods in the table below. Activity Methods: EE_PROCESS

ACT_PROCESS_EE

Method Process expected events

EVM_ETA_UPDATE

ACT_ETA_EVENT_MSG Method Update expected date for an ETA event

STATUS_SET

ACT_SET_STATUS

Method Set a status attribute

Rule condition functions are also defined in this area of the IMG. Review this function. Rule Condition Functions LAST_DELIV_FOUND

/SAPFunction Module TRX/FIND_LAST_DELIV

Check last delivery in shipment


332


2010

SCM663


5.

A rule in a rule set can contain either a single activity or a multitask activity that can include several individual tasks. In a previous exercise you defined some conditions for rule sets. Now you will assign them to the rules in the rule set you configured. In the SCM/EM IMG Define Rule Sets activity, access your rule set and change the rules to match the entries below. Rule Sequence

10

Rule

PROCESS_EE

Description

Process Expected Events

Activity

LTL_PROCESS_EE

Rule Sequence

20

Rule

SET_STATUS_INTRANSIT

Description

Set Transportation Status “In transit”

Condition

Z##_PLANTDEP

Activity

STATUS_SET

Log Task

Selected

Stat. Att. Name

Z##_TP_STATUS

Stat. Att. Val.

IN_TRANSIT

Rule Sequence

30

Rule

SET_STATUS_DELAYED

Description

Set Transportation Status “Delayed”

Condition

Z##_DELAYED

Log Task

Selected

Activity

STATUS_SET

Stat. Att. Name

Z##_DEL_STATUS

Stat. Att. Val.

DELAYED

Rule Sequence

40

Rule

SET_STATUS_ARRIVED

Description

Set Transportation Status “Arrived”

Condition

Z##_CUSTARRIV

Activity

STATUS_SET Continued on next page

2010


333


SCM663

Log Task

Selected

Stat. Att. Name

Z##_TP_STATUS

Stat. Att. Val.

ARRIVED

Rule Sequence

50

Rule

EMAIL_CUST

Description

Send E-mail to Customer

Condition

Z##_DELAYED

Activity

ALERT_CREATE

Log Task

Selected

Activity ID

LTL_DELIV

Rule Sequence

60

Rule

UPDATE_SHPM_GENERAL

Description

Update SAP ERP Shipment

Condition

Z##_GENERAL

Activity

SHIPMENT_DATE_UPDATE

Log Task

Selected

Rule Sequence

70

Rule

UPDATE_SHPM_CUSTARR

Description

Update SAP ERP Shipment (for Shipment End)

Condition


Activity

SHPMT_ENDDATE_UPDATE

Log Task

Selected

Rule Sequence

80

Rule

BW_UPLOAD

Description

Update BI

Condition

Z##_BWUPLOAD

Activity

BW_UPLOAD

Log Task

Selected


334


2010

SCM663


6.

Now assign your rule set, Z##_LTL_RULES, to your event handler type, Z##_EHT.

Task 3: Now you want to test your configuration by creating an event handler in SAP Event Management by creating a new shipment in the SAP ECC application system. Create a shipment for your pumps. 1.


OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-09-##



Material Number

P-102

Quantity Ordered

4

2.

Create the outbound delivery document from the sales order. In the delivery, enter the pick deadline of today’s date + 2 business days and the picking time at 1:00 a.m. This will become the expected time for the Picking Begin event.

3.

Note Delivery Number: _________________________

4.

Create the shipment document. Use the following data in the shipment creation process. Transportation Planning Point

1000

Shipment Type


Shipment Route

R00001

Shipping Condition

SS = Your Shipping Condition

Update the shipment planning dates with the data below.


2010


335


SCM663


Date

Time

Check-In


8:00

Loading Start


9:00

Loading End


10:00

Update the shipment stage with the following data: Shipment Stage

Date

Time

Start


11:00

End


22:00

Note shipment number _____________

Task 4: 1.

Check in SAP Event Management system to see if your event handler was created. Go to the Event Handler List in the SCM/EM system. Narrow the selection by choosing your event handler type Z##_EHT from the list.

2.

Using the knowledge you have gained from the previous exercises, post the events using the MI02 transaction to verify that you have configured the system correctly. Look back at the table used in the exercise “Define Rule Sets” to see if the appropriate updates occurred. Use transaction VT03N in the SAP ECC ERP system to display the fields in the shipment. Use transaction /N/SAPTRX/MI02 and the following data to report the events listed below. Tracking Code Set

DLNR

Tracking ID Code

Your delivery number with leading zeros from the previous exercise

Report the following events: Picking Begin Picking End Packing Carrier Arrival Loading Begin Continued on next page

336


2010

SCM663


Loading End Plant Departure Report the events on the dates and times expected. You may decide to enter these one at a time, or all at once. Check back to your Event Handler Overview to examine the result. 3.

Go back to the session with the Event Handler List using transaction /SAPTRX/EH_LIST and view how the event handler has been updated. Did the expected events change? Are there any new event messages? What are the statuses:

Delivery Status:

__________________


__________________

Did either of them change? 4.

Carrier Role Report a transportation delay using the Web Interface. Use the same logon data that you used to log in to the SCM/EM system. In the Actual Event Date and Actual Event Time fields enter a date and a time that is several hours after the Plant Departure. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field. Select Weather-Related or other suitable reason code. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or from the SCM/EM SAP menu choose: SCM/EM SAP Menu: Event Management → Web Interface → Search

5.

Go back to the session with the Event Handler List and view how the event handler has been updated. How does the delay appear on the Consolidated Events list? __________________________________________ __________________________________________ How does the delay appear on the Expected Event list? Explain: Continued on next page

2010


337


SCM663

__________________________________________ Is reason code shown on the Event Messages tab? Yes What is the delivery status? _____________________________ 6.

Carrier Role Report the carrier’s arrival at the customer and the unloading event using the MI02 transaction, and then check the status again. Enter the same date and time in the Actual Event Date and Actual Event Time as you see in the Planned Event Date/Time field in the Event Handler List. Use transaction /N/SAPTRX/MI02 and the following data to report the events listed below. Tracking Code Set

DLNR

Tracking ID Code


Report the events Arrival at Customer and Unloading. 7.

Go back to the session with the Event Handler List using transaction /SAPTRX/EH_LIST and view how the event handler has been updated. Did the expected events change? Are there any new event messages? What are the statuses:

Delivery Status:

__________________


__________________

Did either of them change?

338


2010

SCM663


Solution 6: Rule Sets, Rules, Conditions and Procedures Task 1: Define Rule Sets 1.

Rules are executed when events are posted. The rule set contains all rules that are executed, depending on the conditions, when the event message for an event handler arrives. When an event message is received, the event handler type of the event handler is determined and the corresponding rule is found and executed. The table below provides an overview of the follow-up activities that we want to trigger: Reported Event


Notification Updates

Arrival Carrier


Loading Begin


Loading End


Plant Departure


Transportation Status = in transit

Arrival Customer


Transportation Status = arrived

Delayed

Deliver Status =

E-mail to customer

delayed

a) 2.

Reschedule all planned times for events following the delay

see task

Define the rule set. Use the Copy As function to copy LTL_RULES to your new rule set as defined in the table below.


2010


339


SCM663

Rule Set

Z##_LTL_RULES

Description


Rules are stored within the rule set that triggers various activities. The rules that are used in the visibility process are defined in the following section. The individual rule consists of a rule condition and a rule activity that is executed based on the result of the evaluation. The rule activity consists of a single-task or multi-task activity that triggers event management activities, for example, sending an e-mail. The rule activity can be an event handler method, a function module or a multitask activity. Rule set Z##_LTL_RULES contains the following rules: • Process an event when it is reported (rule sequence 10) • Set the status of an event handler (rule sequence 20-40) • Send an e-mail to the customer (rule sequence 50) • Update the shipment in SAP ERP (rule sequence 60) • Update the shipment end date in SAP ERP (rule sequence 70)


340


2010

SCM663


• Transfer data to SAP BW (rule sequence 80) a)

In the SCM/EM IMG navigate to: Event Management → Reactions to Event Messages → Define Rule Sets.

b)

Select LTL_RULES and choose Copy As.

c)

Enter your rule set ID and description from the data in the table below.

d)

Choose Enter. When the “Specify object to be copied” message displays, choose Copy all.

e)

Choose Save. Rule Set

Z##_LTL_RULES

Description


Rules are stored within the rule set that triggers various activities. The rules that are used in the visibility process are defined in the following section. The individual rule consists of a rule condition and a rule activity that is executed based on the result of the evaluation. The rule activity consists of a single-task or multi-task activity that triggers event management activities, for example, sending an e-mail. The rule activity can be an event handler method, a function module or a multitask activity. Rule set Z##_LTL_RULES contains the following rules: • • • • • •

Process an event when it is reported (rule sequence 10) Set the status of an event handler (rule sequence 20-40) Send an e-mail to the customer (rule sequence 50) Update the shipment in SAP ERP (rule sequence 60) Update the shipment end date in SAP ERP (rule sequence 70) Transfer data to SAP BW (rule sequence 80)

Task 2: Define Conditions 1.

A condition can be set for each rule. This condition is checked before the rule is executed. The events named above are only executed under the following conditions: • If an event is reported: - Rule UPDATE_SHPM_GENERAL • If the event “Plant Departure” is reported: Continued on next page

2010


341


SCM663

- Rule SET_STATUS_INTRANSIT • If the event “Delayed” is reported: - Rule SET_STATUS_DELAYED - Rule E-mail to customer • If the event “Arrival at Customer” is reported: - Rule SET_STATUS_ARRIVED - Rule UPDATE_SHPM_CUSTARR (if condition LAST_DELIV_FOUND also fulfilled) • If the Upload to BW events are reported: - Rule BW_UPLOAD a) 2.

see task

The first step is to define the rule condition, and the second step is to assign that rule condition to the rule set. In this exercise we will create all of the rule conditions. Create the rule conditions based on the information in the table entries below. Condition

Z##_BWUPLOAD

Description




Operator

=

Expression 2

BWUPLOAD

Condition

Z##_CUSTARRIV

Description




Operator

=

Expression 2

Z##_CUSTARRIV


342


2010

SCM663


Condition

Z##_DELAYED

Description




Operator

=

Expression 2

Z##_DELAYED

Condition

Z##_PLANTDEP

Description




Operator

=

Expression 2

Z##_PLANTDEP

Condition

Z##_GENERAL

Description




Operator

=

Expression 2

Z##_CUSTARRIV

Logic

OR

Expression 1


Operator

=

Expression 2

Z##_CARRARRIV

Logic

OR

Expression 1


Operator

=

Expression 2

Z##_LOADBEG

Logic


2010


343


SCM663

Expression 1


Operator

=

Expression 2

Z##_LOADEND

Logic

OR

Expression 1


Operator

=

Expression 2

Z##_PLANTDEP

a)

In the SCM/EM IMG, navigate to Event Management → Reactions to Event Messages → Define Rule Sets

b)

Select Rule Conditions from the dialog structure on the left.

c)

Choose New Entries and enter the Condition and Description from the table entries below

d)

Choose Enter.

e)

Select the new rule condition.

f)

Choose the Condition Editor icon.

g)

Follow the instructions below each condition to create the condition.

h)

Repeat steps c through g for each condition below. Condition

Z##_BWUPLOAD

Description




Operator

=

Expression 2

BWUPLOAD

i)

Within the Condition Editor, in the Expression 1 area, select Int. Event Code from the Event Msg folder by double-clicking.

j)

Enter BWUPLOAD in the Constant field and choose Enter.

k)

Select “=” from the Operators area.

l)

Choose Transfer Condition (the green checkmark).

m)

Choose Save. Continued on next page

344


2010

SCM663


n)

Deselect the condition. Condition

Z##_CUSTARRIV

Description




Operator

=

Expression 2

Z##_CUSTARRIV

o)


p)

Enter Z##_CUSTARRIV in the Constant field and choose Enter.

q)


r)


s)

Choose Save.

t)


Z##_DELAYED

Description




Operator

=

Expression 2

Z##_DELAYED

u)


v)

Enter Z##_DELAYED in the Constant field and choose Enter.

w)


x)


y)

Choose Save.

z)

Deselect the condition. Continued on next page

2010


345


SCM663

Condition

Z##_PLANTDEP

Description




Operator

=

Expression 2

Z##_PLANTDEP

aa) Within the Condition Editor, in the Expression 1 area, select Int. Event Code from the Event Msg folder by double-clicking. ab) Enter Z##_PLANTDEP in the Constant field and choose Enter. ac) Select “=” from the Operators area. ad) Choose Transfer Condition (the green checkmark). ae) Choose Save. af)


Z##_GENERAL

Description




Operator

=

Expression 2

Z##_CUSTARRIV

Logic

OR

Expression 1


Operator

=

Expression 2

Z##_CARRARRIV

Logic

OR

Expression 1


Operator

=

Expression 2

Z##_LOADBEG

Logic


346


2010

SCM663


Expression 1


Operator

=

Expression 2

Z##_LOADEND

Logic

OR

Expression 1


Operator

=

Expression 2

Z##_PLANTDEP

ag) Within the Condition Editor, in the Expression 1 area, select Int. Event Code from the Event Msg folder by double-clicking. ah) Enter Z##_CUSTARRIV in the Constant field and choose Enter. ai)


aj)

Select “OR” from the Logic area.

ak) Repeat steps a. thru d. for the remaining conditions. Note: Make sure you don’t select “OR” on the last condition. al)


am) Choose Save. an) Deselect the condition. 3.

For the rule UPDATE_SHPM_GENERAL, create a rule condition set, consisting of the previously created condition rule Z##_CUSTARRIV and the example rule condition function LAST_DELIV_FOUND. Condition


Description


Condition Set Rule

AND


2010


347


4.

SCM663

Condition Sequence

1

Condition

Z##_CUSTARRIV

Condition Sequence

2

Condition

LAST_DELIV_FOUND

a)

In the SCM/EM IMG navigate to Event Management → Reactions to Event Messages → Define Rule Sets

b)

Select Rule Condition Sets from the dialog structure on the left. Choose New Entries.

c)

Enter the condition, description, and condition set rule from the table below.

d)

Choose Enter. Condition


Description


Condition Set Rule

AND

e)

Select your rule condition set and then select Condition Set Items from the dialog structure on the left.

f)

Choose New Entries.

g)

Enter the two condition sequences from the table below.

h)


i)

Stay in this screen for the next exercise below. Condition Sequence

1

Condition

Z##_CUSTARRIV

Condition Sequence

2

Condition

LAST_DELIV_FOUND

An activity has been entered for the rule that checks whether Arrival at Customer has been reported for all deliveries in a shipment. When this is the case, the Shipment End field is updated in the SAP ERP shipment. We will not create an activity in this class, but you can view the rule procedures and rule conditions in customizing. Continued on next page

348


2010

SCM663


Activity Functions: Activity

Function Module/ Method Name

Activity Type

Description

ALERT_CREATE


Function Module


BW_UPLOAD

/SAPTRX/BW_EXTRACTION2

Function Module


Function /SAPSHIPModule MENT_DATE_UP- TRX/SET_ACT_SHIPMENT_DDL DATE


Function /SAPTRX/SET_SHIP- Module MENT_ENDDATE


SHIPMT_ENDDATE_UPDATE

Now, review some activity methods in the table below. Activity Methods: EE_PROCESS

ACT_PROCESS_EE


EVM_ETA_UPDATE

ACT_ETA_EVENT_MSG Method Update expected date for an ETA event

STATUS_SET

ACT_SET_STATUS


Rule condition functions are also defined in this area of the IMG. Review this function. Rule Condition Functions LAST_DELIV_FOUND

/SAPFunction Module TRX/FIND_LAST_DELIV



2010


349


SCM663

a)

You should already be positioned in the proper screen from the last exercise; otherwise navigate in the SCM/EM IMG to Event Management → Reactions to Event Messages → Define Rule Sets.

b)

Double-click Activity Functions in the dialog structure. The following table contains examples of some of the activity functions that exist in the system:

c)

Find the corresponding activity functions from the table below and choose Details to review the entry. Activity Functions: Activity

Activity Type Function Module/ Method Name

Description

ALERT_CREATE


Function Module


BW_UPLOAD

Function /SAPTRX/BW_EX- Module TRACTION2


Function /SAPSHIPModule MENT_DATE_UP-TRX/SET_ACT_SHIPMENT_DDL DATE


Function SHIPMT_END- /SAPTRX/SET_SHIP-Module DATE_UPMENT_ENDDATE DATE


Now, review some the Activity Methods in the table below. d)

Double-click Activity Methods in the dialog structure. The following table contains examples of some of the activity methods that exist in the system:

e)

Find the corresponding activity methods from the table below and choose Details to review the entry. Activity Methods:


350


2010

SCM663


EE_PROCESS

ACT_PROCESS_EE


EVM_ETA_UPDATE

ACT_ETA_EVENT_MSGMethod Update expected date for an ETA event

STATUS_SET

ACT_SET_STATUS


Rule condition functions are also defined in this area of the IMG. 1.

2.

Double-click Rule Condition Functions in the dialog structure. The following table contains an example of a rule condition function that exists in the system: Find the corresponding rule condition function from the table below and choose Edit function module to review the entry.

Rule Condition Functions LAST_DELIV_FOUND

5.

Function Module /SAPTRX/FIND_LAST_DELIV


A rule in a rule set can contain either a single activity or a multitask activity that can include several individual tasks. In a previous exercise you defined some conditions for rule sets. Now you will assign them to the rules in the rule set you configured. In the SCM/EM IMG Define Rule Sets activity, access your rule set and change the rules to match the entries below. Rule Sequence

10

Rule

PROCESS_EE

Description


Activity

LTL_PROCESS_EE

Rule Sequence

20

Rule


Description

Set Transportation Status “In transit”

Condition

Z##_PLANTDEP Continued on next page

2010


351


SCM663

Activity

STATUS_SET

Log Task

Selected

Stat. Att. Name

Z##_TP_STATUS

Stat. Att. Val.

IN_TRANSIT

Rule Sequence

30

Rule

SET_STATUS_DELAYED

Description


Condition

Z##_DELAYED

Log Task

Selected

Activity

STATUS_SET

Stat. Att. Name

Z##_DEL_STATUS

Stat. Att. Val.

DELAYED

Rule Sequence

40

Rule

SET_STATUS_ARRIVED

Description


Condition

Z##_CUSTARRIV

Activity

STATUS_SET

Log Task

Selected

Stat. Att. Name

Z##_TP_STATUS

Stat. Att. Val.

ARRIVED

Rule Sequence

50

Rule

EMAIL_CUST

Description


Condition

Z##_DELAYED

Activity

ALERT_CREATE

Log Task

Selected

Activity ID

LTL_DELIV


352


2010

SCM663


Rule Sequence

60

Rule

UPDATE_SHPM_GENERAL

Description


Condition

Z##_GENERAL

Activity


Log Task

Selected

Rule Sequence

70

Rule

UPDATE_SHPM_CUSTARR

Description


Condition


Activity


Log Task

Selected

Rule Sequence

80

Rule

BW_UPLOAD

Description

Update BI

Condition

Z##_BWUPLOAD

Activity

BW_UPLOAD

Log Task

Selected

a)

In the SCM/EM IMG navigate to: Event Management → Reactions to Event Messages → Define Rule Sets.

b)

Select your rule set, Z##_LTL_RULES, and choose Rules from the dialog structure.

c)

Choose Select all then choose Details.

d)

Check each rule in the IMG table against the corresponding entries below and change the rules in the table to match the entries below.

e)

After checking and, if required, modifying, a rule, -click the Next Entry icon.

f)

After checking or modifying the last rule, choose Save.

g)

Choose Exit. Rule Sequence


2010


353


SCM663

Rule

PROCESS_EE

Description


Activity

LTL_PROCESS_EE

Rule Sequence

20

Rule


Description

“Set Transportation Status “In transit””

Condition

Z##_PLANTDEP

Activity

STATUS_SET

Log Task

Selected

Stat. Att. Name

Z##_TP_STATUS

Stat. Att. Val.

IN_TRANSIT

Rule Sequence

30

Rule

SET_STATUS_DELAYED

Description


Condition

Z##_DELAYED

Log Task

Selected

Activity

STATUS_SET

Stat. Att. Name

Z##_DEL_STATUS

Stat. Att. Val.

DELAYED

Rule Sequence

40

Rule

SET_STATUS_ARRIVED

Description


Condition

Z##_CUSTARRIV

Activity

STATUS_SET

Log Task

Selected

Stat. Att. Name

Z##_TP_STATUS

Stat. Att. Val.

ARRIVED


354


2010

SCM663


Rule Sequence

50

Rule

EMAIL_CUST

Description


Condition

Z##_DELAYED

Activity

ALERT_CREATE

Log Task

Selected

Activity ID

LTL_DELIV

Rule Sequence

60

Rule

UPDATE_SHPM_GENERAL

Description


Condition

Z##_GENERAL

Activity


Log Task

Selected

Rule Sequence

70

Rule

UPDATE_SHPM_CUSTARR

Description


Condition


Activity


Log Task

Selected

Rule Sequence

80

Rule

BW_UPLOAD

Description

Update BI

Condition

Z##_BWUPLOAD

Activity

BW_UPLOAD

Log Task

Selected


2010


355


6.

SCM663

Now assign your rule set, Z##_LTL_RULES, to your event handler type, Z##_EHT. a)

In the SCM/EM IMG, navigate to Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types.

b)

Double-click on your event handler type, Z##_EHT, and enter rule set Z##_LTL_RULES.

c)

Choose Save.

d)

Choose Exit.

Task 3: Now you want to test your configuration by creating an event handler in SAP Event Management by creating a new shipment in the SAP ECC application system. Create a shipment for your pumps. 1.


OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-09-##



Material Number

P-102

Quantity Ordered

4

a)

Log into the SAP ECC application system.

b)

To create sales order, use transaction VA01 or the menu: Logistics → Sales and distribution → Sales → Order → Create

c)

On the Initial Screen, enter the order type, sales organization, distribution channel and division. Choose Enter.

d)

On the Overview screen, enter the sold-to party, PO number, requested delivery date, material number and quantity. Choose Enter.

e)

Choose Save.


356


2010

SCM663


2.

Create the outbound delivery document from the sales order. In the delivery, enter the pick deadline of today’s date + 2 business days and the picking time at 1:00 a.m. This will become the expected time for the Picking Begin event. a)

Use transaction VL01N, or from the SAP menu choose: Logistics → Sales and Distribution → Shipping and Transportation → Outbound Delivery → Create → Single Document → with Reference to Sales Order

3.

b)

Enter shipping point 1000. Enter the selection date as today + 2 business days. The sales order created in the previous exercise should appear in the Order field. Choose Enter.

c)

On the Overview screen, select the Picking tab. In the Pick/Date Time field, enter the pick date of today’s date + 2 business days. Enter 01:00 in the Time field.

d)

Choose Save.

Note Delivery Number: _________________________ a)

4.

see task


1000

Shipment Type


Shipment Route

R00001

Shipping Condition


Update the shipment planning dates with the data below. Planning Dates and Times

Date

Time

Check-In


8:00

Loading Start


9:00

Loading End


10:00

Update the shipment stage with the following data: Shipment Stage

Date

Time

Start


11:00

End


22:00 Continued on next page

2010


357


SCM663

Note shipment number _____________ a) Transportation Planning Point

1000

Shipment Type


Shipment Route

R00001

Shipping Condition


To create the shipment document, use transaction VT01N or from the SAP menu choose: Logistics → Sales and Distribution → Shipping and Transportation → Shipment → Create → Single Documents b)

In the Initial Screen, enter the transportation planning point and shipment type. Note: Make sure you have the Expert options set in the Customizing of Local Layout Options so that you can see the display of the Shipment Type codes.

c)

Click the Select Deliveries button in the application toolbar.

d)


e)

Choose the Execute icon at the lower-left corner of the Select outbound deliveries screen.

f)

On the Create: Shipments and Deliveries screen, click the Overview of Current Shipment icon (the mountain and sun).

g)

Under the Processing tab in the upper section of the screen, enter the shipment route and the shipping condition.

h)

In the Deadl. portion of the screen, choose the Planning button.

i)

Enter the planning data from the data table below. When you save the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. Planning Dates and Times

Date

Time

Check-In


8:00


358


2010

SCM663



Date

Time

Loading Start


9:00

Loading End


10:00

j)


k)


l)

Choose the Stage details icon at the lower-left corner of the screen.

m)


n)


Date

Time

Start


11:00

End


22:00

o)

Choose the Copy button at the bottom of the Details on Stage 0001 screen.

p)

Choose Save. Note Shipment Number _____________

Task 4: 1.

Check in SAP Event Management system to see if your event handler was created. Go to the Event Handler List in the SCM/EM system. Narrow the selection by choosing your event handler type Z##_EHT from the list. a)

In the SCM/EM system, navigate to Event Management → Monitoring and Lists → Event handler List

b)

Enter Z##_EHT in the Event Handler Type field and choose Execute.

c)

Select the Event Messages tab and review the posted messages.

d)

Stay in the Event handler List session to check the event message that will be posted in the next exercises.


2010


359


2.

SCM663

Using the knowledge you have gained from the previous exercises, post the events using the MI02 transaction to verify that you have configured the system correctly. Look back at the table used in the exercise “Define Rule Sets” to see if the appropriate updates occurred. Use transaction VT03N in the SAP ECC ERP system to display the fields in the shipment. Use transaction /N/SAPTRX/MI02 and the following data to report the events listed below. Tracking Code Set

DLNR

Tracking ID Code


Report the following events: Picking Begin Picking End Packing Carrier Arrival Loading Begin Loading End Plant Departure Report the events on the dates and times expected. You may decide to enter these one at a time, or all at once. Check back to your Event Handler Overview to examine the result.

3.

a)


b)

Enter tracking code set DLNR and the tracking ID code, then choose Go.

c)

Enter the dates and times for each of the events above.

d)

Select the events to which you posted dates and times.

e)


f)

On the Message Posting Confirmation screen, choose Send.

g)


Go back to the session with the Event Handler List using transaction /SAPTRX/EH_LIST and view how the event handler has been updated. Did the expected events change? Continued on next page

360


2010

SCM663


Are there any new event messages? What are the statuses:

Delivery Status:

__________________


__________________


4.

a)


b)

Select the Expected Events tab. Answer the question above.

c)

Click the Refresh icon. It’s the first icon on the left.

d)

Select the Event Messages tab. Answer the question above.

e)


f)


Carrier Role Report a transportation delay using the Web Interface. Use the same logon data that you used to log in to the SCM/EM system. In the Actual Event Date and Actual Event Time fields enter a date and a time that is several hours after the Plant Departure. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field. Select Weather-Related or other suitable reason code. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction /N/SAPTRX/EM_START or from the SCM/EM SAP menu choose: SCM/EM SAP Menu: Event Management → Web Interface → Search a)


Enter your user name. Enter your password. Select the language, if necessary. Click Log on. Note: You must use the pushbutton, the Enter key does not work.

b)

Select tracking scenario Carrier’s Delivery. Continued on next page

2010


361


SCM663

c)


d)

Choose Apply.

e)

Click on Send Event Messages and select Report Delay. The Report Delay screen should appear.

f)

Enter a date and time in the Actual Event Date and Actual Event Time fields that is several hours after the plant departure. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field.

5.

g)

Select Weather-Related or other reason in the Reason Code field.

h)

Choose Send.

i)

Close the Window. Select the Shipment and click on Display Details. A new window opens up with the event details of the shipment. Click Page Down until you see the Unplanned Event – Delay event. Verify that your actual date is present. You will see the update immediately in the Web Interface.

j)

Close the Web Interface screen

Go back to the session with the Event Handler List and view how the event handler has been updated. How does the delay appear on the Consolidated Events list? __________________________________________ __________________________________________ How does the delay appear on the Expected Event list? Explain: __________________________________________ Is reason code shown on the Event Messages tab? Yes


362


2010

SCM663


What is the delivery status? _____________________________

6.

a)


b)

Select the Consolidated Events tab.

c)

Click the Refresh icon. It’s the first icon on the left. Answer the question above.

d)


e)


f)


g)

Answer the question listed above.

Carrier Role Report the carrier’s arrival at the customer and the unloading event using the MI02 transaction, and then check the status again. Enter the same date and time in the Actual Event Date and Actual Event Time as you see in the Planned Event Date/Time field in the Event Handler List. Use transaction /N/SAPTRX/MI02 and the following data to report the events listed below. Tracking Code Set

DLNR

Tracking ID Code


Report the events Arrival at Customer and Unloading.

7.

a)


b)

Enter the tracking code set and tracking ID code, then choose Go.

c)

Enter the dates and times for each of the events above.

d)

Select the events to which you posted dates and times

e)

Select Post selected messages.

f)

On the Message Posting Confirmation screen, choose Send.

g)


Go back to the session with the Event Handler List using transaction /SAPTRX/EH_LIST and view how the event handler has been updated. Did the expected events change? Are there any new event messages? Continued on next page

2010


363


What are the statuses:

SCM663

Delivery Status:

__________________


__________________


364

a)


b)


c)

Click the Refresh icon. It’s the first icon on the left.

d)


e)


f)



2010

SCM663


Lesson Summary You should now be able to: • Explain the connection of SAP Event Management to WebFlow

2010


365

Unit Summary

SCM663

Unit Summary You should now be able to: • • Configure the system to define what happens after an event is posted • Explain the connection of SAP Event Management to the Alert Framework • Explain the connection of SAP Event Management to WebFlow

366


2010

Unit 10 Web Interface Unit Overview

Unit Objectives After completing this unit, you will be able to: • • • • •

Understand the SAP Event Management User Interface option Understand the features available in new Web Interface (Web Dynpro ABAP) Configure filtering profiles Configure authorization profiles Define conditions for data filtering

Unit Contents Lesson: Web User Interface...................................................368 Lesson: Authorization and Filters .............................................396 Exercise 7: Configuring Screen Layouts for Web Interface...........401

2010


367

Unit 10: Web Interface

SCM663

Lesson: Web User Interface Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • •

Understand the SAP Event Management User Interface option Understand the features available in new Web Interface (Web Dynpro ABAP)

Business Example You have a requirement to provide employees and partners with visibility into your defined processes across your entire supply chain. To do this you will need to configure screen layouts and authorizations.

Figure 268: Web Interface

Recommendation •

368

SAP recommend that you use the Web interface (Web Dynpro ABAP). SAP will continue to support the Web interface (classic), but we will not develop it any further.


2010

SCM663

Lesson: Web User Interface

Figure 269: Web Interface (Web Dynpro ABAP) Features

Only the Web interface displays the network. You cannot display the network in SAP Event Management. If you have the appropriate authorization in your user profile, the authorization concept allows you to display detailed information about the network and to execute a drilldown.

Figure 270: Web Interface (Web Dynpro ABAP) supported Configuration


Figure 271: Web Interface (Web Dynpro ABAP) - Functionality currently not supported

2010


369


SCM663


Figure 272: Web Interface - Profiles and Transactions

To allow people to see the Web interface, you need to have the Web Interface transaction and the user profile. The Web Interface transaction defines the processes that are available. The processes are shown in a dropdown box on selection screen. The user profile specifies what you see in the selection screen and what is displayed in the details of the event handler. Selection and display are assigned to the user profile. If you also allow the update, then you must also assign the notification to the user profile.

370


2010

SCM663


Figure 273: Assigning Profiles and Transactions for Vis. Process

The Web Interface transaction is assigned to the user profile, which is assigned to the user. A user might have multiple user profiles that enable him or her to access views from the WCL.

Figure 274: Configuring Fields for User Profiles

The fields that will be used in the user profiles must be defined and then assigned to the user profile.

2010


371


SCM663

Figure 275: Search

Figure 276: Search Result Overview

372


2010

SCM663


Figure 277: Display Details

Figure 278: Display Details

2010


373


SCM663

Figure 279: Display Event Details

Figure 280: Display Event Details

374


2010

SCM663


Figure 281: Reporting a Single Event

Figure 282: Reporting a Single Event

2010


375


SCM663

Figure 283: Multiple Event Message Sending

Figure 284: Reporting all Expected Events

376


2010

SCM663


Figure 285: Reporting all Expected Events

Figure 286: Document Flow (1)

2010


377


SCM663



378


2010

SCM663


Figure 289: Sending Measurement Data

Figure 290: Sending Measurement Data

2010


379


SCM663

Figure 291: Measurement Data

Figure 292: Measurement Data

380


2010

SCM663


Figure 293: Event Handler Hierarchy

Figure 294: Event Handler Hierarchy

2010


381


SCM663

Figure 295: Drill-down another Event Handler

Figure 296: Drill-down another Event Handler

382


2010

SCM663


Figure 297: Add an attachment during Event Message sending

Figure 298: Show attachment on Display screen

2010


383


SCM663

Figure 299: Show Attachment as example here a PDF was uploaded

Figure 300: General Information - Web Interface (Web Dynpro ABAP)

384


2010

SCM663


Figure 301: Initial Screen

Figure 302: Hide UI elements on a screen

2010


385


SCM663

Figure 303: Restore UI elements on a screen

Figure 304: Hide a single input field

386


2010

SCM663


Figure 305: Set default value

Figure 306: Initial Result Screen

2010


387


SCM663

Figure 307: Set Filter

Figure 308: Settings - Column Selection

388


2010

SCM663


Figure 309: Settings - Sorting

Figure 310: Settings - Filter

2010


389


SCM663

Figure 311: Settings - Display

Figure 312: Settings - Display

390


2010

SCM663


Figure 313: Settings - Save

Figure 314: Settings - Result

2010


391


SCM663

Figure 315: Detail Screen - before

Figure 316: Detail Screen - afterwards

392


2010

SCM663


Figure 317: Administrator

Figure 318: Change Logo or Branding

2010


393


SCM663



394


2010

SCM663


Lesson Summary You should now be able to: • Understand the SAP Event Management User Interface option • Understand the features available in new Web Interface (Web Dynpro ABAP)

2010


395


SCM663

Lesson: Authorization and Filters Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • • •

Configure filtering profiles Configure authorization profiles Define conditions for data filtering

Business Example You want to restrict access to certain users so that they can view only specific event handlers or parts of event handlers.

Figure 321: Authorization and Filtering

This is how we ensure that people, including partners and employees, see only what they are supposed to see. The authorization checks to see if the user is allowed to view the event handler. The filter shows which fields are allowed for viewing. To set up authorizations and filters, in SCM/EM IMG choose: Event Management → Authorizations and Filters.

396


2010

SCM663

Lesson: Authorization and Filters

Figure 322: Authorization Profile

An authorization profile is assigned to the event handler type. This depends on the event handler type; it is not user dependent. Here event handlers are created, for example, for various customers. In the authorization profile, an info parameter is set up to check the Customer field, which is stored together with the event handler.

Figure 323: Authorization for EH Creation and Status Retrieval

We check the authorization profile at the event handler type. The parameter set is determined in the authorization profile and the value of the Parameter field is saved with the event handler.

2010


397


SCM663

When the customer wants to retrieve the information, SAP Event Management checks the role and the authorization object to decide whether the event handler is shown.

Figure 324: Authorization Objects and Profiles

The authorization profile is assigned to the user. The user specifies the role and the authorization object.

Figure 325: Filtering is Tied to the User

Filtering checks what exact data of the event handler is displayed in the event handler list. For example, here the filter profile is assigned to the carrier.

398


2010

SCM663


Figure 326: Filter Profiles

When requesting information, the system checks for the filter profile, which depends on the user and the event handler type. Filtering has different levels: table restrictions, field restrictions, and row restrictions. You can filter for specific event codes only.

Figure 327: Creating Filter Profiles

To set up filter profiles, in SCM/EM IMG choose: Event Management → Authorizations and Filters → Define Filter Profiles.

2010


399


SCM663

Figure 328: Assigning Filter Profiles to Users

The screenshot on the left is found in customizing at: •

SCM/EM: IMG: Event Management → Authorizations and Filters → Assign Filter Profiles to Users.

The screenshot on the right is found in customizing at: •

400

SCM/EM: IMG: Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Set Profiles.


2010

SCM663


Exercise 7: Configuring Screen Layouts for Web Interface Exercise Objectives After completing this exercise, you will be able to: • Configure screen layouts for status retrieval and sending event messages using profiles for selection, display and event messaging

Business Example In your implementation, you want to allow visibility of the event handler status to selected parties within the supply chain via an Internet connection. In this exercise you will configure the Web Interface to accomplish that.

Task 1: Web Interface Transactions are used in the Web Interface selection screen. When you select the text field, the corresponding user profile is used. You can assign several combinations of a Web Interface transaction and a user profile to a user and the selection screens in the Web Interface then change accordingly. 1.

2.

Define the Web Interface transaction. Create a Web Interface transaction from the data in the table below. Web Interface Transaction

Tracking Scenario

EH Set Indicator

Z##_LTL_CUSTOMER

Customer’s Delivery Z##

No EH Sets

Define the fields for user profiles. To do this, you configure fields to be used in the Web Interface. Fields that can be selected are chosen from the info parameters, control parameters, system parameters, status profiles, and event message data. These fields are ultimately then assigned in the display profile, selection profile and event message profile. In this workshop, we will use the fields as they are configured. You can go into customizing and look at the setup, and we will add one new field for display in this section. Display the following fields that are already configured for display: LTL_DELIV_NUMBER LTL_DEL_STATUS LTL_EVENT_CODE Continued on next page

2010


401


SCM663

LTL_EVENT_DESCRIPT LTL_EVENT_MSG_DATE LTL_EVENT_MSG_TIME LTL_EXP_DATE LTL_EXP_TIME LTL_PO_NUMBER LTL_REASONCODE LTL_REP_DATE LTL_REP_TIME LTL_SHIPMENT_NUMBER LTL_SHIP_TO_CITY LTL_SHIP_TO_COUNTRY LTL_SHIP_TO_PARTY LTL_SHIP_TO_REGION LTL_SHIP_TO_STREET LTL_TP_STATUS 3.

4.

Add a new configured field for display from the data in the table below. Configured Field

Z##_LTL_EVENT_ICON

EM Attribute ID

STATUS ICON (choose from F4)

Short Description Text

Status icons Z##

Review some of the configured fields for selection that are listed below: LTL_DEL_STATUS LTL_EH_ACTIVE LTL_EH_TYPE LTL_PO_NUMBER LTL_SHIPMENT_NUMBER LTL_TP_STATUS LTL_SHIP_TO_PARTY

5.

Review some of the configured fields for event messages that are listed below: Continued on next page

402


2010

SCM663


LTL_REASONCODE LTL_REP_DATE_MESSAGE LTL_REP_TIME_MESSAGE LTL_REP_TZ_MESSAGE 6.

Review some of the groups of the configured fields that are listed below. LTL_EXP_DATE_TIME LTL_REP_DATE_TIME LTL_SHIP_TO_ADDR

7.

Create a user profile by joining together the display profile, selection profile and event message profile. When you assign a user to a user profile, the user can then select and display data and confirm events when logged on to the Web Interface. The event message profile is optional if the user does not need to confirm events in the Web Interface. Create a new selection profile by copying an existing profile, LTL_SEL_CUSTOMER, with all of its existing entries.

8.

Create a new display profile by copying an existing profile LTL_DISP_CUSTOMER and its existing entries. After the Display profile is created, add the new Configured Field, Z##_LTL_EVENT_ICON to the profile. Configured Field

Z##_LTL_EVENT_ICON

Display Level Ind

All Screens

Ord Table Ord Detail 9.

Create a new event messages profile by copying an existing event message profile and its dependent entries. In the new Z##_LTL_MES_CUSTOMER profile, change internal event code POD to your new internal event code Z##_POD.

10. Assign these profiles to your new user profile. User Profile ID

Z##_LTL_DEL_CUSTOMER

Text

User Profile Z##

Event Message Profile

Z##_LTL_MES_CUSTOMER

Display Profile

Z##LTL_DISP_CUSTOMER

Selection Profile

Z##_LTL_SEL_CUSTOMER Continued on next page

2010


403


SCM663

11. After deleting the existing LTL_CUSTOMER transaction, add your new Z20_LTL_CUSTOMER transaction to your logon user ID. Web Int. Tran.

Z##_LTL_CUSTOMER

User Profile ID


Order Web

1

Task 2: Customer POD Now test your configuration by updating the event handler created in the exercises for Unit 9, “Reaction to Events – Configuration”. 1.

Report the customer’s proof of delivery (POD) via the Web Interface, and then check the status. Also, verify that your new status icon appears on the Z## Customer’s Delivery Details screen. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction //N/SAPTRX/EM_START or with the following path from the SCM/EM SAP menu: SCM/EM SAP Menu: Event Management → Web Interface → Search

404


2010

SCM663


Solution 7: Configuring Screen Layouts for Web Interface Task 1: Web Interface Transactions are used in the Web Interface selection screen. When you select the text field, the corresponding user profile is used. You can assign several combinations of a Web Interface transaction and a user profile to a user and the selection screens in the Web Interface then change accordingly. 1.

2.

Define the Web Interface transaction. Create a Web Interface transaction from the data in the table below. Web Interface Transaction

Tracking Scenario

EH Set Indicator

Z##_LTL_CUSTOMER


No EH Sets

a)

In the SCM/EM IMG navigate to: Event Management → Event Messages, Status Queries and Web Interface → Web Interface → Define Web Interface Transactions.

b)

Choose New Entries.

c)

Enter the data from the table below.

d)

Choose Enter, and then Save.

e)

Choose Exit. Web Interface Transaction

Tracking Scenario

EH Set Indicator

Z##_LTL_CUSTOMER


No EH Sets

Define the fields for user profiles. To do this, you configure fields to be used in the Web Interface. Fields that can be selected are chosen from the info parameters, control parameters, system parameters, status profiles, and event message data. These fields are ultimately then assigned in the display profile, selection profile and event message profile. In this workshop, we will use the fields as they are configured. You can go into customizing and look at the setup, and we will add one new field for display in this section. Display the following fields that are already configured for display:


2010


405


SCM663

LTL_DELIV_NUMBER LTL_DEL_STATUS LTL_EVENT_CODE LTL_EVENT_DESCRIPT LTL_EVENT_MSG_DATE LTL_EVENT_MSG_TIME LTL_EXP_DATE LTL_EXP_TIME LTL_PO_NUMBER LTL_REASONCODE LTL_REP_DATE LTL_REP_TIME LTL_SHIPMENT_NUMBER LTL_SHIP_TO_CITY LTL_SHIP_TO_COUNTRY LTL_SHIP_TO_PARTY LTL_SHIP_TO_REGION LTL_SHIP_TO_STREET LTL_TP_STATUS

3.

a)

In the SCM/EM IMG navigate to Event Management → Event Messages, Status Queries and Web Interface → Web Interface → Configure Fields for User Profiles.

b)

Select the fields you want from the list of configured fields.

c)

Select several of the fields and review the settings.

Add a new configured field for display from the data in the table below.


406


2010

SCM663


4.

Configured Field

Z##_LTL_EVENT_ICON

EM Attribute ID



Status icons Z##

a)

Add one configured field for display as follows: Choose New Entry.

b)

Enter the data from the following table. Click the F4 function key icon in the EM Attribute ID field. Change the Maximum Number of Hits to 1000.

c)

Choose Enter, then Save Configured Field

Z##_LTL_EVENT_ICON

EM Attribute ID



Status icons Z##

Review some of the configured fields for selection that are listed below: LTL_DEL_STATUS LTL_EH_ACTIVE LTL_EH_TYPE LTL_PO_NUMBER LTL_SHIPMENT_NUMBER LTL_TP_STATUS LTL_SHIP_TO_PARTY

5.

a)

Select Configure Field for Selection from the dialog structure on left.

b)

Find the field, select it, and then choose Details.

Review some of the configured fields for event messages that are listed below: LTL_REASONCODE LTL_REP_DATE_MESSAGE LTL_REP_TIME_MESSAGE LTL_REP_TZ_MESSAGE a)

Select Configure Field for Event Messages from the dialog structure on left.

b)

Find the field, select it, and then choose Details. Continued on next page

2010


407


6.

SCM663

Review some of the groups of the configured fields that are listed below. LTL_EXP_DATE_TIME LTL_REP_DATE_TIME LTL_SHIP_TO_ADDR

7.

a)

Select Build Groups of Configured Fields from the dialog structure on left.

b)

Find the field, select it, and then choose Details.

c)

After you have reviewed the last field, choose Exit.

Create a user profile by joining together the display profile, selection profile and event message profile. When you assign a user to a user profile, the user can then select and display data and confirm events when logged on to the Web Interface. The event message profile is optional if the user does not need to confirm events in the Web Interface. Create a new selection profile by copying an existing profile, LTL_SEL_CUSTOMER, with all of its existing entries.

8.

a)

In the SCM/EM IMG navigate to Event Management → Event Messages, Status Queries and Web Interface Web Interface Define User Profiles.

b)

From the dialog structure on the left, select Selection Profile.

c)

Select profile LTL_SEL_CUSTOMER and choose Copy As.

d)

Change selection profile to Z##_LTL_SEL_CUSTOMER, and then choose Enter. When the message about dependent entries is displayed, choose Copy All.

e)

Choose Save.

Create a new display profile by copying an existing profile LTL_DISP_CUSTOMER and its existing entries. After the Display profile is created, add the new Configured Field, Z##_LTL_EVENT_ICON to the profile.


408


2010

SCM663


Configured Field

Z##_LTL_EVENT_ICON

Display Level Ind

All Screens

Ord Table Ord Detail a)

Select Display Profile from the dialog structure on the left.

b)

Select profile LTL_DISP_CUSTOMER and choose Copy As.

c)

Change the profile name to Z##LTL_DISP_CUSTOMER and then choose Enter. When the message about dependent entries is displayed, choose Copy All.

d)

Choose Save.

e)

Select your display profile Z##LTL_DISP_CUSTOMER and select Event Display Details from the dialog structure on the left.

f)

Choose New Entries.

g)

Enter Z##_LTL_EVENT_ICON as the Configured field. The remaining fields should be set according to the following table.

h)

Choose Enter, and then Save. Configured Field

Z##_LTL_EVENT_ICON

Display Level Ind

All Screens

Ord Table Ord Detail


2010


409


9.

SCM663

Create a new event messages profile by copying an existing event message profile and its dependent entries. In the new Z##_LTL_MES_CUSTOMER profile, change internal event code POD to your new internal event code Z##_POD. a)

Select Event Messages Profile from the dialog structure on the left.

b)

Select event message profile LTL_MES_CUSTOMER and then choose Copy As.

c)

Enter Z##_LTL_MES_CUSTOMER in the Event Msg. Profile field.

d)

Choose Enter and when the message about copying dependent entries appears, choose Copy All.

e)

Choose Save.

f)

Select event message profile Z##_LTL_MES_CUSTOMER.

g)

Select Event Reporting Items from the dialog structure on the left.

h)

Select the internal event code POD and then choose Copy as.

i)

Enter Z##_POD in the Internal Event Code field.

j)

Choose Enter and when the message about copying dependent entries appears, choose Copy All.

k)

Choose Save.

l)

Select the internal event code POD.

m)

Choose Delete and then Save.

10. Assign these profiles to your new user profile.


410


2010

SCM663


User Profile ID


Text

User Profile Z##



Display Profile


Selection Profile

Z##_LTL_SEL_CUSTOMER

a)

Select User Profile from the dialog structure on the left and choose New Entries.

b)


c)


d)

Choose Exit. User Profile ID


Text

User Profile Z##



Display Profile


Selection Profile

Z##_LTL_SEL_CUSTOMER

11. After deleting the existing LTL_CUSTOMER transaction, add your new Z20_LTL_CUSTOMER transaction to your logon user ID.


2010


411


SCM663

Web Int. Tran.

Z##_LTL_CUSTOMER

User Profile ID


Order Web

1

a)

In the SCM/EM IMG navigate to Event Management → Event Messages, Status Queries and Web Interface → Web Interface → Assign User Profiles and Web Interface Transactions to Users.

b)

When the Determine Work Area Entry popup box appears, enter the user ID that you use to log in to the SCM/EM system. Choose Enter.

c)

Select the entry LTL_CUSTOMER.

d)

Choose Delete.

e)

Choose Save.

f)

Choose New Entries.

g)


h)


i)

Choose Exit. Web Int. Tran.

Z##_LTL_CUSTOMER

User Profile ID


Order Web

1

Task 2: Customer POD Now test your configuration by updating the event handler created in the exercises for Unit 9, “Reaction to Events – Configuration”. 1.

Report the customer’s proof of delivery (POD) via the Web Interface, and then check the status. Also, verify that your new status icon appears on the Z## Customer’s Delivery Details screen. Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the Web Interface using transaction //N/SAPTRX/EM_START or with the following path from the SCM/EM SAP menu: SCM/EM SAP Menu: Event Management → Web Interface → Search Continued on next page

412


2010

SCM663


a)

Use the same logon data that you used to log in to the SCM/EM system. 1. 2. 3.

2010

Enter your user name and password. Select the language, if necessary. Click Log on.

b)

Select tracking scenario Z## Customer’s Delivery.

c)

Enter the sales order number of the sales order created in Unit 9, “Reaction to Events – Configuration”. in the Sales Order Number field.

d)

Choose Apply.

e)

Click on Display Details. On the Z## Customer’s Delivery Details screen that should appear, you should see the Status icons Z## that you configured.

f)

Set the flag for Report Proof of Delivery and choose Apply. The Report Proof of Delivery screen should appear.

g)

Enter the same date and time in the Actual Event Date and Actual Event Time as you see in the Planned Event Date/Time field in the Event Handler List. Note: You must enter the date and time in the same format as shown in the Planned Event Date/Time field.

h)

Choose Send. The system will then display the Z## Customer’s Delivery Detail screen.

i)

Verify that your actual date is present. You will see the update immediately in the Web Interface.


413


SCM663

Lesson Summary You should now be able to: • Configure filtering profiles • Configure authorization profiles • Define conditions for data filtering

414


2010

SCM663

Unit Summary

Unit Summary You should now be able to: • Understand the SAP Event Management User Interface option • Understand the features available in new Web Interface (Web Dynpro ABAP) • Configure filtering profiles • Configure authorization profiles • Define conditions for data filtering

2010


415

Unit Summary

416

SCM663


2010

Unit 11 Analytics Unit Overview


Explain how data is mapped from activity in the SAP EM system to reports generated in SAP Business Intelligence Explain how data is uploaded from SAP EM to SAP BI

Unit Contents Lesson: SAP BI Reporting from SAP EM....................................418 Lesson: Data Upload from SAP EM to SAP BI .............................430

2010


417

Unit 11: Analytics

SCM663

Lesson: SAP BI Reporting from SAP EM Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain how data is mapped from activity in the SAP EM system to reports generated in SAP Business Intelligence

Business Example You want to analyze the performance of business processes using information captured by SAP Event Management over certain time periods. You must configure the system to provide this information to SAP Business Intelligence.

Figure 329: SAP BI Query Example for SAP EM

Different roles have needs for different analyses within a company. Higher level positions may be interested in broader views of information, while operational positions need insight to details. In the example above: • •

A transportation manager may analyze delivery performance on a periodic basis at a summary level. A transportation planner might be interested in the same information but at a more detailed view.

SAP Business Intelligence can provide visibility at all levels.

418


2010

SCM663

Lesson: SAP BI Reporting from SAP EM

Figure 330: SAP BI Query Example for SAP EM - Sources of Data

Data is captured in SAP Event Management in different files, including: event header, header appendix, expected events, event appendix, event message, and so on. The data from these files is mapped to SAP BI via configuration in SAP Event Management. Event header, info parameter and control parameter data is usually used for selection criteria in a query. Expected event data, both expected and actual, and event message data is usually used for detail line.

Figure 331: Simplified Data Flow from SAP EM Through SAP BI to User

2010


419

Unit 11: Analytics

SCM663

At the simplest level, the BW Profile defines the mapping of all information from the event handler tables that gets transferred from SAP Event Management into SAP Business Intelligence. Once the data is transferred to SAP BI, various transfer and update rules are used to move the data into info cubes, where it is accessed by queries.

Figure 332: Data Extraction from SAP EM

Data is extracted at event header level, at event level and at event group level. The header data is used mainly for selection criteria. The event itself contains detailed expected and actual event data. At the event group level, you can create a comparison between different events. For performance reasons, groups are used in the SAP Event Management system to perform comparisons between different events before uploading to SAP BI.

420


2010

SCM663


Figure 333: Example of Extract Structures

An extract structure is a flat file that is populated by data from a file in the source system, in this case SAP Event Management. Data that is needed for reporting is mapped to the extract structure. The extract structure is then populated with the specific data on a periodic basis. Time zone is extracted automatically by the system and does not need to be mapped.

Figure 334: Customizing - BW Profile

2010


421

Unit 11: Analytics

SCM663

The BW Profile maps the event handler header and event data, including event groups to extract structures. These extract structures are then copied from SAP Event Management to SAP BI. In the case of complex data mapping requirements or if a customer does not want to use the default SAP settings, a function module could be written and used via the Function Plug-In capability. To define SAP BI profiles, in SCM/EM IMG choose: Event Management → SAP Business Intelligence Interface → Define SAP BI Profiles

Figure 335: BW Profile - Mapping of Header Fields

Header value mapping maps fields from source data files to the extract structure for transfer to SAP BI. The Source field used in SAP Event Management is populated by transactions. In the example above, the Source field CARRIER is read from the source table Event Handler Header. It is then mapped to the Target field CARRIER in the extract structure. The Target field in the extract structure will be populated and used to transfer data from SAP Event Management to SAP BI.

422


2010

SCM663


To define SAP BI profiles: •

•

In SCM/EM IMG choose: Event Management → SAP Business Intelligence Interface → Define SAP BI Profiles Double-click on Header Value Mapping on the left.

Figure 336: BW Profile - Mapping of Events

The BW Profile is used to map the event details. These details include expected events, actual events and event messages. The fields in these files needed for reporting are mapped to an extract structure, which is used to transport the data to SAP BI. To define SAP BI profiles: •

•

2010

In SCM/EM IMG choose: Event Management → SAP Business Intelligence Interface → Define SAP BI Profiles Double-click on Events on left.


423

Unit 11: Analytics

SCM663

Figure 337: Event Fields

Events are listed for each BW profile. When the Exp. Events Indicator box is selected for an event, the Expected Events table is accessed for SAP BI reporting purposes. When the Expected Events Indicator box is not selected, only the Event Message table is accessed. Reason codes exist only in messages, not expected events because they are only expected. To extract reason codes for expected events, an activity or function module is added. This function is delivered with visibility scenarios. Event Additional Functions allows customers to access data not accessed in standard SAP structures, if desired. To define SAP BI profiles, in SCM/EM IMG choose: Event Management → SAP Business Intelligence Interface → Define SAP BI Profiles

424


2010

SCM663


Figure 338: Time Stamp Resolving - Parsing Date/Time

The Time Stamp field in the Event source tables contains date and time together in a single field. Time Stamp Resolving parses the Time Stamp field into separate date and time fields for reporting. Timestamp resolving is done separately at the header, item and group levels, because the timestamp fields are separate fields in each of those files. To define SAP BI profiles, in SCM/EM IMG choose: Event Management → SAP Business Intelligence Interface → Define SAP BI Profiles

2010


425

Unit 11: Analytics

SCM663

Figure 339: Calculating Durations

Durations for header data, event data and group data are all calculated the same way. The Pos. Duration and Neg. Duration fields are always filled using the same formula: timestamp 2 – timestamp 1 = Duration If the result is positive, the Pos. Duration field is filled with calculated results. If the result is negative, the Neg. Duration field is filled with calculated results. Note: A negative duration is indicated with a positive value in the Negative Duration field. To define SAP BI profiles, in SCM/EM IMG choose: Event Management → SAP Business Intelligence Interface → Define SAP BI Profiles

426


2010

SCM663


Figure 340: Groups - Calculating Durations

Sometimes it is desirable to calculate durations between different events. For performance reasons, this duration is calculated in SAP Event Management using groups functionality in the BW Profile. In this query example, “Sum Delay” is calculated by comparing the expected transportation duration to the actual transportation duration. The durations were calculated by comparing the event Plant Departure to the event Customer Arrival. Since these are two separate events, a group is created in customizing to calculate duration.

Figure 341: Defining Groups

2010


427

Unit 11: Analytics

SCM663

To define a group: 1. 2. 3. 4.

Create a Group ID, and assign the appropriate events to that group. Map the group values to the group. Resolve the time stamp. Calculate the duration.

To define SAP BI profiles, in SCM/EM IMG choose: Event Management → SAP Business Intelligence Interface → Define SAP BI Profiles

428


2010

SCM663


Lesson Summary You should now be able to: • Explain how data is mapped from activity in the SAP EM system to reports generated in SAP Business Intelligence

2010


429

Unit 11: Analytics

SCM663

Lesson: Data Upload from SAP EM to SAP BI Lesson Overview Lesson Objectives After completing this lesson, you will be able to: •

Explain how data is uploaded from SAP EM to SAP BI

Business Example

Figure 342: Generic Data Flow for SAP BI (Simplified)

Data from SAP transactions and master files are transferred from the source SAP system to an SAP BI system via a data source. A data source consists of an extract structure and a transfer structure. • •

430

The extract structure is populated with data mapped from source transaction files. The transfer structure is defined in the source system, replicated to SAP BI, and is used for the mapping and data transfer between the two systems. The transfer structure transports the data from the transfer structure in the source system to an SAP BI system. Once the data has been transferred to SAP BI, transfer rules define how that data will be passed on to the InfoSource.


2010

SCM663

Lesson: Data Upload from SAP EM to SAP BI

An InfoSource is a quantity of information that logically belongs together and that has been summarized into a single unit. InfoSources contain transaction data and master data. InfoSources describe all the information that is available for a business process or a type of business process, for example, cost center accounting. •

The communication structure is independent of the source system and is generated from the InfoSource. It is filled from the transfer structure in accordance with the transfer rules. The communication structure contains all the fields in an InfoSource. This process of extracting and transferring cleansed data to the communication structure is known as data staging.

Data is passed from the InfoSource to Info Cubes using update rules. Queries and reports access data stored in Info Cubes.

Figure 343: Simplified Data Flow from SAP EM Through SAP BI to User

The BW profile defines the mapping of all information from the event handler tables into the extract structure. The BW profile is defined in customizing in SAP Event Management, and is assigned to event handler types. This BW profile is referenced when data is extracted from the detail records. The BW profile contains data mapping for the event handler header, expected events, and groups. Groups are used for calculating time differences between two separate events, for example, Plant Departure and Customer Arrival.

2010


431

Unit 11: Analytics

SCM663

Data is extracted from event handlers and used to populate the Data Source field in SAP Event Management. Transfer structures support the transfer of data in a DataSource between the SAP EM source system and a connected SAP BI system. The transfer structure transports the DataSource data from a source system to SAP BI. Info cubes, which are updated with data through transfer rules and update rules, are the main source of data for queries.

Figure 344: Upload of Data to Transfer Structure

Data can be uploaded with an event code, with a transaction, or by using the last event configured: • • •

Event code BW_UPLOAD – This is used for testing or piloting purposes only. Transaction for initial upload, /SAPTRX/BWIU Last event configured to create a new expected event for SAP BI Upload for future date, for example, 3 days later – –

432

Monitoring functionality would execute via rule set Similar to sending an e-mail when an expected event is not reported


2010

SCM663


Figure 345: Upload of Data to the Transfer Structure for Testing

To start the upload to SAP BI, enter report event code BWUPLOAD using transaction /SAPTRX/MI01. This calls rule BW_UPLOAD, which starts the upload to the transfer structure. The first time will cause initial upload of everything. To define rule sets: • •

2010

In SCM/EM IMG choose: Event Management → Reactions to Event Messages → Define Rule Sets Select your rule set and double-click Rules on the left.


433

Unit 11: Analytics

SCM663

Figure 346: Table Structure in SAP Event Management - Generic

Data found in Header and Events Tables are mapped to extract structures. The extract structures are part of the data source, which is used to transfer data between a source system and the Business Information Workbench. Header source data resides in the Event Header Table, the Header Extension Table, Info Parameters and Control Parameters. Event data exists in the Expected Event table and the Event Message table. Group data is used for comparing different events, for example, duration between Departure and Arrival. For performance reasons, this comparison is done in SAP Event Management.

434


2010

SCM663


Figure 347: Table Structure in SAP Event Management - Technical

The technical names of the source structures and extract structures are listed on the screen. By using transaction SE12, you can view the fields in each of the database tables listed here.

Figure 348: Detailed Table Structure in SAP Event Management

This is a more detailed view of the tables located in the SAP EM and SAP BI system.

2010


435

Unit 11: Analytics

SCM663

The Operational Data Store (ODS) is a flat file that contains detailed information for drilldown purposes.

436


2010

SCM663


Lesson Summary You should now be able to: • Explain how data is uploaded from SAP EM to SAP BI

2010


437

Unit Summary

SCM663

Unit Summary You should now be able to: • Explain how data is mapped from activity in the SAP EM system to reports generated in SAP Business Intelligence • Explain how data is uploaded from SAP EM to SAP BI

438


2010

Unit 12 Document Flow Unit Overview


Explain the purpose of document flow Set up your own customizing to create and update a document flow net from SAP Event Management

Unit Contents Lesson: Document Flow .......................................................440 Exercise 8: Document Flow ...............................................457

2010


439

Unit 12: Document Flow

SCM663

Lesson: Document Flow Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • •

Explain the purpose of document flow Set up your own customizing to create and update a document flow net from SAP Event Management

Business Example Imagine you have a complex business scenario and want to gain a quick overview of the relevant business documents.

Figure 349: Concept

Document Flow was developed to have a graphical display of the relevant documents of the entire business process.

440


2010

SCM663

Lesson: Document Flow

Figure 350: Integration with Document Flow - Definition

Event handlers and event messages can contain business documents. A net consists of information from both event handlers and event messages. Document flow functionality is part of Plug-in Basis, which means that different SAP components such as mySAP ERP, mySAP SCM or mySAP CRM can use it.

Figure 351: Document Assignment - Example

Assignment between documents is a central part of the cross-system and cross-partner document flow. Document Flow uses the object link model, available in SAP Web Application Server 6.10, for the assignment. A relationship always consists of two documents and the link between these documents. Multiple links can be built by using single links with common successor or predecessor.

2010


441


SCM663

Figure 352: Integration in SAP EM Web Interface

Document Flow can be displayed only in the SAP Event Management WCL transactions.



442


2010

SCM663



Figure 356: Customizing Document Category for SAP EM

To define document categories for document flow, use transaction /SCMB/DF_CUST or in SCM/EM IMG choose: Integration with SAP Components → Cross-System and Cross-Partner Document Flow → Define Document Categories for Document Flow Predefined categories for SAP Event Management in the system are as follows:

2010

1999

Dummy

1DEL

Inbound Delivery

1INV

Invoice


443


SCM663

1ODL

Outbound Delivery

1POI

Purchase Order Item

1POR

Purchase Order

1SH

Shipment

1SO

Sales Order

1SOI

Sales Order Item

Before you can start to define categories, you have to create structure for your categories. SAP delivers the following structures: /SAPTRX/DF_STRUC_DOCUMENT /SAPTRX/DF_STRUC_ITEM

Figure 357: Maintaining Document Flow Object Link Model for SAP EM

To maintain the object link model, use transaction SOBL_MODEL or in SCM/EM IMG choose: Integration with SAP Components → Cross-System and Cross-Partner Document Flow → Maintain Object Link Model With the help of a role category, it is possible to define one document category and use it in different role types. But SAP recommends that you create your own document category for every business document.

444


2010

SCM663


Figure 358: Maintain the Document Flow Object Link Model for SAP EM

To maintain the object link model, use transaction SOBL_MODEL or in SCM/EM IMG choose: Integration with SAP Components → Cross-System and Cross-Partner Document Flow → Maintain Object Link Model Two role categories can only be connected with each other by one link type. If you want to connect the same documents with different links, the same object type must be included in several role categories. SAP delivers some link types as an example: DUMMY_SO DUMMY_POH POH_POITEM POI_DELIV DELIV_INV PO_SALES SO_DELIV DELIV_SHIP Table /SAPTRX/DF_POITM can be used as a reference of the runtime table.

2010


445


SCM663

Figure 359: Maintain Document Flow Group for SAP EM

To define document flow groups, use transaction /SAPTRX/TSC0DF or in SCM/EM IMG choose: Event Management → Interface to Document Flow → Define Document Flow Groups • •

One group is later assigned to an event handler type activity or an event message rule. A group can be assigned to different event handler type activities or an event message rule. This allows multiple use of one group.

Figure 360: Customizing of Source and Target for SAP EM (1/3)

To define document flow groups, use transaction /SAPTRX/TSC0DF or in SCM/EM IMG choose:

446


2010

SCM663


Event Management → Interface to Document Flow → Define Document Flow Groups • • •

•

A header document is, for example, a Purchase Order header. No item number exists for this business object. An item document is, for example, an item line of a purchase order. In this case a document number and an item number exist. The EM Source Level field is used to maintain the source level. If the source document is on header level, the entry should be Header. Otherwise it should be Item. The EM Level for DF field is used to have a bigger choice if the business document is sent via an event message. If a business document is sent via an event message, the system offers also some event message tables for the source or predecessor mapping.


To define document flow groups, use transaction /SAPTRX/TSC0DF or in SCM/EM IMG choose: Event Management → Interface to Document Flow → Define Document Flow Groups The entries used here have to be defined first in the document flow customizing as shown on the relevant previous slides.

2010


447


SCM663


To define document flow groups, use transaction /SAPTRX/TSC0DF or in SCM/EM IMG choose: Event Management → Interface to Document Flow → Define Document Flow Groups •

•

•

•

448

No Search can be used only if the business document is the first document of the process. For this purpose SAP provides the option of creating a dummy link. For the first document, always use predecessor document category 1999 and create a link type that uses 1999 as predecessor. If you use another document category than 1999, the graphical interface will display this document. Mapping Search is used if a user knows where the parameter of the predecessor document is stored. The mapping is defined in the dialog structure under Predecessor Document Mapping. For example, if the info parameter Sales Order No. contains the relevant number, you can map this field as predecessor. Customer function can be used if other search methods are not sufficient. If you use customer function, you need to assign an activity in the dialog structure under Predecessor Document Function. Sequence Search is similar to mapping search. If you use sequence search, you need to specify a sequence number that already exists in the current DF group. For the predecessor document search, the system takes the information that you have already defined for this specified sequence number in the dialog structure under Source Document Mapping or Source Document Function.


2010

SCM663


Figure 363: Source Document or Predecessor Document Mapping

To define document flow groups, use transaction /SAPTRX/TSC0DF or in SCM/EM IMG choose: Event Management → Interface to Document Flow → Define Document Flow Groups Mapping level is used to define the mapping for the document flow target level. If document number has been chosen, the document number has to be defined. If item number has been chosen, the document as well as the item number has to be defined. SAP provides the following tables: /SAPTRX/EH_CNTRL /SAPTRX/EXTTABID /SAPTRX/EH_HDR /SAPTRX/EH_INFO /SAPTRX/EH_STAT /SAPTRX/EH_TRKID If message is sent by an event message, tables /SAPTRX/EVM_HDR, /SAPTRX/EVM_PAR and /SAPTRX/EVM_REF are also available. Note: A code set has to be defined if table /SAPTRX/EH_TRKID or table /SAPTRX/EVM_REF is used. This is important more than one tracking ID can exist. The Parameter Index field can be used if a user knows exactly in which index parameter a relevant value is stored.

2010


449


SCM663

Figure 364: Source Document Function or Predecessor Document Mapping

To define document flow groups, use transaction /SAPTRX/TSC0DF or in SCM/EM IMG choose: Event Management → Interface to Document Flow → Define Document Flow Groups To define functions for interface to document flow, use transaction /SAPTRX/TSC0TF7 or in SCM/EM IMG choose: Event Management → Interface to Document Flow → Define Functions for Interface to Document Flow In the case of a more complex mapping definition for a document flow group, you can define functions for determining the document number and the item number of a source or predecessor document. First you have to define an activity and create a new function module. Interfaces of this function module are predefined and example coding is available.

450


2010

SCM663


Figure 365: Available Parameters for Document Flow

To define document flow groups, use transaction /SAPTRX/TSC0DF or in SCM/EM IMG choose: Event Management → Interface to Document Flow → Define Document Flow Groups In the standard system, SAP Event Management provides the following information to the document flow: • • • • • •

Event handler GUID (not visible) Universal time stamp of last change (not visible) Document number Item number, if applicable Status code, if applicable Aggregated status, if applicable

If you want to include additional parameters; you need to maintain them in the structure. To add a field in DF Param. Field, first select the relevant structure of the source document category. Then select the field that should be added from the dialog.

2010


451


SCM663

Figure 366: Condition for Document Flow

To define conditions for updating document flow, use transaction /SAPTRX/TSC0TC6 or in SCM/EM IMG choose: Event Management → Interface to Document Flow → Define Conditions for Updating Document Flow It is possible to use a condition defined for an event handler or for an event message. In addition, if a user wants to create or update a net, for example, just for a certain customer or material, this can be defined here.

Figure 367: Define Multitask Activity for Event Handler

To define activities for SAP Event Management, use transaction /SAPTRX/TSC0TP or in SCM/EM IMG choose:

452


2010

SCM663


Event Management → General Settings in SAP Event Management → Functions, Conditions, and Activities in SAP Event Management →Define Activities for SAP Event Management • •

A new multitask activity has to be created or an existing one has to be enhanced. Add activity DF_UPDATE_FROM_EH to the relevant Document Flow group and if applicable a condition.

Figure 368: Assign Multitask Activity to Event Handler

To define event handler types, use transaction /SAPTRX/TSC0TT or in SCM/EM IMG choose: Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types •

•

2010

Be sure to assign the relevant Document Flow activity to the EH Upd. Acty. 2 field. The document flow net can be created or updated only if this field is provided. If you now create a new event handler, a document flow net will be created.


453


SCM663

Figure 369: New Rule for Event Message

To define rule sets, use transaction /SAPTRX/TSC0TR or in SCM/EM IMG choose: Event Management → Reactions to Event Messages → Define Rule Sets • •

If a business document is sent via an event message, a new rule or a task has to be implemented in the rule set. If multitask activities are used, there is also the possibility to check whether the activity should be called or not, for example, by using the Compare activity.

Figure 370: Enabling Document Flow for Display in the SAP EM Web Interface

454


2010

SCM663


To define user profiles, use transaction /SAPTRX/UCUP or in SCM/EM IMG choose: Event Management → Event Messages and Status Queries → Web Interface → Define User Profiles • •

A flag has to be set for every relevant user profile. Document Flow display is available in the SAP EM Web front end list and detail screen. An active accessibility flag means that a table is shown instead of a graphical net.

Figure 371: Deletion of a Document Flow Net

To define settings for deleting document flow, use transaction /SAPTRX/RESTMDF or in SCM/EM IMG choose: Event Management → Archive and Delete SAP EM Objects → Define Settings for Deleting Document Flow • • •

2010

If no residence time is set, the system uses 100 days as the residence time. Relevant categories must be set to make sure that only a net that belongs to SAP EM is deleted. Difference between test run and real run is a result of program logic: For every category, the systems checks whether a net exists and whether it can be deleted. If this is the case, a counter is incremented. If the deletion report does not run in test mode, a commit is executed after every document category. If the next category was also used in this net, nothing is found. In test mode, the net is still available and the counter is incremented again.


455


SCM663

Figure 372: Limitations for Document Flow

456


2010

SCM663


Exercise 8: Document Flow Exercise Objectives After completing this exercise, you will be able to: • Build up your own customizing to create and update a SAP EM Document Flow net • Create and update a Document Flow net

Business Example Your company has a very complex business scenario with different business documents. To get a graphical overview of the relevant business documents in the scenario your company has decided to introduce the Document Flow functionality. You use the LTL delivery scenario to create a new net. Three documents exist for this process: Sales Order, Outbound Delivery and Shipment.

Task 1: The first step is already in the customizing but in this exercise we will review the structure document used to set up the document relationships. 1.

To use the Document Flow functionality normally first a structure has to be set up. Review this structure using the ABAP Dictionary transaction SE11. The structure name is /SAPTRX/DF_STRUC_DOCUMENT.

2.

The categories are also already set up. The document categories are the documents that will be part of the document flow structure. They can be found in the SCM/EM IMG. They are located at Integration with SAP Components → Cross-System and Cross-Partner Document Flow → Define Document Categories for Document Flow. The document categories are: 1999 – Dummy category 1SO – Sales Order 1ODL – Outbound Delivery 1SH – Shipment.

3.

In this exercise review the Link Models used to set up the document flow. Go to the Maintain Object Link Model table in the SCM/IM IMG and review the settings. The relevant Link Types for this exercises call DUMMY_SO as link type between the Dummy and Sales Order category, SO_DELIV between Sales Order and Outbound Delivery and DELIV_SHIP between Outbound Delivery and Shipment. Continued on next page

2010


457


SCM663

Task 2: In this set of exercises you will configure the Document Flow in the SAP Event Management. 1.

2.

3.

First, define a group in SCM/EM IMG Define Document Flow groups using the information the the following table. DF Group

Z##_DF_LTL_DELIVERY

Description

DF Group Z## for delivery

Create the Source and Target entry for the first entry in the document flow. The first document in the flow is the Sales Order. DF Seq. No.

1

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1SO

Rel. type

DUMMY_SO

Pred. Doc. Cat.

1999

DF Pred. Search

No Search

Mapping Level

Document Number

Table

/SAPTRX/EH_INFO

Parameter

SALES_ORDER_NO

Parameter Index

10

Create the next entry in the Customizing of Source and Target for the second document to be shown in the document flow. It is the outbound delivery. DF Seq. No.

2

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1ODL


458


2010

SCM663


4.

5.

DF Seq. No.

2

Rel. type

SO_DELIV

Pred. Doc. Cat.

1SO

DF Pred. Search

Mapping Search

Mapping Level

Document Number

Table

/SAPTRX/EH_INFO

Parameter

DELIVERY_NO

Mapping Level

Predecessor Document Number

Table

/SAPTRX/EH_INFO

Parameter

SALES_ORDER_NO

Index

10

Now enter the value for the third document. It is the shipment document. In this case the predecessor is found with the help of a sequence search. DF Seq. No.

3

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1SH

Rel. type

DELIV_SHIP

Pred. Doc. Cat.

1ODL

DF Pred. Search

Sequence Search

DF Seq. No.

2

Mapping Level

Document Number

Table

/SAPTRX/EH_INFO

Parameter

SHIPMENT_NO

In this step you will must create a Multitask Activity, Z##_MEU_LTL_DELIVERY using the data from the table below.


2010


459


SCM663

Task Sequence

1

Task

Z##_UPDATE_DF

Activity

DF_UPDATE_FROM_EH

Activity parameters:

Z##_DF_LTL_DELIVERY

DF Group Choose Task on the right side for you new Activity. Enter a sequence number 1 and as Task Name Z##_UPDATE_DF and as Activity DF_UPDATE_FROM_EH. After pressing return enter your DF Group Z##_DF_LTL_DELIVERY under Activity Parameters. 6.

Now, you will add the Multitask Activity, Z##_MEU_UPDATE_DF to your Event Handler Type, Z##_EHT.

7.

In this step activate the Document Flow in your User Profiles Z##_LTL_DEL_CUSTOMER and LTL_DELIV_CARRIER for the Web Interface.

Task 3: Test your configuration by creating an Event Handler in SAP Event Management by creating a new Shipment in the SAP ECC Application System. Create a Shipment for your pumps. 1.

2.


OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-12-##



Material Number

Quantity Ordered

P-102

2

Create the outbound delivery document from the sales order. In the delivery, enter the Pick Deadline of Today’s date + 2 business days and the picking time at 1:00 am. This will become the expected time for the Picking Begin event. Continued on next page

460


2010

SCM663


3.

Note Delivery Number: ________________

4.


1000

Shipment Type


Shipment Route

R00001

Shipping Condition


Shipment Stage

Date

Time

Stage Start


11:00

Stage End


22:00

Note Shipment Number: ________________ 5.

2010

In this exercise, log onto the Web Interface and display the document flow for the event handler created in the exercise. Choose the Carrier Delivery scenario and select the new link Document Flow. You will also select the Z## Customer’s Delivery scenario and see the document flow there.


461


SCM663

Solution 8: Document Flow Task 1: The first step is already in the customizing but in this exercise we will review the structure document used to set up the document relationships. 1.

To use the Document Flow functionality normally first a structure has to be set up. Review this structure using the ABAP Dictionary transaction SE11. The structure name is /SAPTRX/DF_STRUC_DOCUMENT.

2.

a)

In the SCM/EM System, from the SAP Menu navigate to: Tools → ABAP Workbench → Development → ABAP Dictionary.

b)

Select the Data type radio button.

c)

Enter /SAPTRX/DF_STRUC_DOCUMENT in the Data type field.

d)

Choose Display.

The categories are also already set up. The document categories are the documents that will be part of the document flow structure. They can be found in the SCM/EM IMG. They are located at Integration with SAP Components → Cross-System and Cross-Partner Document Flow → Define Document Categories for Document Flow. The document categories are: 1999 – Dummy category 1SO – Sales Order 1ODL – Outbound Delivery 1SH – Shipment.

3.

a)

Navigate to the path in the SCM/EM IMG above.

b)

Locate the Document categories in the table and see that they are assigned to the structure /SAPTRX/DF_STRUC_DOCUMENT.

In this exercise review the Link Models used to set up the document flow. Go to the Maintain Object Link Model table in the SCM/IM IMG and review the settings. The relevant Link Types for this exercises call DUMMY_SO


462


2010

SCM663


as link type between the Dummy and Sales Order category, SO_DELIV between Sales Order and Outbound Delivery and DELIV_SHIP between Outbound Delivery and Shipment. a)

In the SCM/EM IMG navigate to: Integration with SAP Components → Cross-System and Cross-Partner Document Flow → Maintain Object Link Model.

b)

In the Dialog Structure on the left side of the table select Link Model.

c)

Review the entries for the Relationship Types: DUMMY_SO SO_DELIV DELIV_SHIP

d)

Select each entry, then choose Details.

e)

After reviewing the last entry, Select Exit.

Task 2: In this set of exercises you will configure the Document Flow in the SAP Event Management. 1.

2.

First, define a group in SCM/EM IMG Define Document Flow groups using the information the the following table. DF Group

Z##_DF_LTL_DELIVERY

Description


a)

Navigate to SCM/EM IMG: Event Management → Interface to Document Flow → Define Document Flow Groups.

b)

Select New entry.

c)

Enter the data from the following able.

d)

Choose Enter, then Save. DF Group

Z##_DF_LTL_DELIVERY

Description


Create the Source and Target entry for the first entry in the document flow. The first document in the flow is the Sales Order.


2010


463


SCM663

DF Seq. No.

1

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1SO

Rel. type

DUMMY_SO

Pred. Doc. Cat.

1999

DF Pred. Search

No Search


464


2010

SCM663


Mapping Level

Document Number

Table

/SAPTRX/EH_INFO

Parameter

SALES_ORDER_NO

Parameter Index

10

a)

Select your DF Group: Z##_DF_LTL_DELIVERY

b)

In the Dialog Structure, select Customizing of Source and Target.

c)

Select New Entries.

d)

Enter the following values DF Seq. No.

1

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1SO

Rel. type

DUMMY_SO

Pred. Doc. Cat.

1999

DF Pred. Search

No Search

e)

Select Enter, then Save.

f)

In the Dialog Structure on the left, select Source Document Mapping. Here you define how the relevant number of the sales order can be found. This information is stored as Info parameter.

g)

Select New Entries.

h)

Enter the Mapping Level, Table, and Parameter data from the table below, then select Enter.

i)

Now, enter the Index from the table below.

j)

Chose Enter and then Save. Mapping Level

Document Number

Table

/SAPTRX/EH_INFO

Parameter

SALES_ORDER_NO

Parameter Index

10


2010


465


3.

SCM663

Create the next entry in the Customizing of Source and Target for the second document to be shown in the document flow. It is the outbound delivery. DF Seq. No.

2

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1ODL

Rel. type

SO_DELIV

Pred. Doc. Cat.

1SO

DF Pred. Search

Mapping Search

Mapping Level

Document Number

Table

/SAPTRX/EH_INFO

Parameter

DELIVERY_NO

Mapping Level


Table

/SAPTRX/EH_INFO

Parameter

SALES_ORDER_NO

Index

10

a)

In the Dialog Structure, select the Customizing of Source and Target.

b)

Select Next Entry.

c)

Enter the following values

d)

DF Seq. No.

2

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1ODL

Rel. type

SO_DELIV

Pred. Doc. Cat.

1SO

DF Pred. Search

Mapping Search

Select Enter and then Save. Continued on next page

466


2010

SCM663


4.

e)

In the Dialog Structure on the left, select Source Document Mapping. Here you define how the relevant number of the sales order can be found. This information is stored as Info parameter.

f)

Select New Entries.

g)

Enter the Mapping Level, Table, and Parameter data from the table below, then select Enter.

h)

Chose Enter and then Save. Mapping Level

Document Number

Table

/SAPTRX/EH_INFO

Parameter

DELIVERY_NO

i)

In the Dialog Structure, select Predecessor Document Mapping. The value of the predecessor is stored also as Info parameter.

j)

Select New Entries.

k)

Enter the Mapping Level, Table, and Parameter from the table below, then select Enter.

l)

Enter the Index from the table below.

m)

Select Enter, then Save. Mapping Level


Table

/SAPTRX/EH_INFO

Parameter

SALES_ORDER_NO

Index

10

Now enter the value for the third document. It is the shipment document. In this case the predecessor is found with the help of a sequence search. DF Seq. No.

3

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1SH

Rel. type

DELIV_SHIP


2010


467


SCM663

DF Seq. No.

3

Pred. Doc. Cat.

1ODL

DF Pred. Search

Sequence Search

DF Seq. No.

2

Mapping Level

Document Number

Table

/SAPTRX/EH_INFO

Parameter

SHIPMENT_NO

a)

In the Dialog Structure, select the Customizing of Source and Target.

b)

Select Next Entry.

c)

Enter the values from the table below, except the DF Seq. No.

d)

After selecting the DF Pred. Search value, choose Enter.

e)

Enter the DF Seq. No. from the table below.

f)

Select Enter, then Save. DF Seq. No.

3

DF Target level

Header

EM Level for DF

Event Handler

EM Source Level

Header

Document Cat.

1SH

Rel. type

DELIV_SHIP

Pred. Doc. Cat.

1ODL

DF Pred. Search

Sequence Search

DF Seq. No.

2

g)

From the Dialog Structure, select Source Document Mapping.

h)

Select New Entries.

i)


j)

Select Enter, then Save.

k)

Choose Exit. Mapping Level

Document Number


468


2010

SCM663


5.

Table

/SAPTRX/EH_INFO

Parameter

SHIPMENT_NO

In this step you will must create a Multitask Activity, Z##_MEU_LTL_DELIVERY using the data from the table below. Task Sequence

1

Task

Z##_UPDATE_DF

Activity

DF_UPDATE_FROM_EH


Z##_DF_LTL_DELIVERY

DF Group Choose Task on the right side for you new Activity. Enter a sequence number 1 and as Task Name Z##_UPDATE_DF and as Activity DF_UPDATE_FROM_EH. After pressing return enter your DF Group Z##_DF_LTL_DELIVERY under Activity Parameters. a)

In the SCM/EM IMG navigate to: Event Management → General Settings in SAP Event Management → Functions, Conditions, and Activities in SAP Event Management → Define Activities for SAP Event Management.

b)

In the Dialog Structure, select Multitask EH Update Activities.

c)

Choose New Entries.

d)

Enter Z##_MEU_LTL_DELIV in the Activity field.

e)

Enter DF Activity for LTL Delivery in the Description

f)


g)

Select the Activity you just created.

h)

Select Tasks from the Dialog Structure.

i)

Choose New Entries.

j)

Enter the Task Sequence, Task and Activity from the table below.

k)

Select Enter.

l)

Enter the Activity Parameter: DF Group from the table below.

m)


n)

Choose Exit.


2010


469


SCM663

Task Sequence

1

Task

Z##_UPDATE_DF

Activity

DF_UPDATE_FROM_EH


Z##_DF_LTL_DELIVERY

DF Group 6.

7.

Now, you will add the Multitask Activity, Z##_MEU_UPDATE_DF to your Event Handler Type, Z##_EHT. a)

In the SCM/EM IMG navigate to: Event Management → Event Handlers and Event Handler Data → Event Handlers → Define Event Handler Types.

b)

Select your Event Handler type, Z##_EHT.

c)

Choose Details.

d)

Enter the Multitask Activity Z##_MEU_LTL_DELIV in the EH Upd.Acty 2 field.

e)


f)

Select Exit.

In this step activate the Document Flow in your User Profiles Z##_LTL_DEL_CUSTOMER and LTL_DELIV_CARRIER for the Web Interface. a)

In the SCM/EM IMG navigate to: Event Management → Event Messages, Status Queries and Web Interface → Web Interface → Define User Profiles.

b)

Select your User profile: Z##_LTL_DEL_CUSTOMER

c)

Choose Details.

d)

Select the checkbox Document Flow.

e)

Choose Save, then Back.

f)

Deselect the User Profile.

g)

Select User Profile: LTL_DELIV_CARRIER.

h)

Choose Details.

i)

Select the checkbox Document Flow.

j)

Choose Save, then Exit.


470


2010

SCM663


Task 3: Test your configuration by creating an Event Handler in SAP Event Management by creating a new Shipment in the SAP ECC Application System. Create a Shipment for your pumps. 1.


OR

Sales Organization

1000


10

Division

0

Sold-to Party

1280

PO Number

EM-12-##



Material Number

Quantity Ordered

P-102

2

a)

Log into the SAP ECC Application System.

b)

Use transaction VA01 to create the sales order or Menu Path: Logistics → Sales and distribution → Sales → Order → Create

c)

On the Initial Screen enter the Order Type, Sales Organization, Distribution Channel and Division. Select Enter.

d)

On the Overview screen enter the Sold-to Party, PO Number, Requested Delivery Date, Material Number and Quantity. Select Enter.

e)

Select Save.


2010


471


2.

SCM663

Create the outbound delivery document from the sales order. In the delivery, enter the Pick Deadline of Today’s date + 2 business days and the picking time at 1:00 am. This will become the expected time for the Picking Begin event. a)

Use transaction VL01N, or Menu path: SAP Menu: Logistics → Sales and Distribution → Shipping and Transportation → Outbound Delivery → Create → Single Document → with Reference to Sales Order

3.

b)

Enter Shipping Point 1000. Enter the Selection Date as Today + 2 business days. The Sales Order created in the previous exercise should appear in the Order field. Select Enter.

c)

On the Overview screen, select the Picking tab. Enter the Pick/Date Time of Today’s date + 2 business days. Enter 01:00 in the Time field.

d)

Choose Save

Note Delivery Number: ________________ a)

4.

see task


1000

Shipment Type


Shipment Route

R00001

Shipping Condition


Shipment Stage

Date

Time

Stage Start


11:00

Stage End


22:00

Note Shipment Number: ________________ a)

To create the shipment document use transaction VT01N or use the menu path: SAP Menu: Logistics → Sales and Distribution → Shipping and Transportation → Shipment → Create → Single Documents


472


2010

SCM663


b)

In the Initial Screen, enter the Transportation Planning Point and Shipment Type. Note: Make sure you have the “Expert” options set in the Customizing of Local Layout Options so that you can see the display of the Shipment Type codes.

c)

Select the Select Deliveries button in the application toolbar.

d)

Scroll down the Select outbound deliveries popup screen to the W.ref.to box and enter your delivery document number in the Outbound Delivery field.

e)

Select the Execute icon at the lower left-hand corner of the Select outbound deliveries screen.

f)

On the Create: Shipments and Deliveries screen, select the Overview of Current Shipment icon (the mountain and sun).

g)

Under the Processing tab on the top portion of the screen, enter the Shipment Route and the Shipping Condition.

h)

In the Deadl. portion of the screen select the Planning button.

i)

Enter the Planning data from the data table below. When saving the shipment, these fields will be used to create the expected events Carrier Arrival, Loading Begin and Loading End in SAP Event Management. Planning Dates and Times

Date

Time

Check-In


8:00

Loading Start


9:00

Loading End


10:00

j)


k)


l)

Select the Stage details icon at the lower left corner of the screen.

m)


n)

Update the Shipment Stage information with the following dates and times. When saving the shipment, these fields will be used to create the expected events Plant Departure and Customer Arrival. Shipment Stage

Date

Time

Stage Start


11:00

Stage End


22:00 Continued on next page

2010


473


5.

SCM663

o)

Select the Copy button at the bottom of the Details on Stage 0001 screen.

p)

Choose Save.

In this exercise, log onto the Web Interface and display the document flow for the event handler created in the exercise. Choose the Carrier Delivery scenario and select the new link Document Flow. You will also select the Z## Customer’s Delivery scenario and see the document flow there. a) Hint: The actual URL used is based on the system used for training. Your instructor will give you the URL. You can also access the WCL using the following menu path: SCM/EM SAP Menu: Event Management → Web Interface → Search or transaction /n/SAPTRX/EM_START b)

Use the same logon data that you used to login to the SCM/EM system. 1. 2. 3. 4.

Enter your User-Id. Enter your Password. Select the Language, if necessary. Select the Log on pushbutton.

c)

Select the tracking scenario: Carrier’s Delivery

d)

Enter the Shipment Number: Your shipment number from the Exercise.

e)

Choose the Apply button.

f)

Select the Shipment and click on Display Details. In the Detailed Information area you should see Document Flow. Select it.

g)

The Document Flow pop-up screen should appear. A graphic showing the link between the sales order, deliver and shipment document will be displayed. You can also display this information in list for by selecting the Table View link on the screen.

h)

Choose Close to return to the Carrier’s Delivery Detail screen.

i)

Select Apply.

j)

Choose the Z## Customer’s Delivery scenario.

k)

Enter the Sales Order Number of the order that was created in the exercise.

l)

Select Apply. Continued on next page

474


2010

SCM663

2010


m)

In the next screen, ID’s and Attributes, you should see the link to Document Flow on the right side of the screen. Select Document Flow.

n)

Review the Document Flow data in the popup screen, then select Close.

o)

Select Log Off.


475


SCM663

Lesson Summary You should now be able to: • Explain the purpose of document flow • Set up your own customizing to create and update a document flow net from SAP Event Management

476


2010

SCM663

Unit Summary

Unit Summary You should now be able to: • Explain the purpose of document flow • Set up your own customizing to create and update a document flow net from SAP Event Management

2010


477

Unit Summary

478

SCM663


2010

Unit 13 SAP Object Event Repository Unit Overview


Get an overview on SAP Object Event Repository (SAP OER) Solution Understand how SAP OER maps to EPCIS Architecture Understand the EPCIS compliance of SAP OER solution Explore the Product Tracking and Authentication Scenario

Unit Contents Lesson: SAP Object Event Repository.......................................480

2010


479

Unit 13: SAP Object Event Repository

SCM663

Lesson: SAP Object Event Repository Lesson Overview Lesson Objectives After completing this lesson, you will be able to: • • • •

Get an overview on SAP Object Event Repository (SAP OER) Solution Understand how SAP OER maps to EPCIS Architecture Understand the EPCIS compliance of SAP OER solution Explore the Product Tracking and Authentication Scenario

Business Example

Figure 373: Solution Scope - SAP Solution for Auto-ID and item serialization - Context

480


2010

SCM663

Lesson: SAP Object Event Repository

Figure 374: SAP Solutions for Auto-ID & item serialization mapped to the GS1/ EPCglobal architecture

Figure 375: Quick Facts: SAP Object Event Repository

2010


481


SCM663

Figure 376: SAP Object Event Repository (OER) - Overview Principal Dimensions of OER Capabilities

Figure 377: SAP Object Event Repository GS1 - EPCIS standards based data repository

482


2010

SCM663


Figure 378: SAP Object Event Repository The single point of truth

Figure 379: SAP Object Event Repository Compliance towards Serialization Requirements

2010


483


SCM663

Figure 380: SAP Object Event Repository Sense & Respond with SAP Event Management

Figure 381: SAP Auto-ID Enterprise: Fundamental Capabilities

484


2010

SCM663


From a software architecture perspective, capabilities are spread across the platform at three levels: 1. 2.

Real World: where data is read / captured and events are recorded from a variety of sources like readers, sensors and devices. AII and OER: combined together , they provide the capability to address “business scenario mapping” requirements of an enterprise. The “edge” end of this layer consists of AutoID Infrastructure and the Enterprise end consists of the SAP Event Management based Object Event Repository , which allows supply chain wide tracking & discovery services.

At the top end of the platform are the composite applications like Product Tracking & Authentication (PTA), asset tracking, product lifecycle management, promotion execution etc., which utilize the other layers and deliver value to a business.

Figure 382: Main SAP OER Software components

2010


485


SCM663

Figure 383: Preconfigured Value added item Traceability with Auto-ID Enterprise

Figure 384: SAP Product Tracking and Authentication

486


2010

SCM663


The SAP Product Tracking and Authentication (SAP PTA) solution enables companies to ensure safe production and secure distribution of their products by providing visibility and traceability of product flow across the enterprise and the extended supply chain network. It provides the following capabilities: •

• • •

Tracking the flow of products at multiple levels of hierarchy (item, case, pallet, etc.) across the enterprise and extended supply network to detect discrepancies between expected and actual product flow such as shipping/receiving discrepancies, malicious product movement, diversions, etc. Provide full traceability of all business events and transactions at unique object level (item, case, pallet, etc..) Automated multi-layered authentication of products and validation during any kind of goods movement to ensure product legitimacy Establish of a chain of custody of the product to ensure consumer/patient safety, brand protection and a secure supply chain

Figure 385: SAP Product Tracking and Authentication Process Flow

PTA is part of the scenario Secure Tracking and Tracing. As described above it consist out of different functionalities: • • •

2010

Product Tracking by Delivery Product Tracking by EPC Product Authentication


487


SCM663

Figure 386: SAP Product Tracking and Authentication

Figure 387: High Resolution Traceability of Events that can be queried by the business partner

488


2010

SCM663


Figure 388: High Resolution Traceability of Events that can be queried by the business partner

Figure 389: SAP Solutions for Auto-ID and Item Serialization (Enhanced Product Tracking and Authentication)

2010


489


SCM663

Figure 390: SAP OER Item / UII lifecycle tracking High Resolution Traceability & Situational Insight

Figure 391: SAP OER Item / UII lifecycle tracking High Resolution Traceability & Situational Insight

490


2010

SCM663


Figure 392: Executive Summary - SAP Event Management a key component in the Object Event Repository

Figure 393: Classical SAP EM processes vs. SAP OER processes

2010


491


SCM663

Figure 394: Example Usage: Secure Tracking and Tracing with GS1 EPCIS and SAP Object Event Repository

Figure 395: EPCIS B2B Querying supported by SAP OER Example

492


2010

SCM663


Figure 396: Example OER [Custom] EPCIS Client querying the Standard SAP OER

Figure 397: SAP Object Event repository

2010


493


SCM663

Figure 398: Central Number Range Management: Business Background

Figure 399: Central Number Range Management: Solution Approach

494


2010

SCM663


Figure 400: Central Number Range Management: Process Flow


2010


495


SCM663


Figure 403: Object Event Repository Menu: Central Number Range Administration

496


2010

SCM663


Figure 404: Customization Settings

Figure 405: EPCIS Compliance - Overview

2010


497


SCM663

Figure 406: EPCIS: Event Capture Notification Service

Figure 407: EPCIS: Simple Event Query Service

•

•

498

With this event query it is possible to retrieve the data corresponding to the EPCIS events specified by the parameters in the query. The query service can be used via PI or by web service and the answer includes a list of capture events The predefined queries have a large number of optional parameters; by appropriate choice of parameters a client can achieve a variety of effects


2010

SCM663


Figure 408: SAP Object Event Repository - Simple Event Query Support

Figure 409: SAP Object Event repository - EPCIS Compliance

2010


499


SCM663

Figure 410: EPCIS Subscription Support

Figure 411: SAP Object Event repository Special security capabilities

500


2010

SCM663


Figure 412: SAP Object Event repository Special security capabilities

Figure 413: SAP Object Event repository Security Summary

Post capture events only for locations that are assigned to the user's business partner. Receive event query results only for events at locations that are assigned to the user's organization. The organization to which a user, say USER1 belongs will be modeled in OER as a business partner of type organization, say BP1. BP1 will be assigned to a company prefix, say 0037000. All locations that are based on the

2010


501


SCM663

company prefix 0037000 will be assumed to belong to BP1. When USER1 queries for an event he can only see the events with business locations belonging to BP1 and satisfying the parameters of his query. Receive master data query results only for locations that are assigned to the user's business partner. USER1 can only see the locations that belong to BP1 and satisfying the parameters of his query. Extension of this default authorization behavior by the customer is possible through BADI implementation.

502


2010

SCM663


Lesson Summary You should now be able to: • Get an overview on SAP Object Event Repository (SAP OER) Solution • Understand how SAP OER maps to EPCIS Architecture • Understand the EPCIS compliance of SAP OER solution • Explore the Product Tracking and Authentication Scenario

2010


503

Unit Summary

SCM663

Unit Summary You should now be able to: • Get an overview on SAP Object Event Repository (SAP OER) Solution • Understand how SAP OER maps to EPCIS Architecture • Understand the EPCIS compliance of SAP OER solution • Explore the Product Tracking and Authentication Scenario

504


2010

SCM663

Course Summary

Course Summary You should now be able to: • • • •

2010

Explain the elements of SAP Event Management Send event notifications and perform status retrieval Configure the Fulfillment visibility process in the SAP ERP application system and SAP Event Management Configure the user interface, the Web Communication Layer


505

Course Summary

506

SCM663


2010

Appendix 1 Additional Topics

Explain Connectivity to Other Systems

Figure 414: Defining Connections to the AS and SAP EM

To connect the application system with the SAP EM system, you must define the technical connections.

2010


507


SCM663

Figure 415: Customizing in the Application System

1.

2. 3. 4.

508

To define the RFC destination, use transaction SM59 or from the SAP ERP menu, choose Tools → Business Communication → IDoc Basis → Administration → RFC destination. Enter transaction SALE. Enter transaction /SAPTRX/ASC0TS. Enter transaction /SAPTRX/ASC0AO.


2010

SCM663


Figure 416: Customizing in SAP Event Management

1.

2. 3.

4.

2010

To define the RFC destination, use transaction SM59 or from the SAP ERP menu, choose Tools → Business Communication → IDoc Basis → Administration → RFC destination. Enter transaction SALE. Enter transaction /SAPTRX/SAPLTSADMIN or from the SCM/EM IMG menu, choose Event Management → General Settings → Define Application System. From the SCM/EM IMG menu, choose Event Management → Event Handlers and Event Handler Data → Parameters → Define Parameter Mapping.


509


SCM663

Define Archiving in SAP Event Management

Figure 417: Archiving in SAP Event Management

Figure 418: Archiving for SAP EM

510


2010

SCM663


Figure 419: Starting Archiving for SAP EM

Figure 420: Reading the Archive

2010


511


SCM663

Explain the Purpose of the Application Log

Figure 421: Application Logs

Figure 422: Application Logs with /SAPTRX/ASAPLOG

This transaction logs all activities you do during the creation or changing of event handlers. When you save the business object, it saves everything into a log and you can view this log, for example, when an event handler isnt created as you expect it to be. Logs exist in both SAP EM and ERP.

512


2010

SCM663


Log can be switched off in ERP in transaction SAPTRX/ASC0AO. Under General Data, select Appl. Log. Deactiv.

Figure 423: Configuration of Log Level

The following fields are used to configure the log level: • • •

Log EH Posting: Writes an application log for an event handler when posting updates from an application system. Log Msg. Proc: Writes an application log during event message processing. Log Ext. Update: Writes an application log for external updates (for example, BAPIs) and manual changes in transaction /SAPTRX/EH_LIST.

You can choose the level of detail recorded in these logs.

2010


513


SCM663

Use the Consistency Check

Figure 424: Consistency Check in SAP EM

This screenshot shows the report for the consistency check in SAP EM. To access this screen, in SCM/EM from the SAP Menu, choose Event Management → Administration → Consistency Check

Simulation Capability in Application System and SAP EM

Figure 425: Simulation of EH Processes

514


2010

SCM663


Figure 426: Simulating SAP EM Process

Set simulation mode at the business process type. When you make a change to the application object, you will see the simulation

Figure 427: Protocol of the Simulation Process

This screenshot is from the SAP Event Management simulation. If you keep paging through the application simulation, you come to the Event Handler side and the posting of the Event Handler. It tells you then whether the event handler is created. In SAP Event Management, you can set a parameter in your user ID that gives you the ability to restart tracking and do simulation: parameter = TRKOBJ_UPDATE with a value of X

2010


515


SCM663

Then you are able to step through the simulation on the SAP Event Management side.

516


2010

Feedback SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.

2010


517

SAP Event Management.pdf

Recommend Documents