No number range found for 01 RP_REINR SP11--Travel Manager

Hi
While creating Travel request in in Travel manager i got this error messages"No number range found fo 01 RP_REINR SP!!-Travel Manager..Plse advice me how to resolve this..
Thanks&best regds
Shaila

In adition to task from Shailaja .. Consider this:
Please note that while defining your number ranges, the number must be two Digits  i.e ( 01,02,03)  , it must NOT be single digit  i.e (1,2,3)..
I'd had the same issue, but with the two digits number it has been solved.
Regards,
Rodolfo

Similar Messages

  • No number range found which is maintained in pr10

    Hi All,
    I ahve maintained nuber range for travel in PR10 for the respective personnel area....but the employee when trying to put the expeses in PREX....here the error is
    "No number range found for 01 RP_REINR ZONC"
    I have don the same in sand box and development client but in quality it not appearing....
    Plz guide...
    Amol

    Hi Amol,
    Check number range once from SNUM transaction Input object RP_REINR. Then select number ranges and input personnel area.
    Regards,
    Dilek

  • Number range 01 for object BANF is nearly exhausted.

    Hi ! When we do total planning run in the background we got the message "Number range 01 for object BANF is nearly exhausted.". Our system is configured to create a new purchase requisition for every requirement. I can found that we have reached 98% of our PR number range and the warning message (through SNRO) is set at 2%. As a temporary solution, before I assisgn a new number range to PR, I reduced the percantage for warning message to 1% so that we can get few more days before the number range is changed. But, we continue to get the same error and no purchase requisition is created. Kindly help and suggest.
    regards,
    Satya

    this is probably caused by the buffering. Buffering of numbers is made to increase performance. the Program reads the number range just once to get 10 numbers (and the percentage for the warning message as well, otherwise it would not make sense to use buffers if SAP has to access the number range anytime to check if it is nearly exhausted )

  • How to find out the Number range object for Incident number

    How to find out the Number range object for Incident number ?
    CCIHT_IAL-IALID
    regards,
    lavanya

    HI, an example.
    data: vl_num type i,
          vl_char(6) type c,
          vl_qty type INRI-QUANTITY,
          vl_rc type INRI-RETURNCODE.
    CALL FUNCTION 'NUMBER_GET_NEXT'
      EXPORTING
        NR_RANGE_NR                   = '01'
        OBJECT                        = 'ZRG0000001'
       QUANTITY                       = '1'
      SUBOBJECT                     = ' '
      TOYEAR                        = '0000'
      IGNORE_BUFFER                 = ' '
    IMPORTING
       NUMBER                        = vl_num
       QUANTITY                      = vl_qty
       RETURNCODE                    = vl_rc
    EXCEPTIONS
       INTERVAL_NOT_FOUND            = 1
       NUMBER_RANGE_NOT_INTERN       = 2
       OBJECT_NOT_FOUND              = 3
       QUANTITY_IS_0                 = 4
       QUANTITY_IS_NOT_1             = 5
       INTERVAL_OVERFLOW             = 6
       BUFFER_OVERFLOW               = 7
       OTHERS                        = 8
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    vl_char = vl_num.
    write vl_char.
    Regard

  • Maintain number range object for excise grp

    Hi Gurus,
    During stock transfer, while doing Goods receipt I am getting the below error
    "Maintain number range object for object J_1IRG23D, year 2010, excise group"
    Could anyone please tell me the trans code for maintaining no range for excise group...
    Thanks,
    Raja

    Go to J1I9 T Code for a particular object object J_1IRG23D, execute and then give the excise group and maintain the number series.
    Regards,
    Nagesh
    Edited by: Nagesh MS on Dec 20, 2010 3:59 PM
    Edited by: Nagesh MS on Dec 20, 2010 3:59 PM

  • Error in MIGO :Number range object for object J_1IINTNUM, year 2010, excise

    Dear Experts,
                              While  posting  MIGO, System throws below error : 
    Mainintain number range object for object J_1IINTNUM, year 2010, excise
    Maiintain number range object for object J_1IRG23A1, year 2010, excise
    Maintain number range object for object J_1IRG23A2, year 2010, excise
    Actually we are posting the MIGO for the  fiscal year 2009, still i am getting error  why ?
    regards
    rajakarthik.

    check the posting date what u r puting , it should be on or  before 31/03/2010
    i think this is only the issue dont looks like any other issue
    or do one thing just o\go in SNRO and for J_1IINTNUM object put 9999 year and the number range
    and try to post your transaction in 2009
    hope this helps
    Edited by: Umakant Bhangale on Apr 1, 2010 10:22 AM

  • Mass deletion of document number ranges intervals for several company codes

    Dear experts,
    We are running version ECC6 and are about to go-live a lot of company codes simultaneously. We would like to delete satndard number ranges intervals for these company codes.
    Is there a way to delete the number ranges intervals (which have not been used) for several company codes at the same time ? I'm looking for a transaction or a program similar to OBH1 (used for the creation of number ranges ).
    Thanks in advance for your help.
    Best Regards,
    Steven

    Hi
    I am also not aware of such T.code to delete number ranges for a company code.
    Alternatively, you can go to FBN1 in change intervals mode.
    From the Menu Select all and Press Shift + F2 (Delete interval).
    Ofcourse, this have to be done individually for each co. code.
    Regards

  • Number range R4 for object BANF nearly exhausted

    Dear,
    when I use MD15 to convert Planned order to PR, this error message shows up "number range R4 for object BANF nearly exhausted"
    I know the range of PR number is nearly exhausted. but could someone teach me how to check it. I mean use which transaction to check what BANF stands for...
    Best regards
    Meng HM

    >
    Meng HM wrote:
    > Dear,
    >
    > when I use MD15 to convert Planned order to PR, this error message shows up "number range R4 for object BANF nearly exhausted"
    > I know the range of PR number is nearly exhausted. but could someone teach me how to check it. I mean use which transaction to check what BANF stands for...
    >
    > Best regards
    >
    > Meng HM
    Check this path: spro>MM>Consumption based planning>number ranges>define NR for planning run, execute and maintain the interval of planned orders.
    Then apply this internval in OPPQ, under number range button.
    Edited by: Afshad Irani on Aug 30, 2010 10:34 AM

  • Facing problem in Number Range Allocation for Objects in OM

    Hello Friends,
    I have couple of questions in setting number range for Objects OM :
    1) Can we set one single number range for the objects in all planned versions or do we need to set different number ranges for varous planned versions?
    2) If we are already using existing Internal Number Range in $$$$ for Objects in OM, how do we set number range External Number range to use it for forthcoming object creation?
    3) If we set the External Number Range, will the system use the set num range combinedly for all object types or individually for each object type (Ex: If we have an external  num range 100~200, then while creating Org Unit the system may take 100 after that if we try to create another Org Unit the system may take 101 in seqeuence. After creating these two Org Units, if we try create an Position object will the system start allocating the number from 102 or will it again start from 100)
    4) Can we default number ranges for various Object Types Planned version wise? If YES, what feature is used to default this number range?
    Regards
    Tharak

    Hi,
    For 1). Yes you can set number ranges for all plan versions.
    2. You can devide like this.
    IN - 00000001 to 49999999 
    EX - 50000000 to 99999999  - EXT.
    3. In my view it is applicable to all Objects.
    4. Don't know.
    Reward me if helps.
    Thanks,
    vasu.

  • Re : Maintain number range interval "" for quants

    Hi
        While doing the transfer order i am getting the following error.
    " Maintain number range interval "" for quants "
    How to solve this.
    Thanks
    Anto

    dear sir
    go to Tcode : OMLW click for quants tab, give your warehouse number and maintain the number ranges, for your warehouse.
    Regards
    jrp

  • Maintain number range object for object J_1IRG23C1, year 2008, excise

    Dear All,
    I am doing the purchase cycle for Assets, while doing GR i am getting the below error, pls guide me
    Maintain number range object for object J_1IRG23C1, year 2008, excise
    Maintain number range object for object J_1IRG23C2, year 2008, excise
    B/regds,
    CB

    Dear CB,
    Use Transaction "SNUM", and give the object name as "J_1IRG23C1" and maintain number range for the financial year.
    Do the same procedure for Object "J_1IRG23C2" and maintain the number range.
    Hope this helps.
    Njoy SAP
    -Saravanaganesh

  • Maintain number range object for object J_1IINTNUM

    Dear,
    While doing GRN i am getting this error:
    Maintain number range object for object J_1IINTNUM, year 2009, excise group
    Maintain number range object for object J_1IRG23A1, year 2009, excise  group E1
    Maintain number range object for object J_1IRG23A2, year 2009, excise group E1
    What i did is:
    1) I maintained NR for Objects J_1IINTNUM,  J_1IRG23A1,J_1IRG23A2 in J1I9 Tcode.
    Still i am getting the same error in MIGO.
    Regards
    Utsav
    Edited by: Utsav.agra on Nov 18, 2009 12:24 PM

    Dear Pankaj,
    thanks actually i wans maintaining number as 1 instead of 01.
    Thanks
    Utsav

  • Maintain number range object for object J_1IINTNUM, year 2009, excise group

    Hi SAP Guru !
    Plz tell me the solutions quickly, Even after mantaining the required Objects in "J1I9" , when I am going to post GR , once again it is saying that ........
    1 - >   Maintain number range object for object J_1IINTNUM, year 2009, excise group
           Message no. "4F159" .
    2 - > Maintain number range object for object J_1IRG23A1, year 2009, excise group 21
           Message no. 4F159
    3 - >  Maintain number range object for object J_1IRG23A2, year 2009, excise group 21
            Message no. 4F159
    Regards,
    San

    dear sir
    while maintain number range , in the number column, it should be 01. other than 01, you will get same error.
    so please check it should be 01 in the number column and year and number range interval .
    regards
    jrp

  • Maintain number range object for object J_1IRG23A1, year 2007, excise

    Hi All,
    I have configured CIN in ECC 5.0. When i am doing MIGO getting errror that "Maintain number range object for object J_1IRG23A1, year 2007, " and
    Maintain number range object for object J_1IRG23A2, year 2007, excise group 10
    but i have already maintained number range for  such object.
    please guide me.
    Regards,
    Ravindra

    Hi,
    Which Number u given,
    No    year       From number       to number
    01     2007      1                          10000
    I think u allready given,this is for checking.
    Raghu

  • Number range buffering for dimension tables (DIM IDs) and InfoObjects (SIDs

    Hi BW Experts,
    How to check whether this number range buffering for dimension tables (DIM IDs) and InfoObjects (SIDs) is Active or not ??
    can you please provide me this technical information where to go and check in the system ?
    Thanks in Advance.

    The Early Watch report lists these because of the large number of rows in the MD/Dim tables.  Keep in mind though, that Number Range buffering will really only help if you continue to generate a large volume of new SIDs or Dim IDs with ongoing loads, e.g.
    If your transactions being loaded to a cube result in several thousand new rows being added a Dim table, then it makes sense to turn on Number Range buffering for that Dim ID.  But if the transaction volume is only cause a few hundred DIM IDs to be added, buffering will not really get you anything.

Maybe you are looking for