Project

General

Profile

Production Ticket(ST) #8788

Yakult customer import request

Added by Muhammed Assyafiq Bin Ahmad Kamal over 1 year ago. Updated over 1 year ago.

Status:
Ticket Resolved
Priority:
P5 - Feature Request
Start date:
14/03/2023
Due date:
17/03/2023
% Done:

100%

Estimated time:
Job Remark:
Ticket Logged Date:
14/03/2023
Ticket No.:
Related Ticket ID:
Type:
SLA Initial Response:
SLA Delivery:
Esclation Time:
Issue Reoccurance#:
Actual Initial Response:
Resolution:

This ticket is closed as client has provide new requirements that will handle separatedly.

Requester ExpectedDeliveryDate:
Delay Justification:
Priority Seq:
Effort (Hour):
External Ticket #:

None


SALESMAN ROUTE LIST.xlsx (23.8 KB) SALESMAN ROUTE LIST.xlsx Muhammed Assyafiq Bin Ahmad Kamal, 14/03/2023 09:40 AM
ACTIVE OUTLETS.xlsx (4.32 MB) ACTIVE OUTLETS.xlsx Muhammed Assyafiq Bin Ahmad Kamal, 14/03/2023 09:40 AM
Customer_Import_Yakult.xlsx (2.29 MB) Customer_Import_Yakult.xlsx Muhammed Assyafiq Bin Ahmad Kamal, 14/03/2023 11:55 AM
Datanory_User_List_Template.xlsx (10.4 KB) Datanory_User_List_Template.xlsx Muhammed Assyafiq Bin Ahmad Kamal, 14/03/2023 11:56 AM

History

#1 Updated by Muhammed Assyafiq Bin Ahmad Kamal over 1 year ago

  • Status changed from Assigned To to Support In Progress

#2 Updated by Muhammed Assyafiq Bin Ahmad Kamal over 1 year ago

Hi @Muhamad Kamal Arif,

We have prepped the data and noticed that we’ll further information from client. Attached is the file and highlighted columns is the missing information. For better understanding, I’ll list down as below :

1. Branch code (yellowed column)

 As checked from the file provided, it does not indicate the customer is tied to which branch. Hence, will need to get advice from customer if they already have an existing branch for the setup and filled up accordingly. If Yakult did not really have a branch, please advice if could setup all under 1 default branch.

2. Person in charge (yellowed column)

 From the provided file, we have done mapping the route ID with the salesman route list. For your information, we noticed that Yakult provide a list of 275 salesman. Further, we noticed that it successfully mapped for SS salesman and for HD,PR the route ID was not tied to any outlet in the Active Outlet file.
 Please note that this person in charge is tied to Datanory users. As understand from @Jann Yap from previous email, Yakult only subscribe for 5 users. However, we also been told that Yakult will subscribe 150 users. Hence, kindly confirm the total number of users that we shall create in Datanory.
 For Datanory new user creation, please refer to attached for the template (Datanory_User_List_Template.xlsx). Do note that the column with * is compulsory.
 Once the total number of users been finalised, it must be mapped to the outlet list. Hence, will need to get advice from Yakult for the person in charge of and assign the users to the outlet accordingly.

3. Outlet area code, address, state code and post code (yellowed column)

 From the provided file, we noticed that the outlet list did not contain the outlet address. Hence, will need to get advice from Yakult for the outlet address.
 Please note that the area code, state code and post code will depend on the address. Hence, once we obtain the outlet address, we could help customer to fill the column accordingly.

4. Chain, channel, and cluster code (greyed column)

 For your information, chain code we refer to BPGroup column from Active Outlet file. For the blank value, we update as UNGROUP.
 For your information, channel code we refer to chain code column. Other than UNGROUP is update as GKA, and UNGROUP is update as GT
 For your information, cluster code we refer to Category column from Active Outlet file. We follow exactly.

To update on the progress, we will start working on SKU import today.

Thank you,
Regards,

#3 Updated by Muhammed Assyafiq Bin Ahmad Kamal over 1 year ago

  • Due date changed from 15/03/2023 to 17/03/2023

#4 Updated by Muhammed Assyafiq Bin Ahmad Kamal over 1 year ago

  • Status changed from Pending Client Feedback to Ticket Resolved
  • % Done changed from 50 to 100
  • Resolution updated (diff)

Also available in: Atom PDF