Logincal Corruption, Customization Error or Am I Clueless

eparty

Hi Everyone,

Today I identified a document/s that have been used on different days accross different customers. For one of the customers it is listed as an invoice while for the other it is a credit memo.

So the way I interpret this is that the system allows the reuse of document numbers accross customers and accross different document types. Am I correct in thinking that this is logical corruption and customization error?
Your input on this is greatly appreciated!

David_Cox

Not at all,
You could if you wanted set the same number series for all documents, it is the Customers choice, but would not make good practice, the sample data is really poor, as the Blanket Orders start with the same number 1001, the Customer will use thier own numbers, often prefixed with Alpha characters or continuing on from thier old system, you will see in the demo data on navigate, the number has been used more than once, so there is a warning.

So if you want Invoices and Credit Memos to use the same range of numbers it will let you, but systems are setup by logical thinking people and this is not often an issue, that is unless the system is setup by a developer and is just the default data with the ledgers deleted.


David (Analyst Developer)

eparty

Hi David - yes, I do get a warning that the document has been used twice when I search for it. Maybe my initial post is not very clear, here is what the documents look like:

Posting Date Document Date Document Type Document No. Sales (LCY) Customer No.
1/30/2006 1/30/2006 Invoice B3-00000056 1,790.57 2222
7/11/2005 7/11/2005 Credit Memo B3-00000056 -227.21 11111

But I guess what you are trying to say that as long as the documents are from different number series, even if the numbers are the same, this should not be a problem.
Many thanks!

David_Cox

No if you post duplicate numbers from different "No. Series" it will let you, but you will get the message.

I could have a Invoice and Credit Memo both with B3-00000056 if I setup the two series the same, but why would I?

I would Identify different posted documents by a prefix to stop this.

SINV00001 SCR00001 etc:

David

eparty

Thanks David! Now it is crystal clear. Yeah, why should it be easy and have a different prefix for the different types of documents. Lets use the same document number for confusion