MIGO Number range problem
For goods receipt in MIGO how to maintain different number ranges for different material types.
To maintain number ranges for material document u can use OMBT. Material document number can not be differentiated or maintained differently for Material types
Rgds,
Saurabh
Similar Messages
-
Billing Number Range problem ( accounting document not generated)
Hi All,
I have created some billing types and for them I have assigned some internal number ranges. Now when I create a billing document it is getting saved with the proper number range but no accounting document is getting generated.
Also when I try to release the invoice I am getting an error which says " *Incorrect doc.no.: 10000009. Select document number between 0090000000 and 0099999999* "
K I N D L Y suggest as U R G E N T.
Regards,
Danny.Dear,
Billing Number Range problem ( accounting document not generated) is not an error because when you create billing document then accounting document not generated. Accounting done after posting of that billing document with VFX3 or VF02 T.Code by account department.
And for second issue you had define number range between 0090000000 and 0099999999 for invoice so thats why it happen.
Regards,
Sandip Shaktavat -
Dear All,
Previously Document number range(FBN1) for Invoice was External, then i have changed to Internal number, now the problem is that in Counter it shows 1800000126 but system is showing document number 1800000136. Pls help on this & when i am changing from Internal to External system is showing error as "Lower limit can only be changed during Initial Entry".
Pls pls help on this.Dear ranjith,
If you want to change number ranges from external to internal no ranges,
from T-code FBN1 you can for the changes first go to ,<change status button> and make you counter no as 0 and save the intervals,
and come to change intervals button and change the no ranges according to ur requirement.
Assign points.
SU -
Error in MIGO :Number range object for object J_1IINTNUM, year 2010, excise
Dear Experts,
While posting MIGO, System throws below error :
Mainintain number range object for object J_1IINTNUM, year 2010, excise
Maiintain number range object for object J_1IRG23A1, year 2010, excise
Maintain number range object for object J_1IRG23A2, year 2010, excise
Actually we are posting the MIGO for the fiscal year 2009, still i am getting error why ?
regards
rajakarthik.check the posting date what u r puting , it should be on or before 31/03/2010
i think this is only the issue dont looks like any other issue
or do one thing just o\go in SNRO and for J_1IINTNUM object put 9999 year and the number range
and try to post your transaction in 2009
hope this helps
Edited by: Umakant Bhangale on Apr 1, 2010 10:22 AM -
Assessment: number range problem
Hi Fi-CO gurus's,
my problem is the following: I try to perform an assessment (Tx code 3KE5), but I receive an error message in the "display EC-PCA: Actual assessment basic list " screen:
Document number: range not found
And further:
Document number: range not found
Message no. GA703
Diagnosis
An error occurred during document number determination. No range was found for number range object GL_LOCAL, sub-object 0010.
System Response
No document number was determined. Results could not be updated.
Procedure
Inform the person in charge of number ranges.
Could anyone help me.
Thanks in advance.
Ric.Hi Seth,
I checked out table NRIV and found entry....
But in GB02 I have the following problem:
when I try to create an interval for the group (group maintenance) I choose "Act. document from direct posting with GB0" ...
There is no displayed number range and when I try to create it, it is not possible because there is already an existing number range, but it can't activate it...
An it takes all the available range (from 000000000 to 9999999999)
Regards.
Ric -
MIGO -Number range for trans./event type WE in year 2012 does not exist
Hi to all
i got one erro while going do MIGO , error is
Number range for trans./event type WE in yar 2012 does not exist .But i checked in OBA7 for the document type WE for that company code i have already maintain number ranges for the year 2011. but system showing error message is WE in year 2012 does not exist . how it showing .Actually My fiscal year is 2011 . why system asking maintain number ranges WE in year .After that i maintaion number ranges for the fiscal year 2012 . and try to post MIGO but i got the same error .Please help us in this sence
Error Details :
Number range for trans./event type WE in yar 2012 does not exist
Message no. M7562
Diagnosis
The number range for document number assignment has not been maintained in the year 2012 for the transaction/event type WE.
Procedure
Contact your system administrator.
If you are authorized to do so, do you want to check the number ranges for the
u2022 Material documents
u2022 Reservations?
Thanks in Advance
RajeshHi Tej,
Even I am getting the same error
"number range for trans./event type WE in year 2014 does not exist"
I have maintained the below number range in tcode OMBT,
Am I missing anything?? Please help!! -
Error : Message no. F5695 number range problem
hii all
i am facing a serious error. my 'SA' document type has picked up maximum number from the assigned no range. and so that i have assigned a new no range in SA document type
but when i am doing a new doument entry in Tcode - FB50 system pick the maximum number for the newly assigned no range and getting error messege
"Number range 6000 in year 22 has been used up for company code 2011"
Message no. F5695
Co Code = 6000
No Range = 22
Fiscal year = 2011
also when i am doing vendor invoice tcode = FB60, my system also shows the same error related to that document type. please help to resolve
i am also facing this no range problem when i try to post document from FI to CO. please see the link
http://forums.sdn.sap.com/thread.jspa?threadID=2132125&tstart=0
why system pick up the maximum no? i cant understand. i have checked the object RF_BELEG and RK_BELEG. in Tcode - SNRO. but there is no inconsistency. please also suggest what should be the standerd setting in the above object in Tcode-SNRO
please help. i am unable to post any document
Regards
Rajeshhi Marssel Vilaça
In FBN1 22 no range already has taken maximum no and showing the messege
"Number range 6000 in year 22 has been used up for company code 2011"
Message no. F5695
This is for SA document type. also when i make entry with different document type such as vendor Invoice (DR), it also picks the maximum number from the no range
You can I adjust my counter in BKPF? and how can i use the remaining no range?? in FBN1 all the no range in internal, not external
i am also facing this no range problem in CO also (Tcode = KANK).
I just confused. please see my 1st thread
please resolve
Regards
Rajesh -
Enhancement required in MIGO number range
Hi Gurus,
I have a requirement to decide the number range of GR document in MIGO transaction depending on the combination with Plant, document type, Movement type,year.
Is any enhancement available for this purpose ?
Waiting for your reply..
ThanksHi,
Inorder to set the number range you use the code OMC1, Click on the Object and create you required combination of the plant, stor loc & movement type.
These can done current using the help of fucntinal consutlant.
Path from SPRO>Material Management>Inverntory Management & phy manag-->Define Number assignment for GR.
Please close the thread,if solved
Regards,
Aditya -
My requirement is,
Currently my user is doing
Raw material Goods Issue - Movement Type - 101 - No Range E.g. 001-999 Transaction MIGO
And
Goods Issue for Finished Store - Movement Type - 101- No Range 101-999 Transaction MB31
what the user wants is to have a different No. Range for different material docs.
Is this possible?? if yes then how to do this? or
Is there is any exist for this?
Please give me a solution on this. As the user is adamant that he wants different No. ranges for different material docs.
Thanks in advance.Dear,
U can assign different Number Range for Issue or Receipt.
SPRO --> MM --> Inventory & Physical Inventroy --> Number Assigment --> Define number range for material or physical Invt.
WA for goods issues, transfer postings, other goods receipts
WE for goods receipts with reference to purchase orders
WF for goods receipts with reference to production orders
WI for inventory differences
WL for goods issues with reference to deliveries (SD)
WN for net posting of goods receipts
PR for revaluation documents
but one thing more, u can not assign individual number range for one type of difrent trnasctions eg good Issue againt Internal order or Good Issue to Cost Center.
this may help u
Reagrds,
pardeep Malik -
Hi,
I can see the latest quant number is 172 via tcode LS26, but current number in the customzing of quant number range definition is 170, so the errors occurred when the system tried to create TR, so what's the problem with the number range update?
Kindly please advise.
Thanks.Hi Jürgen L,
Thanks.
I've changed the current number range to a higher number, but I got the following error message when performing stock transfer
ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC
Another thing is, I transport all the WM setting including number range from DEV system into QA system twice, before that I've already perfom stock transfer in QA system.
Kindly please advise -
MIRO and MIGO number range for new financial year
All SAP Gurus,
We want same number range to be continued for MIGO and MIRO documents.
Is it needed to create the number range for MIGO and MIRO for new financial year or same number range will be continued automatiaclly?
Regards,hi,
The number range to be applied for the MIGO And MIRO documents depends on the YEAR which you have feed while maintaining the number range...If you want a new number range for next year, then you can maintain it from above transactions...Or if you wanna continue wid the same then can use the same number range as well...
As suggested maintain the number range get it applied, but remember if you maintain the number range as 2010 then that number range will be valid for the given year only...but if you give the number range 9999 then it will be valid upto 9999 year...
Hope it helps..
Regards
Priyanka.P -
Hi Experts,
I have to generate separate number range plant wise while posting the document in Migo.
Please suggest me how to do this.
Regards
MohitHi Mohit ,
first u need to check in CONFIG or try to post in MM forum.
regards
Prabhu -
Material Master Number range Problem
Hi Experts,
There is a Group 1 which has ROH assigned...then i changed the assignment,assigned ROH to a
Group 2.
Recently Material Type config was done in different R/3 system and transported to our R/3 system.I did had a look in the TR it had only material type releavnt changes like Authorisation group and S.ref material type (T134 and T134T)
But as a result ROH got reallocated to Group1 as initial.
I had checked the log in MMNR the log shows me the assignment ROH to a Group 2 which i have done as the last change.
No Clue what could have happened,If any one have some idea pls do let me know.
Thanks in advance.
RathaHi Dheeraj
I did found a root cause of the problem.
In Mat.type configuration there is number range code(NRC) 01,02,03 getting recorded.
In our system NRC for ROH was 01,but in other R/3 system NRC for ROH was 02
And when TR came from diff R/3 system our NRC was over written to 02.
Regards
Ratha -
i want to maintain the same excise number range for both EXPORT / Domestic,
how to do it .
Other things is while posting for the excise in SEZ case i am getting error===
ERROR in allocating excise invoice number interval not found number objetc J_1IEXCEXP.
plz guide itDear Rishi
Check my suggestion in this thread
[excise invoice and domestic invoice sharing same number range |Re: excise invoice and domestic invoice sharing same number range]
thanks
G. Lakshmipathi -
Hi Friends ,
I have done all settings for Supplier Registration Process. I am able to transfer the supplier from pre selection screen and all the relevant information is coming in supplier screen, when i am clicking on SAVE button, I am getting following error messages.
1. Number not in interval 0000100001 u2013 1999999999
2. Business partner 162 already exists
In supplier screen partner number shows 162 which is in between Internal Number range assignment while at the time of SAVE system comparing with External Number Range assignment why? When I am changing partner number 162 with External Number range Number for example 100009 then only I am able to create Bidder else it is getting error. Should I have to change Number range assignment or Am I missing any steps?.
I have assigned following entries in Tx. BUCF in SRM.
01 0000000001 0000100000 170
AB 0000100001 1999999999 0 X (Ext)
MD 9000000000 9999999999 0 X (Ext)
Entries defined in SRM Server - Technical Basic Settings - Settings for Supplier Synchronization - Define Global Settings
Vendor Number Assignment Type u2013 Assign SAP-ERP Numbers Only
AbhijeetDear Nitesh,
What is the exact error message that you are getting?
Regards,
Naveen.
Maybe you are looking for
-
Can SAP run the depreciation for closed Period and posting to diff month?
My client forgot to run the depreciation for Jan 2011, and now the Jan period has been closed and report also done. My solution was to re-open the Jan and does the depreciation, once completed reclassify Jan depreciation posting to Feb 2011 manually.
-
Formatting a document in non-book layout
How can I go about formatting a document so that the pages are in (say) a 4x3 grid, or whatever, instead of a typical facing or non-facing book format? Thanks!
-
Passing data values to all the view without inbound plugin
Hi Experts , I am in a complex situation. Scenario is as below. I have 4 views say A, B, C, D when user click Continue on view A he goes on B and so on... Most of the Context created are in COMPONENT CONTROLLER and is being used in Views . This is al
-
charging the battery of my iphone 4s nothing lasts, why?
-
Microsoft Virutal Machine is Virtual Trash
I installed the Hotfix for the MS Virtual Machine and I can no longer Customize my Internet Security settings to a lower level. I adjust the settings and they revert back to a medium level, thus preventing operation of certain database access across