SAP continues to innovate on several crucial component systems, one of which is interface monitoring. Inter-system messages form a core part of how disparate elements of a business’s system communicate. As most sections are added to function with SAP as the core, there is an increased volume of messages transmitted from system to system. Message transmission has historically accessed the SAP Intermediate Document (IDoc) as a route in most customer setups. Reviewing these messages has been around since R/3, but an in-depth inspection was only possible through manual means. You had to know precisely what you were looking for.
Early thrusts into interface monitoring were overly technical. Implementing these monitoring solutions typically fell to a technical support team. When SAP designed S/4HANA, it aimed to simplify most of the typical interactions that staff would have with data and systems. Users on S/4 HANA can now perform actions that previously depended on the technical IT support staff, making it much easier to get the information they want out of their system. This change significantly reduces the dependence a business has on its IT support staff and empowers the non-IT staff to do their jobs more efficiently.
Original Components Untouched
One of the best parts of SAP’s upgrade path is that it doesn’t force users to relearn the system completely. Instead, it offers them old transaction records alongside new ones for users who have grown accustomed to the traditional way of doing things. The same is true here, as the interface monitoring elements that SAP on-premise users would be familiar with (WE02, WE05) are still available. However, a new functionality comes with the release of Enhanced Package 4 of ECC which can help you build your own website. These upgrades offer a lot more independence for the interface monitoring systems.
In the recent past, the only way a business could leverage the benefits that interface monitoring could provide was to activate other business functions it depended on to work correctly. Even though the company itself had no use for these functions, they were a prerequisite for interface monitoring to work. Today’s update sees these dependencies removed. Businesses can now access the full functionality from SAP S/4HANA 1511 On-premise version onwards. The functionality has three (3) core components:
- EDI Monitor for Forecast Delivery Schedule and JIT Delivery Schedule (accessed using Transaction Code EMJIT)
- EDI monitor for inbound ASN (accessed using Transaction Code EMASN)
- EDI monitor for inbound sales orders (accessed using Transaction Code EMORD)
The new monitor demonstrates more independence between sales analysts and shipping specialists. The primary functionality upgrades the functionality offers to businesses are:
- Messages’ content can be used as a search parameter. From customer purchase order to the recipient, businesses can leverage powerful search functions to find the information they’re looking for
- Organization elements have become standard, and businesses can use sales offices, distribution channels, and sales organization fields as part of the selection
- Multi-search functionality allows different types of messages to be searched in tandem. The table linked data allows for customer orders, order changes, and specialized requests to be pulled from a single search.
By implementing these changes, SAP has given users a new level of freedom and independence from tech teams. There is less time spent sorting through search queries making for more efficient use of employee time.