BAPI_SALESORDER_CREATEFROMDAT2 don`t generate consecutive sales order

[Former Member]

Hi !!!

I have a problem with the bapi, BAPI_SALESORDER_CREATEFROMDAT2, with an example i show what are happening.

The bapi generate the next sales orders:

sales order

1 Material A,B

2 Material C,D

3 MAterial E,F

4 Material G,A

-

---

> MATERISL A,B ( Sales order 1 )

6 MATERIAL H,E

-

---

> MATERIAL C,D ( Sales order 2 )

8 MATERIAL G,I

jumnp the sales order: 5,7.

i Rewiew the sales order 5, 7 (sales order that not appear or don't generate in the bapis' result) in the va03, curiosly the sales order 5 there is in the sistem

with information the sales order 1, the sales order 7 appear with information de the sales order 2 and so forth with the others sales order that don't appear in

bapis' result.

Someone have any idea, what are happening

Message was edited by: Noemi Huerta

Message was edited by: Noemi Huerta

Message was edited by: Noemi Huerta

Message was edited by: Noemi Huerta

[Former Member]

This could be possible if the Number range object is buffered. The standard object RV_BELEG is not buffered. Must have been changed later.

To verify go to transaction

SNRO

from the menu select

Number Range Objects -> Overview.

Pick RV_BELEG from the List and double click on the line. Check if Buffering is allowed. (if not allowed, it should say "Number ranges not buffered at the bottom of the screen") If this is the case, your problem is different

If allowed, you will see "Main Memory Buffering" and a checkbox and "No. of numbers in buffer".

to reduce the gaps in the number range, either reduce the "No. of numbers in buffer" or deactivate it from the menu

Edit -> Set-up buffering -> No Bufffering.

Rishi

[Former Member]

Hi Rishi !!!!!

I verified in the transaction SNRO, AND the configuration is Ok.

The curiously is that the documents that don't generate consecutive appear in sap with data of

sales order that had created by the bapi before.

[Former Member]

Can you expand on that!

Check to see if there are any update terminations (transaction SM13) as this could also cause gaps in the number ranges.

Check to see if OSS note 424486 applies in your case.

Rishi

Message was edited by: Rishi Joseph (OSS Note)