Skip to Content

Trip number range concept

Hi All,

Please explain me the concept of trip number ranges that would be beneficial in production environment. I have few doubts:

1. Are trip number ranges based on yearly basis i.e. is it possible to change the trip number range on year basis.

2. What is main logic to keep in mind for trip number ranges for a production environment.

3. We have 40 personnel areas..so we are planning to keep different number ranges for each Personnel Areas. Is it the right approach?

Please advise

Regards 😊

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Nov 19, 2012 at 12:39 PM

    Hi,

    I usually report interview questions by reflex, but in this case I'll make an exception, because I find the IMG documentation to be blurry.

    The number ranges are not concepted annually, they are permanent. It is possible to delete the ranges' entries with technical means in general, but this will most probably lead to inconsistencies, so don't do this. I would recommend using one number range and pipe all trips into one single number interval, i.e. one single number subobject, check BADI TRIP_WEB_NUMBER. Using different number intervals, in my humble opinion, does not hold any benefit. It's not like you can use 40 identical overlapping intervals to multiply your number volume by 40, intervals should not be used more than once, because an employee might change the personell area which would lead to duplicate keys.

    Cheers, Lukas

    Add comment
    10|10000 characters needed characters exceeded

    • Some really useful replies there Andy and just to re-iterate the advice given as there is a real danger that if you incurred a scenario whereby number ranges overlap that different accounting objects and trips could result in duplication.

      For example

      Personnel area "A001": if the users create the first travel, the number
      will be 001000000.
      Personnel area "A002": if the users create the first travel, the number
      will be 001000000.

      In the scenario above, you have to define a range so that each area is not overlapping as not only will you most likely get the error: "Number assignment: Last number has been assigned" at some point - but also it could result in inconsistency so you need to absolutely ensure they are not overlapping when you define a new number range and ensure to finish and close

      There's a KBA about closing and ending number ranges (1581701) and also sligthly off topic but keep in mind buffering for the number ranges as per note 62077 as the numbers are not continuous anyway if buffering is activated (which is recommended)

      hope it helps

      Sally