How to combine header and line item characteristics in DSO

[Former Member]

I have a need for a DSO that is keyed off a combination of sales document & item number. I need to preserve the line item granularity, but I also want characteristics from my header records. For each of my line items for an order I would like to have characteristics like doc_date, doc_type, etc. My current architecture has an order item DSO and an order header DSO.

However, I obviously don't have the line item part of the key for my target DSO when using my order header DSO as a source. What is the best solution for getting order header characteristics associated with all line items for a given order in my DSO?

[Former Member]

Your Target is a DSO with Header part.

Source1 : DSO1 with header part

Source2 : DSO2 with line item part.

Update from DSO1 and include some Constant = 0 for line item parts key figures

Update from DSO2

DSO upload in in overwrite mode

[Former Member]

Multi-provider does sound like a viable solution. My concern is the large number of line-items I have and the added complexity of using the MP to join the information 'on-the-fly' rather than doing that work before hand.

InfoSet brings the same concerns as the MP. Extending the extractor means pulling lots of information from the source system twice which I would prefer not to do, but I hadn't considered that as an option.

SDBI - would that load work when I have multiple line item's for a given header record? It doesn't seem that every line item records gets the order head characteristics? Perhaps I'm doing something wrong?

Thanks for all the suggestions, this is helping me figure out the correct path to take!

[Former Member]

HI,

If i understood right, you want to have a DSO on item level, with a characteristic from header data. The best is to create a DSO on ITEM level (DOC_NUM; DOC_ITEM) and put the characteristic you need into data part. So just extrend the item level DSO with one characteristic. If you need the value of the caracteristic added to your item level DSO, load the header DSO first (activate if necessary), and during the load of the item level DSO, write an ABAP routine that reads the header based characteristic, and assign this element to the item level DSO's relevant characteristic.

If you need any more information, let me know. If i misunderstood your problem, please write me more details, technical names, etc. If u need any help in that abap routine, i can help too.

Regards,

Laszlo

[Former Member]

You understood correctly, I want an item level DSO with header characteristics on the records. So your suggestion is to load/activate my header information first and then write a routine during the transformation between line item and new DSO? I see that loading the header data first will get me records with an empty line item so I could then reference the active table during my line item DTP/transformation. However, one of the things I'm looking to do is update a 'status' characteristic that is coming from my header level information.

It would appear that a second load of header information for an existing key would not update my existing records?

Now that I reread your response I think I have a second interpretation. Are you saying just perform a lookup to my header DSO during the load of my item level information into my extended item level DSO? That makes sense, but I worry about that because I have multiple order header characteristics (upwards of 10) that I want to populate - perhaps an end routine is the right answer then?

Thanks for the help.

[alexander_prill]

Hi,

for reporting-only purposes it would also make sense to combine both header and item into a multi-provider.

Maybe this is also a solution for you?

Alexander

[Former Member]

hello

The best way could be to build an InfoSet based on header and item DSO - joined on Document Number characteristic.

However, if you need the header fields in the item dso itself, then you can enhance the item extractor with header fields.

Regards

Sanjyot