Business Goal
ECCO is the customer organization organized by customer segmentation and market clusters.
Links & documents |
|---|
FAQ |
|---|
Reporting Region ECCO
| Expand | ||
|---|---|---|
| ||
It is available at the account level, on the children pages. It is |
HypercareHypercare period
Reference Documents
To be completed
Key roles
Sarah Chattin : GBU data Steward
Andrea Pappada : CRM champion
FAQ
New fields added impacting users and reports/Dashboards (more than 400 reports update by Sept 15th , much more by end September 2020) :
Reporting Region (SCME-2060) : in Account page layoutused to regroup sub-regions (still |
exists and updated by the GBU |
Team Cluster (SCME-2094 ): in Account page layout , mass update done with file provided by business (4 values : Transportation, Industrial, Consumer/ Healthcare/Environment , Channel partners ) . This field can be challenged only by Account owner at Child account level, when S.Chattin approves, new Team cluster value is automatically updated at Parent account level and then will update all child accounts. Then 1 case by region is generated for CSR can update in SAP . Data updates in Icare must be handled only by GBU data steward , not by SBS.
Data steward). This field was created to be used on reports. |
| Expand | ||
|---|---|---|
| ||
Values are (in November 2020): Great China, EMEA, Americas and APAC |
- if Team cluster = Channel partner ==> Market cluster = Channel partner
- else ==> mapping table defined in set up ( reference document in Library documents) based on End use .
Hypercare period
1- User request to have access to data related to new Visibilty ECCO organization ==> nothing will be available before end Septembre
2- High priority master dashboards have been delivered , a document will be built and shared with users to show in which folder new reports/dashboards are available with new fields . If need to support to build new additional reports ==> forward to Sarah Chattin
3- if user is asking why his customer is in a certain Market or team cluster , guide user to see File tab / "Library " tab (referential) , if user need more explanation we will forward to Andrea Pappada. |
Team cluster
| Expand | ||
|---|---|---|
| ||
It is available at the account level, on all pages (parents and children). |
| Expand | ||
|---|---|---|
| ||
On the account pages, Account owners can ask for a change by using the "Challenge team cluster" button. It triggers the approval process (refer to the related Q&A to learn more about this part). The field on the page layout only is editable for the Data steward and admin users. Please be careful because if someone edits the field (Sarah or us) on the page layout, the value is changed without approval process. |
| Expand | ||
|---|---|---|
| ||
The change request is sent to Sarah for approval. When she approves / rejects, the Account owner receives a notification to inform him/her. The Account owner will not be able to "Challenge Team cluster" before the first request has been approved/rejected. If she/he tries to click on the button again, a message will appear to indicate her/him that a request was already submitted. |
| Expand | ||
|---|---|---|
| ||
If the account owner asked for the change on the account A1 and Sarah approved, only A1 will be impacted (Team cluster updated). The parent (A) and children (A2, A3...) will not. Also, no case is generated for CSR at the moment because the SAP part is not ready for now. Please note that this wasn't the initial behaviour. When Team cluster was implemented, one change was impacting all accounts (parent + children) and a case was generated (one by region) for CSRs. The case part will maybe be reimplemented later. |
Market cluster
| Expand | ||
|---|---|---|
| ||
It is available on:
|
| Expand | ||
|---|---|---|
| ||
It depends on the "Team cluster" field which is available at the account level. When a new record is created (RS, S&P or devpool):
Please check the end use mapping on the setup part. If a user asks you why a specific Market cluster is used, guide her/him to the File tab > "Library " tab (referential). If she/he needs more explanations, ask her/him to refer to the CRM Champion or Data Steward. Same comment for Team cluster. |
| Expand | ||
|---|---|---|
| ||
Sold & Pending
*The records will be deleted during the night and replaced by new ones (with correct values). Business agreed to have the new "Market cluster" available within 24h. Realized Sales & Devpool
|
Security
| Expand | ||
|---|---|---|
| ||
The security part was reviewed as with the ECCO project, the organization changed to a regional focus:
|
SCME - To learn more
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
| Expand | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Initial logic:
New logic in October 2020:
Check the linked issues + search "Team cluster" to find all other Jira related to this field. |
| Expand | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
Check the linked issues + search "Market cluster" to find all other Jira related to this field. |
End Use
| Expand | ||
|---|---|---|
| ||