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. Itrepairs the object catalog (TADIR) for the activated content objects.The TADIR entries for the A version of SAP content objects arecorrected. These TADIR entries have SAP as an original, but belong tothe customer after the new delivery logic. As an entry the programeceives a customer development class <> $TMP and a person responsible.The TADIR entries for the content objects are then modified in thefollowing 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. Thisorder must be transported in all later systems so that correct entriesare also available there.
This program can only run in development systems, as the originallocation of the object is here. A warning is given if a system otherthan the development system is invloved. There can, however, becustomers who only have a productive system. In every case the upgradeguide or documentation must therefore be refered to. A check should bemade that the new development class has a transport layer equivalent tothe old one.
The second correction program should run in all customer systems. Twoactions are carried out:
All TADIR entries from old SAP A Content objects for which no A versionexists will be deleted.
A local TADIR entry is created for all BW customer objects without aTADIR entry,. Entry is here for every person responsible.
The original system is set to the current system (objects without TADIRentry have not yet been transported. The original system isconsequently 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

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

Features