oss note 0164222

8/9/2019 Oss Note 0164222

http://slidepdf.com/reader/full/oss-note-0164222 1/5

22.04.2007 of 5

SAP Note Number 164222 - Transporting overhead rates of the costingsheet Note Language: English Version: 8 Validity: Valid from 25.01.2007

Summary

SymptomWhen you transport the overhead rates of the costing sheet, an automatic

postprocessing of the transported overhead rates starts up during the

import. This postprocessing converts numbers assigned internally and moves

the overhead rates from the transported table to the overhead tables of the

costing sheet in question in the target system.

In general it cannot be defined for postprocessing methods in which client

of the target system these are executed during import. The automatic

postprocessing of the transported client-specific overhead rates is stopped

if they are executed in the import client. The transport is ended with

Return Code 4 and Message KA442 is included in the transport log. As you

can see from the long text of the message you must now manually execute the

postprocessing in the import client.

First make sure that all other steps of the transport request were ended

successfully. If errors occurred for other objects which are contained in

the transport request, eliminate these first.

Using Transaction SE38 start Report RKAZUTR1 in the client of the target

system, in which the overhead rates should be imported, to manually

postprocess the transport of overhead rates. Transfer as a parameter the

request number of the transport in which the overhead rates were included

during maintenance.

The successful execution of Report RKAZUTR1 is confirmed with MessageKA444. All transported overhead rates are in the costing sheet of the

target client, the transported table was cleared of these rates. The

transport of the overhead rates has been closed successfully.

For technical reasons Message KA442 in the transport log remains unchanged

after successful manual postprocessing of the transport by Report RKAZUTR1.

Description of the step-by-step manual procedure

1. Create a transport request

a) Choose entry 'Table view > Transport' from the menu of the

maintenance of the percentage (KZZ2) or quantity-based (KZM2)

overhead.

==> You change from the maintenance view to the transport view.

b) Select or create a Customizing Transport Request.

c) Select an overhead to include this overhead and all overhead rates

of the overhead in the transport request, or alternatively, select

individual overhead rates (in detail screen) to only include these

rates and the definition of the superior overhead in the transport

request.

d) Press pushbutton 'Include in request'.

8/9/2019 Oss Note 0164222


22.04.2007 of 5

SAP Note Number 164222 - Transporting overhead rates of the costingsheet

==> The overhead is flagged as a superior entry for marked overhead

rates - for marked overhead, all overhead rates for the overhead

are flagged as dependent entries. The particular number results

from the information message.

e) If all required entries are flagged, save.

==> You can only create and view a transport request if you save it

first (Transaction SE10).

f) You can change from the transport view into the maintenance view by

selecting Menu Option 'Table view > Display -> Change'.

2. Carry out the export from the source system and the import into the

target system. Source and target systems can also be different clients

of one system.

3. Postprocessing of transport

a) Check the transport log. If the manual postprocessing of thetransport is necessary since the automatic postprocessing was

unsuccessful, you will find Message KA442 ('Postprocessing in

incorrect client -> Start Report RKAZUTR1') in the transport log.

The transport was ended with Return Code 4. If these prerequisites

are not fulfilled, the successful import of the overhead rates into

the target system has already been carried out.

b) Start Report RKAZUTR1 for manual postprocessing with Transaction

SE38 in the target system and enter the transport order number.

c) If imported overhead rates exist, these are transferred into the

tables of the costing sheet when executing the report. Report

RKAZUTR1 ends with Message KA444 after successful execution.

Prerequisites

o In the source system, the indicator 'Running Setting' must not be

set in View V_KONX (as of Notes 709504, 733777 and 820955). The

indicator will be edited to Object V_KONX in the detail screen of

the header data using Transaction SOBJ (as of Release 4.5, see Note

301665).

o In the source system the switch must be set to 'Recording Routine'

in the setting 'No or Individual Recording Routine'. This setting

is carried out in Transaction SE54 > Generated Objects.

In SAP-standard outbound delivery both settings are already

correctly set.

Transporting deletions

New entries, changes and deletions of the overhead rates are automatically

dealt with correctly in clients with automatic recording.

If you do not use automatic recording, transport a deletion by first

including an existing overhead rate in the transport request. If this

8/9/2019 Oss Note 0164222


22.04.2007 of 5

SAP Note Number 164222 - Transporting overhead rates of the costingsheetoverhead rate is deleted afterwards and the costing sheet saved, the

deletion is taken into account in the transport request.

Transport in a cascade

The transported table is cleared of the affected overhead rates duringpostprocessing: the transport entries to be processed are converted by

executing Report RKAZUTR1 in the import client and they are deleted from

the transport table. The cleanup of the transported table is necessary to

prevent multiple postprocessing of the same transport request and an

excessive growth of the table size.

If the same transport is now distributed to other systems or clients, the

overhead rates are no longer contained. After you executed Report RKAZUTR1

start the transport request again in every system in which you imported

overhead rates and from which these rates should be exported again where

the overhead rates are affected.

Alternatively you can use Report RKAZUTR1 to initiate the transfer of the

transport request in subsequent systems prior to executing the post

processing. However, this procedure can only be used if postprocessing was

not executed automatically.

Error Message KA443: No entries for the order number found

The postprocessing processes all overhead rates which were entered for the

specified transport request. You receive Error Message KA443 if no records

are found in the transported table for the request number. The possible

causes are:

o No overhead rates were included in the transport request.

o Specification of an incorrect transport request number. Using

Transaction SE10 check which number the required transport request

has. Make sure that the required overhead rates were actually

maintained under the determined transport request number. The

specification of an incorrect transport request number in Report

RKAZUTR1 can cause an unwanted change to your overhead rates.

o The transport request number with which the overhead rates were

placed in the transported table and the transport request number

with which the transport was carried out into the target system are

not the same. This occurs if a client copy was carried out inaccordance with the transport request or the individual transports

with which the overhead rates were maintained, were combined in an

object list to a new transport request. To eliminate a program

error, read Note 163301.

Correction report

Inconsistencies can occur in the database tables after incorrect or

incomplete transports, causing errors in the overhead calculation.

Correction Report RKZUKO00 corrects or deletes the inconsistent parts of

the costing sheet. Bear in mind that it is only as of Release 4.6 that

Report RKZUKO00 has the possibility of a test run and to list the deleted

and changed data.

8/9/2019 Oss Note 0164222


22.04.2007 of 5

SAP Note Number 164222 - Transporting overhead rates of the costingsheetThe transported overhead rates are set out in Table TKZUTR. Postprocessed

rates are removed, rates not processed remain in Table TKZUTR. The table is

used for transport, not for current operations. You do not need to delete

overhead rates which were not processed. Should you require this anyway,

you can use the following Report Z_DEL_TKZUTR for the deletion of overhead

rates via the selected transport request number.

More TermsCosting sheet, percentage overhead, quantity-based overhead, overhead

rates, method execution, postprocessing

KZZ2, KZM2, KZS2, STMS, SAPL0COE

Cause and PrerequisitesTransport of overhead rates

Solution

Consulting note

Header Data

Release Status: Released for CustomerReleased on: 25.01.2007 12:50:03Priority: Recommendations/additional infoCategory: Consulting

Main Component CO-OM-OPA-F Period-end Closing

Valid Releases

Software Component Release FromRelease

To Release and Later

SAP_APPL 40 40A 40B X



SAP_APPL 46C 46C 46C X

SAP_APPL 470 470 470 XSAP_APPL 500 500 500 X

SAP_APPL 600 600 600 X

SAP_BASIS 46C 46D 46D X

Support Packages

8/9/2019 Oss Note 0164222


22.04.2007 of 5

SAP Note Number 164222 - Transporting overhead rates of the costingsheetSupport Packages Release Package Name

SAP_APPL 46A SAPKH46A02

Related Notes

Number Short Text397799 INFORMATION: CO-OM-OPA (Order & Project Accounting)

301665 Costing sheet: overhead rates in live system

208474 Costing sheet: batch input of the overhead rates

175853 Correction report for costing sheet RKZUKO00_UPD

173857 Newly created overhead rates are not transported

163301 Transport.overhd records w/ client copy/obj. list

126551 Composite note: Customizing of costing sheet

Correction Instructions

CorrectionInstructions

Validfrom

Validto

SoftwareComponent

Type*)

ReferenceCorrection

LastChange

2403 45A 45A SAP_APPL C 30.07.1999 03:09:20

*) C Correction; B Pre-Implementation Step; A Post-Implementation Step; M Step Not DeterminedYet

oss note 0164222

Documents