Diff between Update options

[Former Member]

Hi,

Anyone explain me the what is the exact difference between the update options

like

PSA and then data targets(package by package)

Only PSA and update psa subsequently in data targets

and what is advantages and disadvantages of both and why SAP has given those two options when both functionality remain almost the same and when do we use those options meaning under which scenarios we go for it.

Thank you....

[Former Member · Accepted solution]

Hello Sridevi

Only PSA: Data will be loaded into PSA only.

PSA and then subsequently in data target: Data will be first loaded into PSa...once all the records are in PSa they will be loaded in corresponding data target...we use it when we want to chk data before loading in data target

PSA and data target in serial: The process which is bringing data from source system to PSA same process will move those records into Data target from PSA. we use it when no. of process available in system is less

PSa and Data target in parallel: One process will be bringing data from Source system to PSA. Another process will be there to move data from PSA to Data target...so parallely data is comming to PSa and PSA to target....we use it when no. of processes available in system is more enough

Thanks

Tripple k

[Former Member · Accepted solution]

Hi

Thanks for u r inputs,

Is there another specific functionality difference in both the options.

<b>PSA and the data target in serial</b>

and

<b>Only PSA: Data will be loaded into PSA only</b>.

Thanks

Sridevi

[Former Member]

Hi Sridevi,

1. PSA and Data Targets/InfoObjects in Parallel (By Package)

A process is started to write the data from this data packet into the PSA for each data package. If the data is successfully updated in the PSA, a second parallel process is started. In this process, the transfer rules are used for the package data records, data is adopted by the communication structure, and it is finally written to the data targets. Posting of the data occurs in parallel by packet.

• This method is used to update data into the PSA and the data targets with a high level of performance.

The BW system receives the data from the source system, writes it to the PSA, and starts the update immediately and in parallel into the corresponding data target.

2. PSA and Then into Data Target/InfoObject (by Package)

A process that writes the package to the PSA table is started for each data package. When the data has been successfully updated to the PSA, the same process then writes the data to the data targets. Posting of the data occurs in serial by packet.

• Compared with the first processing option, you have better control over the whole data flow with a serial update of data in packages, because the BW system carries it out using only one process for each data package.

Only a certain number of processes are necessary for each data request in the BW system. This number is defined in the settings made in the maintenance of the control parameters in customizing for extractors.

3. Only PSA

Using this method, data is written to the PSA and is not updated any further.

• You have the advantage of having data stored safely in BW and having the PSA, which is ideal as a persistent incoming data store for mass data as well.

The setting for the maximum number of processes in the source system can also have a positive impact on the number of processes in BW.

To further update the data automatically in the corresponding data target, wait until all the data packages have arrived and have been successfully updated in the PSA, and select Update Subsequently in Data Targets from the Processing tab page when you schedule the InfoPackage in the Scheduler.

A process that writes the package to the PSA table is started for each data package. If you then trigger further processing and the data is updated to the data targets, a process is started for the request that writes the data packages to the data targets one after the other. Posting of the data occurs in serial by request.

4. Only Data Target/InfoObject

• We only recommend this method when loading from flat files or from data sources that are always available.

This is because the data is not always saved persistently into an incoming data store. This saves hard disk space, although it leads to a loss of the following: data security, an option to rebuild processes, and simulation options.

Sarhan.

[Former Member]

Just have a look at :

http://help.sap.com/saphelp_nw70/helpdata/en/43/02c52ce87e2c9ce10000000a1553f6/frameset.htm