Show TOC

Component documentationChange Request Processing

 

The change request processing documents outline the functions and processes used for creating and processing change requests. During a typical workflow a user might first search for and display materials, then generate change requests to create, change, or mark materials for deletion depending on their requirements. The user can also update multiple materials at the same time using the Create Change Request and Mass Change services.

The user does not actually create, change, or mark materials for deletion here; instead they create change requests that, in a typical workflow, are sent for approval by a master data expert. Once the expert approves the change request, the system performs a validity check, and if there are no errors the new or updated material data is written to the active area. During the change request process the new or changed master data is stored in the master data governance staging area.

The change request worklist provides the user - either a normal user or a reviewer - with a list of work items to be considered. The user typically opens a work item in the Change Requests screen from which he can activate the change request, reject the change request, validate the change request data, view the validation log, forward the change request, or perform a duplicate check. The user can also access the BCV side panel to view additional information for the change request. For more information, see Configuring Business Context Viewer for MDG Material.

The steps in a typical workflow are outlined below:

  1. The user creates a change request and the data in the change request is written to the staging area. The user may use the duplicate check to have the system scan for duplicate master data entries.

  2. The change request is sent to a Master Data Steward to review and approve.

  3. The Master Data Steward reviews the change request and either approves it or rejects it. The Master Data Steward has the option to use the built-in duplicate check to have the system scan for duplicate master data entries. Note that the duplicate check does not provide a ranking feature for the duplicate entries.

  4. If the Master Data Steward rejects the change request it is sent back to the creator who can either discard the change request or modify and resubmit it.

  5. If the Master Data Steward approves the change request the system performs a validity check on the data contained within it.

  6. If the validity check comes back with errors then the change request cannot be activated. The Master Data Steward must correct the errors.

  7. If the validity check comes back without errors, the information in the change request is written to the active area and the process is complete.