SAP Integration developer specializing in SAP PO, Workflow, ABAP and Netweaver Gateway development.

This the company through which Richard works as an SAP Developer.

This project involved the upgrade from ECC5 to ECC6. Richard's primary role was to migrate custom JAVA web-dynpro ABAP applications to web-dynpro ABAP. His other roles on the project also included supporting the upgrade of existing applications to the ECC6 platform and offer advice on design strategies for migration of existing XI interfaces to the new SAP PO instance.

Richard was a SAP developer on the Finance Futures 1 project which was the merger of 9 Qld government agencies and their disparate SAP systems into a single SAP solution.

While at the department Richard had the opportunity to build a fully functioning purchasing approval APP in UI5 that was integrated into the departments custom purchasing approval solution. This development leveraged much of the work that he had done previously in optimising the existing purchasing approval solution at DETE. As one of Richard's connection you will be able to review the attached document for further details.

Richard took on a position within the departments SAP business support unit while the department transitions to long term support arrangements. He took on the role as primary support within the technical team for the business's workflow and PI implementations as well as other development activities.While in this position he had the opportunity to re-develop the departments purchasing approval process (i.e. custom workflow, approval screen and logic within the standard SRM and ERP purchasing functionality) to fix long standing reliability issues with the solution.

Richard started work on this project during blueprint doing scoping work and writing developing standards around ABAP, Web-Dynpro, Workflow, Netweaver BPM and PI. His role on the project was to co-ordinate the development process with project management, interview and select potential development resources, co-ordinate the allocation of work to those resources and empower them to produce a quality outcome for the project. The project successfully went live on the 1st of October 2013 and Richard stayed on until the middle of November during the warranty period after which the program ended.Along with a co-ordination role, Richard participated in development activities and configuring components of the solution. In particular the PI services registry, the central SOA manager and SOA manager in each of the other systems connected to the services registry. He gained some valuable exposure to developing applications using Netweaver BPM and Visual Composer. He was also responsible for the development of new workflows on the project along with the enhancement and configuration of enhanced notifications for those workflows.He was also responsible for developing and documenting guidelines for the use of floor plan manager (FPM) for WD4A developments. As general rule custom web-dynpro components were not used and only developed when absolutely necessary. Rather the project used standard FPM components and feeder classes to enable web-dynpro functionality, a much quicker, cost effective and maintainable approach to FPM and WD4A development than building custom components.

Richard was on the Wattlebird project at Holcim Concrete where he was on the integration team which was responsible for delivery of interfaces and workflows at that organisations implementation of SAP. Richard was invited onto the project by the technical manager after being sought out to offer advice on how to use workflow in a complex integration requirement between SAP and Command Concrete Holcim's batching software. He was doing a mix of development on this project including Web-Dynpro/FPM, Workflow and PI.

Richard was integration lead at Revenue SA (South Australia) working on that organization's implementation of SAP's TAX and Revenue Management solution (release 1). TRM is a complex development environment that requires the integration of a number of SAP technologies, including Web Services (PI), interactive Adobe Forms, BRF+ and Web-Dynpro. His own responsibilities encompassed the overall technical design of the solution during blue print as well as the actual development of that solution during realisation which included among other things development of interactive adobe forms, complex BRF+ applications and business workflows which were used extensively to manage the progression of forms through their life cycle as well as the BRF+ based framework that was developed to manage a forms status and handle exceptions through the life cycle of a given form(s).

Richard was consultant contracted to SAP at the Office of State Revenue on their grants, tax and revenue management solution. OSR's solution was implemented on a number of platforms including SAP CRM 2007, TRM and PI. In particular he was working with adobe forms, the SAP business rules framework in both the CRM and TRM systems in addition to the development of a number of interfaces in PI.

Richard was a consultant contracted to SAP working at RIO Tinto on that company's ABS program as an XI developer, ABAP & Workflow technical advisor. He worked primarily within the integration team while on the program, although during the early stages of the program he developed the framework/standards that were used for all RIO TINTO business workflows. As an XI developer he was responsible for the development and support of interfaces that used a variety of middleware technologies including XSL stylesheets, ABAP and the SAP graphical mapper. The development of a number of XI BPM's for both synchronous and asynchronous scenario's and the the use of a number of communication technologies including SOAP, RFC's, IDOC's, & Files.

During this period he worked on the migration of a number of comalco non XI interfaces to XI.

ABAP/workflow developer.

ABAP/Workflow developer.

Richard started his career as a software developer at Qld Rail and worked as a visual basic developer and ABAP developer on the SAP R/2 implementation in that organisation.