Show TOC
Copy Operating
Concern including Customizing
In this IMG activity, you can create an
operating concern by copying an existing one. There are three ways you can do
this:
Note: This step is not intended to be used as a
means of creating backup copies of operating concerns that could be imported
if needed. No transaction data is copied in this step!
1. Import
operating concern
This function lets
you copy the customizing settings for an operating concern to another client.
In particular, you can use this function to copy one of the standard
"templates" from client 000 to your test client.
Note: Unlike the
function
Import objects , this function copies ALL the settings for the
operating concern, not just individual objects.
The logic for
copying settings is different from the logic for transporting in that settings
that simply reference the operating concern instead of being dependent on it
(such as PA transfer structures) are copied as well. To avoid inadvertently
overwriting settings in the target client, you should only use this function
when the target client does not contain any customizing settings yet, or when
you want customizing in the source and target clients to be
identical.
1. Copy
operating concern
This function lets
you copy an entire operating concern within the same client. You can choose
whether you want to copy the data structures only, the customizing settings
only, or both. These are copied in separate steps.
a) First you
need to copy the data structures. When you do so, you can decide whether the
(cross-client) environment should be generated automatically or not. If you
want to make changes to the new operating concern after copying it, you should
generate the environment later.
Note: To copy the
data structures, you must enter a target operating concern name does not yet
exist.
b) Once you
have done this you can copy the customizing settings. You can also repeat this
step as often as required. The data structures in the target operating concern
must be active, and they must at least contain the same
characteristics and value fields as the source operating concern.
If you repeat the
copy, the system overwrites any existing settings.
2. Copy
specific objects
This special
function lets you copy specific customizing settings between clients or
between operating concerns within one client. To do so, you must collect all
the relevant tables in a transport request using the transaction
Transport objects or the manual transport function in the
transaction for each setting. Do NOT release the request.
When you call up this function, enter the number of the TASK (not the
request). The source client is determined based on the client the transport
request is defined for. If you are copying between clients, you cannot change
the operating concern. If you are copying between operating concerns, they
must be in the same client.
Caution: The system cannot automatically check whether all the table
entries in the transport request belong to the specified source operating
concern. You need to pay special attention to this when you use this
function.
Log
display
For each copying
action, the system writes a log in the application log. You can display these
logs at any time using transaction SLG1. Use the object "COG_PA" and the
subobjects "IMPORT" (Import operating concern) and "COPY" (copy operating
concern and copy specific objects).
When you import
an operating concern (SAP template), you need to generate the operating
concern's environment. In addition, you need to maintain the record types and
number ranges.