TBW42_2 (Parte 2)

1. An Infosource is a persistent structure consisting of Infoobjects for joining two transformations

2. You use Infosources If you want to run sequential two transformations in the data flow without storing the data again

3. An Infosource is a non persistent structure consisting of Infoobjects for joining two transformations

4. An infosource is not recommended If you want to run two transformations sequentialy in the data flowflow

1. Data Transfer Process controls the transfer of data from the source to the entry layer of BI and Infopackage controls the distribution of data within BI.

2. InfoPackage controls the transfer of data from the source to the entry layer of BI and Data Transfer Process controls the distribution of data within BI.

3. A Data Transfer Process can also be used to control data distribution from BI system into any target outside of the BI System such us Open Hub.

4. The data can be updated from an Infoprovider to another Infoprovider using an Infopackage

5. The data can be updated from an Infoprovider to another Infoprovider using an DTP

1. DTP transfer data from persistent object form another object with certain transformations and filter

2. DTP doesn`t repleace the data mart interface and Infopackage in SAP Nwt 2004

3. in SAP Netwaaver 2004s, the Infopackage only loads data to the entry layer of BI (PSA).

4. DTP makes the transfer processes in the data warehousing layer mre transparent

1. There are error handling avalaible for both, an Infopackage and DTP

2. Using an Infopackage, in case of invalidad record, data needs to be reloaded from the source system. So that, there is no error habling avalaible for an Infopackage

3. The error DTP uses delta update to extract the data from the error stack

4. The error DTP uses the full update mode to extract the data from the error stack

1. If errors do ocurr, the update of the entire data package is canceled, the request is not release for reporting and the system doesn`t continue to check the records

2. If errors do ocurr, the update of the entire data package is canceled, the request is not release for reporting but the system continues to check the records

1. The option "Updating records, no reporting (request red)" enables you to update valid data only after the administrator has checked the incorrect, not updated records, and has manually released the request by QM action but is not avalaible for reporting

2. The option "Updating records, no reporting (request red)" enables you to update valid data that is released for reporting only after the administrator has checked the incorrect, not updated records, and has manually released the request by QM action.

3. The option "Updating valid Records, reporting possible" enables you to update valid data that is released for reporting only after the administrator has checked the incorrect, not updated records, and has manually released the request by QM action.

4. With the option "Updating valid Records, reporting possible" the valid records can be reported on inmediately, and automatic follow up actions are also carry out, such us adjusting the aggregates

1, If you don't make any entry in "Specify" the maximun number of incorrect data record allowed before the transfer process is terminated, the treatment of the incorrect data is not activated, and the update is terminated with the last package updated

2, If you don't make any entry in "Specify" the maximun number of incorrect data record allowed before the transfer process is terminated, the treatment of the incorrect data is not activated, and the update is terminated with the first error.

1. A difference between the number of records received and a number of updated records can ocurr if the records are sorted, aggregated or added in the transformation rules or furing the update

2. A difference between the number of records received and a number of updated records can ocurr if the records are sorted, aggregated or added during the update only

3. A difference between the number of records received and a number of updated records can ocurr if the records are sorted, aggregated or added during the transformation rules only

4. The number of data records received is always the same as the number of data records updated

1. The key fields for the Error Stack is known as semantic group. The key should be as detailed as possible with a maximum of 16 key fields.

2. The key fields for the Error Stack is known as semantic group. The key shouldn`t be with too much detailed fields, a minimun of 16 is recommended.

3. The fewer the number of key fields defined, the more record are updated to the error stack

4. More numbers of key fields defined, the more record are updated to the error stack

1. Once the data records have been successfully posted, they are deleted from the error stack

2.. Once the data records have been successfully posted, It is recommend to delete from the error stack

3. If a request is deleted in a DataStore object, the associated data recors are also deleted in the error stack

4. If a request is deleted in a DataStore object, the associated data records are also deleted in 15 days in the error stack

In combination with the characteristic 0SOURSYSTEM

0COMP_CODE

The InfoObject is a unit Infoobject (0UNIT/0CURRENCY)

You can use this InfoSource to update master data like attributes, hierarchies and text, and transaction data

You can use this InfoSource to update master data like attributes and hierarchies, and transaction data

You can use this InfoSource to update master data like attributes and text, and transaction data

You can use this InfoSource to update master data like attributes, hierarchies and text and not transaction data

You can use this InfoSource to update only transaction data