Describing Mass Runs in SOM

Objective

After completing this lesson, you will be able to describe mass runs in SOM

Business Example: Mass Runs in Subscription Order Management

Business Example Mass Run: Create with Master Agreement

A customer’s headquarters and the service provider both agree on a master agreement. Development South and Development North have closed 100 subscription contracts.

The customer collects the relevant master data for the service recipients, for example, business partner number and contract duration. The collected data is uploaded to the mass run. If the data validation was successful, then the subscription order and contract can be created and distributed. If an error occurs, the subscription orders will not be created.

Business Example Mass Run: Create Without Master Agreement

The service provider needs to run a mass activation of contracts for the same product, with identical contract start date, but for different sold-to parties. The service provider collects the relevant sold-to and ship-to parties together with the technical resource IDs.

The collected data is uploaded to the mass run. If the data validation was successful, then the subscription order and contract can be created and distributed. If an error occurs, the subscription orders will not be created.

Business Example Mass Run: Change

A service provider needs to extend a set of contracts. The service provider preselects the contracts to be extended. The system processes the contract extension change process. Depending on the settings in order data distribution, the subscription contracts are updated and distributed at the given activation date.

Mass Runs in Subscription Order Management

A flowchart of subscription order management features categorized under six sections: Product Modelling, Order Capture, Order Distribution, Contract Change Processes, B2B Features, and Solution Quote and Business Portfolio. Each section lists specific tasks and capabilities related to managing subscription orders.

The mass run functionality enables the planning of the creation or processing of a preselected number of subscription orders and contracts, ensuring high-performance execution. It allows for tracking progress, monitoring results, and further processing of new or changed entities. Mass run execution can be triggered in the mass run maintenance or by planning appropriate jobs.

Definition of a Mass Run

A Mass Run:

  • Functionality supports the bulk creation of orders and the mass change of contracts. This feature is usually in B2B scenarios.
  • Has a set of parameters that is used to either create a predefined number of subscription orders or to change a selected set of contracts.

Focus on the following two aspects:

  • Mass Run Definition – Plan the creation or processing of a preselected number of subscription orders or contracts.
  • Mass Run Execution:
    • Ensure high performance execution by supporting process parallelization.
    • Track processing progress.
    • Support mass run monitoring, further processing of new or changed entities, as well as erroneous entities.
    • Trigger mass run execution in mass run maintenance or by planning appropriate jobs.

Industry Examples

  1. Mass Contract Cancelation, for example, 100 Contracts are expired and need to be canceled.
  2. A big customer orders 100 subscriptions for different subsidiaries with the same product.
  3. Changes to the Cloud Selection Service are necessary for more than 100 customers.

You can find predelivered sample mass run types such as the following:

  • Create subscription orders with reference to a master agreement.
  • Create subscription orders for a specific product and individual sold to parties and technical IDs.
  • Run a mass change for change of cross catalog mapping version.
  • Run a mass cancellation of contracts.
Flowchart illustrating the mass run process for creating subscription orders and changing subscription contracts in SAP S/4HANA Service. Includes steps like file data entry, master agreement reference, product bundle selection, subscription contract creation, and change order execution.

This business scenario shows the Mass Run Process Flow:

In scenario A, a subscription order / contract is created with reference to a master agreement:

  1. The data is entered as a CSV File and contains business partner data, such as sold to party and ship to party, as well as the corresponding technical resource
  2. Choose the master agreement as reference for the order creation and add following data:
    1. Product Data - The field is called Custom ID
    2. Transaction Type- Subscription order PRVO
    3. Contract Account
  3. Execute a mass run.
  4. Check subscription order and subscription contract creation.

In the scenario B, subscription order/contract is created without reference to a master agreement.

  1. The data is entered as a CSV File and contains business partner data, such as sold to party and ship to party and the corresponding contract account and corresponding technical resource
  2. Add the following data: Enter Product Data
    1. Enter the transaction type, Subscription Order PRVO Execute Mass Run.
    2. Check the subscription order and subscription contract creation.
  3. Execute a mass run.
  4. Check the subscription order and subscription contract creation.

In scenario C, a mass run for contract change, a cancellation is shown:

  1. The data entry consists in subscription contract IDs.
  2. Enter an activation date and cancellation reason.
  3. Execute a mass run.
  4. Check change order creation.

Consider that step 1, data entry from scenario A and B can be done without a CSV File, manually.

Mass Run Data – Header Status

Header StatusDescriptionAllowed Activities
OpenInitial status.

Can be edited.

Not observed by execution jobs.

Cannot be started.

Can be manually switched to Released for Processing.

Released for ProcessingCan only be set manually.

Can no longer be edited.

Status can be switched back to Open.

Execution can be started by choosingRun.

Mass run is observed by execution jobs.

In ProcessSet automatically once the elements are processed manually or by an automatic job.

Mass run cannot be changed.

Transient status: Status switches to Processed Successfully orProcessed with Errors after processing.

Processed Successfully

Set automatically after processing.

Prerequisite: All elements in status Processed successfully or Processed Manually.

Final status

Processed with Errors

Set automatically after processing.

Prerequisite: At least one element in status Processed with Errors.

Elements with errors can be manually adjusted or transferred to a follow-up mass run.

Once all elements have been manually adjusted to Processed Successfully or taken over into a new mass run, the status switches to Processed Successfully.

  • Mass runs consist of a general header data, a mass run category, and a type of specific header and element data.
  • Mass run ID, identifies a mass run and is taken from a number range in the customizing.
  • Earliest execution date for this mass run is observed by the report if an automatic job is used; it's not evaluated if the execution is started by choosing run.
  • Mass run type defines the behavior of the mass run (activity type).

Mass Run Process Data:

  • Create without a master agreement, supports, product, employee, contract start, and transaction type.
  • Create with master agreement. In addition, it also supports, master agreement ID, custom product ID, and sharing contracts, together with several partners.
  • Correctness of entered process data can be checked. On process header level all fields are maintained, which are shared between all orders/contracts within a mass run.

Process data for mass runs depends on the mass run category and type:

  • Create without master agreement support product, employee, contract start, and transaction type
  • Create with master agreement, in addition, support master agreement ID, custom product ID and sharing contracts, together with several partners.

Correctness of entered process data can be checked. On process header level, all fields are maintained, which are shared between all orders/contracts within a mass run.

Mass Run Process Data: Elements - Status

Element StatusDescriptionAllowed Activities
OpenInitial status of an element

Element can be edited (according to the field settings), but the status cannot be changed.

Element can be deleted.

Element can be checked.

Element will be processed when mass run is processed.

Successfully ProcessedElement has been successfully processed without any errors being reportedFinal status
Processed with ErrorsErrors occurred during processing

Messages can be displayed choosing Show Messages in the Actions column.

Element can be reprocessed, transferred to a new mass run or status can be set to Processed Manually.

Processed ManuallyFinal status that can only be set manuallyCan be set if the contract of an element, processed with errors, has been corrected manually.
  • The element information can either be entered via search, .csv file upload, or using a predefined selection.
  • Details are displayed on a separate page. Choose Details.
  • To avoid performance problems and enable high-volume processing, you'll find another search screen to limit the number of displayed contracts.
  • To verify the entered information, choose Check All.

Background Processing

Mass runs can be executed in two ways:

  • Execute a mass run in dialog mode on the UI.
  • Schedule a mass run to be executed at a certain point of time.

Mass run scheduling requires the report CRM_ISX_MR_PROCESSING to be scheduled periodically as a background job (transaction SM36).

General selection criteria:

  • The planned execution date is earlier or the same as the time at which the report is executed.
  • Current mass run status is Released for Processing.

Additional optional selection criteria (to be specified during report execution):

  • Mass run type priority.
  • For execution order, the selected set of mass runs is sorted descending by priority from the mass run header data.

Mass Run Error Monitoring

In the elements table (Create), or in details section (Change), you can find details about the mass run results. For successfully processed elements, order/contract IDs are displayed. For not successfully processed elements, you can check the details by choosing Show Messages. A pop-up window opens and provides details about the error.

Mass Creation – Processing in Dialog Mode

  • After data entry, the mass run status can be set to Released for Processing.
  • Executing the mass run in dialog mode by choosing Run Processing will start to observe the current processing status. Choose Update.
  • The summary provides an overview about the status of the elements.
  • The header status is set as summary of the elements’ status.
  • The results for each elements are shown in the Elements table in the Status column.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn