Professional Documents
Culture Documents
SOP Particulars:
Prepared By:
Name Designation Department Signature Date
Senior Officer
Sylvia Sultana Supply Chain
Distribution
Checked/Reviewed By:
Name Designation Department Signature Date
Asst. Manager
Ashraful Alam Raju Supply Chain
Distribution
Senior Executive
Md. Rafiqul Ahsan Supply Chain
Distribution
Approved by:
Name Designation Department Signature Date
Md. Rofiqul Alam Director Supply Chain Supply Chain
Distribution List:
Role Role
Managing Director
1. Purpose
Standard Operating Procedure
This SOP is prepared to ensure that proper process is in place for creation, modification, updating and
auditing of Customer Master Data in SAP and ensure proper maintenance of customer tagging in
eSET (Electronic Sales Effectiveness Tool).
2. Scope
This SOP is applicable in managing customer master database for all Sales Centers (SC) and
Distribution Head Office (DHO). Following processes are covered by this SOP:
2.4. Tagging and mapping customer data in eSET with respective BUs and its territories
3. Definition
3.1 Customer Master Data: The master database in SAP containing all necessary information of a
customer for conducting business transactions.
2.1. Customer Master Data Audit: A systematic and independent examination of customer records
for accuracy, completeness, status and performance (financial or otherwise) in a periodic
interval.
4. Archival Period
Master copy of this SOP has to be archived at DHO for six years with acknowledgement record sheet.
After the date of expiry, one original copy of this SOP has to be preserved.
5. Responsibility
6. Procedure
6.1. Creation:
6.1.1. MIA will initiate customer creation by filling Customer Enlistment Request Form (CERF)
with all required information (Annexure-I: Customer Enlistment Request Form).
6.1.2. MIA will ensure that the following information are clearly mentioned in CERF at minimum:
Customer Trade Name (full name including abbreviation, if any)
Full Address (Traceable detail information including Street, Location, Upazilla /
Thana / District and Postal Code)
Business Phone Number
Name of Owner / Proprietor / Director or Authorized Person
Owner / Proprietor / Director or Authorized Person’s mobile number
Drug License and / or Trade License Number
6.1.3. MIA will attach all relevant supporting documents (Trade License, Drugs License,
Registration Certificate or Enlistment Request Letter in Official Pad) with CERF and
submit to immediate supervisor (ASE / ASM).
6.1.4. MIA will ensure authenticity of all submitted supporting documents with CERF for new
Customer ID creation. Relevant supporting documents may differ from customer to
customer based on different Customer Category as mentioned below:
Retail Pharmacy
1 Wholesale Pharmacy Drug License
Distributor
Clinic
Diagnostics Retail
2 Trade License
Diagnostics Center
Vaccination Center
Dispensing Doctor
Vaccination Doctor
Pvt. Hospital
Pub. Hospital Letter of Intent from Proprietor /
3
Pvt. Institution appropriate Authority in official pad
Pub. Institution
Int. Institution
NGO
Counter Customer
6 Sales Center No document required
Direct to Patient
6.1.5. Any CERF containing fake / duplicate / tampered documents will be immediately rejected
by ASM / RSM.
6.1.6. ASE / ASM / RSM will check the information and give recommendation for enlistment with
company.
6.1.7. One customer can have only one enlistment i.e. one customer ID on company’s system
for doing business. If one customer has physical establishment in multiple places then,
more than one ID can be created in system as per below process:
2 ‘Goods receiving’ is done at one One ‘Bill to party’ + One ‘Ship to Party’
location and ‘Bill payment’ is done from
separate location.
6.1.8. ADM will check and ensure that all required supporting documents are submitted along
with CERF (e.g. Drug License, Trade License etc.) by MIA.
6.1.9. ADM will further check the genuineness of supporting documents and will reject if any
fake / duplicate / tampered documents are submitted.
6.1.10. CSO will check by wild search (asterisk*) using “Name” and “Address” field in SAP and
will confirm ADM that the customer is not enlisted earlier to avoid duplicate ID creation.
6.1.11. After checking and validating all written information provided in the CERF, ADM will
approve and handover the CERF to CSO.
6.1.12. CSO will immediately fill-up the standard XL template (Annexure-II: XL Data Set for
Customer ID Creation in SAP) for new Customer ID creation as per the approved CERF.
6.1.14. CSO will preserve approved CERF with all supporting documents at SC (as per the ID
sequence) in designated file.
6.1.15. CSO will send Customer ID Creation request once in a day to DHO. After getting
approved CERF from ADM up to 12:00 PM, CSO will send the request in XL Data Set
within same day by 3:00 PM. CSO will send the Customer Creation Request in the next
day if approved CERF is received after 12:00 PM.
6.1.16. After receiving the XL template DO will cross check and validate XL file by wild search in
SAP by using “Name” and “Address” field to ensure that no duplicate ID exists against the
Customer.
6.1.17. For all request received from Sales Centers up to 3:00 PM, DO will create the Customer
IDs within same day by 5:00 PM.
6.1.18. DO will link Territory Code in eSET and will send the request to IS by e-mail for updating
in mOrder immediately (before 5:30 PM).
6.1.19. DO will communicate the new Customer ID to SC by e-mail on the same working day of
creation.
6.2. Modification:
6.2.1. For any change in Customer Master Data (e.g. Name, Address, Upazilla, District, Postal
Code, Shipping Point, Shipping Condition, Industry, MIA Name, Territory Code etc.) both
in SAP and eSET, MIA will communicate with ADM by email with reason for change /
modification.
6.2.2. MIA will submit necessary supporting documents for any change / modification request.
depending on the change request type as given below:
6.2.3. ADM will verify the change requested taking help of Delivery Assistants or by directly
communicating with customer.
6.2.4. After verification if the change request is found valid, ADM will send such change request
to DO by email for bringing the change in SAP and eSET copying Asst. Manager
Distribution.
6.2.5. Asst. Manager Distribution will review and approve such change request. If the change
request is major (e.g. complete change of name) then it has to be approved by DSC.
6.2.6. After approval, DO will do the change in SAP on the same day of receiving such request.
6.2.7. ADM will check and confirm that the change has been done in SAP as requested.
6.2.8. For any change / modification request processing, procedures mentioned in Clause 6.1.4
- 6.1.14 has to be followed (as applicable).
6.2.9. For any change of MIA Name or Territory Code tagging in SAP and eSET, DO will inform
IS to update other systems accordingly.
6.3.1. Blocking:
I. At the time of Customer ID creation, if CSO identifies any duplicate Customer ID through
wild search in SAP, CSO will immediately inform DO by email to block the duplicate ID.
II. For any type of request for blocking / unblocking of Customer ID, CSO will communicate
to DO by email, copying ADM, Asst. Manager, Distribution and SAP SD Power User.
III. CSO will mention the reason for blocking / unblocking in detail.
IV. If DO finds any duplicate Customer ID while creating Customer ID through wild search in
SAP, DO will immediately block the duplicate Customer ID and inform CSO and ADM
through email.
V. As part of the yearly audit process, if DO identifies any fake / duplicate Customer ID, DO
will block the duplicate Customer ID and inform CSO and ADM of the respective SC
through email.
VI. Asst. Manager, Distribution will inform DO if any disputed outstanding is reported against
a customer. DO will immediately block the Customer ID and inform CSO / ADM through
email.
VII. After identification of any duplicate Customer ID, DO will include the Customer ID of the
duplicate one in the name field of the original Customer ID. An illustration is given below:
6.3.2. Unblocking:
I. ADM will send request to unblock a Customer ID if a customer whose ID was blocked for
disputed outstanding has paid / cleared-off the dues.
II. ADM will also send request to unblock if any customer whose ID was blocked for no
business for long time and wants to resume business transaction.
III. DO will take approval from Assistant Manager, Distribution to confirm that the customer’s
dues have been paid off.
IV. After receiving unblocking request, DO will check the particular ID in the Duplicate ID list
maintained at DHO and will ask for further clarification from CSO, if required.
6.4.1. DHO team will audit the full Customer Master data once in a year and DO will lead the
audit program.
6.4.2. Audit team will check the following items while conducting audit:
Sl. Items for Checking Remarks
Nomenclature Pattern and Format
1 Customer Name
Names are understandable
Traceable and detail information including Street,
2 Address Location, Upazilla / Thana, City / District and Postal
Code
6.4.3. Asst. Manager Distribution and SAP SD Power User will jointly review the audit results /
observations.
6.4.6. After completion of audit, DO will close all action plans in time and will ensure cross
checking of these action plans by Asst. Manager Distribution and SAP SD Power User.
6.4.7. Audit report has to be submitted to DSC for review and approval with proper
documentation.
Document History:
Major
Fields Example Comment
Group
Country BD Bangladesh
Region BD Bangladesh
Partner
Vendor 46258 Sales Colleague Customer ID
Information
2 BD02 Direct to Patient Products directly sold and delivered to end customers
3 BD03 Retail Pharmacy patients. These pharmacies may conduct retail sale to
customer but do not sale any loose strips or bottles.
4 BD04 Wholesale Pharmacy Pharmacy whose 80% sale is towards retail pharmacy
5 BD05 Dispensing Doctor Qualified (minimum MBBS) doctors who practice privately
13 BD13 Diagnostics Retail Any retail outlet doing business mainly of diagnostics items
rd
20 BD20 Distributor Authorized 3 party who distributes Sanofi products
21 BD21 Toll Other company who does toll business with Sanofi
23 BD23 Others Any category not included in the fields mentioned above
10 BA Others Others