Create an implementation of the extension hook method extHookAfterOnInit from Main.controller.js in your extension project within MainCustom.controller.js

Implement the extension point S1_FilterBarListExtension from the overview screen S1.view.xml to add new facet filter lists. An empty fragment is created, in which you can insert the new filter list.

Furthermore, the implementation of this extension point is registered in the Component.js in your extension project:

Within MainCustom.controller.js extension hook method extHookAfterOnInit, you need to register the new filter list in the FilterBarEvtHandler via method addNewFilterList. As input, this method requires the key of the new filter list as a string, and an object containing the properties for the selection criteria (selectField), as well as the corresponding description (ODataLabel) and the corresponding field label (i18nLabel). Finally, you also need to change the entity set of the new OData service, if its name deviates from the standard delivery

Implement the extension point S1_ItemsTableLastColumnExtension from the overview screen S1.view.xml to add new columns to the table. An empty fragment is created, in which you can insert the new column definitions.

Implement the extension point S1_ItemsTableLastCellExtension from the overview screen S1.view.xml for adding the content of the newly defined columns. An empty fragment is created, in which you can insert the new column content to be displayed.

Create an implementation of the extension hook method extHookAfterOnInit from the Main.controller.js file in your extension project within MainCustom.controller.js and enhance the S2 data provider accordingly (name of entity types, select fields), if required.

Implement the extension point S3_DetailFormNewLabelExtension of fragment S3Detail_Form.fragment.xml. An empty fragment is created, in which you can insert the fields. Furthermore, the implementation of this extension point is registered in the Component.js file in your extension project.

Create an implementation of the extension hook method extHookAfterOnInit from the Main.controller.js file in your extension project within MainCustom.controller.js and enhance the S1 data provider accordingly (name of entity types, select fields), if required.

Implement the extension point S1_ItemsTableColumnsExtension from the overview screen S1.view.xml to replace the table columns. An empty fragment is created, in which you can insert the new column definitions.

Implement the extension point S1_ItemsTableCellsExtension from the overview screen S1.view.xml to replace the content description of the newly defined columns. An empty fragment is created, in which you can insert the new column content to be displayed.

Create an implementation of the extension hook method extHookAfterOnInit from the Main.controller.js file in your extension project within MainCustom.controller.js and enhance the S2 data provider accordingly (name of entity types, select fields), if required.

Implement the extension point S2ProcStepObjHeaderAttrExtension from the master screen S2ProcessSteps.view.xml to replace the object header attributes. An empty fragment is created, in which you can insert the new attributes.

Implement the extension point S2ProcStepFirstStatusExtension from the master screen S2ProcessSteps.view.xml to replace the first status attribute of the object header. An empty fragment is created, in which you can insert the new first status.

Implement the extension point S2ProcStepSecondStatusExtension from the master screen S2ProcessSteps.view.xml to replace the second status attribute of the object header. An empty fragment is created, in which you can insert the new second status.

Create an implementation of the extension hook method extHookAfterOnInit from the Main.controller.js file in your extension project within MainCustom.controller.js and enhance the S3 data provider accordingly (name of entity types, select fields), if required.

Implement the extension point S3DetailObjHeaderAttrExtension from the fragment S3Detail_ObjectHeader.fragment.xml to replace the object header attributes. An empty fragment is created, in which you can insert the new attributes.

Implement the extension point S3DetailFirstStatusExtension from the fragment S3Detail_ObjectHeader.fragment.xml to replace the first status attribute of the object header. An empty fragment is created, in which you can insert the new first status.

Implement the extension point S3DetailSecondStatusExtension from the fragment S3Detail_ObjectHeader.fragment.xml to replace the second status attribute of the object header. An empty fragment is created, in which you can insert the new second status.

Check component.js file of your enhancement project regarding the registration of your custom controller:

Define the hook method extHookSetHeaderFooterOptions in your custom controller (S1Custom.controller.js), which is used to overwrite existing information and action triggers and as well to add new ones. To change something, object oOptions has to be adjusted. Within the standard app these options are provided:

- Jam-Integration (-> oJamOptions)

- For adding new buttons in the footer area, you can add new buttons to the button list of parameter oOptions. Alternatively, you can remove properties of parameter oOptions, if you do not support the actions of the standard delivery.

Check component.js file of your enhancement project regarding the registration of your custom controllers

Define the hook method extHookSetHeaderFooter in your custom controllers, which is used to overwrite existing information and action triggers and as well to add new ones. To change something, object oOptions has to be adjusted. Within the standard app these options are provided:

- SAP Jam integration (oJamOptions)

- Title for the detail screen (sI18NDetailTitle)

- Button for triggering action (oEditBtn)

- Other buttons, contained under the “Open In..” button (buttonList)

Create a new file PECBaseDetailController.js in the view folder of your extension project and define an extension for the hook method extHookSetHeaderFooter of the PECBaseDetailController.js file from the standard delivery

Create an empty controller extension of the master list S2ProcessSteps.controller.js and require the PECBaseDetailController.js of the extension project, which overwrites the empty hook method of the standard base detail controller with the function defined in the first step

Each process step has 3 digits, starting with a capital letter. For customer enhancements in particular, a “Z” or “Y” should be used as the capital letter. This new code value can be used as part of the input parameter for the underlying query (input parameter P_Processstep of the standard delivery).

Copy the existing reuse views RetailPromnPreparationIssues and RetailPromnPreparationItemIssues in a custom package.

Adjust the reuse views located in your package with a customer-specific logic, to determine the due, overdue, and error situations of your process step. To do this, you can create new calculated columns in view node PromoHeaderItemJoin. Use the existing calculated columns such as PurPriceActvtOverdueDate, PurPriceActvtDueDate, PurPriceActivationIsNotCmplt, PurPriceActivationHasError, PurPriceActivationIsDue, PurPriceActivationIsOverdue of the process step purchase price activation as an example. Propagate your new fields to the semantic level. In the view node FilterOutIssues you have to consider your new key figures in the existing filter expression

Repeat the second step for the item view RetailPromnPreparationItemIssues located in your package.

Copy the existing query view RetailPromnPrepIssuesTileQuery in a custom package.

Adjust the query view located in your package, and propagate the new fields to node InputParamConsideration. In this node the indicators are recalculated by considering the input parameters P_ProcessStep, P_Urgency, and P_ErrorCategory. Use the existing calculated columns such as PurPriceActivationHasError_1, PurPriceActivationIsDue_1 or PurPriceActivationIsOverdue_1 of the process step "purchase price activation" as an example

Propagate your new fields to the next node. In the view node FilterOutIssues you have to consider your new key figures in the existing filter expression

Propagate your new fields to the node NumberCalc. Consider the new key figures in the formulas of PromotionContainsError, NmbrOfDueIssInPromn, NmbrOfOverdueIssInPromn, NmbrOfOverdueErrorsInPromn, and NmbrOfDueErrorsInPromn

Copy the existing query view RetailPromnProccessStepsQuery in a custom package.

Adjust the query view located in your package and propagate the new fields to node InputParamConsideration. In this node the indicators are recalculated by considering the input parameters P_ProcessStep, P_Urgency, and P_ErrorCategory. Use the existing calculated columns such as PurPriceActivationHasError_1, PurPriceActivationIsDue_1, or PurPriceActivationIsOverdue_1 of the process step Purchase Price Activation as an example

Propagate your new fields to the next node. In the view node FilterOutIssues you have to consider your new key figures in the existing filter expression

Create a new projection pair for your process step, just like the pair ProcessStepPpa and FilterOutNoIssuesPpa for the process step Purchase Price Activation. Introduce a new abbreviation (maximum 3 digits) for your process step

Include your new process step in the union UnionProcessSteps

Copy the existing OData service kpi.xsodata into a custom package. Replace the package path sap.hba.apps.rtl.s.v with your own package path and also replace the query name

Copy the existing OData service pec.xsodata into a custom package. Replace the package path sap.hba.apps.rtl.s.v with your own package path and also replace the query names for RetailPromnPrepIssuesQuery and RetailPromnProcessStepsQuery with the names of your query copies. Finally, add the new master/detail query view to the OData service

The standard service list defined in the Configuration.js file needs to be changed in your extension project if you plan to replace the existing model promoprocsteps on the master detail view with a new model, or you plan to add a new model for the new process step related detail view (see section “Using Another OData Service”). For the latter, you cannot use the S3DataProvider class and you must implement your own code to work with a third model.

You have to enhance retail.promn.promotioncockpit.utils.ProcessStepsConstants using the methods addProcessStepToList and addProcessStepToMap.

- Object PROCESS_STEPS_MAP

- Array PROCESS_STEP_LIST (3-digit abbreviation)

Some texts, such as field labels or table column headers have to be inserted into the respective enhancement i18n-property-files

Enhance the properties XS_ENTITIES and queries in retail.promn.promotioncockpit.model.S3DataProvider

Create a new detail screen for the new process step, in accordance with other process step-related detail screens. Use the naming convention S3<yourName>.view.xml

Register the new detail screen within the routing definition in the retail.promn.promotioncockpit.Component.js file