cancel
Showing results for 
Search instead for 
Did you mean: 

Table "RMAN_PRSP_OPER_LIST_TYPE_ST" could not be activated

Former Member
0 Kudos

Hi

During phase ACT_UPG i'm stuck with activation error.

1EEDO519X"Table" "RMAN_PRSP_OPER_LIST_TYPE_ST" could not be activated

The really big problem is that this data type is not mentioned in SAP Note 1143022.

Further investigation shows that structure "RMAN_PRSP_OPER_LIST_TYPE_ST" involves field MATNR and also an include for "RMAN_PRSP_PROBLEM_DETAILS_TT" which also has field MATNR !!!

Manual activation result:

-


=========================================================================

Activation of worklist (DDIC / 07.04.2011 / 09:52:33 /)

=========================================================================

-


Technical log for mass activation

See log DDIC20110407095233:ACT

-


TABL RMAN_PRSP_OPER_LIST_TYPE_ST was not activated

Check table RMAN_PRSP_OPER_LIST_TYPE_ST (DDIC/07.04.11/09:52)

Field MATNR in table RMAN_PRSP_OPER_LIST_TYPE_ST is specified twice. Please check

Field name PRESUC_TAB can be provided in this system. Please do not use.

Field name PREDEC_PROBLEM_TAB can be provided in this system. Please do not use.

Exactly one field TXTSP of type LANG: Selection as text language possible

RMAN_PRSP_OPER_LIST_TYPE_ST-CONF_TYPE: Table SYST in search help attachment differs from table of search field

RMAN_PRSP_OPER_LIST_TYPE_ST-PROJN: Table VSOPRINF in search help attachment differs from table of search field

RMAN_PRSP_OPER_LIST_TYPE_ST-PRZ01: Table CAUFVD in search help attachment differs from table of search field

Check on table RMAN_PRSP_OPER_LIST_TYPE_ST resulted in errors

-


=========================================================================

End of activation of worklist

| =========================================================================

Anyone with a workable solution

best regards

Mads Hammer

Accepted Solutions (0)

Answers (2)

Answers (2)

tomas_black
Employee
Employee
0 Kudos

Hello Mads,

it's never advisable to ignore the errors and proceed, unless specified in a SAP note. If you don't get a timely answere in SDN forums, don't hesitate in opening an OSS message in order to have a consultant logged on and checking your system.

Regarding the problem: as you correctly identified, there's an extra MATNR field on the customer include. Please delete it and do a syntax check again on this table. Please pay attention to other duplicated fields on this table. If there're no more, the other errors will likely disappear.

Then you should be good to proceed.

Best regards,

Tomas Black

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Try to use option Accept non-severe errors and continue with the upgrade.

Thanks

Sunny

Former Member
0 Kudos

Hi

That is also what I decided to do.

best regards

Mads Hammer