Number ranges - APO or ECC system - Which one is master system?

Hi
In SRM always SRM system is a  master system for issuing number range. to create a folow on documents like purchase request and Purchase order . SRM system always determines the number range  for  purchase orders , Purchase request .
for example in Classic scenario :-
SRM we create a Shopping cart and Purchase order in  ECC system.but SRM determines the number range which number Purchase order needs to be created.
What about in APO number ranges for Purchase request and Purchase order ? .iS That SAME ? .
In APO , do you have technical scenarios like Classic and Extended classic?
classic :- shoping cart crated in SRM and Purchase order will be created in ECC system.
Ext Classic :- Shopping card created in SRM and Purchase order will be created in SRM itself and replicated to ECC system.
But both above scenarios, SRM system is a master system to issue number ranges.
i learnt that APO system dont supply any number ranges to create a PR or PO in ECC system (trigger from APO) only ECC system determines? is it true?
BR
Muhtu

Hi,
For Purchase requisition there is temporary number range in APO system but once requisition gets transfered to ECC through CIF it determines number range from ECC and returns back same number to APO.
For Purchase order number range exists in ECC only and not in APO. Even if you trigger conversion of PR to PO from APO number range will be taken from ECC only.
So ECC remains master system .
Regards,
Santosh

Similar Messages

  • Z Number range objects in ECC 6.0

    Dear SMRer's,
    System Info: SRM 5.0 and ECC 6.0
    I created some Z number range objects for eforms in ECC 6.0. And all of them went in to the same transport request DXXXXXXX . I just wanted to confirm if it is the right way to do it.
    Also, if some one can throw light on the transport mechanism that would be great.
    Points will be rewarded for answers,
    Best regards,
    Bob

    Hi,
    Usually best practice is to not transport number range but to recreate it in the target system.
    However, technically it is possible.
    Kind regards,
    Yann

  • Vendor Number Range Conflict SAP ECC and CRM 2007

    I need to load SAP ECC Vendor data from SAP to CRM and have setup most of the configuration as required. However I have an issue, the vendor number range used currently in our SAP system is already in use in our CRM system and has been for some time (for Prospects and Contacts).  What is the best approach to dealing with this issue...
    My initial thought was to see if we could have two different numbers for the same vendor in ECC and SAP CRM
    eg SAP Vendor "50000001" equates to CRM "VEN50000001"
    Is such as approach supported?  Can you point me to the documentation that shows how such an approach could be implemented.  What approaches have others done to address similar issues?
    Thanks in advance
    Eddie
    By the way we are on CRM 2007 sp4

    Hi Eddie,
    SAP Note 1044637 - Customize Vendor Numbers
    Implement the code present in the attachment. You can
    change it according to your own requirements. The example code
    suffixes 'VEND' before the first six digits of the vendor
    number before it is downloaded to CRM.
    Thanks,
    Vaibhav Shah

  • Same material number Ciffing from different ECC system

    Hello Gurus,
           I have APO system connected with two ECC system.
    If there is a material with the same name in both the system how does the APO system finds the respective system.
    Even if I assign BSG for the logical systems, to which system will the transaction data will be transferred after planning?
    Thanks,
    Siva.

    Although I do not have real-time experience working in this kind of scenario from what I understand there will be two product-codes based on the BSG.
    Eg. HAMMER@BSG1 will be the Product code for material HAMMER coming from your first ECC system which is mapped to BSG1 and HAMMER@BSG2 will be the product code for material HAMMER comping from the other second ECC system that is mapped to BSG2.
    Transaction data will then flow back from APO to respective ECC system based on the BSG mapping. Note in the Distribution Definition you maintain the connected ECC logical system name as well.
    Hope this helps.
    Thanks,
    Somnath

  • Number ranges for orders - divide an existing one/ add a new one

    Hello,
    following two problems:
    - We have an CO order number range from 4000000 to 4999999; these range is used for quality orders as well as maintainance orders (two different order types): Is there a way to divide this number range into 2 (so e.g. 4000000 - 4499999 and 4500000 - 4599999).
    - In addition we have to add a new number range for a totally new order type. Unfortunately I don't find any possibility to add one to the existing ranges (T-Code KONK/ Customizing) - where can I do this?
    Thanks a lot in advance!
    BR,
    hansi

    Hi,
    In other words, you want to maintain number ranges as:
    4000000 - 4499999 : Quality orders
    4500000 - 4599999 : Maintenance orders
    You can split the number range into two by changing the existing 'To number' from '4999999' to '4499999' and creating another number range for 4500000 - 4599999. Now, it is a question of unassigning Maitenance order type from numer range1 and assigning to new number range (4500000 - 4599999) which I don't think is possible.
    As regards, creating new number range: KONK> Maintain groups (F6) > Group > Insert (F6)..give a text to the number range group and assign the number range. Once you have created the group assign your new order type to this number range group.
    Hope this helps.

  • ERS number range for France (ECC 5.0)

    Hi,
    We have done the required settings for the vendor wise sequential reference number in ERS invoices for France.
    1. create number group
    2. create number range
    3. assign number range in company code additional data
    4. assign number range group in 'tax number 4' in vendor master
    Still, the sequential number is not updated in the ERS vendor invoices. And MM document number is getting updated in the reference field.
    What could be wrong? Any clue?
    Regards

    I got the same problem.
    I have OSS but could not find any notes relating to this.
    Looking for help too.

  • Classic - SAME PO number ranges in SRM  PO via SC as well as ECC PO  via PR

    Hi
    for example we do have PO
    existing
    PO 54XXXXX number serial creates via SRM by shopping cart
    PO  55XXXXX number serial created PO via ECC system
    but business now wants same number ranges for Both system Purchase orders WHATERVER IT MAY BE.
    54XXXXXX only for SRM created PO as well as ECC PO .
    SC IN srm  PO in ECC 54XXXXX
    PR-PO in ECC 54XXXXX
    is it possible? TO HAVE SAME NUMBER RANGE
    *CUSTOMER EXPECTS LIKE BELOW.*
    *FOR EX  PO 540000001 CREATED FROM srm by Shopping cart
                  *PO 540000002 CREATED BY ECC SYSTEM.via Purchase request or direct me21n*
    HOW CAN I MAKE INTERNAL AS WELL EXTERNAL VIS DOC TYPE.
    THEY DO NOT WANT TO HAVE TWO SEPARATE NUMBER RANGES FOR ONE BUSINESS OBJECTS. aNY ONE ACHIEVED IN REAL TIME?
    br
    Muthu

    Thanks much Ahmed for confirmation on this.Appreciate you  Ahmed on this help.
    why i have asked this question we do create some PR from APO system. but their APO Purchase request uses same number range in the ECC system.
    for eg. APO creates PR -300001
                ECC creates PR -300002
    but i dont know how it achieved in APO -ECC scenario.
    Muthu
    Edited by: Muthuraman Govindasamy on Jan 16, 2010 3:01 PM

  • Transporting Number range Intervals

    Dear SRMers
    System Information: ECC 6.0,
    We created Z Number range objects in ECC system A and transported them to ECC System B.
    The custom objects were transported, but the number range intervals did not transport to the target system. My question is do we need to transport the number range intervals for the custom objects seperately?
    Points will be rewarded for answers.
    Thanks in advance,
    Best Regards,
    Bob

    Hi,
    Usually best practice is to not transport number range but to recreate it in the target system.
    However, technically it is possible.
    Kind regards,
    Yann

  • Number range" A to ZZZZZZZZZZu201D is not replicating to ECC

    Number range" A to ZZZZZZZZZZu201D is not replicating to ECC.
    Number range A to ZZZZZZZZZZ is assigned to u201CAS04u201D Grouping in CRM system and this same number range are configured in ECC system as well.
    I understand that in order to replicate business partner we need to have same number ranges in both the systems and if CRM having external number range, R/3 number range
    Should be internal.
    I found in my systems, external check box is checked for this number range in both the systems.
    I tried to uncheck the external number check box in R/3 system and System gives an error message to u201Center a numeric numberu201D and it doesnu2019t allow me to uncheck the external number check box and save.
    Please advise, can we use alphabetic number range from CRM to R/3?
    Regards,
    Silpa.

    Hi Arup,
    Thanks a lot for your reply,
    Yes, we have configured the same number range in ECC as well.
    We have three account groups in CRM, number ranges configure correctly in both the systems.
    1)AS01
    2)AS02
    3)AS04
    AS01 is replicating from CRM to R/3 fine, but AS02, AS04 Groupings are not replicating to R/3.
    But i found some thing wrong in PIDE settings for AS02, AS04 groupings, below are the PIDE settings.
    CRM->R/3
    Classification/Account Group/Name
    A/AS01/End customer
    B/AS01/End customer
    E/AS01/End customer
    R/3->CRM
    Account Group/Name/Classification/Group/External
    AS01/End customer/B/03/External
    AS02/Agent/B/04/External
    AS04/Trading house/B/05/External
    Kindly note that, for AS04 grouping we would like to use external number range in CRM system.
    Please advise what should i change in PIDE settings?
    Regards,
    Silpa.

  • Classic & EC -  PO & other purchasing documents number range

    Hi SRM Gurus,
    Can any one please explain me more precisely about number ranges in SRM & MM.
    For classical scenario, we will define number ranges for PO & other purchasing documents in SRM as internal number ranges and in MM as external number ranges.
    But in Classical scenario we will create POs (or other Purchasing Documents) in backend system. Suppose If it is to be replicated to SRM as per business need, then how system works. Because we defined in SRM PO number range as internal number range and in backend system as external number range.
    Again in Extended Classical scenario, for MRP materials PR or Reservation will be created in backend system with internal number range. But in Plan-Driven scenario they will be replicate to SRM. In this case how we have to choose number ranges.
    I am confused. I'll appreciate if any one explains me with step by step or with examples for Classic and Extended classical scenarios
    Points will rewarded
    Thanks,

    Hi,
    Please find my responses in bold below:
    For classical scenario, we will define number ranges for PO & other purchasing documents in SRM as internal number ranges and in MM as external number ranges.
    Sundeep: In Classic Scenario, you do not define number ranges for PO internally in SPRO. You would only define number ranges for shopping carts, Confirmation and Invoices if required. Please see description of classic and extended classic scenario below.
    External number ranges are defined for PR's and PO's in ECC in a classic scenario environment. (No Internal number range is defined in SRM for these documents in classic scenario and a shopping cart is a PR in SRM)
    So, basically in classic scenario, you create only a Shopping cart (Internal Number Range) and all follow on documents such as PR, PO etc are created as external number ranges in ECC, which are a result of a shopping cart from SRM having an internal number range locally.
    But in Classical scenario we will create POs (or other Purchasing Documents) in backend system. Suppose If it is to be replicated to SRM as per business need, then how system works. Because we defined in SRM PO number range as internal number range and in backend system as external number range.
    Sundeep: This scenario is not possible. In classic scenario you cannot replicate the PO back to the SRM system. Such a scenario is usually accomodated by an Extended Classic Scenario.
    Again in Extended Classical scenario, for MRP materials PR or Reservation will be created in backend system with internal number range. But in Plan-Driven scenario they will be replicate to SRM. In this case how we have to choose number ranges.
    Sundeep: In a Plan driven procurement the PR is created in SRM as a shopping cart with internal number range. (PR = Shopping cart in SRM). No reservations are created locally in SRM from a PDP. Reservation are only possible in a Classic scenario from SRM -> R/3.
    · The classic scenario
    The shopping cart is created and approved in SAP Enterprise Buyer. The remainder of the procurement process takes place in the backend ERP system(s) and all other follow-on documents, such the purchase order, goods receipt/service entry sheet and invoice, are located there. With SAP Supplier Self-Services, you have partial supplier involvement for the operational procurement business scenarios when buying materials. There is no support for services.
    · The extended classic scenario
    The shopping cart is created in SAP Enterprise Buyer. The purchase order and follow-on documents are also created there and then replicated to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order and cannot be changed in the backend system. Goods receipts and invoices can be pre-entered in SAP Enterprise Buyer or entered directly in the backend system. With SAP Supplier Self-Services, you have partial supplier involvement for all your operational procurement scenarios. In these scenarios, you have supplier involvement for the purchase order and the purchase order response.
    Hope this info helps !!
    Pls assign points for usefull answers !!
    Sundeep
    Message was edited by:
            Sundeep Ravande

  • Automatic number range assignment for creation of material issue

    Hi Experts,
    I need to create material with automatic assignment of internal and external number range .
    Already existing logic for one exit which is working fine in one system and I am using that same logic in other system
    where it is not working and  throuhging the following error:
    "Internal number assignment is not possible for the material type Operating supplies"
    Can you please suggest where i am dong wrong ?
    Thank you in advance.

    Hi,
    Please slect material type operating supplies  click on detaials. check  the external number assignment w/o check  checkbox
    Regards
    AKM

  • Document number range object

    Hi
    Please tell document number range object . T-code :FBN1
    PLEASE URGENT
    Thanks
    Krishna

    Hello
    A number range must be assigned to each document type in the SAP System. Via the document types, you distinguish the postings according to the different business transactions, for example customer payment, vendor credit memo, and so on. To store documents separately according to document types, you must assign a separate number range to each document type, for example to invoices or to credit memos.
    In the following activities:
    You define your document number ranges.
    You can determine which intervals of document number ranges are to be copied from one company code into another.
    You can determine which intervals of document number ranges are to be copied from one fiscal year into another.
    Define Document Number Ranges
    In this IMG activity you create number ranges for documents. For each number range you specify (among other things):
    a number interval from which document numbers are selected
    the type of number assignment (internal or external)
    You assign one or more document types to each number range. The number range becomes effective via the document type specified in document entry and posting.
    You can use one number range for several document types. This means you can differentiate documents by document type but combine them again for filing the original documents, provided you store your original documents under the EDP document number.
    Note
    The type of number assignment is of special importance. For each document type you should check whether a separate number range must be used and which type of number assignment is most appropriate.
    One example of a case where external number assignment would be suitable is when you transfer documents into your SAP system from a non-SAP system. The numbers must be unique. The number range is not displayed with external numbers. You must therefore ensure that you do not skip any numbers when entering numbers manually (for organizational reasons).
    You should use internal number assignment if the original documents do not have a unique document number. This is the case, for example, with vendor invoices.
    Number ranges for documents are company code-dependent. You must therefore create your number ranges for each company code in which the document type is used, namely with the same number range key.
    The number intervals must not overlap. If you use year-dependent number ranges, you can specify the same interval with the same key several times for different to- fiscal years  (the limit up to which a number range is still valid). If you want to define number ranges which are independent of the to-fiscal year, enter 9999 in the to- fiscal year field.
    Caution
    For sample documents, use a number range with key X2, for recurring entry documents with key X1. These keys may not be used for other number ranges.
    Recommendation
    Store your original documents (paper documents) under the EDP number of the SAP System. You should write the EDP document number on the original document. In this way, the original document for a business transaction can be found at any time.
    Activities
    1. Determine how document filing is to be carried out in your company codes.
    2. Define your number ranges accordingly.
    3. Make sure that the number ranges are assigned to the corresponding document types.
    Copy to Company Code
    In this activity, you can copy intervals of document number ranges from one company code to other company codes. To do this, you have to store the following information:
    Intervals which are copied
    To fiscal year(s) (validity limit up until which the number range is valid)
    Company code from which you copy (source company code)
    Company code(s) into which you copy (target company code(s))
    Activities
    Make all necessary specifications for copying the number ranges.
    Note
    The number ranges are only copied into a target company code if no number ranges exist there within the selected "To fiscal year" interval.
    Notes on transporting
    The documentation for the step "Define document number ranges" describes how to transport document number ranges.
    Copy to Fiscal Year
    In this activity, you can determine which intervals of document number ranges are to be copied from one fiscal year into another per company code. To do this, you have to define the following information:
    Company code(s) within which you copy
    Number range number(s) which are copied
    Fiscal year from which you copy (source fiscal year)
    Fiscal year into which you copy (target fiscal year)
    Activities
    Make all necessary specifications for copying the fiscal years.
    Note
    The number ranges are only copied per company code into the target fiscal year if no intervals exist there for this fiscal year.
    Reg
    *assign points if useful

  • Multipe number range for indonesia tax invoice no.

    Hi All,
    I have one question to confirm with you all:
    Our indonesia office need to print out tax invoice when billing document is created.
    The format is TTS.BBB-YY.NNNNNNNN , and only TTS is fixed, the other 13 digits changes.
    And we can only get one number range from tax office for almost one month's usage, which means we can not maintain the number range for one whole year in one time.
    Question 1:  How to maintain mulitple of number ranges for one year:
    I'm thinking if we can maintain different number  in table "V_OFF_NUM_ID"
    2014/01/01 – 2014/12/31  900    ID0114  01
    2014/01/01 – 2014/12/31  901    ID0114  03
    2014/01/01 – 2014/12/31  902    ID0114  04
    2014/01/01 – 2014/12/31  903    ID0114  05
    2014/01/01 – 2014/12/31  904    ID0114  06 
    But the "code 2" is same sometimes, so I have to do so
    2014/01/01 – 2014/12/31  900    ID0114  01
    2014/01/01 – 2014/12/31  901    ID0114  03
    2014/03/28 – 2014/12/31  901    ID0114  04
    2014/01/01 – 2014/12/31  903    ID0114  05
    2014/01/01 – 2014/12/31  904    ID0114  06 
    But if so, I don't know when the billing date is after 2014/03/28, and the number "03" is not used up, system will pick number range of 04 or 03?
    Question 2:
    The revision billing document after reversal must have the same tax invoice no. with the "original billing" & reversal billing"
    The SAP standard use new tax invoice no.
    How to realize it?
    Question 3:
    YY is year and defaulted from billing date?
    Thanks and best regards
    Cathy

    You are correct that this is statutory requirement, and SAP deliver the solution, you can refer to note
    1033737 - Indonesia: Tax Invoice & VAT Reporting 1107 .
    However, from 04/2014, the requirement changes
    TTS.BBB-YY.NNNNNNNN
    Before: Only NNNNNNNN changes and SAP suggest using one number range
    Now: BBB-YY.NNNNNNNN  changes, and there are quite a few number range per each year.
    Can not get one number range for one whole year.
    Therefore, I raised my question as above. However, I think I have answer to my question, just I'm looking for one more perfect solution if there is:
    1> The answer for 1st question
    When the "code 2" is same sometimes, I will maintain as below
    2014/01/01 – 2014/12/31  900    ID0114  01
    2014/01/01 – 2014/12/31  901    ID0114  03
    2014/03/28 – 2014/12/31  901    ID0114  04
    2014/01/01 – 2014/12/31  903    ID0114  05
    2014/01/01 – 2014/12/31  904    ID0114  06 
    By testing, only if the number of 03 is used up even though the billing date is 2014/04/01, the number 04 will be used, so should be okay.
    2> The answer for 2nd question
    The revision billing document after reversal must have the same tax invoice no. with the "original billing" & reversal billing"
    The SAP standard use new tax invoice no
    Since there are only 3-4 reversal per year, so user can realize it by changing the "current number" in J1AB
    You mentioned it in
    http://scn.sap.com/thread/3519329
    but I did not try until I'm sure it will work
    3> YY
    I think it's should be from billing date.

  • For object RF_BELEG LT, number range interval 50 does not exist FBN1

    dear all
    system showing this message (For object RF_BELEG LT, number range interval 50 does not exist FBN1)

    Hey Manish,
    You can use these t-codes.It can be solved with all together number ranges.
    1- OBH2
    In this activity, you can determine which intervals of document number ranges are to be copied from one fiscal year into another per company code.
    2- OBH1
    In this activity, you can copy intervals of document number ranges from one company code to other company codes. To do this, you have to store the following information:
    Wish you all the best.
    Onur

  • Message while creating plant,Do you really want to transport number ranges?

    hI
    while creating plant[Copy from existing] i got the message 'Do you really want to transport number ranges?'
    can some one through some light on this message
    Thanks

    REad carefully the info coming along with this message.
    IF you transport number ranges, then you overwrite existing number ranges in your production system. you transport the e.g. the current number from your development system into production and overwrite there the current number.
    As you usually produce less data in Development system than in a production system, the current number will be smaller after the transport, and SAP would then try to create data using the next number, which leads to a dump as thereis already a record in the database having this number.
    so you should only transport number ranges if you do not effect existing number ranges in your production system.

Maybe you are looking for