Development of Solutions for SAP Information Systems

Galaxy Header

SAP CERTIFIED ASSOCIATE

" Evolution Not Revolution

The emergence of cloud computing, cloud native, and REST, along with the clean core extensibility principle, has necessitated an evolution of the ABAP language and ABAP development models that developers have used over the years. Luckily, ABAP has the ability to evolve based on changing technology and needs.In ABAP's earliest days as a fourth-generation programming language (in the 1980s), it was primarily used to do reports on the SAP R/2 platform. With the emergence of SAP R/3 (in the 1990s), the languagewas enhanced so that both SAP and customers could use it to create programs and extensions. With service packs to enhancement packs to release upgrades, the ABAP language has continuously evolved to meet the needs of the moment. While admittedly the shift to cloud computing was a fundamental change, nevertheless, SAP's strategy for ABAP is centered around "evolution not revolution", meaning that changes made to ABAP to adapt it to cloud computing were precise, controlled, well thought out and incremental. Most importantly, customer needs were always paramount."

SAP Fiori Application Developer

(C_FIORD_2404)

SAPUI5 Foundation, SAP Fiori Elements & Smartcontrols, Deployment & Testing, SAP Fiori Architecture Overview, OData and Advanced Data Handling, Extensibility in SAPUI5, Fiori Launchpad Configuration, SAP Fiori Strategy, Standards and Guidelines

Core ABAP Programming, ABAP Core Data Services and Modeling, ABAP RESTful Application Programming Model, Object-oriented design, SAP Clean Core Extensibility and ABAP Cloud, ABAP SQL and Code Pushdown

Particle Animation

Back-End Developer - ABAP Cloud

(C_ABAPD_2309)

(C_TAW12_731)

ABAP with NETWEAVER 7.31

Last position

SAP ABAP DEVELOPER (FSCM) Application Architect at Client UBS BANK, with Wipro Technologies

From 07/2024 until 11/2024 (4 months) in UBS Headquarters, Kappeli, Zurich, Switzerland (onsite)

The Client

The Team

As an external member of the SAP ABAP team for UBS CCA (Client Cash Accounting), I collaborated with business functionals and Product Owners from the CCM (Client Cash Management) team. Hired to cover ABAP team absences due to leave, I quickly familiarized myself with key reports and processes, including mainframe job communications, parallel processing, and SAP UBS CCA custom tables and T-codes (e.g., ZSL) related to client account settlements and payments. In addition to supporting CCA/CCM colleagues and addressing incidents in CCA production, I contributed to the SAP HANA V7.5 Conversion under the UBS SAP CCA 2027 Vision Project. This involved creating parameterized CDS views for UBS CCA custom tables, exposed as OData services in Eclipse and SAP Gateway. During this period, I also resolved a critical housekeeping issue due to the SAP HANA Data Migration. UBS had accumulated millions of account records dating back to 2004, with only the past five years legally required. I designed and implemented a complete solution for CCA real settlement housekeeping (ZCCA_HOUSEKEEPING) with configurable parallel processing. This solution used ZBAPI_HOUSECLEANING in parallel updates, tracked processed records, and preserved entries related to possible future account reactivations. It also supported configuration of batch sizes and parallel processes, preventing timeouts and memory issues, with outputs in test and real modes, viewable online or in job logs. The solution was extended to other processes (Simulation Settlement, Payments, Shopping List) using the same parallel-processing framework. I documented the solution in MS Visio with UML, covering data mappings, data flow, and specific parallel-processing algorithms. Additionally, I developed several different SAP ABAP prototypes for REST API consumption (supporting XML and JSON), also an ABAP prototype for automatic generation of STID

Click here for details

Click the logos for navigation..

"ABAP has always evolved in such a way that it is generally "backwards compatible". This means that changes are usually forward looking only. Existing code does not necessarily need to be adjusted to comply with any new ABAP standards or features. Developers simply use the new features going forward in their project developments.", by SAP

It is a pleasure to have had the chance of learning while developing with SAP ABAP for these great companies

Previous projects:

For details click here

Check details

It is a privilege to showcase the Esteemed Companies that have always steadfastly supported NMMTech, furnishing all essential tools and technologies to meet every requirement:

Very experienced working with SAP ABAP, in different cultural SAP Business Environments, across multiple Business Industries, always evolving from R3, through ERP, until S/4 Hana.

NMMTech's commitment to Developing and Evolving with SAP ABAP has allowed remarkable journeys to have happened, amazing travels, discoveries, adventures, and conquests.

Our Collaborators and Business Partners