SAP BI Asset Extraction Architecture in S4/ECC

[renish]

Asset extraction from SAP is designed such a way that it could be optimized for delta extraction. Asset delta extraction is designed differently from other delta mechanism using SAP standard extractors / data sources.

SAP BadI  FIAA_BW_DELTA_UPDATE is responsible for marking data records as delta if any transaction has been posted in the ECC/S4 system related to Asset master or asset transaction. Delta extraction in BW system will delete these delta marked records from these tables with specified limit. The last step of the delta extraction is to delete data from these tables based on its type and store the new timestamp of successful delta. At a very high level, I will try to explain the process of asset extraction architecture.

BadI FIAA_BW_DELTA_UPDATE will update the mainly below three tables as per the asset posting.

Table 1 : BWFIAA_AEDAT_AS – Asset Master

Table 2 : BWFIAA_AEDAT_AB – Asset AFAB - depreciation area specific master

Table 3 : BWFIAA_AEDAT_TR – Asset Transactions

If you are not using Asset extraction by standard content/extractors at all, the mentioned BadI must be deactivated. Please refer 590034 - Deactivating implementation FIAA_BW_DELTA_UPDATE - SAP for Me. If you are extracting any of the delta, mentioned BadI must be active.

For e.g. if you are only extracting masterdata, BadI must be active, however the tables related to transactions will grow day to day without deletion. You must take care of growing such unnecessary logs by deleting from Transactions by creating small custom ABAP report or direct table update. Please refer 952920 - Reorganization of change tables for delta upload - SAP for Me and 2969759 - How to reduce the data volume of BWFIAA_AEDAT_ table - SAP for Me.

Interface class IF_EX_FIAA_BW_DELTA_UPDATE of BadI FIAA_BW_DELTA_UPDATE has mainly 3 methods.

IF_EX_FIAA_BW_DELTA_UPDATE~UPDATE_POSTING_720 is updating below tables for delta marking

BWFIAA_AEDAT_AS and BWFIAA_AEDAT_TR

IF_EX_FIAA_BW_DELTA_UPDATE~UPDATE_MASTERDATA is updating below tables for delta marking

BWFIAA_AEDAT_AS and BWFIAA_AEDAT_AB

IF_EX_FIAA_BW_DELTA_UPDATE~UPDATE_DEPRECIATIONS is updating below tables for delta marking

BWFIAA_AEDAT_AB and BWFIAA_AEDAT_TR

There are four SAP provided Asset extractor for Delta extraction which utilizes above tables.

1. ASSET_ATTR_TEXT  - Asset Subnumber with Description
2. 0ASSET_AFAB_ATTR - Depreciation Area Real or Derived
3. 0FI_AA_11 - FI-AA: Transactions
4. 0FI_AA_12 - FI-AA: Posted Depreciations

SAP has created internal validation for extracting data in sequence based on timestamp of last successful delta extraction which is stored in table BWOM2_TIMEST. Validation is very straight forward. Timestamp should be  ASSET_ATTR_TEXT  <= 0ASSET_AFAB_ATTR <= 0FI_AA_11/12. i.e. SAP system will not allow to extract 0FI_AA_11/12 without extracting 0ASSET_AFAB_ATTR. (I am not including 0FI_GL_4 dependency because most of the organization has already started using ACDOCA based extraction). There is a ABAP report BWOM2_TIMEST which also useful in case of identifying which timestamps should be compared within above extractors.  Please refer 2420714 - FI delta initialization ends with error - SAP for Me. In your ECC/S4 system there are more than one entries for timestamp depending on table BWOM2_TIMEST-DELTIMEST or 15 days. There is only one and most preferably last timestamp should be marked as LAST_TS = 'X'.

Delta / Init with data / Init w/o data extractions is deleting the unnecessary data logs from BWFIAA_AEDAT_ tables as well as timestamps from BWOM2_TIMEST which are older than 15 days as default. There is another table BWOM_SETTINGS for maintaining these parameters for lot many SAP extractors if you wish to change these default parameters. Here in below example, above 15 days has been changed to 60 days. It means now after successful Asset delta extraction, logs are being deleted which are 60 days older.  

Below is exact location of Asset delta extraction code where deletion from logs table are handled. Below SAP function module is getting called for all four extractors at the end of successful extraction. Code will dynamically identify the table from which data needs to be deleted.

1. ASSET_ATTR_TEXT  will delete data from BWFIAA_AEDAT_AS
2. 0ASSET_AFAB_ATTR will delete data from BWFIAA_AEDAT_AB
3. 0FI_AA_11  will delete data from BWFIAA_AEDAT_TR
4. 0FI_AA_12 will delete data from BWFIAA_AEDAT_TR

Below is standard ABAP report and function group which is being called during Asset extraction. There are lot many useful comments/documentation maintained by SAP in code itself.

Report : SAPLBWFIAA

Function Group : BWFIAA