cancel
Showing results for 
Search instead for 
Did you mean: 

InfoSource having two sources with different fields, writing into DSO

Former Member
0 Kudos

Dear experts,

I just came across a problem which seems to be quite general since it is a typical scenario in LSA concept and I don´t have a good answer. Maybe you have...

The problem is following:

I have following design with two Sources, one InfoSource and an InfoProvider on top. This InfoProvider is a Standard DSO.

The DataSources on the left (L) and the one on the right (R) deliver different fields (but same key) and should all be written into the same DSO updating different fields.

The bottom transformations going into the InfoSource have only update rules for the fields populated.

But the top Transformation has all fields (since it is the combination out of the two Sources) as update to the DSO.

http://help.sap.com/static/saphelp_nw70/en/44/0243dd8ae1603ae10000000a1553f6/h-00100120000_image004.gif

Now what happens is, that depending on which DTP is loaded second, it overwrites the already existing fields not being delivered with blank. Why? Because the InfoSource cannot transport the information which fields to update. This seems quite obvious.

But what´s to do here? Do I need to read forward to the DSO selecting the already existing, missing fields?

Or can I create two InfoSources? If this is the suggested way how to do it, how does this work with a SPO-DSO on top?
As I learned, they all automatically include a Inbound Infosource which has the structure of the DSO and a 1:1 Transformation going forward to the DSOs:

This would be the same scenario as described above... without the possibility to create different InfoSources here.

So what´s the suggestion here? Do the Sources always have to deliver all fields to use SPOs?

Thanks in advance,

Oliver

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

A colleague came across a strange behaviour:

If the transformation does not contain any master data lookups or similar, the behaviour seems to be different.

The system then does not overwrite the not mapped fields during DSO activation.. however this works… anyone an idea?