External document number already assign

Hi,
I am running Extended Classic Scenario.
In my Application Monitors under Purchase Order : Backend application errors
I once in a while get an error like this:
"PurchOrder 3000002452: PO header data still faulty "
"Purchase order 3000002452: External document number 3000002452 already assign ed"
As far as I can see the PO is fully copied into R/3 and if there is made a chage to the PO, it is also replicated in R/3
Does anyone have an idea why I am experiencing this error?

Hi
Which SRM and R/3 versions are you using ?
Please give complete Error message details using RZ20 Transaction ?
Any other dumps noticed in R/3 or SRM System, using ST22 Transaction ? If yes, give details.
Meanwhile, please look at the following SAP OSS Notes ->
Note 990946 - BBPSC01: Accounting error during PO creation
Note 815849 - FAQ: Account assignment system response
Do let me know.
Regards
- Atul

Similar Messages

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

External Document Number assignment using Bapi_acc_document_post

Hi All Experts and Max,
We want to post th same external document no using BAPI_ACC_document_post, but we are unable to post thatexternal Document no.
Note: If we are posting the same no using transaction FB01 , we are able to post the document , if we are passing the Acc_do_no field as the external Document no.
Our requirement is to post the document no of the e.g A system to B system with th esame document No .
Kindly provide what value we need to pass in the obj_type , obj_key and obj_sys fields of BAPI_ACC_Document_post.
I am aware about the scenario that in case of internal document no creation we will get all these 3 fields from th eBAPI, but we need the values in case of external document no assignment.
We tried with obj_type as 'BKPFF' but we are not able to post the document with that obj_type, In that case Bapi is clearing the exterbal document no acc_doc_no field in the first subroutine.
Note: We are uploading a file in different system with the .dat format and we are using BAPI_ACC_DOCUMENT_POST method.
Please refer the below link for more issue details.
Link:[External Document Number assignment using Bapi_acc_document_post;
Kindly provide the solution.
Thanks,
Rahul Sisodia

Hi All,
Please suggest if you came across such situation. <removed by moderator>
Thanks,
Rahul Sisodia
Edited by: Thomas Zloch on Sep 19, 2011 10:18 PM

"Receipt Number Already Assigned" error message in F-28 screen

Hi
When posting Incoming Payment using T Code: F-28, we got "Receipt Number Already Assigned" error message. Can any one hanve any idea why system has shown this error message?
Thanks & Regards,
Chandra

do you enter a payment advice number or document number?
Seems like you want to enter a number that has been already entered before, so system does not accept to have same entry.
Check your entry, if corect check old one. Or add something to the number to make it unique.
Regards
Hein

SD (External document number of vendor confirmation)

Hi Friends,
Below are my report output fields.
Orer entry date     Sales Order     Sales Org            Shipping quantity   External
(VBAP-ERDAT) (VBAP-VBELN) (VBAK- VKORG) (LIPS-LFIMG)        doc no
                                                                                (EKES-XBLNR)
Could any of you please give me the details abt
"How to fetch XBLNR from EKES based on sales doc no .
Regards.
Jeyaseelan

Thanks Karan.
Its an existing report.
Its (Proactive Late Report)
in the current code they are fetching all the data from the tables VBAP VABK VBUP VBEP VBPA.
now i need to add 3 more fields.
delivery date.
shipping quantity (lips-lfimg)
External document number (ekes-xblnr)
Jeyaseelan

External Document Number Range

Dear Forum,
We have an issue with the Document Number Range that has been defined in the system, according to which the document numbering is automatic. When the users post the entries for audit adjustments in the back date, the numbers jump, which becomes an audit issue. However, to resolve this the users want the externally controlled document number range, so that they have the option to chose the manual numbers. Another problem is that we are using the ledgers 0L as well as 1L, while the entries are posted in the leading ledger 0L, the same get replicated in the non leading ledger 1L and we want the external document number range in the non leading ledger 1L also.
Your prompt help would be highly appreciated as to how can we resolve the same.
Regards

Hi Dianne,
Your advice is quite helpful. I have one more confusion. The fiscal year for the leading ledger 0L is calender year and for the non leading ledger 1L is the year from April to March. Thus period 03 for 0L corresponds to period 12 of 1L. Therefore, to keep the 'external document numbers' same in 0L and 1L, would the following be corect way, say for year 2010 -
0L Year 2010 (Calender Year Jan to Dec) - External Doc nos. From 01 to 1000
1L Year 2009 (April'09 to Mar'10) - External Document nos. From 01 to 1000
Thus if the audit adjustmnets are posted on 31 March, 2010 with document no with 001 in 0L, it would appear with same document no. 001 in 1L on 31 March, 2010. In ledger 0L it will be in period 3, but in ledger 1L it will be in period 12.
Would really appreciate your help.
Regards,

MIRO- Document number already exists on Subsequent Debit/Credit for 3rd pty

We have problem in invoicing a third party Purchase order, we get the message as " Document -<SD invoice> already assigned".
Error: F5152
Our Flow is: SO created-- PO Created--MIGO MIRO VF01.
Now the Vendor sends a Debit/Credit for the same PO.
While posting a vendor invoice in MIRO for subsequent Dr/Cr, the system(FI_DOCUMENT_NUMBER_CHECK) checks the number range of already invoiced SD document# and we get the error message " Document -<SD invoice> already assigned".
I checked the other question posted for this but did not see the solution.
Nimit

Please dont cross post in different forums per forum rules.
As mentioned in the other forum check OSS Note 414742 - Error F5 512 during the billing document update.
Regards,

Problem substituting document number into Assignment field

We have a requirement to substitute document number and fiscal year into Assignment field when posted to a Sp.GL account (Using FB60). Sort key is substituting doc# and fiscal year into Sp.GL Assignment number. I am trying to use a substitution rule, but it's not working probably because the substitution is being called before document number is generated. Any thoughts or input on this is greatly appreciated.
Thanks
Edited by: Chandra Nallam on Jan 29, 2009 3:13 AM

hi!! guys ,
Can anybody help me on this BB module of Vistex pl.
I have one very basic Questions and not getitng the right answer.
Look at this Business scenario
1) I have created Billback from Agreement and Invoice and I did accrued this BB like this there are various invocies I accrued thro various agreement and BB combination - I dont see any issues in Config here
2) now we have got Claim request from the Customer (for the same Partners) now how do I validate what is demanded by customer is same or less or more then the accrual happened thro the BB of Invoice??
So the issue here is mainly reconciliation of what accrued agains invoice need to be validated here in Claim document so I can take decision.
so Is this Billback module has got a possibility of reconciling in vistex ???
Let me know If you or any of your friennd can help me to understand this.
As you rightly said the document provided by Vistex are really Bad and not much helpful. looking at this i dont see this Product has really helped us much.
regards,
Himanshu

Sort key- Sales document number in assignment field-

Hi,
Please clarify how sales document number flows in to revenue line item when we release billing document to a/c in VF01/VF02.
We maintained sort key042(sales order)- FS00 for G/L account .
But data flowing to few documents only. What is reason?
Thanks
Chidambaram

Hi
In order to get the value you require in BSEG-ZUONR you need to populate field vbrk-zuonr in the userexit (RV60AFZC:
USEREXIT_FILL_VBRK_VBRP)
In FI documents which are created from SD billing documents the assignment number in the customer line item of the FI document   (BSEG-ZUONR) is filled with the assignment number in the header of the billing document in FORM ACCOUNTING_HEAD_LINE of function module RV_ACCOUNTING_DOCUMENT_CREATE:
FORM ACCOUNTING_HEAD_LINE. (LV60BF00)
XACCIT-ZUONR = VBRK-ZUONR.
Kind Regards
davide

Incorrect document number range assigned to Credit Memo in FB65

In our SAP system, a Credit memo's document number always starts with 17 and invoice's document number always start from 19. Our user has somehow parked a credit memo in SAP system with doc# starting with 19.... while recording through FB65.
Document type and double entry of the parked documen is correct, i.e, KG...
Please advise...

goto SNUM and seletc the object BELEG and seletc the number range 1000 to 2000n make the number bufferning by 10 there..
you will get your soloution..
Reward if it helps
Ramki

Post depreciation with external number range assignement

HI
When i am running Depreciation run AFAB, i am getting error"created doucment number range with internal assignement.
Currently the number range assigned for documents is external.
Why this error is coming... please provide solution without changing number range to internal..
Thanks and regards
Ramarao.p

HI
see the SAP document .....
Specify Document Type for Posting of Depreciation
In this processing step you determine the document type for each company code for posting depreciation.
Standard settings
SAP supplies document type AF for depreciation posting.
Requirements
You must have defined the document number ranges.
Activities
1. Check the standard document type AF. If needed, define your own document type.
2. Specify the document type for depreciation posting. The document type you select must meet the following conditions:
It must be a document type for batch input.
It must be defined with external document number assignment
So please provide the solution ...with out changing internal number range...
Thanks and regards
Ramarao.p

Invoice & Accounting Document Number

Dear Experts,
We are facing number range problem. When we are saveing an invoice then Invoice number and accounting document number showing different. It should come same number. Can you pls advice why this is happening and how I can resolve this issue.
Thanks in advance for your kind support.
Best Regards.
Ripon Kumar Paul

Dear Ripon,
Please check the below which will help you achieve same document number:
SAP gives you customizing options to make both document numbers the same. The solution lies in the number range assignment of the MM and FI document. You need to configure the MM document number assignment as internal and external for the FI documents. (FI documents are set up with external-assigned numbering, while the MM document has internal, or system-generated, numbering.) In this case, the MM document number is passed on to the FI document, which means that the number of the FI document is identical to the MM document.
Because the document number assignment in MM is not company code-specific, in contrast to the FI document, you need to take the following points into consideration before using external document number assignments for FI documents. They have the following effects on your system:
Continuous number assignments for FI documents are not guaranteed, especially if you have more than one company code.
The document number ranges in MM and FI have to be the same for all company codes.
In Release 4.6C, you need to use internal number assignments for revaluation documents, invoice reduction documents, Evaluated Receipt Settlement (ERS) postings, or reversal documents. There are no restrictions as of SAP Enterprise 4.70.
Use a different number range assignment for FI invoice posting (FB60), because FI invoice postings usually use internal number range assignments and the postings originate in FI, not MM.
If you use document parking and the number range intervals are fiscal year-dependent, you cannot change the posting date of the document if the fiscal year is different to that determined for the previous posting date. In this case you have to delete the document and re-enter it. There are no restrictions for fiscal year-independent number ranges.
What do you do if you have already posted thousands of invoices in your system and the numbers are already different? In this case, you need to find unused number range intervals in MM and FI. Since most companies do not change the SAP standard delivered number ranges during the original implementation, number range interval 52 is usually available in MM and FI.
Now let's look at the detailed customizing steps. With the following customizing steps, you can align the MM and FI document numbers going forward only. No fix is available for invoices already posted in your system, since SAP does not allow the change of document numbers.
Step 1. Maintain FI document number range. Use transaction OMR4 and go to Number range for document types in FI. Select the company code for which you want to create the new number range interval and click on the change interval button. Insert a new document number range by clicking on the insert interval button on top of the screen. In this example, I created number range interval 52 with the document numbers 5200000000 u2013 5299999999. Don't forget to set the external number range check box (Ext).
Step 2. Assign FI number range to FI document types. The second step is to assign the number range created in step 1 to the FI document type for invoices. Again use transaction OMR4 and go to Document type. Double-click on the document type, which you are using for LIV invoices. In my example, I used the SAP standard document type RE. In the number range field, assign the new number range interval 52.
Thanks!!!
Murlidhar Khatri

Controlling document number (belnr) is reflecting in accounting document as

Hello
Controlling document number (belnr) is reflecting in accounting document as refrence feld(xblnr).
Fot this any configuration requied ..?
Please guide me on this
Thanks in advance.

Hi Joseph,
The change you noticed from 4.7 to ECC 6.0 is true
In the ECC 6.0 you have to maintain the AF document type in "Internal Document Type", where as in 4.7EE we have maintained the same in "External Document Type"
Assign point if found usefull
Regards
KM Naidu

Error in document number while posting the material

Dear experts
while posting the stock MB1C for the material the error is " incorrect doc number $ 1 .select doc number between 800000100 and 800000199.
how to correct this error. where to check this number ranges of document.
Thanks & Regards.
Erfan.

Hi
The document type, which is integrated for Material related posting is appears to be configured as "External Document Number Ranges". In the event of external number ranges, MM transaction tries to post same document number individually at MM system and propose same number in FI for Accounting Posting. If the proposed number is not within document number ranges, then you would expect this kind of errors.
What you need to do is:
1. See the document type, which is being posted and set correct number ranges as per MM transaction document type number ranges or
2. change MM transaction number rages in order to FI document number rages
Hope this helps

2 material document number having the same delivery number???

hi
is it possible to have 2 different material document numbers assigned to the same Outbound delivery number????
the situation is that one of the material document number was assigned to a particular delivery number say 'a' and deleted later on a particular date.
on the same date another material document number was created with the same delivery number 'a'.
is this possible to happen .(i.e functionally correct) ?????? bcoz i am getting such type of output in transaction "MIGO"...
PLZ HELP .POINTS WILL B AWARDED!!!

Hi,
Yes,it is possible.If you take example of partial delivery then say for example one delivery contains 10 items.Out of whixh I have delivered 4 yesterday and 6 today.This is done via creating transfer orders.Then two material documents will be created at time of PGI but they will refer to same delivery number.
Reward points if useful
Regards,
Amrish Purohit
Message was edited by:
AMRISH PUROHIT

External document number already assign

Similar Messages

Maybe you are looking for