2018-10-12

Incident: 348393 / 2018 - RPU12W0C restore wage types

after upgrade
ID 002075129400003483932018
Customer 499063 - Alcaldia De Medellin
Installation 0020136997 - ERP Enterprise Resoruce Planning Municipio de Medellin
System QAS - QAS sandbox flash
Component Tools (PY-XX-TL)
Status Confirmed
Priority Medium

Communication
05.07.2018 16:47:41 UTC-5 - Problem Description: Team Basis Municipio de Medellin (S0006654702)

Hi support,

we upgraded an ERP sandbox system from version 603 to 608. in preparation phase, we did a backup of
wage types, then we run the upgrade.

after that we restore that backup but we find differences and we are not sure if we are missing something or
we have missconception about the behavior of this report, also we want to know how can we avoid this
situation?

attachtment document details the issue.

regards

Jonathan Caballero

06.07.2018 08:17:19 UTC-5 - Reply: SAP

Hi Jonathan,

The additional wage types seen in V_512W_B and the other views are wage types that have now been
introduced with the 608 release and were likely not present in the previous versions.

Regarding the differences in the processing and cumulation classes, the values displayed in your attachment
from the upgraded system match the ones from our standard 608 systems. Is it possible that you were
previously using cumulation classes 64, 65 and 66 for other purposes?

As for the errors listed after running program RPU12W0C regarding table T512B, the logs show that the
errors pertain to country groupings 01 (Germany) and UN (United Nations), so I guess these should not pose
any issues to you.

Best regards,

Douglas Spindler

SAP Product Support

________________________

© 2018 SAP SE or an SAP affiliate company. All rights reserved 1 of 5

2018-10-12

Get quicker support! Use SAP Expert Chat! 2213344

12.07.2018 16:54:58 UTC-5 - Info for SAP: Team Basis Municipio de Medellin (S0006654702)

Hi Douglas,

in the attachment document wage types issues after upgrade.docx, we describe the differences found,
comparing our systems devsap (without upgrade) and ci1san (after upgrade and running report RPU12W0C
). in the document describe some clarifications about the points you commented in the first answer.

please let us know what solutions are possible to avoid this changes or if there are any pos activities that can
restore this modifications.

thanks

regards

Jonathan Caballero

18.07.2018 15:14:55 UTC-5 - Reply: SAP

Hi Jonathan,

Notice that programs RPU12W0C and RPU12W0S do not save or restore the definitions of the processing
and cumulation classes. Therefore, the changes to the description and possible values as you are seeing for
processing class 31 or cumulation class 60, for example, are not because of the backup process. Since these
are specific to Payroll Colombia, you would need to raise an incident under component PY-CO in case you
would like further details on why they have changed. However, from the screenshots provided, it looks like
the values remain the same - only the descriptions and value helps are different.

Regarding the errors in RPU12W0C, the documentation of the program states the following: "The program
only reloads the wage types from table T512B that are also available in table T512W. Since you no longer
need wage types that are deleted with an HR Support Package or whose validity end date is changed in table
T512W, you cannot reload these wage types from table T512B". When the program finds a wage type in
t512w for which BEGDA is not the same as in T512B, it displays an error message. The reason for
considering this an error is that SAP does not consider comparable wage types whose BEGDA and ENDDA
are not the same.

One possibility is to split a WT into the same BEGDA and ENDDA dates as the ones you have in T512B, then
run again RPU12W0C. This solution worked fine for all the other customers experiencing the same issue.

Thank you and best regards,

Douglas Spindler
SAP Product Support

27.08.2018 16:05:35 UTC-5 - Info for SAP: Team Basis Municipio de Medellin (S0006654702)

Hi Douglas,

thanks for those clarifications.

we have some more questions, maybe you can help us with some guide line for the next:

1- This process was carried out in the SAMBOX system, which recommendation or what would be the best
way/practice to restore the definitions of the accumulators, which would be friendlier in its execution?

© 2018 SAP SE or an SAP affiliate company. All rights reserved 2 of 5

2018-10-12

2- When executing in the DEV system. can we take into account an activity that can be foreseen this type of
changes, and reduce the impact and post activities?

regards

Jonathan Caballero

28.08.2018 18:22:12 UTC-5 - Reply: SAP

Hi Jonathan,

Unfortunately I'm afraid I cannot comment on the common business practices related to this scenario. Such
cases are normally handled outside of Product Support. My guess is that you would need to reimport the
definitions of the processing and cumulation classes from another system without the upgrade.
I have attached notes 83020 and 1054121 which describe further channels that you may refer to in case you
need further assistance.

Best regards,

Douglas Spindler

SAP Product Support

Contacts

Secondary
Role Name Time Zone Primary Phone E-Mail
Phone

Team Basis
yonatan.echeverr
Municipio de
Reporter UTC +57-3002687268 +57-3166165532 i@medellin.gov.c
Medellin
o
(S0006654702)

Attachments

File Name Description File Type File Size Created By Created On

Team Basis
wage types
wage type Municipio de 05.07.2018
backup erp 603 DOCX 2.6 MB
restore Medellin 16:47:41 UTC-5
to 608.docx
(S0006654702)

Team Basis
wage types
differences wage Municipio de 12.07.2018
issues after DOCX 2.3 MB
types Medellin 16:54:58 UTC-5
upgrade.docx
(S0006654702)

KBA/SAP Notes

© 2018 SAP SE or an SAP affiliate company. All rights reserved 3 of 5

2018-10-12
KBA/SAP Note Number Note Text

83020 What is consulting - What is support?

1054121 The SAP Ecosystem in a Nutshell

2213344 Starting an Expert Chat with SAP Support [video]

Using RPU12W0C to load backup table T512B into

2653865
T512W does not import all entries

Action Log

Changed On Changed At Changed By Action Old Value New Value

Team Basis
Donnerstag Municipio de
16:47:41 UTC-5 Component PY-XX-TL
05.07.2018 Medellin
(S00066

Team Basis
0020751294
Municipio de
16:47:41 UTC-5 Incident created 0000348393
Medellin
2018
(S00066

Team Basis
Municipio de
16:47:41 UTC-5 Status Not Sent to SAP Sent to SAP
Medellin
(S00066

Freitag
08:20:18 UTC-5 SAP Status Sent to SAP Customer Action
06.07.2018

SAP-Hinw.
08:20:18 UTC-5 SAP 2213344
hinz./entf

Notiz/Text
08:20:18 UTC-5 SAP Reply
geändert

Team Basis
Donnerstag Municipio de
16:54:58 UTC-5 Status Customer Action Sent to SAP
12.07.2018 Medellin
(S00066

Team Basis
Municipio de Notiz/Text
16:54:58 UTC-5 Info for SAP
Medellin geändert
(S00066

Mittwoch SAP Proposed

15:17:17 UTC-5 SAP Status Sent to SAP
18.07.2018 Solution

Notiz/Text
15:17:17 UTC-5 SAP Reply
geändert

© 2018 SAP SE or an SAP affiliate company. All rights reserved 4 of 5

2018-10-12
Team Basis
Montag Municipio de SAP Proposed
16:05:35 UTC-5 Status Sent to SAP
27.08.2018 Medellin Solution
(S00066

Team Basis
Municipio de Notiz/Text
16:05:35 UTC-5 Info for SAP
Medellin geändert
(S00066

Dienstag SAP Proposed

18:25:10 UTC-5 SAP Status Sent to SAP
28.08.2018 Solution

SAP-Hinw.
18:25:10 UTC-5 SAP 83020
hinz./entf

Notiz/Text
18:25:10 UTC-5 SAP Reply
geändert

Team Basis
Montag Municipio de SAP Proposed
16:16:28 UTC-5 Status Confirmed
03.09.2018 Medellin Solution
(S00066

© 2018 SAP SE or an SAP affiliate company. All rights reserved 5 of 5