Demonstrating the Concept Order Activities & Events

Orchestration is only one of the processes in the lifecycle of the order.

Processing continues after dispatch.

In order to orchestrate these processes we need the ability to:

• Track key activities for an order, and for parts of an order - including partial lines
• Receive key activity updates from fulfillment systems about the order (shipment)
• Receive key activity updates from other systems about the order (delivery)
• Send these key activity updates to other systems via Event Mesh (shipment notification)
• Trigger standard order processing on an activity (is the order now fully shipped?)
• Trigger custom processes to tailor business-specific requirements
• Store a history of all the key activities in the lifecycle of the order

This is what we use Order Activities for in SAP Order Management foundation.

Order activities and events in SAP Order Management foundation represent a key aspect of understanding the lifecycle of an order. In this lesson, we will outline what order activities are, dive into the concept of order life cycles, and explore how custom activities can provide flexibility. We'll also discuss how order updates to other systems are managed.

With the dispatch of fulfillment requests to fulfillment systems like WMS, ERP, or store applications, the order process begins. However, that's not where the order life ends. For both business users and consumers, it's essential to have awareness about the status of the order throughout its life. This requires tracking updates and intervening where necessary.

Order activities allow tracking key steps for full orders, part of an order, or even partial lines. Order updates may come from fulfillment systems or other systems, such as third-party logistics platforms. These order activities are then sent to other systems via the Event Mesh, which disseminates information such as shipment notifications.

In addition, order activities can trigger standard order processing steps, like determining if an order is fully shipped and updating the ERP accordingly. It can also trigger custom processes, tailoring the order processing to meet specific business or industry requirements.

Customizability is the essence of SAP Order Management foundation. With varied businesses across different industries and markets, SAP has designed the SAP Order Management foundation to be as adaptable as possible for each business's unique requirements.

Lastly, all these activities are stored and provide a history of all the events in the lifecycle of each order.

In the next section, we'll go into a practical demonstration of what order activities look like and how they can be used.

Order activities within SAP Order Management foundation can be broken down into two main categories: standard activities and custom activities.

Standard activities pertain to common steps within an order's lifecycle. These encompass key milestones such as when the order was first created, when a shipment has happened, when delivery has occurred, and when the order is officially marked as fully delivered.

On the other hand, custom activities allow you to define and track additional actions or steps that are unique to your specific business situation. They offer flexibility and adaptability, allowing your SAP Order Management foundation setup to document every critical step of your unique order processing journey.

When configuring these activities in SAP Order Management foundation, it provides an interface where you can define the type of activity, its name, a short description, and whether or not it is currently enabled. An 'enabled' status implies that the system will record it when triggered.

You can also specify if you want this activity to be published as an Event Notification to Event Mesh, and whether you want this activity to appear in the list of activities. These settings allow you to use the activity in workflows, and also make it visible in the UI for easy tracking and referencing.

Next, we'll look at a practical demonstration of these order activities, and how they can be configured and used in the SAP Order Management foundation UI.

In this section, we will explore how to navigate through order activities within the SAP Order Management foundation user interface.

In the settings, you'll discover a number of standard activity types like Fully Delivered, Created, etc. These are system-defined activities that capture common milestones in the order journey.

However, SAP Order Management foundation also offers the flexibility to create custom activities. You can easily add a new activity by clicking on the 'Add' button in the activity settings. Each activity can be defined with a unique name, type, and description.

By checking an actual order within the SAP Order Management foundation UI, you can see a chronological stream of activities that have transpired for that particular order. This feature provides a sequential snapshot of the order's progress and can be incredibly helpful for order tracking and management.

The ability to define new order activities offers the opportunity to maintain visibility into custom steps and actions in your order process. The possibilities are as diverse as the needs of your business.

In the upcoming sections, we will delve into different ways to utilize these custom-defined order activities to enhance your order management process.

The capacity to create custom activities offers significant advantages, especially when it comes to extensibility and reflecting actions back into SAP Order Management foundation and the broader IT landscape. This empowers businesses with a comprehensive view into their operational processes, freeing them from being limited to a hard-coded process.

For instance, you can model each step in your process as a custom activity. An 'Order Created' activity can trigger an 'Order Created' update in the Event Mesh. Likewise, when a shipment occurs, a customized 'Shipment' activity can trigger a shipping update in the Event Mesh.

This seamless integration with Event Mesh allows for the generation and publishing of custom activities, providing real-time updates to both the end-users and other connected applications. Such cross-platform communication builds an integrated operational system wherein everyone is updated about order progress.

In the next sections, we'll delve deeper into ways these custom activities can be optimally utilized to guarantee the seamless flow of information and maintain transparency across all stages of order management.

In the given scenario using SAP Order Management foundation, shipping activities from fulfillment systems are received via the Order Activities API. The same method is used to receive delivery activities. These activities are then dispatched to other systems through Event Mesh as notifications for end consumers.

Crucially, SAP Order Management foundation also aggregates and processes these activities. Since partial completion of an order (like a part of the order being shipped) doesn't indicate the completion of the full order, the system aggregates the various activity notifications received from the fulfillment systems to determine when the order is complete.

Not only does SAP Order Management foundation store this history, but it also displays these records in the user interface. This stored activity log helps to conveniently track the history of all events in the order's lifecycle and contributes to analytics. It could provide insights into aspects like on-time performance rates in comparison to customer promises, among other things.

In the following, we will explore more on how to utilize stored order activities and history in optimizing order management operations.

The relationship between order activities and the Event Mesh provides a clear picture of how continuous updates and communication are maintained throughout the order lifecycle in SAP Order Management foundation.

End-points exist to post and retrieve activities, providing a constant exchange of information on the status of the order. This process pertains to both the context of orders and orchestration. For instance, once a fulfillment request is created, the system can receive that update asynchronously. The receipt of this information then triggers the publishing of these updates to the SAP Event Mesh.

Moreover, activities can also trigger workflows within the system, by setting certain processes in motion based on the triggered activity. These workflows, in turn, can generate additional activities, cementing a circular process that guarantees continuous progress and updates at each step of the order lifecycle.

In the upcoming sections, we will delve more deeply into the role of these activities in triggering workflows and explore how this interconnected system can boost the efficiency of your order management operations.

In SAP Order Management foundation, there are primarily three types of activities: system, standard, and custom activities.

System activities are generated exclusively by SAP Order Management foundation. These represent inherent processes and milestones in the operation of the SAP Order Management foundation system and are usually tied to key software functions.

Standard activities, while pre-defined in SAP Order Management foundation, can also be triggered by other systems. These activities are usually tied to common operational tasks and milestones that are not limited to SAP Order Management foundation alone.

Lastly, custom activities allow users to create and define their own set of activities. This can cover any additional or unique processes that your business needs to track, which might not be covered by the system or standard activities.

In the upcoming sections, we'll delving deeper into these activity types, how to create and manage them, and their role in enhancing your order management process with SAP Order Management foundation.

The payload of an order activity, essentially the data it carries, varies depending on whether the activity is a standard one or a custom creation.

While standard activities have pre-set structures, custom activities give you the flexibility to define your own. The structure of these models is available in the API hub for easy reference, enabling users to tailor the data they pass on in the activities with ease.

Additionally, even standard order activities enable some tailoring through the use of custom fields. These fields enable users to pass on customized information within a standard order activity. Similar to the order itself, these fields can accept tailored information in your own JSON structure.

There is a maximum size limit for this data, but on the whole, it's generously set and more than sufficient for most users' needs.

In the coming sections, we'll delve into the creation and management of these custom fields and look at how they can provide additional flexibility in the way you manage and track your order processes.

API Hub is a comprehensive portal where you can view the structure and understand how the 'Post' and 'Get' requests work for your order activities.

A 'Post' request is used when you want to send information or custom data to be stored in the system. For example, when you're passing additional information during the order process, you would use a 'Post' request. In contrast, a 'Get' request retrieves data from the system. You'd use a 'Get' request when you want to view or obtain information about your order or its activities.

Both requests are straightforward, and mainly require an order ID and any additional information you want to post or get.

In forthcoming sections, we will delve into more specific examples and scenarios where you might use 'Post' and 'Get' requests in the context of SAP Order Management foundation.

The user interface (UI) in the SAP Order Management foundation provides an effective and intuitive way to view and manage your order activities. The list of activities for each order can be seen and further expanded to see which items these activities pertain to.

There's an option to specify whether to display a specific activity in the list. This feature comes in handy, as you might have certain technical activities that aren't relevant for a business view or for customer-facing communication. For instance, statuses related to communication transfers may not be meaningful for most users or customers, and you might choose to hide such activities for clarity.

Being able to control what is visible not only helps to maintain a clean and focused overview of the order's progress but also supports customer communication efforts by only displaying activities that are valuable for the end-users or customers.

Further lessons will cover more about customizing and managing order activities within the SAP Order Management foundation UI.

SAP Order Management foundation uses the data from order activities to provide real-time updates and generate insightful reports.

One of the useful features in the SAP Order Management foundation UI is the display of actual shipment and delivery dates of orders. These are then compared with the expected delivery dates. The UI highlights these timelines in different colors to signify whether the order was delivered on time or was delayed. Such features aid in providing an at-a-glance view of delivery performance.

This same information is instrumental in generating reports and conducting an analytics review. These evaluations help detect issues and inefficiencies, and support troubleshooting and optimization initiatives.

In following, we'll learn how to generate these reports and how to derive valuable insights from them to enhance the order management processes.

In SAP Order Management foundation, business events go beyond just order activities. They encompass a range of actions and updates throughout the entire order process. Examples include whether an order transfer has been successful, if the order was amended during the buffer period, updates to the order statuses, and the cancellation of an order. Subsequently, business events also include order activity notifications.

These business events can be forwarded to the SAP Event Mesh, which allows for real-time updates and communication across multiple systems without disrupting core functionalities.

By subscribing to the Event Mesh, custom processes can be initiated based on the events received. This could trigger a Lambda function or activate a microservice to perform an action.

For example, if a business event denotes a potential issue, it may trigger a notification to the operations team or send an update to a customer. This communication could be managed directly or routed through another system such as Commerce Cloud or MarSys integrated via Event Mesh.

These mechanisms lay the groundwork for a dynamic and responsive order management system. In the next lessons, we will see how these layers of communication can be harnessed to streamline processes and enhance customer experience.

This allows custom processes to take place without disrupting the core functionality.

Simply having a listener on event mesh can trigger a lambda function or a micro-service to take another action, such as send an email.

When it comes to order activities, all the activities are sent through the Event Mesh as one general 'Order Activity Notification' event. This setup means each type of activity doesn't require a separate event on the Event Mesh, providing a streamlined approach.

This design was chosen intentionally as pre-defining individual events for each activity in the Event Mesh can be challenging, especially as new order activities can be created dynamically as needed.

Thus, when you subscribe to the 'Order Activity Notification' event from the Event Mesh, you can parse the content to identify the specific activity type and respond as needed.

The API Hub provides additional information on the structure and content of these Event Mesh notifications, offering thorough visibility into the payload and structure of these events.

In the following sections, we will dive into practical demonstrations and scenarios of handling event notifications and how they contribute to the efficient management of order processes.

As each lesson follows a similar structure, there might be some repetition with regards to the way content is presented.

However, the documentation links provided at the end of each lesson will differ according to the lesson topic. These resources can offer a deep dive into the specific aspects covered in each lesson, providing comprehensive details and guides on how to implement the concepts discussed.

In the next lessons, we'll use these resources as references and guides, showing you how to practically apply what you learn to your order management processes