Worked & simulated 3 aftersales FBs.

Worked on ECU replacement page disabling issue.It includes trail and error mechanism. Did changes simulated it also did validation on module level along with DICV team and completed

1) License Portal Technical Discussion with James Sheets (MSSU). Had a Live session and modified a few files of the license portal application to test the password reset email notification with the advice of James.2) Tried some trials and checked the log information along with James.3) Checking the feasibility for an alternate option by reviewing the application deployed in the DICV Server.

1) Did some debugging trials to find the root cause of the password reset email receiving issue before reaching out to James Sheets.2) Later, Coordinated with James Sheets (MSSU) for password reset issues in the OES Tool.3) Tried some trials as instructed by James

1) To troubleshoot the password reset issue, I checked the SMTP details on the code and tried changing it with DICV SMTP to check the email was received. 2) Later, created a test account in Gmail, enabled SMTP, tested the email working through a script written in PHP, and verified email was sending out successfully. 3) Changed Gmail SMTP info in the OES Tool Mail Properties Configuration file but email was not received as expected.

1) Shared OES V305 VATBIN to DICV Team2) Modified the GetFlashingData API to test the V305 flashing by defining the part number and the A2L file statically by using the reference name BSVI_Engine_OBDI_V305 by accessing the input data from CDMT via API directly.3) Coordinated with Jey Ganesh on the testing. 

DICV Aftermarket Meeting

Regarding the Password Reset issue in the OES tool, checked the feasibility of providing an alternation option for password reset by looking into the table fields in the license portal database to manipulate the password hashing.

Discussion with the DICV team on revising the open points target dates.

Reviewed an updated open points spreadsheet document to Vikram (DICV) with the target dates, FB Tickets & Mahle Comments. 

Review the Mahle open points spreadsheet that was received from DICV and update the sheet with responsibility, FB tickets, and comments.

Mahle After sales - Clarity on Open points

Mahle After sales - Clarity on Open points:DTC Status ModificationCAN Log Storing in Local MachinePassword Reset - option in RuntimeBS 3 INS ParameterizationOffline Flashing in Run-timeLicense Portal Open Points 

DICV Open points discussion on Aftersales and EOL points

Creation of auto job service to execute on a daily basis to check and migrate the EOL VIN to the Aftersales DB server after completion of all VINs manually.

Prepare DB Migration report and share it with DICV

Production EOL VIN Migration - Updated all BSIV records with the ECU Part Number and Project type which are blank as per instruction by Barani & Jey Ganesh

EOL VIN Migration - Continued the VIN Migration Activity in Production by coordinating with the DICV team (Bharani & Jey) and completed all 68452 VINs as on this date. 

VIN Migration Activity in Production by coordinating with the DICV team (Bharani & Jey) - 2826 VINs moved.

Modification In the VIN Migration script because of 3 DB Servers are referenced (2 DB Servers in case of development)

VIN Migration Activity In Production - captured the record counts in EOL Activity table and Aftersales Factory table to know it before commencing the migration activity.

1. Discussed with Jey Ganesh on the last communication had for the development migration activity.2. Discussed with Vikram and clarified his doubts about the Migration process and the importance to have one resource support for the same. 

BS3 Vehicle DCM Mismatch - Cross-functional team meeting to analyze the issue in DCM flashing when two VINs are flashed without closing the Techpro tool.

BS3 Validation Analysis Meeting with DICV on wrong DCM flashing with two VINs if try flashing without closing the tool

Variant BSIII Label Mismatch technical discussion with Tushar and explained the concept of DCM + A2L and checked it by viewing the log files shared by DICV on Friday. We compared and reviewed the Aftersales Dataset Report PDF of OK VIN (Set 9) and NOT OK VIN (Set 11) files. Also compared those failing labels result with the EOL Dataset Report which is a validation passed file.  

Worked on FB 27184Analyzed how DCM & HEX files worked and what is the probable issue of BS3 Label value mismatch.Notified runtime issue to MSSNA to rectify on pririty

CDMT API - Removing Vehicle DCM file Check for BSIV & Deployment

3. Get Flashing Data from Retro-fitment DetailsHandling project type null scenario by fetching it from CDMT Database when it is not available in the Aftersales database and performing testing in the local system with data preparation.

1. Get Flashing Data from the Factory Data table2. Get Flashing Data from As Maintained Data tableHandling project type null scenario by fetching it from CDMT Database when it is not available in the Aftersales database and performed testing with the local system by creating dataset release.

Missing project type TitanWave1 in CDMT JSON which causes in back documentation and checking the code feasibility to handle it from the release mechanism.   

TitanWave1 Back Documentation Issue:Coordinated with Tushar in checking VAT for the functions that use the state for the string parameter using for Project type Titan with the comparison of other project types - BS3, BS4, BS6.

VIN Migration from EOL To Aftersales Factory table from the year 2012-2018. And verified again all the records if any VIN has been left over from the year 2012-2023 till July.

Fixing Back documentation issue with CALID updating blank in Aftersales DB.

Aftersales Development Database:Aftersales Factory VIN Migration from EOL Final VIN data in Activities log table through a script running it manually in Dev Server from date range 2018 - 2023 till date along with DICV team - Barani & Jeyganesh. 

worked of FB265212707327072

Coordinated with DICV (Mr.Barani) on the latest VAT Bin uploaded in the Mahle cloud. Downloaded and uploaded the latest VAT Bin shared by Tushar and GTS Exe file to the MSSI cloud server as a temporary measure as there is an issue in loading the files in the Mahle Cloud link provided with DICV. Checking the blank page with DICV login.

In both Dev & Prod CDMT Server, Updating the script file to fetch the Factory VIN list that is not available in Aftersales based on the start date and end date specifying the URL for easy range selection, and checking it.

FB27073 - INS ABS Enable/Disable Back Documentation Fix in Replacement Screen.Remark: It is working fine but observed that the Fuel Tank characteristics of 160L for BS4 do not seem to be updated in VAR_PART_NO_9 because the DID and its Data for this part number (160L) seem not been released in CDMT.

API Changes:Remove leading extra space in ESN for the Get Flashing and Back documentation in following scenarios:1. Get Normal Factory Flashing Data2. Get Normal AS Maintained Flashing Data3. Get Retro Flashing Data4. Push Flashing Data5. Push Retro Flashing Data 

Validation & Debug Session with DICV - Aftersales - INS Param Validation for Back Documentation

Validation of the migration script for the processed VIN from the Bosch tool to the Factory table in AS DB in the local system

To develop a script for the Migration of processed VIN from the Bosch tool to the Factory table in AS DB