cancel
Showing results for 
Search instead for 
Did you mean: 

Problems V2 update GETWA_NOT_ASSIGNED message during V2 Update

Former Member
0 Kudos

Hi all, I hope you can help with a critical problem just after upgrade.

After an upgrade process (4.6.C to ECC 6.0) we have a systematic error in transaction CO11 (Product order confirmation). After end of process, the user receives an express mail with a Update error GETWA_NOT_ASSIGNED.

When looking the updates via SM13 - with a long queue with unprocesses V2 Updates related to CO11 (see hereunder the update logging).

1 K_DOCUMENT_ACTIVITY_POSTING V1 Processed

2 STATUS_UPDATE V1 Processed

3 CYIB_ISTBED_CREATE_POST V2 Error

4 CY_BT_KBED_POST_IN_OTHER_TASK V1 Processed

5 CO_VB_ORDER_POST V1 Processed

6 MCF_STATISTICS_UPD_V2 V2 Initial

7 MCF_MCKALK_VERSION_UPD_V1 V1 Processed

8 MCF_VERSION_UPD_V1 V1 Processed

9 CO_RU_VB_CONFIRMATION_POST V1 Processed

system gives error when stepping in function : DIMENSIONCHECK_TIME.

When looking the error message more in detail :

Runtime Errors GETWA_NOT_ASSIGNED

Date and Time 02.05.2007 16:48:19

User and Transaction

Client.............. 001

User................ "VA_01"

Language key........ "D"

Transaction......... "CO11 "

Program............. "SAPLSMUN"

Screen.............. "RSM13000 3000"

Screen line......... 2

Information on where terminated

Termination occurred in the ABAP program "SAPLSMUN" - in "DIMENSIONCHECK_TIME".

The main program was "RSM13000 ".

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

of the (Include) program "LSMUNU05".

The program "SAPLSMUN" was started in the update system.

Source Code Extract

Line SourceCde

>>>>> FUNCTION DIMENSIONCHECK_TIME.

2 *"----


3 ""Lokale Schnittstelle:

4 *" IMPORTING

5 *" VALUE(MEINH) LIKE T006-MSEHI

6 *" EXCEPTIONS

7 *" DIMENSION_NOT_TIME

8 *" T006D_ENTRY_MISSING

9 *" T006_ENTRY_MISSING

10 *"----


11

12 * vorgegebene Einheit lesen .....*

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Luc,

Please raise a message with SAP.

Regards.

Ruchit.

Former Member
0 Kudos

Hi,

Did you check SM13 before you start upgrade?

If yes..

You can clear sm13 errors ...

If no ...

speak with abap developer and functional consultant

clear sm13 errors

Regards

Ben