Skip to main content

Open Issues/Improvements in CMD

  1. Add two additional columns to the customer_information table to track the validity of addresses. One column will indicate whether the address is valid (valid_address), and the other will provide an address_score. This enhancement will contribute to improving address quality.
  2. Implement the capability to selectively publish codes.
  3. Introduce metrics to monitor publish events.
  4. Enable code publishing based on the source system.
  5. Enrich customer data and attributes during active integration with BVD.
  6. Develop an approach for integrating M&A data and applications with CMD, excluding TAMR.
  7. Enhance and complete the Confluence documentation for the entire CMD application functionality.
  8. Correct inaccuracies in the data related to Customer-Contact relationships, concern groups, and more.
  9. Establish a Business Partner model.
  10. Create a comprehensive Customer 360 view.
  11. Generate statistical reports on: a. The number of customers, contacts, concerns, and facilities created or updated daily and monthly. b. The number of customers currently in the approval process. c. The number of customers that have been approved or rejected.
  12. Implement BBU functionality for creating scenarios.
  13. Develop a centralized data model for all types of facilities, including customer, operational, commercial, and site master.
  14. Suggest the best approach for new consumers to integrate with CMD via the EMP channel: a. Consume data from the day they go live. b. Consume data from the last three days. c. Consume a complete snapshot of data.
  15. Restore the following foreign key (FK) constraints and adjust the code accordingly:
  16. CUSTOMER_WF_PROCESS_DETAILS between CUSTOMER_WF_PROCESS_DETAILS and CUSTOMER_INFORMATION.
  17. CUSTOMER_INFORMATION between CUSTOMER_INFORMATION and ref_invoice_iso_languages.
  18. How can I edit or add details for a suspended customer?

The modern portal restricts editing of suspended customer data if any mandatory information is missing or if there is incorrect data, such as an invalid tax reference. The temporary solution is to submit a BBU request to edit or add the necessary fields for the suspended customer. Once the data is updated through BBU, the customer will be eligible for reactivation on the CMD portal.

  1. What should I do if a city name is not available in the city drop-down list?

In the modern CMD portal, the city list is directly linked to the cities listed in SMDS GEO. If a city name is missing, please submit a SNOW request for the city to be created in GEO. Once this request is approved and the city is added to GEO, you will be able to create customers for the newly added city. Users will be requested to create the GEO ticket; in the meantime, should the customer request be left pending or rejected to avoid having it pending for more than 24 hours?

  1. How do I edit or add details for an inactive contact?

The modern portal does not allow the reactivation of an inactive contact if any mandatory information is missing, such as an email ID. The temporary solution is to submit a BBU request to edit or add the required fields for the inactive contact. Once the data is updated via BBU, the contact will then be available for reactivation on the CMD portal. As previously mentioned, users will be instructed to open a SNOW SMDS/CMD ticket to update details in the backend before reactivating the contact. (Although these cases are less frequent, they are urgent when they arise.)

  1. Why am I unable to reactivate an inactive contact?

If an inactive contact lacks mandatory information, such as an email ID, you will not be able to edit or reactivate the contact from the CMD portal. The temporary solution is to submit a BBU request to edit or add the necessary fields for the inactive contact. Once the data is updated via BBU according to CMD rules, the contact will then be available for reactivation on the CMD portal. Similar to the previous cases, users will be instructed to open a SNOW SMDS/CMD ticket to update details in the backend before reactivating the contact. (Although these cases are less frequent, they are urgent when they arise.)

Was this page helpful?