DI: Automatic selection batch numbers for the stock transfer

[Former Member]

Hello!

An user creates a stock transfer in the system. It is monotonously for him to select batch numbers for all items in the document. I need to select batch numbers automatically using SDK. The problem is that this stock transfer is not added to the database, therefore I have no access to the SDK DI StockTransfer Object and its child objects.

Is it possible to add batch numbers for a stock transfer that is not added to the database else?

I know the problem when using batch numbers exists. Does It mean that I have to use my own connection to the

database and use sql queries to select batch numbers?

Thanks.

WBR, Anatoly

[Former Member]

Hi,

Does anyone knows the purpose for the table OSRD?

I have to use the same SQL solution to use Batch Numbers but the table OSRD it appears to hold the items that were introduced in the warehouse but without a batch number.

But it appears to hold more information.

Does anyone knows the purpose of this table?

Kind regards,

L. Iván Juárez

[Former Member]

Hi Luis

The purpose of OSRD is:

You have a batched item called BatchedItem.

Now you buy 100kg of BatchedItem. You create a "Goods Receipt PO" document - but you DON'T (because of any reason, doesn't matter) fix Batch Number(s) for these 100kg of BatchedItem. So, SBO knows that 100kg of BatchedItem are on stock, but SBO doesn't know any BatchNumbers for these 100kg; there CAN'T be any entries in the Batch Tables OIBT and IBT1 because there AREN'T Batches for these 100kg of BatchedItem, nevertheless there ARE 100kg of BatchedItem on stock.

OSRD is keeping in mind this state. OSRD tells you: "There are 100kg of BatchedItems on stock WITHOUT BATCHNUMBERS."

That's the goods receipt part of the problem. OSRD handles the goods sales part of the problem too. It tells you which quantities of which batched items you have sold WITHOUT DESTINATING BATCHNUMBERS for the sold quantities.

[Former Member]

Hi Anatoly

We had the same problem as you - and we have solved it. But it was a lot of work and it isn't a beautiful solution at all, because:

- There is no batch object at all in UI, that means: you can't perform any batch action while a business document is open (= while the business object's data are not contents of the database)

- There is no useful batch object in DI, that means: you have to perform every batch action by means of SQL. I have mentioned the tables you will have to work on in my answer to Kurt Huwiler's question.

[Former Member]

Thanks for the reply.

I think using of SQL is the best solution of this problem.

WBR, Anatoly.