Explore to the Update Tab of Data Transfer Process in SAP BI 7.0

Transcription

1 Explore to the Update Tab of Data Transfer Process in SAP BI 7.0 Applies to: SAP BI 2004s or SAP BI 7.x. For more information visit the Enterprise Data Warehousing. Summary This article will explain about what are all the options available in the Update tab of Data Transfer Process and which options has to select in different scenarios. Author: Venkateswarlu Nandimandalam Company: Mahindra Satyam Created on: 17 September 2011 Author Bio Venkateswarlu Nandimandalam, working in Mahindra Satyam has one and half year experience in SAP BI 7.0 and he has been working in Production Support and Custom Development 2011 SAP AG 1

2 Table of Contents Data Transfer Process:... 3 Data Target:... 3 Error Handling:... 4 How to Create Error DTP:... 4 How to Correct Error Records in Error Stack:... 5 Step 1:... 6 Step 2:... 6 Maximum Number of Errors per Package:... 7 No Update without Master Data:... 7 Related Content... 8 Disclaimer and Liability Notice SAP AG 2

3 Data Transfer Process: Data transfer process (DTP) loads data within BI from one object to another object with respect to transformations and filters. In short, DTP determines how data is transferred between two persistent objects. It is used to load the data from PSA to a data target (Cube or DSO or Info Object etc.) thus, it replaced the data mart interface and the Info Package. Now in this article I am going to explain what are all the options available in the Update tab of DTP, and how to use those based on our requirements Data Target: This is the target to which DTP has to load the data. The below are the different types of objects to which we can load data using DTP in SAP BI Info Cube 2. Data Source Object. 3. Info Object: Attributes 4. Info Object: Texts 5. Info Object: Hierarchies 6. Open Hub Destinations. After we select the type of the target object, we have to give the technical name of that in the next field. You can see in the below screens respectively SAP AG 3

4 Error Handling: In Data Transfer Process, we can specify how the system has to respond when data records contains errors. If we activate error handling, the records with errors are written to Error Stack. Error Stack is nothing but a request based database table (PSA table). We have 4 types of settings available for error handling as mentioned below. 1. Switched Off 2. No Update, No Reporting (Default) 3. Update valid records, No Reporting (request red) 4. Update valid records, Reporting possible (request green) Switched Off: In this option we don t have error stack to store error records. If we have any incorrect records in the data then DTP will get fail and we have to load the entire data again. This is again burden to the system. No Update, No Reporting (Default): In this also we will not have error stack to store the incorrect records. If error records found, system terminates the update of the entire data package and DTP will turn to red. As we don t have error stack again we have to load the entire data from source. This is also burdened to the system. This option is selected by default in DTP. Update valid records, No Reporting (Request red): This option allows us to update the valid records. The correct records will be loaded to the target and error records will move to the error stack. The request will not be available for reporting (request status is red). We have to load the error records through error DTP after editing in the error stack. After the error DTP load is completed, we need to change the QM status of the main request to green in target to make sure it is available for reporting. Update valid records, Reporting possible (request green): This is also works same as above; the difference is the request will be available for reporting and error records written to the error stack. We have to load the error records using error DTP after editing the records in error stack. We can see the available options for error handling in the below screen How to Create Error DTP: In Update tab, if DTP already has error DTP then under error handling we will have the option Display error DTP.If DTP does not have error DTP, then we will have option create error DTP. If we click on create error DTP, and then system automatically creates error DTP for main DTP SAP AG 4

5 How to Correct Error Records in Error Stack: Let s take an example where we made the setting for error handling as Update valid records, no reporting and executed the DTP. Because of data contains error records DTP fails with below error and request in the target will set to RED. See the below screen. If we drill down till data package level, we can see the error as mentioned above. Now we have to click on error stack to go into the error stack and check the exact error in the records. We will have error stack symbol at the top in DTP monitor screen as shown below. In error stack we will have error records in package wise. In our case as we have only one data package there is only one data package in error stack SAP AG 5

6 Now we have to select the data package and click on tick mark to go into the records. Now if we double click on status on each record, we will get the exact error as shown below. To edit each record, select the record and click on edit symbol. Make necessary changes and save the record. Repeat the same steps until all the records are completed in error stack. Step 1: Step 2: 2011 SAP AG 6

7 Once all the records are edited and saved, come back main DTP and click display error DTP then execute the error DTP to load the data from the error stack to target. After error DTP is successfully loaded data to the target, we have to change the QM status of the main DTP request from RED to GREEN to make sure it is available for reporting. Maximum Number of Errors per Package: Here we have to give how many records have to allow per data package in error stack. If it receives more records than defined then it terminates the load process. If we do not enter anything here, then error records will not be accepted by error stack. No Update without Master Data: If we select this option, the system terminates update of the request if no master data is available for a data record. Before we select this option, we have to make sure that the master data is loaded for all the relevant fields SAP AG 7

8 Related Content Creating Data Transfer Processes c644cd119f46?quicklink=index&overridelayout=true For more information visit the Enterprise Data Warehousing 2011 SAP AG 8

9 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 9