Combining Sales Delivery Billing Data in one DSO

[Former Member]

Hi Experts ,

I have a requirement where I need to combine Sales , Delivery , Billing Data into one single consolidation DSO . At first level I will be using a staging DSO to pull the data from 2LIS_11_VAITM , 2LIS_11_VASCL , 2LIS_12_VCITM , 2LIS_13_VDITM . Please advice on how to design a consolidation DSO on top of all these 4 DSOs . The crucial part I beleive is going to be the Key Combination . 2LIS_11_VAITM , contains Sales Order No and Item as Key . 2LIS_12_VCITM , contains Delivery Order No and Item as Key . 2LIS_13_VDITM , contains Billing Order and Item as Key . I know there exists a relation between all these three flows through reference document number , but look up doesnt work as for single Sales Document No there exists multiple Deliveries and Billings and these different Deliveries are posted at different point of time . Also cannot use Multi Provider , as I need to do some calculations in the backend .

I have gone through many threads before posting this , but still no match to my requirement . Please help on this .

[former_member186399]

Hello,

Its not going to be  straight solution. Your calculation will work at Sales order / line item level not at any other level

My approach would be to go from Sales > Delivery > Billing. So no issues whether a sales order is still to be delivered or billed the model will support.

1) Sales Order, SOItem , Delivery &  Delivery item as key field in the DSO.

There is always one to one relation between delivery and billing.  So billing document can be as data field.

2)  Map  2LIS_11_VAITM , 2LIS_11_VASCL kpis to the data field in the DSO. For these fields there will not be any mapping from   2LIS_12_VCITM , 2LIS_13_VDITM.

3)  Map 2LIS_12_VCITM kpis to the data field in the DSO.

4)  In 2LIS_13_VDITM you will get the delivery document / item in the field  preceding document / item. So this makes things easy as in 13_vditm you have sales order, delivery & billing document.

Hope this gives you some idea

Regards

Gajesh

[former_member647563]

Hi Gajesh,

Thanks for the proposed solution. I was thinking as well to create a DSO with key delivery item, delivery number, order and order item initially. The problem is that with this key we will miss the information for the billing credit memos, debit memos and the cancellations. It is possible to get more than one billing document per delivery item (billing cancellation for example)

At the end maybe it will be a compromise solution as it is not that easy to cover everything.

If you have the order and delivery number in the key, how do you plan to control the delta records to the key. For example, if today order is created without delivery the key will contain:

order and order item and blank values for delivery. The next day delivery is coming and we will get at the end 2 rows in the key for one order. I think it is good to delete the old record in the key by appending recordmode D value.

Regards,

Marin

[former_member647563]

Hi,

Did you manage to combine the orders, deliveries and billings in one DSO? I also need to combine this data in one DSO and plan to have the following approach:

- create a DSO with key , order no, order item, delivery no, delivery item, billing doc, billing item.

- in the billings you can get the reference delivery no and item and order no and item. load first the billings to the target DSO

- it is possible to have deliveries without a subsequent billing document. Then we load the deliveries by checking the target DSO for those who were not updated from the billings load. The same approach for the orders (it is possible to have orders not yet delivered).

Delta management.

- if in the key we have a order and delivery number, which are have not been built and a billing document is coming for them - we check the target DSO for delete the previous record by appending the same row from the target DSO with record mode D. Then the new billing document will populate the reference order and delivery information. The same approach for the deliveries and orders. If a delivery document is coming check if the delivery, which refers to order is already there, if not append deletion record to the target DSO record.

I hope this helps.

[Former Member]

Hi Marin ,

I am keen to know the approach. Can you please share in detail please/.

@ Vignesh, you require  item level also in the key  of the DSO?.

Regards,

Rajesh

[amine_lamkaissi]

Hi,

in fact it seems to be a complicated requirment.

I don't have all the details of your requirment, in my opinion, using an infobject refering to each DSO in the key of your consolidation DSO will allow you to store all the records from the 4 DSOs (duplicated records). But this is not very good for performance.

What's kind of calculation do you have to do?

Amine