Exploring Multiple Object Processing

Objective

After completing this lesson, you will be able to explore multiple object processing.

Mass Changes and Multiple Record Processing

Characteristics of Multi-Record Processing:

The characteristics of multi-record processing include the following:

  • Well-defined governance process with multiple workflow steps for a limited number of Business Partners

  • Typically a collaboration of multiple processors

  • Governance processes for single and multiple objects

  • Examples:

    • An account manager wants to compare and harmonize sales data for all customers belonging to the account.

    • A strategic buyer wants to update purchasing conditions of all relevant suppliers based on a newly signed contract.

Characteristics of Mass Processing

The common characteristics of mass processing include the following:

  • Interactive master data change process for a huge number of Business Partners

  • Typically ad-hoc / on-request / project-based processing by one data specialist

  • Examples:

    • Change dunning parameters for all C-Customers of a country based on a newly defined process.

    • After reorganization in purchasing, Suppliers are assigned to newly responsible purchasing groups.

Processing of Multiple Objects: Multi-Record Processing: Getting In

The process to change multiple Business Partners is performed using a spreadsheet-like UI.

The screenshot shows several selected business partners from the result list, selected for multi-processing.

Start from the search result list:

  1. Select multiple Business Partners.
  2. Choose the Multi-Processing button.

Pre-defined Change Request types are:

  • Multi-Processing for Customer Sales
  • Multi-Processing for Customer Financials
  • Multi-Processing for Vendor Purchasing
  • Multi-Processing for Vendor Financials

Multi-Record Processing: Functionality

Functions for rows are:

  • Add new rows
  • Copy rows
  • Delete rows

Functions for field values are:

  • Edit single fields
  • Find and replace
  • Select rows with same value
  • Copy value to selected rows

Functions for Visualize/handle changes are:

  • Highlight changes
  • Discard changes
The screenshot shows the Multi-Record Processing Functionality.

Switch On or Off Highlight Changes

The Highlight Changes button, in some template UI configurations, allows the user to toggle the highlight changes function in multi-record processing.

The screenshot shows the Highlight Changes functionality.

At startup, the highlighting of changes is always switched Off.

This may enhance UI performance in certain cases.

For more information, see SAP Note 2547067 - MR Processing: Switch "Highlight Changes" and How to Guides on the SAP Community, such as Create User Interface for Multiple-Record Processing.

Change Request Types for Multiple Objects

SAP Master Data Governance change requests can be used for different tasks. Besides single object processing, they manage mass change processes, multiple object, and form-based workflows.

The figure gives an overview of the different change request types in master data governance.

Note

When a change request is approved, all object changes contained in it are approved. In other words, activities with one change request affect all contained objects.

Change Request Types for Multiple Object Processing

With change requests, it is possible to work with multiple objects in one transaction. Change requests for multiple processing can contain multiple objects (as long as they are the same object type, for example, a material and a supplier in one multiple change request is not possible), and manage hierarchy processing and mass changes.

The figure gives an overview of different change request types for multiple object processing.

Change Request Workflow for Multiple Object Processing

The figure illustrates the change request workflow of multiple-object processing. It starts with a mass change request. First step in the workflow is to select the entities you want to change from the active area. Assign entities and changes to the mass change request in the second step. In step three, the validation takes place. Next, approve the change request. In the last step, the replication to a connected system takes place.

The figure illustrates the change request workflow of multiple-object processing. It starts with a mass change request. First step in the workflow is to select the entities you want to change from the active area. Assign entities and changes to the mass change request in the second step. In step three, the validation takes place. Next, approve the change request. In the last step, the replication to a connected system takes place.

For mass changes or other multiple object management features, it is necessary to prepare an appropriate change request. After this, the end user can select the objects and assign them to the change request. The change request type determines the workflow steps, agent determination, validations, and so on - in exactly the same manner as used for a single object change request.

Change Request Type Definition

The determination of whether a change request is appropriate for multiple processing is defined in SAP Master Data Governance customizing (the Implementation Guide).

For an example of a Business Partner change request, refer to the figure here.

The screenshot shows the change request customizing settings.

Perform Multiple Material Record Processing

Business Example

In this exercise, you are acting as a product manager who wants to change different material master records using one change request. Therefore, you can use multiple-record processing.

ExerciseStart Exercise

Learning

SAP FacebookSAP YoutubeSAP LinkedIn