App Extensibility: Manage Internal Requirements

Use

You can extend Manage Internal Requirements according to your business needs for different aspects.

For this purpose, the following extensibility options are available:

New Columns for the Stock/Requirements List

You can add columns to the stock/requirements table in the detailed view of this app.
New Blocks for the Quickviews

You can add blocks at the end of each quickview with additional fields or add fields at the end of an existing block.

New Columns for the Stock / Requirements List

To add columns to the table in the detailed view, 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:

UI		Back End/ABAP
View	Extension Point	Design Time: Gateway Entity	Design Time: OData Entity Type	Design Time: Extension Include (in DDIC Structure)	Runtime: BAdI to Be Implemented
SupplyDemandPanel.fragment.xml	extSupplyDemandPanelAddColumnHeader1 extSupplyDemandPanelAddColumnData1 (Column added to the left of the Date column.)	PP_MRP_COCKPIT	SupplyDemandItem	PPMRP_SUPPLY_DEMAND_ITEM_INCL	BAdI: PPMRP_ENHANCE_SDIV_DETAILS Method: ENHANCE_SDIV_DETAILS
	extSupplyDemandPanelAddColumnHeader2 extSupplyDemandPanelAddColumnData2 (Column added between the columns Date and Icon.) Note that the Icon column does not have a header.
	extSupplyDemandPanelAddColumnHeader3 extSupplyDemandPanelAddColumnData3 (Column added between the columns Icon and MRP Element.)
	extSupplyDemandPanelAddColumnHeader4 extSupplyDemandPanelAddColumnData4 (Column added between the columns MRP Element and Quantity.)
	extSupplyDemandPanelAddColumnHeader5 extSupplyDemandPanelAddColumnData5 (Column added between the columns Quantity and Available.)

Note

The view that contains the extension points for adding columns to the stock/requirements table is located in the UI5 application PP_MRP_REUSE (reuse library). The stock/requirements table must therefore be extended in the reuse library and this extension must then be added to the component file for this app. The app then includes the extension made in the reuse library during runtime.

If the data that should be displayed in the new columns is not part of the entity type SupplyDemandItems, you can proceed as follows when adding new columns:

In the back-end system, you have to perform the following task:
- Insert an append structure in the include structure PPMRP_SUPPLY_DEMAND_ITEM_INCL and add your new field to this append structure.
- Implement BAdI PPMRP_ENHANCE_SDIV_DETAILS (Extensibility of Stock/Requirements and Shortage Lists) to enable the OData service to fill the data in the new field.
- Redefine the OData model and add the new field to the properties of the entity type SupplyDemandItems. Proceed as follows:
  1. Open transaction SEGW (Gateway Service Builder) to redefine the data model of the gateway project PP_MRP_COCKPIT.
  2. Select all artifacts of the gateway project PP_MRP_COCKPIT to copy them into your new OData model.
  3. In the new OData model, add the new field to the properties of entity type SupplyDemandItems and map this field to the new field in the append structure.
  4. Generate the runtime objects
For more information about redefining OData models, see SAP Help Portal at http://help.sap.com/nwgateway. Open the Developer's Guides and choose SAP NetWeaver Gateway Cookbooks OData Channel Cookbooks Getting Started with the Service Builder Redefining Services Redefining OData Services (GW) .
On the UI, you have to implement two extension points for each 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’s columnListItem element.

Example
If you want to add a new column between the columns MRP Element and Quantity, you have to implement the extension points extSupplyDemandPanelAddColumnHeader4 and extSupplyDemandPanelAddColumnData4.

New Blocks and Fields for the Quickviews

To add blocks with additional fields at the end of each quickview or to add fields at the end of an existing block, 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:

UI		Back End/ABAP
View	Extension Point	Design Time: Gateway Entity	Design Time: OData Entity Type	Design Time: Extension Include (in DDIC Structure)	Runtime: BAdI to Be Implemented
ContactInformationQuickView	extContactInformationAddSimpleForm (Allows you to add fields to the contact information in the quickviews, for example for the vendor, customer, or plant.)	PP_MRP_COCKPIT	QuickView	PPMRP_QUICKVIEW	BAdI: PPMRP_ENHANCE_QUICKVIEW Method: ENHANCE_QUICKVIEW
MaterialShortageQuickView	extMaterialShortageQuickViewAddBlock1 extMaterialShortageQuickViewAddBlock2 extMaterialShortageQuickViewAddBlock3 extMaterialShortageQuickViewAddBlock4 extMaterialShortageQuickViewAddBlock5 extMaterialShortageQuickViewAddSimpleForm (Allows you to add fields to the material information.)
PlannedOrderQuickView	extMaterialShortageQuickViewAddBlock1 extMaterialShortageQuickViewAddBlock2 extMaterialShortageQuickViewAddBlock3 extMaterialShortageQuickViewAddBlock4 extPlannedOrderQuickViewAddSimpleForm (Allows you to add fields to the planned order details.)
ProductionOrderQuickView	extProductionOrderQuickViewAddBlock1 extProductionOrderQuickViewAddBlock2 extProductionOrderQuickViewAddBlock3 extProductionOrderQuickViewAddSimpleForm (Allows you to add fields to the production order or process order details.)
PurchaseOrderQuickView	extPurchaseOrderQuickViewAddBlock1 extPurchaseOrderQuickViewAddBlock2 extPurchaseOrderQuickViewAddBlock3 extPurchaseOrderQuickViewAddSimpleForm (Allows you to add fields to the purchase requisition or the purchase order details.)
SalesOrderQuickView	extSalesOrderQuickViewAddBlock1 extSalesOrderQuickViewAddBlock2 extSalesOrderQuickViewAddBlock3 extSalesOrderQuickViewAddSimpleForm (Allows you to add fields to the sales order details.)

Note

The view that contains the extension points for adding blocks or additional fields to quickviews is located in the UI5 application PP_MRP_REUSE (reuse library). The quickviews must therefore be extended in the reuse library and this extension must then be added to the component file for this app. The app then includes the extension made in the reuse library during runtime.

Additional Extensibility Entities

Business Add-Ins (BAdIs)

The following Business Add-Ins (BAdIs) are available for extensibility purposes:

BAdI: User-Defined Field Transport for Purchase Orders (BADI_MRP_COCKPIT_PUR_PO)

You can use this BAdI to import user-defined fields for purchase orders from the front-end system to the back-end system or you can export user-defined fields from the back-end system to the front-end system by using OData services.
BAdI: User-Defined Field Transport for Purchase Requisitions (BADI_MRP_COCKPIT_PUR_PR)

You can use this BAdI to import user-defined fields for purchase requisitions from the front-end system to the back-end system or you can export user-defined fields from the back-end system to the front-end system by using OData services.

These BAdIs are available in Customizing for Production under Start of the navigation path Material Requirements Planning Next navigation step Apps for Material Requirements Planning System Enhancements and Business Add-Ins End of the navigation path .

More Information

For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation Start of the navigation path Extensibility Information for SAP Fiori End of the navigation path .