You want to get to know our software better? Then arrange a non-binding live demo!
The most important factors for successful IT projects
SAP IT projects are considered complex, lengthy and often prove to be a bottomless pit in financial terms. But there is another way. SAP projects can be fast and successful - if the application offers the right conditions for this. The software's features determine how quickly and easily it can be implemented. And whether the time and costs involved remain low during implementation and also in subsequent IT support.
COST AND PROJECT SECURITY DURING IMPLEMENTATION
A decisive factor for successful IT projects with low time and cost expenditure is the degree of integration with SAP. The example of a document processing solution illustrates this.
SAP transport managment.
If the application is embedded in SAP, has its own SAP namespace and uses the SAP transport system, then importing a transport is sufficient to implement the software. The logistics correspond to the familiar structures of the SAP landscape and offer the same advantages. Deliveries are made via SAP transport requests. Individual requirements are implemented through uncomplicated customizing. The customer can extensively test the new application in its own QAS system. Only when everything runs flawlessly here is the transport into the productive system carried out and thus the solution goes live. This ensures the functionality of the new application.
Adoption of SAP authorization concept.
With a solution that is embedded in the SAP IT landscape, the existing authorizations in SAP can be easily adopted. The access rights within the document processing correspond to the existing authorization concept in SAP. Only access to the document processing software itself is controlled via separate authorization roles. No new concept needs to be developed, so there is no further implementation effort here either. Whereby the application should, of course, be designed to be flexible enough to allow adjustments to the authorizations if this is desired.
No additional database.
A document inbound processing solution that is SAP-embedded runs entirely within the SAP database and accesses the SAP master and transaction data directly for interpretation and validation as well as when editing and posting content. There is no need to set up another working place for validation with an additional database. A separate workplace for training documents is also not required. Improved recognition is trained directly in the application.
No interfaces.
Since no data is exchanged via import and export of master and transaction data, there are also no interfaces that would have to be set up and maintained. This simplifies implementation enormously and also reduces the subsequent IT support effort to a minimum.
SAP Look&Feel.
Applications embedded in SAP offer SAP Look&Feel. This keeps training costs low. At tangro, for example, experience has shown that one day is sufficient to train department employees in the use of the new software. Further support is of course possible if desired.
MINIMAL EFFORT AFTERWARDS AS WELL
To ensure that the time and financial effort required for the project remains manageable after implementation, further criteria should be met.
Additional functionalities and change requests in their own namespace.
New features and enhancements should also be implemented in their own SAP namespace and delivered via transport requests. This ensures that enhancements are also available immediately in the event of an update and that no further adaptation effort is required.
New features for all customers.
The software provider should implement further developments in its own central development system. This ensures that innovations are always incorporated into the core product. Although customer-specific functionalities can initially only be made available to the customer who has commissioned and paid for the innovation, tangro delivers further developments to all customers in a regular cycle. Via subsequent transports, all customers then benefit from enhancements - free of charge.
User exits for in-house enhancements.
Conversely, the software should be designed so openly that customers can also implement enhancements themselves if they have the corresponding SAP expertise in-house. To this end, the application should offer appropriate user exits that companies can use to make their own IT adjustments if necessary.
Release security.
In addition, the application should be release-secure. An application that is embedded in SAP meets this requirement. Runnability on current and future SAP versions is ensured. Likewise on S/4HANA. For tangro customers, the switch to S/4HANA is possible without any additional costs. The IT support effort therefore remains minimal even in the event of a release change.
Simple rollouts.
Subsequent rollouts to other companies and countries should also be as quick and uncomplicated as possible. One factor is again the embedding in SAP. If embedding is the case, all that is required is the import of a transport or the creation of a new company code, as well as straightforward customizing to implement the application at additional company locations. This is usually done in one day and can be carried out in-house if required. The IT effort remains low here as well.
These features ensure maximum project security. Deliveries via SAP transport, adoption of the SAP authorization concept and the elimination of an additional database or additional workstations keep the time and costs for the implementation project low. Thanks to these features, tangro, for example, is usually implemented in less than 17 project days, which is so unusually fast and secure that we can offer the implementation at a fixed price. Subsequent costs also remain low because new features are available to all customers, rollouts require little effort and additions can even be made in-house if required.
You might also be interested in