cancel
Showing results for 
Search instead for 
Did you mean: 

Change Existing InfoSource from Direct to Flexible Update

Former Member
0 Kudos

Hi Gurus,

We are currently loading 0CUST_SALES InfoObject with direct update from InfoSource 0CUST_SALES (DataSources 0CUST_SALES_TEXT and 0CUST_SALES_ATTR). It is Delta.

But now we also have to load one new attribute from 0CUST_SALES InfoSource to 0CUSTOMER InfoObject.

I believe, for this, we have to change the InfoSource 0CUST_SALES (DataSource 0CUST_SALES_ATTR) to Flexible Update. Then we would write our logic in the New Update Rules from InfoSource 0CUST_SALES (DataSource 0CUST_SALES_ATTR) to InfoObject 0CUSTOMER.

1. Firstly, am I right in assuming that we can do as I said above?

2. If yes, then what are the steps we have to take for changing our existing InfoSource 0CUST_SALES from Direct Update to Flexible Update?

3. Would it affect our Deltas?

4. Do we have to do Initialization etc again?

Please clarify.

Regards

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member205352
Active Contributor
0 Kudos

How is your 0CUSTOMER being loaded as of now ???

Flexible ????

Former Member
0 Kudos

Yes,

0CUSTOMER is currently being loaded using Flexible Update InfoSource 0CUSTOMER_ATTR.

Regards,

former_member205352
Active Contributor
0 Kudos

In that case you cant load from 0CUST_SALES for only one attribute.

The problem will be the overwrite issue.

Assume attr2 comes from 0CUSTOMER.

Infosource Customer Attr1 attr2

0CUSTOMER 1000 Hi blank

0CUST_SALES 1000 blank No

Finally

0CUSTOMER 1000 blank No.

You can do a load and test this.

Hope this helps.

Former Member
0 Kudos

Hi,

I don't think it would happen like this.

I would have tested some scenarios like this but unfortunately our system is down and I have to complete design.

My thinking is: we are picking up NEWFIELD from 0CUST_SALES InfoSource and all other fields for 0CUSTOMER InfoObject are coming from 0CUSTOMER_ATTR InfoSource. So it should be okay,but not sure.

Any expert opinion is welcome

Regards

former_member205352
Active Contributor
0 Kudos

Even I thought the same way but I faced the same issue for 0MATERIAL.

The reason which I found out was it had two update rules.

One update rule mappings were :

Attr1 <--- Attr1

Attr2 <---Attr2

Attr3 <--- blank

Other update rule mappings were :

Attr1 <--- blank

Attr2 <---blank

Attr3 <--- attr3

Since our second update rule runs latter it was overwriting our data making attr1 and 2 blanks.

We solved this by using direct update for one of them.

Direct Update and Flexi Update from multiple datasource behave differently so just warned you.

Anywayz even I want to see others opinions.

Former Member
0 Kudos

Thanks Pravin.

But I believe if we do not make assignment for some InfoObject of Data Target in Update Rule, then it means "NO UPDATE". It does not mean "Update with Blank". So it should be ok.

However my questions are still open. Let us hope that somebody replies soon else I am anyway working on it by going thru some documentation.

Regards,