Prasath Sivaraman: Working Currently Lead SAP Technology Consultant in Bangalore, KA

Team Size 5 Duration June 2016 to May 2018 Platform ABAP, BMC Remedy, Service now Role ABAP Developer, Lead Architect, Integration Developer, Maintanace Support Company Volvo Group India Pvt Ltd, Bangalore, India Project Explanation 1. BSR - Fetch Balances from GL Ledgers & Assets & Open & Cleared Items data and integrate the Cadency Tool for Volvo Stakeholder to review year & Period wise Profit and Loss Analitical Report. 2. Parma Master Data Integration - Master Data of Vendor & Customer master Data & Internationalize Data & Bank information integrated to Master Finance System 3. Ondemand System integration - Masterfinance System send various Invoices like Elander customer invoice to ondemand system via PI and MQ Channel and Ondemand system used by customers 4. VCE Excel Project - Worked as Lead Architect for VCE Excel Company code legal separation from master finance system on EA Certification to get approved from Volvo Architect Office Challenges and Deliverables • Developed Report to fetch GL Open & Clear Items Balances extraction based on Period & Profit centre wise cumulated using Transaction FS10N and send to Cadency System via File Interface. • Developed Report to fetch Vendor & Customer (FBL1N & FBL5N) Open Items Balances & Balance Carryforward from last fiscal year open items Extraction and send to Cadency System via File Interface. • Developed Report to Fetch GL Open Items Balances & Balance Carryforward from last fiscal year open items and send to Cadency system via File Interface. • Developed Report to Fetch Asset Profit Centre Balances extraction Based on Period & Profit centre wise cumulated using Transaction AR01 and send to Cadency System Via File Interface. • Developed Proxy to get Bank Key Information from Parma System and create as as change in Master finace System via FI01 & FI02 • Developed Proxy to get IBAN Information from Parma and update Respective Vendor & Customer Master Bank data with Proper IBAN data. • Developed Custom CREMAS and DEBMAS IDOC to get Parma data as inbound interface to Master finance system to update Vendor & Customer master. • Developed Custom ADRMAS to hold International Data and update respective masters with Different Country language Address Data. • Played Lead Architect Role for VCE EXCEL Project on India & Russia & Malaysia Regions for EA Certification purpose. • Involved in Support & Maintanace Acitivity & Year End Activity in Maserfinance system also handled tickets in BMC Remedy & Service Now Tools. • SAP ABAP&PI Implementation - Deutsche bank Integration

TITLE Deutsche Bank Integration Client Deutsche Bank, Bangalore, India DB Clients United Sprits private limited Team Size 2 Duration AUG 2015 - June 2016 Platform SAP PI 7.4 , ECC 6.0 Adapters used XI, File Role PI & ABAP Developer Company Arteria Technologies, Bangalore, India Project Explanation It aims to provide seamless link between the Bank and Customer using secured connection for automating the payment processes. Forword Flow: Customer make the payment in SAP ECC and its send to Customer SAP PI. Here we are converting the IDOC format to ISO XML format using PI configuration after that message will send to Bank PI (DB). Reverse Flow: After receiving the payment, bank will send MT940 File as per the customer requirements. Challenges and Deliverables • Developed Inbound Proxy to Process MT940 files to Post BR Document Type entry using BAPI and posting Entry would be customer account posted as credit and Incoming GL posted as Debit. • Developed Report to Clear DG/JV/AB Document on basis of document type priority using F-32 Transaction Batch Data Communication Method and this report scheduled via Background job. • Developed Inbound Proxy to Process MT940 files to Post ZR Document Type entry using BAPI and posting Entry would be Incoming GL account posted as credit and Main GL posted as Debit. • Clearing of Incoming GL using Standard Configuration of F.13 Transaction. Java Mapping • USL 4 Regions FTP File to File Scenario Implemented for USL for Remote Cheque Printing process. • SAP ABAP Implementation - SONY-RELIANCE Integration TITLE Sony - Reliance Integration

Client Sony India, Bangalore, India Team Size 2 Duration JAN 2015 - JULY 2015 Platform ECC 6.0, SAP PI 7.4 Adapters used XI, File Role ABAP Developer Company Arteria Technologies, Bangalore, India Project Explanation In the existing scenario, the Reliance is exchanging the documents with Sony using Mails and they want to automate the Process using EDI. Reliance will be sending the PO using IDOC XML and the same need to be acknowledged by Sony and send the Technical Acknowledgement within 10 Min. Sony will create the Invoice against the delivery and ASN needs to be sent to Reliance, the moment Invoice is created in SAP. The ASN will be sent with serial no #, the ASN received by Reliance will be acknowledged and if there are any errors in the ASN, then Sony needs to resend the ASN. The Daily Stock data will be pushed from Reliance to Sony system. The Secondary Sales data will be pushed from Reliance to Sony on Daily basis and Monthly Once. Challenges and Deliverables • Configured Inbound Function Module: IDOC_INPUT_ORDERS for Message Type ORDERS to convert Reliance Purchase order into Sales order and SO will be created in Sony SAP Environment. • Logical System Created and Configured Process code for Sales Order Creation. • Developed report to re-trigger ASN using outbound proxy Proxy Development • Developed Outbound Proxy to validate and avoid posting of duplicate PO in Sony SAP Environment. • Developed Outbound Proxy to trigger ASN from Sony sap environment to Reliance, While creation of Invoice using VF01 Transaction. • Developed Inbound Proxy to update Daily Stock Details in ZTable. • Developed Inbound Proxy to update Monthly Stock Details in ZTable. Enhancements: • Created enhancement on standard function module to validate duplicate PO. • Created enhancement on standard transaction VF01 to Triggered ASN. • SAP ABAP Implementation - HSBC Bank Integration TITLE AR Invoice Level Reconciliation

Client HSBC BANK HSBC Clients PEPSICO INDIA Team Size 1 Duration OCT 2014 - DEC 2014 Platform ECC 6.0 Role ABAP Developer Company Arteria Technologies, Bangalore, India Project Explanation Invoice Level Reconciliation using Customer Payments, This implementation involves integration of Bank and its Customers Sap environment. Bank provides its customers with SAP system an interface to the Bank's Payment services through multiple channels and for different payment formats. This interface to SAP Accounts Accounts Receivable module facilitates transfer of Incoming payment details from Bank to the customer's SAP system. Foods Company Development: Challenges and Deliverables • Developed Report to extract Customer Open items (FBL5N) based on Bank File Format to Application server and those files pushed to HSBC FTP Location. • Developed Report to post Collections CSV file Details via F-28 Transaction using Bata data Communications and if any Credit Entries appeared in file then that entries post to Exception GL using BAPI_ACC_DOCUMENT_POST. • While posting Collection Files handled scenarios like fully paid, partially paid, Over Paid, Credit Note Scenarios. • While posting Collections files details of success and exceptions entries sent to user via Email Attachment for their reference. • FI OT83 Configuration Done HSBC External Transaction code for MT940 Files upload via Standard FF_5 Transaction and post like on account entries in sap environment. • Developed Report to Clear Incoming Payments GL of debit and Credit matching entries via FB05 Transaction BAPI. Beverage Company Development: Challenges and Deliverables • Developed Report to extract Customer Open items (FBL5N) based on Bank File Format to Application server and those files pushed to HSBC FTP Location. • Developed Report to get files from Application Server and post those Intraday (MT942) File in Sap Environment. • Developed Report to get Collection CSV files from Application server and Clear Invoice and Payment Entry via F-32 Transaction Batch Data Communication method. • While posting Collections files details of success and exceptions entries sent to user via Email Attachment for their reference. • Developed Report to post collection payment entries from one sweep account to another Sweep Account using MT940 File. • SAP ABAP Implementation -Standard Chartered Bank Bangladesh / India Integration TITLE Bank Corporate Connectivity Kit Client SCB Bank Integration SCB Clients Robi- Bangladesh, JCB INDIA, TCL, Luminious,Wheels India, Rashi, Bamburi (Kenya Customer) Team Size 1

India Project Explanation The purpose of the project is to integrate the various customer SAP systems with Bank portal Using ALE/ IDOC and Middleware Server XI/PI system to send payments to bank and reverse Feed update using BANSTA Inbound PROXY. Challenges and Deliverables • F110 Automatic payments Transactions details captured via Standard IDOC using Message Type PAYEXT to transfer Vendor payments like Cheque, Demand Draft, and Electronic Payment Transactions to Bank. • Developed report for Trigger Manual Payments F-58/F-53 transaction details to capture via Custom IDOC and contains Payments, Invoice line items and Deductions like Invoice level TDS, WCT data and send to BANK Via PI Server. • Developed report for Trigger GL to GL Payments using Custom IDOC to transfer funds from company one account to another account. • Developed Custom Report to Trigger Collective Payments IDOC Data to Bank via ZWE14 Transaction. • Bansta Inbound Proxy using FB09 Transactions to update Cheque number/ UTR Number in Assignment Field in sap. • Developed Inbound Proxy to Reverse Payments Documents / Cheque Number which are payments Rejected at Bank Portal. User Exit and Enhancements: • Implemented user exits FEDI0004 for amending Bank IDOC format Payment Structure for triggering F110 Payments. • Enhanced Standard Basic Type of PEXR2002 and inserted Custom Segment to Capture Payment Advise Details. FI Configurations: • Created RFC Destination, Port, Partner Profile Configuration Based on customer Requirement • Cheque Lot Configured for corresponding House Bank and Account ID using Transaction FCHI. • FI FBZP configuration done for Vendor Payment Methods. JAVA Mapping: • Implemented Java Mapping for Dynamic Configuration for AS2 Adapter to pick file from AS2 Adapter and place same file name as a file in file Adapter using Rashi & SanDisk Integration. • Implemented Java Mapping to fetch Account number from MT940 File and same Account number as a file name in File Adapter for SCB Bank & Bamburi Customer Integration. • SAP ABAP Implementation - BANKING TITLE Banking Client Standard Chartered Bank, ANZ, AXIS, Rattnakar,HSBC Bank Clients HCL Info Systems, Roots, ZS Associates, Kehin Fie,Ruchi soya, Pi Industries, Mercedes Benz, Brittania, J&M,Godrej..etc (Nearly 83 customers) Team Size 6

India Project Explanation Bank provides its customers with SAP system an interface to the Bank's Payment services through multiple channels and for different payment formats. • This interface to SAP Accounts Payable module facilitates transfer of outgoing payment details from the customer's SAP system to Bank. • The package is also provided with the Re-Extraction for payments in case of failures. Challenges and Deliverables • Implementing automatic payment & manual payment program for vendor payments customer payments & salary payments • Installed the encryption kit and downloading the file with encryption FI Configurations: • FBZP Transaction Configurations done based on Customer company code, payments methods, house Bank, Bank Determination, GL Configuration, Debit bank account number maintenance to make payments Via F110 Transactions. • Cross Company Code Payments Configurations. • OT83 Transaction Configurations, like Account Symbol Creation, Assign Account Symbol to Accounts, Create Posting Keys, Define Posting Rules for Posting Keys, Transaction Type Creation, External Transaction Type Configuration. Etc., • Bank Key Creation, House Bank Creation based on Customer Requirement. Dialog Programming: • Developed Table Control Screen to provide End users flexibility to select particular payments while processing bulk of payments using Bank Payment Extraction Kit. User Exit and Enhancements: • Implemented user exits FEB00004 for phrasing MT940 File and validate corresponding Company Bank account Number to process file via Standard Transaction FF_5. BADI Enhancement: • Enhanced Standard BADI Implementation FEB_BADI for update UTR Number in document Header Text for Reconciliation Posting Entries. BTE • Developed a BTE in F110 to remove the payment block in the invoices as per client requirement at the time of payment proposal. DECLARATION I hereby declare that the above written particulars are true to the best of my knowledge. Place: Date: