Same Document type, Different number ranges

All SAP Gurus,
I want to assign  Different number based on movement types, but the problem is that both the number ranges (101 for purchase order and 122 return delivery to vendor) are having the same document type (WE).
Is it possible to assign different number ranges to them?
Please give ur valuable suggestions.
Regards

In Std SAP , It is Not Possible..

Similar Messages

  • 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.

  • One order type different number range for different company code

    Hi
    I have created one order type. Same order type I extended in another company code (plant).
    I required different number range for another company code.
    Can any give detail solution.
    Regards
    ARK

    Hi,
    In CO82, define groups of order types. Define number intervals and assign number intervals to groups. Organize order types that you want to assign same number interval under groups.
    Regards.

  • To create document type related number range

    Dear Experts,
    I want to maintain number range document typewise say ABC, XYZ, LMN.
    For these document type i want to maintain internal numcer range.
    Please suggest.
    Thanks

    Dear all,
    Go to SAP customizing implementation guide--> cross application component->  Document management--> control data--
    .> Define ducument type.
    Select document type for which internal number range has to be assigned and click on Details
    nuber range assignment should be  '1'
    Then select the Internal number range for which your are going to assign  say 04/05/06/08  etc
    Then come back
    Go to SAP customizing implementation guide--> cross application component->  Document management--> control data--> Define number range for document number
    here for assinged number maintain required number range.
    Thanks

  • Document Types and  No range

    Hi Gurus, i am new to SAP,
    please guide me in
    Configuring  document types and number ranges for PR, RFQ, PO, Quantity Contract, Value Contract and Scheduling Agreements with release.
    Thank is Advance
    Kapil

    You have to maintain No Ranges for PR at Materials Management->Purchasing->
    Purchase Requisition->Define Number Ranges
    Define number range interval
    Choose type of number assignment (internal or external)
    You maintain the associated number ranges in the step Define Number Ranges under "Purchasing".
    SAP recommends that you accept the settings defined in the standard system. In this case, no action is required on your part.
    <b>Document type</b>
    Purchase Requisition->Define Document Types
    Steps
    1)Create new document types
    2)Define the item interval
    3)Allowed Item category.
    4)Define allowed follow-on document types
    5)Assign document types to a number range group
    Similarly for all the processes you can maintain Number ranges and Document Types at IMG menu path at Purchasing.
    Reward if helpful
    Regards
    Sanjay l

  • Number range based on different business area for same document type

    Hi All,
    The scenario is my client wants to give the different number range for a particular document type based on different business area.
    Is there any user exit by which I can restrict the same.
    Regards,
    Meenakshi

    Hello,
    Document number ranges are created per company code and fiscal year. You cannot create / restrict the document number ranges per business area.
    Business areas a independent of all organizational values, they cut across all company codes.
    Regards,
    Ravi

  • Different number ranges for same order type

    Hi PP Guru's ,
    Can anyone send me the user exit for the differnet number range creation for the same order type.
    Same order type is used in two different Plants. So our client want to track the production order plantwise.
    Thanx in advance.
    Regards,
    Nagraj

    Hi Nagaraj,
    The number range is defined at order type level ( i.e. client level)
    So if you want to use different number range for different plant,  then use different order type for different plants.
    Thanks and regards
    Murugesan

  • Different number range for different  sales area but same order type

    i have 2 different sales area but i have assigned same sales order type for 2 different sales area,
    but i need the number range different for different sales area for that same sales doc type,
    is that there is any user exists for number range? if so how can i find the user exists

    Hi,
    You can surely have a different number range per Sales Area. For this you will have to make use of a User Exit (which would surpass the standard SAP functionality). Try USEREXIT_NUMBER_RANGE.
    Maintain the desired range in VN01 with the respective Range Keys.
    Make a custom table comprising of Sales Area and Number Range keys (same keys which you maintained in VN01).
    Now everytime, the system will check which sales area is used and accordingly, it will fetch the Number Range Key~Sales Area combination from the custom table, and will pick up the number range from VN01.
    Coding should done by a good technical guy to make this work nicely.
    Hope this helps you.
    Regards,
    Vivek

  • Is it possible to create Order type with different number ranges-Plant wise

    Hi Experts
    Client wants to get the different number ranges for the order types created in the different plants. Is there any user exit for the same.
    I have assigned the order type to the different plants. And Order type is assigned to a no range. So whenever a order type is created in different plants; order types uses the same number ranges.
    so with this situation one cann't know the total no. of order created within a plant.
    Is there any solution for the same.
    Pease give your valuable solutions.
    Regards
    Pankaj

    Hi
    Best way is to create different order types for different plants.
    like we have order types OR15 ,OR20 & OR30 for different plants 1500 ,2000 & 3000 .
    you can assign different number range for different order type.
    this is simplest solution.
    Regards
    Sujit

  • Duplicate BP Reference Numbers for same document type -need check on orders

    Version: (2007A)
    Description of requirements:
    The user is allowed to create two sales orders for the same customer that have exactly the same BP Reference. When the user invoices one of them and then tries to invoice another, they are  warned that there is already a document of the same type with this reference number. The problem is, they ship the goods out physically before they actually create the invoice document, so that by the time they are entering the invoice in the system, the goods have already been shipped twice, when they should only have been shipped once, If they were warned when they were adding or updating the order, then this could be prevented from happening. Same thing for vendors. Our customers would like to have the check for duplicate BP references on the purchase order as well as on the AP Invoices.
    Business needs: Our Clientsu2019 customers are receiving duplicate shipments and this has a negative impact on their business relationship as it creates costly extra work and inconvenience for all.
    Examples: Would like the same check that is currently on AR and AP Invoices for the same BP reference number existing already on the same document type implemented on the sales order and purchase order. When the user is adding an invoice for a BP and there is already an invoice for the BP with the same BP reference number, the user is warned and asked if they want to continue.
    Current Workaround: None. As our customers often physically ship the goods before creating an invoice from the order, there are duplicate shipments and this is most inconvenient and costly to our customers as well as their customers.
    Proposed solution: see above. This is a high priority item for our customers.
    Sally Weinrauch,
    Senior Support Analyst
    Coastal Range Systems Inc.
    Recipients of: SAP's Partner of the Year 2007 & 2005,
    North America's Top Ten 2008, 2007 & 2006.
    200 - 6400 Roberts Street, Burnaby, BC, V5G 4C9

    hi,
    Use SP_TransactionNotification to block sales order & purchase order from adding having duplicate bp reference number.
    SAP Note 1258097 - Can the Suppliers Reference number be
    made unique? activated approval procedure also for ar invoice.
    It may solve problem.
    Jeyakanthan

  • How can I setup different number range for each company code?

    Dear GURU,
         Is it possible to setup different number range for material document by company code? If yes, what should i do.
         Thank you in advance.
    Thammarit

    Hi,
    you maintain the number assignment for the following documents:
    material documents
    physical inventory documents
    The number assignment for these documents is not to be confused with the number assignment for accounting documents . The number assignment for accounting documents depends on the document type which is allocated to the transaction.
    The number assignment for material documents and physical inventory documents depends on the transaction/event type which is also allocated to each transaction in Inventory Management. The transaction/event types are divided into groups of number ranges. A number range interval has to be defined for each group.
    You cannot change the transaction/event types. However, you can change the number range intervals or you can allocate transaction/event types to new groups.
    Caution: Change in the Fiscal Year
    If, at the time of a fiscal year change, you reset the number range in the new fiscal year, separate number range intervals for the previous year and for the current year must be maintained for one month to allow postings to the prior period.
    Example:
    Interval for 1995: 4900000000 to 4999999999 status: 4900451234
    Interval for 1996: 4900000000 to 4999999999 status: 4900000000
    If only one number range interval exists for both years and you make any postings to the previous period, the system will assign numbers that already exist in the previous year. This would lead to an update termination.
    In the standard system, the transaction/event types and number range intervals are preset for Inventory Management as follows:
    Physical inventory documents
    Number range interval from 0100000000 to 0199999999
    This group contains the following transaction/event types:
    - IB Physical inventory documents
    - ID Physical inventory documents for counts and differences
    without reference
    - IN Physical inventory documents for recounts
    - IZ Physical inventory documents for count without reference
    - WV Physical inventory documents for difference postings in the WM System
    Material documents for goods movements and inventory differences
    Number range interval from 4900000000 to 4999999999
    This group contains the following transaction/event types:
    - WA Goods issues, transfer postings, other goods receipts
    - WH Goods movements for handling units (HU)
    - WI Material documents for inventory adjustment postings
    - WL Goods issues for delivery documents (SD)
    - WQ Goods movements for usage decisions (QM)
    - WR Goods movements for completion confirmations (PP)
    - WS Goods movements for run schedule headers (PP)
    - WZ Documents for batch status changes
    Material documents for goods receipts
    Number range interval from 5000000000 to 5999999999
    This group contains the following transaction/event types:
    - WE Goods receipts for purchase orders
    - WF Goods receipts for production orders
    - WO Subsequent adjustment of subcontract orders
    - WW Subsequent adjustment of active ingredient materials
    Inventory sampling numbers
    Number range interval from 0200000000 to 0299999999
    This group contains the transaction/event type SI.
    SAP recommends that you accept the settings defined in the standard system. In this case, no action is required on your part.
    Note
    For performance reasons, 10 document numbers are buffered on the application server. In this way, gaps in number assignment can occur.
    Actions
    Check whether you can use the predefined groups and number intervals.
    If you want to change any groups, proceed as follows:
    a) Choose Group -> Maintain.
    b) Select the transaction/event type that you want to re-allocate.
    c) Place the cursor on the new group and choose Edit -> Assign element group).
    d) Save your settings.
    If you want to define new groups, proceed as follows:
    a) Select Group -> Maintain.
    b) Then select Group -> Insert.
    c) Enter a text for the number range group.
    d) Maintain the number interval for this number range group.
    e) Allocate the transaction/event types to the number range groups (see step 2).
    If you want to maintain new number range intervals for an existing group, proceed as follows:
    a) Choose Group -> Maintain.
    b) Select a group and choose Interval -> Maintain.
    c) Choose Edit -> Insert year.
    d) Maintain the number interval for the new fiscal year.
    If you do not want to use the year-related number assignment method, enter 9999 in the field Year.
    Note on transport
    You transport number range objects as follows:
    In the initial screen, choose Interval -> Transport.
    Note that all intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.
    Dependent tables are not transported or converted.
    Thanks and regards
    Rajesh

  • 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

  • Different Number range for different objects

    HI Gurus
    Could you please explain how can we make different Number range for different objects(O,S,P).Can we do with standards or we can go for UserExit??.
    Your early Advise will be appreciated.
    Thanks
    Chandra

    Hi Chandra,
    SM31 -> T77IV : 01S -> Number Range Maintenance.
    (or SPRO -> Pers Man -> Org Man -> Basic Settings -> Maintain Number Ranges)
    For the subgroups
    01C (plan variant 01, Object type C) Job
    01O (plan variant 01, Object type O) Org unit
    01S (plan variant 01, Object type S) Position
    Define the following number ranges respectively.
    (EX 60000000 69999999)
    (EX 70000000 79999999)
    (EX 80000000 89999999)
    Regards,
    Dilek

  • Same FI and SD number ranges

    Hi,
    How can in the system FI and SD number range for billing documents be made same.
    thanks
    Rekha

    Hi,
    FI and SD number ranges can be made same for billing documents. SD number range should be made internal and FI number range should be made external.
    Thanks
    G.Bharathi

  • Generation of Billing Document with odd number range.

    Hello SAP folks,
    There is specific issue related to billing document which are generated on Production server. There are billing document which are created on a date lets say 06.01.2009 and number ranges are assigned to it. But when another Billing doc is created on some later date, then how come the number of that billing document be less number range produced on 06.01.2009.
    Billing doc -- > 95906218 dated 06.01.2009
    Billing doc -- > 95906249 dated 13.01.2009
    Billing doc -- > 95906264 dated 06.01.2009
    Could anyone throw any light on the reason for this topic ???
    Regards,
    Sarthak

    how come the number of that billing document be less
    One possible reason could be the user would have executed via VF04 and selected for collective billing.  Based on ascending order of delivery documents, invoice would also have been generated.  This means, you have to check the corresponding delivery for the following:-
    95906249 dated 13.01.2009  and
    95906264 dated 06.01.2009
    If my assumption is correct, the date what you had indicated is nothing but "Actual GI Date" from delivery.  Having said this and also as stated above,  delivery would have been created first for the billing document dated 6th and followed by the other delivery on 13th.
    thanks
    G. Lakshmipathi

Maybe you are looking for