Error encountered while running the TX: RSTCO_ADMIN

[] [] [] [] [] [] []

Symptom

Error encountered while running the TX: RSTCO_ADMIN.
Other terms

BI_TCO_ACTIVATION, 0TCTUSERNM, 0ORGUNIT
Reason and Prerequisites

Relevant for BI_CONT 7.0 release.
During the activation of the technical content, all necessary objects are collected for each BI object. The InfoObject 0INFOPROV does indirectly refer to 0TCTUSERNM (through the link 0INFOPROVI – 0TCTIFAREA – 0TCTUSERNM). The InfoObject 0TCTUSERNM has been changed in the BI Content for BI 7.0. The Attribute 0ORGUNIT has been removed from the attribute list. In the system if there is still an update rule, that uses the Attribute 0ORGUNIT.

Solution

Incase you have upgraded the system from 3.5 to 7.0 and have ran the TX: RSTCO_ADMIN and ended in errors.
In content release 3.5 0TCTUSERNM has an attribute 0ORGUNIT which is no
longer supported in 7.0 release.

Please follow the below mentioned steps to resolve the issue.
1)If there is existing transfer rules and update rules for the 0TCTUSERNM remove the same from the system and install the object from business content.
2)Go to table RSDCHABASLOC and Change CNVSTAT from 1 to 0 for 0TCTUSERNM.
Tx:se16 -> table rsdchabasloc enter chabasnm = 0TCTUSERNM, press f8, change CNVSTAT to 0, save and exit. Restart the activation in RSD1.
The field CNVSTAT resets the conversion state.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment