Using the PPO in the DOE
I am almost sure plenty of SAP Consultants never heard about the Post Processing Office (PPO). This cross-component is an open Framework you can implement to process error messages from mass runs or external calls in a business perspective. You can enhance it with your own components or SAP components which are not part of the PPO implementation list yet. This Framework is quite easy to use and to extend with few code enhancements and customizing.
The PPO is based on the concept of postprocessing orders. When an error occurs, a postprocessing order is created like a message is set or an exception raised. Generally, it is implemented within a BAPI or a mass report in replacement of the standard log handler. Then, going to the PostProcessing Desktop, processors will be able to manage their messages, changing status or dispatching them to other processors. You can extend the PPO in order to be able to resend the information which failed.
Scenario : Conflict Detection
MI 7.1 ensures conflict detection by providing standard flow blueprints. Just assume, a back-end user modifies a record in the back-end system while, in the meantime, a mobile user does another change on the same record. The back-end is the master system and the information goes directly to the DOE thanks to an “alert-push” mechanism, then to the outbound queue, waiting for the next receiver synchronization. The receiver starts the synchronization. The DOE must reject the information because of conflict detection.
Fig 1: Scenario – Conflict Detection
Scenario : Post Processing
Considering the standard architecture of MI7.1 which ensures data integrity by rewriting the information contained in the master system (normally, the backend) in the Data Orchestration Engine (DOE) and then the mobile client during synchronization, it sounds reasonable to think about implementing the PPO somewhere; simply because the post processing of a functional issue doesn’t only consist of resending the message. The issue must be analyzed by a business champion to ensure the correctness of the information. Why is it so important? simply because implementing a mobile solution is rarely the choice of end users but the one of the Business/IT department which wants to increase the quality of the information. Mobilizing processes must guarantee to end-users to save time, to the company to save costs. Do not ask to end users to redo the same job if the synchronization failed because of something which is not their fault. For the rest, let’s do administrators with the monitoring administration desk.
According to the Logical Unit of Work (LUW) & the ACID principles and thanks to the openess of the MI architecture, a mobile application which is based on various back-end systems (or not) must be controlled on the DOE itself. Within the process flow, just before or after calling the REJECTION_SERVICE, you can guarantee an appropriate error handling by creating post processing orders in a custom service. This one will store the information people will be able to process again later on.
Finally, I though that I know the PPO thanks to several implementations I did when I was banking consultant. I said : “Can I do the same with FS-AM?”
Using the PPO when integrating Account Management
The Account Management solution (FS-AM, also named Deposit Management or Banking Services depending on the release) fully integrates the Post Processing Office. For instance, during the mass execution of the Account Closure process, several checks must be done to guarantee some requirements. Let’s assume, several of them cannot be closed because of their status, a post processing order will be created.
Having two PPO? I want a single point of entry but in the meantime, I understand that implementing the PPO in the DOE to control the complete process is more than a nice to have. Can I solve this issue and make the complete process working? How can I do? Probably, I will take care of controlling the postprocessing orders so that they do not appear twice and depending on the requirements, I will either decide to do it in FS-AM, in the DOE or somehere else. Then, perhaps, I will have to manage remote desktop access if FS-AM-PPO is not the central PPO instance. There is always a technical solution (checking BAPI) but is there a business value of doing it? Should we use MI on top of FS-AM?
Few years ago, a banker said about his bank : “We will be the first “cool” bank in the world!” Why do not say : MI Bank is cool!
Indeed, most of the banks want to attract students and young workers in order to fidelize them as customers. Whereas other industries do not hesitate to offer mobile phones, IPods and other high-tech products, we can probably assume a “cool” bank can do the same. It is not my business but I would say, you can provide the capability to manage a student account on top of an “IPod-like” hardware; you can help banking employees to manage their customers portfolios; you can imagine sharing contracts and retrieve signatures remotely; Then you will say that SAP solutions are not only reliable products but also very cool!
And I said: “perhaps, I would be able to ask for a cool job opportunity in my christmas wishlist next time!”