Local Scenario: Invoice 'Error in Process'

Question

Hi
We are implementing SRM5.0. Some product cat are defined as Extended Classic via a BADI whereas Local scenario has been defined for the rest.
There is no problem with the extended classic process. When we create an invoice for a local product (which is not in r/3), the status of the invoice becomes 'Error in Process'. In EBP, trans we02 shows that the IDOC of the invoice has been processed successfully but when we do we02 in r/3, there is an error in the particular IDOC.
The error message states that 'Incorrect doc.no.: $ 1 . Select document number between 5200000000 and 5299999999'
Is there some additional setting required for this local scenario. The same thing works perfectly when we select a backend product.
Also, I am wondering why the info like product, product cat passed to r/3 in the invoice IDOC when the source and target sys of this prod cat has been defined as local SRM system.
Please help us in solving this issue.
Warm regards
Ajay

Answer 1

Hey Keith
Thanks for the response!
I'll list the doc types and the number ranges in our system and then maybe you can point out is there is some error;
SRM:
For Local invoices:
Internal number range: 01  [1000000001 to 1599999999]
External number range: 02 [2000000000 to 2000000020]
In R/3:
Under Logistics Inv Verfication --->
In 'Maintain Num Ranges for acct documents':
For Document Type RE --->
Number Range: 52 [5200000000 to 5299999999] external
In 'Maintain Num Ranges for logistics documents':
For Trans type RD and RS:
Number Range: 52 [5200000000 to 5299999999] internal
I guess, in ext classic scenario, invoice log docs are also created....so it assigns a number from 52 internal number range and the same number is passed on to FI and thats why 52 is the external number range above.
But in Local scenario, it expects just the FI doc and hence expects a number in the 52 number range to be provided from SRM.
So, I modified the internal number range in SRM to 52 series. Now, the invoice is getting created in SRM in the 52 series but still I am getting the same error.
Seems wierd, but I am sure we would be missing some link and thats why it is not working as expected.
Warm regards
Ajay