Search Results

[4 Matches Found]
 
Article icon
SAP Professional Journal – 

Kurt Bishop shows you how to avoid costly mistakes in a disaster recovery plan. He discusses the 15 most overlooked items - including the cost of downtime, security issues, loss of personnel and systems, and the importance of testing - and explains how to incorporate them into your own recovery planning.


Article icon
SAP Professional Journal – 
Kurt Bishop explains how to use SAP Desktop Office Integration (DOI) to leverage thousands of custom and off-the-shelf COM objects to build powerful applications with a minimum amount of code. He discusses a technique for ActiveX documents (forms quickly assembled in Visual Basic) through an example in which SAP report data is downloaded to a Microsoft Access database.

Article icon
by Kurt Bishop, Independent Consultant March 15, 2000
SAP Professional Journal – 
Whether your SAP system is still in its settling-in phase, or is one that has been firmly entrenched for years, ushering in new changes is a nontrivial challenge. Even small, seemingly innocuous changes, like rearranging a screen, introducing new headings on a report, or revising your backup practices can introduce downtime. Large or small, IT teams obviously need to avoid downtime and make sure that a change does not have an adverse effect on users, partners, or customers. Kurt Bishop prescribes a three-step process for averting downtime: document the risk/reward and cost associated with each R/3 change request; categorize change requests according to their risk/reward profile; and safeguard, schedule, and implement the change in a manner that is consistent with its risk/reward profile. This article provides details on all three steps.

Article icon
by Kurt Bishop, Independent Consultant October 15, 1999
SAP Professional Journal – 
 – Capacity planning is not a trivial task. Choose your hardware vendor and equipment carefully, and upgrades will pose few problems. Choose the wrong vendor-model combination, and you will be forced to make extensive changes to your hardware and operating system that will entail extensive planning and testing, and could ultimately require all new equipment. So how do you, as a customer, set yourself up for a successful collaboration with your hardware vendor—one that ensures the final system design meets your current requirements and adequately scales over time? This article describes the capacity planning process, some basic tools and techniques employed by the vendors, and how you can ensure that all of these items work in your favor as you attempt to size your SAP R/3 system.