ERROR IN ASSIGNMENT OF DOCUMENT NUMBER

Dear all,
While making a MIRO transaction my user is getting the subject error. Can you guide me exactly how to rectify this error.
Message # 8i130
Regards,
Sudish
SAP Helpdesk

Message class 8I is related to Excise as well as TDS...so please check any number range missing wrt TDS
Go to configuration for Logistic invoice verification and check for Number range interval asssignment for document type RE- Invoice Verification.
Check whether , Have you maintained TDS in header field of invoice?
Thanks,
Vishal

Similar Messages

Error while detrmining Internal Document Number for Excise Invoice.

Hello mate, I am trying to create excise invoice for for factory sale. while saving the document I am getting an error" Error
while detrmining Internal Document Number for Excise Invoice. Message: Maintain Number Range for J_1IINTNUM". I have already maintained number range for mentioned object "J_1INTNUM" in TCODE SNUM , still getting error. Please solve my querry . Is it related to transport or number range activation or something else? I have maintained number range with serial no. "01"

Hello ,
Ensure that number ranges are properly maintained in the respective client that should be the year specific.Some times even u maintained the system should not consider that number ranges due to table updation problem ,because i had faced the same in the earlier and received the reply from the sap stating that this error was occured rarely after the years,so please ignore that ,for your problem u first come out of the screen and then re log in and then create the excise invoice ,then check the number ranges .
Please revert for any
Kalyan

Error in allocating RG23D document number Interval not found Number object

Dear
Expert
Error in allocating RG23D document number Interval not found Number object J_1IRG23D
I tried the solution given in the forum but its not working,
Pls help me out.
Thanks and Regards
Deepankar

Hi,
As a know that this is a problem of number range and I mentioned the same(SNUM> given the object and maintain the number range of this fiscal year but it didnt work also searched in the forum but didnt got any other solution so posted the issue.
hope now its clear.
Thanks and regards
Deepankar

Error on Purchase Order - Document number 45* not within defined interval

Hi All,
PLEASE HELP ME or guide me in the right direction.
I am faced with a somewhat unique case in our enviroment. Some background first.
Back in 2000 when we upgraded from Walker to SAP, a number of Purchase orders had to be migrated, one of them is the order i am struggling with. Back then very little validations were built in, resulting in a Local Order being incorrectly created as a International Order but against a local currency.
Now this ordered is still being reflected as open in our system. When attempting to change the order by activating the 'Delivery Complete indicator", we get an error "use only foreign currency" This is due to the fact that validations against Document Type and Currency was created in 2003 and are in full operation now. It is hard coded thus i can not remove this easily.
Now when attempting to get around this by changing the Document Type to a Local Purchase order or trying to delete a line, we get the error below.
"Document number 45* not within defined interval"
Number ranges do come to mind based on the error description, however, Local Orders have a number range of 45, International Orders have a number range of 47. In this case, the order is created as a International Order BUT the number range is 45*, again, due to a lack of validations/incorrect config back in 2000
Do any of you know a possible solution to such a problem.
Regards,
Jody Ponnusami.

The validation of document type and currency is not standard, and if this validation cannot be deactivated, then you will have to resort to making changes in debug mode. Put a breakpoint at the relevant check and force it to accept the current combination.
The second option is to update EKPO table manually using SE16N. Set the delivery completed indicator to X.

IDOC error status 'Enter the Document Number'

Hi PI or SD masters,
I have a status 51 in my IDOC. The reason was 'Enter the Document Number'. Has anyone encountered this before?

Sold To Party Account number was changed

Error while cancelling a document number in MBST

Dear,
In MB03 the material is with 101 movement.
When i am performing MBST then i am receiving an error message
"Document Flow for delivery cannot be updated".
Message No. M7352.
Purchase Order is assigned to delivery. The current Transaction cannot update the document flow , because the system does not recognize the delivery number.
Plz provide me the details on how to proceed with this error as to cancel this document.
Thanks in advance.

Dear,
Its cancelled.
Used MB0A Enter Delivery Note, Movement Type (reversal of that you see in MB03) - 102, Plant, storage Location ,
& Under -- Find Po's for preceding document-- enter the Delivery Number that you will find from the PO history.
Thanks & Regards,
Vivek.

Error in assigning sales document type to sales area

Dear All,
I am trying to assing sales document type to sales area, but system is not allowing me to do that
I am having this error message
" First, maintain the sales area <1000/14/00> as a common sales area, and
then assign allowed sales document types. This means: Complete the IMG
activity Assign sales area to sales document types in the sequence
entered here."
Note:
I have never created a distribution channel "14" and division "00" then why system is asking me to define this as a common sales area.
How can I maintain common sales area ?

Dear Ali,
1.You go to VOR1 transaction here you check what is the distribution channel assigned as common distribution channel for your sales organisation and distribution channel ,if it is improper then maintain correct Distribution channel.
2.You go to VOR2 transaction here you check what is the division assigned as common division to your sales organisation and Divisionif ,it is improper then maintain correct Division.
3.You go to OVAO transaction here you assign reference sales organisation to your sales organisations.
4.You go to OVAM transaction here you assign reference distribution channel to your sales organisation and common distribution channel.
5.You go to OVAN transaction here you assign reference division to your sales organisation and common division.
6.Finally you assin sales document type to your referenced sales area.
I hope this will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Nov 11, 2008 5:58 AM

Document number assignment can be found in the critical area (MATNRUnknown)

Dear all,
Pls advice me to resolve mention error which is pertaining to msg no -vf205 in sap.
while creation of idoc associated document (article and billing) is not generating by our system. when ill see the error its showing "upper limit of number range is exceeded" but in spro in not exceeding.
kindly advice .
Regards
Sunil kr.savita

dear raju,
we dont want to increase upper limit coz document no generated by system is within the no. range limit .
but when we double click on this error its showing.
Document number assignment can be found in the critical area
    Message no. VF205
Diagnosis
    Document number assignment for the number range object RV_BELEG in
    number range 49 is found in the critical area.
Procedure
    You can either increase the upper limit of the number range interval o
    set the current status back. You must, however, make sure that infutur
    no number is entered more than once.
regards

Manual document number in User-Defined Object

Hi Experts,
I have a user-defined object of document type. I am trying to post a document using the General Service. However, I cannot assign manual document number. There is no handwritten property available. Is it possible to assign manual document number in user-defined objects using the DI API?
Thanks.
Melvin

Hi,
This issue has been resolved. For the benefit of those who will be encountering this error, it was resolved by manually assigning the Handwrtten field to 'Y'. Here is the code fragment:
shipmentHeader.SetProperty("Handwrtten", 'Y')';

Document Number ranges

Dear All,
Pls help me to solve the issue reg document number ranges.
We have defiend the document number ranged for two company codes. Now ths issue is.. this document number range is being used/shared by both the company codes. For ex.. Invoice 01, 02 and 03 is posted in the company code A and we have not posted any Invoice in the Company Code B. If we post the Invoice in the Company Code B, number for the Invoice will be 04. And the next invoice in the Company Code A will be 05. But i will required to change the configuration to split the document number ranges..
Pls help me to do so.
Thank you

Hi,
This thing is obvious if the document number is being shared by more than one company code then it will act the following way...
for example :- Company code "A" is assigned with document number 01 and if you raise an entry it will take the range from 01...like document number generated will be 0000001
Company code "B" assigned with the same document number range 01 the next entry will create the next available number that is ....0000002
This happens b'cz its being shared by both the company codes.
Hence you have to keep seperate document number range for both the company code to avoid this confusion.
Please assign points.
Zia.

Document number ranges in entry view and in General Ledger view

What is the difference between Document number ranges in entry view and in General Ledger view ?
We have new GL activated in our system , and found that the GL Document types ( SA) are assigned to document number ranges in entry view . What is the need to define document number ranges in General Ledger view ?

Hi,
Document Number Range in entry view is the document numbers which are posting in your leading ledger. You cant achieve the same document number range to the general ledger view. A General ledger view can have both Leading ledger view and non leading ledger view therefore document number range should not be kept same for both ledgers as your running document number gets skipped.
That to some times you can only post documents to only Non Leading ledgers. Therefore a separate number ranges needs to be created for general ledger view
Hope u understood.
regards
srikanth
Edited by: boddupalli srikanth on May 21, 2009 9:28 PM

AR AUTOINVOICE ignores the checked box "copy document number to transaction

dear ,
AR AUTOINVOICE ignores the checked box "copy document number to transaction number"
I setup the batch source as check "copy document number to transaction number" but when
I import the invoice by auto invoice I found the transaction number is 2 and
the document number is 1
That mean the system ignore the check box in definition of batch "copy document number to transaction number"
Facts: Navigate -> Setup -> Transactions -> Sources
Setup Transaction Source with Automatic Transaction Numbering checked and Copy Document Sequence Number to
Transaction Number checked.
Navigate - > setup -> system option  tab (transaction & customer)
Document number generation level: when completed
Expected Behavior:
The Expected Behavior is that when I checked the "copy document number to transaction number" in definition of the source
AR Auto Invoicing must assign the document number to transaction number
Business impacts :
There is gaps with the sequence number for the invoice that not accepted from the finance auditor in the last of the year
thanks

check have u performed these steps or not.
you have to do all the necesarry set up steps:
1) Enable the Sequential Numbering Profile Option
2) Enable the AR: Document Number Generation Level Profile Option
3) Check Copy Document Number to Transaction Number box on Transaction Sources
4) Define Sequences
5) Assign Sequences to Categories
In batch source definition for your invoice, there is a flag for 'copy doc num to trx num'. is it ticked?

Material Document Number is missing

Hi experts,
I am creating material documents. First document created number a 100 then second document created 101 and then third document created with 103 number.
My client is asking where is 102 documents.
plz tell whatu2019s the problem.
Thanks & Regards,
Chandhu

Based on my knowledge, let me say what happens in principle when you create a document in SAP.
SAP collects and check all the data and then assigns a document number. Then it sends instructions to the database to update appropriate tables. If the tables cannot be updated for any reason, then the update fails. Note that since the document number is already assigned, the next time you create any such document, the next number is used.
Do you have any custom code that creates material documents? Sometimes incorrect coding can cause update terminations.
If not, then do not worry about standard SAP document numbering process.
Just ensure that all your business transactions are in sync and that this 102 document that is missing is not referenced by other documents. If it was a document that existed earlier in the system and has now disappeared, then it is cause for concern.

Purchase Order Modification: External Document Number already assigned

Hello,
We're running Extended Classic Scenario in a SRM 4.0 implementation.
The problem is the following: When the user modifies a purchase order (this purchase order is already replicated to the backend), sometimes (not always), the next error occurs:
"Purchase Order XXXXXXXXXX: PO header data still faulty "
"Purchase Order XXXXXXXXXX: External document number XXXXXXXXX already assigned"
The system does not provide additional info (RZ20 give us the same message, no ST22 dumps...
We think it could be some kind of error in the standard BAPI BAPI_PO_CHANGE.
We've revised the SAP OSS but didn´t find anything....
Some idea?
Regards and Thanks in advance!!!

Hi
Any other rrors / dumps noticved in system using RZ20 and ST22 transactions ?
Have you seen this helpful pointers and link ?
The related SAP OSS notes are as under :
"Purchase Order item 00010 still contains faulty account assignment items"
Note 1000184 - Account assignment error when document transfer to back end
Note 966323 - Service Item: Not able to create PO in ERP backend
"Purchase Order item 00010 still contains faulty account assignment items"
Re: How to create a PO in R/3 from a local Bid Invitation in classic scenario ?
Re: From local Bid invitation PO is not generated in backend
Do let me know.
Regards
- Atul

Document number 1700000000 has already been assigned

Dear all
I create a credit memos but when I post I receive message "Document number 1700000000 in company code HDQC and fiscal year 2008 has already been assigned"
I checked in IMG define number range but I don't know where to assign number range to document type
Anyone tell me why I meet this error and how to fix it
Thank in advance
Minh

Use Transaction code OBA7 to go to Change view Document Types.
Select and double click on Relevant Document Type
Assign Number Range
You can also view number range information from this screen to check number ranges.

ERROR IN ASSIGNMENT OF DOCUMENT NUMBER

Similar Messages

Maybe you are looking for