Entering content frameBackground documentation Performance, Parallel Processing, and Partitioning Locate the document in its SAP Library structure

Realignments should not be executed in parallel with processes that post data to Profitability Analysis (more accurately: processes that determine a profitability segment). Especially with large data volumes, the conflicts that arise between read and write actions usually cannot be reconciled by the database system. In most such instances, the reading processes is forced to terminate - in this case, the realignments. Larger realignments can therefore only be processed at a time when the system workload is low and - most importantly - when no postings are made to Profitability Analysis.

Realignment runs in which the conversion rule merely carries out derivation again for some characteristics and does not change the others may be executed at the same time. To avoid unpredictable results, you should always use partitioned datasets when executing realignment runs in parallel. To do this, select one characteristic that divides the dataset into separate parts that are of the desired size. Then you need to define a realignment run for each characteristic values specified, and change each realignment request in the run to include that value as a selection parameter. (Note that the characteristic value used to partition the datasets is not changed during the realignment run.)

Example

Situation: The sales view of a customer master record has changed. You create a realignment run called "Adapt sales hierarchy", which contains only one realignment request - to derive characteristics WWS01, WWS02, ..., WWS05 of the sales hierarchy. However, your experience tells you that the realignment run cannot be completed during the available time window. The existing profitability segments are equally distributed between the five company codes in your organization (0001 through 0005). Your database hardware, the physical distribution of the data on the hard drives (see also the section Physical Distribution of the Data in CO-PA ), and the available application servers suggest to you that it would be possible to execute multiple runs simultaneously.

Procedure: Create four copies of the realignment run "Adapt sales hierarchy" and change the names to "Adapt sales hierarchy, CoCd 0001", and so on. In the realignment request of "Adapt sales hierarchy, CoCd 0001", specify company code 0001 as a selection criterion. Do the same with the other four realignment requests, each time specifying the corresponding company code. Then schedule the realignment runs for execution at the same time.

Note

If the realignment request already contains selection criteria, you need to add this characteristic value to the existing ones.

If the realignment run you are partitioning contains more than one realignment request, you need to add the partitioning characteristic value to each of the requests.

Example

The following realignment run is to be partitioned into two parts depending on the company code ("1000" and "2000").

Realign.Run0
  Realign.Request1
    Selection criterion
      Material hierarchy 1 between 1010 and 1019
    Conversion rule
      Derive material hierarchy 1 again
      Derive material hierarchy 2 again
      Derive material hierarchy 3 again
  Realign.Request2
    Selection criterion
      Material hierarchy 1 = 1010
    Conversion rule
      Derive material group again

This yields the following realignment runs:

Realign.Run1 (CCode 1000)
  Realign.Request1
    Selection criterion
      Material hierarchy 1 between 1010 and 1019
      Company code = 1000
    Conversion rule
      Derive material hierarchy 1 again
      Derive material hierarchy 2 again
      Derive material hierarchy 3 again
  Realign.Request2
    Selection criterion
      Material hierarchy 1 = 1010
      Company code = 1000
    Conversion rule
      Derive material group again

Realign.Run2 (CCode 2000)
  Realign.Request1
    Selection criterion
      Material hierarchy 1 between 1010 and 1019
      Company code = 2000
    Conversion rule
      Derive material hierarchy 1 again
      Derive material hierarchy 2 again
      Derive material hierarchy 3 again
  Realign.Request2
    Selection criterion
      Material hierarchy 1 = 1010
      Company code = 2000
    Conversion rule
      Derive material group again

 

 

 

Leaving content frame