SAP OSS Notes

1263115 SAP OSS Note - Technical settings cannot be activated








SAP OSS Note 1263115 version 0004 contains details of a know issue related to Technical settings cannot be activated. This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 1263115 Details:






When does this problem occur

During the upgrade or an import, the following error message is contained in the log:
...
Table <(><<)>tabname> was deleted
...
Activate technical settings for <(><<)>tabname>
Table <(><<)>tabname> is not an active table
Technical settings for <(><<)>tabname> were not activated
...

The return code of the activation program is 8.

Description of problem

Mass activation, technical settings, DT610, DT22

Cause of the problem and Pre-requisites

The problem described in this note can occur only within a merge import of several transport requests. In this case, individual requests that contain the following individual actions are merged:
First, a table is transported with technical settings. The technical settings are then changed and are separately sent again. The table is then deleted.
As a summary, only the deletion of the table must be executed in this case, and not the activation of the subobjects that are also deleted when the table is deleted.

Solution instructions

If the problem has already occurred, you can ignore the relevant activation messages. When you repeat the activation process, the system will report the error again.
If the phase has to be completed successfully, you can temporarily recreate the table (with technical settings and indexes), execute the phase, and then delete the table manually.
Implement the specified correction instructions or import the relevant Support Package to prevent the problem from occurring.

Note 1263115 Correction instructions:



NOTE: Only source text changes are displayed here

*$*$----------------------------------------------------------------$*$*
*$ CORRECTION INSTRUCTIONS 0120031469 0000691857 $*
*$--------------------------------------------------------------------$*
*$ VALID FOR : $*
*$ Software Component SAP_BASIS SAP Basis component $*
*$ Release 711 To SAPKB71101 $*
*$*$----------------------------------------------------------------$*$*
*&---------------------------------------------------------------------*
*& Object REPS RADMASUTC
*& Object header PROG RADMASUTC
*&---------------------------------------------------------------------*
*& FORM MA_DEL_OBJ
*&---------------------------------------------------------------------*
...
delete adjacent duplicates from deltab
comparing objtyp objname indxname.
* For objects to delete and activate the activation-entry is stronger
loop at deltab.
*>>>> START OF DELETION <<<<<
read table gentab with key
*>>>> END OF DELETION <<<<<<<
*>>>> START OF INSERTION <<<<
perform ma_del_handle_part_objects tables gentab oktab
using deltab run.
read table gentab with key
*>>>> END OF INSERTION <<<<<<
...
*&---------------------------------------------------------------------*
*& FORM MA_DEL_HANDLE_PART_OBJECTS
*&---------------------------------------------------------------------*
*>>>> START OF INSERTION <<<<
*----------------------------------------------------------------------*
* Form MA_DEL_HANDLE_PART_OBJECTS
*----------------------------------------------------------------------*
* Handles the case that a table is deleted but a part object as
*Technical Settings or index exists to activate. The part object will be
* set to o.k. and no activatiopn started.
*----------------------------------------------------------------------*
* --> DELWA : Workarea with object to delete
* --> GENTAB : Tables with objects to activate
* <-- OKTAB : Objects which are fully activated and can therefore be
* set to o.k in the input-medium
*----------------------------------------------------------------------*
form ma_del_handle_part_objects tables gentab type gentb
oktab type oktb
using delwa type dcdeltb
run like ddrefstruc-bool.

data: obj_type like dcdeltb-objtyp,
ok_wa type okwa,
pos like syst-tabix.

check run = 1.
check delwa-objtyp = tabl.

obj_type = indx.
read table gentab with key
name = delwa-objname
type = obj_type.
if syst-subrc = 0.
pos = syst-tabix.
ok_wa-name = gentab-name.
ok_wa-indx = gentab-indx.
ok_wa-pgmid = gentab-pgmid.
ok_wa-type = gentab-type.
ok_wa-tabix = gentab-tabix.
ok_wa-nodoku = gentab-nodoku.
append ok_wa to oktab.
delete gentab index pos.
endif.

obj_type = tabt.
read table gentab with key
name = delwa-objname
type = obj_type.
if syst-subrc = 0.
pos = syst-tabix.
ok_wa-name = gentab-name.
ok_wa-indx = gentab-indx.
ok_wa-pgmid = gentab-pgmid.
ok_wa-type = gentab-type.
ok_wa-tabix = gentab-tabix.
ok_wa-nodoku = gentab-nodoku.
append ok_wa to oktab.
delete gentab index pos.
endif.

obj_type = xinx.
read table gentab with key
name = delwa-objname
type = obj_type.
if syst-subrc = 0.
pos = syst-tabix.
ok_wa-name = gentab-name.
ok_wa-indx = gentab-indx.
ok_wa-pgmid = gentab-pgmid.
ok_wa-type = gentab-type.
ok_wa-tabix = gentab-tabix.
ok_wa-nodoku = gentab-nodoku.
append ok_wa to oktab.
delete gentab index pos.
endif.

endform.

*>>>> END OF INSERTION <<<<<<
...
*&---------------------------------------------------------------------*

Effected Objects:


(REPS) - RADMASUTC

(REPS) - RADMASUTC

(REPS) - RADMASUTC

(REPS) - RADMASUTC

Solution instructions


Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 1263115 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 1263115 has already been downloaded and is valid


To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 1263115 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.



If note 1263115 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)