Extend GL number intravel for an number range

Hi All,
I have question like, one GL number intravel of one number ranges are over and my client want to extend the number intravel with out creating another Document Type. can any one please tell me is ther any process to extend the same number intravel for the same number range.
Thanku

Hi,
Is your requirement is to extend the number range of a particular document? If the number is permiting it can be extended, however if it is overlapping with another range it cannot be extended. Also you need to look into the fact whether your number ranges are year dependant ot continuous.
Thanks
Murali.

Similar Messages

Number range in Material Master for document number

Dear All,
I have an issue in that i have specified a number range (ex:5000000000-5111111111) for the year 2010.
If the number range finishes before the end of that year and i want to create a new number range. Is that possible
and how should i do that.
thanks ,
Vidhya

you can not create new number range but can extend the number range
number range (ex:5000000000-5111111111) for the year 2010.
number range (ex:5000000000-5911111111) for the year 2010.
tcode OMBT
hope this helps

Billing number Range to be extended?

hii
experts
i have an error during running the biling j1iin for excise . During the time of saving the error giving is number range is finished .plz help me out how to extend the number range
thanx in advance

hi,
hope this helps.
1. T Code SNRO
2. Select object relevant for billing
3. in that object select the number range you were using
4. If the number range is frequently used and same number range has to be extended then extend the number range by a substantial amount.
e.g - if its a regular invoice then increase by a lakh .
5. Make sure that the number range is not used anywhere in this object.
6. Good prcatice is to already allot a number range for this with a diffrent name so that it can be used later.
thanks
swapnil

T code KANK - Number Range for CO

Dear experts,
When I create CO number range(T code KANK) for a controlling area and do a posting, system takes last document number and therefore I can only post one document at a time.
Example: When I creat number range 1 to 100 and try to do FI posting with a CO object, system will take number 100 as the first document and hence I have to extend the number range again and again. It is ignoring the number range 1 to 99.
I get the message as 'Number interval for transaction COIN in CO area 2000 is exhausted'
Any solution to this problem?
Thank you.
Regards
Paul
Edited by: Paul01 on Dec 12, 2010 8:12 PM

Hi,
Check this post as well. You may find it useful
CO Document Number range issue
Since you gave CO number range from 1 to 100 and the buffer in SNRO for object RK_BELEG is 100, you are not able to create any additional CO documents.
One solution is to make sure you give sufficient number range intervals in KANK in order to avoid this.
Thanks
Ram

SALES ORDER INTERNAL NUMBER RANGE

Hi friends,
I have a problem with Sales Order Number Range with Doc Type SO(Standard Order) its about internal number range OBJECT ASSIGNED in document type is 01
In VN01 for object 01 range assigned is from 01 to 999999 & current number range is 976832 which is about to finish ,
Help me in this regards what r the steps involved in this as while saving order its already showing a warning error that number range is about to finish your earlier help will be appreciated & rewarded.
Regards

System will not allow overlaping of number range. As the number range is nearing to end of redefined, followinwing are the options:
Option 1:
Set number range for number range object 01 is 01 to 999999 . Check if the number range starting from 1000000 is free or already being used. If it is free & that number range is not being used else where, you can reduce the number range in it say number range object 02 is assigned number range from 1000000 to 1999999, you amend the number range to 1500000 to 1999999 & extend the number range fornumber range object 01 as 01 to 1499999.
Option 2:
If the following number range is in use, go to VOV8 --> select the Sales Document Type SO --> change number range object say 01 to say A1 & transport the same from Development to Test (QA) & then to Production Server. In the next step step maintain new number range (not overlaping) to say A1, number range being 10000000 to 19999999. The imapct of transporting the reauest of VOV8 transaction will be that you will have to maintain the new number range immediately & from very next Sales order, the new number range will be active.
Hope this is useful input for you.
Regards,
Rajesh Banka
Reward point if helpful.

Message no. 8I766 Number Ranges are not maintained For Extended Withholding

Dear All,
I am facing the following problem when i am trying to generate the withholding tax certificate
1.) Message no. 8I766 Number Ranges are not maintained For Extended Withholding Tax
     Number Ranges are not maintained for Business Place and Section. Check entries in tables J_1iewt_cert (for Business Place) or J_1iewt_cert_n (for Section Code) and j_1iewt_certno in EWT.
I have checked all the above tables and found that the entries are maintained
2) When i am trying for print priview and then print its generating spool request and the certificate is getting saved -
> here the following problems are faced
      A) . TDS Number is not coming
      B).Details Of the tax deductor ( Name , Adress , TDS Circle , TAN & PAN is not coming Where       to update these details
      C) In Amount Paid / Credited Column - Some fixed amount is comming irrespective of the actual amount credited
Please help me in soving the above issues
Thanks & Regards
Arun.R

Hi
You need to maintain Section Code wise number range . Go to Sm30 Select Table J_1IEWT_CERT_N and maintain it.
Thanks
GG

Number range for extended classic scenario

Hi,
we've activated extended classic scenario for some defined categories (material groups), other will use classic scenario as before. It works, we are able to craete POs in both ways. I've tried to use the same number range for backend POs and for local POs. I've set the same number for both ranges but only the one which is used is getting updated. Is it possible to syncronize these ranges so backend POs will all be created in the same range?
Regards
Hubert

Hi Hubert,
Not the best practice that you are following. it might work for some time but will fail for most of the time . The maintenance is going to be huge and you could expect problem with these.
I would suggest not to think on the solution of same number range itself.
Thanks
Iftekhar Alam

Anybody ever created multple PO doc type/number ranges in extended classic?

I have searched this forum, and found plenty of useful threads which would help me determine different document types/number ranges for back-end purchase orders in a classic scenario. (And I have done something similar many years ago on a classic EBP 3.0 implementation)
However, I have a customer who has an SRM 5 extended classic implementation, and who (Based on certain simple criteria) requires a different PO number range to identify certain types of indirect orders. (They also have direct materials procured using doc type ECDP, but that's not relevant to this requirement)
This would obviously have to apply to the local PO in SRM, as well as the backend ECC PO.
It would also need to be derived for orders created automatically via approved shopping carts, as well as those orders that are created via sourcing.
I've copied ECPO via define transaction types IMG step, as well as assigned a new number range.
Just to test, I've also added the second doc type in the BSA attribute for a particular test user - just initially see if it was possible to manually choose when creating a PO in sourcing. However, I could only get ECDP and ECPO.
I have looked at various BADIs to see if I can determine doc type or number range somewhere in the PO creation, but as far as I can see, they either:
- Seem to apply only to the object type (PO, requisition, reservation etc) rather than the transaction type within that object.
- Or look like they are too late in the process to influence the doc type and number range (BBP_DOC_CHANGE_BADI?) ... which doesn't seem to have those doc type or PO number fields available anyway
- Or I doesn't seem to be trigerred at all when turning requirement into Po and ordering via sourcing. (tried break-point & endless loop in implemnetation of BBP_CREATE_BE_PO_NEW, but nothing happened. In any case the PO number was alreadya ssigned)
If anybody has ever managed this before, or can tell me that I am definitely barking up the wrong tree, it would be gratefully appreciated. The document type is actually lesss important than the different number range... and was really just an attempt to trigger a different number. I'm starting to think that this sort of thing may only be possible in a classic implemntation.
What I need ideally, would have been some kind of 'local PO' equivelent of the BADI that enables you to determine transaction type for a bid.
Regards,
Vince
Edited by: Vincent White on Dec 6, 2010 5:13 PM

Hi. Not sure on this, but I can tell you that with extended classic it is BADI BBP_ECS_PO_OUT_BADI that is called for the backend PO instead of the CREATEPO_BACK BADI.
You can have a look in BBP_ECS_PO_OUT_BADI and see if that helps?
Don't think it will influence the PO in SRM at all though.
Have you tried the number range / grouping BADIs? They definitly work for changing the number range for classic POs.
Regards,
Dave.

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

Copy of Internal Number Range of extended withholding tax

hi,
Can any one tell me the transaction code for copy of the Internal Number Range for extended withholding tax from one year to another year
points will be assigned
thanks in advance

hi,
use t.code:J1INUMBER
all the best
Prasad

Modify Number Range for Purchase Order

Hi All,
We have created a new transaction type 'ECPO' for Shopping carts in SRM.We have
given it a new number range. While creating a shopping cart and based upon a
condition how do i ensure that my shopping carts get created with this
transaction type? Is there any attribute which controls this ?
I tried changing the attribute BE_DOC_TYPE = 'ECPO' when the condition is met
in DOC_CHANGE_BADI for shopping cart, but it didn't create the PO with the
new number range.
We are using Extended classic scenario and so the purchase order is created in
the SRM system and not at the backend.
Please do let me know if there is any way to achieve this.
Points will be updated for valuable solutions.
Thanks in Advance,
Raj
Edited by: Prasanna Ram on Oct 13, 2008 10:27 PM

Prasanna,
Did you assigned the attribute called BSA (Transaction type for shopping cart and Follow-on documents) in the org structure? Herewith you need to define the backnend and the transaction type (eg: PRDCLNT500\ECPO).
Please note that same transtion type should available in the backend system too..
Kind Regards,
NMK

Extended Classic - Purchase Order Number Ranges

We are using Extended Classic EBP. When a PO is created in SRM the PO replicated into R/3 does not have the same number.
The backend PO document type is ECPO. We have assigned an internal and external number range to this document type.
When an SRM PO is replicated to the backend, the backend PO number is taken from the internal number range for the document type. This internal number range does not include the number range of the SRM POs.
We expect the SRM PO number to be pushed into R/3 and therefore the external number range of the R/3 document type should match the SRM PO number range.

Hi
No need to maintain the internal number range for the SRM PO document type ECPO in R3 (maintain the external number range code of SRM PO transaction type).
As the PO is created in SRM, and the number range you maintained in SRM and R3 should be same, but in SRM it will be internal number range and in R3 it should be external number range. (number range code should be same in both the systems).
Regards
Reddy

Error in J1INCHLN for internal number range

Dear Experts,
I am getting the below error when I am executing J1INCHLN. I checked J1INUMBER but of no use. Number range for 2008 is maintained. I am not able to maintain number range for 2009. Kindly guide.
Number range for internal challan numbers not maintained
Message no. 8I706
Diagnosis
Number range object 'J_1ICHLNNO' is not maintained fully.
System response
There is an error in the number range object and a new internal number can not be generated.
Procedure
Check if the number range object exists in your system and also check if number ranges for the number group is maintained for the current year. Maintain the number range object and then start this transaction. The transaction code for the number range maintenance is 'J1INUMBER'.
Regards
Komal

Hi
Go to SPRO>IMG>Financial Accounting (New)>Financial Accounting Global Settings (New)>Withholding Tax>Extended Withholding Tax>Posting>India>Remittance Challans>Maintain Number Groups
here define - cocode , section , tds section code , number group
now go
SPRO>IMG>Financial Accounting (New)>Financial Accounting Global Settings (New)>Withholding Tax>Extended Withholding Tax>Posting>India>Remittance Challans>Assign Number Ranges to Number Groups
here assign number group to Number range
now create number range go to SPRO>IMG>Financial Accounting (New)>Financial Accounting Global Settings (New)>Withholding Tax>Extended Withholding Tax>Posting>India>Remittance Challans> Maintain Number Ranges
here create a number range on year base
**some time you have to update the table so go SM30 and update J_1IEWTNUM , J_1IEWTNUMGR and J_1IEWTNUMGR_1 tables
Best Of Luck
Tanmoy

For object RF_BELEG number range does not exist

Hi,
while doing PGI, i get an error For Object RF_BELEG ,number range does not exist in company code ABCD. Where do i create the number range for this. I tried with FBN1 but not useful.
" Diagnosis says, the database table NRIV has the delivery class as C. Make chages in customizing. "
what could be the reason for this error? can anyone help me to fix this error.
i tried to fix it through transaction code 'SNRO' and 'OBA7' but in vain
can anyone help me out

Try Extending the same in VN01 , and assigning it to your relevant document
Cheers

For sweden the employee number range is completed Eg:23000000 to 239999999 now how to generate next employee id

For sweden the employee number range is completed Eg:23000000 to 239999999 now how to generate next employee id

Hi Bharathi,
If required no ranges are not there which you want to add then will not be problem and you can extend the 23999999 to your next limit like 39999999 check the overlapping.
Check extended no rage are present in the system and then system would not except because of overlapping.
Check and tell.
Regards,
Sankarsan

Extend GL number intravel for an number range

Similar Messages

Maybe you are looking for