Kontakt

Ansicht
Dokumentation

FINS_CFIN_KEY_MAP_CHANGE_LOG - Central Finance: History of Key Mappings

FINS_CFIN_KEY_MAP_CHANGE_LOG - Central Finance: History of Key Mappings

ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this report in the Central Finance system to keep track of changes to mappings (ID mappings) between a source and the Central Finance system for desired key mapping entities, such as company ID or cost center ID. With this report, an auditor, for example, can always check who added, changed, or deleted a certain mapping value and when. You can answer, for example, the following questions:

  • Which value in the source system was assigned to a certain value in the Central Finance system at a certain point in time?
  • Who has changed the mapping of a value in the source system and when?
  • Who has deleted a certain key mapping and when?

Integration

To display, mass upload, mass download, or delete mappings or to generate templates for mappings, you can use the Central Finance: Manage Mappings report.

Prerequisites

  • You have executed the following Customizing activities under Cross-Application Components -> Processes and Tools for Enterprise Applications -> Master Data Governance -> Central Governance -> General Settings -> Key Mapping:
  • You have defined mapping contexts for UKMS.

Define a Mapping Context for UKMS ->Define Mapping Contexts.
In this Customizing activity, you can define mapping contexts across clients for the Unified Key Mapping Service (UKMS).
  • You have activated the change log for MDG.

Define a Mapping Context for UKMS ->Activate Change Log for Mapping Context.
In this Customizing activity, you can activate the change log per main context. See also SAP Note 2256665.
Caution
Please be aware, that once you activated the change log in your productive system, if you deactivate the change log and activate it again afterwards, this may lead to inconsistencies in the history of key mappings.
  • You have assigned business objects to main contexts.

Enhance Key Mapping Content ->Assign Business Objects to Main Contexts.
In this Customizing activity, you can assign business objects to a main context ID that is defined within the Unified Key Mapping Service (UKMS). UKMS is the basis for the key mapping framework. Within UKMS, you define mapping contexts, whereby each mapping context has a main context ID. If you want to map different business objects (such as supplier, customer, and business partner) to each other, you assign the same main context ID to them.
  • You have authorization for the transaction FINS_CFIN_KM_AUDIT.
  • You have display authorization for the authorization object MDG_IDM.

Features

On the basis of the selection criteria, the report retrieves the historic key mapping statuses for one source system and the Central Finance system. It also retrieves the differences between just two past statuses so that the details of each action can be displayed.

Selection

You can choose for which source system and mapping entity you want to display a history of mappings.

  • If you want to check what happened to a certain mapping value, you enter this specific mapping value and choose either Target or Source for the perspective you want to explore. If you leave the Mapping Value field empty, the report selects all mapping values for the respective source system and mapping entity.
You can enter one or more mapping values in the search help, but not ranges of mapping values. You can also use wildcard searches.
  • If you are using the search help for mapping values or for mapping values and context fields for the source system, then the system determines the RFC destination from the business system and the usage for Check Reports (Data Flow Verification Reports) that you defined in the following Customizing activities:

  • To display the context field that is relevant for a mapping entity, you select the desired mapping entity and then choose Enter. If you would like to check mapping values for cost center IDs in a specific controlling area, for example, you would then have to enter the respective controlling area, as well.
  • You can choose the period for which you want to explore the key mapping history. By default, the time zone of the user is set, and you can change it to suit your requirements.

Note

The report works best when you restrict the selection as much as possible.

Standard Variants

Output

You obtain a list of source mapping values and target mapping values with the name of the user who last changed the key mapping value and the day and time at which the changes were made. To display the action that led to the change of the mapping value, you can select the desired line and choose the Details (magnifier) icon. The following details are displayed dependending on the changes made:

  • Mapping Added
Two lines are displayed with the + (plus sign) in the Action field. One line shows the mapping value in the source system and the second line shows the mapping value in the Central Finance system.
  • Mapping Deleted
One or more lines are displayed with the - (minus sign) in the Action field. The line or the lines show the mapping values in the source system or the mapping value in the Central Finance system, depending on which entries have been deleted. For example, you can delete only one mapping value in the transaction MDG_KM_MAINTAIN, but as a result the complete mapping is not valid anymore.
  • Mapping Changed
Two lines are displayed. The first line with the # (hashtag) shows the changed mapping value, that is the original and the new value. This mapping has been changed. The second line with the - (minus sign) shows the original value.

Activities

To access this report, call up transaction FINS_CFIN_KM_AUDIT. This transaction is also part of the user role SAP_SFIN_CFIN_AUDITOR, which can be assigned to your user.

Example






Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.

Length: 8573 Date: 20240601 Time: 011116     sap01-206 ( 104 ms )