DESKTOP PROCESS FOR CONSUMER ST CLAIMS

Input Data Matrix

The list below provides details of input required To Prepare Consumer ST DSR For Claims Submission:

SL No	Required Inputs	Received From	Date	Purpose
1	CSD CONS ST DSR	Download from OWB Tool https://owb.lenovo.com/resaletracking	On 8th day of every month for the previous months of the same QTR.(Consider after clearing all the exceptions or manual upload)	Data used for claims submission
2	Consumer T2 Rebate List	Consumer BPRM Team	After the closure of the previous month. Before 2nd of current month.	To Map the MDM IDs T2 Rebated Partners This is done to identify any differences in MDM IDs mapped in Master FIle & Rebate List
3	Channel BP Code Mapping	Download from CoData	After the closure of the previous month. Before 2nd of current month.	To map LPP codes that are not listed in T2 Rebate List
4	Issue Tracker	Wyzmindz (Internal Tracker)	9th of every month	To check if all the issues received from Sales or Ops team are addressed and resolved.
5	India BP Type Maintenance file	Download from OWB Tool https://owb.lenovo.com/dataMaintenance/indiaTerritoryMapping	9th of every month	To Check if the mapping done in DSR is matching with Master file

Consumer CSD ST DSR Preparation & Validation:

Step 1 : Download CONS CSD ST DSR from OWB

https://owb.lenovo.com/resaletracking

• Once we click the above link we will ge the page as shown in the below snap shot.

• Click on ST and Select Fiscal year, Quarter, Invoice Date, Geo Segment, Geo Sub Segemnt and Status.

  • If Fiscal Year is FY2526 and Quarter is Q3 then select the Month using Invoice Date(we should select the whole Month for Ex.. 01st of Oct to 31st of Oct if we are preparing a DSR for M1 for M2 it should be 1st of Oct to 30th Nov, for M3 it should be 1st Oct to 31st Dec)
  • Geo Segment as CON
  • Geo Sub Segment as CS
  • Status as “Released and Soft Error”

• Once we select all the filter as explained in above, click on Search and wait for a while to get the data, after that click on Export (if the data is less then 10k line items we can export as an Excel sheet, if the data is more than 10k line items we get a link via mail and we need to click the link so that the data get downloaded externally)

Step 2: Consider “CONS ST DSR” Download from OWB Tool

Step 3: Validate No Qty using Daily DSR Vs OWB DSR

a. Concat Invoice No and Product No/MTM in both the DSR to check the Qty based on transaction level

b. After selecting data as explained in the above step we should get a “0” Qty diffrernce, if there are any variences connect with Ops team and take Approval/

Process For Data Consolidation: - Not Required

Consumer ST Claims DSR Preparation:

The DSR will be automatically transafered to Megallen for claims considereation once we clean, Map all the required data in CSD/OWB

Step 1: Consider CONS CSD ST DSR which has been downloaded and Validated as mentioned in the previous steps.

Step 2: Consider the T2 Rebate Master file received from BPRM Team to check if the MDM IDs and vertical are mapped in CSD ST DSR. (Note we need to check basis the L3 MDM ID)

📊 Consumer ST Claims Desktop Process V1 (2).xlsx (Excel)

Attached the file of T2 Rebate.

Cross Check the L3 MDM IDs in rebate list matches with the Channel BP Code file downloaded from CoData.

a. There will be 8 BP Categories “Shown in the below snap shot” if T2 partner name is not available in T2 Rebate master then the partner Bp Classification will be tagged as “T3_Reseller”

b. L3 MDM ID will be mapped as per “State & Pan India Level” refer below table on basis of BP category

BP Category	Mapping Level
LFR	Pan India
ONLINE
E-COMMERCE
RD	State
S&P RD
LES
LMB

c. Map all the L3 MDM ID for T2 partner available in T2 Rebate master based on Name & as explained in step b. (Please Note tagging will be automatically picked in CSD basis the Master file(India BP Type Maintenance file), in master file L3 MDM ID will be tagged basis the Buyer details(Buyer Tax ID, Cust Code, City) reported by T1 Partner)

d. If Partner is not a rebated partner the we need to update the Buyer India BP Type as “T3” and Keep Buyer L3 MDM ID Blank

Step 5: Updating MDM & othere Colums Related to MDM.

a. L3 MDMs will be available in the rebate list shared for T2 and same will be updated in India BP Type Maintenance file as well.

b. There are 3 More Columns which are related to MDM “Buyer BP Type”, “Buyer BP Sub Type” & “Buyer BP Classification” for T2.

c. Buyer BP Type will be picked Automatically based on the MDM IDs updated in the DSR/Master file.

d. Buyer BP Type which is automatically mapped from backend should be “TRT2” if there are any other values then please check the MDM ID mapped in the DSR and change it.

e. Please refer below table to update Buyer BP Sub Type and Buyer BP Classification

BP Cat	BP_Sub_Type	D365
RD/Visual RD	Regional_Distributor
S&P RD	Regional_Distributor	AP S&P Partners
Online/E.Com	etailer	AP eCommerce
LFR	Storefront	AP Large Format Retailer
LMB	Storefront	AP Large Multi Brand
LES	Storefront	AP Lenovo Exclusive Store
OTP(Blank)	T3_Retailer

Validation Process

SL No.	Headers as displayed in Claims DSR(In Same Sequence)	Logic/Data Mapping - Description for populating respective headers	Mandatory Field to check	Validation Points
1	L3 MDM ID Buyer	1. For Rebated Partners - MDM Code has to be based on Rebate List and as per respective vertical. 2. For Non Rebated partner: MDM ID Can be Blank	Yes	1. Blanks Can be There. 2. Partner Name,vertical has to match with MDM ID based on the rebate list shared. 3. MDM ID Has to be Mapped based on the defined logic
2	INDIA RTM	1. Tagging as per Rebate List for all rebated partners 2. For OTP or Non rebated Partner Leave it Blank 3. For RD, Visual RD, S&P RD, LES & LMB - Vertical Tagging is based on State 4 Should map the India RTM as RD for Visuals RD Partners 5. For LFR/Online/E-Comm - Tagging is Pan India Level	Yes	1. Valid Category are RD, S&P RD, LES, LMB, LFR, E-Commerce & Online 2. Blanks Can be there 3. Cross validate against rebate list for Partner Name & Vertical tagging under Consumer Segment
3	Buyer L3 MDM name	Check if the Buyer L3 MDM Name are aligned with Buyer name Reported and MDM ID updated	Yes	1. No Blank 2. Cross validate against rebate list for Partner Name tagging under Consumer Segment
4	CITY	1. As per Disty shared	Yes	1. No Blanks
5	STATE	Mapping is based on Consumer Segment Territory mapping file	Yes	1. No Blanks
6	Territory	Mapping is based on Consumer Segment Territory Mapping file	Yes	1. No Blanks
7	Sub Territory	Mapping is based on Consumer Segment Territory Mapping file	Yes	1. No Blanks
8	MTM	As per Disty reporting	Yes	characters has to be 10 digits, less than or greater than that cross validate once
9	Buyer BP Type	Picked Automaticaly in CSD based on the MDM ID updated	Yes	Everthing should be mapped as TRT2
10	Buyer BP Classification	Logic should be as per below Table	Yes	Blanks Can be there
11	Buyer BP Sub Type	Logic should be as per below Table	Yes	Blanks Can be there
12	Status	Check Status of the file reuploaded again after 1 or 2 days if the status has been changed from released or Soft error to Error	Yes	Blanks Can be there

New BP Category	T2_BP_Type	T2_BP_Sub_Type	T2_D365
LFR	T2 Retailer	Storefront	AP Large Format Retailer
RD	T2 Retailer	Regional_Distributor
ONLINE	T2 Retailer	etailer	AP eCommerce
LES	T2 Retailer	Storefront	AP Lenovo Exclusive Store
E-COMMERCE	T2 Retailer	etailer	AP eCommerce
LMB	T2 Retailer	Storefront	AP Large Multi Brand
VISUALS RD	T2 Retailer	Regional_Distributor
S&P RD	T2 Retailer	Regional_Distributor	AP S&P Partners

Process For Approval & Upload

• Once the DSRs are prepared for Claims submission, the DSR is validated at WyzMindz end and shared with the Lenovo Ops Heads for Approval.
• After the approval from Ops Head is shared, the DSR is validated for one last round for standard columns like Qty, Buyer Details like “MDM ID, Buyer BP Type, Sub Type and BP Classification
• After the final Check we will give a confirmation to claims team marking AP team on Claims DSR rediness in CSD, below snapshot of the mail confrimation given to claims team