Report RADNTLANG, Exception Table Check, Runtime object table

[Former Member]

Hello,

I'm preparing one of our SAP ERP 2004 systems for Unicode Migration, right now.

When running report RADNTLANG I have the following two issues:

1. When I check "Exception Table Check" I get several "Text language indicator set incorrectly" error messages

2. When running the report without "Exception Table Check" 54 nametabs of 57 are succesfully generated. The are three remaining, where I get at "Runtime object table could not be generated":

/DSD/PE_CONDITIONTYPE, /DSD/PE_EXTPHYSI, /DSD/PE/EXTPHYSICALUNIT

Is this anything I have to worry about? Notes 672835, 480671 don't give any advice on this, in my opinion.

Best Rgs and I appreciate your help.

Thorsten

[nils_buerckel]

Hi Thorsten,

for 2), did you already check those tables in SE11 for consistency ?

Best regards,

Nils Buerckel

SAP AG

[Former Member]

Hallo Nils,

tanks for your input. I checked the structures and they are all valid.

I reran RADNTLANG and the three renaimg nametabs where generated as well.

This only leaves

1. When I check "Exception Table Check" I get several "Text language indicator set incorrectly" error messages.

eg. Table HRP1020: Text language indicator set incorrectly. I checked the database object and the runtime object in SE11

(I gather aka "database object == Oracle DB table" "Runtime Object == SAP DDIC object") and both seem to be ok.

I can't assess if this is really a problem, though.

Best Rgs

Thorsten

[nils_buerckel]

Hi Thorsten,

HRP1020 is listed in the attachment of SAP note 672835.

The text lang attribute should be set off for this table.

This is included in SAPKE50026.

The SAP recommendation is to set the flag accordingly.

From my point of view, this is a MUST for this table in case you have

a) an HCM system (as this is a HCM table) and the table contains data

b) an MDMP system

Best regards,

Nils

[Former Member]

Hi Nils,

sinnce the system is neither (HCP, MDMP) we decided to leave the tables unchanged due to our "we will not change any SAP objects" pollicy. Hope this will not turn out to be a problem.

Best Rgs,

Thorsten

[nils_buerckel]

Hi Thorsten,

my statement regarding HCM was for this specific table.

in SAP note 480671 you can find the relevant scenarios / cases:

Excerpt:

The following mechanisms require this flag:

- in Unicode systems:

RFC between Unicode and non-Unicode, single code page or multiple code page (MDMP), systems

- in non-Unicode systems:

Conversion of a non-Unicode system to a Unicode system (trx SPUMG)

- R3trans, when transporting text data between non-Unicode and Unicode systems.

- Abap statement IMPORT FROM DATABASE: in Unicode systems when importing data exported by an MDMP system, and in non-Unicode systems when importing data exported by a Unicode system.

However the text flag is for example not relevant if the table is completely empty (and will not be filled by interfaces).

Best regards,

Nils Buerckel

SAP AG

[Former Member]

Hi Nils,

our ABAP developer team checked on it and were sure, that these tables won't pose a problem. They were very anxious about changing the "SAP standard", though. Problem is, since we don't use HCM in this system at all, we don't apply any SPs for the component either...

The system will be ugraded to ECC 6.0 after the Unicode migration, so I hope this will resolve the actual problem, which is: these tables right now do have 2 LANG fields, 1 flag.

A lot of thanks for your support in this.

Best Rgs

Thorsten