sapnote_0000616836
3
06/11/2013 Page 1 of 3 SAP Note 616836 - Misleading object types in BW transport logs Note Language: English Version: 2 Validity: Valid Since 04/24/2003 Summary Symptom When you transport BW objects, misleading messages appear about the object type in the log display of the method execution. In particular, error messages are displayed for the wrong object type. These are the messages o Message no. PU122 "Subsequent processing RS_AFTER_IMPORT for <TLOGO> L started at hh:mm:ss" o Message no. PU133 "Errors occurred during post-handling RS_AFTER_IMPORT for <TLOGO> L" <TLOGO> stands for a BW (transport-) object type (for example CUBE, IOBJ, ELEM, AREA, ...). The errors, however, occurred for another object type. For example the message "Errors occurred during post-handling RS_AFTER_IMPORT for CUBE L" could appear, although actually an error has only occurred during the processing of InfoObjects. Other terms PU 122, RS_AFTER_IMPORT, TLOGO, logical transport object Reason and Prerequisites All BW objects are handled by the same after import method RS_AFTER_IMPORT, to adhere to the correct sequence during the activation. Messages PU122 and PU133 are sent by the Basis transport framework. The object type is then selected by chance from the group of objects involved. (Generally, an after import method only works for one object type, so that no misunderstandings arise. In BW this does not apply for the reasons given above). This object type is not necessarily the object type for which errors occurred during the method execution. Solution Procedure before the Support Packages specified below Expand the log by clicking on the character on the left beside message PU122. You will then see BW-specific messages on the object types to be processed - for example, message no. R7501 "Start of the after import method for object type R3TR <TLOGO> (activation mode)". In this view the error messages are each assigned to the correct object type. Alternatively, you can use the correction instructions, which you can implement in your system using transaction SNOTE. New correctly formatted logs are then set up. Correction of the log display With the Support Packages given below, the new logs are formatted differently. You will then see the error messages immediately assigned correctly to the object types.
description
SAP NOTE
Transcript of sapnote_0000616836
06/11/2013 Page 1 of 3
SAP Note 616836 - Misleading object types in BW transportlogs
Note Language: English Version: 2 Validity: Valid Since 04/24/2003
Summary
SymptomWhen you transport BW objects, misleading messages appear about the objecttype in the log display of the method execution. In particular, errormessages are displayed for the wrong object type.These are the messages
o Message no. PU122 "Subsequent processing RS_AFTER_IMPORT for<TLOGO> L started at hh:mm:ss"
o Message no. PU133 "Errors occurred during post-handlingRS_AFTER_IMPORT for <TLOGO> L"
<TLOGO> stands for a BW (transport-) object type (for example CUBE, IOBJ,ELEM, AREA, ...).The errors, however, occurred for another object type. For example themessage "Errors occurred during post-handling RS_AFTER_IMPORT for CUBE L"could appear, although actually an error has only occurred during theprocessing of InfoObjects.
Other termsPU 122, RS_AFTER_IMPORT, TLOGO, logical transport object
Reason and PrerequisitesAll BW objects are handled by the same after import method RS_AFTER_IMPORT,to adhere to the correct sequence during the activation.Messages PU122 and PU133 are sent by the Basis transport framework. Theobject type is then selected by chance from the group of objects involved.(Generally, an after import method only works for one object type, so thatno misunderstandings arise. In BW this does not apply for the reasons givenabove). This object type is not necessarily the object type for whicherrors occurred during the method execution.
Solution
Procedure before the Support Packages specified below
Expand the log by clicking on the character on the left beside messagePU122. You will then see BW-specific messages on the object types to beprocessed - for example, message no. R7501 "Start of the after importmethod for object type R3TR <TLOGO> (activation mode)". In this view theerror messages are each assigned to the correct object type.Alternatively, you can use the correction instructions, which you canimplement in your system using transaction SNOTE. New correctly formattedlogs are then set up.
Correction of the log display
With the Support Packages given below, the new logs are formatteddifferently. You will then see the error messages immediately assignedcorrectly to the object types.
06/11/2013 Page 2 of 3
SAP Note 616836 - Misleading object types in BW transportlogs
o BW2.0B
Import Support Package 32 for 2.0B (BW2.0B Patch32 or SAPKW20B32)into your BW System. The Support Package is available when note0523191 with the short text "SAPBWNews BW 2.0B Support Package32", which describes this Support Package in more detail, isreleased for customers.
Note 0523191 may already be available before the Support Package isreleased, to make information available in advance. However, theshort text then also contains the words "preliminary version".
o BW2.1C
Import Support Package 24 for 2.1C (BW2.1C Patch24 or SAPKW21C24)into your BW System. The Support Package is available when note0523204 with the short text "SAPBWNews BW 2.1C Support Package24" is released for customers.
o BW3.0B
Import Support Package 09 for 3.0B (BW3.0B Patch09 or SAPKW30B09)into your BW System. The Support Package is available when note523243 with the short text "SAPBWNews BW 3.0B Support Package09", which describes this Support Package in more detail, isreleased for customers.
Note 0523243 may already be available before the Support Package isreleased, to make information available in advance. However, theshort text then still contains the words "preliminary version".
o BW3.1C
Import Support Package 03 for 3.1C (BW3.1C Patch03 or SAPKW31C03)into your BW System. The Support Package is available when note0539820 with the short text "SAPBWNews BW 3.1C Support Package03", which describes this Support Package in more detail, isreleased for customers. See note 110934, which contains furtherinformation on BW Support Packages.
Header Data
Release Status: Released for CustomerReleased on: 04/24/2003 11:12:59Master Language: GermanPriority: Correction with low priorityCategory: Program errorPrimary Component: BW-WHM Data Warehouse Management
Secondary Components:BW-SYS Basis System and Installation
BW-BEX-ET Enduser Technology
BW-WHM-MTD-CTS Transport connection
06/11/2013 Page 3 of 3
SAP Note 616836 - Misleading object types in BW transportlogs
Valid Releases
Software Component Release FromRelease
ToRelease
andSubsequent
SAP_BW 20 20B 20B
SAP_BW 21 21C 21C
SAP_BW 30 30A 30B
SAP_BW 310 310 310
Correction Instructions
CorrectionInstructions
Validfrom
Validto
SoftwareComponent
Type*)
ReferenceCorrection
LastChanged
547566 20B 21C SAP_BW C J10K013250 04/24/200304:48:37
547671 30A 310 SAP_BW C 04/24/200305:03:09
*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work
