mapping types not exist in TDMS HCM 4.0

[JohnWick]

Hi, gurus

We are implementing SAP TDMS HCM 4.0 and we have a problem, mapping types not exist so, we can´t make the scrambling. Any idea?

The SP03 is implementing.

An OSS message are open for this problem.

Regards, Manuel

[AlbertVentosa · Accepted solution]

Did You solve it ?

We have the same problem with same pacth level.

Many thanks!

[former_member65049 · Accepted solution]

Hi Albert,

This needs to be analyzed on a case to case basis.

You can raise an OSS message in CA-TDM-HCM component.

The TDMS HCM colleagues will check this.

Thanks,

Rupam

[JohnWick · Accepted solution]

Hi Albert, Rupam

The problem is not solve. We have two OSS messages:

Message (0000963763 2012)

1058989

We have this problem for three weeks and still it´s not resolved.

Please Rupam help us, we are delayed with the project with this problem.

Thanks. Manuel

[AlbertVentosa · Accepted solution]

Hi Manuel, Rupam

Our system is Linux+Oracle, and I have another sandbox system with Windows+SQLServer.

In both cases, with the same patch level, we have the same problem.

It seems that scrambling types are not copied from template to project. ( If template exists .. )

In SAP Note 1665861 - TDMS 4.0 - Collective note for Scrambling, there are references to different notes:

1782451 TDMS 4.0/SP03/01/ Various Corrections - Mandatory

1786034 TDMS 4.0: SP02/SP03: MAPPING_ID_NOT_FOUND Error in Copy Func

1769730 TDMS 4.0:SP02/03: Scrambling function module update

1770441 TDMS 4.0:SP02/03: Country code update in scrambling rules

but only first can be applied. Note 1786034 seems reference to our problem, but it's released internally only and can't be applied/consult.

We will open a OSS message and inform you about results.

Many thanks!

[JohnWick · Accepted solution]

Hi Albert, Rupam

We have checked all those notes and none of them fix our problem:

The standar MAPPING TYPES are not in table  CNVTDMSSCR_MTYP, so these entires may not be copied to our workcenter

We have checked In client 000 the entries in table CNVTDMSSCR_MTYP  and in this client the table have the needed entries

We have two OSS, those reported in the previous message. I´ll write you fo news.

Thanks, Manuel

[AlbertVentosa · Accepted solution]

Hi,

more information in adition to Manuel.

these tables with mandt row, have entries for mandt 000 but not for work client.

CNVTDMSSCR_MTYPT -> Mapping Types Texts

CNVTDMSSCR_MTYP -> Mapping Types for Scrambling

CNVTDMSSCR_MLNK  -> Link Table : Connects Mapping ID's to Rules

CNVTDMSSCR_MIDT -> Mapping ID Texts

CNVTDMSSCR_MID -> Mapping ID's for Scrambling.

I think that's the problem...

thanks.

[former_member65049 · Accepted solution]

Hi,

The responsible colleagues are analysing the issue. They will reply to the OSS soon.

@Alert, you can raise an OSS message and colleagues will answer to you through that.

Thanks for your understanding.

Regards,

Rupam

[AlbertVentosa · Accepted solution]

If it is helpfull ..

problem seems to be in class CL_CNV_TDMS_SCR_COPY_DATA, method APPEND_DATA when it cry to method APPEND_MAPPING_TABLES.

It writes correctly in corresponding tables CNVTDMSSCR_* of work client, until table CNVTDMSSCR_MID but when try to append table CNVTDMSSCR_MIDT and CNVTDMSSCR_MLNK, it don't write any entry and seems to stops the program.

After that, program APPEND_DATA have continue writing onto CNVTDMSSCR_MTYP and  CNVTDMSSCR_MTYPT, but I think the program had an exeption and not continue anymore.

[AlbertVentosa · Accepted solution]

I think note:

"SAP Note 1786034 - TDMS 4.0 Scrambling SP02/SP03:Append Data customizing issues"

will have the solution ( actually is released internally).  In note "1665861 - TDMS 4.0 - Collective note for Scrambling", the number correspon to :

"1786034 TDMS 4.0: SP02/SP03: MAPPING_ID_NOT_FOUND Error in Copy Func"

but I downloaded it before beginning this project, and It had that name.. curious.

[AlbertVentosa · Accepted solution]

Hi,

I confirm "Note 1793099 - TDMS Scrambling: The Mapping could not be found" solves this incident.

thanks