CL_EHHSS_BI_INC_EXTRACTOR - Extractor class of Incidents for BW content

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Functionality

This Class merges extractors and common functions. Each extractor method has name like EX_DSxx_NAMEwhere xx is the number of the destination DSO as it is described in SDD, the Name is short descriptionof what data of Incident that extractor extracts. That is, all this extractors are public methods and all common methods are private.

This extractors share some common functionality. Of course this is constructor of object, as well functionsthat have to deal with input filters. Function module have to set properties of extractor object, thesame input variables it gets. This is I_MAXSIZE, I_UPDMODE and I_T_SELECT. Extraction method has tocheck update mode and depending of this to get keys from Change Doc regarding what Nodes this extractorcares for. Extractor has to initialize root keys by calling GET_FILTERED_KEYS of class and to createmo_root ENA object. The middle point/juncture of initialization process is GET_FILTERED_KEYS function,it could take input from GET_DELTA_KEYS, to execute query over input keys regarding filter fields (I_T_SELECT).The final result of initialization process is mr_root_keys table and mo_root object, this table havekeys of root nodes of all incidents that will be extracted/reported. This is done by methods ROOT_HAS_MORE_ROWS() and GET_NEXT_PACKAGE( ), these methods take care for creating and reading mo_root object, regardingoptimization of ENA for mass mode. First one checks for data on mo_root object and if it isn't initialized or is out of index then method GET_NEXT_PACKAGE( ) is called to collect next data.

mr_root_keys table is used also to determine steps one and two, if it is initial we are on step oneinitialization, if mr_root_keys is created then it contain root keys and extraction should begin. Toprepare this keys programmer have to use method GET_FILTERED_KEYS( ). This method uses several queriesof Incident BO to collect necessary keys. If extractor is on update mode Delta it also has to call GET_DELTA_KEYS(), input of this method is table with names of DB tables that have to be checked for changes during expired period, for this purpose it use CHANGEDOCUMENT_READ function module.

Extraction start always from root node, object mo_root, to loop over it extractor has to use methods ROOT_HAS_MORE_ROWS() and GET_NEXT_ROOT() to read next instance and data of root node.

Warning: One package could exceed maxsize because all records of one incident must be together for proper work of BW.

Relationships

Example

Notes

Further information

CPI1466 during Backup   CPI1466 during Backup  
This documentation is copyright by SAP AG.


Length: 2655 Date: 20120526 Time: 115834     triton ( 175 ms )