Wednesday, February 4, 2009

Note 492399 - Realignment tool - Consulting

Note 492399 - Realignment tool - Consulting

Summary

Symptom

This note describes the realignment tool for Demand Planning.
With the Release of Support Package 20 for Release 3.0 or with the Release of Support Package 6 for Release 3.1 or with the installation of note 488568, this consulting note replaces note 360935.
This note also requires note 509171 or Support Package 21 of Release 3.0.

Other terms

/SAPAPO/TS_REALIGNMENT

Solution
General

To specify the realignment/copying characteristic values, an input table is created for the selected planning area. This consists of

  • a key column for the record ID (numbered sequentially) as well as
  • two columns for each characteristic of the planning area:
    • the source column (prefix 'F_' + information object name of the characteristic) and
    • the target column (prefix 'T_' + information object name of the characteristic).


By editing the input table, you define which combinations of target characteristic values (entries in the fields with the 'F_' prefix) are adjusted based on the combinations of source characteristic values (entries in the fields with the 'T_' prefix).Here, each data record of the input table (realignment/copy job) corresponds to a logically separate realignment/copy run.The jobs are processed in ascending order according to the specified job IDs.If no source characteristic value combinations are found during the realignment/copy run for a processed job, the process is cancelled.An inconsistent dataset is thus avoided.
The /SAPAPO/TS_REALIGNMENT report creates the input table and also carries out the actual realignment/copying process.

Note that no locks are set for the realignment. Generally, planners should not edit characteristics combinations to be changed (both in the source and in the target) during the realignment.

Input table

You can change (recreate) an input table created for a planning area at any time using the 'Generate input table' option.Here the application checks the validity of the input table and only generates a new table if the old one is no longer valid.An input table is valid when the number and names of the characteristics match the current configuration of the characteristics of the planning area.During the generation of the input table, you can select 'Restrict table characteristics' to limit the number of planning area characteristics copied to the table.From the list of all characteristics, select the characteristics required for specifying the combinations to be realigned/copied.If the planning area has so many characteristics that the table can no longer be physically generated, you MUST restrict the characteristics in the table.Here the graphic status display of the dialog box displays whether it is possible to generate the table with the number of currently selected characteristics.
You must specify characteristic values in pairs in the source and target column of a characteristic (prefixes: F_/T_). A characteristic value pair that is not specified always implies that all planning objects are selected with any values for the characteristic in question.The application sets the value of the status column of the input table to 'X' as soon as the realignment/copy job or the data record has been processed successfully.Realignment/copy jobs with the 'X' status are no longer considered for subsequent realignment/copy runs and can remain in the table to document the history of past realignment/copy runs.

In addition to the classic realignment, you can also use the /SAPAPO/TS_REALIGNMENT report for copying across characteristic combinations.Realignment and copying are explained separately below.Remember that the same input table is used for realignment and copying.If you want to execute both functions, SAP urgently recommends that you carry out these two steps separately from each other:once all entries of the input table are successfully processed (status 'X'), make the entries in the input table for the second step and execute this step.

Realignment process
    1. Prerequisites (these prerequisites do not apply if only InfoCube data is realigned (option 'Only InfoCube Realignment')):
      a) Time series objects must be available for at least one planning version of the planning area for which you are performing the realignment (cf. transaction /SAPAPO/MSDP_ADMIN).
      b) At runtime, each realignment job (cf. above) requires that at least one characteristic value combination is selected by the entries made earlier in the input table for combinations of source characteristic values and, at the same time, that no characteristic value combinations are selected by the combinations of target characteristic values made in the input table.If this requirement is not met, the job does not consist of realignment and therefore cannot be executed.If all target characteristic value combinations are already present, the job involved is copying (for details, see later section).If only some of the target characteristic value combinations are present, the job involves a combination of realignment and copying.This mixed scenario can be depicted via the copy function (see later).

Example:In the input table, an entry was made only for the characteristic 9AMATNR : Source: MAT1, target: MAT2.For the characteristic MAT1 2, 2 characteristic values LOC1 and LOC2 are available for the characteristic value 9ALOCNO.Only the characteristic value LOC1 is available for the characteristic value MAT2.In this case, realignment cannot be performed, since the target characteristic value combinations MAT2 LOC1 are already present.This is a mixed scenario consisting of realignment (since characteristic combinations have to be created) and copying (since some of the necessary characteristic combinations exist).

There must be no entries in the delta table /SAPAPO/TSPLOBDE. Reason:Created or deleted characteristic value combinations are stored again temporarily in the delta table.These entries are then read, the necessary liveCache objects are created/deleted and the entries in the delta table are deleted again.either you chose the option for immediately adjusting time series objects in transaction /SAPAPO/MC62 or you ran the report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC for the basic planning object structure of the planning area.Since this delta table is also used in realignment, it must not have any entries for the basic planning object structure of the planning area or for any existing aggregates (cf. transaction /SAPAPO/MSDP_ADMIN)when a realignment job is started. If such entries exist, realignment is cancelled.In this case, you must execute the report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC in advance if no other system activities indicate otherwise (for example, the time series objects should be adjusted at a later stage to avoid locking problems with a current background process).

    2. Planning area

Generally, all the liveCache time series key figures maintained for the planning area are realigned. You cannot restrict the key figures.
If several planning areas use the same master planning object structure, when the realignment is carried out for one of these planning areas, then the rest of these planning areas are automatically realigned too.This is necessary to avoid inconsistencies.In this type of situation, we recommend you specifically use one (always the same one) of these planning areas for the realignment.
If only InfoCube data is realigned (if the option 'Only InfoCube Realignment' was selected, a planning area is not realigned.

    3. Planning version

In principal, the data of all planning versions of a planning area is always adjusted.You cannot restrict the versions because this would create inconsistencies.

    4. InfoCube

If the planning area has key figures that are saved in a separate InfoCube (cf. transaction /SAPAPO/MSDP_ADMIN), then you can use these to explicitly specify whether a realignment should also be carried out through this InfoCube.You can display these InfoCubes in a display frame by selecting the 'Realignment InfoCubes' button.In general, however, you cannot select InfoCubes assigned to the planning area.
If an InfoCube does not use the same characteristics as the planning object structure for the planning area (cf. transaction /SAPAPO/MSDP_ADMIN), then you must note that the InfoCube must contain all the characteristics that were selected during the realignment assignment;that is, the InfoCube must contain all the characteristics that a restriction was made for in the input table (cf. above).In addition to this basic requirement, the InfoCube may still also contain more characteristics.
Generally, all key figures of an InfoCube assigned in this way are realigned. You cannot restrict the key figures.
If, during realignment, you select the option 'Only InfoCube Realignment' and then select one or more InfoCubes, the realignment is executed only for these InfoCubes.Using this option, you can therefore realign InfoCubes irrespective of planning areas.
Note that it is not currently possible to realign InfoCubes in which there is compressed data.If you execute this nevertheless, this can result in incorrect data.

    5. Settings:

During realignment, the data of the source characteristic value combinations is deleted by default together with the relevant movement data.If you select the 'No deletion of source data' option, then the data of the combinations of source characteristic values and its relevant movement data are retained.

Copying
    1. Prerequisites
      a) Time series objects must exist for at least one planning version of the planning area.If specific planning versions are selected for the copying process (cf. below), time series objects must exist for these planning versions.
      b) Every copying job (cf. above) requires that at least one characteristic attribute combination is selected during the runtime by the entries previously made in the input table for the source characteristic attribute combinations and, at the same time, at least one characteristic attribute combination is selected by the target characteristic attribute combinations made in the input table.If no target characteristic combinations are selected, then it is realignment and copying is not possible.
    2. Planning version

If you do not restrict the planning versions, the copy procedure is carried out for all planning versions of the planning area, for which time series objects exist.Here the data is copied across characteristic value combinations within the same planning version.
If the source and target planning version is restricted, the copy process is carried out only for these planning versions.
If source and target planning versions are different, the copy process is carried out across characteristic value combinations and across versions.

    3. Logic

In the case of the 'move' logic, any existing target data may possibly be overwritten by the source data.
With the 'Add' logic, the source data is added to the already existing target data.

    4. Options

The options 'Adding characteristics combinations' and 'Deleting the source data' can only be selected for copying if no version restriction has been made.

      a) Adding characteristics combinations:

If this option is NOT selected and the appropriate target characteristic attribute combinations are not available for all source characteristic attribute combinations according to the input table, the copy process is only executed for those source characteristic attribute combinations for which there are also the appropriate target characteristic attribute combinations.

Example:In the input table, an entry was made only for the characteristic 9AMATNR : Source: MAT1, target: MAT2.For the characteristic MAT1 2, 2 characteristic values LOC1 and LOC2 are available for the characteristic value 9ALOCNO.Only the characteristic value LOC1 is available for the characteristic value MAT2.If, in this case, copying is executed WITHOUT the option 'Add characteristics combinations', only the data of the combinations MAT1, LOC1 are copied to the combinations MAT2, LOC1.

However, if the option 'Add characteristics combinations' is selected, first the new characteristic attribute combinations MAT2 LOC2 are created and then the data of the combinations MAT1, LOC1 are copied to the combination MAT2, LOC1 and the data combinations MAT1, LOC2 are copied to the data of the combinations MAT2, LOC2 (mixed scenario with realignment and copying).

      b) Deletion of the source data:If this option is selected, the data for the source characteristic attribute combinations and the source characteristic attribute combinations are deleted even after copying.


Header Data



Release Status:Released for Customer
Released on:30.12.2002 22:18:54
Master Language:German
Priority:Recommendations/additional info
Category:Consulting
Primary Component:SCM-APO-FCS-RLG Realignment
Secondary Components:SCM-APO-FCS Demand Planning

Affected Releases

Software
Component
Release
From
Release
To
Release
And
subsequent
SAP_APPL
46C
46C
46C
SAP_APO
30
30A
30A
SAP_APO
310
310
310

Related Notes




1098441 - Automating the realignment process

812045 - Realignment exceptions and performance

540926 - Collective consulting note on planning object structures

512195 - Realignment without aggregates

509171 - Addition to note 488568

1 comment:

KrRahul said...

Thanks for sharing...