Warning: include_once(/home/piarchitecture2/piarchitecture.com/wp-content/plugins/wordpress-support/wordpress-support.php): failed to open stream: Permission denied in /home/piarchitecture2/piarchitecture.com/wp-settings.php on line 223
Warning: include_once(): Failed opening '/home/piarchitecture2/piarchitecture.com/wp-content/plugins/wordpress-support/wordpress-support.php' for inclusion (include_path='.:/usr/local/lib/php:/usr/local/php5/lib/pear') in /home/piarchitecture2/piarchitecture.com/wp-settings.php on line 223 exchange infrastructure Archives - SAP PI Architecture
SAP professionals as well as business consultants have a great role in building a formidable business. While SAP professionals like developers works on the technical side of a business, there are times where the problem can never be solved by the SAP developer. The requirements may not be clear which is sent to the developer or the software was not tested properly.
Nevertheless, there are two challenges in checking of SAP to one’s business. The technical error and the business error. When we speak of the technical error, it involves about mapping and configuration settings of PI. If these two fails this can also result to failure of communication. For instance, we would like to send a message to a vendor say, “Mr. Smith”.(I’m referring to the data input) and is not appearing on the configuration and mapping settings, tendency is an error message will appear and the message won’t be sent.
For PI, there are also business errors that result to failure of business communication. It can be a communication barrier between the SAP Developers and Business Consultants. Direct communication on both parties are important to meet the standards for PI in a business perspective. In monitoring PI, business consultants and SAP developers should work hand in hand to ensure that the configuration and mapping are in set especially when testing software is being conducted.
For SAP developers and business consultants, SAP PI has a long way to go.
[order_box_1 width=”85%” + border=”4px”]Post your comments, suggestions and reactions about, “SAP PI: The Importance of Monitoring One’s Business” And don’t forget to subscribe to our newsletter to get the newest updates! We’ll be waiting![/order_box_1]
I had to do some knowledge transfer. I got some great learning’s from this. Please see this short video about what happened. Hopefully it will help you and inspire you to create some experiments with it.
Even I learned something and found ways to improve the scenarios to make the better fulfill the business requirements.
I was waiting in the lobby of a hospital. One of the things I noticed was there was as lot of posters on how to work on documentation. It made me think that documentation is a universal issue that every profession has or at least most profession experiences.
I was thinking of areas where they do not document. I was thinking of childcare or housepainters. I guess that in the first instance it would make sense to document the child’s progress. The house painter could probably document what he has done, in order to avoid other problems in a later stage and easy paint the same color for the client again.
Sorry the poster was in Danish, but I’ll try to give must best summery of them.
One of the things I noticed about the posters is that they focus a lot of the process on creating documentation. The first poster present a process that a unit has been thru to learn what and how to make sure the documentation was in order.
The main principle that they are proposing is to du an audit, where a large part of the staff is working together to review the documentation already created. They use a list of 28 questions from the hospital to make sure the documentation is up to the state the hospital requires. Then they implement changes to improve the documentation for later patients.
The other poster wrote about a process for a creating for an entire hospital and how to make sure that everybody know how to document. A part of the process is also the test everybody’s knowledge according to some guidelines. That should also be an idea that we should start to implement.
It claims that documentation is a process that can be improved all the time, and effort needs to be created to work on this.
This is also something that I see as possible in the perspective of SAP documentation. It is not enough just to use the same templates or process that we used 10 years ago. We need to update our knowledge to make sure that we use the best procedures.
I’ll be talking about documentation in SAP PI at SAP Teched in Las Vegas. I hope that my presentation there will inspire you go learn more about your own documentation process and make sure you create better documentation.