You are here:

SAP roll-out: implementing a system based on a template

Adam Książek

Roll-out projects should be understood as the implementation of a system using an existing template. This template is most often a fully configured and operational environment. In the case of international roll-outs, which are the most common, the template is a branch of the corporation operating in the country most similar in nature to the roll-out location, or the branch where the SAP system was implemented earliest, and where the number of functionalities implemented is the highest (though this is not, of course, a rule). The existing template ensures an efficient implementation in areas consistent with the established corporate model, whilst allowing the team to focus on implementing solutions that reflect local specificities.

The implementation methodology for roll-out projects assumes that the pre-implementation phase does not include a full analysis of the client’s business specifics. This work was carried out during the initial implementation, and each subsequent roll-out requires, rather, familiarisation with the model solution. At this stage, it is important to organise meetings with the working team of the company’s local branch and to share knowledge regarding the scope of the original implementation. During such workshops, staff from the company undergoing the roll-out gain an understanding of how well the global template – which forms the basis of the implementation – aligns with local requirements; this step serves as an excellent introduction to the next stage, namely the Fit & Gap analysis.

The Fit & Gap analysis serves to determine the extent to which the implementation template aligns with local conditions. At the same time, it aims to identify the differences – both business-related and, frequently, legal – between the reference entity and the entity undergoing the roll-out. Analysing the current state, analysing the target structure of business processes and identifying existing differences is a crucial step in determining the success of the implementation. At this stage, the consultants’ experience and their knowledge of local conditions are of the utmost importance. Specific provisions of local law, the economic conditions of the branch, or business processes not included in the model implementation but occurring locally – all these factors contribute to the outcome of the deviation analysis.

All discrepancies should be identified and named, and the method for handling them should be specified in detail. It is important to bear in mind that, regardless of whether a given deviation is handled within the SAP system or a decision is made to manage it outside the system, it should be included in the gap catalogue. Identifying GAPs involves assigning a difference ID – usually a GAP reference number – which specifies the area to which the deviation relates, the person reporting it, its priority and, ultimately, the course of action. Attention should also be paid to the fact that – where possible – efforts should be made to standardise business processes within a common model. Standardising business processes, even at the cost of organisational changes within a local entity, often brings benefits on a global scale – centralised maintenance and administration of the SAP system is made easier and less costly as a result of such measures.

The assumptions developed during the Fit & Gap analysis phase should be incorporated into the business concept, which is an integral part of every implementation. A document detailing the functionalities to be implemented will facilitate a smooth transition through the phase of prototyping the production environment. It is also worth ensuring that those at the group’s head office responsible for maintaining the SAP system verify and approve the local implementation concept document – particularly with regard to the solutions adopted to address differences arising from local specificities.

Once the system configuration phase is complete, testing can begin, preceded by the loading of master data into the system. When migrating data, it is advisable to use the tools created for the original implementation, although experience shows that these often need to be adapted to local requirements. In the case of greenfield implementation projects (full implementations from scratch), an additional stage – known as regression testing – is introduced during the system testing phase, alongside module and integration testing.

As the implementation of additional functionalities not derived from the reference model may affect processes currently carried out in other organisational units, the system must be tested for any adverse effects resulting from the expansion of the SAP system’s organisational structure to include a further unit (this usually involves adapting existing customised code). The next stage is the production data migration, which forms part of the pre-launch preparation phase. The go-live of a new organisational unit is, of course, preceded by training for key and end users.

 

Polish specifics in roll-out implementations – rely on SI-Consulting!

The
decision by the head office of an international company to transfer the corporate SAP solution to its Polish organisational unit is usually the first step in preparing for a roll-out project. It is worth securing a reliable implementation partner at this stage – one with a proven track record of tackling similar challenges and a thorough understanding of Poland’s specific legal regulations and generally accepted business practices. Mapping local specifics within the SAP system is often an extremely difficult task for the group’s central units responsible for developing the SAP environment.

SI-Consulting has successfully completed over a dozen roll-out projects (Axellus, Komet-Urpol, Mitsubishi, etc.), either taking full responsibility for the work or providing expert services.

By far the most differences that will emerge during the gap analysis phase relate to the FI module, i.e. financial accounting. Complex accounting and tax regulations necessitate the adaptation of the standard solution in areas such as the chart of accounts, financial statements, reports, exchange rates, account allocations, tax codes and VAT registers, amongst many others. In the SD module, particular attention should be paid to the invoicing process, the content of sales document printouts and the handling of complaints (correction of original invoices). If the implementation covers HR and Payroll, particular attention should be paid to processes relating to payroll accounting and HR administration – changes to Polish law in this area are particularly frequent.

Adam Książek – SD Consultant

He possesses specialist knowledge in areas including the implementation of the mySAP ERP integrated system in the Sales and Distribution domain, the management of logistics processes, and the development of business concepts and configurations within the SD module.