October 2010 to present

1. October 2010 to Present:
After the announcement of the planned purchase of SABMiller by AB InBev, I accepted a two year Retention Package from
SABMiller at the end of 2015, after being identified as a key employee.
I have now applied for a Voluntary Seperation Package, being offered by AB InBev, as the roles I have been fulfilling for
SABMiller are not available in the new AB InBev structures.
Managing the Global SAP Solution Manager ChaRM functionality was my top priority, and I had involvement with:
 The maintenance and running of SAP CPS,
 Basis activities related to Solution Manager, specifically ChaRM.
 ABAP Development, including CRM Web UI development.
Managing the Solution Manager ChaRM functionality for SABMiller global landscapes involved:
 ChaRM has been implemented for Support and Release tracks in the Global SAP Environments on a single Solution Manager
instance (7.1).
 Because of the two tracks, the Retrofit processing has been implemented to keep the release and support tracks aligned.
 The ChaRM system manages transport movement in the ECC, HCM, SRM, CRM, BW and BW HANA environments as well as
JAVA ChaRM corrections for PI and Portal. Non SAP systems are also managed by the ChaRM system using a modified ChaRM
Admin Correction. The ChaRM normal correction is used for the support track ABAP based systems, and the project correction for
the release track.
 The environments managed by ChaRM contain in excess of 50 systems covering the release and support tracks.
 ChaRM Web UI customisation. Adding required custom functionality to the current standard ChaRM documents.
 ABAP based custom reporting for users as transactions on Solution Manager.
 ABAP based custom transport processing applications. I have developed these applications to run:
o Automated imports of the Transport of Copies, into all DEV and QAS clients, created when the status of the Normal and
Project corrections are set to “To Be Tested”.
o Automated imports of original transport requests, into QAS and Pre-Production systems, on the release track after the
setting of the “Authorised for Import” status of Project Corrections.
o Automated jobs to run housekeeping on import queues on all the various satellite systems to ensure that only requests
still to be processed are kept in the queues.
 Setup and maintenance of the transport routes via STMS on all Domain Controllers for all the SAP environments.
 Setup and maintenance of the all ChaRM projects. This includes the creation and maintenance of all Logical Components and
RFC connections required in the ChaRM projects.
 Ensuring ChaRM Project roles are created. The maintenance of these roles is then handed over to the Security team.
 Ensuring all required ChaRM user roles are maintained on Solution Manager and the satellite systems.
 CTS Plugin Maintenance for all satellite systems linked to ChaRM.
 Setting up and maintaining user documentation covering the ChaRM processes.
 Facilitate ChaRM training sessions for users new to the ChaRM process or requiring refresher sessions.
 TMSADM user setup and maintenance.
 All the testing and considerations required for upgrades. The last upgrade I was involved with was the move from SOLMAN 7.0 to
7.1.
 Business Partner maintenance for ChaRM requirements.
 ChaRM Category structure setup.
 Downgrade Protection has been set up and is currently used on the Support track.
 CSOL have been implemented on all ABAP based systems except BW.
 Building of import queues for Technical Cutover (TCO) processing on the release track for all production systems. This has also
happened on the support track at times.
 Processing of import queues via the ChaRM Project Task Lists over the TCO weekends. These are the production imports.
 Daily support of the ChaRM system during normal business hours. All user issues that need Global ChaRM team technical
assistance are investigated and resolved. This covers all transport related issues as well.
 After hours support of the ChaRM system. Due to the Global nature of the business support is required for 20 of the 24 hours each
day and on call support is required.