Ansicht
Dokumentation

PY_DSN_T5FDSNFMAPC - Redefine mapping and differences for change blocks - Customer views

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
view

You use these views to modify or validate the configuration delivered by SAP and to neutralize or not the creationof this mapping.

For more information, please refer to the DSN version change documentation, published on the SAP Help Portal.

Note:

View V_T5F99FMAP, subapplication DSN, always takes control of view V_T5F99FMAPS.

View V_T5FDSNFMAPC, subapplication DSN, always takes control of view V_T5FDSNFMAPS.

With this customizing activity:

• You redefine the mapping delivered by SAP.

• You neutralize the differences in the change blocks (blocks 41) during your transition period and after the annual start of the new production version.

In both views, you specify 06as HCM Location then DSN as subapplication.

You modify the mapping according to the modified code values, as well as your functional needs.

view view view Note regarding ratings:

PxxVyy corresponds to the DSN version being used. That is, for the year 2021: P21V01 or P21V011

PxxVyy +1 corresponds to the DSN version to come, which is the PxxVyy version incremented by one year. That is: P21V01 (or V011) +1 = P22V01.

1. Select the Sectionand Zone pair corresponding to the block and item of the DSN affected by the version change.
2. In the Source value column, indicate the code value that was added or merged into the new DSN version (version PxxVyy +1).
3. In the Version column, indicate the DSN version PxxVyy +1.
4. For the End date, indicate 31.12.9999or the specific date that the mapping must finish. Replace the Start datewith the date on which the mapping must be taken into account.
5. For Target value, indicate the code value that must be generated in your current DSN version )DSN Version PxxVyy).

view Note:

The value before changing is also called the source value.

The value after changing is also called the target value.

Example of contract block (40) configuration for view V_T5F99FMAP

In the event of a code change in the standard, associate the old code for version PxxVyy with the code for version PxxVyy +1.

For example, if the value in block 40 for the COCCLitem is equal to 81 for versions lower than PxxVyy+1 and to 37 from version PxxVyy+1, keep the V_T5F99FMAP view as follows:

Sect.	Field	Source value	version	Target value
CONT	COCCL	81	PxxVyy +1	37

Examples of change blocks settings (41) for the V_T5FDSNFMAPC view

Example 1

When the new DSN version is launched or when the transition period is activated, the source valueis 81 and the target valueis 37.

The difference between the values indicates a change in the standard, but not the employee's situation. As such, you must neutralize the generation of block 41, which detects a change in the value in block 40:

Sect.	Field	Source value	Version	End date	Start date	Target value
CONT	COCCL	81	PxxVyy+1	31.12.9999	01.01.2022	37

Example 2

When the new DSN version is launched or when the transition period is activated, the source valueis 81 and the target valueis 44 instead of 37. This change is caused by a code changing from 81 to 44, due to a contractual change of the employee.

In this case, a block 41 is required, but this will carry the default value 37 to reflect the change of standard.

Block 40 will have the value 44.

Sect.	Field	Source value	Version	End date	Start date	Target value		Default value
CONT	COCCL	81	PxxVyy+1	31.12.9999	01.01.2022	37		37

ABAP Short Reference   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 6276 Date: 20240523 Time: 221538     sap01-206 ( 66 ms )