Orecord mode dso
3 likes2,269 views
This document explains the recordmode concept in SAP BI which describes how changes to data records are recorded during delta processing. There are three main types of delta processing - ABR (After Before and Reverse image), AIE/AIM (After Image), and ADD (Additive image). Each type supports different update methods and data loading options. The recordmode values identify the type of change in the data record, such as after-image, before-image, add, delete, new image, or reverse image.
Orecord mode dso
- 1. Record Mode Concept in Delta Management Applies to: SAP BI 2004s or SAP BI 7.x. For more information, visit the Business Intelligence homepage. Summary This document explains the recordmode concept which describes how changes to data records are recorded during delta processing. Author: Apeksha Maniar Company: L&T Infotech Created on: 04 January 2010 Author Bio: Apeksha Maniar, working in L&T Infotech has an experience of more than 3 years in SAP BI. She has been a part of Production Support, Development and Implementation Projects. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 1
- 2. Record Mode Concept in Delta Management Table of Contents What is Delta? .................................................................................................................................................... 3 0recordmode ....................................................................................................................................................... 3 The values for 0recordmode ........................................................................................................................... 3 How do we identify the Delta? ............................................................................................................................ 4 How Data is Brought to BI .................................................................................................................................. 5 ABR: After Before and Reverse Image ........................................................................................................... 5 Example of ABR Delta Process ................................................................................................................................... 5 AIE/AIM: After Image Delta Process ............................................................................................................... 6 Example of AIE/AIM Delta Process.............................................................................................................................. 6 ADD: Additive Delta Process .......................................................................................................................... 7 Example of ADD Delta Process ................................................................................................................................... 7 Related Content .................................................................................................................................................. 7 Disclaimer and Liability Notice ............................................................................................................................ 8 SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 2
- 3. Record Mode Concept in Delta Management What is Delta? Delta is a feature of the extractor, which refers to the changes (new/modified entries), occurred in the Source System. 0recordmode The record mode describes the type of change that a data record contains. If a datasource is delta capable, the field ROCANCEL which is part of the datasource, holds the changes from R/3 side. This field for the DataSource is assigned to the InfoObject 0RECORDMODE in the BI system. ROCANCEL serves the same purpose at R/3 side which its counterpart 0RECORDMODE does at BW side. The values for 0recordmode Figure 1 The following 6 Record Mode types are available, which identify how a delta record is updated to the data target: After-image ‘ ‘ : The record provides an after image, i.e. how does the record look like after the change. The status of the record after it has been changed, or after data has been added is transferred. Before-image ‘X’ : The record provides a before image, i.e. what did the record look like before the change. The status of the record before the change is transferred. Add ‘A’ : The record provides an additive image. Only the differences for all the numeric values are available. Delete ‘D’ : This recordmode type signifies that the record must be deleted. New Image ‘N’ : The record provides a new image, i.e. when a new record is created; a new image is set for it. Reverse Image ‘R’ : The record provides a reverse image. The content of this record is equivalent to a before image. The only difference occurs when updating a DataStore object: An existing record with the same key is deleted. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 3
- 4. Record Mode Concept in Delta Management How do we identify the Delta? The delta process (how the data is transferred) for the DataSource is determined in the table ROOSOURCE (in the source system) or in the table RSOLTPSOURCE (in BI for DataSources 3.x) or in the table RSDS (in BI for DataSources) respectively Properties of the delta process are determined in the table RODELTAM (in BI or in the source system) Figure 2 SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 4
- 5. Record Mode Concept in Delta Management How Data is Brought to BI Data is brought (extracted) to BI using one of the following delta processes: ABR: After before and Reverse image AIE/AIM: After image ADD: Additive image ABR: After Before and Reverse Image What is it? Once a new entry is posted or an existing posting is changed at R/3 side, an after image shows the status after the change, a before image shows the status before the change with a negative sign and the reverse image shows the negative sign next to the record while indicating it for deletion. What update type (for key figures) it supports? Addition Overwrite Does it support loading to both infocube and DSO? YES Example of ABR Delta Process Let us consider a scenario to demonstrate the ABR Delta Process. Since it can be used for both Infocube and DSO, let us consider a scenario where in the loading happens directly to DSO, with the advantage that we can track the record changes in change log table for the DSO. In our case, the DSO is set to additive mode so that the data source sends both before and after image. Incase if it is set to overwrite, it sends only after image. Let us check the new entry in DSO. As shown below (Figure 3), the recordmode has the value N (New entry), indicating that this record is a new one. Here, the CRM Gross Weight (CRM_GWEIGH) field has the initial value 4,093. Figure 3 Next, the value of CRM gross weight (CRM_GWEIGH) is changed to 5,360 in the source system. In order to reflect this change, the data source will send two entries to BI: One is before image with negative sign to nullify the initial value (Figure 4). Figure 4 SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 5
- 6. Record Mode Concept in Delta Management And the other one is after image entry (modified value) as shown below (Figure 5). Figure 5 Upon activation, the after image goes to active table (Figure 6). Figure 6 AIE/AIM: After Image Delta Process What is it? Once a new entry is posted or an existing posting is changed at R/3 side, an after image shows the status after the change. What update type (for key figures) it supports? Overwrite Only Does it support loading to both infocube and DSO? No, only DSO Example of AIE/AIM Delta Process Let us consider the example given above. The initial load to the target DSO is as shown in Figure 7. Figure 7 This time after the value of CRM_GWEIGH is changed to 5,360 in the source system, the datasource sends only one entry to BI, i.e. the After Image, which will hold the change as shown below (Figure 8). Figure 8 Upon activation, the after image goes to active table (Figure 9). Figure 9 SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 6
- 7. Record Mode Concept in Delta Management ADD: Additive Delta Process What is it? Once a new entry is posted or an existing posting is changed at R/3 side, an additive image shows the difference between the numeric values. What update type (for key figures) it supports? Addition Only Does it support loading to both infocube and DSO? YES (In case the DSO has Update type Addition) Example of ADD Delta Process Again consider the above scenario. The initial load to the target DSO is as shown in Figure 10. Figure 10 When the value of CRM_GWEIGH is changed to 5,360 in the source system, the datasource sends one entry to BI with the CRM_GWEIGH value 1,267, i.e. the Difference between the new value and the original value as shown below (Figure 11). Figure 11 Upon activation, the final entry in active table is the result of the addition of the original value and the new value (4093+1267=5360) KG (Figure 12). Figure 12 Related Content For more information, visit Data Extraction from SAP Source Systems For more information, visit the Business Intelligence homepage. SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 7
- 8. Record Mode Concept in Delta Management 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 COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com © 2010 SAP AG 8