Direct Update to Flexible Update

Hi,
I was trying using transitive attributes in which one InfoSource needs to update 2 infoobjects.
I have an infosource which is an direct update because of which it is not allowing to me to create an update rule using this infosource.
Can anyone please explain how do I convert this InfoSource from Direct to Flexible update so that I can update the different objects with the help of update rules.
Please help.
Thanks
Ramesh Ganji

Hi,
To move from Direct update to Flexible update go to RSD1 -> Master data/texts tab -> Bottommost section -> InfoSource with Direct updae = 'X'
To remove this, remove the InfoArea. You cannot use the InfoObject as the flexible InfoSOurce. You need to create a new one for that.
Assign points if useful
Regards,

Similar Messages

Direct update and flexible update

Hi BWers,
I want to know the difference between direct update and flexible update in detail. Could someone explain me in detail with an example? or send me some documents explaining this clearly?
Regards,
RV.

hi
Using the fleixble update method for master data loads you need to create update rules for the
InfoSource and the InfoObject. The direct update loads the data directly without going through the
update rule layer.
The presence of Update Rules allows for extra processing and data transformation capability. Also the
flexible update makes it possible to load data from several sources to the InfoObject, since all
you need to do it to create update rules between the InfoSource and your InfoObject. An example
of using this is when you need to populate certian master data attributes but the data is
coming as transaction data. Sometimes the descriptions are also a part of transaction data,
whereas you may want to load them as text rather than in the cube (this happens a lot in CRM datasources).
So here flexible updates are useful.
check these links also
http://help.sap.com/saphelp_nw04/helpdata/en/98/3a14836fe5e1499a4e17d2d45f4612/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/86/cade377806e664e10000009b38f842/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/41/56ba275e032f1ee10000000a114b54/frameset.htm
http://help.sap.com/search/highlightContent.jsp
Regards,

Differnce b/w flexible update and direct update

Hi gurs,
please tell me the difference between flexible update and direct update.
Rakesh

Hi Rakesh,
Normally when we upload the master data we can select DIRECT UPDATE .. or Flexible update... ..
if you select Direct Update means.. there is no need to create Update rules..
but this is only possible for master data..
if you select Flexible update means.. we need to cretae Update Rules also.., this is mainly for transactional data..
Direct update is generally used for Master data infoobject & here no update rules are used, that means data from source system passes though transfer structure, rules, & communication structure directly to Data target i.e. InfoObject.
Flexible Update - generally used for transaction data ( nowadays can be used for few master data as well) has another set of rule after communication structure i.e. update rule before moving data to data target.
Re: Flexible Update Vs Direct Update?
Flexible update of Master data
Re: Flexible update Vs direct update.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/37dda990-0201-0010-198f-9fdfefc02412
thanks
@jay

When to use Flexible Update and when Direct update??

Hi ,
I know some situations when to load flexible update( transaction , flat file) and when to use direct update (only for master data).
Can some one correct me and tell what are all the possible situations for these 2 types of Update when loading Infosource?
Thanks alot in advance.

hi,
The direct update methods used previously used DataSources for attributes and
texts connected directly with master data tables and text tables for the InfoObject.
In the flexible update, the master data and text tables now appear as data targets. T
he flexible update is used to fill these data targets from master data and text
InfoSources that were created for the InfoObjects listed above. This enables you to
use update rules for the data targets (master data/text tables) in addition to the
transfer rules already used.
check these links for detail.
http://help.sap.com/saphelp_nw04/helpdata/en/98/3a14836fe5e1499a4e17d2d45f4612/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/86/cade377806e664e10000009b38f842/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/41/56ba275e032f1ee10000000a114b54/frameset.htm
http://help.sap.com/search/highlightContent.jsp
Regards,
Manoseelan

Conversion from Direct to Flexible Update

Dear Gurus,
Currently we have direct update for InfoObject 0CUST_SALES (DELTA LOAD). We have to write some update rules for 0CUST_SALES_ATTR and hence we have to go for Flexible Update.
However I do not know any way by which we can just change the type of existing InfoSource from Direct to Flexible. The way I know consists of deleting the Transfer Rules for 0CUST_SALESA_ATTR. And then creating a new Flexible 3.x InfoSurce with DataSource 0CUST_SALESA_ATTR. The problem with this approach is that if we delete transfer rules then system will delete PSA as well. This means, once our Flexible Update design is complete, we have to go for a Full or INIT Load. Is there any way, we can change from Direct to Flexible update and continue to receive Deltas as usual?
Please help.
Regards,
X

Hi,
Have you tried this. In your infoobject properties you will have the option of selecting the application component and Info Area in which this has to sit. So when it is direct update you select application component.
Now try selecting InfoArea and check what happens. It is for sure that your IO will come in the Dataprovider list.
I think you can try this once.
Regards,
Pramod

Flexible update or Direct update

Hi Gurus,
When we load the master data using a generic extractor from R3 to BW, which update(direct or flexible) is preferable. Can you please tell me about the pros and cons.
Thanks,
Regards,
aarthi
[email protected]

Hi Aarthi,
Direct or Flexible update will actually be dictated by which Infosource the datasource needs to be attached to. If this data is just going to the InfoObject, then you can work with direct update. If the data extracted by this datasource has to be fed to multiple objects/targets, then you need a flexible update as this involves update rules from the InfoSource into the data targets.
There is really no pro and con to each method, but just the decision as to whether you need another layer of processing (update rules) or need to push the data to multiple targets.
Hope this helps...

Flexible update Vs direct update.

Hi Experts;
could someone explain what are flexible and direct updating of Infosource, I kind of know the definitions but need more explanations.
Krishma

Hi Krishma;
InfoSources with Flexible Updating:
For an InfoSource with flexible updating, the data from the communications structure is loaded into the data targets (InfoCubes, ODS objects, master data) using update rules. Several data targets can be defined by one InfoSource. The InfoSource can contain transaction data as well as master data.
InfoSources with Direct Updating:
Master data (characteristics with attributes, texts or hierarchies) of an InfoObject can be updated directly (without update rules, only using transfer rules) to the master data table with an InfoSource with direct updating. To do this you must assign it application components. The characteristic is subsequently displayed in the InfoSource tree in the Administrator Workbench. You are able to assign DataSources and source systems to the characteristic from here. You are also able to load master data, texts, and hierarchies for the characteristic.
Hope it makes clear to you now.
Regards:
BK

Direct and flexible update

Hi,
In the infopackage of a masterdata object which is having direct update i.e; no infosource in between masterdataobject and the datasource, can the option under processing " only psa and update subsequntly in Data targets" be checked.
This option is available for flexible update masterdata objects where as for directupdate objects this option is disabled in the infopackage.
Kindly clarify if this option is possible or not.
Regards,
Geetha

Hi,
U shall get the option in both scenarios, irrespective of direct or flexible update.
But if your datasource is a 7.x datasource the infopackage will be defaulted to load till PSA only
Hope it helps.
Regards,
Rathy

Loading Master Data with Flexible Update

Hi,
I have created an Infoobject - Business Partner (Master Data bearing characteristics). The attributes to this are Region, Sales Person, Industry code which are master bearing characteristic as well.
I need to load data to the business partner from a csv file.
The layout of the CSV file is -
BP number, BP text (long Text), Region Code, Region Desc (Med Text), Sales Person Code, Sales Person Desc (Med Text), Industry Code, Industry description (Med Text).
How do I define the infosource to load this data.
Appreciate any help with this.
Thank You,
Prashanth

Hi,
First of all, I need to note that there are two kind of Infosources: with direct and flexible update.
If you choose a direct IS, then in the creating of the IS you just enter the name of the infoobject where you are going to load data. The system will create a IS (comm. structure). Enter this IS for changing. The system will propose you the communication structure, click on a bottom icon Transfer structure/Transfer rules, choose as a Source system your flat file system. Agree with the system when it asks you to save assignments (up to 3 times). Activate TRs. Then click in the field for Datasource. You may see there another datasources (for texts, attributes and hierarchies). Choose one by one another datasources with their activation.
Now you can create an infopackage for a load you can choose what kind of package it is going to be for loading texts, attributes or hierarchies.
Note that in this case the structure of the flat file is proposed by the system and you need just prepare the flat file corresponding to the proposed structure (different for each of 3 possible datasources). Execute infopackage.
If you use a flexible IS, then you may insert into comm. structure the fields that you think you may need in the master data. Note that here you may have not only attributes but TEXTS also. Save a comm. structure. Assign a flat file source system and activate a TRs.
After that in RSA1-dataproviders tab right click insert IO as a data target choose your IO. Refresh the screen. Youll see up to three data targets. Create update rules for each of them. In URs map the fields in the IS with the fields in URs.
Best regards,
Eugene

What is Flexible Update in this context?

Hi,
when you told...
"...if you are having a problems....then you have to do a flexible update ..."
Can you share your thoughts on what you think this discussion may be about regarding "Flexible Update?
Thanks

hi Amanda,
"...if you are having a problems....then you have to do a flexible update ..."
this info isn't sufficient ? what problems ?
problem with direct update master data ?
check flexible update vs direct update
http://help.sap.com/saphelp_nw70/helpdata/en/86/cade377806e664e10000009b38f842/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/87/3fdf9587f211d5b2ff0050da4c74dc/frameset.htm
hope this helps.

Infosource to be used for both Direct update and Flexiable update

Hi,
I had a Data source 0CUST_SALES_ATTR.
A infosource is created Direct Update of Master Data from DS:0CUST_SALES_ATTR to 0cust_sales.
So the Data source 0CUST_SALES_ATTR is being used to load ATTR data of 0CUST_SALES.
Now as per my requirment created a new Z infoobject to use for Transtive attributes....How can i use the same data source 0CUST_SALES_ATTR to load 0CUST_SALES (Direct Update) and the new Z infoobject using Transfer & Update rules.
and
Question:
Will it be possible to switch the current Infosource with direct update to Flexiable update with out deleting the Transferrules as there are lot of routines in the transfer rules
Thanks
Edited by: suser1234 on Oct 5, 2010 11:21 AM

Hello Sir,
How did you handle your above problem I am into a compeltely similar situation. Your help would be appreciated if you can share the approach you followed.
Thanks,
-Su

HT6030 I have many problems with my mail since I moved to mavericks. The filter is very sensitive, read mail appears as unread, I can't drag mail to the folders and more. I can't update the mail program as directed on this page, update says my system is u

I have many problems with my mail since I moved to mavericks. The filter is very sensitive, read mail appears as unread, I can't drag mail to the folders and more. I can't update the mail program as directed on this page, update says my system is updated

I don't think that a software update from Apple will solve the issues that you are having. You have a rogue installation. After you posted I have just done the following:
Disk Utility can verify my partitioned Volume (including my boot disk) AND REPAIR the non-boot disks on the same Volume without a glitch. It repairs the non-boot disks containing data smoothly.
I have used Mail to send some mails from some Yahoo and Hotmail accounts to my Thunderbird client containing GMail accounts - absolutely normal.
I have iLife '09 but my iMovie '09 and iPhoto '09 open in a jiffy and I see no issues here. I have 6GB RAM (Maximum) on an early 2008 Macbook Pro with a 750GB hard drive partitioned with 120GB reserved for the Boot Drive.
I am sorry that I cannot help further but I am sure there must be a way to reinstall the software without having to revert to restoring your ML backup. I have two clones and if you have such I would attempt to do that through that rather than through Time Machine - that is of course if you have a cloned drive.
Good luck!

DRAWBACKS OF DIRECT DELTA, SERIALIZED V3 UPDATE...........

HI,
anybody explain me in details draw backs of Direct Delta, Sereilized v3 update ,Unsereialzed v3 update and Queued Delta in lo-cockpit.
Regards.
ASIM.

Unserialized V3 update:
With this update mode, the extraction data of the application being viewed is written
to the update tables with an V3 update module and is kept there until the data is read
with an update collection run and processed. The data in the update collection run,
however, is read from the update table without considering sequence and is transferred
to the delta queue.The method Unserialized V3 Update does not ensure serialization of the document
data. Update to the DataStore objects is not recommended if serialization is desired
(for example, for reporting purposes)
Direct delta:
With this update mode, the extraction data is transferred directly to the delta queue
with every document posting. The sequence of the transfer thus agrees with the
chronological order of data creation.Benefits and properties of Direct Delta:
By writing to the delta queue within the V1 posting process, serialization by
document is ensured with the enqueue concept of applications.
For customers with fewer documents, the process is recommended if a
downtime is possible in the initialization process during restructuring and delta
initialization requests.
V1 is more burdened by this process than with V3 or Queued Delta. For
customers with the amount of documents mentioned above, this is not really
a factor.
Extraction is independent of V2 updating.
Additional monitoring of update data or extraction queue is not required.
Queued delta:
With this update mode, instead of being collected in the update data, the extraction
data from the affected application is collected in an extraction queue and can be
transferred to the delta queue, in a similar manner to the V3 update, with an update
collection run. Depending on the application, up to 10,000 delta extractions of
documents can be aggregated to an LUW in the delta queue per DataSource.
Benefits and properties of Queued Delta:
By writing to the extraction queue in the V1 update process, serialization by
document is ensured with the enqueue concept for applications.
Due to the collection of data in the extraction queue that is regularly processed
(SAP recommends hourly), the process is especially recommended for customers
with a high amount of documents.
The collection run uses the same reports as previously (RMBWV311,...).
In the initialization process, the collection of new document data during the delta
initialization request can reduce the downtime on the restructuring run (filling
the setup tables).
V1 is much more difficult than the use of V3.
In contrast to the V3 collection run, a definitive end of the collection run is
within reach and a subsequent process can be scheduled. After the collection
run for an application has finished, an event (&MCEX_11,...) is triggered
automatically, that can be used at the start of a subsequent job.
Extraction is independent of V2 updating.
(V3)serialized delta ;
With this update mode, the extraction data of the application being viewed is written
to the update tables with an V3 update module and is kept there until the data is read
with an update collection run and processed. The data in the update collection run,
however, is read from the update table with keeping original sequence and is transferred
to the delta queue.
Error:
1) The serialized V3 update can only guarantee the correct sequence of extraction data in a document if the document has not been changed twice in one second.
2) Furthermore, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if the times have been synchronized exactly on all system instances, since the time of the update record (which is determined using the locale time of the application server) is used in sorting the update data.
3) Furthermore, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if the times have been synchronized exactly on all system instances, since the time of the update record (which is determined using the locale time of the application server) is used in sorting the update data.
4) In addition, the serialized V3 update can only ensure that the extraction data of a document is in the correct sequence if an error did not occur beforehand in the U2 update, since the V3 update only processes update data, for which the U2 update is successfully processed
Hope this helps.
Regards,
Viren

Flexible Update Creation

Working on using 0MAT_PLANT as the main Master Data for our material information. I need to create it as an Infoprovider and was told that I needed to create a flexible update for it. Although I have tried I seem to be having a problem with a data source assignment for it. Why am I having the issue with the data source assignment and what do I need to do to complete this? Is there another way I should be going about this?
Caroline

Hi Caroline,
Have you done these:
- Transferring business content DSs you need in RSA5 in the source system
- Replicating source system DSs in BW?
Best regards,
Eugene

Flexible update master data inconsistencies

Dear experts,
I have the following issue with flexible update master data for 0employee.
0employee is getting loaded from 3 different sources. here is the example below;
employee address   phone compcode
1                germany   123
1                denmark                001
1                UK
here employee is a key for 0employee what happens to above data after attribute change run.
can any one let me know what will be final results. my requirement is i have to get company code at any circumstances. it there a proper sequence of load to be followed in this case. your inputs is highly appreciated with points.
Cheers,
VSN

If 0employee gets data from 3 different sources it will overwrite the existing records when same employee '1' is coming from Germany , Den , UK .. Only the recent record will be availble in MD tables..
You need to add SOURCESYSTEM as compounding object to 0EMPLOYEE.
Put constant GE for 0SOURCE SYSTEM in transformations
constant Den for 0SOURCE SYSTEM in transformations
constant UK for 0SOURCE SYSTEM in transformations
when you execute MD
Source system ...employee address phone compcode
GE.............................1...................... germany.... 123
Den.............................1...................... Denmark.... 123
UK.............................1......................UK .............. 123

Direct Update to Flexible Update

Similar Messages

Maybe you are looking for