Alternative SOLUTIONS are usually very expensive and do not react as FAST as your situation may demand.

For example, if you use MANUAL entry method, it could be expensive, would be extremely slow, and will be subject to human errors. Error trapping and correction is also not easy.

ABAP, SECAT, CATT, and LSMW - all have some common issues:

• ABAP, SECAT, CATT, or LSMW are too technical for most people.
• Experts who knows these technologies are usually very expensive, centralized, and hard to access or otherwise difficult to reach across organizational boundaries.
• Even with approval to utilize and create these solutions, you are still dependent on data, process owners, and BASIS and change management personnel to WORK in perfect synchronization before you can implement their use in a production environment. In short, you are constrained by the RELEASE process with these technologies.
• Your SAP landscape may be littered with one-time use and throw away conversion programs that have lost their relevancy due to prohibitive modification and update costs.
• Overall User action time and SAP execution time is longer to significantly longer as compared to running process with Process Runner.
• These technologies are constantly and significantly changing as SAP releases changes.
• When something does not work: SAP does not provide direct support. If you have questions or issues, you will be routed to a normal OSS support process or will be directed to a consulting group. In contrast, we at Innowera will quickly help you to come to the right resolution.

Alternative solutions are usually very expensive and do not react as fast as your situation may demand.

For example, if you use manual entry method, it could be expensive, would be extremely slow, and will be subject to human errors. Error trapping and correction is also not easy.

ABAP, SECAT, CATT, and LSMW - all have some common issues: