ERS and number ranges

All,
I'm trying to test in 6.0 the ERS number range functionality.  In configuration I've set up the  ERS invoice number range and I'm trying to link the number range to the company code.   The SAP instructions say I should enter the 2-digit number range in the ERS invoice number range field on the Additional Data screen.   
I do NOT see the ERS invoice number range field anywhere.   Any idea what I'm doing wrong?
Thanks
Sandra

Sandra,
Just to add to Kishore's very good response.
Apart from France and Spain (the SAP ECC 5.0 release notes mention only these), these special legal requirements in EU seem to have been extended to a few other countries as well like Hungary, Belgium and Portugal (from OSS).
Please read the following OSS notes (I am not sure which country you are trying to implement this for). They should explain what you need to do implement this ERS numbering functionality.
Note 684514 - ERS: Vendor-specific sequence number (France & Spain)
Note 893068 - ERS numbering for Hungary
Note 959930 - ERS: Numbering for Belgium and Portugal
Note 1068926 - ERS:Numbering for Belgium and Portugal updated
The assignment of your number range to your company code is not quite obvious as it seems. It is done through a parameter value in the company code 'additional details' section in the ERS config or OBY6 config. The OSS notes explain what needs to be done in detail.
Hope this helps.
H Narayan

Similar Messages

  • Could you check our source? (To determine the PR type and number range)

    Hello.
    We use SRM Server5.5 with Classic Scenario.
    We will use the BADI BBP_SC_TRANSFER_BE to determine the PR type and number range according to your recommend.
    We have two PR type in R/3.
    1) KGPR
    2) KTR1
    As you know that shopping cart has no type. So we add customer field to mapping to R/3 PR type and this field has two values.
    1)     PR01: mapping to KGPR
    2)     PR02: mapping to KTR1
    We will use the method GROUP_RQ to determine the PR type.
    If customer field is PR01, PR type is determined KGPR
    If customer field is PR002, PR type is determined KTR1.
    To determine the PR number range, we will use the method GET_NUMBER_OR_RANGE.
    If PR type is KGPR, Choose the No key 12
    If PR type is KTR1, Choose the No key 16.
    Configuration step:
    1.     Maintain the PR number range in SRM.
    No key: 12  (for KGPR) internal NR
    No range: 2520000000 – 2529000000
    No key: 16 (for KTR1) internal NR
    No range: 2560000000 – 2569000000
    2.     Maintain the PR number range in R/3
    No key: 12  (for KGPR) Ext NR
    No range: 2520000000 – 2529000000
    No key: 16 (for KTR1) Ext NR
    No range: 2560000000 – 2569000000
    3.     Assign the PR number range to PR type in R/3
    KGPR – 12 (EXT)
    KTR1 – 16 (EXT)
    4.     Maintain the attribute in SRM
    Document type in R/3
          Add KGPR and KTR1
    We developed this logic, but it’s not working.
    LOOP AT ct_proc_item INTO ls_proc_item “ Where is no date in ct_proc_item:
    We can not find out the reason.
    Could you check our source?
    METHOD if_ex_bbp_sc_transfer_be~group_rq.
      DATA:
           ls_proc_item           TYPE bbps_procurement,
           lv_number_int          TYPE bbp_item_no,
           ls_item                TYPE bbp_pds_transfer_item,
           lv_group_counter       TYPE numc5,
      CONSTANTS:
          lc_on(1)               VALUE 'X'.
      SORT ct_proc_item BY obj_to_gen.
      CLEAR: lv_group_counter.
    LOOP AT ct_proc_item INTO ls_proc_item  
    where obj_to_gen eq iv_object_to_generate.
    get item data which includes customer fields
        MOVE ls_proc_item-preq_item TO lv_number_int. " convert
        READ TABLE it_item INTO ls_item WITH KEY number_int = lv_number_int.
        IF sy-subrc = 0.
          IF ls_item-pr_type EQ 'PR01'.
            ls_proc_item-doc_type = 'KGRP'.
          ELSEIF ls_item-pr_type EQ 'PR02'.
            ls_proc_item-doc_type = 'KTR1'.
          ENDIF. " lv_cust_field
          lv_group_counter = lv_group_counter + 1.   " increase counter
          ls_proc_item-group_1 = lv_group_counter.
          MODIFY ct_proc_item FROM ls_proc_item
                 TRANSPORTING group_1.
        ENDIF.  " sy-subrc
      ENDLOOP.
      cv_method_active = lc_on.
    ENDMETHOD.
    method IF_EX_BBP_SC_TRANSFER_BE~GET_NUMBER_OR_RANGE.
      if is_item-pr_type = 'PR01'.
         CV_NUMBER_RANGE = '12'.
         CV_NUMBER = '2520000000'.
      elseif is_item-pr_type = 'PR02'.
         CV_NUMBER_RANGE = '16'.
         CV_NUMBER = '2560000000'.
      endif. " is_proc_item / is_item
    Thank you
    Best Regard
    SH

    Hi
    Please find some suitable sample code, which might help you out.
    method IF_EX_BBP_SC_TRANSFER_BE~GET_NUMBER_OR_RANGE .
    * IV_OBJECT_TO_GENERATE
    *   '1' Reservation
    *   '2' Purchase Requsition (BANF)
    *   '3' Purchase Order
    *   '4' Customer Object
    * 1. current item data are in structures
    *    - IS_ITEM shopping cart item data including Customer Fields
    *    - IS_PROC backend relevant item purchasing data
    * 2. accounting data in tables
    *    - IT_ACCOUNT all shopping cart account. data with Customer Fields
    *    - IT_PROC_ACCOUNT backend relevant accounting data for current item
    *  - key criteria between this tables are
    *    - it_proc_account-preq_item
    *                     -serial_no (numc 2)
    *    - guid from is_item
    *    - it_account-p_guid
    *                -accno(numc 4)
    * A) example to use current item data + item customer fields
    *  if is_proc_item-DOC_TYPE = 'ABCD' AND
    *     is_item-<field of CI_BBP_ITEM> = .
    * set own number range
    *  CV_NUMBER_RANGE = .
    ** set own number
    ** .. ==> if initial SAP Standard with no.range will be processed
    *  CV_NUMBER = .
    *  endif. " is_proc_item / is_item
    * B) example to use only proc_account no accounting customer fields
    *data:
    *     ls_proc_account   type bbp_bapipogna.
    *  loop at it_proc_account
    *            into ls_proc_account.
    *    if ls_proc_account-BUS_AREA = '9988'.
    ** set own number range
    *  CV_NUMBER_RANGE = .
    ** set own number
    ** .. ==> if initial SAP Standard with no.range will be processed
    *  CV_NUMBER = .
    *     endif. " ls_proc_account
    *  endloop.
    * C) example to use only accounting customer fields, no other accounting
    *data:
    *     ls_account        type bbp_pds_acc.
    *  loop at it_account
    *            into ls_account
    *            where p_guid = is_item-guid.
    *    if ls_account-<field of CI_BBP_ACC> = .
    ** set own number range
    *  CV_NUMBER_RANGE = .
    ** set own number
    ** .. ==> if initial SAP Standard with no.range will be processed
    *  CV_NUMBER = .
    *   endif. " ls_account
    *  endloop.
    * D) example to use proc_account + customer fields for accounting
    *data:
    *     lv_serial_no      type bbp_bapipogna-serial_no,  " sequence num 2
    *     lv_acc_no         type bbp_pds_acc-acc_no,       " sequence num 4
    *     ls_proc_account   type bbp_bapipogna,
    *     ls_account        type bbp_pds_acc.
    *  loop at it_proc_account
    *            into ls_proc_account.
    *    move ls_proc_account-serial_no to lv_acc_no.
    *    read table it_account
    *         into ls_account
    *         with key p_guid = is_item-guid
    *                  acc_no = lv_acc_no.
    *    if sy-subrc = 0.
    **     if ls_account-<field of CI_BBP_ACC> = .
    ** set own number range
    **  CV_NUMBER_RANGE = .
    ** set own number
    ** .. ==> if initial SAP Standard with no.range will be processed
    **  CV_NUMBER = .
    **      endif. " ls_account
    *    endif. " sy-subrc
    *  endloop.
    endmethod.
    method IF_EX_BBP_SC_TRANSFER_BE~GROUP_RQ .
    * 1. current item data are in structures
    *    - IT_ITEM all shopping cart item data including Customer Fields
    *    - IT_PROC_ITEM backend relevant item data of current log.system
    *    key criteria between this tables are:
    *    - IT_ITEM-NUMBER_INT (numc 10)
    *    - IT_PROC_ITEM       (numc  5)
    * 2. accounting data in tables
    *    - IT_ACCOUNT all shopping cart account. data incl. Customer Fields
    *    - IT_PROC_ACCOUNT backend relevant accounting data for current item
    *  - key criteria between this tables are
    *    - it_proc_account-preq_item (numc 5)
    *                     -serial_no (numc 2)
    *    - is_item-guid
    *             -number_int (numc 10)
    *    - it_account-p_guid
    *                -accno(numc 4)
    constants:
          lc_on(1)               VALUE 'X'.
    * A) example to use only proc_item with NO customer fields
    *         group requisitions by backend document type
    *data: lv_doc_type            TYPE esart,
    *      ls_proc_item           type BBPS_PROCUREMENT,
    *      lv_group_counter       type numc5.
    *    clear lv_group_counter.
    *    clear lv_doc_type.
    *    SORT ct_proc_item BY obj_to_gen doc_type.
    *    LOOP AT ct_proc_item
    *            into ls_proc_item
    *            WHERE obj_to_gen EQ iv_object_to_generate.
    ** new group criteria?
    *      if lv_doc_type ne ls_proc_item-doc_type.     " backend doc.type
    *        lv_group_counter = lv_group_counter + 1.   " increase counter
    *        lv_doc_type      = ls_proc_item-doc_type.       " save criteria
    *      endif.
    *      ls_proc_item-group_1 = lv_group_counter.
    *      modify ct_proc_item from ls_proc_item
    *             transporting group_1.
    *    ENDLOOP.
    * B) example to use item customer fields
    * data:
    *      ls_proc_item           type BBPS_PROCUREMENT,
    *      lv_cust_field          type <field of ci_bbp_item>.
    *      lv_number_int          type BBP_ITEM_NO,
    *      ls_item                type BBP_PDS_TRANSFER_ITEM.
    *    clear lv_group_counter.
    *    clear lv_cust_field .
    *    SORT ct_proc_item BY obj_to_gen.
    *    LOOP AT ct_proc_item
    *            into ls_proc_item
    *            WHERE obj_to_gen EQ iv_object_to_generate.
    ** get item data which includes customer fields
    *      move ls_proc_item-preq_item to lv_number_int. " convert
    *      read table it_item
    *           into ls_item
    *           with key number_int = lv_number_int.
    *      if sy-subrc = 0.
    **       new group criteria?
    *        if lv_cust_field ne 'XYZ'.
    *         lv_group_counter = lv_group_counter + 1.   " increase counter
    *         lv_cust_field = ls_item-<field of ci_bbp_item>."save criteria
    *        endif. " lv_cust_field
    *        ls_proc_item-group_1 = lv_group_counter.
    *        modify ct_proc_item from ls_proc_item
    *               transporting group_1.
    *      endif.  " sy-subrc
    *    ENDLOOP.
    * C) example to use accounting data with customer fields
    *            group requisitions by backend document type
    *data: lv_doc_type            TYPE esart,
    *      ls_proc_item           type BBPS_PROCUREMENT,
    *      lt_account             type BBPT_PD_ACC,
    *      ls_account             type bbp_pds_acc,
    *      ls_item                type BBP_PDS_TRANSFER_ITEM,
    *      lv_number_int          type BBP_ITEM_NO,
    *      lv_account_flag        type c,
    *      lv_group_counter       type numc5.
    *    clear lv_group_counter.
    *    clear lv_doc_type.
    *    SORT ct_proc_item BY obj_to_gen doc_type.
    *    lt_account[] = it_account[].
    *    SORT lt_account BY p_guid acc_no.
    *    LOOP AT ct_proc_item
    *            into ls_proc_item
    *            WHERE obj_to_gen EQ iv_object_to_generate.
    ** get accounting customer fields for this item
    *    clear lv_account_flag.
    ** ..first get item guid
    *    move ls_proc_item-preq_item to lv_number_int.
    *    read table it_item
    *         into ls_item
    *         with key number_int = lv_number_int.
    *    if sy-subrc = 0.
    *      loop at lt_account
    *           into ls_account
    *           where p_guid = ls_item-guid.
    *        if ls_account-<field of CI_BBP_ACC> = .
    *           lv_account_flag = lc_on.
    *        endif.
    *      endloop.
    *    endif. " sy-subrc it_item
    ** new group criteria?
    *      if lv_doc_type ne ls_proc_item-doc_type OR     " backend doc.type
    *         lv_account_flag = lc_on.                    " accounting
    *        lv_group_counter = lv_group_counter + 1.   " increase counter
    *        lv_doc_type      = ls_proc_item-doc_type.       " save criteria
    *      endif.
    *      ls_proc_item-group_1 = lv_group_counter.
    *      modify ct_proc_item from ls_proc_item
    *             transporting group_1.
    *    ENDLOOP.
    * !!!! set flag that BADI was processed
    * .. ==> no SAP Standard grouping will be processed
        cv_method_active = lc_on.
    endmethod.
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul

  • Restructure Customer Account Groups and Number Ranges

    We already have existing customer account groups and number ranges and therefore customer accounts.
    We need now to restructure Customer Account Groups incl. number Ranges and Number Range Allocation.
    Is this possible? Any advice?
    Can a customer keep is old customer number and be assigned to the new customer account group, which has a different number range?
    Please adivse.
    Many thanks
    Petra

    Ravi,
    thanks very much for your reply. This information is very useful.
    Just one more question:
    WIth which Customer Number will reallocated customer end up? the originial one or does the customer get a new number relating to the number range of its new customer account group?
    Many thanks,
    Petra

  • BBP_BS_GROUP_BE for new document type and number range

    Hi gurus,
    I am working on Classic scenario in SRM and currently have used the above BADI to use a different document type and number range when creating the PO in the backend system. It all works fine. The only thing is I noticed that the BE_DOC_TYPE field in the shopping cart is still reflected as 'EC' even though the PO created in ECC is for example EC1. My question: Is this standard SRM? If so, is it common to leave this field as it is or is it advisable for us to change the document type to EC1 as well? Also, is there any implication in standard SRM reporting and downstream processes that you are aware of?
    Appreciate any advice on the above.
    Cheers!
    Sf

    We have ended up having to populate the document type on a custom field or alternatively replace the existing one.

  • Internal order types and number ranges

    We have two SAP instances and want to load Internal order types and number ranges and Internal orders from 4.6 to 4.5 version.
    I need to determine if there is an overlap of number ranges for the internal order types used in 4.6 and 4.5
    Could you please help me how to approach? Manually verifying each range in both system is a tedious job and very confusing as the numbers are too big.

    Hi,
    I can suggest one thing which seems to be worth trying. Involve one technical guy in downloading the number ranges as well the orders of the numbers used from both the system and compare it. Then compile them and upload it again.
    Trust this helps much!
    Cheers!

  • Vendor acct group and number range in the MDC vs MDS

    IN MDM 3.0 when a new BP with vendor as role is created via UI in MDS the vendor is created with a generic BP number range in the MDS.  The down stream MDC's all have different vendor account groups with different number ranges assigned in each MDC..  example...
    client     type of vend   acct grp      num range
    MDC1      purch vendor     com2      1000000-1999999
    MDC1      acct vendor      act1      2000000-2999999
    MDC2      purch vendor     pur1      2400000-2499999
    MDC3      purch vendor     POV1      3599999-3599999
    How does MDS know when it distributes the vendor to the MDC's what account group and number range to create the vendor with in the MDC's.  The MDC cannot change all its existing master data that has been created already with the account groups and number ranges becuase field variants have been established.  Where is this mapping contained MDS or XI and how is it done.

    The number range in the MDS is determined by the value in the "Grouping" combo-box.  This combo-box is populated by values entered in IMG activity Master Data Objects -> Business Partner -> Business Partner -> Basic Settings -> Number Ranges and Groupings -> Define Groupings and Assign Number Ranges.  Each value must have an associated number range and one of the values must be defined as the standard grouping in case the user doesn't select a grouping.  This is how numbering occurs in the MDS.  Unfortunately you cannot assign more that one grouping to a new BP.
    Now, for the MDCs.  When sending a new BP to an MDC, for example an R/3, there must be an external number range setup in the MDS for that MDC and it shouldn't conflict with any number range in that MDC. 
    IMG Activity Master Data Exchange -> Central Settings -> ID Mapping -> Make General Settings for ID Mapping allows you to define which number range you want to use for a specific object type in a specific system (e.g. KNA1 (customer) in system R/3_100). 
    So far this isn't sufficient for you because you have 2 number ranges for MDC1 in your example. 
    In the IMG activity I just mentionned, there is also a possibility to add an additional parameter which allows you to assign a number range for each unique object-type/system/additional parameter combination.  By putting the account group in the additional parameter field, this allows you to assign number ranges per account group.
    What remains to be done is to use this information in the XI Mapping for BP to R/3 Vendor.  The first thing is for the XI Mapping to map the MDS account group to the MDC account group.  Then the XI Mapping must call the MDS to create a new ID-Mapping between the BP and the Vendor.  During this call, the XI Mapping must provide all the usual parameters as well as the account group.  This will ensure that the correct number range will be selected so the correct vendor id will be generated.  This id will then be used in the ID Mapping.
    If you need to create the Vendor for multiple account groups, then you will have to implement special logic to map the MDS account group from the BP to the many MDC account groups needed for the Vendor.
    Hope this helps!

  • BP creation in CRM WebClient - Role and Number Range assignment

    Hello,
    I have the requirement to specify a particular number range and BP role when an Account is created in the CRM WebClient Interface.
    For example as standard, when an employee is created through the CRM WebClient (BSP component BP_EMPL) the default employee role (BUP003) and the default number range are assigned to the BP.
    I would need to specify a different number range and role to the employee
    I've tried to configure the Account Identification profiles (activity "Define Account Identification Profiles" in customizing); with that activity you can specify which role and which number group you want to use for the BP (account) creation. However this customizing is affecting the IC WebClient only and not the CRM WebClient.
    I was wondering if a similar customizing activity exists for the CRM WebClient (in particular for the BP_EMPL application), or if there's a way around this.
    Anybody has an idea about how to solve this?
    Any help would be greatly appreciated, thank you in advance.

    Hi all,
    I have done this by defaulting the bp group in the BADi 
    1.Go to the se18 and select BADI_CRM_BP_UIU_DEFAULTS and select the interface IF_UIU_BP_DEFAULTS
    2. Go to the method IF_UIU_BP_DEFAULTS~GET_DEFAULT_VALUES and you can write your logic here to default the grouping.
    In my case I wanted all accounts created to be defaulted to a particular grouping and my code looks like this
    lv_name1 = lr_current->get_property_as_string( iv_attr_name ='BP_CATEGORY' ).
                        IF lv_name1 IS NOT INITIAL.
                          IF lv_name1 = '2'.
                            lr_current->set_property( iv_attr_name = 'BP_GROUP'
                                       iv_value = '0060' ).
                          ENDIF.
                        ENDIF.
    Thanks & Regards,
    Sanila

  • System Performance and Number Range Buffering

    Hi,
    This is regarding the following issue for which we welcome any relevant inputs.
    Issue: Recently the SAP production system in one of our regions had a performance issue resulting in production system outage. On checking , it was found that there were locks on table NRIV when this outage occurred.
    Analysis: While searching for suitable OSS notes on this issue, we came across some OSS notes that discussed Number Range buffering.
    Inputs needed:
    1.How to determine if number range buffering is applicable in a particular situation.
    2.If an OSS note is to be applied for number range buffering, how do we test the impact of the same on system.
    3.Methodology for Number range buffering
    Any pointers in this direction would be highly appreciated.
    Thanks and Regards,
    Prasun Goel

    Hi Prasun,
    I had gone through this page of help.. might be helpful to you also
    [Number range buffering|http://help.sap.com/saphelp_nw04/helpdata/en/7b/6eb2aa7aed44ea92ebb969e03081fb/frameset.htm]
    [Administration|http://help.sap.com/saphelp_nw04/helpdata/en/aa/dbc9b4b56143bb8f2ae909d7d040fa/content.htm]
    regards
    sadhu kishore

  • Copy, delete, check personnel subarea and Number ranges

    Hi All,
    I am creating a new personnel subarea using copy the personnel subarea in enterprise structure definition.
    (Copy, delete, check personnel subarea)
    While doing this I am getting prompt about number ranges over writing issue.
    It seems that number ranges in production system may get affected due to this transport.
    So I am planning to note all the available number ranges in production system before transport and reset similar as earlier after the transport directly in production
    OR
    set number ranges in development similar in production then to transport to production.
    Please comment on the above approach.
    I am planning to check on the following number ranges only
    Tcodes u2013OONR ( for OM)  and PA04 (for PA)
    Can you suggest in case if any other number ranges to be taken care?
    Regards
    Thomas

    Hello,
    Do you have another option for the copy  : Copy (without reference) ?

  • Organizational units and number range

    Hi
    how to maintain number ranges for organizationl units.. can someone explain?

    IMG>Personnel Management>Organizational Management-->Basic Settings>Maintain Number Ranges
    ~Suresh

  • FM for checking EAN control digit and Number Range

    Hello All!
    Anybody know what functional module is used for checking correctness of EAN ?
    Parameters:
    exporting ean11, ean type
    importing EAN_Ok
    I need to do this check procedure when I upload additional EANs via artmas (but it doesn't matter).
    Best Regards,
    Eugene

    Check FM EAN_CHECK. There are other FMs also starting with EAN_*.

  • HU and SU number range

    Hello,
    If storage location is HU and WM managed ( SU management active), is it required that for the number range of  HU simialr overlapping number range has to be maintained for SU (assigned to the warehouse)?

    Hi,
    you activate handling unit management independent from storage unit      
    management.                                                                               
    Only in case if storage location is full-WM- AND HU-managed the storage  
    unit management is always active and HU numbers are taken over as SU     
    numbers. In all other cases HUM and SUM are independent from each other  
    and number ranges must be set a way that they are not overlapping.       
    Regards,
    Ely

  • Wrong Depot Excise Invoice Number Ranges

    Hi,
    We have created the new number ranges for the year 2010 for Object - J_1IDEPINV(series group S11)
    But when the Depot excise invoice is created by using J1IJ with reference to delivery, the number ranges are picked from old series of 2009.
    The Delivery is dated 29 March 2010, the excise invoice is created on 2nd April 2010.
    The number ranges are maintained on 1st April 2010.
    Regards,
    Jagadish

    Please check Object - J_1IDEPINV in SNUM ,J1I9,SNRO
    whether To-year flag is set or not , check must be. and number range interval no is 01
    For your info- even in the compnay code setting in LG-- Tax ongoods movment-
    here First Month :4April----if these setting are there surelly you will get new number range maintain in 2010
    likes points please

  • Excise number Range Maintenance

    How to maintain Excise number Range and in which object we have to maintain number range for domestic /export etc

    Hi rohith
    Go to SNRO (or) SNUM and select any of the below objects required by you and select NUMBER RANGE on top. It will ask for "Series Group". Give the respective plant's series group and click "Change intervals".
    Now give some value in the field "No" followed by year and number range and save.
    J_1IARE1         ARE1 Doc No object based on Series Group
    J_1IARE3         ARE3 Doc No object based on Series Group
    J_1IBOND        Excise Bonding: Bond number object
    J_1ICERT         Withholding Tax Certificates (India)
    J_1ICHLNNO     Internal number range for challans
    J_1ICONPLA     Consolidated PLA serial no. generation
    J_1IDEPINV      Excise Invoice Number for Depot Invoices
    J_1IEXCEXP     Export excise invoice number range
    J_1IEXCINV      Excise invoice number
    J_1IEXCLOC     Local excise invoice numebr range
    J_1IEXCTST      Excise invoice with intervals
    J_1IEXINEX       Excise invoice number for export
    J_1IINTNUM      Internally document number to be generated
    J_1IINTPR2       Despatch serial number
    J_1ILIC             Excise Bonding: License number object
    J_1IPLA2          PLA part II number range object
    J_1IRG1           RG1 Number range object
    J_1IRG1_T        No. Range for RG1 - Excise group / Material
    J_1IRG23A1      RG23A part 1 no. range object
    J_1IRG23A2      RG23A part II number range object
    J_1IRG23C1      RG23C part I number range object
    J_1IRG23C2      RG23C part II number range object
    J_1IRG23D        Folio Numbers for RG 23D
    Thanks
    G. Lakshmipathi

  • Same number range for two different series groups?

    Dear all,
    There are two scenarios
    1.Normal export under bond case, series group is 20 and number range maintained,running number is 300016
    2.Another scenario,where ARE1 document generation for Deemed exp customer(already customised) , series group is 30.
    But, client requirement is , for this second scenario also, system should pickup running number range of series group 20(under bond case)  as per excise legal requirement
    Ie running number is for series group 20 is 300016
    For the above deemed exp case (second scenario)it should pickup 300017
    And again when they do under bond case(first scenario), it should pick up 300018 like that
    Is it possible to maintain the same number range for two different series groups(20 and 30)?
    Even if you maintain the same number range for 30, as per running number range of 20
    Will the system update simultaneously the same number range for 20 and 30 series groups?
    Please suggest the way.

    With two different series groups, it is not possible to have the same number range. Even if you maintain it, they will be treated independently.
    Normally, you should not use different series groups if the same number range has to be used. In fact, the concept of series group has been developed to ensure that number ranges can be maintained separately.
    Regards,
    Aroop

Maybe you are looking for