MCDelta

SAP Customizing Comparison & Harmonization

for Adoption of Central Finance
Version 9.0
March 2020

User Guide
TABLE OF CONTENT

PURPOSE OF USE AND TARGET GROUP .................................................................................................... 3

REQUIREMENTS AND RESTRICTIONS ......................................................................................................... 3
GLOSSARY ....................................................................................................................................................... 4
1.) GENERAL INFORMATION ......................................................................................................................... 5
1.1) Background ............................................................................................................................................... 5
1.2) Overview on process phases .................................................................................................................. 6
2.) HOW TO USE MCDELTA ............................................................................................................................ 7
2.1) Overview .................................................................................................................................................... 7
2.2) First time using MCDelta ....................................................................................................................... 10
2.2.1) Select the project task ID (TID) ............................................................................................................. 10
2.2.2) Display analysis results ......................................................................................................................... 10
2.2.3) Adapt display of customizing comparison ............................................................................................. 10
2.3) Understand comparison analysis results ............................................................................................ 14
2.4) Data drill-down ........................................................................................................................................ 16
2.4.1) Display customizing entries per object .................................................................................................. 19
2.4.2) Detailed view per object key .................................................................................................................. 21
2.4.3) Show it “SCU0”-style: all data in one screen ......................................................................................... 22
2.4.4) Data categories and how to access directly .......................................................................................... 23
2.4.5) Print / export object result ...................................................................................................................... 24
2.5) Table statistics........................................................................................................................................ 25
2.6) Interpretation of customizing analysis results .................................................................................... 26
2.6.1 Conflict handling: Assign solutions on table level ................................................................................... 27
2.6.2 Conflict handling: Assign status / actions on key level ........................................................................... 28
2.7) Running a new comparison .................................................................................................................. 29
2.7.1) Add maintenance view object ................................................................................................................ 31
2.7.2) Check for changes after a certain date ................................................................................................. 32
2.7.3) Compare DDIC structure of master data table – Check customer fields .............................................. 33
2.8) Distribution of customizing ................................................................................................................... 34
3.) MAPPING AND FILTER ............................................................................................................................ 35
3.1) Create mappings via the integrated mapping functionality ............................................................... 35
3.2) Central mapping creation ...................................................................................................................... 37
3.3) MapFactory ............................................................................................................................................. 39
3.4) Filter – Differences to mapping engine ................................................................................................ 44
4.) PROJECT: SETTING IT UP AND MONITOR............................................................................................ 45
4.1) Project menu ........................................................................................................................................... 45
4.1.1) Role “Project Lead”................................................................................................................................ 45
4.1.2) Role “Subproject Lead” ......................................................................................................................... 49
4.2) Monitoring ............................................................................................................................................... 51
4.3) Inbox ........................................................................................................................................................ 52
5.) USAGE CHECK ......................................................................................................................................... 53
5.1) Usage of customizing ............................................................................................................................ 53
5.2) Utilization statistics for customizing .................................................................................................... 54
5.3) Rate of master data change .................................................................................................................. 57
SAP MCDELTA, VERSION 9.0 - USER GUIDE

PURPOSE OF USE AND TARGET GROUP

This user guide supports project team members active in implementations of SAP Central Finance.
The document gives an overview on the functionalities of MCDelta and provides detailed explanations
on how to interpret the results of a customizing comparison.
MCDelta helps to accelerate customer projects that are realized via service offerings of SAP
Consulting or assists during the pilot phase of implementing a new product from SAP SE.

Target group:
Project team members with SAP application knowledge who are responsible for aligning customizing
data (blueprint / harmonization).

REQUIREMENTS AND RESTRICTIONS

Requirements:
o SAP S/4 1709 or higher for target cFin; SAP ECC5 (basis 6.40) or higher for source systems
o The tool consists of several transports of which most need to be imported into both central and
source systems. Please check the MCDelta installation guide for more details.
o RFC connections from central system to all systems taking part in the comparison (direction back
not needed)
o The system administrator must generate several profiles via transaction PFCG. These profiles are
based on role templates that are not part of the SAP standard installation:
▪ 1. Standard user (SAP_MCT_MCDELTA)
▪ 2. Subproject lead (SAP_MCT_MCDELTA_SUB)
▪ 3. Project lead (SAP_MCT_MCDELTA_PRO)
▪ 4. Additional right to use MCDelta-embedded TAANA (SAP_MCT_MCDELTA_TAAN)
▪ 5. RFC user in satellites: scan and fetch data (SAP_MCT_MCDELTA_SAT)
▪ 6. RFC user in satellites: display remote master/transact. data (SAP_MCT_MCDELTA_RLST)

Please note:
▪ The role templates are part of the MCDelta transport.
▪ The customer role “Project lead” should be handled with care. Do not attach to several users
but the real project lead only. For differentiating the project into subunits, use role “Subproject
lead” instead

Restrictions:
MCDelta and the underlying platform MCS are provided as an accelerator, exclusively offered with
SAP services delivered by SAP SE or its subsidiaries. Any software delivered during the project
belongs to SAP and usage is allowed for the duration of the SAP project only.

3
SAP MCDELTA, VERSION 9.0 - USER GUIDE

GLOSSARY

Definitions used within this document:

o EasySetup: Transaction to quickly set up a task ID (→ TID) and define the scope of the
comparison. Please check the EasySetup user guide which is part of the adoption service content
o GID: Group ID → see TID for further explanation
o Central system: the cFin system from where the analysis is executed and where users work with
MCDelta
o Logical system: synonym for system client
o Mapping: value conversion of a key or attribute field in a customizing table row. Conversion is
done by the means of a mapping table with columns for old and new values. MCDelta does not use
the MDG concept of “Key / Value Mapping”
o Primary: cFin target client with SCID = 01 (→ SCID)
o Remote system(s): technically, MCDelta only knows remote systems. If the local cFin client of the
central system gets compared, too, it must be connected using RFC = “NONE”
o Result types of analysis:
• Identical: a specific object (a complete customizing table or a single table row) exists in all
systems which are compared and has identical values (attributes)
• Conflict: a specific object (e.g. single customizing table row) exists with identical key in at least
two systems that are compared but the attributes do not have the same values
• Delta: a specific object (e.g. single customizing table row) exists in one of two compared
systems only
o Satellite: Source system connected to central system
o SCID: System Client Identifier; each system client taking part in the comparison has a unique
number from 01 to 31. In the system merge example used in this document the system clients are
as follows:
▪ “BC4” 01 “Target”
▪ “802” 02 “Source 802”
▪ “810” 03 “Source 810”
o Secondary: any connected ERP source system (SCID > 01).
o Source system: any system connected to the central system; satellite is a synonym. Both the
Primary and the Secondaries are source systems
o System name: any 3-character combination to name a participating system client, not to confuse
with the standard SAP System ID. The system names will be specified by the SAP technician
setting up MCDelta for the first time
o Target system: Principally, MCDelta does not use the term “Target” but “Primary” (→ Primary).
Still, in this special cFin context we can refer to the local cFin client as the target
o TID: Task ID; grouping tables in one logical unit, e.g. all client dependent tables or all tables for
logistics. The task ID is the main parameter in the start screen of MCDelta. Task ID is different to
the group ID (GID), which bundles several TIDs, so they can share mapping for example.
Internally, each TID will be assigned to a GID and the GID will not be used anywhere as selection
parameter but determined automatically (e.g. for mapping maintenance)

4
SAP MCDELTA, VERSION 9.0 - USER GUIDE

1.) GENERAL INFORMATION

1.1) Background
Companies facing business challenges - such as incorporating a company recently acquired or
reorganizing the company’s organizational structures - are often struggling to adjust their system
landscape consistently on IT level. A major concern is to ensure that the customizing data of all
affected SAP systems is fully aligned to secure continuous business processes and consistent data.
Furthermore, necessary adaptation and integration efforts as well as creating suitable mapping
approaches to align the relevant customizing settings can be very complex.
The SAP MCDelta Customizing Comparison accelerator provides a proven solution to assist
project teams in comparing the customizing and selected master data of up to thirty-one source
systems.
MCDelta scans all customizing tables in the systems (connected via RFC) and identifies all
conflicts and deltas of the customizing data between them. The results are logged centrally and can be
accessed in the central system (cFin) providing you a detailed and comprehensive overview of your
customizing data across your system landscape. Furthermore, MCDelta enables you to solve
identified issues with conflicting customizing by providing integrated mapping functionalities. Mapping
created within MCDelta can also be integrated into the migration tools used by SAP experts, thus
avoiding error-prone spreadsheet-based approaches. Users can classify objects with pre-defined
solution tags to categorize the identified conflicts or deltas.
In addition, MCDelta offers several project monitoring functionalities: Users can assign tasks to
project members, maintain status per specific work items and maintain due dates per single objects.
Please note that the customizing analysis results provided in MCDelta are based on a snapshot of
the systems that has been created at a certain point. The original customizing data of all sources is
stored in the central system, so you can work independently of the availability of the remote
connections. This can be an advantage, if the RFC connections are not available full time (e.g. system
refreshes). If configuration settings and / or data change afterwards, it might become necessary to
repeat the customizing comparison completely or for single objects.
In this document we will show data examples based on a cFin adoption scenario. Two ERP
systems are supposed to be harmonized in reference to an already existing cFin client. Two ERP
clients (labeled “802” and “810”) will be compared against the cFin client (labeled “BC4”/“Target”).
In MCDelta context, the two clients “802” and “810” are the so-called Secondaries, while the
receiving client “Target” is the Primary.

5
SAP MCDELTA, VERSION 9.0 - USER GUIDE

1.2) Overview on process phases

This chapter gives a short overview on the typical phases when carrying out a customizing comparison
using MCDelta.

Fig. 1: Process phases

The first step is to gather the required information for the planned comparison. This includes especially
information about which systems will be compared and the data scope (fiscal years). The definition of
the relevant customizing is already part of the content of the cFin adoption service.
Based on this information, either an SAP technician or customer (if using EasySetup) then set up
the comparison accordingly and carry out the customizing analysis. Next – if involved – SAP
consultants will interpret the analysis results. In this phase, the conflicting customizing entries are
evaluated about potential impacts on other systems. SAP will hand over the analysis findings and
recommendations to the customer and jointly discuss with the customer project team. Normally, this
takes place within a handover workshop (remote or onsite).
Based on the provided analysis results, the customer project team can evaluate the identified
issues and decide about the preferred solution how to handle the conflicting entries. In a next step, the
customer project team can create appropriate mapping to define how those entries should be handled
in the subsequent project steps.
As soon as the customer has decided on all relevant customizing entries and maintained the
mapping the initial load phase may start.

6
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.) HOW TO USE MCDELTA

2.1) Overview
Use transaction MCDELTA to access the customizing harmonization cockpit:

Fig. 2: MCDelta start screen

MCDelta provides a central work center structure. Below you find a short description of the main
functionalities accessible via the start screen (see figure 2):
1) Menu buttons
Inbox - Access to personal messages
Status / Notes - Save status info and notes maintained in MCDelta for editing or backup purpose
Project - Project maintenance view and administration
Mapping - Central access for maintaining mappings
Filter - Central access for maintaining filters (data selection)
Org. Structure - Display the organizational unit structures
for each source. The data is shown redundantly twice
in a split screen for easy comparison
Rate of change - Ad hoc analysis of data
changes based on year/month.
Summary DB table sizes - Show size and
growth of tables used in master / transaction data filter
Customer fields in DB tables - Check Y/Z-fields and their values; compare structure
User Settings - Change your personal layout
General product info

7
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2) Project task ID
With EasySetup a task ID (TID) was already created prior to using this analysis display. When
setting up the TID, it was determined which systems (max. 30 ERP sources) to scan and which
customizing / master tables to compare.

3) Additional Display field

Within this box, you can adapt the display options according to your individual requirements and
select different views. Please refer to chapter 2.2.3 for more details.

4) Filter for Display and Export Status/Notes

You can assign status settings to single components and assign work packages and
responsibilities after a comparison run. Within this box, you can configure which analysis results
are displayed by applying filters on:
• Status
• Processor
• Responsible
• Component

Please note: In case, you want to display all results referring to a specific application
component and below, please add a ‘*’ to the component name: e.g. for all analysis results
belonging to the application Controlling (CO) set filter ‘CO*’.

Furthermore, it is possible to hide data of inactive components. This option is not automatically
included, and the checkboxes might be without effect. This data filter can only be used, if all
systems involved were scanned regarding whether application components are possibly not active.
Please keep in mind, that this is only an indicator, not a guarantee that the component is inactive.
This filter cannot be activated after a complete comparison run was already done.
The “Mark only” checkbox is only meaningful combined with the flag "Filter inactive components". If
this filter is active, you have two options using this flag:
• Not flagged: Data belonging to an inactive component will not be displayed. It is treated
as non-existing. This allows a better overview of the relevant data.
• Flagged (default value): Data belonging to an inactive component will be displayed as
usual, also in the statistics. The only difference is that affected columns and rows will
show in a different color to indicate that this specific data is potentially irrelevant.

5) Statistics box
Within this box, you can select additional statistics to be displayed on the customizing comparison
results screen.
Data share per system

• When flagging the “Data share per system” box, the number of table keys of the table in the
participating logical system is listed.
• When flagging the “in %” box, the comparison will show the ratio (in %) of number of table
keys of a customizing table of a single system client compared to the overall number of
existing customizing table keys in all assigned systems.

8
SAP MCDELTA, VERSION 9.0 - USER GUIDE

CMP – Counter Secondary systems

• Unique entries: Setting this flag will show the number of truly unique entries in each logical
system
• Unique entries relative to Primary: Setting this flag will show the number of unique entries in
each Secondary, but only in relation to the Primary
• Missing entries: Setting this flag will show the number of keys for each secondary system,
which exist in the Primary but not in this Secondary
• Modified entries relative to Primary: Setting this flag will show the number of conflicts in each
logical system in relation to the primary system
• Modified entries between Secondaries only: This flag is only useful for comparisons of more
than two systems. Here the number of conflicts is only counted for differences between
Secondaries. The primary system is not considered (e.g. if it is an “empty” system which was
not cleaned up)
For more details, please see item “Statistics” at the end of chapter 2.2.3.
Press the button for showing the history log of the major key indicators. This function is only
active after there was a complete rerun of the analysis. If you just compare single tables within
MCDelta it will not be reflected here.

6) Find TID for a table and free text search

You can search for the TID of a specific table. Type the table name and press the Enter key. Or
enter any term into the text search field. All descriptions of tables and their fields will be scanned,
and any matches be shown.
Use the button labeled “IMG nodes” to show only the tables which correspond to certain IMG
topics. Please note that selecting a node will automatically select all sub nodes. Deselect sub
nodes if needed.

7) Individual status box

This box gives an overview about the status of working packages assigned to a single user. The
number / existence of user-specific personal messages in the inbox is also displayed here.

8) Project News
The assigned project lead can create general project relevant news to show in this window. The
news is visible to all users having access to MCDelta.

9
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.2) First time using MCDelta

This chapter shows the first steps of how to display the analysis results.

2.2.1) Select the project task ID (TID)

In the “Project TID” field you can select a task ID. You cannot create a task ID in this transaction,
this was already done using EasySetup.

Fig. 3: First step - select a project task ID (TID)

2.2.2) Display analysis results

Select “Display” : In the subsequent screen (figure 4), MCDelta now shows the analysis results
of the tables assigned to the selected TID.

Fig. 4: Result screen of customizing comparison

2.2.3) Adapt display of customizing comparison

You can change the standard of the data display style and blend in additional columns for the result
display. To do so, go back to the MCDelta start screen and enter the user settings ( ). Additionally,
you can make use of the standard ALV variant configuration directly in the data grids.

10
SAP MCDELTA, VERSION 9.0 - USER GUIDE

User Settings:

Fig. 5: User settings and their effect on the table overview screen

General settings
• Standard TID:
Enables you to define a TID as default in your personal settings

• Preferred text language: MCDelta is only available in the two languages English and
German. If you want to see the table, component and text table descriptions in another
language, then please log on in English and set your preferred language here in the settings.
MCDelta screen elements will remain in English, but the data gets translated as far as
possible.

MCDelta – Customizing Comparison

• Data display “SCU0” style:
The data of the comparison run displays in the style of the SAP Customizing Cross System-
Viewer (SCU0)
• Display field Transport:
On the results screen another column “Transport” is added, where you can enter information
on transport numbers

• Display counter for usage check:

In the “SCU0” style display, an extra column will be added to show for each key how often it
is used. From there you can directly jump to the usage statistics

MCDelta XXL – Object Comparison (not included or described here)

• Conflict free columns hide automatically if a table has more than the defined number of
fields.

MCCheck – Customizing Integrity Check (not included or described here)

• Limit ALV rows: The maximum number of rows in the result list can be limited here

11
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Additional Display:

Fig. 6: “Additional Display” box

Objects without conflicts:

• Additional display of objects that show no conflicts (flagged by default). This does not imply
that this object / table is 1:1 identical between all system clients participating in the
comparison. It just means that an object is shown, which has no database entries with the
same key but differing attributes. Check the F1-Help which offers a very detailed
description (both in German and English)

Text tables:
• The analysis shows also text tables (flagged by default)

Classified objects only (if applicable/available):

• Activate this flag to display only those objects, which are deemed important / central for the
initial evaluation of a standard ERP system. This list is based on past experiences handling
various customer projects. Thus, it will not necessarily exactly match your "own" list.

Statistics:

On the MCDelta start screen, you can also select from different statistics to be displayed:

Fig. 7: “Statistics” box

12
SAP MCDELTA, VERSION 9.0 - USER GUIDE

In the examples below you can see the results on the overview screen when all checkboxes have
been flagged:

Fig. 8a: Display statistics

Fig. 8b: Display statistics for new keys; only effective after a table was compared for the second time

13
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.3) Understand comparison analysis results

This chapter provides you with an overview about how to understand and interpret the fields displayed
in the analysis results overview.
For the comparison in this example, the fields “Objects without conflicts” and “Show text tables”
were flagged on the start screen. The results screen below shows an extract of the tables found in the
systems.

Fig. 9: Results screen of customizing comparison

In the following, all relevant columns of the results screen are explained in more detail:

Action:
Provides a protocol function: By clicking on a field in this column, a popup window opens
showing protocol messages, e.g. when and by whom a specific comparison run was carried out.
This column does only appear if the re-comparison and / or distribution feature is activated by
the project lead!

Total:
Total number of customizing entries in all systems analyzed (not counting entries that are
marked as “not used” in the secondary systems).

Conflicts:
This field shows the number of effective differences found during the comparison. It means that
in at least two logical systems there is an entry with the same database key but one or more
attributes having different values. But if one logical system contains a specific customizing entry
(database key) which is not existing in any other system then this is not classified as a conflict
but would be classified as a “Delta” (the latter could be transferred to the primary system
without mapping of the key or changes to its values).

Diff. Vers. (Different Versions):

Maximum number of different versions found for a single customizing entry in all assigned
systems.

Example:
A Purchasing Group has an entry with the same key in two out of three systems, each having a
different value for the same attribute. In this case “Diff. Vers.” is equal to 2.

1:1
Only relevant in case you selected the option “Objects without conflicts” in the Additional-
Display selection screen (see chapter 2.2.3).
The list shows objects with no conflicts, which does not imply that this object is 1:1 identical
between all system clients participating in the comparison. It just means that an object is shown,
which has no DB entries with the same key but differing attributes (thus "Conflicts" = 0). In a
merge scenario, a simple insert (DB insert) with option "Accept Duplicate Keys" would suffice to
ensure completeness of this customizing object in the “target”.

14
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Possible settings of field “1:1” (please also check the detailed F1-Help in German or English):
• ‘=’ Table completely identical
• ‘+’ Delta only on target side
• ‘-’ Entries - though no conflicts - existing in at least one secondary system but
not in the primary system
New (New keys / participants)
This field is only of relevance once a table got compared for a second time. If the result of the
new comparison was to show new keys appearing, then this field will contain the icon .

PiV (Primary table in at least one maintenance View):

If the field is checked, the object is a primary table in at least one maintenance view.

IC (Inactive Components):
In case the “Hide data of inactive components” checkbox (on the MCDelta start screen in the
“Filter for Display and Export Status/Notes” section) has been flagged this column is displayed
on the results screen. If the field is checked this indicates that the corresponding component is
not used in at least one of the logical systems.

Component:
Name of the application component to which the customizing table belongs. The specific short
component ID can also be added via ALV layout settings.

Cl (Client Independent):
If this field is checked, the table is client independent.

DC (Delivery Class):
Specifies the delivery class as found in the Data Dictionary:
▪ C, E and G Customizing
▪ A Master data
▪ S and W Repository

TT (Text Table):
If checked (value ‘X’), then the table is a text table. Click on the empty field of a non-text table to
enable the text-inline feature: if a non-text table does own a text table, the value ‘D’ will be set
and when displaying the actual table data, the text from the text table will be added to the table
structure automatically. This feature is already activated by default. To not display text inline,
click on the value ‘D’ to remove it.

UC (Usage Check in Master / Transaction Data):

If marked, the customizing table has been crosschecked with master / transaction data. For
more details on this, see chapter 5.

LR% (System with Lowest Ratio in %):

This field shows the lowest of the utilization percentages among the systems if UC=X. By
clicking on the value, you can see the usage per system in percentage (see chapter 2.5).

15
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.4) Data drill-down

Fig. 10: How to access different views from the comparison results screen

1) Select a row and click on the “Conflicts” button to display the count of conflicts for each
object field. In this example, several fields contain differences (see column “Count”). Double
clicking on a specific field lets you jump to the corresponding data rows of the tables directly.
2) By pressing the “Alternative display” button , all values / data per object will be displayed
at first level - listed by systems compared. This is like the output of transaction SCU0. If you
marked “SCU0” as standard in your user settings, then this button will show the classical
MCDelta key view instead (detailed data on second level only).
3) If the local system (the system running MCDelta) is part of the comparison, you can access
additional views per object. Button lets you access the customizing maintenance
view and by pressing the button, you can access the IMG (SPRO). You should select
a table first.
4) With the button , you can start a new comparison run per object. For details, see chapter
2.7. Please note: this feature might not have been activated yet by the project lead (see
details in chapter 4.1.1).
5) This functionality is not part of the adoption service.
6) Suggest mapping via the “Mapping Factory” functionality (please see chapter 3.2).

Please note: You must be the processor of the respective object to be able to suggest / create
mapping. Use the menu button to change the processor or click the field “Processor” directly.

7) Select the button to simulate the comparison for a different combination of system clients.
For example: you’d like to see the number of conflicts and unique entries only between two
out of five source clients. The result will be displayed but not saved.
Additionally, a filter can be applied based on the organizational unit relationships. For each
system client, you can specify the type of filter and the specific values (figure 10b). The filter is
either based on company codes or plants. The filter specified is a base filter only, which
means it is not required that the table itself contains the key company code or plant. For the
16
SAP MCDELTA, VERSION 9.0 - USER GUIDE

filter to work, the table only needs an org. unit in its key which can be derived from the filter.
Example: the table T014 shows the credit control areas. By specifying a company code filter,
only those credit control areas will be compared which have a relationship with these company
codes. You do not have to specify the field T014-KKBER or the KKBER values, this
information will be derived automatically. Naturally, next to the org. filter you can still use the
standard filter and mapping features as described in chapter 3.

Fig. 10b: Compare table in simulation mode; apply org. unit filter

8) It is possible to conduct the following activities for the selected object(s):

• Change status
• Change processor
• Assign solution

9) You can apply a filter on the key fields of a table to limit the amount of result data shown.
Starting MCDelta, the filter is off by default. Press to activate the filter. Next time
you click on an object / table, a new popup will appear (figure 10c) where you can enter your
filter specification or select an existing one (double click on a filter name in the list below). This
specification can be saved for later use (use “Save and apply filter” instead of just “Apply
filter”) and be applied on this and other tables with the same key fields.
If you do not want to use the filter anymore, click again on the button to deactivate it. The
button text “Filter on” will change back to “Filter off”.

17
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Fig. 10c: Apply filter on table keys to limit amount of data to be displayed

10) By pressing the refresh button , you can update the customizing results e.g. after re-
comparing a table.

18
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.4.1) Display customizing entries per object

This functionality allows you to display the actual customizing entries per single object. To do this, click
on the hot spot of the first column or double-click on the row of a specific object. In the standard
setting, the data is shown using the classical MCDelta 2-level display. At the end of this chapter we will
see how to show all data in one screen directly (2.4.3).
The figures below show the first level data screen listing the customizing keys of an object. The text
boxes will help you to understand the output. Important to understand is the role of the version number
(green columns in figure 11a), which states if a customizing key exist in a particular system and
whether its attributes vary from the entries of other systems.

Fig. 11a: Overview on customizing keys: version number explained

Fig. 11b: Overview on single object and its database keys in the compared systems

1) With the Notes function, project team members can maintain notes per object that are then also
accessible from the analysis overview screen.
2) From this screen, you can access a detailed view per object. Click on the value in the first key
column to display the complete customizing entry (see chapter 2.4.2).

19
SAP MCDELTA, VERSION 9.0 - USER GUIDE

In the case that a mapping was applied on at least one of the key fields of the table, the screen will
look a bit different (figure 12a). There will be new columns for each system showing where a key value
resulted from mapping and did not exist this way in the original system. This helps you to keep an
overview on any mapping effects (later, when the mapping function gets explained in more detail, we
will create a mapping for table T003 holding document types. There the key BLART=’DG’ of system
810 gets mapped to the value ‘DX’, exactly as you can see it in figure 12a).

Fig. 12a: Doc. type DG from system 810 gets mapped “away” to the new type DX

Please note: If a mapping was applied to a table, the protocol column “Action” in the table
overview will show the icon .

If new entries (new keys) appear because of a consecutive run, the icon will be shown in the
overview screen. Additionally, in the 1st level data screen each new entry will be marked by setting a
corresponding icon in the first column “Status”. Using two different icons, it will be distinguished
between a completely new key (in our example company code 1002) and a new participant (0001). In
the second case, the company code 0001 already existed for target system BC4 in the first run, but a
company code with the same key was created in system 802 only afterwards. It then got added
because of the second run.

Fig. 12b: Appearance of new keys gets visualized by the status icon
20
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.4.2) Detailed view per object key

To have a detailed view on a customizing entry with all attributes for each system, click on the
respective key in the first level data screen.
The graphic below (figure 12c) shows the second level data screen with all the attributes. Differences
are highlighted:
• The first example (material type) shows – among others – a conflict for the field “FLREF”
which has different definitions for the compared systems. This might lead to a different
process behavior for materials.
How conflicts can be classified is described in more detail in chapter 2.6.
• The second example (factory calendar definition) shows differences in three fields which are
not of relevance. This user change info is not categorized or counted as conflict.

Fig. 12c: Details: customizing attributes

21
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.4.3) Show it “SCU0”-style: all data in one screen

If you have not already made it your standard (user settings), use button to access an alternative
display showing all key and attributes together. The look is similar to transaction SCU0.

Fig. 13a: Alternative display showing all data together

Figure 13a shows an example for the sales organization. The first
column indicates the system of origin. The data is organized in
blocks of the same customizing key. The color of the first row of
one block is either yellow (key exists in the primary system client)
or green (key does not exist in the Primary). Conflicting fields are
colored red. For any attribute field related to a check table you
can see its definition by double clicking into that field (figure 13b).
For example, clicking into column “CoCd” in the third row, would
show the definition of the company code “0001” as defined in
system “810”!
F
Fig. 13b: Check table attributes

If the flag “Show counter for usage check” is checked in the user settings, then you will find the usage
count of the particular key and system in a column attached at the end of the result list. This gives you
an immediate overview on the importance of the customizing values. If you click on a number, the view
changes to the full list of the usage data of this object. From there you can even jump into a remote
system (SE16-style) showing you the full data lines of the corresponding master or transaction tables.
This will be explained in more detail in the chapter on usage check.
Any customizing object which is directly or indirectly connected to the company code will show the
button in the menu bar. Press the button to open a new screen showing a bar chart based on
countries (figure 13c). This chart quickly shows how intensely a customizing object is used by the
countries. This can help in where to focus on in the harmonization. The default is as if you had clicked
on column “SOrg.”: counting the number of different sales org. per country. Click on any other column
to show the usage of this attribute. For example, click on column “Currency” to see how many different
currencies are used per country in relation to sales organizations.

22
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Fig. 13c: Grouping data by country if related to an organizational unit

2.4.4) Data categories and how to access directly

Depending on your task, you might want to check only certain aspects of a customizing object. For
example, which entries are missing in the Primary or how many conflicts are there just between the
secondaries? To help you to get faster to the data you need, MCDelta groups the result sets into
different categories. The first two we have already seen in one of the earlier screen shots. Click on the
object name to see all entries and click on just the number in the “Conflicts” column to see only keys
with conflicting attributes (figure 13d). Clicking on the conflicts number replaces the toggle button
used in earlier releases.

Fig. 13d: The two main data categories: “All” and “conflicts only”

Press button to open the layout selection popup. There you will find all the other categories in the
section “Hidden Columns” (figure 13e). Add them to your layout temporarily or permanently by creating
a global layout for all users. Select the categories of your interest, move them into the section
“Displayed Columns” and confirm. Now you will see additional columns (figure 13f). If you click right
into a column, you will see the data of that category only. The display mode (“SCU0” or classical) is
based on your user settings. Use the right mouse button to switch to the alternative display. It is the
last option in the mouse context menu.
Click into different categories and check the data to familiarize yourself with this concept. Using the
classical view, it might be easier to understand, because it shows more transparently which system
does have data for this key and which not.

23
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Fig. 13e: Add more result categories to your screen layout

Fig. 13f: Result overview showing all data categories. Hover with the mouse over the column label to
see the long text descriptions

2.4.5) Print / export object result

The data lists / grids offer the standard print and export functions with which you can output all the
results. But these functions do not support an editable export of the colored “SCU0”-style results in all
releases. Additionally, you cannot export several objects at a time but would have to enter each single
object and display the result before exporting.
Therefore, MCDelta offers an inbuilt method to create XML files which you then can open with a
spread sheet editor (e.g. MS Excel). Please save the data then again using the editor’s own /
proprietary format because non-compressed XML data usually gets too large to send or archive. For
example, a 10,000-lines result can reach 300MB in size but shrinks to about 6-8MB when saved again
using a suitable file type.
To export an object, mark the corresponding line in the table list and press the key combination
String-Shift-F12. You can select more than one line to export several objects. A popup will ask for a
directory in which the file(s) will be saved. Flag the field “Conflicts only” for only exporting the data
showing conflicts in the attributes.
The popup which shows the list of the conflicts per field ( in figure 10), also features a print
button. Select the line with the field you are interested in and press the print button. Only lines which
show a conflict in the field selected will be exported.

24
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.5) Table statistics

Click on the value in the column “Total” to open a popup showing additional statistics. In the list
displayed, the first column states for each system the number of table rows (unique keys) in the
database. The second column “Selected” tells you how many entries have been used for the
comparison. The number can be smaller than the total in case that either user filters or the usage
check had been applied. Only the selected keys are shown in the MCDelta display. The others are
treated as if non-existing!
The other columns show statistics about the relation between a Secondary and either the Primary
or the other Secondaries. For example, how many keys exist in one logical system only or how many
entries have differences compared to the Primary? Check for more details in figure 14 or use the F1-
Help in the column of interest.

Fig. 14: Example for system statistics

25
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.6) Interpretation of customizing analysis results

The following four groups are used to classify the identified differences. The descriptions and
screenshots below show a comparison of two systems (BB5 and BB3) only, instead of the 3-system
comparison example we normally use in this document:

Identical Customizing (2 levels):

“Identical” means that either a single customizing table exists in both systems and has identical
content (same number of rows with identical values) or the same table key (in the example below
EKGRP=001) exists in both systems with identical attributes:

Delta Customizing:
“Delta” means that a specific customizing entry (key) exists in one of the two compared systems
only. In this example, only system BB3 does own a purchase group 851:

Depending on which system is affected, you can further differentiate between the following two
types of delta customizing:
• “Delta in source”: Delta object exists in the source system only
• “Delta in target”: Delta object exists in the target system only

Conflicting Customizing:
A customizing entry (represented by its key) for movement type 652 exists in both systems but is
not identical. If it is the same movement type (from a business perspective) then you need to
decide which system’s entry wins and align field “Debit/Credit”; if it is not the same movement type,
but just shares the same database key (BWART) by coincidence, then you have to solve the
conflict by applying an appropriate mapping on the key to allow for inserting the new entry from the
remote system (in a later migration of master and transaction data: wherever this movement type
occurs, it needs to be mapped to the same new value).

26
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Conflicting Exclusive Customizing:

If the client field (MANDT) is the only key field of a table, this means that only one setting per client
is possible and settings defined in one system must overrule the other one. An example for this is
the valuation level in logistics (plant or company code), residing in table TCURM. All these tables,
where the client field is the only key field, do have a central controlling functionality.

2.6.1 Conflict handling: Assign solutions on table level

In the overview list, you can assign one of the pre-defined solution categories. They describe how to
handle the identified issue. Two types of solution categories are available: transfer and merge. The
project lead can modify or add solutions. As you can also see in figure 15, a solution can be assigned
to not just one but several tables belonging to the same component with one click.

Fig. 15: How to assign solutions and comments per object / table

You can provide more information by using the notes function or comment field. Instead of attaching a
remark / note to an object, you can also send a message directly to the inbox of either the processor (if
not your object) or the responsible of the component e.g. to ask a question.
Examples of use: the processor assigns a solution and provides some insights and questions in the
notes. By sending a remark to the responsible person, the receiver will be notified (showing “New
messages” on the entry screen) and can read the message in the inbox and jump to the object by
following the link provided. Or, you want to ask a question about an object not belonging to yourself.
You can do so by sending a remark to the processor. See chapter 4.3 about the link back to the object
in the inbox message.

27
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.6.2 Conflict handling: Assign status / actions on key level

Depending on your needs, it might not be detailed enough to assign solutions or comments just on
object / table level. If a table cannot be transferred or distributed in a whole, you must be able to
assign information on table key level.
To accommodate for this, you can assign a status to a key record directly. Three predefined status
exist, but you can change the description texts in the project settings. Additionally, you can define so-
called activities and transfer modes. While the transfer mode is a one-character code and could be
useful in automated custom migration procedures (reading the result with an API), the activity is a text
description. You can either select an action from a list defined by your project lead or enter a free text
of a maximum of 15 characters. The texts in the example figure 15b are just for demonstration, there
are no predefined activity texts or transfer modes.

Figure 15b: Assign status / activities on key level

If you want to use the status icon to emulate a 2-man rule, you can restrict the right to change the
status to the main responsible assigned to the object. The project lead must set the flag “Only main
responsible allowed to change” in the section “Maintain other group and TID-independent
configuration” of the project settings. This way, the processor can assign an activity and only the
responsible can change the status to “Completed” (or another description if redefined by the project
lead). Naturally, the fields activity and transfer mode cannot be changed anymore once the status is
set to “Completed”. The status would need to be changed first.

28
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.7) Running a new comparison

Before you start working, a project member will already have compared the whole set of relevant
customizing and master data tables (around 200 tables) using EasySetup. The MCDelta cockpit just
shows the results and is not suited for this kind of mass-processing. Nevertheless – because of
changes in the remote systems over time in the component you are interested in or because you have
created a mapping and want to test it – it is possible to compare one or several tables again right from
your MCDelta overview screen.
Additionally, later in this chapter we will see how to add maintenance views for a table for
comparison or how to check only the changes which occurred after a date specified (only if table is
logged).

Fig. 16: How to repeat comparisons

From the overview screen, you can repeat comparisons. Select one or more objects and press the
button . If you select more than one object, a popup (1) appears showing the objects. In this screen
the released objects are on the left side. Objects assigned to another processor appear in the
exclusion list on the right side. To release them you will need to assign them to yourself (which would
trigger a message to the original owner of the object).
After you have confirmed the selection, another pop-up screen appears (2). Here you have different
options:
▪ Convert data (apply mapping maintained in MCDelta)
▪ Compare original data without conversion
▪ Filter data (apply filters maintained in MCDelta)
▪ Compare full data
▪ Compare with local data copies of remote systems (unconverted and unfiltered remote data
will always be stored redundantly in the local system to allow for uninterrupted work in
MCDelta)
▪ Compare with current data of remote systems (remote function call (RFC) must be in place!)

29
SAP MCDELTA, VERSION 9.0 - USER GUIDE

In addition, you can select to perform the comparison as background job (if your system profile
permits) and suppress the popups per table showing the list of mappings. Please consult the F1-Help
for further information on the latter. If you want to see all data and therefore bypass the usage check,
check the box “Suppress master / transaction data filter”.
If the flags “Convert data” and “Filter data” are checked, you will see the following screen offering
available mappings and filters:

Fig. 17: Selection of mapping and filters

The example in figure 17 shows table T003 ready for comparison. MCDelta proposes mappings for the
fields BLART and STBLA which are both based on the domain BLART. The corresponding mapping
(column “Map-ID” = BLART) for this domain will be offered automatically, because this mapping was
created earlier (see chapter 3.1) with reference T003-BLART (see columns “Table” and “Field Name”).
Therefore, the system automatically activates the mapping for field BLART by preselecting the row in
the table control. This is further expressed by showing the “Header” icon. If the table contains more
fields of this domain or domains of other reference tables, the conversion will be proposed accordingly
(see icon “New proposal”) but not preselected (field STBLA). If you want to make use of a certain
additional conversion, select the corresponding entry in the table control.

Please note: The table control column “Table” in figure 17 does not hold the name of the table to
be re-compared but the reference table on which the mapping ID was created. In our example it
happens to be the same table.

If you did not choose the filter or mapping option in the earlier popup, selecting mappings or filters
here (if existing) will have no effect.
You might have noticed, that the table columns “1st Add.”, “2nd Add.” and “3d Add.” are open for
change. Applying the mapping for its own reference table will have the right additional fields by default,
naturally. But when using a mapping for another table, MCDelta might not automatically find the right
additional fields, especially if the corresponding domains appear more than once. In this case, check
the table definition and enter the correct field names. If you do not have suitable fields in your table,
then you cannot apply that mapping. For our example here it does not matter, because BLART is only
of type 1:1 mapping (further right in the tab control you’ll see another display-only field “1st Add.”,
which is empty. Only if this or the next two fields were filled, you would need to have data in the
“Add.”-Fields open for entry).
30
SAP MCDELTA, VERSION 9.0 - USER GUIDE

MCDelta saves your final selection and will propose it for the next comparison run with already
preselected lines (see icon “Mapping was already used”). Use the “Suppress” option to skip these
popups in later runs and just use the preselected lines. If values are missing in the mapping database
for whatever reason, you will find a warning in the protocol (hotspot click in column “Action”; figure 18).

Fig. 18: Protocol warnings

Please note: If the table key gets converted, then please also add the corresponding text table to
the comparison. Otherwise the text-inline feature will not work correctly.

2.7.1) Add maintenance view object

As you noticed, the tables shown in MCDelta are the basis customizing tables. There is table T003
defining the document types, T003T showing the texts and other tables adding more attributes to the
object. This is different to the IMG view where you start – depending on your business task – with a
maintenance view showing all the data you need in one place.
Use the button to add the maintenance view you are interested in. Select the corresponding
basis table (the ones flagged in column “PiV”) and start the comparison. You cannot select more than
one entry this time. The next popup will show an additional button “Viewbased comparison” (see figure
19). After pressing the button, MCDelta shows a list of available views from which you can select your
favorite. You can either start the comparison immediately or just create the object. Back in the
overview screen you must refresh first to see the new object. If you do not see the object, then you
might not have set the option “Objects without conflicts” in the start screen. Adding an object will
automatically populate the column “Processor” with your user name.
Alternatively, if you have problems to identify the correct maintenance view, you can also go by the
IMG to create a new object. Press to see a popup list with all the related customizing activities.
Double-click an item and select “Add new obj” in the following popup. Don’t forget to refresh the object
list.

31
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Fig. 19: Create and run comparison of maintenance view

Please note: To run the object for the first time the RFC(s) must be in place and working. You
must select the option “Compare with current data of remote systems”!

2.7.2) Check for changes after a certain date

MCDelta stores all original table data in the local system client where you work. This makes you
independent of the availability of remote connections (RFC) and lets you access the data a lot faster.
Customizing does not change that frequently, so this is a good trade off. Still, after a few months of
working with your data and maybe shortly before go-live you might want to see if your object has
changes. You could just repeat the comparison as you learned before and see all the data, the non-
changed and the changed. Or, to quickly just see the latest changes, you can make use of the
database logging which is in place for many customizing tables. Use again the re-comparison function
and press the button . Then specify a date (like the last comparison run) and execute. Now, you
should only see the keys which were either newly created or had their attributes changed after that
date.
To avoid confusion, this kind of comparison does not use the original table overwriting its results
but adds a new object showing the date in the object name. See figure 20 for the steps to follow. If a
table is not logged, then you will not see the button for adding the object. The feature is simply not
available then.
Independent of the occurrence of changes, there will be a new object in the overview screen. If the
column “Total” does not show a value, then your original object is still up-to-date. You can use the new
object to run again with a different date. The original table will not show the button anymore.

32
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Fig. 20: Check changes based on database logging

2.7.3) Compare DDIC structure of master data table – Check customer fields

For various reasons it is useful to know, if the DDIC structures of relevant master or transaction data
tables differ, customer fields exist and what their value range is. MCDelta has a small, inbuilt feature
which combines basic features of a repository comparison with data scans.
For example, you want to check if the materials table MARA does have fields with the same name
but different technical definition across the source systems or which of the systems have customer
fields (Y* or Z*). It is also of interest to see if these fields are filled at all.
Go to the start screen of MCDelta and press button . In the next screen create an object (1) for
the table(s) in question, refresh (2) and start the run (3). Because we are also checking the content of
the table which
can be very large,
you will need an
extended authorization to create and run the object (role template SAP_MCT_MCDELTA_TAAN is
needed, unless you already own the project or subproject lead role).
Click on the object name to look at the field differences. The display is the same as it is used in the
customizing comparison. Therefore, we will not go deeper into this here. Click the hotspot in column
“UC” to see the values of the customer fields (if existing). If the column shows the value “R” then the
data scan is still running in at least one of the source systems.

Please note: The data scan on the customer fields inherits the MCDelta filters on fiscal year or
org. unit automatically if available. This means that – for example – table BKPF would only count and
show the content which belongs to the fiscal year range and company code set specified! It works the
same way as in the master data usage scan.

33
SAP MCDELTA, VERSION 9.0 - USER GUIDE

2.8) Distribution of customizing

Please note: This functionality is not available to customers as part of the cFin adoption service.
Support is restricted to projects where trained SAP consulting is directly involved.

34
SAP MCDELTA, VERSION 9.0 - USER GUIDE

3.) MAPPING AND FILTER

Transferring data into a new system means that some attributes need to be converted to make them fit
with the new environment. There can be technical or business reasons. Alternatively, a filter prevents
data from being transferred, which is deemed obsolete. In general, there are two ways of working with
mapping in MCDelta:
▪ Create mappings via the integrated mapping functionality (chapter 3.1)
▪ Import mapping from external source (chapter 3.2)

Principally, all the functions described for mapping are the same for the filter functionality. Therefore,
chapter 3.5 holds a short description only, which lists the few differences.

3.1) Create mappings via the integrated mapping functionality

From the list of customizing tables, you can choose an object and create suitable mapping to align the
corresponding customizing entries coming from the different systems.

Fig. 24: Integrated mapping functionality in MCDelta

The first step is to select the relevant object and to enter the first level data screen with the key values.
Select a line and press the “Create Mapping” button , or go to the second level data screen and
press the button directly. A popup will open to guide you (see figure 24). If no mapping for this object
had been created yet, you will now need to define the mapping ID and its definition. Select the option
“Create new” and continue. If the mapping already exists, the first popup will show the mapping ID with
the radio button already selected and the flag “Created here” being true (other mapping IDs might

35
SAP MCDELTA, VERSION 9.0 - USER GUIDE

appear if the current object shares the same data elements with them. This way, you can enter new
mapping values even if you are not in the leading object. The flag “Created here” remains empty. But
you should never create a mapping ID from another object which is not the primary table!).

Attention: Field mapping MUST be created with reference to the leading table of the customizing
object. By doing so, other related tables, which contain the same field, can automatically find and use
the mapping that was created for the specific field (e.g. when carrying out a new comparison run).
Example: create the mapping for company codes by referencing table T001 and not any other table
showing company codes! For quality governance reasons, MCDelta does not allow using integrated
mapping without a reference.
The second popup appears only if you are going to create a new mapping ID. Specify the ID
(maximum 12 characters), a description and the fields used for the mapping.

Please note: The field labeled “Field” needs to hold the main field. Example: you want to map the
plant (WERKS) dependent object “Storage Location (LGORT)” in table T001L. The plant is part of the
DB key in T001L (the first key even) but not the leading object (that would be for T001W). Therefore,
the field name ‘LGORT’ will be placed in “Field” and the name of the plant field ‘WERKS’ in field “First
Dependent”. The other fields would remain empty.

Now continue to the last popup where you can add the mapping values. The source value cannot be
changed. You can only enter the target values (in figure 24 example value KX got entered). This will
minimize typing errors. If you need to add mapping for non-existing source values, then wait for
chapter 3.2. Use the flag located behind the system names to enforce a blank target value.
After the mapping ID had been created for a specific table the mapping icon is shown on the results
overview screen (see figure 25). By clicking on the mapping icon, you can access the maintained
mapping for this table. By clicking the change documents icon , you can see all the changes that
have been performed for this specific mapping.

Fig. 25: Change log per single reference table / mapping ID

36
SAP MCDELTA, VERSION 9.0 - USER GUIDE

3.2) Central mapping creation

Instead of creating mapping from within the reference table’s results entry by entry, you can do this in
bulk in the central mapping workbench. Access it by clicking on the corresponding menu button in
the MCDelta start screen:

In the following popup (figure 26), you will find a table control either being empty (first time) or showing
the mappings both created here or the integrated way (3.1). Create a mapping ID (use the button
showing the blank page) and assign a reference table. After confirming your choice, enter the mapping
fields in the next screen (the flag “Field search by data element” should only be used exceptionally,
please check the F1-documentation and check with an SAP consultant). Save and get back to the first
table control that will now show the new mapping ID and its specification. Please note: the button
“Self-define mapping structure” is an expert function and should be used by SAP experts only.

Figure 26: How to create a mapping ID

The conversion process can also make use of pattern-based mapping (e.g. A+++ or D*) or numerical
offsets. Please consult the F1-documentation of field “Method Type” for examples. For standard
mapping you should use the default type “F” (or blank) which uses fixed value lists. Please keep in
mind that conversion or migration engines ultimately using this mapping might not support patterns.
Select a mapping ID and click on the button to open a new window for editing mapping (figure
27). Here you can change or add new mappings by inserting new rows. You must enter a name (e.g.
802) in the “Name” field to identify for which system the mapping applies. By pressing , the column
labeled “SCID” will be updated with the corresponding SCID number. The SCID field is not open for

37
SAP MCDELTA, VERSION 9.0 - USER GUIDE

editing to avoid confusion. Pressing the save button will also result in a correct population of the SCID
fields.

Fig. 27: Central mapping in edit mode

You can also store mappings that were created outside of MCDelta (e.g. cost centers or material
numbers). For this, select an existing mapping ID and press the upload function ( ). The button to
the right of the upload buttons will show information on the column specification of the upload file. The
format required is tabulator-separated columns.

Please note: Making use of the button will delete both the selected mapping ID and its data.
The data cannot be recovered. Only the project lead owns the right to delete a mapping ID (unless all
project members work with SAP_ALL).

Use the function “Edit ID” (button ) to change the definition of an existing mapping ID. You may
change the description or add additional fields which you forgot to specify when creating the ID.
Please keep in mind that changing the field definition will trigger the activation of a new mapping
structure. You must verify that already existing data is aligned. An existing conversion exit can be
switched off or a simple Alpha conversion can be activated. As this can have serious consequences
on the maintenance of mapping data, please discuss with your SAP consultant. Changing these
settings should be a rare case!

Using mappings for subsequent project steps:

A major advantage of this mapping functionality is the option to integrate the mapping entries
maintained here directly into the migration tools used by the SAP project team. Creating synergies,
time-consuming and error-prone spread sheet-based data entry can be avoided this way.

38
SAP MCDELTA, VERSION 9.0 - USER GUIDE

3.3) MapFactory
How to access the mapping factory
Starting from the overview screen you can suggest / create suitable mappings via MapFactory. The
mapping factory does have some functions to assist you in finding the connection between
customizing entries with the same meaning in different systems but with different data base keys.

Fig. 28: How to access the mapping factory

As described in the figure above, the first step is to select the relevant object. In the subsequent
screen, you can select from four options:
• Using text similarity: an algorithm uses the corresponding text tables to create probability measures
• Using matching fields: specify the fields which can establish a connection when matching 1:1
• Combine text similarity and matching fields
• Without similarity check: simply display all data rows and group them yourself by drag & drop
Option 1 will ask (popup) for the name of the text field(s) and the language to be used. This option will
also allow you to work with different languages on the same object: e.g. the first project member
creates some mapping suggestions based in English and other project members later enrich the
mapping using e.g. Spanish or French (the processor assignment needs to be changed).
If using the text similarity check on larger tables (e.g. vendors), you must check the box labeled
“Use background processing”. Text string operations are very computing intense and running in
foreground would result in a short dump because of exceeding the maximum allowed runtime.
Naturally, you will return to the main screen and need to check periodically if your result is available.

39
SAP MCDELTA, VERSION 9.0 - USER GUIDE

There is also the option to exclude systems from the matching process. For example, you only want to
match the sources because the target does only hold “play data”. Results are saved per system
combination and language.
Principally, the matching of similar text does operate on the text field of a corresponding text table:
field T003T-LTEXT would be proposed for the document types in T003. If the main table does contain
other text-like fields, you can add up to two of them (figure 28b). The matching algorithm operates then
on a concatenation of these fields. If a table does not have a text table, then the system proposes a
suitable field from the main table. For the company codes in T001 this would be T001-BUTXT. If the
value lists in the popup are empty, then no suitable field exists.
If you choose the option to match fields 1:1, you will find that you can match up to nine fields. For
each of them additional options can be defined. In the example in figure 28b two fields are used:
“KOARS” and “STBLA”. Content of field “KOARS” must be identical, otherwise the two document
types in question will not match. Content of field “STBLA” on the other hand does not need to be the
same because the option “Deduct only” is flagged. But the measured probability will be lowered by a
certain percentage. Additionally, because the field “Joker=blank” is set to true, any source value in
field “STBLA” will match with an initial target value.
Not used in this example is option “Joker”. The value in this field allows that any source value
matches with the target value specified in “Joker”. For example, let’s look at the field tax category in
table SKB1: if “Joker” = ‘*’, then target value ‘*’ in field “MWSKZ” would match with any source value,
but other values like ‘<, >, +, -’ would require the identical value in the source.

Fig. 28b: Additional features for the options text similarity and 1:1-matching

40
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Overview: Main screen of the mapping factory

The main screen is divided into different sections. You always find all customizing entries of the
primary system in the upper section labeled “Mapping confirmed”. This is because these values serve
as a mapping “reference” (new value). This implies that MCDelta expects the Primary to be the target
of a merge or transfer scenario.

Fig. 29: The mapping factory – overview

1) Menu
- Use button to remove selected entries from the list labeled ”Mapping confirmed“ (and move
into the list “Open items” ).
- Use button to remove all entries with a matching probability (third column “Degree”) less
than the percentage specified (popup).
- Use button to remove all entries except for the one with the highest probability.
- Use button to create mapping for all objects listed in the section “Mapping
confirmed“ (data will be stored in the mapping workbench described before).
- Use button to rearrange the position of the sections in the mapping factory.
- Press the save button to leave the MapFactory without losing the data changes in the “Mapping
confirmed” and “Open items” lists.

2) “Mapping confirmed” window

In this window, all suggested mapping is displayed. The initial state of this list depends on which of
the options was chosen before the mapping factory was accessed the first time. This section
contains at minimum a list with all the values of the primary environment. Primary values reside in
this section only; you cannot move them to the open items section! If you are working with option 1,
2 or 3, some of the secondary values might already appear in this window assigned to its
respective target value. If you have chosen option 4 and enter the first time, this window can only
contain the values of the Primary (BC4 in our example).
41
SAP MCDELTA, VERSION 9.0 - USER GUIDE

3) “Open items” window

In this list, all remaining items are listed for which no suggested mapping exists (option 1 and 2).
You can select open items and add them to the “Mapping confirmed” list via drag & drop.

4) Create mapping ID or show mapping as stored in mapping engine (chapter 3.1 and 3.2)
By double-clicking on this section (picture) this third window changes:
• In case, mapping had already been created for this specific object, the mapping is displayed
here.
• In case no mapping has been created for the specific object, a new window opens where you
can create a new mapping ID and define mapping details (see chapter 3.1 for details).

Working with the mapping factory

The graphic below shows in more detail how to work with the mapping factory:

Fig. 30: How to work with the mapping factory

In the section “Mapping confirmed” all values of the primary system (SCID=01) appear in yellow
colored rows. These rows cannot move elsewhere. They serve as the target reference. Non-yellow
rows in-between are always entries from secondary systems (SCID>01) and are either pre-assigned
by the probability / matching algorithm or assigned manually (drag & drop). For removing secondary
entries (not possible with primary values!), use either drag & drop the other way (back into the “Open
items”) or mark the row and press the first button in the menu. If already mapping exists, you can drag
& drop single mapping groups from here (just select the primary value) into the mapping zone on the
right. Keep in mind, that this drag & drop operation will commit values in the mapping database. The
“Save” button has no function for the active mapping on the right!
The section “Open items” is the main window from where you can move data rows or assign them
a different status (color, 4). Rows can be dragged both into the “Mapping confirmed” list (2) and into
the final mapping list on the right (3).
42
SAP MCDELTA, VERSION 9.0 - USER GUIDE

1) Create or show mapping section

This section appears when double-clicking on the MapFactory picture on the start screen (actual
values only appear in case mapping had been created already, naturally). If no mapping ID is yet
connected to the leading table, you can now create a mapping ID using the current table as the
reference table.

2) Add open items to the “Mapping confirmed” list

Per drag & drop you can select open items in this list and add them to the “Mapping confirmed” list.
If you dropped in onto the wrong target row, instead of removing and dragging it again, you can
drag it right there in the “Mapping confirmed” window from one section to another. Therefore, you
can have several source values from the same system connected to the same target value. This
can also be saved (in the mapping factory, not the mapping database). Keep in mind, the “Mapping
confirmed” window is not a final mapping and can be used for “playing around”.

3) Define target values for single items

Per drag & drop into the right section, you can define target values for single open items. After a
value has been entered this way, the respective row in the section “Open items“ turns green. A
valid mapping ID must already exist!

4) Mark items as not relevant

You can mark (color) single items as “Not relevant“ to show your progress. To undo, choose
“Remove color“.

Please note: The save button has no effect on the actual, active mapping data on the right side of
the main window (double click on picture). It only saves the assignments between source values and
target values in the other two windows. These assignments do not constitute actual mapping, just
suggested mapping! To make these assignments real mapping, you must either drag data into the
right side of the window or use the “Create mapping” button. These two actions work like a save button
in respect to the data in the mapping engine! Once done, the mapping is changed and visible to all
other project members! If the action shows a popup saying that the same source value maps to
several target values the whole action aborts (impossible situation to solve for a migration engine).
Using “Create mapping” might overwrite your existing mapping (it should rather be used for an initial
creation of mapping, not for continuous change)!

43
SAP MCDELTA, VERSION 9.0 - USER GUIDE

3.4) Filter – Differences to mapping engine

As mentioned already, the procedures for how to create and apply filters are like the ones for mapping.
Therefore, this chapter will only list the differences. There is no equivalent to the MapFactory for filters.

When creating a filter ID, there are some additional definitions as shown on the following figure:

Fig. 31: Creating filter ID

There are two types of filter: Include and Exclude. Leaving the field “Include/Exclude” blank or typing
‘I’, the filter will let all values pass which are listed for this filter ID. Setting the value ‘E’ will block
exactly those values from the filter list. Normally, leaving the field blank should be the standard.
The field “Method Type” should be left empty. This will make MCDelta use the standard filter
method: an incoming value will be checked against a fixed list of filter values. Patterns (*, +) saved in
the filter will not be recognized when re-comparing the table and treated like a fixed value. If you want
to use patterns, please check with your SAP consultant. Technically, MCDelta can handle patterns but
some migration engines do not, so patterns should be used only exceptionally.

44
SAP MCDELTA, VERSION 9.0 - USER GUIDE

4.) PROJECT: SETTING IT UP AND MONITOR

4.1) Project menu

Select the menu item on the start screen to access the project maintenance menu for the
following roles (depending on assigned authorizations):
▪ Project lead
▪ Subproject lead
The first screen of the project maintenance menu always shows the data of the specific TID entered
on the start screen only, not the data of the whole group to which the TID has been assigned. The TID
and group information is shown on the right side of the project maintenance menu. If both values are
given, the shown data is TID dependent. If only the group is shown, then changes can be made which
affect all TIDs of that specific group.

Difference between TID and Group:

The TID refers to a specific task (e.g. compare all client depending customizing in logistics) during a
project while a group can contain of two or more TIDs. Within a group the project lead can specify and
/ or change settings which automatically apply to all TIDs belonging to the specific group (e.g. define
solutions, allow / forbid new comparisons for single tables, share mapping etc.). Task IDs of one group
also share the same mapping and filters you create in MCDelta.
In the following section the main functions of both roles within the project maintenance menus as
well as available settings are described.

4.1.1) Role “Project Lead”

Fig. 33: Project maintenance screen for role “project lead”

The project screen (figure 33) gives you an overview on the project lead relevant information and
contains of two areas – the menu and the information section .

45
SAP MCDELTA, VERSION 9.0 - USER GUIDE

The menu:

Stats:
Display additional columns in the information section providing information about the status
(Conflicts, Waiting, In Process, Done) of components assigned to project team members. The
column “Still open” sums up the conflicts for tables which have not been set to status ‘Done’ yet.

Main Resp.:
Create messages and send them to all main responsible.
News:
Create news which will be displayed in the news section on the start screen.
All Status / Notes:
Upload status and notes information stored locally on your computer. Export / Download of status
and notes can be done via the button in the start screen menu.
Main Resp. only:
Upload assignments of main responsible for components via this button. This functionality enables
the project lead to separately define / change the main responsible without affecting other status
already maintained by the project members (to upload the main responsible the same file is used
as for the general up- and download functionality. However, in this case only the column
“Responsible” will be considered for the update).
Adm. Unit:
Within this menu the project lead can maintain specific administration settings. Major functionalities
are described below:

Fig. 34: Administrative unit menu

46
SAP MCDELTA, VERSION 9.0 - USER GUIDE

1) Solutions / Components / Distribution

• Solutions
Here you can define the solution tags for the classification of identified conflicts. The
solutions defined in this place will be shown as options in the solution column in the
comparison results screen.
• Components
Not of relevance in context of this adoption service.
• Distribution
Here you can maintain the RFC connection for distribution if the target for distribution is not
the local client. You can exclude satellite systems or the local client from exporting
customizing or protect the local client from being overwritten. If customizing distribution is to
be used, you must check the flag “Activate distribution” in this section!

Please note: Changes to distribution settings should only be done after briefing by SAP
consultants.
• Maintain IMG
Use this function to store an RFC connecting to the harmonization system client. Having
specified an RFC, you can directly jump to the IMG maintenance view (SPRO) when selecting
a table in the table overview screen and pressing the button . The corresponding RFC
user would need authorizations for transaction SPRO. Please note: all users having access to
MCDelta would be able to change data via SPRO using this feature.
• MDG mapping
If you want to pull mapping from the Master Data Governance mapping layer, then you can
specify here an RFC destination for a non-local installation. Currently, only the Central
Finance mapping layer in MDG is supported. You cannot generally pull mapping from MDG.

2) Check boxes for restrictions

With the first checkbox, you can allow / forbid all other project team members to create /
copy mapping IDs.
With the second checkbox, you can allow or forbid to carry out new comparisons of single
objects / tables. If this box is flagged, the project team members can run new comparisons
from the overview screen (table list).

3) Maintenance of group and roles

In this table, you can enter the user name of the project lead (must have the role “Project
Lead” assigned) which will enable this person to receive messages. If this assignment is
missing here, no messages can be sent using function “Message to Project Lead” ( ).
If the project lead is absent, you can assign the role “Project Lead” to another team member
and replace the current user name in this table with the new user name.

Please note: Since the upload functionality of status and responsibilities and the RFC
distribution settings relate to the project lead role, it is highly recommended to assign the
project lead role only to one project team member.

4) Settings for groups, TIDs and scenarios

Shows the list of all existing group IDs, TIDs and their solution categories. These settings are
defined already prior to harmonization start (by SAP technicians). Please keep in mind, that
mappings and filters can only be shared across task IDs if assigned to the same group
number.

47
SAP MCDELTA, VERSION 9.0 - USER GUIDE

Adapt RFC connections:

If the RFC destination of a source system changes then you can enter the new value here.
MCS<->MDG Business Sys.:
If you plan to pull mapping from the CFin-MDG (Central Finance using Master Data Governance)
mapping layer, you need to map here the MDG business name of the source system to the
MCDelta source ID. The MDG business name is the source identifier as used in the MDG mapping
data. If unsure, then go directly to the MDG mapping to check the names right in the data.
Maintain group / task-independent configuration:
Here you can maintain configuration which is globally active for all the Task IDs of the local client:
▪ Processor groups (Join single users into one group for easy multi-processor assignment)
▪ Activity texts (value list for column “Activity/Comment” for result data on key level)
▪ Transfer modus (value list for column “Transfer Modus” for result data on key level)
▪ Rename status names and/or restrict usage to subproject lead (also record/key level)

The information section:

Fig. 35: Information section on the Project Maintenance screen

Within this section all component relevant information for the specific TID is displayed. Press the
“Stats” button to see also the number of conflicts aggregated on component level.

Component:
By clicking on a specific component, you can access the comparison results screen of the
corresponding tables.

Main Responsible:
This column shows you the main responsible who is assigned to a specific component. You can
also assign and/or change main responsible here. Making a project member the main responsible
for a table (indirectly component) does not automatically make this member a (technically fully
authorized) subproject lead (still needs the subproject role assigned).

sMR (Several Main Responsible):

If this field is flagged, two or more main responsible are assigned to the specific component.

Due:
The symbol shows which components are overdue because of at least one object passing the
set due date. By clicking on the symbol, you jump to the corresponding objects / tables.

48
SAP MCDELTA, VERSION 9.0 - USER GUIDE

4.1.2) Role “Subproject Lead”

The view of the subproject role is limited to information related to the specific components the
subproject lead is assigned to (main responsible for a table or component). Therefore, a subproject
lead must own the role “Subproject” (use template SAP_MCT_MCDELTA_SUB) and ideally have tables /
components assigned as main responsible.

Fig. 36: Project maintenance screen for role “subproject lead”

The menu bar:

Stats:
With this button, you can display information about the status (Waiting, In Process, Done, Not set)
of components assigned.
Status / Notes Subproject:
Upload status and notes stored in files on your computer.
Team:
Create and send message to the team. The team is automatically defined by the following criteria:
Persons who are assigned to an object which is part of a component assigned to the subproject
lead (=main responsible).
Lead:
Create and send message to the project lead.
New Table:
Use to add a new object. When “Check if DDIC table” box is not flagged, any name
can be used (e.g. for representation purpose), otherwise it needs to be an existing SAP DB table.

Fig. 37: Adding tables in subproject menu

49
SAP MCDELTA, VERSION 9.0 - USER GUIDE

The information section:

In this section, all those components are listed to which the respective subproject user is assigned to
as main responsible. Information on the single columns:

Component:
By clicking on a specific component, you can list the corresponding objects / tables.

sMR (Several Main Responsible):

If this field is flagged, two or more main responsible are assigned to the specific component.

Due:
The symbol shows which components are overdue regarding the maintained due dates. By
clicking on the symbol, you access the corresponding comparison results.

50
SAP MCDELTA, VERSION 9.0 - USER GUIDE

4.2) Monitoring

Fig. 38: Project monitoring functionalities in MCDelta

Status fields: change directly by clicking on it

Status & Due Date:

In the object overview you can maintain a status and assign a processor (project member) on table
level. The change can be done by directly clicking into the corresponding field of the line belonging
to the table. Furthermore, you can assign a due date. Dates which are maintained here and are
due or overdue will appear in the project maintenance menu as a warning (see chapter 4.1).

Processor:
Most project teams will opt for assigning just one processor to a single object. Still, if working in
large teams on customizing with huge harmonization needs, you might want to assign the work not
based on tables but based on the type of result data. While one user processes the real conflicts,
others specialize on transferring the unique, collision-free entries. To be able to work on the same
object without locking each other out, MCDelta supports a multi-user concept. If processor A enters
the result based on a data category (here “Conflicts only”) instead of opening all, another user B
can enter the data category (“Only in secondaries, no conflicts”). Each area is separately locked for
data change, so both A and B can make their changes without interfering. If one user wants to
enter a category which is different but overlapping with another already locked category, a warning
message pops up and the data is protected against change.
In the popup for maintaining the processor, there are two extra buttons. The first button allows
to assign a processor group, which is predefined by the project lead in the project settings ( ). The
second button allows to individually add users directly. Group names start with ‘&’ to distinguish
them from normal users.

Main Responsible:
A main responsible (ideally equipped with the subproject lead role) can be assigned on table level,
too. While you can have more than one responsible per component, only one can be assigned to
one table directly. The assignment of responsible is needed if you opt for restricting the status
change of single result records.

Status fields: assign same value to multiple lines

If you want to assign the same status or processor to more than one object, then select the lines of
interest and press the corresponding button in the top button row.

51
SAP MCDELTA, VERSION 9.0 - USER GUIDE

4.3) Inbox

Fig. 39: Inbox

You can access the inbox via the menu bar on the start screen.

1) In the inbox all messages are displayed which are addressed to your user (processor / main
responsible). Three kinds of message exist:
▪ Technical Note
▪ Personal Note
▪ Reply
Except for technical notes, you can reply to the sender by using the right mouse-button.
2) Within this column, you can mark messages as read. Via the button, you can change the
view between messages already read and not read.
3) In this column, the object is displayed to which the message refers. By clicking on the object, you
jump to the corresponding results screen for the specific object.

Global messages from the project lead are displayed on the start screen (see fig. 2 in chapter 2.1).

52
SAP MCDELTA, VERSION 9.0 - USER GUIDE

5.) USAGE CHECK

5.1) Usage of customizing
MCDelta helps to assess the actual degree of utilization for the most important customizing objects. A
detailed knowledge about the usage of customizing entries in a company’s system landscape can help
to limit the complexity of harmonization. Before trying to solve a conflict, it should be checked whether
the customizing entries in question are maybe only rarely or not even used at all in production. Making
use of this knowledge will reduce the needed reconciliation efforts by the functional experts.
As part of the initial setup, background processes in all connected systems will scan various master
and transaction data tables. These scans log the key of a customizing object and count the number of
rows where it is found. The result is transferred to the system in which you work with MCDelta. Thus,
the utilization info from all systems is centrally stored and accessible. Based on this data you can
additionally check the (uncompressed) size of these tables to get an estimate for your sizing of an
initial load. To access this data use button in the entry screen.
To facilitate your work, MCDelta not only logs the usage counts but also blocks (filters) all
customizing keys from comparison which are not used at all. These entries with a count zero will not
be transferred from the source systems to the target. Figure 40 shows the effect of this technique. In
this real customer example, thirteen systems were compared. The standard company codes delivered
by SAP had not been deleted in the customer systems which resulted in many entries on the right side
of figure 40 considering the high number of source systems. On the left side of the figure instead, the
company codes which are not productively used were blocked from comparison so that only very few
codes need to be compared.

Fig. 40: Analysis of company codes showing effective application of the master / transaction data filter
in a real customer example

Attention: If a customizing table does hold more data in the source system than displayed in
MCDelta then please first check if this object is subject of the
usage check technique. The usage log is used as a filter blocking
all keys deemed “not used”. In the statistics you find the overall
number of source entries in column “Total”, in column “Selected”
the number of entries passing this filter. Only the latter are used
and displayed in the comparison!

53
SAP MCDELTA, VERSION 9.0 - USER GUIDE

5.2) Utilization statistics for customizing

When a customizing is scanned for usage then the column “UC” is flagged with value “X”. To access
the logs, click on the field to show the distribution and counts of the customizing keys among the
leading master and transaction data tables (figure 41). If the column field is empty, then the
customizing table was not cross checked for usage.
Please note: In some scenarios the column “UC” might hold the value “I”. In this case the object is
scanned for usage, too, but only for information purposes. This means that the logs are not used as a
filter blocking entries from comparison. The list of transaction data tables scanned is not
comprehensive enough to check whether the object is productively used or not.

Fig. 41: Display data distribution / usage counts per leading master table and source system

The standard display shows each customizing key listed for the systems of origin and the selected
data tables. You might wonder why there are entries with an empty key: all data table rows with an
empty attribute still get counted. In our example above in figure 41 the FI table BKPF holds 13.002
rows in source “810” with no document type set.
Double click on a counter value to see the real data behind a customizing value. Look at the first
row in figure 41. If the RFC user (not your personal user!) owns enough authorization (role template
SAP_MCT_MCDELTA_RLST), then the data rows of table COBK from system “802” are shown in a
kind of SE16, filtered based on table field BLART=’SA’. Before the data gets pulled, you can enter
more restrictions in a popup which appears after you clicked the counter. There you can – if such
fields exist – specify a date or a year and limit the maximum number or rows to pull.
The MCDelta service offers the optional extra “Extended Analysis” where the usage check is
clustered additionally by organizational unit and fiscal year. Figure 42a shows how to access this
functionality. The new screen consists of three parts. On the left side there are some functions to limit
the data set calculated, the lower half shows all clustered data and the upper half is a bar chart
representing the data graphically. By default, the calculation of the chart starts using all data with a
54
SAP MCDELTA, VERSION 9.0 - USER GUIDE

org. unit assigned to derive the country. The sum of all key counters is shown based on the country by
system of origin. By using the buttons and fields on the left side you can restrict the chart display on
systems, master source tables and org. units. Press the button in the upper menu to recalculate.
You can filter for specific org. units by entering them directly in the fields on the left side (Select-
Options parameters) or use the right mouse button on the org. unit field in the data grid.

Fig. 42a: Display data distribution / usage counts per leading master table and source system

Additionally, you can switch between the available org. units by pressing the corresponding buttons at
the top in the menu. If a certain org. unit is not presented there, then there is simply no data with this
org. unit. At the top of the left-hand side you find several buttons reflecting the number of systems
compared. Deselect systems you want to exclude from the analysis. In the field below the button “All
master” you can enter one of the tables from column “Table Name” to further restrict your selection.

If you want to show the chart also based on

the actual customizing keys, then select the
corresponding column. Please keep in mind, that
the grid in the lower half always shows all data.
Only the chart is changed based on the selection.

By default, the chart does not take the fiscal year into account (equivalent to button ).
Make use of the buttons at the top to either show the data for a specific single year or for a period of
years. Once selected, new buttons will appear which allow you to either toggle through the single
years or to limit / expand the period range (figure 42b and c). When using the period range, two

55
SAP MCDELTA, VERSION 9.0 - USER GUIDE

additional buttons (“Show year” and “Hide year” in fig. 42c) are available which allow you to toggle the
display accumulated for all years of the range or by each year of the range.

Fig. 42b: Display data distribution for a single year

Fig. 42c: Display data distribution for a range of years

Attention: If you sort or filter the data grid for a better overview but still want the bar chart to be
displayed on basis of countries, then do not forget to reselect the column “Country”!

Please note: Sometimes the bar chart appears to be cut when showing for the first time or garbled
up in full screen. Resizing the windows normally corrects this problem.

56
SAP MCDELTA, VERSION 9.0 - USER GUIDE

5.3) Rate of master data change

MCDelta features another ad hoc analysis: the data change rate (or frequency of change). Here you
can check in what quantities master data entries get created or changed. For this you can choose any
field from the table of interest and use an available org. unit and year / month information for further
clustering.
Figures 43a and 43b show an example based on table LFB1 (company code-based view on
vendors). Here we want to check the numbers of vendors created per month and company code. This
might help in discussions on how to – or if at all – connect certain sources for replication. Another
interesting example would be document types as how they are used in the FI document header
(BKPF).

Fig. 43a: How to create an ad hoc analysis for checking data change rate

Attention: The connected source systems might be production servers. Please refrain from
sending various requests for very large tables simultaneously.

When creating the analysis object, you can select any of the date or period fields in the table. It also
includes fields which can only hold a year like the fiscal year. In that case you can add an additional
field which holds the month or posting period information. In our example both year and month are
taken from field ERDAT. Don’t forget to first fill the table name and hit the enter key. Then all drop-
down lists will be populated with the available (and valid) field names. Optionally, you can specify an
org. unit and two other fields for adding more information. Also, for your convenience, the analysis can

57
SAP MCDELTA, VERSION 9.0 - USER GUIDE

include up to two filters specified in MCDelta. Available filters will be automatically proposed in the
drop-down lists.

Fig. 43b: Result display for the vendor analysis

58
www.sap.com

© 2019 SAP SE or an SAP affiliate company. All rights

reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP SE.
The information contained herein may be changed without prior
notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE and its affiliated

companies (“SAP Group”) for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are
set forth in the express warranty statements accompanying such
products and services, if any.

Nothing herein should be construed as constituting an additional

warranty. SAP and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered
trademarks of SAP SE in Germany and other countries.

Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.