Ansicht
Dokumentation

RSDG_REORG_TADIR_BW_OBJECTS - Conversion of the TADIR entries of BW meta objects to 2.0

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Purpose

Following an upgrade to 2.0 a customer must carry out a repair program. Program Nr.1 should only run in the customer's development system. It repairs the object catalog (TADIR) for the activated content objects. The TADIR entries for the A version of SAP content objects are corrected. These TADIR entries have SAP as an original, but belong to the customer after the new delivery logic. As an entry the program eceives a customer development class <> $TMP and a person responsible. The TADIR entries for the content objects are then modified in the following ways:

The original system is set to the current system

The development class is filled form the entry

The person responsible is filled from the entry

The original language is set to the logon language

In addition all changed TADIR entries are written to an order. This order must be transported in all later systems so that correct entries are also available there.

This program can only run in development systems, as the original location of the object is here. A warning is given if a system other than the development system is invloved. There can, however, be customers who only have a productive system. In every case the upgrade guide or documentation must therefore be refered to. A check should be made that the new development class has a transport layer equivalent to the old one.

The second correction program should run in all customer systems. Two actions are carried out:

All TADIR entries from old SAP A Content objects for which no A version exists will be deleted.

A local TADIR entry is created for all BW customer objects without a TADIR entry,. Entry is here for every person responsible.

The original system is set to the current system (objects without TADIR entry have not yet been transported. The original system is consequently the current system)

The development class is set to $TMP

The person responsible is filled from the entry

The original language is set to the logon language

Integration

Prerequisites

The program can only be executed after the upgrade to 2.0.

Features

Selection

Standard Variants

Output

Activities

Example

Addresses (Business Address Services)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 2576 Date: 20240520 Time: 110428     sap01-206 ( 52 ms )