Skip to Content
avatar image
Former Member

GETWA_NOT_ASSIGNED_RANGE

Hi,

I am trying to setup the Service Desk in newly installed Solution Manager. I have through with the active services step. When I am trying to activate the services in Tcode SPRC20 I am getting error GETWA_NOT_ASSIGNED_RANGE.

Some one told me that you need to maintained some Number Ranges. Can anyone please guide me to maintain the ranges and solve the problem.

Thanks

Lokendra

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 27, 2009 at 05:30 PM

    Hi,

    For number ranges setup, there are 2 perspective to it. Mainly the basis part of it would be dno_notif, for the crm part it will be crmc_nr_ra_service

    For more examples, please have a look at this blog which mentioned on snum

    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417400)ID0768526150DB00328557856513007437End?blog=/pub/wlg/9489

    Hope this helps.

    Cheers

    Sh

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 27, 2009 at 04:01 PM

    Hi,

    that is correct. The error means that some number ranges are missing.

    Goto transaction snum.

    Normally you need the number ranges for the object CRM_SERVIC.

    If you uses ChaRM you also nee /tmwflow/D, /tmwflow/M, /tmwflow/V.

    But the standard number ranges should have been set when activating the BC-Sets.

    Best regards,

    Alex

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 28, 2009 at 03:39 PM

    Hi,

    Please find below the details log:

    Runtime Errors GETWA_NOT_ASSIGNED_RANGE

    Date and Time 28.10.2009 14:07:36

    -


    Short text

    Field symbol is not assigned.

    -


    Error analysis

    A field symbol that was not assigned was accessed

    (data segment no. 32774).

    The field symbol is no longer assigned because there was an attempt

    makde previously in a Unicode program to set the field symbol using

    ASSIGN with offset and/or length specification. Here, the memory

    addressed by the offset/length specification was not within the

    allowed area.

    -


    How to correct the error

    "SAPLSCPRHI" "GETWA_NOT_ASSIGNED_RANGE"

    System environment

    SAP-Release 700

    Application server... "smserver"

    Network address...... "192.168.1.30"

    Operating system..... "Windows NT"

    Release.............. "5.2"

    Hardware type........ "2x Intel 80686"

    Character length.... 16 Bits

    Pointer length....... 32 Bits

    Work process number.. 0

    Shortdump setting.... "full"

    Database server... "SMSERVER"

    Database type..... "ORACLE"

    Database name..... "SMP"

    Database user ID.. "SAPSR3"

    Char.set.... "C"

    SAP kernel....... 700

    created (date)... "May 15 2006 00:16:38"

    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

    Database version. "OCI_10103_SHARE "

    Patch level. 58

    Patch text.. " "

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

    SAP database version. 700

    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

    Memory consumption

    Roll.... 8176

    EM...... 22994928

    Heap.... 0

    Page.... 81920

    MM Used. 17005528

    MM Free. 760080

    -


    User and Transaction

    Client.............. 100

    User................ "LOKEN"

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

    Transaction......... "SCPR20 "

    Program............. "SAPLSCPRHI"

    Screen.............. "SAPSCPR7 0100"

    Screen line......... 8

    -


    Information on where terminated

    Termination occurred in the ABAP program "SAPLSCPRHI" - in

    "SCPR_HI_KEY_TO_ACTKEY".

    The main program was "SAPSCPR7 ".

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

    of the (Include) program "LSCPRHIU08".

    -


    Source Code Extract

    -


    Line

    SourceCde

    -


    40

    <datakey> type x,

    41

    <flddescr> type scpr_descr,

    42

    <link_flddescr> type scpr_descr,

    43

    <value_bcset> type c,

    44

    <value_intern> type any.

    45

    46

    47

    • check parameters

    48

    if tablename is initial or key is initial.

    49

    message e320 raising WRONG_PARAMETERS.

    50

    endif.

    51

    52

    53

    • get keylength (in characters), tab_tabledescriptions and

    54

    • link_tabledescriptions

    55

    clear: linkkeylng, rc_temp.

    56

    PERFORM GET_DESCR_AND_KEYLNG

    57

    USING TABLENAME tabledescr[]

    58

    CHANGING LINKKEYLNG tab_tabledescr LINK_TABLEDESCR rc_temp.

    59

    if rc_temp <> 0.

    60

    message e395 raising FIELDDESCR_ERROR.

    61

    endif.

    62

    if linkkeylng > 255.

    63

    message e408 raising KEY_TOO_LARGE.

    64

    else.

    65

    66

    67

    • assign x_container (conversion into x-format)

    68

    assign key(linkkeylng) to <datakey> casting.

    69

    • copy data in order to ensure correct alignment

    >>>>>

    move <datakey> to key_x.

    71

    72

    73

    • convert data

    74

    loop at tab_tabledescr assigning <flddescr>

    75

    where not keyflag is initial.

    76

    • assign value of the data key (position and length in bytes)

    77

    if <flddescr>-vtype = 'P'.

    78

    assign key_x+<flddescr>-position(<flddescr>-intlen)

    79

    to <value_intern> type 'P' decimals <flddescr>-decimals.

    80

    else.

    81

    assign key_x+<flddescr>-position(<flddescr>-intlen)

    82

    to <value_intern> type <flddescr>-vtype.

    83

    endif.

    84

    • assign value of actlink_key (position and length in characters)

    85

    read table link_tabledescr assigning <link_flddescr>

    86

    with key fieldname = <flddescr>-fieldname.

    87

    • rel. >= 610: different coding in different releases ************

    88

    position = <link_flddescr>-position

    89

    / cl_abap_char_utilities=>charsize.

    -


    Thanks

    Lokendra

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      Problem solved after applying required service packs. Minimum support level is required SPS 13 for Solution Manager.

      Thanks

      Lokendra

  • avatar image
    Former Member
    Jan 20, 2010 at 10:09 AM

    After applying the service pack problem got solved now it is upto pack 13.

    Add comment
    10|10000 characters needed characters exceeded