I have a problem with transporting classes. ie I want to transport all the classes present in the transaction code CL03 from my development server to production server. The class type is 032.
How to do this? Is it possible to include the classes to objects/Requests?
Try SE09
It has to be done with ALE. You cannot tranport ( with a normal
transport request ).
OSS 45951 explains all the process.
SAP Note No. 45951
19.03.2003
________________________________________________________________________
Number
45951
Version
12 from 11.06.2002
Set on
11.06.2002
Language
EN
Short text
Transporting class data: system / client
Component
CA-CL
Classification
________________________________________________________________________
Long text
Symptom
Use ALE to transport class data from client
to client or system to
system. This ensures consistent data (unlike
the client copy of class
data).
In contrast, you can only copy master data
and transaction data
completely for the client copy of class data,
and the target client m u
s t be e m p t y. Copying individual
class tables does not ensure
consistency of data.
Additional key words
Transport classes
Transport characteristics
Transport classification
OMGQ, ME179
Cause and preconditions
Assigned object dependencies can only be distributed
as of Release 3.1G.
Changes with the engineering change management
can only be distirbuted
as of Release 4.0B.
Solution
Maintain the partner profile and the port
(automatically or manually)
with Transaction SALE by choosing 'Communication'
in the hierarchy.
You may need to consult your system administrator
to do this.
Maintain the logical connection and the message
objects for distribution
by choosing 'Distribution customer model'
in the hierarchy.
The objects are CHRMAS (characteristics),
CLSMAS (classes), and CLFMAS
(classification). Please note that you can
only distribute
classification correctly if the classified
object is distributed first.
The distribution of classifications of class
type 013 and 014 is not
supported in IDoc type CLFMAS because of mass
problems.
Classifications for class type 100 cannot
be sent via ALE (CLFMAS).
By choosing 'Communication', you can check
the consistency of objects in
the source and target systems.
Select the object you want to check in Transaction
BALE. Choose 'Master
data', select the object you require, then
enter the range of the
objects to be distributed.
Under Help - R/3 (SAP) Library you can find
an overview on how to carry
out the ALE Customizing. It is located on
the path 'Cross Application ->
Business Framework Architecture (as of Release
4.0B) --> ALE Application
Link Enabling -> Quickstart'.
The required Customizing is explained by using
the material master as an
example. For your Customizing, replace message
type 'MATMAS' (for the
material master) with message types 'CHRMAS',
'CLSMAS', and 'CLFMAS'
(see above for more information).
(As of Release 4.6A, the following path exists:
Help - SAP Library -
BASIS - Middleware - ALE Application Link
Enabling: ALE Introduction /
ALE programming guide. You must set up ALE
for the message types CHRMAS,
CLSMAS, CLFMAS)
Source code corrections
________________________________________________________________________
Valid releases
Software Component
Release
from
to
SAP_APPL SAP Application
46C - 46C
46A - 46B
45A - 45B
40A - 40B
30B - 31I
X
________________________________________________________________________
Reference to related Notes
Number Short text
____________________________________________________________
138056 Customizing batch:
Sort rule / Selection class
93334 Transporting
characteristics of class SAP_KKR_CLASS
86900 Transport of
Release strategies (OMGQ,OMGS)
365604 FAQ: Release strategies
in purchasing
73012 Customizing
batch: Sort term/selection class
____________________________________________________________
|
|
Beam Back -> SAP Cafe for Basis Components |