SAP Master Data Governance: Centralize and Consolidate Supplier Master Data

See how SAP software can help you manage supplier master data more efficiently and effectively.

  • 7aba1db3-c3e7-4f6e-bce7-5e1d97f7ca4d
  • Match
    • GroupCollection Groups =
      • Match [Previously Displayed]
      • Group
        • bool Success = true
        • CaptureCollection Captures =
        • int Index = 21
        • int Length = 6
        • string Value = "demos/"
      • Group
        • bool Success = true
        • CaptureCollection Captures =
        • int Index = 27
        • int Length = 82
        • string Value = "sap-master-data-governance-centralize-and-consolidate-supplier-master-data-demo-us"
    • bool Success = true
    • CaptureCollection Captures =
    • int Index = 0
    • int Length = 114
    • string Value = "src=/demos/richmedia/demos/sap-master-data-governance-centralize-and-consolidate-supplier-master-data-demo-us.epx,"
  • http://global.sap.com/demos/mmov/demos/sap-master-data-governance-centralize-and-consolidate-supplier-master-data-demo-us.mp4
    • SAP Master Data Governance: Centralize and consolidate supplier master data.
    • This demonstration shows how SAP software allows you to: add a supplier to master data,
    • review supplier data change requests, approve change requests based on areas of responsibility, and verify master data changes
    • Enabling you to ensure the validity of supplier master data, facilitate master data changes with approval workflows,
    • and reduce costs associated with data management by streamlining maintenance processes.
    • Add a supplier to master data.
    • Tom Morgan is a master data administrator.
    • Tom opens his SAP software to add Panorama Services to the company’s master data as a supplier.
    • First he checks to see if the company is already listed as a supplier in the data.
    • He finds a supplier based in Chicago, but it’s not the correct one, so he creates a change request to add a new supplier.
    • He types in a description and enters the supplier’s address.
    • He also specifies the company as a vendor and assigns a company code.
    • These fields need to be completed so the supplier is recognized as a vendor in enterprise applications.
    • Tom could now maintain payment, accounting, or correspondence data for this company code,
    • but instead he focuses on the reconciliation account.
    • He selects the purchasing organization.
    • And he defines the currency and terms of payment before submitting the change request.
    • The software confirms the creation of the change request and routes it to the appropriate master data specialist for approval.
    • Review supplier data change requests.
    • Pete Miller is a master data specialist, responsible for central supplier data.
    • When Pete checks his worklist, he finds the change request from Tom, waiting to be approved.
    • After he has specified all the objects, he checks and approves the change request.
    • The request is now ready to be reviewed by the master data specialists responsible for approving changes to company-code data and purchasing-organization data.
    • Approve change requests based on areas of responsibility.
    • Sue Baker is a master data specialist responsible for reviewing company-code requests.
    • Sue checks the worklist and finds items ready to be processed.
    • Since she’s only responsible for company-code data, she’s not able to process purchasing-related requests.
    • Sue selects the work item for the change request from the worklist.
    • She adds payment terms then processes the change request.
    • Steve Thomson is master data specialist responsible for reviewing purchasing-organization requests.
    • Steve opens the change request so he can add purchasing-related data.
    • He enters the order currency and the terms of payment before submitting the changes.
    • Now that Sue and Steve have processed the change request, the software routes it for review by other master data specialists.
    • The software enables duplicate review of change requests to ensure the validity of master data changes.
    • Verify master data changes.
    • Chris Boyle is also a master data specialist for purchasing data and is responsible for approving the processed change requests from his colleagues.
    • From his worklist, Chris opens the work item to approve the new supplier purchasing data.
    • He checks the purchasing data and approves the change request.
    • Andrew Miller is a master data specialist for company code-related accounting data, and will also review the processed change requests.
    • He finds the work item to approve the company-code data.
    • He checks the accounting and payment data and approves it.
    • Since the change requests have been approved, the software updates Tom’s worklist.
    • He checks his requests and sees that the new supplier has been approved.
    • On the organizational data tab, he finds the ID number for the supplier.
    • He now checks whether the new supplier data is live in the company’s enterprise software.
    • He searches and is able to find the supplier.
    • He displays the vendor master data and verifies that the data for company code and the purchasing organization have been created correctly.
    • Tom can now create a purchase order and start doing business with the new supplier.
    • SAP Data Governance enables you to centralize and consolidate supplier master data to facilitate master data management and reduce associated costs.
  • Play Again?
  • 512
  • 288
  • video SAP Master Data Governance: Centralize and Consolidate Supplier Master Data

Closing this window will discard any information entered and return you back to the main page