Professional Documents
Culture Documents
Turkey
IT SIGNIFICANT PROCESS
ITSP-2– Install and Accredit Systems
Document Control
Approval Status
Revision History
Version Issue Date Status Reason For Issue
1.0 30/04/2008 Approved Process Documented
1.1 26/06/2008 Approved Process documentation fine tuned
1.2 30.05.2009 Approved Process documentation updated with 2009 OCA Guide
Table of Contents
1 STANDARD OPERATING PROCEDURE................................................................................................. 4
1.1 Introduction............................................................................................................................................................................................................ 4
1.2 Statement of Scope............................................................................................................................................................................................... 4
1.3 Operating Process................................................................................................................................................................................................. 5
2. Segregation of Duty Matrix......................................................................................................................... 17
1.1 Introduction
RAC Turkey provides Delivery of Projects for the Key financial Application SAP for Unilever Business Units of various countries in Asia AMET Region.
The Business units (Countries) require migration from Legacy System to SAP – ERP System, Unilever RAC being the Regional Application Centre
provides service to the Countries to implement the Project. The end to end Change Request Process is divided into three IT significant processes (ITSP
1, 2, &3) to align with IT Operational Control Assessment (OCA) requirement.
This Document
(i) Narrates the Standard Operating Procedures for the ITSP 2 – Install and Accredit Systems for SAP- Project Delivery
(ii) Segregation of Duty matrix for ITSP 2 operations
Before the Acquired or Maintained Key Financial Systems (KFS) are promoted into production, appropriate testing and validation must be performed to
ensure that financial systems are operating as designed. Without adequate testing, new or changed systems may not function as intended and may
provide invalid information, which could result in unreliable financial information and reports.
This Install and Accredit Systems process is initiated on the completion and sign off of the “Blue Print-Design Studies” and is concluded when the Gate
Control 2 is Signed off including go-live plan.
The Delivery of Projects Overview depicts the various steps involved in the process and also the reference to the ITSP’s. The steps involved are-
Document Ref:
D2.A3 - Country Test Plans
D2 A4 –Country Test Scripts
P2.A3 Regression Test plan Manual Business Analyst of Business analysts of the Live countries, create unit specific
Live Countries Test Plans and unit specific Test scripts for Regression Test
based on the generic Test Plan and scripts.
Document Ref:
D2 A4 –Country Test Scripts
P2.A4 Approve Integration Test Manual Project Manager Project Manager (Country) approves integration Test and UAT
and UAT Plans, Test (Country) Plans, Test Scripts from country and sends the plan for
Scripts integration testing process. (Integration Test includes Security
and Interface Testing)
Document Ref:
D2.A3 - Country Test Plans
D2 A4 –Country Test Scripts
P2.B1 Verify Entry Criteria for Manual Solution Delivery After Test Plan Process is completed, the Plan and script files
Integration Testing Team (RAC), are sent to Solution Delivery Team (RAC) for verification and
confirmation.
P2.B2 Prepare Necessary Test Manual EUIT (UK) If necessary test environment is not created, RAC IT follows
Environment /Automated up with Europe IT to create test environments. After necessary
test environment is created, Solution Delivery Team (RAC)
checks for all entry criteria.
P2.B3 Transport Build to QA Automatic / Basis Team (RAC) When all the entry criteria are met, Solution Delivery team
Automated requests Basis Team (RAC) to transport the build to QA
environment for testing. Basis Team performs the transport to
QA from Development environment.
Control Ref. No: C 2.6
Document Ref:
D2.B2 – Integration Test Result Document
P2.B5 Raise Test Problem Manual Project Team If some of the tests are not successful, it is considered
Report (Country) whether the failed tests can be ignored. In that case, failed
test result is accepted with the reasons for its acceptance
being documented in the Test Result document. If failed test
result is not accepted, the test case goes to defect
management process for further testing after raising test
problem report.
Integration testing Sign off includes sign off for C 2.2 Security
Configuration and C 2.3 Interface testing.
Control Reference No: C 2.2, C 2.3
Document Ref:
D2.B2 Integration Test Result Document
D2.B3 Integration Test Summary sign off sheet
D100 Authorisation Matrix
D-2-C User Acceptance
Testing
Document Ref:
D2.C1 UAT Test Plan and Test Scripts with Test Data
D2. C2 UAT Results
P2.C4 Raise Test Problem Manual Project Team/Key If failed test result is not accepted, the test case goes to defect
Report Users (Country) management process for further testing after raising test
problem report.
Document Ref:
D2.C3 UAT Results
D2.C4 UAT Summary sign off sheet
D100 authorisation Matrix
D-2-D Regression Test
Documents Ref:
D2. D1 Regression Test Plans and Scripts
D2. D2 egression Test Results
P2.D3 Raise TPR Manual Testing Team Live If the test result did not meet exit criteria, then TPR is raised
Countries depending on requirement and sent to Defect Management
Process.
Documents Ref:
D2. D2 Regression Test Results
D2.D3 Regression test Summary Sign off sheet
D-2-E Capacity and
Performance Testing
P2.E1 Capacity and Manual IT Team and IT Team of the Country and Business analyst of the Country
performance Testing Plan /automated Business analyst of prepares the Capacity and performance Testing Plan
Country Document.
Documents Ref:
D2. E1 Capacity and Performance Test Plan and Scripts
Documents Ref:
D2. E2 Capacity and Performance Test Results
D2. E3 Capacity and Performance Test Summary Sign off
sheet
D-2-F Data Migration
Documents Ref:
D2. F1 Data Collection File Templates
P2.F2 Review the Template to Manual Master Data Team, Master Data Team of the country verifies the Data Templates,
check whether they are country compares with their needs. They inform RAC Master Data
sufficient and suitable Team about their additional requirements / Modification to the
existing data structure.
Documents Ref:
D2. F1 Data Collection File Templates
P2.F3 Prepare additional Manual RAC Master Data RAC Master data team prepares the templates as need by
templates / modify Team Country.
existing templates
P2.F4 Provide required Data Manual Country Master Data The master Data Team / Business analyst provide the required
/Automated Team / Business Master data in the collection file.
analyst
Documents Ref:
D2. F4 Data Collection File Templates
P2.F5 Master Data Check Manual / Master Data Team The Master Data Team Checks the data filled in by the
Automated Business analyst and performs initial validation.
P2.F6 Data Upload & , Manual / RAC Master Data Master Data Team uploads the data into QA environment for
Migration. Automated Team the purpose of Integration testing. Country performs data
tests during Integration testing cycles along with other test.
There are 3 trial conversions during integration testing and
final trial conversion is done before UAT starts.
P2.F7 Testing Manual Business Business Analyst/Master Data Team (Country) tests the
Analyst/Master Data migrated Data at each environment during each test phase
Team (Country) and validates.
At the end of each test phase any issues related to data are
resolved by the country / RAC Master Data teams.
If there are no issues, the test results are approved and signed
off by the Master Data Lead / Project Manager of the country.
The sign off after UAT and Regression tests but before
migrating to productions is the evidence for Control C. 2.4,
C2.6
Documents Ref:
D2. F3 Data Conversion Test Results
D2. F4 Data Conversion Test Summary Sign off sheet
D-2-G Defect Management
Documents Ref:
D2. G1 Test Results
D2. G2 TPR
D2. G3 Defect Monitoring Sheet
P1.G2 Allocate TPR Priority Manual Business Analyst Business Analyst (Country) allocates TPR Priority depending
(Country) on the Business needs and impact.
Documents Ref:
D2. G2 TPR
P1.G3 Follow up Manual Defect Coordinator Defect Coordinator (RAC) follows up with the Team for
(RAC) resolution of the issues
P2.G4 Verify Result Manual Application Application Specialist or ABAP / Interface Team & or RAC IM-
Specialist/ABAP BW Team (as the case may be) verifies the results and
Team/IM-BW Team analyze the problem.
Documents Ref:
D2. G2 TPR
P2.G5 Resolution of Problem Manual Application Application Specialist/ABAP Team/IM-BW Team identifies the
Specialist/ABAP problem and prepares solution- (whether related to
Team/IM-BW Team Configuration change / Code correction/IM-BW
Related/Infra/Others).
P2.G6 Implement Solution Manual / Application Application Specialist/ABAP Team/IM-BW Team implements
Automated Specialist/ABAP solution and performs unit test. If the results are as expected,
Team/IM-BW Team then the country Project Team is informed of the fact for
retesting.
P2.G7 Inform Resolution Manual Application If the results are as expected, then the country Project Team is
Specialist/ABAP informed of the fact for retesting by the Application
Team/IM-BW Team Specialist/ABAP Team/IM-BW Team
Documents Ref:
D2. G2 TPR
D2. G3 Defect Monitoring Sheet
P2.G10 Retesting Manual / Project Team (Testing Project Team (Testing Teams) Country, performs retest.
Automated Teams) Country
P2.G11 Set Status to Resolved Manual Project Team (Testing If the retest has passed, then the TPR status is changed to
Teams) Country Resolved by the Project Team (Testing Teams) Country.
P2.G12 Change Status to Manual Project Team (Testing If the Retest is not OK, TPR status is changed to ‘Reopened’
Reopened Teams) Country and sent back to RAC Defect Resolution Team.
Then the Defect Management cycle is invoked again.
Once the TPRs are resolved and retests completed, then the
process moves back to the respective test phases.
D-2-H Go Live Plan and Gate Control 2
P2.H1 Go Live Plan Manual Integration Lead The process starts during integration testing or after the
(RAC) completion of integration testing.
Documents Ref:
D2. H1 Cut Over Plan
P2.H6 Gate Control 2 Sign off Manual PMO (Regional) If PMO finds that all the criteria are met, he provides GC 2
signoff.
(Control C 2.7)
Documents Ref:
D2. H2 Sign offs for C1.1, C1.5, C2.1 to 2.6 and supporting
documents
D2. H3 Approved GC2 sign off Form
P2.H7 Send GC2 to Change Manual PMO (Regional) After providing the sign off, the PMO (Regional) sends GC2
Manager approval to Change Manger for approval for Promoting
changes to production.
Preparation of country specific test Solution Delivery Team Project Manager, Country Project Team, Country prepares the test plan
plans for Integration test (including
Interface and Security Test plans),
User Acceptance Test
Preparation of country specific test Solution Delivery Team Business Analyst of respective IT Team / SAP Team of different country BUs
plans for Regression Test countries
Integration Test Solution Delivery Team Project Manager, Country Project Team, Country prepares the test plans
User Acceptance Test Solution Delivery Team Project Manager, Country Project Team, Country prepares the test plan
Regression Test Solution Delivery Team Business Analyst of respective IT Team / SAP Team of respective country BUs
Live Countries
Volume and Stress Testing Solution Delivery Team Project Manager, Country IT, Country
Data Migration Master Data Team, RAC Master Data Lead / Project Country MD team prepares the data, RAC
Manager, Country verifies and and loads the data
Defect Management Project Team, country -- Application Specialist, ABAP Team / IM-
BW Team