SAP Note 28148 - Table category processing during language import

Symptom:

Different handling of the individual table categories during the language import

Cause and prerequisites

Different processing with the import of the language-dependent tables into the available clients, dependent on the table type.

Solution

When importing the language-dependent tables, these tables must be differentiated depending on the delivery class of the tables, into which clients they may be imported.
The delivery class of a table is determined in the dictionary (Transaction SE11).Also see the existing F4 help for the delivery class.
Importing Customizing tables in Clients < > 000 is problematic because customer entries must not be overwritten.

As of Release 3.0, language-specific tables are imported as follows:

A. Import of client-specific tables

1. general check:
The respective client is protected against cascading
if field CCNOCASCAD = 'X' in table T000), then no import.

2. Check against the table category:
Class S Insert/Update into all clients except 1.
Class E Insert/Update into all clients except 1.
Class W Insert/Update only into client 000
Class C Insert/Update only into client 000
Class G Insert/Update into client 000
Insert for all clients < > 000, except for 1.
Class L No Insert/Update
Class A Insert/Update only into client 000

B. Import of client-independent tables

1. Check against the table category:
Class S Insert/Update
Class E Insert/Update
Class W Insert/Update
Class C Insert with full language import
No Insert/Update with delta language import
Class G Insert
Class L No Insert/Update
Class A No Insert/Update

As of Release 4.6C language-specific tables are imported as follows:
As of Release 4.6C, the language transport was changed on the tp/R3trans transport tools. The table types have the importance as described in Note 2857.