Confirmation Number Range

Dears,
While doing PM order confirmation through IW41 we are getting error message as Update was teminated. When we analyzed this is because of number range conflict. Where do we maintain this number range?
Kindly advice
Senthil

Hi,
Once you create the Order, confirmation number will be assigned to that. While doing confirmation, against that predefined number, that confirmation will happen.
Give the order number (AUFNR) as input in AFKO table to get the Operation Task list number (AUFPL). Give AUFPL value in AFVC table to get the assigned confirmation number.
Against that number only, old confirmation will happen. Only for the new orders, new confirmation number range will be assigned.
Regards,
Maheswaran.

Similar Messages

Confirmation number reaches maximum number

Hi,
In my client production system, we are getting close to the limit in terms of QM Confirmation Number for Inspection Characteristic (table QAMV-RUECKMELNR).
We have standard SAP number range configuration 1 - 99,999,999 for object QMERKRUECK and actual number is <10%
To resolve the isse, we are planning to archive old inspection lots.
But my question is how the confirmation number behaves after archiving a set of inspection lots, we may face the situation where the confirmation number holds two inpsection lots ( one is archived & other is new)?
What will happen when the system start number with 1 and we would have duplicated numbers in table QAMV.
Please advise with details steps for archiving inspection lots and how the confirmation number reset to 1 and its consequences etc.,
Thanks a lot and best regards,
Nagesam

Thanks you Sujit,
You are saying to create new number range for inspection lots ( QCC3 ) and assign origin & type, please calrify if I am wrong. Please find my exact issue and help to fix...
In my production system.....
QMERKRUECK range is...
00000001 to 99999999 and the current number is already 91245679
and QLOSE intervals are below..
000000000001 to 009999999999
040000000000 to 049999999999
070000000000 to 079999999999
and the flag for 'No interval rolling ' is NOT checked, so the number range will be automatically resets to 1, once reaches to the upper limit
Issue : Warning message ' Internal number assignment for object QMERKRUECK (numbers are in critical area)" is showing while creating inspection lots using QA01.
What could be the best solution to fix this?
1. Archive old inspection lots ( on specific criteria ) ? Later, once the confirmation numbers reaches to 99999999, it will reset to 1. In this case...do we get the situation where the confirmation number holds both archived inspection lot and active ( newly created) inspection lot ? Do we have any business impacts?
2. How creating new nuber ranges for inspection lots fix the confirmation number range issue? Please clarify if I am missing anything.
Thanks in advance,
Nag

Number range of the "Confirmation of Service".

Hello, LE Experts,
I have a question about the number of "Confirmation of Service".
After completeing "Confirmation of Service" by VL02N, I can find its number in the document flow screen.
I want to know where I can find the number range for "Confirmation of Service" and if user have to care about overflow or not.
Regards,
Jun Shibata

I found theanswer in note 578766 ('Confirmation of Service' entries in doc flow disp (contd)) .

Number range of confirmation of service

what transaction code can we check the number range of confirmation of service.
thanks.

Hi,
You can create the number range from transction - SNRO assign the same in IMG.
or
In IMG under
Materials Management -> External Service management -> Number Ranges
-> Define Number Range for Service Entry Sheet
-> Define Internal Number Range for Service Specifications
-> Assign Number Range
Regards,
Naveen.

Just to confirm this feature in number range object

Hi all,
I've created one number range between 00001 to 99999. And i hope it will start over again automatically from 00001 after hit the upper limit.
I did not choose the "No Interval Rolling". Is that all i have to do?
thanks.

Hello,
I think this is correct.
From the F1 help from the field you can see:
Flag: No rolling of intervals
Selecting the flag prevents the number range object intervals from automatically starting from the beginning at the upper limit.
Regards,
David

External number range for purchase order response?

Hi all,
is it possible to use an external number range when creating purchase order responses (BUS2209, PCO, POR) manually?
If I transfer the POR from an external system like SUS via XML, can I use an external number range?
I'm using SRM 4.0 (EBP 5.0) in standalone scenario with Business Connector 4.7 as XML interface.
Any help is appreciated,
Karsten

Hi
No need to maintian Internal number range.. Yes you need to use an external number range
Only the PO, RQ & RS are sync and therefore must correspond with the R/3 number ranges.
The rest, Shop Cart (SC), Local PO (EBP), Confirmation, Invoice, Bid Inv and Bid, aren't synced and can be assigned to any number range. (FYI- using ECS)
Re: Extended Classic - Purchase Order Number Ranges
http://help.sap.com/saphelp_srm50/helpdata/en/87/7cc73cee4fb55be10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/6d/0f343e47fd6b2ee10000000a114084/frameset.htm
Re: Number range config
Re: config for Number Ranges ? :-(
Re: PO Creation with external PO number
Purchase Order Response BUS2232
PO number range Issue
Re: Defining the number range
Regards
- Atul

Number range for object MDTB does not exist - Message no. 61501

Hi All ,
I have done the necessary configurations in PP say
Order Type
Order Type Dependent Parameters
Scheduling parameters for planned & production order
Confirmation parameters
Availabilty check etc
and iam able to create planned & production order and confirma the production order.
I want to configure for MRP: -
Settings done are
Have activeted planning file entry for all plants.
When i run MRP system throws a error <b>Number range for object MDTB does not exist - Message no.61501 </b>
Is there anything to do with plant parameters OPPQ and Mrp Group OPPR.
I just tried plant parameters,standard 0001 is not available for copying.
Suggest me how to proceed to set MRP.
Shankar

Hi shankar
it is a good practice while creating the plant copying the plant from the standard plant so that all the standard table enteries will be copied for the plant as the standard plant is not there youcan think of copying from any other plant similar to your plant which has the required entry. else
in SE16N check the NRIV table for the Object MDTB. if enteris found then make the table entry with the help of abaper.
hope this helps
regards
SK

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.

Number range generation failure

Dear Team,
While creating 57F4 challan in J1IF01, we are getting followng error "number range generation failure". Kindly suggest why we are getting this error & also the solution.
Regards,
Sathya.

I dont remember correctly but we have to assign a number range to the excise group which we use while creating 57F4 challan.
check what exsice group / series group you are usiung ang check in customization whether numbner range has been assigneg to it.
I remember that number range should be for particular excise group and fiscal year.
check and confirm if your problem is solved.

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

Inspection lot number ranges skipping

My inspection lot number ranges are skipping, those are std number ranges like 01 origin, 04 origin etc, what could be the reason for that.
Inspn lots are getting generated and I took UD also. But certain numbers in the range got skipped.
Eg:- Incoming inspn lot 010000000041 then it comes 010000000045
Lot numbers 01/42, 01/43, 01/44 does not exist in sytem.
Please suggest a way out
Thanks
Vineeth
Edited by: vineeth varghese on Jul 18, 2008 11:31 AM

Craig,
But expert suggestion says, not to switch off buffer thru SNRO as it may affect fuctionality as you said early in this discussion.
But I believe, this is to be relooked by SAP as number range skipping is not good (My case its skipping 5-7 numbers at a time). But I am not convinced with the reply from SAP also.
Anyway thanks to you craig for your advice.
SAP Note on this matter for reference of all. Thanks
================================
Note: 62077
Summary
Symptom
Gaps (jumps) occur when allocating internal numbers.
The status of the number range interval does not match the number that was last assigned.
The number assignment does not reflect the insert sequence.
IMPORTANT: Read Notes 504875 and 678501.
Other terms
Document number, number range, number range object, buffering, current number level, trip number assignment, number interval, CO document, CO actual posting, inspection lot, material document, physical inventory document, production order number, planned order number, process order number, maintenance order number
FB01, VF01, KO88, KE21, KE11, FD01, FK01, XK01, XDN1, MB01, MB0A, MB11, MB1A, MB1B, MB1C, MB31, KANK, KB11, KB13, KB14, KB41, KB43, KB44, KB21, KB23, KB24, KB31, KB33, KB34, KB51, KB53, KB54, PR01, PR02, PR03, PR04, PR05, XD01, VD01, MK01, SNUM, SM56, SNRO, VL01, VL02, CO01, CO40, CO41, VA01, MR1M, MIRO
Reason and Prerequisites
A large number of number range objects are buffered. When the system buffers a number range object, it does not update numbers individually in the database but reserves a preset group of numbers (depending on the number range object) in the database the first time a number is requested, and makes these numbers available to the application server in question. The following numbers can then be taken directly from the application server buffer. New numbers are not used in the database until the application server buffer has been used up.
The effects described under "Symptom" are a direct consequence of this:
If an application server is shut down, the numbers that are left in the buffer (that is, that are not yet assigned) are lost. As a result, there are gaps in the number assignment.
The status of the number range interval reflects the next free number that has not yet been transferred to an application server for intermediate buffering. The current number level therefore does not display the number of the "next" object.
The current number level (for each server) can be displayed using Transaction SM56. Call transaction SM56 and choose the menu 'Goto' -> 'Entries'. In the dialog box, enter the client, the affected number range object (for example, RK_BELEG) and possibly the required subobject (corresponds to the controlling area for the object RK_BELEG).
If you use several application servers, the numerical sequence will not reflect the (chronological) insert sequence because the numbers are buffered separately on the individual hosts.
Buffering the number range objects has a positive effect on performance, because the system no longer has to access the database (number range table NRIV) for each posting. Furthermore, a serialization of this table (database locking) is prevented to a large extent so that posting procedures can be carried out in parallel.
Solution
Since number range buffering does not cause any expressly assured qualities to be lost, no correction is required.
If you still require continuous allocation, you can deactivate the number range buffering specifically for individual objects.
Proceed as follows:
- Start Transaction SNRO and enter the affected object.
- Choose 'Change'.
- Deactivate buffering: Choose 'Edit' -> 'Set Up Buffering' -> 'No Buffering'.
- If you want to change the buffer size only, enter the corresponding value in the field 'No. of numbers in buffer'.
- Save the changes.
Please note that this change is a modification. The modification is overwritten as soon as the affected number range object is redelivered - in other words, you must check the change manually each time you import a release.
In particular, read Note 678501, bearing in mind that changing the buffering type - if not explicitly recommended by SAP - constitutes a modification. For other possible solutions, refer to the following notes:
179224, 599157 and 840901.
For the the following number range objects, gaps may cause users to have doubts since they are 'expecting' a sequential numbering:
Area CO:
- RK_BELEG   (CO Document)
CAUTION: Note that the problems described in Notes 20965 and 29030 may occur if you deactivate buffering.
- COPA_IST (Document number in actual posting)
- COPA_PLAN (Document number in planned posting)
- COPA_OBJ   (Profitability segment number)
Area FI:
- DEBITOR    (Customer master data)
- KREDITOR   (Vendor master data)
Area HR:
- RP_REINR (Trip numbers)
Area PM, PP, PS
- AUFTRAG    (Order number, production, process, maintenance order, network number)
- QMEL_NR    (Number range - message)
Area MM:
- MATBELEG   (Material documents)
- MATERIALNR (Material master)
Area QM:
- QLOSE      (Inspection lots in QM)
- QMEL_NR    (Number range - message)
- QMERK      (Confirmation number)
- QMERKMALE (Master inspection characteristics in QSS)
- QMERKRUECK (Confirmation number of an inspection characteristic in QM results processing)
- QMETHODEN (Inspection methods in QM)
- ROUTING_Q (Number ranges for inspection plans)
- QCONTROLCH (Quality control chart)
Area Workflow:
- EDIDOC     (IDocs)
Number range buffering can be activated or deactivated at any time.
Number range objects that have to be continuous due to legal specifications (for example, RF_BELEG, RV_BELEG), or due to a corresponding application logic must not be buffered using the buffering type 'Main memory buffering'. See also Notes 37844 (for RF_BELEG) and 23835 (for RV_BELEG).
Header Data
Release Status: Released for Customer
Released on: 10.07.2007 12:57:00
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-SRV-NUM Number Range Management
Secondary Components: CA-GTF General Application Functions
BC-SRV-ASF-UOM Unit Management
CO Controlling
CO-OM-CCA Cost Center Accounting
CO-OM-CCA-A Master Data
CO-PA Profitability Analysis
FI Financial Accounting
FI-AP Accounts Payable
FI-AR Accounts Receivable
FI-GL General Ledger Accounting
FI-TV Business Trip Management
LO-MD-MM Material Master
MM Materials Management
MM-IM Inventory Management
MM-IM-PI Physical Inventory
PM Plant Maintenance
PP Production Planning and Control
QM Quality Management
QM-PT Quality Planning
QM-QN Quality Notifications
Edited by: viny on Jul 23, 2008 9:18 AM

TDS Certificates Number Range issue

Dear all
I am doing J1INMIS for particulat section code say 3200 and withholding key 194 c, then i am updating the challan and it takes me to screen Create remittance challans, here after processing i get the following error-
<b>Number Group not maintained for CO code 1000 section 3200 and business place 194 C</b>
kindly suggest , is there any table to update , as i have chked the table where in found that number group is also maintained and internal number range is also assgined...
please let me knw if any other table needs to update,
regards
sgs

Hi,
Good evening and greetings,
Please go through the following link...You will have to maintain the number range for your TDS Certifcates...I will confirm the tcode for the same...
http://help.sap.com/saphelp_erp2005vp/helpdata/en/29/3e3d911ab311d4b5b5006094b9ec21/frameset.htm
Please reward points if found useful.
Thanking you
With kindest regards
Ramesh Padmanabhan

Prefix Number range: Transport number range

Hi All,
Here is the situation. there are 2 dev servers. the prefix number range in both are maintained as 901 . The workflows will be trasported to a single prod servers. Now as i understand this will create some trouble in prod coz two workflows in two system might have the same number.
Now I think maintaining different number range might help. but when transporting to prod how willl this number range will be taken into account. I mean how to make sure that 901 will be transported as 901 and same as 902 range? Do i need to maintain some config in prod system or just reserving both the number ranges 901 and 902 in prod will solve the issue? Just need some confirmation ..
Thanks in Adv !
Anuj Sethi

Exactly. The numeric ID that is assigned to your workflow template follows it through the transport system in the same way that the include for a function module follows it.
The difference between workflow templates and reports (in this matter) is that you are not allowed to define the program name of the workflow template. Instead it is composed from the prefix and the next available number in that prefix range.

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

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

Confirmation Number Range

Similar Messages

Maybe you are looking for