PowerPoint Presentation

[Audio] Master Data Governance for Suppliers (MDG-S) Understanding MDG-S and Approval Flows Key Performance Indicators and Data Quality Reports Enhancements and Collaboration with Global Master Data Team.

[Audio] Section 1 Master data governance SAP MDG.

[Audio] What is sap mDG Introduction: Application within SAP for high-quality supplier data. SAP MDG or SAP Master Data Governance (MDG) is a vital component of the SAP NetWeaver platform, designed to manage master data across diverse systems. Master Data is the single source of information used by the business. It supports key business processes and transactions: A blue and white background with a face and text Key Features A diagram of a cloud computing system SaplingHR | Workday Integration See related image detail. SAP SRM Review: Pricing, Pros, Cons & Features | CompareCamp.com SAP Concur partners with MicroChannel in first reseller agreement for ... Salesforce Certified Developers and Implementation Partners Le sommet sur le fonds de roulement de Taulia arrive à Johannesburg ... Centralized System System Integration Business Process Integration SAP MDG serves as a centralized governance system for master data. It manages data across SAP and non-SAP systems. Master data is integral to various business processes..

[Audio] Value of Data Governance MANAGE YOUR DATA THE WAY YOU MANAGE YOUR COMPANY The goal of Data Governance is to ensure an accurate, current, complete, and relevant single source of master data to support business processes and transactions. Company Assets Data is a Valuable Asset. Data Governance lets you realize its full potential A black building with columns Description automatically generated A black rectangle with white dots A black and white symbol of a hammer and wrench Description automatically generated A black and white image of a check mark Governance & Policies Processes & Workflows Tools Standards & best practices THIS INCLUDES Data Governance addresses data challenges by establishing a unified view of master data to facilitate efficient decision-making and business processes. The BENEFITS OF DATA GOVERNANCE INCLUDE Silos of Critical Information Lack of Consensus on Source Data Compliance Issues Bad Decisions Due to Bad Data Cost of Poor Data Quality (COPDQ) Loss of Revenue Common Data Issues Quality, Speed & Availability Data is replicated with little to no governance processes to manage information.

[Audio] Section 2 Approval process Roles & Responsibilities.

[Audio] vendor data management (callback process).

[Audio] MDG S Change request: Approval Flow Process Signed Current Tax form: US: W9 Form (For USA only) Canada: Document that includes HST/GST number (For Canada Only) International Vendor: W8 if applicable Banking information in one of the following formats: Voided Check On company letterhead with a signature from an official of that company Provide an email address that will receive payment remittance advice. Sample Invoice or RFQ (Request for Quote) or Contract if the company is a DBA to ensure we pay according to the way we will be billed. Signed Contract with Bacardi entity and from Global Procurement (If applicable only). MDG CR WORKFLOW Automated Interface to different platforms.

[Audio] Section 3 Key Performance Indicators and Data Quality Reports.

[Audio] Current kpi – vendor mdg change requests & sysaid tickets (Maintenance & incident tickets) Link to: Global Data Services SLA and Ticket Priorities Link to PowerBI Dashboard: Vendor MDG Dashboard (powerbi.com) 3rd Level Categories Valid MR Remarks Data Extract Data Extract / Reports Ex. Requesting for a data for a specific list of vendors or company codes. Mass Requests Mass update/blocking 30 records and up Data Loading Mass Creation System System update - Push data from PM0/P00 to other system Ex. PM0 to QM0/Q00 to be used for testing Data Operation Bank Key Creation Do not process bank key changes, swift code update and ticket can be cancelled. All bank keys related should be managed by treasury team through swift load Mass Requests Monthly Swift Load New bank key and bank key changes are done on this load Data Operation Data correction during project migration Ex. SAP RISE, SAP Upgrade etc.. Data Operation Temporary blocking/unblocking of employee vendor vendors which start with 5 series Fast Track Request with Fast Track category Process only fi with Regional Director approval ( Change category if no approval attached ) Request information Request information for a specific vendor Ex. Asking for details of the changes done on this vendor Data Operation CR Deletion Warning for deletion tickets Mass Requests Approval Matrix Related Specific for Procurement approval matrix Data Operation Removal of FFD in company code or Purchasing org level Do not process removal of FFD on central level if all company code and purchasing org extended to the vendor are blocked. They need to request unblocking in MDG S as this will automatically remove the FFD on central level Incident IDOC Monitoring Do not process via back end if After investigation an MDG S ticket can be raise to resolve the issue, then seek assistance from the user Timeliness Vs Agreed SLA Ave. Processing Time or Lapse Days per Role Per Type of Request and Category (including Fast Track/ Mass Uploads type of request) Valid and Invalid Request SLA Breakdown: With Bank and without Bank Changes SLA Trend per Region Invalid and Valid Tickets SLA Trend: Illustrates the on-time performance for indirect, direct, and customer SLAs, with overall compliance rates dropping when bank changes are involved. Aging Ave Trend: Shows average aging times for indirect, direct, and customer categories, indicating that aging times generally increase with bank changes. SLA Compliance Split: Breaks down SLA compliance by request type, highlighting that certain types of requests, such as "Change Vendor," have lower on-time percentages when associated with bank changes. Aging Split (In Days): Details the average processing time by different stages (PSO, procurement, finance, master data, requestor sent back aging) for requests, with and without bank changes, suggesting that bank changes lead to increased processing times in several categories. Overall, the dashboard reveals that bank changes significantly impact SLA compliance and processing times, with a notable decrease in on-time performance and an increase in aging times when bank changes are present. The dashboard allows for identifying areas for improvement and strengths in the process. Vendor SysAid Tickets SLA Results The dashboard collectively assesses the service level achievements, indicating areas of strength and opportunities for improvement in ticket handling and SLA fulfillment across different regions and categories. SLA Rate Results: A gauge chart showing that 91% of the SLA targets were met, slightly below the goal of 95%. Total Tickets by Ticket Type: A pie chart indicates that the majority of tickets are of type "MR," with "INC User" tickets.

[Audio] Dashboard for vendor data –sysaid Split of Tickets: Incident and Maintenance Monthly Trend Regional Volume & Lapse Days SLA/ Volume and Lapse Days per Category Valid and Invalid Ticket Count Total Closed in Time over Total Processed The "MDG Dashboard" provides an overview of Service Level Agreement (SLA) compliance across various metrics, differentiated by whether there are bank changes involved or not. Key aspects of the dashboard include: SLA Trend: Illustrates the on-time performance for indirect, direct, and customer SLAs, with overall compliance rates dropping when bank changes are involved. Aging Ave Trend: Shows average aging times for indirect, direct, and customer categories, indicating that aging times generally increase with bank changes. SLA Compliance Split: Breaks down SLA compliance by request type, highlighting that certain types of requests, such as "Change Vendor," have lower on-time percentages when associated with bank changes. Aging Split (In Days): Details the average processing time by different stages (PSO, procurement, finance, master data, requestor sent back aging) for requests, with and without bank changes, suggesting that bank changes lead to increased processing times in several categories. Overall, the dashboard reveals that bank changes have a significant impact on SLA compliance and processing times, with a notable decrease in on-time performance and an increase in aging times when bank changes are present. The dashboard allows for the identification of areas for improvement and strengths in the process. Vendor SysAid Tickets SLA Results provides a snapshot of service performance for the year 2024, focusing on the month of May. Key elements include: SLA Rate Results: A gauge chart showing that 91% of the SLA targets were met, slightly below the goal of 95%. Total Tickets by Ticket Type: A pie chart indicates that the majority of tickets are of type "MR," with "INC User" tickets making up a smaller fraction. Total of Tickets Created by Status: A bar chart compares the number of tickets that are "Closed - Verified (auto)" versus "Closed - Cancelled," with a total count provided. SLA Met by Month: A line chart depicts the fluctuation in SLA compliance over five months, with a high of 99% in January and a low of 88% in March. Vol Lapse and SLA by Category: A table provides detailed percentages of SLA met and corresponding volume lapse days for categories such as "Data Operations" and "Data Extracts." Total Tickets and SLA Met by Country and Requestor's Region: A global map highlights the distribution of tickets and SLA performance across different regions. Total Tickets, Ave Lapsed Days, and SLA Met by Ticket by Region/Team: A table with bars and lines shows a breakdown of total tickets, average lapsed days, and SLA compliance by region or team, indicating variations in performance. The dashboard collectively assesses the service level achievements, indicating areas of strength and opportunities for improvement in ticket handling and SLA fulfillment across different regions and categories..

[Audio] Vendor SysAid Ticket Categories 3rd Level Categories Valid MR Remarks Data Extract Data Extract / Reports Ex. Requesting for a data for a specific list of vendors or company codes. Mass Requests Mass update/blocking 30 records and up Data Loading Mass Creation System System update - Push data from PM0/P00 to other system Ex. PM0 to QM0/Q00 to be used for testing Data Operation Bank Key Creation Do not process bank key changes, swift code update and ticket can be cancelled. All bank keys related should be managed by treasury team through swift load Mass Requests Monthly Swift Load New bank key and bank key changes are done on this load Data Operation Data correction during project migration Ex. SAP RISE, SAP Upgrade etc.. Data Operation Temporary blocking/unblocking of employee vendor vendors which start with 5 series Fast Track Request with Fast Track category Process only fi with Regional Director approval ( Change category if no approval attached ) Request information Request information for a specific vendor Ex. Asking for details of the changes done on this vendor Data Operation CR Deletion Warning for deletion tickets Mass Requests Approval Matrix Related Specific for Procurement approval matrix Data Operation Removal of FFD in company code or Purchasing org level Do not process removal of FFD on central level if all company code and purchasing org extended to the vendor are blocked. They need to request unblocking in MDG S as this will automatically remove the FFD on central level Incident IDOC Monitoring Do not process via back end if After investigation an MDG S ticket can be raise to resolve the issue, then seek assistance from the user Bank key creation – via ticket Bank change/ bank name change / swift code – close cancel the ticket no change should be done in the bank. Coordinate with Karen Fallas (Mngr Tech Service).

[Audio] Dashboard for vendor data –MDG. Dashboard for vendor data –MDG.

[Audio] DACORE - vendor 98% 99% Data as of 06/10/2024 Pending Business Rule revision For review For review DEI – Data Excellence Index | FTR- 1st Time Right.

[Audio] Section 4 Enhancement requests. [image]. Enhancement requests.

[Audio] New Enhancement Request Process Steps for Effective Collaboration: Initiate Early Engagement: Involve the Global Master Data team early. Define Clear Requirements: Gather and document detailed requirements. Regular Communication: Maintain communication through meetings and updates..

[Audio] .