Skip to Content
0
Former Member
Aug 28, 2008 at 06:29 PM

Infospoke Activation Problems after Upgrade

36 Views

Hi All,

We recently upgraded the BW system from 3.1 to 7.0 version.

After the upgrade here in the Dev it is the copy of the Quality. So in the infospoke i need to change the application server so that the default directory can come in the default destination path.

Now when i try to change and activate the infospoke i am facing the dump it states that as pasted below kindly help me

SAP_BW support pack is SP 15

Runtime Errors GETWA_NOT_ASSIGNED

Date and Time 08/28/2008 11:40:06

Short text

Field symbol has not yet been assigned.

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_RSO_TLOGO_COLLECTION=======CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

You attempted to access an unassigned field symbol

(data segment 32779).

This error may occur if

- You address a typed field symbol before it has been set with

ASSIGN

- You address a field symbol that pointed to the line of an

internal table that was deleted

- You address a field symbol that was previously reset using

UNASSIGN or that pointed to a local field that no

longer exists

- You address a global function interface, although the

respective function module is not active - that is, is

not in the list of active calls. The list of active calls

can be taken from this short dump.

How to correct the error

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"GETWA_NOT_ASSIGNED" " "

"CL_RSO_TLOGO_COLLECTION=======CP" or "CL_RSO_TLOGO_COLLECTION=======CM009"

"ACTIVATE_INTERNAL"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP-Release 700

Application server... "dneomp17"

Network address...... "172.22.112.69"

Operating system..... "AIX"

Release.............. "5.3"

Hardware type........ "00CA6DE04C00"

Character length.... 8 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "dneomp17"

Database type..... "ORACLE"

Database name..... "CBR"

Database user ID.. "SAPR3"

Char.set.... "en_US.ISO8859-1"

SAP kernel....... 700

created (date)... "Feb 3 2008 20:53:59"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 146

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Memory consumption

Roll.... 16128

EM...... 8379840

Heap.... 0

Page.... 57344

MM Used. 2816360

MM Free. 1371032

User and Transaction

Client.............. 300

User................ "HENDEDJ"

Language key........ "E"

Transaction......... "RSBO "

Transactions ID..... "48B555B3880A010EE1008000AC167045"

Program............. "CL_RSO_TLOGO_COLLECTION=======CP"

Screen.............. "SAPLRSBO_GUI 0200"

Screen line......... 10

Information on where terminated

Termination occurred in the ABAP program "CL_RSO_TLOGO_COLLECTION=======CP" -

in "ACTIVATE_INTERNAL".

The main program was "SAPLRSBO_GUI ".

In the source code you have the termination point in line 144

of the (Include) program "CL_RSO_TLOGO_COLLECTION=======CM009".

Source Code Extract

Line SourceCde

114

115 * error handling

116 DATA: l_s_tlogo TYPE rso_s_tlogo.

117 LOOP AT l_th_tlogo_check_error INTO l_s_tlogo.

118 READ TABLE o_th_tlogo_coll ASSIGNING <l_s_tlogo_coll>

119 WITH TABLE KEY objnm = l_s_tlogo-objnm.

120 <l_s_tlogo_coll>-error = rs_c_true.

121 ENDLOOP.

122 * if warnings / errors exist --> pop up

123 IF i_show_check_protocol = rs_c_true.

124 CALL METHOD show_msg_popup "throws cx_rs_cancelled

125 EXPORTING

126 i_r_msg = l_r_msg.

127 ENDIF.

128 ENDIF.

129

130 * 4. save tlogo objects (unmark those with errors)

131 FIELD-SYMBOLS <l_s_tlogo> TYPE rso_s_tlogo.

132 DATA: l_th_tlogo_save_error TYPE rso_th_tlogo.

133 CALL METHOD save_internal

134 EXPORTING

135 i_with_cto = rs_c_false

136 i_suppress_i_messages = rs_c_true

137 i_detlevel = l_detlevel_1

138 IMPORTING

139 e_th_tlogo_error = l_th_tlogo_save_error.

140 LOOP AT l_th_tlogo_save_error ASSIGNING <l_s_tlogo>.

141 READ TABLE o_th_tlogo_coll ASSIGNING <l_s_tlogo_coll>

142 WITH TABLE KEY objnm = <l_s_tlogo>-objnm.

143 <l_s_tlogo_coll>-error = rs_c_true.

>>>>> ENDLOOP.

145

146 * add / remove objects from collection

147 CALL METHOD adjust_object_list

148 EXPORTING

149 i_only_marked = rs_c_true

150 CHANGING

151 c_th_tlogo = c_th_tlogo.

152

153 * 5. try to activate (first pass)

154 CALL METHOD activate_one_step

155 EXPORTING

156 i_with_cto = i_with_cto

157 i_reset = rs_c_false

158 i_detlevel = l_detlevel_1

159 i_after_import_mode = i_after_import_mode

160 IMPORTING

161 e_subrc = l_subrc

162 e_t_tablnm_cnv = e_t_tablnm_cnv

163 e_th_tlogo_error = e_th_tlogo_error

Thanks & Regards

Janardhan KUmar K