DOWNSTREAM-ONE

Support Pack Stack (SPS) Engagement

October 2013

Version 0.5
Contents

Introduction to Support Pack Stack (SPS)

SPS Project Activities and Timelines

Frequently Asked Questions

Open for further Q&A

2
INTRODUCTION TO
SUPPORT PACK
STACK (SPS)

3
 What is a Support Pack and why is it needed?

A Support Pack is a compilation of bug fixes and

enhancements to a version of SAP
It is sometimes called a Support Pack Stack (SPS)
SAP releases these fixes twice a year and strongly
recommends an annual update to the Support Pack Stack.
The implementation of the latest Support Pack Stacks
leads to improved reliability of our transactional processes
and applications by proactively removing known bugs and
introducing new functionality

4
Why do we need to implement a new Support Pack
now?
Previously Support Packs have been deployed as part
of the standard GSAP plan on a page update releases
In 2012 the regular Support Pack implementation did
not take place due to the GSAP upgrade
The current version of GSAP, upgraded in February
2013, is 5 instances behind the most recent Support
Pack
It is normal for Shell to be just 1 or 2 versions behind.
The latest version of the Support Pack is a pre requisite
for the HANA migration (which is part of the US Fuels
implementation) and makes it possible to take
advantage of new enhancements in SAP functionality 5
SPS PROJECT
ACTIVITIES AND
TIMELINES

6
SPS is a DV Sponsored Project with business support
SPS Steering Committee
Tobias Bahnsen (Delivery Vertical - DS Business), Tony Mistry (SAP CC Manager), Doutie Nadema (ITSO),
Chris Prince (GSAP), Frederik Paauwe (DS1 Live Country Integration & Assurance), Robert Wilkinson (IBM),
Roger Atwal (SAP), Rahmi Bayraktar (T-Systems)

SPS Project Management DS-1 S&I Project Management

Marcio Bentos/Paul Thompson Linda Chabouni

CoB/F Delivery Leads

Manu, Supply, Dis, LSC,
OTC, Fuels, Lubes,
Test Manager DS-1 S&I Local
Aviation, Marine,
Teams
Specialities, Retail/Cards,
Integration Manager Finance, FO, CP, MI,
Credit
Functional Leads
OTC, CRM, DIS, HM, LSC,
FSS, PGS, GAME, MI

Local GMs and CoB/F Focal Points

Manu, Supply, Dis, LSC, OTC, Fuels, Lubes, Aviation, Marine,
Specialities, Retail/Cards, Finance, FO, CP, MI, Credit 77
 Draft
High Level POAP for SPS
Challenging timelines for testing due to holiday periods and year-end activities. A
risk based testing approach is required. Testing strategy to be completed by 11th
October
CIA to be completed by 4th October and handed over to the CDLs/PEs.

CDLs will use the information from the CIA to create Business Impact Assessments
(BIA) which will use business friendly terminology and include details of the CAT
scope
Business Impact Assessments will be published to S&I teams who cascade to their
2013 2014
Sept Local CoB/F
Oct Focal Points
Novto review the
Decimpact andJan
CAT scope Feb Mar
KT to PE ITC sign off
ITC
27/09/13

CIA BIA BIA

(SPS Prep Q&A
BIA Readout 01/11 Country Readiness Sign-Off
Team) (CDLs) (S&I)
BIA Published 18/10
CIA handover to PE/CDLs 04/10 PSU
Year-End Regres
CAT Prep * CAT sion
Closing
Test
Go
PRD
Performance Performance test live
CAT Strategy Sign-Off 16/02/14
testing report Report
Today out
Care +

Copyright of Shell International Petroleum Company

*CAT Prep Detailed POAP on Slide 8

 BIA and CAT Scope: Roles and Responsibilities
Activities Responsibl Timeline
e
Develop BIA material (similar to Upgrade) including; CDLs 4th October to 18th
October
Change Impact Assessment for functional, look and feel,
technical changes
Testing approach and proposed CAT scope
Publish BIA materials / Confirm CAT Scope Change Central S&I 18th October
Control Process / Set-Up BIA Q&A Forums/ Provide BIA PMO
Readouts templates
Cascade BIA materials to local business focal points Integration 21st October
Leads
Review BIA materials and provide do-ability Local CoB/F 21st October to 1st
confirmation based on; Focal Points November
Change Impact (functional, look and feel, technical changes)
CAT Scope
Support BIA reviews and monitor Q&A Forums CDLs/PEs From 21st October
Facilitate BIA process locally, tracking progress and Integration 21st October to 1st
escalating where necessary Leads November
9
Collect business feedback and provide consolidated Integration By 1st November
 How will CAT testing work Strategy and Big Rules
mmary To be discussed/expanded and
A risk-based approach will be taken for CAT testing. Key focus should be where SPS
agreed by 11th October
technical or functional impacts have been found and critical business scenarios
Change Impact Assessment will capture impacts to GSAP. All functional and technical
impacts as a result of SPS will have traceability to at least one test script
The ITC and CAT scoping process will ensure alignment across SPS Project Team and the
business through weekly scoping meeting with CDLs/PEs
Potentially 700-800 unique scenarios which will confirmed with the test strategy (country
variations to be kept to a minimum). Testing country will be selected based on :
Key country for the process

Spread across clusters

Business critical scenarios will be defined from CCAT scope, forming a core upon which
the total CAT scope will be built
CAP interfaces are requested to be connected and available for test execution.
Confirmation of connectivity will be published during CAT prep
Kick-Off calls to be scheduled for CAT prep and execution. Daily progress update calls
scheduled during CAT
10
10
CAT Preparation: Detailed POAP

11
11
FREQUENTLY ASKED
QUESTIONS

12
 Draft
What is the impact of SPS Implementation on
Business Resources?

The key activity where business resources will be required is to

support CAT testing. Little or no training requirement is expected at
this point.
Process Experts and SuperUser resources will execute CAT between
25th November and 17th January.
As testing will be front-loaded the resource requirement will peak in
the first 4 weeks of CAT until Xmas
Resource requirements and do-ability will be reviewed by the local
business during the BIA Q&A phase between 18th October and 1st
November.
Note that after 20 December Year-End closing will impact the
availability of key FO resources so testing will need to be carefully
planned 13
 Frequently Asked Questions

1. Will C94 be refreshed prior to CAT?

C94 will be upgraded prior to CAT with the SPS. There is no plan to refresh with
latest production data

2. Will all CAPs be connected for the duration of the CAT window to allow
full E2E testing?
All CAPs connectivity in C94 are as-is. Review of CAP requirements will be
completed and connectivity schedule will be published during CAT prep.

3. Is there a detailed week by week POAP (to allow full alignment)?

Weekly discussions between Project team and Process Experts are ongoing.
Detailed CAT prep POAP has been created, including weekly requirements. CAT
Prep and Execution calls will be held with S&I/CDL/SPS teams to ensure
alignment.

4. There is no defect resolution window?

The defects identified follows the sequence of testing and will be remediated
during the test window. CAT test window has been extended to Jan 17th. We need14
to front load testing before Christmas with defect resolution and final testing in
 Frequently Asked Questions
5. When is the individual country scope ready? - number of tests per COB/test
objectives?
Once ITC scope is finalized, CDLs will define CAT scope by 18th October. At this point it
will be cascaded for local review/consideration

6. Will we get scripts including the right roles and transactions for the tests or do
we need to work without scripts?
We will use existing scripts already available in HPQC. Discussion underway to provide
offline scripts was we did for GSAP Upgrade more info during CAT prep.

7. In case of test questions WoW do the countries go to GSAP SMEs or PEs?

Clarification can be directed to S&I and SPS Project team

8. I do understand there will be no local BIA but a central CIA only. Correct?
POAP has now been updated and CDLs will create BIA materials by 18th October. Local
review and do-ability readout required by 1st November.

9. Is there any local readiness assessment or sign-off on any activity or milestone

within the project expected and if so how should this work without BIA?
BIA is created and Local do-ability should be provided by 1st November. A country 15
 Q&A

Copyright of Shell International Petroleum Co. Limited 16

1
 Appendix

Copyright of Shell International Petroleum Co Ltd 18

 Draft
DS-One GSAP Service Pack upgrade
IT project organisation

SPS Steering
Committee

SPS Project Manager

Marcio Bento / Paul
Thompson

SPS Test Manager

Belinda Yee /
Porchelvan

CRM DIS FSS PGS/GAME Team MI Solution Integration

OTC Team Lead HM Team Lead Heinz LSC Team Lead ABAP Lead Maneesh
Team Lead Team Lead Team Lead Lead Team Lead Andy Team Lead John
Mangesh Katyarmal Dirks Russell Coronado Kuriyedath
Fazal Hamid Jason Meier Santosh Narayana Joey Chung Chong Smith

OTC DIS FSS

CRM Functional Lead PGS Functional Lead HM Functional Lead LSC Functional Lead MI Functional Lead
Functional Lead Murari Janka Functional Lead Functional Lead Siva RajaGuru / Pratyusha Dileep Kumar Shaik Mastan
VinodKumar
Hariprasad Shyam Thallikar reddy / Swati

GAME Functional
OTC Build Focal CRM Build Focal Point DIS Build Focal FSS Build Focal Point Lead HM Build Focal Point LSC Build Focal Point MI Build Focal Point
Point Jayan Jalla Lakshmi Point Kartik Vandana Rama Devi Dharsana Dube Guruprasad
Suresh

OT Test Focal Point CRM Test Focal Point DIS Test Focal Point FSS Test Focal Point Build Focal Point HM Test Focal Point LSC Test Focal Point MI Test Focal Point
Vinayaka Kiran Rupkumar Balaji AS Jasleen Kaur Girraj Venkata Dillep Bhavya

PGS/GAME Test
Focal Point Rakesh /
Raghavendra

SUS Test Focal Point

Praveen Kumar
 Current
assessment of
impact per
process area
Copyright of Shell International Petroleum Co Ltd 20
 Summary of expected changes identified so far
This overview will be updated once the Sandbox testing environment has
been uploaded with the new Service Pack.
Functional Technical Look & feel RIEFs Narrative

OTC - - Changes mainly found in the billing

and AR space

CRM - Mainly technical changes all within

CRM web user interface
FSS - Changes mainly on document
journal and print program
PGS - Changes mainly on PR and PO
screen with introduction of
document flow
DIS - - Technical changes to delivery, SD
shipment and TD shipment create
and update functionality
GAME - extra navigate option in
Maintenance Order and Maintain
Tasks List
HM - - Changes mainly technical.
Around 10 RIEFs are impacted.

BW - - - Technical Changes mainly on BW

backend
LSC & APO - Minimal APO impact so far from
SBX testing, and LSC has only
encountered technical issues. 21

SUS/SRM - Changes mainly of look and feel

 FSS Change Impact Summary
Process team Functional Technical Look and Feel RIEFs requiring
changes changes changes remediation

FSS 0 21 0* 4

Functional changes
Additional configuration options introduced by Service pack, as the new configuration options not being used
now, no impact.
Legal fiscal correction OSS notes will introduce functional changes. Panaya is not providing the details of functional
change, hence we have to wait for Service Pack to be applied in Sandbox to understand this impact.

Technical changes:
21 programs required code corrections

Look and feel changes:

*Look and feel changes anticipated in Legal correction notes on reports. Panaya does not provide this information.
We have to wait for Service Pack upgrade in Sandbox.

RIEFs changes:
4 RIEFs required to changes

22
 PGS Change Impact Summary
Process team Functional Technical Look and Feel RIEFs requiring
changes changes changes remediation

PGS 0 13 + 3(TBC) 0 0

Functional changes
No Functional changes anticipated however re-evaluate after remediation in Sandbox

Technical changes:
13 program which was previously clone from standard SAP programs will be upgrade with latest SAP coding but
existing GSAP design remain un-change.
3 Clone program pending final confirmation from next Panaya Usage statistics.
27 PGS relevant standard transaction code/programs will be upgraded.
29 customize transaction code/programs will be upgraded.
In SUS, 15 notes will be applied to correct program bug/errors and 92 are basis relevant changes.

Look and feel changes:

No look and feel changes anticipated however re-evaluate after remediation in Sandbox.

RIEFs changes:
No RIEF changes anticipated however re-evaluate after remediation in Sandbox.
23
 LSC and APO Change Impact Summary

Process team Functional Technical Look and Feel RIEFs requiring

changes changes changes remediation
ECC LSC 0 182 0 0

SCM APO 0 31 0 0

Functional changes
ECC LSC
No Known functionality changes identified impacting existing business process
Further evaluation pending once SPS is applied to SBX

Technical changes
SCM APO
Side effect notes have only been evaluated
Based on evaluation, 31 solving notes to be applied to address incoming causing notes
Further evaluation pending once SPS is applied to SBX (e.g. Custom code impact)
DP, BW platform, PPDS, and SNP identified as impacted modules

24
 LSC and APO Change Impact Summary CONT

Technical changes
ECC LSC
Based on side effect evaluation, 9 solving notes to be applied to address incoming causing notes
Panaya identified 104 potentially impacted BDCs however, no screen changes were detected.
Testing will be conducted for these transactions
Analysis identified 29 notes to be re-applied that currently already exist in production (notes to be
reset by SPS)
40 programs which were previously cloned from standard SAP programs will be upgraded with
latest SAP coding but existing GSAP design remain un-changed.

Look and feel changes:

No look and feel changes anticipated however re-evaluate after remediation in Sandbox.

RIEFs changes:
No RIEF changes anticipated however re-evaluate after remediation in Sandbox.

25
 CRM Change Impact Summary
Process team Functional Technical Look and RIEFs requiring remediation Key Message(s)
changes changes Feel
changes
CRM 0 62 13 TBD After SP import in Sandbox Analysis based on Side Effect report only
system. which does not include custom built
objects.
Custom Objects have been identified and
will be analyzed after SP import in Sandbox
system.

Functional changes
No Known functional changes identified that will cause a change to existing business process functionality.
Further evaluation after sandbox remediation.

Technical changes
Analysis based on Side Effect report only which does not include custom built objects.

Look and feel changes:

Look and feel changes anticipated however re-evaluate after remediation in Sandbox.
Minor unnotice-able look and feel changes mostly around fixes. Ie. Defects in scroll bar in transaction launcher,
print printer defects

RIEFs changes:
Custom Objects have been identified and will be analysed after Support Pack import in Sandbox system. 26
 OTC Change Impact Summary
Process team Functional Technical Look and Feel RIEFs requiring remediation
changes changes changes
OTC (Non-CRM) 0 132 None Functional : OTCE411, OTCI195, OTCE189
Technical : OTCI195, SBCR086
TBD : After Validating Batch Input program

Functional changes*
No Known functional changes anticipated to change existing business process. However, further impact to be re-
evaluate after remediation in Sandbox

Technical changes
11 of Technical changes are to fix Syntax error (4) / Replace use of Obsolete table (7) . Rest all to Validate Batch
input program (45 ) & Adjust cloned program ( 64)
3 of Technical changes are to adjust modified object, remaining impact due to reset (7) / approve(2) OSS note
which are part of SP7 but implemented beforehand.

Look and feel changes:

No look and feel changes anticipated however re-evaluate after remediation in Sandbox.

RIEFs changes:
As indicated above; to be re-evaluated after remediation in Sandbox

Note: Preliminary analysis utilizing 3rd party tool Panaya for ECC items. Statistics extracted and evaluated DEV environment as baseline (e.g. Existing
components, usage, etc.)
27
 SPS 2013 Overview & Status
Background
SAP releases bug fixes via Support Pack bi-annually.
Annual SPS implementation has always leveraged GSAP POAP/Release Deploy
BAM Led SPS deployment since 2010 and was updated in 2011
SPS 2012 was cancelled due to Upgrade
SPS 2013 was unplanned as upgraded GSAP was deployed in 2013.

Key Drivers
DS GSAP upgraded by Feb 2013 is 4 SPS behind ( normally 1- 2 SPS behind)
Annual support pack required for DS GSAP
Pre requisite for HANA migration
Enables future delivery of new capability via enhancement packs

Proposed Scope
Latest version of Enhancement/SP as of May 2013 ( see Annex for details)
SABRIX will not be upgraded as Australia and USF functionality going live with existing version
NLS scope confirmation pending

This Analysis
Preliminary analysis utilizing 3rd party tool Panaya for ECC items.
Statistics extracted and evaluated DEV environment as baseline (e.g. Existing components, usage, etc.)

28
 FSS Change Impact Summary

Category Task type Number of

tasks in
scope
Adjust Cloned Program 15
Fix Code due to Syntax Error 6
Code corrections
Replace Use of Obsolete Table 1
Validate Batch Input Program 37
Modifications Reset Note 32
Modification adjustment 1

Code corrections have impact on four RIEFs.

Around 33 OSS notes applied by project/support needs to be reapplied again.

29
 GAME Change Impact Summary
Process team Functional Technical Look and Feel RIEFs requiring
changes changes changes remediation

GAME 0 4 0 2

Functional changes
No Functional change anticipated however re-evaluate after remediation in Sandbox

Technical changes:
4 program which was previously clone from standard SAP programs will be upgrade with latest SAP coding but
existing GSAP design remain un-change.
37 standard transaction code/programs will be upgraded.
17 customize transaction code/programs will be upgraded.

Look and feel changes:

No look and feel changes anticipated however re-evaluate after remediation in Sandbox.

RIEFs changes:
2 RIEFs required to changes as table was obsolete in new support pack. Existing information will required to
extract from other table.
30
 DIS Change Impact Summary
Process team Functional Technical Look and Feel RIEFs requiring
changes changes changes remediation

DIS 0 82 0 0

Functional changes
No Functional changes anticipated however re-evaluate after remediation in Sandbox

Technical changes:
62 program which was previously clone from standard SAP programs will be upgrade with latest SAP coding but
existing GSAP design remain un-change.
8 DIS relevant standard transaction code/programs will be upgraded.
2 customize transaction code/programs will be upgraded.
In DIS, 27 notes will be applied to correct program bug/errors and 72 are basis relevant changes.

Look and feel changes:

No look and feel changes anticipated however re-evaluate after remediation in Sandbox.

RIEFs changes:
No RIEF changes anticipated however re-evaluate after remediation in Sandbox.
31
 HM Change Impact Summary
Process team Functional Technical Look and Feel RIEFs requiring
changes changes changes remediation

HM 0 21 0 ?

Functional changes
Additional configuration options introduced by Service pack, as the new configuration options not being used
now, no impact.
Legal fiscal correction OSS notes will introduce functional changes. Panaya is not providing the details of functional
change, hence we have to wait for Service Pack to be applied in Sandbox to understand this impact.
Technical changes:
21 programs required code corrections
Look and feel changes:
Look and feel changes anticipated in Legal correction notes on reports. Panaya do not provide this information.
We have to wait for Service Pack upgrade in Sandbox.
RIEFs changes:
? RIEFs required to changes

32
 HM Change Impact Summary

Category Task type Number of

tasks in
scope
Adjust Cloned Program 17
Code corrections Fix Code due to Syntax Error 4
Validate Batch Input Program 40
Modifications Reset Note 27
Modification adjustment 3

To be evaluated:
Code corrections have impact on ? RIEFs.
Around ?? OSS notes applied by project/support needs to be reapplied again.

33
 BW Change Impact Summary
Process team Functional changes Technical changes Look and Feel
changes

MI 0 35 0

Functional changes
No Functional change anticipated.

Technical changes:
1 technical impact for Consolidation (BCS).
15 technical impact for Reports.
19 technical impact for Database Objects.
Key message: Impact based on SP side effect report and all technical impact have solving notes that will be apply.

Look and feel changes:

No look and feel changes anticipated.

34
 Draft
NEXT STEPS

Functional Leads to schedule weekly calls with Process Expert (PE) / CoB
Delivery Lead (CDL) from September 2, 2013 to discuss the following:
Further Q&A on CIA by Process area
Input to BIA Material Publish Oct 4, 2013
Sandbox remediation and findings

ITC scoping ITC scope sign-off Oct 4, 2013

CAT scoping CAT scope sign-off Nov 15, 2013

3
 SPS 2013 escalation POINT Feb 2014
CORE TEAM Go-To-Matrix
Process Area Main Focal Point

FSS Santosh Narayana

GAME Joey Chung

HM Heinz Dirks

LSC Russell Coronado

Andy Chong
MI

PGS Joey Chung

DIS Jason Meier

OTC/CRM Fazal Hamid

Integration/Testing Belinda Yee

Upgrade Manager Marcio Bento

Security Andreas Stumpenhorst

SOM ABAPER Maneesh Kuriyedath

36

3
SPS related links
Please find below the links to the relevant documents for SPS
BELINDA TO PROVIDE LINK
Description

Consolidated Change Impact Assessment (CIA)

Details of CIA spreadsheet

ITC Sign Off Scope

37