You can extend the Monitor Material Coverage app according to your business needs for different aspects. For this purpose, the following extensibility options are available:
To add customer-specific columns to the table, the extensibility entities listed below are available on the different software layers. You have to extend each of these entities according to your specific business needs.
Configuration of the Back-End
Back End/ABAP |
||
---|---|---|
Design Time: Gateway Entity |
Design Time: OData Entity Type |
Runtime: Business Add-In to Be Implemented |
PP_MRP_COCKPIT |
MaterialShortage |
Enhancement Spot: ODATA_PPMRP_EXTENSIONS BAdI: PPMRP_MAP_MATSHORT Method: MAP_MATERIAL_SHORTAGE |
To add new columns to your material list, you have to perform the following tasks in the back-end system to extend the back-end OData service:
You can define your customer-specific fields within the extension include.
For this app create an append structure in the include structure PPMRP_MATERIAL_SHORTAGE_INCL and add the new, customer-specific fields to this append structure. These new fields can be used in the gateway entity PP_MRP_COCKPIT.
Redefine the OData model. Proceed as follows:
Open transaction SEGW (Gateway Service Builder) to redefine the data model of the gateway project PP_MRP_COCKPIT.
Select all artifacts of the gateway project PP_MRP_COCKPIT to copy them into your new OData model.
Enter a name and a data type for the new field in the entity type that maps to the new field in the append structure.
Generate the runtime objects.
Create an implementation for the BAdI method MAP_MATERIAL_SHORTAGE of the BAdI PPMRP_MAP_MATSHORT to enable the OData service to fill the data in the new field.
If there are additional fields available in the OData service, you can display these fields on the UI. 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 more information about redefining OData models, see SAP Help Portal at http://help.sap.com/nwgateway. Open the Developer's Guides and choose .
Configuration of the Front-End
Extension Points
On the UI, you have to implement two extension points for every column you want to add: one extension point for the header and one for the corresponding data. The extension points for the header extend the columns aggregation of the table. The extension points for the data extend the cells aggregation of the table.
The following extension points are available:
View |
Extension Point |
Use |
---|---|---|
S1.view.app.xml |
extMaterialShortgeAddColumns extMaterialShortgeAddCells |
Allows you to display additional SAP standard fields as table columns in the Monitor Material Coverage app. |
If there are additional fields available in the OData service, you can display these fields on the UI. 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 .
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller |
Hook |
Use |
---|---|---|
S1.controller.js |
extHookGetBaseSelectFields |
Allows you to display customer-specific fields as table columns in the Monitor Material Coverage app. You have to extend the array aSelectedFields to retrieve the data values for the new columns. |
In the Monitor Material Coverage app, you can personalize the table by choosing which table columns are shown. You can also use this function to hide table columns you added by extending the app.
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 .
To add fields to the material quickview, the extensibility entities listed below are available on the different software layers. You have to extend each of these entities according to your specific business needs.
Configuration of the Back-End
Back End/ABAP |
||
---|---|---|
Design Time: Gateway Entity |
Design Time: OData Entity Type |
Runtime: Business Add-In to Be Implemented |
PP_MRP_COCKPIT |
QuickView |
Enhancement Spot: ODATA_PPMRP_EXTENSIONS BAdI: PPMRP_ENHANCE_QUICKVIEW Method: ENHANCE_QUICKVIEW |
If there are additional fields available in the OData service, you can display these fields on the UI. 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 .
Configuration of the Front-End
Extension Points
The following extension points are available:
View |
Extension Point |
Use |
---|---|---|
MaterialShortageQuickView |
extMaterialShortageQuickViewAddBlock1 extMaterialShortageQuickViewAddBlock2 extMaterialShortageQuickViewAddBlock3 extMaterialShortageQuickViewAddBlock4 extMaterialShortageQuickViewAddBlock5 extMaterialShortageQuickViewAddSimpleForm |
Allows you to add fields to the material quickview. |
If there are additional fields available in the OData service, you can display these fields on the UI. 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 .
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller |
Hook |
Use |
---|---|---|
QuickViewHelper.js |
extHookMaterialShortageQuickView |
Allows you to display customer-specific fields in the material quickview. You have to extend the array sPath to retrieve the data values for the new fields. |
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 .