You can extend Monitor Data Aging Objects according to your business needs for different aspects. For this purpose, the following extensibility options are available:
Add fields, tabs, and controls
You can add fields, tabs, and controls to the views of Monitor Data Aging Objects app.
To add customer fields, tabs and controls to the app, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:
UI |
Back End/ABAP |
|||
---|---|---|---|---|
View |
Extension Point |
Design Time: Gateway Entity |
Design Time: Extension Include (in DDIC Structure) |
Runtime: Superclass/ Method to Be Redefined |
S2.view.xml |
extS2ObjectListItemAttribute |
DataAgingObjectCollection |
DAAG_S_MONOBJ_DAGO_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJECTC_GET_ENTITYSET GET one data aging object: DATAAGINGOBJECTC_GET_ENTITY |
S3.view.xml |
extS3ObjectHeaderAttribute |
DataAgingObjectDetail |
DAAG_S_MONOBJ_DAGO_DET_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: GET one data aging object detail: DATAAGINGOBJEC04_GET_ENTITY UPDATE / PUT one data aging object detail: DATAAGINGOBJEC04_UPDATE_ENTITY DATAAGINGOBJEC04_PUT_ENTITY |
extS3ObjectHeaderStatus |
DataAgingObjectDetail |
DAAG_S_MONOBJ_DAGO_DET_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: GET one data aging object detail: DATAAGINGOBJEC04_GET_ENTITY UPDATE / PUT one data aging object detail: DATAAGINGOBJEC04_UPDATE_ENTITY DATAAGINGOBJEC04_PUT_ENTITY |
|
extS3BeforeHotPartitionTable |
DataAgingObjectTableHotPartitionColl |
DAAG_S_MONOBJ_TAB_HOT_PART_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJEC02_GET_ENTITYSET GET one hot partition of table: DATAAGINGOBJEC02_GET_ENTITY |
|
extS3AfterHotPartitionTable |
DataAgingObjectTableHotPartitionColl |
DAAG_S_MONOBJ_TAB_HOT_PART_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJEC02_GET_ENTITYSET GET one hot partition of table: DATAAGINGOBJEC02_GET_ENTITY |
|
extS3HotPartitionTableToolbar |
DataAgingObjectTableHotPartitionColl |
DAAG_S_MONOBJ_TAB_HOT_PART_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJEC02_GET_ENTITYSET GET one hot partition of table: DATAAGINGOBJEC02_GET_ENTITY |
|
S4.view.xml |
extS4ObjectHeaderAttribute |
DataAgingObjectDetail |
DAAG_S_MONOBJ_DAGO_DET_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: GET one data aging object detail: DATAAGINGOBJEC04_GET_ENTITY UPDATE / PUT one data aging object detail: DATAAGINGOBJEC04_UPDATE_ENTITY DATAAGINGOBJEC04_PUT_ENTITY |
extS4ObjectHeaderStatus |
DataAgingObjectDetail |
DAAG_S_MONOBJ_DAGO_DET_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: GET one data aging object detail: DATAAGINGOBJEC04_GET_ENTITY UPDATE / PUT one data aging object detail: DATAAGINGOBJEC04_UPDATE_ENTITY DATAAGINGOBJEC04_PUT_ENTITY |
|
extS4BeforePartitionTable |
DataAgingObjectTablePartitionCollection |
DAAG_S_MONOBJ_TAB_PART_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJEC01_GET_ENTITYSET GET one table partition: DATAAGINGOBJEC01_GET_ENTITY |
|
extS4AfterPartitionTable |
DataAgingObjectTablePartitionCollection |
DAAG_S_MONOBJ_TAB_PART_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJEC01_GET_ENTITYSET GET one table partition: DATAAGINGOBJEC01_GET_ENTITY |
|
extS4BeforeOtherObjectsTable |
DataAgingObjectForTableCollection |
DAAG_S_MONOBJ_DAGO_TAB_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJEC03_GET_ENTITYSET GET one data aging object table: DATAAGINGOBJEC03_GET_ENTITY |
|
extS4AfterOtherObjectsTable |
DataAgingObjectForTableCollection |
DAAG_S_MONOBJ_DAGO_TAB_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJEC03_GET_ENTITYSET GET one data aging object table: DATAAGINGOBJEC03_GET_ENTITY |
|
extS4IconTabBarItems |
DataAgingObjectDetail |
DAAG_S_MONOBJ_DAGO_DET_GWI |
Superclass: CL_DAAG_MONOBJ_DPC_EXT Method: DATAAGINGOBJEC04_GET_ENTITY UPDATE / PUT one data aging detail: DATAAGINGOBJEC04_UPDATE_ENITITY DATAAGINGOBJEC04_PUT_ENTITY |
The gateway entity DataAgingObjectCollection assigned to view S2.xml is also available for all other views.
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller |
Hook |
Use |
---|---|---|
S2.contoller |
extHookModifyFilterOptions |
Allows you to modify filter options |
extHookModifySortOptions |
Allows you to modify sort options |
|
extHookSetHeaderFooterOptions |
Allows you to modify header and footer of the S2 screen |
|
S3.controller |
extHookBeforeDataLoaded |
Allows you to modify request parameters |
extHookOnDataLoaded |
Allows you to access the loaded data |
|
extHookSetHeaderFooterOptions |
Allows you to modify header and footer of the S3 screen |
|
S4.contoller |
extHookBeforeDataLoaded |
Allows you to modify request parameters |
extHookOnDataLoaded |
Allows you to access the loaded data |
|
extHookSetHeaderFooterOptions |
Allows you to modify header and footer of the S4 screen |
If there are additional UI controller hooks available in the controller code, you can add own code. For more information, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation .
For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation .