Introduction To Classification

Classification in R/3
Gabriele Klapper,
Martin Walter
Support Consultants – Logistics
Active Global Support

SAP AG
Contents
The following topics are covered by this presentation:

 Online help
 Important notions and transactions
 Characteristics
 Class system
 Classification
 Interface Design
 Dependencies
 Object search
 User specific settings in classification
 Customizing classification
 Technical and additional information
 Analyzing CA-CL messages
 SAP AG 2003, Title of Presentation, Speaker Name / 2

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Online help available at http://help.sap.com

Online help available at http://help.sap.com
Online help
for
Classification

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Important notions and transactions
Object type The underlying table which is used for

classified objects.
(MARA, DRAW, KNA1,…)
(Material, Documents, Debitor,…)
Object which can be classified.
Object
Defines which object type can be classified

Class type with the class of that class type.
It groups similar objects or classes. By

assigning an object to a class the objects can
Class be valuated with values of characteristics of
this class.
Defines a set of possible values which can be
Characteristic used to valuate an classified object.
A value describes a certain specfication of a

Value characteristic.

Important notions and transactions
Transactions of the class system:
Characteristic Maintenance CT04
Class Maintenance CL02
Classification e.g. CL20N, CL24N, MM01
Objectsearch CL30N

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Characteristics I
In R/3 classification, characteristics describe the properties of objects.

Transaction CT04: In the Characteristic field, enter a name for your new
characteristic. Furthermore you have the possibility to enter a change number if
you want to create the characteristic using engineering change management.

Characteristics II
You enter the main characteristics data on the Basic data tab page.

Characteristics III
Enter a short description of the

characteristic.
You can group characteristics.
Characteristics Groups are
defined in Customizing for
classification. The
characteristics group can help
you to find characteristics with a
matchcode.

Characteristics IV
The Status field shows which applications you can use the characteristic in, such as the
classification of objects:
•"In preparation" status: only possible to choose, when you first create a characteristic.
You cannot use a characteristic with In preparation status in a class.
•"Locked" status: a characteristic with this status, cannot be used in a new class.
However, if you have used a characteristic in a class, and then set Locked status for the
characteristic, this does not affect the characteristic in the class.
•"Released" status: you can use this characteristic in classes.
You can use an authorization group for characteristics to restrict access to certain
characteristics.

Characteristics V
The values of the characteristic can have different data types. The data type of the
characteristic determines which values you can enter for the characteristic. The
following data types are supported: Character Format; Numeric Format; Time
Format/Date Format; Currency Format; User-Defined Data Type.
Characteristics VI
Enter the number of chars for your characteristic. In this case the values of the
characteristic can contain any alphanumeric character of one char.
You have also the possibility to decide, if the values should be case sensitiv.
If you choose character format for your characteristic, you can define the length
of the values by entering a template.

Characteristics VII
•Single-Value/Multiple values: You

define whether you can enter one
value or multiple values for a
characteristic, when you define the
characteristic format.
•Restrictable: This indicator is only
relevant to variant configuration.
•Entry required: A value entry for
this characteristic is required,
otherwise values for the
characteristic are optional entry.

Characteristics VIII
On the tabstrip Descriptions you have the possibility to enter a language-

dependent description of the characteristic.

Characteristics IX
The values of a characteristic specify the properties of a characteristic. The

values must match the format that you defined on the Basic Data screen. You
can enter up to the number of characters that you defined in the format. If
your characteristic is an alphanumeric characteristic, enter a language-
dependent value description. You can enter up to 30 characters.

Characteristics X
Additional Values: If required, you can use the allowed values you define as
possible entries, but still allow other values for your characteristic. This means that
you can assign values that are not in the allowed values in characteristic value
assignment functions. To do this, select Additional values.
Default value: You can define one allowed value as a default value. This value then
appears as a default in characteristic value assignment functions. You can either
accept the value or select another value. To define a default value, select column D.

Characteristics XI
Check table:
You can use a table to check
the allowed values of a
characteristic. If you enter a
check table in the
characteristic, any values you
assign to the characteristic
must match entries in the table.
Entering a Function Module:

On the allowed values tab page
in characteristics maintenance
functions, you can enter the
name of a function module for
checking the values you enter
when you classify an object.

Characteristics XII
For values in character format CHAR or

number format NUM, you can define
language-dependent documentation:
On the Allowed values screen, choose

Extras -> Change language. Enter the
language in which you want to write
documentation.
Select the value with the cursor and

choose the pushbutton
'Documentation'.
Enter your text in the text editor and

save.

Characteristics XIII
On the Additional data screen, in subscreen Procedure for value

assignment you can decide if the characteristic is ready for input, is
not displayed or if the possible entries displayed.

Characteristics XIV
You can link documents, such as drawings or photographs with characteristics and
you can also link documents to a value. This allows you to describe the value in
more detail. (Place the cursor on the value and choose 'Document for value'.)

Characteristics XV
When you create a reference characteristic, choose the Additional data

tab page in characteristics and insert table name and field in this table
you want to refer to. You do not have to maintain the tab page Basic data
first for reference characteristics. The system copies the formatting data
from the object master to the characteristic.

Characteristics XVI
If you only want your characteristic to be used only for specific class types, you can
enter these class types on the Restrictions tab page.

Characteristics XVII
In transaction CT04 you

have the possibility to
display the change
documents of the
characteristic.

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Class system – Overview I
Classes are used for grouping characteristics

and assigning objects to them. The central
transaction for maintaining, creating and
deleting classes is cl02.

Class system – Overview II
The class field contains the name of the class, the class type depends on the
object type you would like to classify. The buttons from left to right stand
for
 Display
 Change
 Create
 Create by Copying
 Delete
You also have the possibility of using ECM (Engineering Change Management).
This means possible changes are valid from a certain date.

Class system – Creation I
On the basic data tab enter a description for the class, gather classes in a group
for finding them easier via match code or restrict characteristics from maintenance
by means of organizational areas.
Moreover you can let check the system if one object is going to be classified twice
with a class of same class type.

Class system – Creation II
String used for finding a class via

match code.
On the tab characteristics enter the

characteristics you would like to use
in that class. Later they will represent
the characteristics you will assign values
to for the objects you are classifying.
On the other tabs you can assign more texts in different

languages or documents. The standard tab mainly
shows the standards organization, such as DIN, ISO,
or ANSI.

Class system – More settings I
You can assign dependencies to a class, like
You are able to assign dependencies to a class, namely actions (obsolete) and
procedures. There are executed each time classification transactions are
executed (cl20n, cl24n, …) (as long as class type 300 is not selected. This a
special case of variant configuration.)

Class system – More settings II
In order to adjust a characteristic or

its allowed values class specific, you
can overwrite the characteristic or its
allowed values.
For example characteristic_1 has

values A,B,C but especially in class
class_1 it should have values B, D
simply press

Class System - Class Hierarchy
class_1
class_11 class_12 class_13
class_111 class_112 … …
You can build hierarchies of classes, manually using transaction

cl20n or cl24n, or graphically using transaction cl6c.
In this case subordinated classes inherit the characteristics of

the superior class. Then, the inherited flag is set in the class
display on tab characteristics.

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Classification I
Transaction CL20N:
You can use this function to assign
an object to one or more classes
(multiple classification).
Enter the object you want to classify
and select a class type. Confirm
your entries. Enter the class or
classes to which you want to assign
your object.
If the object already has assigned
classes, choose ‘Edit’ and ‘New
assignments’.

Classification II
Classification Status
You can assign various statuses to a classification record.
These statuses are defined separately for each class type in
Customizing for Classification. The R/3 System contains the
following settings as standard:
Released: This status is assigned when the assigned values
are complete, which means that values are assigned to all the
characteristics that have the Entry required indicator.
Incomplete: A classification is incomplete if not all
characteristics with the Entry required indicator have a value
assigned to them.
Locked: If you want to ensure that the characteristic values
assigned to an object are checked again, for example, you
can set this status.
The classification status is relevant to the find objects
function. You can exclude locked and incomplete
classifications from your search.
Ltm = Sort position of the class

Classification III
If you want to assign values to characteristics, position the cursor on a class.

Double-click on the class. You see a list of the characteristics of all the classes to
which the object is assigned. Select the values and save your assignment(s).

Classification IV
Transaction CL24N:
You can use this
function to assign
several objects to
one class at the
same time.
Select button 'Only
new assignments'.

Classification V
A dialog box appear, asking

whether you want to assign
a class or a specific object
type (such as material) to
the class.
If you choose object type:
Enter the objects you want
to assign to your class.

Classification VI
If you want to assign values to characteristics, you can select them from the
list.

Classification VII
Transaction MM01:
Enter a material number, an
industry sector, and a material
type. Confirm your entries. In
the dialog box, select
classification and choose
Continue.

Classification VIII
Enter one or more classes in

which you want to classify the
material.
To assign values, double-click
on the class in which you want
to assign values. Assign values
to the characteristics, by
selecting one or more values.
Save the values.

Classification IX
Transaction CL24N:
Enter a class name and class
type. Choose 'Only new
assignments'. You see a
dialog box, asking whether
you want to assign a class or
a specific object type (such
as material) to the class.
Choose Classes.
Enter the classes you want to
assign to your class. These
classes are assigned to the
class you started with.
When you assign classes to
a class, you can restrict the
allowed values of the
characteristics. This means
that only values from the
restricted allowed values are
allowed when you classify
objects in these classes.

Classification X
Transaction CLHP:
Enter a class name and
class type and press
the button 'Change'.

Classification XI
Please choose the button 'Create New Assignment'.

Classification XII
Enter the classes you

want to assign to
your class.
These classes are
assigned to the class
you started with.

Classification XIII
Now the class you enter is part of a class hierarchy, you can see the classes
assigned to the class you started with, in the hierarchy in tree form.

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Interface Design I
You can use Interface

design to group
characteristics together
and define your own value
assignment screen with
pushbuttons or tabs for
groups of characteristics.
On classification view:
Choose Value assignment
-> Characteristics
grouping -> Create.

Interface Design II
You see a dialog box

in which you enter a
name for your
characteristics group.
The combination of
characteristics is
saved under this
name.
You can define that characteristics groupings are displayed as pushbuttons or

tabs in value assignment. You can define up to 15 pushbuttons and 9 tabs.
If you select Summarize, the characteristics you grouped together are no
longer displayed individually on the main characteristic value assignment
screen.
Interface Design III
Select the
characteristics which
should be grouped
together.

Interface Design IV
You see the processing screen on which you can design the interface
for the characteristics you want grouped together.

Interface Design V
The system shows the characteristics, which are not belonging to a

characteristic group, on the tab 'General'.

Interface Design VI
The characteristics which are selected for the characteristic group

'TAB1' are shown on the tab 'TAB1'.
For more information on designing the interface for characteristic
groupings, see Processing the Interface Design.

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Dependencies I
We make a distinctions between local and global dependencies:
You create global dependencies independently of any specific object. For a

global dependency you assign an external name to identify a global
dependency. Global dependencies are maintained and managed centrally.
Changes to a global dependency affect the dependency wherever it is
used.
You create local dependencies for a specific characteristic or characteristic

value. You can only use a local dependency for the object for which it is
created. The system assigns an internal name to identify a local
dependency.

Dependencies II
Transaction CU01:
You see the initial screen. Enter
a name for your dependency.
If you want to create your

dependency as of a specific
date, enter a change number.

Dependencies III
On the basic data screen, enter a language-dependent description for the

dependency and select a dependency type. In the standard R/3 System, you see the
status 'in preparation' when you first create a dependency. You cannot set the status
to 'Released' until you have written syntactically correct source code.

Dependencies IV
Select the ‘Dependency editor’ pushbutton, you see the editor, where you can enter
the source code for the dependency.
Once you have entered the source code, choose ‘Check’ to check whether your source
code contains errors.

Dependencies V
Go back to Basic data. If the source code contains no errors and you want
to use the dependency, change the status to 'Released'. Save your
dependency.

Dependencies VI
You can assign dependencies to classes, characteristics and characteristic
values for classification. You can use the following dependency types:
Dependency type Object

Preconditions Characteristic,
characteristic value
Selection conditions Characteristics
Actions (obselete) Characteristic,
characteristic value, class
Procedures Characteristic,
characteristic value, class
Dependencies can be used in class, characteristic, characteristic values

Concerning syntax and object dependency types please have a look at
documentation.
For more information on creating global dependencies, see the R/3
Library Variant Configuration (LO-VC) and for local dependencies, see
the R/3 Library Characteristics (CA-CL-CHR).

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Object search I
The main transaction of finding objects once having

been classified is transaction cl30n.
Class and class type must be entered, in order to search for

objects which have been classified with it.

Object search II
Searching in the
entire hierarchy
Searching only You can select

in the top class characteristic
of the hierarchy values as a filter
for the search
Here the class

hierarchy is
displayed

Object search III
The search result is shown in the ALV-grid.
Leaving all values blank, you get a list of all objects classified
with this class and class type.

Object search IV
You can define a function (in the customizing) or directly here.

Object search V
It allows you to execute the defined transaction from the result screen.
Mark the object

and press here.
In this example
you would go to
transaction mm03.

Object search VI
Customizing the result screen

enables you for example to let you
display all characteristic value
assigments.
Mark the characteristic

in questions.

Object search VII
Now additional characteristics and their value assignments are displayed.
Moreover you can define

a sort order, set filters for
the search and optimize
the display.

Object search VIII
In order to set a
default view on the
result for a class
type and/or a
specific class,
you can use
the report
RCL_CREATE_INIT_
LAYOUT.
(Confer OSS note

419578)

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

User specific settings in classification I
In most transactions of the R/3 classification component you have

the possibility of customizing your view on classification screens:

User specific settings in classification II
Most settings are self-

explanatory.
As long as no profile
is defined the user has
an SAP standard profile
which cannot be
changed.

User specific settings in classification III
On the tab ‘Find object’

you can customize the
display of the result
of an object search in
transaction cl30n.
For example the number

of hits is set 100 as
default.

User specific settings in classification IV
You decide whether you

would like to have the
characteristics or its
values generally
displayed language-
independent or language-
dependant.

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Customizing classification I
For customizing the classification system

use transaction spro and then the path
on the left.
Most of them are self-explanatory. We want

to focus on
‘Maintain Object Types and Class Types’
Transaction o1cl

Customizing classification II
Choose the object table for which you would like to customize
classification and press Class types.

Customizing classification III
You get all the class types you can use to classify materials in R/3.
Mark the class type you would like to customize for this object type.
By clicking on Objects, Class Status, … you can customize the settings

according to your needs.

Customizing classification IV
 Objects
Enter the objects which can be classified with classes of this class type when the flag
multobj is set.
 Class Status
Define the class status.
 Organizational Areas
Define the organizational areas you would like to use in classes of this class type.
 Text types
The system proposes text types when entering a long text for a class.
 Classification Status
Define classification status for the class type.
 Functions/Filters
Define which functions and filters can be used in class search.

Customizing classification V
If you would like to maintain the object

table, double click in the initial screen of
transaction o1cl on the corresponding
object table.
Select the screens in classes that you

want to process for your object type
(for example, keywords screen and
characteristics screen).
Specify the subscreens that you want
to embed in the central assignment
screens of the Classification System.
These subscreens contain the fields
where you enter the object key.
Other indicators are only relevant to
some objects. The Redundant storage
indicator controls how the
classification data in reference
characteristics is stored.

Customizing classification VI
If you would like to

maintain the class types
for an object table, mark in
the initial screen of
transaction o1cl the
corresponding object
table, then press class
types, and double click on
the class type.

Customizing classification VII
You can define the screens to be processed for classes of this

class type, activate change documents or ECM and allow various
functions which you find explained in the F1-help.

Customizing classification VIII
Especially the flag ‘multiple objs allowed’ (flag multobj)

is very important.
It has to be set if you would like to classify objects of

different object tables like batches for example. They
are usually classified with class type 001 (MARA) and
and class type 023 (MCHA).
Once you already have classified objects, you cannot set the
flag your self anymore. This has to be done by the report
Rccluka2. (Confer OSS notes 80907)
Also if you wish to activate change documents in

classification this flag has to be set.
(Confer OSS note 65124)

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Technical and Additional Information
The following slides are providing a deeper knowledge of

classification in R/3 which will help finding solutions for customer
problem messages. Therefore we discuss the following topics:
 Data Base Storage of Classification Data
 Classification BAPIs and User Exits
 Distribution via ALE
 Relevant Function Groups / Modules
 Authority objects

Data Base Storage of Classification Data I
Characteristics:
Table Description Important fields

CABN Basic data of atinn: internal char number
atnam: char’s name
characteristics attab, atfel: reference char.
CAWN Values for the atinn: internal counter

atwrt: char value
characteristics atflv: internal floating point
(for intervals lower bound,
atflb: upper bound)
CABNT Characteristic’s atinn: internal counter

atbez: char’s description
description in
different languages
CAWNT Value descriptions in atinn: internal counter

atwbt: char’s value descrip.
different languages

Data Base Storage of Classification Data II
Classes:
KLAH Basic data of class clint: internal class number

klart: class type
header class: class name
KSML Characteristics clint: internal class number

imerk: internal char number
assigned to a class (if not overwritten) omerk:
internal char number (if
overwritten)

Data Base Storage of Classification Data III
Classification:
AUSP Value assignments to objek: key of classified obj.

atinn: internal char number
objects atzhl: char value counter
atwrt, atflv, atflb, klart
KSSK Class/Object to class objek, clint, klart

mafid: indicator obj/class
assignment
INOB* Internal key to object cuobj: internal number

obtab: name of data base
assignment table for object
objek: key of object to be
classified
*) This table is only relevant if the flag multobj is set. Then value and class assignment in AUSP and
KSSK are not stored directly with the object, but via an internal number. The assignment internal
number to object is given by this table.

Data Base Storage of Classification Data IV
Customizing: (The most important ones)
Table Description Remarks
TCLA Class Types All settings being

necessary for the class
types.
TCLAO Several Objects in If multobj = ‘X’, in this table

the different object settings
one Class Type are stored.
TCLO Key Fields of Objects The format of the key fields

of objects are stored.

Classification BAPIs and User exits I
There are various BAPIs in BAPIs for characteristics :

classification which the customer can BAPI_CHARACT_*
use for reports and setup classification BAPIs for classes :
as background for example. They can BAPI_CLASS_*
be found in transaction se37 using the BAPIs for classification:
following nomenclature: BAPI_OBJCL_*
A detailed overview is
given by transaction bapi.

Classification BAPIs and User exits II
For each BAPI you will find a detailed documentation how the
import / export parameter look like.

Classification BAPIs and User exits III
You also have the possibility to test these function modules

directly from transaction bapi.

Classification BAPIs and User exits IV
The following user exits are available (cf. also OSS note 383092)
 CLCLRS01 Additional Fields on the Result Screen
 CLCLRS02 Fill the Additional Fields on the Result Screen
 CLCTMS01 Default values for finding objects
 CLCTMS02 Check for Same Classification
 CLCTMS03 Dependencies for Finding Objects
 CLFM0001 Change or set default for classification of object
 CLFM0002 Call classification data before saving
 CLFM0003 Call Up After Check of Assigned Char. Values
 CLMMD001 Selection of Objects for Mass Processing

Classification BAPIs and User exits V
Detailed information can be can be

obtained in transaction smod.
Then click on button ‘Components’.
Finally, mark the exit and

press the information
button.

Distribution via ALE I
Distributing classification data

from one R/3 system to another
can be realized by ALE. The
following master data can be sent
(confer OSS note 45951):
Characteristics BD91
Classes BD92
Classification BD93
Class Hierarchies CLHI
These transactions generate

IDOCs which are sent from the
source to the target system.

Distribution via ALE II
For example, enter transaction bd91 for sending characteristic

‘characteristic_1’ to logical system ‘U6BCLNT800’.

Distribution via ALE III
The corresponding
IDOC can be
displayed in
transaction we02.
The different
segments contain all
the information about
the characteristic
and its values.

Distribution via ALE IV
The test tool for

analyzing an IDOC
is transaction we19.
In order to check an
incoming IDOC simply
press the button

Distribution via ALE V
You have 3 standard test

function modules
depending on the type of
the IDOC:
Characteristic IDOC  IDOC_INPUT_CHRMAS

Class IDOC  IDOC_INPUT_CLSMAS
Classification IDOC  IDOC_INPUT_CLFMAS

Relevant Function Groups / Modules
The following function groups for characteristics, classes and

classification, respectively, are very important:
 CTMV Characteristics Maintenance
 CLCM Class Maintenance
 CLFM Classification: Assign Object to Class
Below we will mention some of the numerous modules and

subroutines of these groups which play an important rôle and
help analyzing customer problem messages.

Function group CTMV
Function modules:
CTMV_CHARACT_CHANGE
All changes regarding a characteristic.
Subroutines:
SAVE_VALUES
Routine saving the values of a characteristic.
SAVE_ALL
Routine saving the characteristic.

Function group CLCM
Function modules:
CLCM_CLASS_CHANGE
All changes regarding classes.
Subroutines:
BUCHEN_CHECK
Check if class is ok an can be updated.
KLASSENART_PRUEFEN
Check if class type is allowed.

Function group CLFM
Function modules:
CLFM_OBJECT_CLASSIFICATION
Runs everytime time a classification transaction is called.
CLAP_DDB_UPDATE_CLASSIFICATION
Update the classification data.
Subroutines:
BUILD_ALLAUSP
Creates the internal table of value assignment during classification process.
INSERT_CLASSIFICATION
Creates internal classification table (allkssk).

Authority Objects I
In order to get an overview

of the authority objects which
can used in classification,
select the displayed path.
Enter CLAS as object class.

The documentation button explains very well the use of each
authority object.

Contents
 Online help
 Characteristics
 Class system
 Classification
 Dependencies
 Object search

Analyzing CA-CL messages I
We now would like to give an idea of how to start analyzing

customer problem messages in CA-CL, which consists of the
following subcomponents:
CA-CL-CHR Characteristics
CA-CL-CLS Classes
CA-CL-CL Classification
CA-CL-SEL Object Selection
CA-CL-ENV Environment

Analyzing CA-CL messages II
Always let give you a

reproduceable example before
starting analyzing the problem!
Since sometimes it is hard to

figure out what kind of objects are
classified with which class, it is
useful to set a breakpoint at
CLFM_OBJECT_CLASSIFICATION.
Enter for example mm03, and click

on the classification tab:

Analyzing CA-CL messages III

Analyzing CA-CL messages IV
If you would like to know what classification data is stored on the data
base for an object, first get the object name. If it is class type where
the flag ‘multobj’ is not set, you directly find the entry in AUSP:
And in KSSK:

Analyzing CA-CL messages V
If the flag ‘multobj’ is set, you have to proceed as follows: Find the INOB-
CUOBJ for the corresponding object. Suppose you have a material to
which batches are assigned: In order to get the complete key you can
use table MCHA

Analyzing CA-CL messages VI
Or you directly enter the material in transaction se16 for table INOB
as a part of the complete object key.

Analyzing CA-CL messages VII
Use the key field

INOB-CUOBJ to
view the entries
stored on the
data base
concerning
classification.

Analyzing CA-CL messages VIII

Analyzing CA-CL messages IX
Looking on the data base can be necessary if classification data

is already stored and an application tries to save an identical
entry in AUSP or KSSK (SAPSQL_ARRAY_INSERT_DUPREC).
So first look what is stored on the data base, then figure out what
the application tries to save. This can be done as follows:
Set breakpoints in subroutines BUILD_ALLAUSP and

INSERT_CLASSIFICATION of function group CLFM.
Go into the corresponding transaction where the value

assignment is changed, for example transaction mm02.

Analyzing CA-CL messages X
Change the value ‘Cypress Hill’ to ‘Singing in the rain’
Press save.

Analyzing CA-CL messages XI
At the end of build_allausp table allausp contains the new

value assignments.

Analyzing CA-CL messages XII
You can see the new value and the old value in allausp.
The old value gets deleted (Statu = L), and the new value is added
(statu = H)
This should consistent with the data base. For example, if a line
should be deleted in AUSP which does not exist, one would get
a dump ‘Delete data in table AUSP terminated’.

Analyzing CA-CL messages XIII
Process to the next break point and then as far as shown in the picture.

Analyzing CA-CL messages XIV
In table allkssk you will see what classification is going to be send to the
update task.

Analyzing CA-CL messages XV
There are a lot of reports in classification helping removing

inconsistencies, of which we mention only a few.
RCCLZUOB If classification data in AUSP / KSSK is

stored, for which the objects do not exist
anymore, they will be removed. Simply
enter class type and/or class.
RCLINOB2 Similar, but for objects stored via the

INOB table. (Confer report)
RCLAUSP2 / 3 Synchronize Table AUSP with KSML
RCCLUKA2 Convert KSSK and AUSP to Internal Number

(Table INOB)

Analyzing CA-CL messages XVI
Idoc problems generally can be analyzed by determining what IDOC type

is used and then use the corresponding inbound function module in
IDOC test transaction we19.
Process it in foreground or in debugging mode.

Analyzing CA-CL messages XVII
The function modules which are responsible for displaying and saving
the values on the value assignments screens are
CTMS_DDB_OPEN / CTMS_DDB_CLOSE
in function group CTMS. You can set a breakpoint in order to see if the
correct values are going to be saved for example.
Enter transaction mm03.

Analyzing CA-CL messages XVIII
The internal table IMP_SELECTION contains the assigned values

Analyzing CA-CL messages XIX
In order to check what characteristics are overwritten and what

values are allowed, you may check table KSML and AUSP.
For example, characteristic

mawa_cd_preis has the values
displayed on the left.
But in the class mawa_cd it has
the following values:

Analyzing CA-CL messages XX
The OMERK entry in table KSML points to the ATINN of the overwritten
characteristics whose values can be found in table CAWN.

Analyzing CA-CL messages XXI
If overwritten characteristics were used, value assignments of

objects would be found in table AUSP with this ATINN, which is
stored as OMERK in KSML.

Analyzing CA-CL messages XXII
Sometimes it can occur, that there

are inconsistencies between
values and there associated
language dependant descriptions.
One possible reason can be

buffering of the tables CAWN
and/or CAWNT.
Transaction se11:

Analyzing CA-CL messages XXIII
Buffering should not

be allowed during
a lot of changes are
done. Since it always
reads from the buffer,
but writes to the data
base, inconsistencies
can occur.

Introduction To Classification

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Introduction To Classification

Hochgeladen von

Copyright:

Verfügbare Formate

Classification in R/3

Active Global Support

The following topics are covered by this presentation:

 SAP AG 2003, Title of Presentation, Speaker Name / 2

 SAP AG 2003, Title of Presentation, Speaker Name / 3

 SAP AG 2003, Title of Presentation, Speaker Name / 4

 SAP AG 2003, Title of Presentation, Speaker Name / 5

 SAP AG 2003, Title of Presentation, Speaker Name / 6

Object type The underlying table which is used for

Defines which object type can be classified

It groups similar objects or classes. By

A value describes a certain specfication of a

 SAP AG 2003, Title of Presentation, Speaker Name / 7

Transactions of the class system:

Characteristic Maintenance CT04

Class Maintenance CL02

Classification e.g. CL20N, CL24N, MM01

 SAP AG 2003, Title of Presentation, Speaker Name / 8

 SAP AG 2003, Title of Presentation, Speaker Name / 9

In R/3 classification, characteristics describe the properties of objects.

 SAP AG 2003, Title of Presentation, Speaker Name / 10

 SAP AG 2003, Title of Presentation, Speaker Name / 11

Enter a short description of the

 SAP AG 2003, Title of Presentation, Speaker Name / 12

 SAP AG 2003, Title of Presentation, Speaker Name / 13

 SAP AG 2003, Title of Presentation, Speaker Name / 15

•Single-Value/Multiple values: You

 SAP AG 2003, Title of Presentation, Speaker Name / 16

On the tabstrip Descriptions you have the possibility to enter a language-

 SAP AG 2003, Title of Presentation, Speaker Name / 17

The values of a characteristic specify the properties of a characteristic. The

 SAP AG 2003, Title of Presentation, Speaker Name / 18

 SAP AG 2003, Title of Presentation, Speaker Name / 19

Entering a Function Module:

 SAP AG 2003, Title of Presentation, Speaker Name / 20

For values in character format CHAR or

On the Allowed values screen, choose

Select the value with the cursor and

Enter your text in the text editor and

 SAP AG 2003, Title of Presentation, Speaker Name / 21

On the Additional data screen, in subscreen Procedure for value

 SAP AG 2003, Title of Presentation, Speaker Name / 22

 SAP AG 2003, Title of Presentation, Speaker Name / 23

When you create a reference characteristic, choose the Additional data

 SAP AG 2003, Title of Presentation, Speaker Name / 24

 SAP AG 2003, Title of Presentation, Speaker Name / 25

In transaction CT04 you

 SAP AG 2003, Title of Presentation, Speaker Name / 26

 SAP AG 2003, Title of Presentation, Speaker Name / 27

Classes are used for grouping characteristics

 SAP AG 2003, Title of Presentation, Speaker Name / 28

 SAP AG 2003, Title of Presentation, Speaker Name / 29

 SAP AG 2003, Title of Presentation, Speaker Name / 30

String used for finding a class via

On the tab characteristics enter the

On the other tabs you can assign more texts in different

 SAP AG 2003, Title of Presentation, Speaker Name / 31

You can assign dependencies to a class, like

 SAP AG 2003, Title of Presentation, Speaker Name / 32

In order to adjust a characteristic or

For example characteristic_1 has

 SAP AG 2003, Title of Presentation, Speaker Name / 33

class_11 class_12 class_13