sapnote_0001413183(1)

26.04.2013 Page 1 of 8

SAP Note 1413183 - Problems during DTP transport incomplex landscapes

Note Language: English Version: 5 Validity: Valid Since 02.05.2011

Summary

SymptomIn complex system landscapes, or after you change these landscapes,problems may occur during the import of data transfer processes (DTPs) ordependent objects (process chains).

The majority of these problems occur when transport requests are importedinto a system from several source systems. Similar errors may occur whenyou import transports after you make a system copy.

Examples:

o Multilevel system landscape

The system landscape is a chain that consists of developmentsystem, quality system or quality systems, and production system.You now add new systems to this system landscape or you removeexisting systems from the chain.

- After you carry out the import again, DTPs (especially with theextraction mode "Full") are duplicated. The system may issueerror messages when process chains are imported (see below).

- When you try to import DTPs with the extraction mode "Delta",the system issues error message "Overlapping selection criteriawith DTP ...".

o Branched system landscape

The system landscape consists of a system A that supplies thesystems B and C, which branch out from A. You transport a DTPseparately into the systems B and C (that is, A->B or A->C).

- Afterwards, you import a process chain, which references theDTP, from the system B into the system C. If the DTP istransported at the same time, no problems occur. However, ifthe process chain is transported from B to C without a DTP, thesystem issues the error message "Process variant DTP_LOAD ...does not exist in version A" even though the corresponding DTPexists in all three systems (A, B, and C) in an active version.

- The DTPs have the extraction mode "Delta". If you change thefilter criteria of the DTP in system B and you transport thesechanges to system C, the existing DTP is not changed in systemC during the import; instead, the system creates a new DTP.When this DTP, which was incorrectly created, is activated, thesystem may issue the following error message: "Overlappingselection criteria with DTP ...".

Other termsRSPC097, RSPC 097, RSBK019, RSBK 019

Reason and Prerequisites

26.04.2013 Page 2 of 8


SolutionThis correction improves stability when DTPs are transported.

Detailed technical description:

Behavior before you implement the correction:

It is assumed that in the target system, no DTPs currently exist between aspecific source and a specific target. When a DTP (DTP1) is imported intothe target system for the first time, a new DTP with a new GUID that has 25characters (which differs from the GUID of the DTP in the source system) iscreated in the target system (DTP2). The connection between the DTPs in thesource system and in the target system of the transport is created throughan entry in the header table of the DTP that is created in the targetsystem (DTP2). In this header table entry, the GUID of the DTP from thesource system is saved as a pointer (database table RSBKDTP, fieldDTP_ORIGINAL='DTP1'). As a result, the system identifies this DTP as beingrelated to DTP2 when DTP1 is imported into the target system again, and thesystem transfers the transported changes to DTP2.

The pointer DTP_ORIGINAL is put in parentheses in the following example:

Source system Target systemDTP1 -> DTP2(DTP1)DTP3 -> DTP4(DTP3)

If you import a different DTP between the same source and the same target(DTP3) into the target system, the system behaves as follows:

o DTP has the extraction mode "Full":

A new DTP (DTP4) is created in the target system.

o DTP has the extraction mode "Delta":

System behavior differs depending on the filter criteria of theDTPs in the source system and the target system:

- If the filter criteria of DTP2 and DTP3 are disjunct, a newDTP4 is created and activated.

- If DTP2 and DTP3 have the same filter criteria, the systemtransfers the changes that are included in DTP3 to DTP2.

- If the filter criteria of DTP2 and DTP3 overlap, the systemcreates DTP4 but it does not activate it.

If you have multilevel system landscapes (more than two systems in achain), the reference to DTP1 in the original system is lost with thesystem behavior described above.

In the following example, the DTP in the development system is called DTPE,the DTP in the quality system is called DTPQ, and the DTP in the productionsystem is called DTPP. The DTP is first transported from the developmentsystem to the quality system and then from the quality system to the

26.04.2013 Page 3 of 8


production system. The pointers DTP_ORIGINAL are put in parentheses:

Development system Quality system Production systemDTPE1 -> DTPQ1(DTPE1) -> DTPP1(DTPQ1)DTPE2 -> DTPQ2(DTPE2) -> DTPP2(DTPQ2)

Behavior after you implement the correction:

When you import a new DTP, the GUID of this DTP is transferred to thetarget system and no new GUID is issued.The following applies for DTPs that have a DataSource as the source: If youhave a DataSource that is distributed to several target source systems inthe target systems of a transport using 1:n, the first source systemassignment to the DataSource receives the GUID of the original DTP of thetransport. The system then takes a new GUID for all further source systemconnections and saves the reference to the original DTP in the fieldDTP_ORIGINAL.

If the exported DTP was originally created by importing another DTP, thereference DTP_ORIGINAL of the exported DTP is also passed on to the DTP inthe target system. For DTPs that were created by a transport before youimplemented these corrections, the DTP_ORIGINAL pointer can be corrected inconjunction with the new system behavior so that it can be propagated by anew transport request that is created after you implement the corrections.

To demonstrate these changes, it is assumed that the DTPs DTPE1, DTPQ1, andDTPP1 in the above example are created before you implement thecorrections. If DTPE1 (or DTPQ1) is transported through the entire systemlandscape again after you implement the corrections, the pointerDTP_ORIGINAL of DTPP1 in the production system then points to DTPE1:

Development system Quality system Production systemDTPE1 -> DTPQ1(DTPE1) -> DTPP1(DTPE1)

If DTPE1 is exported only after you implement the corrections, the GUIDassignment (and the pointer assignment DTP_ORIGINAL) is as follows:

Development system Quality system Production systemDTPE1 -> DTPE1(DTPE1) -> DTPE1(DTPE1)

Additional information:

o The GUIDs of DTPs that are created by an import before youimplement the corrections are not changed. The fact that the DTPskeep their name in the target system applies only for new DTPs(that is, those DTPs that are exported and imported for the firsttime after implementing the corrections provided by this note).

o When you display the overview information in DTP maintenance (menu"Goto -> Overview of DTP"), the GUID of the original DTP is nowalso displayed for imported DTPs.

o You have the option of limiting the number of "Full" DTPs for asource/target/filter criteria combination in the target system ofthe transport (similar to the "Delta" DTP). To make this

26.04.2013 Page 4 of 8


restriction, create an entry in the table RSBKADMIN with the object'DTP_MATCH_FULL_AFTERIMP' and the value 'X' in the respectivetarget system of the transport.

o The after import of the DTP uses the existing DTPs to check theimported DTPs according to the following rules:

- O: The system searches for DTPs that reference the imported DTP(that is, DTP_ORIGINAL=imported DTP).

- I: The system searches for a DTP that has the GUID of theimported DTP.

- P: The system searches for DTPs that point to the same DTP asthe imported DTP (that is, those that have aDTP_ORIGINAL=DTP_ORGINAL of the imported DTP).

The default sequence for the call of the methods when importingDTPs is as follows: P,O,I. When DTP deletions are imported, thesequence is reversed: I,O,P. You can change the call sequence forthese methods using two RSBKADMIN entries:

- Object='DTPA_MATCH_ORDER_INS' for the importwith the default value POI

- Object='DTPA_MATCH_ORDER_DEL' for the deletionwith the default value IOP

You can also use these entries to control which of these methodsare called.

Recommended procedure:

The objective of this correction is the following system behavior: In yourentire system landscape, all DTPs that have the same combination of source,target, extraction mode, and filter criteria, are assigned to a singleoriginal DTP (this is not mandatory for "Full" DTPs).After you implement the corrections, the GUIDs of the new DTPs are nolonger system-dependent. Exception: DataSources in the scenario describedabove. You can then change a DTP in several systems (including the filtercriteria of "Delta" DTPs), and afterwards import it from several sourcesystems (old and new development systems) into a target system (productionsystem) without producing DTP duplicates or causing other conflicts duringthe import.

1. If undesired DTP duplicates exist in a system after the import (forexample, several DTPs for the same combination of DTP source, DTPtarget, extraction mode, and filter criteria), delete these DTPs. Makesure that the systems can be changed for the duration of thisactivity.

2. Implement this note in all systems of your system landscape.

3. If you want to reorganize a system landscape, adhere to the followingprocedure. We assume that you have the following scenario: Aproduction system is supplied with data from a development system(development system "old"). You want to change to a new development

26.04.2013 Page 5 of 8


system (development system "new"), from which the production system isto be supplied (after a transition period). In this case, note thefollowing procedure:

a) The "new" development system must be created as a system copy ofthe "old" development system. Alternatively, you must use atransport to replicate the DTPs that exist in the "old" developmentsystem to the "new" development system; you must not create themagain in the "new" development system.

b) During the transition period, that is, as long as the developmentsystems "old" and "new" exist at the same time and the productionsystem is still supplied with data from the "old" developmentsystem, you must transport all new DTPs that you create in the"old" development system to the "new" development system.

Additional information about step a and b:These two measures ensure that a corresponding DTP exists in the"new" development system for all DTPs from the "old" developmentsystem (the DTP in the "new" development system has DTP_ORIGINAL =the corresponding DTP from the "old" development system).

c) Before you switch the supply of data to the production system fromthe "old" development system to the "new" development system, youmust first transport all DTPs from the "old" development systemthrough the existing system landscape to the production system.Then transport all DTPs from the "new" development system throughthe existing system landscape to the last quality system before theproduction system. Afterwards, you can finalize the reorganizationof your system landscape from "old" to "new".

As a result, all imported DTPs (in the "new" development system,all quality systems, and the production system) are divided intotwo categories:

- DTPs that have an original DTP from the "old" developmentsystem

You can also maintain these DTPs in the "new" developmentsystem after the reorganization without triggering thegeneration of DTP duplicates during the import into theproduction system.

- DTPs that have an original DTP from the "new" developmentsystem

These DTPs were generated in the "new" development system andwere imported into the production system only after thereorganization.

Implement the corrections

o SAP NetWeaver BW 7.00

Import Support Package 24 for SAP NetWeaver BW 7.00 (SAPKW70024)into your BW system. The Support Package is available when Note1407598 "SAPBINews NW BI 7.0 ABAP SP24", which describes thisSupport Package in more detail, is released for customers.

26.04.2013 Page 6 of 8


o SAP NetWeaver BW 7.01 (SAP NW BW 7.0 Enhancement Package 1)

Import Support Package 07 for SAP NetWeaver BW 7.01 (SAPKW70107)into your BW system. The Support Package is available when Note 1369294 "SAPBINews NW BI 7.01 ABAP SP07", which describes thisSupport Package in more detail, is released for customers.

o SAP NetWeaver BW 7.02 (SAP NW BW 7.0 Enhancement Package 2)






In urgent cases, you can implement the correction instructions as anadvance correction.

You must first read Note 875986, which provides informationabout transaction SNOTE.

To provide information in advance, the notes mentioned above may already beavailable before the Support Package is released. In this case, the shorttext of the note contains the words "Preliminary version".

------------------------------------------------------------------------|Manual Pre-Implement. |------------------------------------------------------------------------|VALID FOR ||Software Component SAP_BW Business Inform...|| Release 700 SAPKW70019 - SAPKW70023 || Release 711 SAPKW71102 - SAPKW71104 || Release 701 SAPKW70103 - SAPKW70106 || Release 702 SAPKW70202 - SAPKW70202 || Release 720 SAPKW72002 - SAPKW72002 |------------------------------------------------------------------------

26.04.2013 Page 7 of 8


o Enhance the structure (data type) RSBKDYNP201 in the ABAPDictionary (transaction SE11). Insert a new component between"DATUM" and ".INCLUDE". The new component has the nameDTP_ORIGINAL, the type category TYPE, and the component typeRSBKDTPNM. Save and activate the structure.

o Create the new text symbol 042. Call transaction SE38. Enter theprogram name SAPLRSBK_GUI and select "Text elements". Create thetext symbol 042 with the description "Original DTP". Set themaximum length to 16, save and activate the text elements.

Header Data

Release Status: Released for CustomerReleased on: 02.05.2011 09:02:20Master Language: GermanPriority: Correction with medium priorityCategory: Program errorPrimary Component: BW-WHM-DST-DTP Data Transfer Process

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_BW 70 700 702

SAP_BW 71 711 720

SAP_BW_VIRTUAL_COMP 70 701 701 701

Support Packages

Support Packages Release Package Name

SAP_BW 700 SAPKW70024





SAP_BW_VIRTUAL_COMP 701 SAPK-70114INVCBWTECH

Related Notes

Number Short Text

1407600 SAPBWNews NW BW 7.02 ABAP SP03

1407599 Preliminary Version SAPBWNews NW BW 7.20 ABAP SP03

1407598 SAPBWNews NW BW 7.0 ABAP SP 24

1369294 SAPBINews NW7.01 BW ABAP Support Package 07

1260071 SAPBINews NW 7.10 BI ABAP Support Package 08

Attributes

26.04.2013 Page 8 of 8


Attribute Value

DownPort/UpPort-WF UpPort check necessary

Symptoms - Side-Effects

The following SAP Notes correct this SAP Note / patch:

SAP NoteReason

Versionfrom

Versionto

SAP NoteSolution

Version SupportPackage

1413183 1431614 1

Correction Instructions

CorrectionInstructions

Validfrom

Validto

SoftwareComponent

Type*)

ReferenceCorrection

LastChanged

1167704 720 720 SAP_BW C BI8K004538 08.12.200905:01:04

1167707 711 711 SAP_BW C BROK009534 08.12.200905:01:49

1167708 700 702 SAP_BW C BR9K086243 06.01.201022:01:06

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work

Documents

sapnote_0001413183(1)