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

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.

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

  • 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

  • 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

  • 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

  • How to create document type ?

    Hi experts
    We need assign document type to mateiral in material master. So we need create new document type background. How to create it ? Does it just copy one doc type from spro-> cross application componets-> document management-> define document type?  It seems it will also copy the following screen setup .... but dont' know anything else need be setup ?
    Thanks
    Alice

    Hi Alice,
    You have create document type from
    spro-> cross application componets-> document management-> define document type
    There are already standard document types available. You ca use that or copy and create new types and assign it on the material master.
    Thanks and regards
    Murugesan

  • Dynamically create document type Item Attribute using WF_ENGINE.AddItem API

    Hi
    Is WF_ENGINE.AddItem API , supported to create document type Item attributes dynamically ? If yes how do we set the display name of the attribute. If no then is there is any other method to dynamically create document tyoe item attribute?
    Thanks

    Hi,
    If the document is stored on a file system, then I would replace the message body with a PL/SQL document which includes links to the files as straightforward URLs. There would be no need to include them in the Workflow in any way. For example, I recently worked with a client where all the (file) attachments made within eBusiness Suite were then migrated into Oracle Universal Content Management and the attachment was replaced with a URL to the new document. Any notifications now just reference the URL link to the document within the document management system in an HTML notification. While the processing is going on, the user is given the list of files that exist as attachments, but no links because the document is being processed by the management system.
    If the attachments are going to be stored in Workflow as documents, you won't be able to change the display name though - display name is set for the attribute on the message, not for each specific notification. Changing the value of the display name for the message would impact all notifications that use that message, which isn't what you want.
    What you need is to dynamically build the notification (either using PL/SQL or OA Framework) and include a list of attachments in the notification. This may be a direct link to the document (either in a document management system or on a file system somewhere) that you can render as a URL, or a link to code that can retrieve the document from the database and serve that to the user. This is not a straightforward piece of work.
    If this is purely internal, you might be better off having a custom form / screen which displays the different documents, and link to that from the notification. Or you could link to a standard form for the transaction and have the users pick up the attachments directly from the transaction.
    HTH,
    Matt
    WorkflowFAQ.com - the ONLY independent resource for Oracle Workflow development
    Alpha review chapters from my book "Developing With Oracle Workflow" are available via my website http://www.workflowfaq.com
    Have you read the blog at http://www.workflowfaq.com/blog ?
    WorkflowFAQ support forum: http://forum.workflowfaq.com

  • Document type and No. range for non leading ledger

    Hi Friends,
    can anybody tell me about the document type and No. range I can take for the non leading ledger.
    Regards

    Ok Pankaj,
    I am taking document types by copying it from the SAP standard document type and the No. range identical to the No. range assigned in the standard Doc. type. Is it ok
    LA                9A                               
    LB                 9B
    LC                 9C
    LD                 9D
    LE                  9E
    LF                  9F
    LG                  9G
    LH                  9H
    LI                   9I
    LJ                  9J
    LK                 9K
    LM                 9L
    LN                 9M
    LN                 9N
    LO                 9O
    LP                  9P
    LQ                 9Q
    LR                  9R
    LR                  9S
    LS                  9T
    LT                  9U
    LU                 9V
    LV                9W

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

  • Document Types and No. ranges

    Hi Gurus,
    How many types of document types should we have in a business?
    If we have 5 banks and client wants number ranges of bank vouchers related to one particular bank should be in continuation, so How it should be done?
    Please revert asap.
    Thank You

    Hi
    Firstly, there is no fixed number of Document types, depending upon the need, the business can have any number of document types.
    For your requirement, analyse the nature of transactions for every bank and create as many document types as the bank has if client wants to have the number range similar / in continuation along with the bank.
    I know this is not practical. But atleast, you should try to minimise the number of transactions to be in line with the bank, so the number of document types you should create.
    Thanks
    Siva

  • Movement type wise number range

    Hi,
    We have created a 'Z' Movement type (copying 541 movememt type).
    Now, we want to assign a new number range to this 'Z' Movement type.
    How it can be done?
    Regards,

    Hi,
    As per SAP Standard, we assign no:ranges to document types only such as WE,WA etc in MM-Inventory management.
    Hence you have to create Z - No range object &  assign the same to your Z movement.
    check for available BADI's/User Exits to meet your requirement.
    Thanks & Regards,

  • Plant wise, Delivery type wise number range

    Is it possible maintain of number range plant wise and delivery type. If possible can suggest the user exit with related program.
    Can some body arrange the document regarding depot excise process which inclusive of A certificate registration etc.

    Hi Rao,
    use MV50AFZ1 user exit
    FORM USEREXIT_NUMBER_RANGE
    Reward points if it helpful
    Regards
    Govind.

  • Re: Creating document types

    Hello,
    Can you post a snipet from the code that you are using?
    Regards,
    Shane
    In article <R_ZIc.1560$[email protected]>,
    [email protected] says...
    > I've got a GW 5.x postoffice in a lab enviroment for testing. One thing I
    > have to do is create some GW documents using the 5.x client. The client
    > refuses, saying "invalid entry" for the document type (which is set to
    > "Document", and says I have to pick a type from the list. But there is
    > nothing in the list. How do I go about putting some entries in the list?
    > Or is this some other problem?
    >
    >
    >

    Hi...
    I've written down my suggestions here because the support can't help me farther.
    The B1 Support told me that here are members of the Solution Management team in the Forum (View SAP Support Number 1028874 - Missing Functionality / Product Development Collaboration). But - none of my "wishes" have been answered.
    Whats wrong here?
    A simple thing like "Will come in the next Patch" or "Is not manageable" will be enough for me.
    It's essential for our customers to get these functions or know when it will be implemented!
    Thanks!

  • Material type HERS - number range

    I have configured the HERS material type which external number assignment, however I am now encountering a problem with tcreate a purely numerical MMR.  I have selected "external no. w/out check" and that does not let me create MMR with only numerical digits. The MPN will be both alphanumerical, numerical or alphan. 
    any suggestions.

    Hi,
    The number range for material type can be External or Internal.
    If you have configured External number range for HERS material type,it will allow for  alphanumerical or  numerical whatever u wants.Accordingly u can define the number range in MMNR Transaction code
    If you have configured Internal number range for HERS material type,it will allow only numerical Numbers..

Maybe you are looking for

  • How to Count schedule lines in IDoc ORDERS05 using XSLT Mapping

    Hi Experts, In a Scenario where we are sending Purchase order (ORDERS05) to SAP SNC using XSLT Mapping, where in we need to count the no. of schedule lines against the Purchase Order line. As in Schedule line segment there is no such provision, so it

  • How can I correct time zone information

    Yesterday  Europe/Moscow zone was changet from  GMT+4 to GMT+3 I've managed to adjust ical4j.jar library replacing Moscow.ics by this very simple zone file BEGIN:VCALENDAR PRODID:-//Oracle//Calendar Server//EN VERSION:2.0 BEGIN:VTIMEZONE TZID:Europe/

  • Error in the browser

    I have generated with JHeadstart a master detail form. When I run the application i get a error in the browser in second page. line 1 char 17 expected '(' code 0 What kind of error is this. The UIX page generated with JHeadstart has a valid syntax Jd

  • Copy CS5 batch files to CS6

    Hi: Am in the process of upgrading from CS5 Design Standard to CS6 DS. I had no problem copying my custom InDesign workspaces from the earlier version to the new version. What I'm having a hard time with, is how can I get the batch files I use in Pho

  • Mail & location settings question

    Can I customise mail to change its Outgoing Mail Server settings in conjunction with the Location settings in Network Prefs? I am always using my PB in different locations, while the Locations Prefs serve me well, I find I have to remember to manuall