Quality in and of itself is a critical success factor for HCM Projects and any ERP projects. It should, however, be based on a clear concept and not simply be implemented for its own sake. Projects can also be needlessly    stifled  in the name in quality.

Structured Procedure: There are many process models  for implementing   standard software products. Quality problems arise for the following three reasons:

ü  The selected process model is not used because it entails to great a workload.

ü  The selected process model is not used  because it cannot be applied to the actual situation

ü  The process model focuses on implementation and requires clear and sensible definition of the requirement.

An "Off-the -rack" process model can only server as a rough guide. One of the first tasks of a project team is to create a project-specific model from a general process model. The team must not only consider company -specific factors, but also the special characteristics of SAP ERP(HCM). It is not enough for a technically oriented process to stipulate the definition of the most important structures. For a HCM project, the team must define the company and employee structure and use of the Organizational management.

A clear definition of requirements that clearly describes the planned processes is indispensable for Quality. The planned processes are, after all, the means for measuring the success and therefore the quality of Project .

Implementation projects for IT systems are often subject to extreme time and budget constraints. Even if the initial project planning is realistic, pressure can arise from the following factors :

ü  Late or drawn out project start;

ü  Use of capacity elsewhere (especially if the workload for ongoing everyday tasks has been underestimated);

ü  Changes in the  project team members during the project execution;

ü  Constantly changing requirements during the project execution stage.

·         Finding your place

When we talk about Information/Data Management we usually talk about 3-4 broad areas:

In last blog we discussed about why regression testing should be automated. Also we discussed about the contents & important of Process Mapping and Test cases. In this blog we will look at the approach to automation project and tools provided by SAP.

Approach to test automation project:
The approach to SAP automation will also depend on many other non technical issues few examples are business process readiness, test case readiness and budget and time constraints.

Regression testing, Integration Testing and Unit Testing, all form important part of any SAP project. Testing is necessary but never sufficient. Testing becomes more complex in global-local object development scenario with multiple SAP clients across the geographies. In such scenario any rollout or a complex enhancement should ensure that regression testing is sufficient so that it does not affect normal operations.

The ability to stay connected at all times and the ability to process data faster than ever has made Mobility and HANA the hottest topics in this year's Sapphire. At Infosys we leverage SAP's newest technologies to provide the best in class mobile solutions for our customers. At Sapphire Madrid we will showcase our Mobility capabilities and some of the smart apps like mBrochure, Guided Sales that we have built on devices like iPAD and smart phones.

Opportunity Maintenance (OM) is the term we are using to describe an opportunity window of maintenance for the machines by virtue of breakdown with another machine(s). In this article let us discuss about the event for opportunity window, how maintenance tasks can be identified and execute within this time frame and finally look at the challenges posed for doing opportunity maintenance.