Tell us what you think

We want to create the best possible experience for our learners. Your feedback helps us to improve the experience for everyone.

Enabling Components

Objective

After completing this lesson, you will be able to explain the procedure to enable SAP Service and Asset Manager extension components

SAP Service and Asset Manager Extension Control Enablement Matrix

Note

This is only available for Applications before 2205.

Crew Management, Asset Central, Field Operation Worker, Customer Service, Meter Management.

SAP Service and Asset Manager standard release comes with base application, and extension components, in separate metadata files. To enable an extension component, you must merge extension component metadata with base application metadata using Component Integration Metadata (CIM) file, with MDK design time tool. SAP back-end system configuration changes, including MAIF configuration changes, might also needed for some components.

The following matrix provides guidelines on how to enable extension components. Note CIM files for all standard extension components are delivered with SAP Service and Asset Manager branding SDK zip file.

Guideline on How to Enable Extension components

Extension Component	Client Tasks	SAP Backend Tasks
Asset Central	Tool: MDK design time tool Task: Merge metadata file ASSETMGR ASSETCENTRL META nnnn into target workspace ‘/AssetCentral’ Task: Import CIM file from branding SDK → SAPAssetManagerAssetCentral → SAM.mdkproject → metadata → sam.definitions → SAPAssetCentral.cim into target workspace ‘/SAPAssetManager’	Tool: tcode SM59 Task: Define RFC destination to ASPM Cloud Tenant. Tool: MAIF ConfigPanel Task: Assign RFC destination to SAP Service and Asset Manager mobile application system component SAM_ASPM_PUBLIC_CLOUD.
Crew Management	Tool: MDK design time tool Task: Merge metadata file ASSET MGR CREW METADATA nnnn into target workspace ‘/Crew.’ Task: Import CIM file from branding SDK → SAPAssetManagerCrew → SAM.mdkproject → metadata → sam.definitions → SAPCrewManager.cim into target workspace ‘/SAPAssetManager’	None
Customer Service	Tool: MDK design time tool Task: Merge metadata file ASSETMGR CUSTOMERSVC META nnnn into target workspace ‘/CustomerService.’ Task: Import CIM file from branding SDK → SAPAssetManagerCustomerService → SAM.mdkproject → metadata → sam.definitions → SAPCustomerService.cim into target workspace ‘/SAPAssetManager’	Tool: MAIF ConfigPanel Task: Update rules for oMDO SAMnnnn_ORDER_TYPE filter ORDER_TYPE. Enable/add filter rule to include customer service order types.
Field Operation Worker	Tool: MDK design time tool Task: Merge metadata file FIELD OPS WORKER METADATA nnnn into target workspace ‘/FOW-Component’ Task: Import CIM file from branding SDK → SAPFieldOperationsWorker → SAM.mdkproject → metadata → sam.definitions → FieldOperationsWorker.cim into target workspace ‘/SAPAssetManager’	None
Meter Management	Tool: MDK design time tool Task: Merge metadata file ASSET MGR METER METADATA nnnn into target workspace ‘/Meter.’ Task: Import CIM file from branding SDK → SAPAssetManagerMeter → SAM.mdkproject → metadata → sam.definitions → SAPMeterManager.cim into target workspace ‘/SAPAssetManager’	None

To Enable Multiple Components with Overlapping Objects

To integrate multiple add-on components to the base SAP Service and Asset Manager application, a new integrator component is created and used. The integrator component includes only files common to two or more components. These common files are the only files that require merging. When you shift these merged common files to the integrator component, you leave the original components as-is or untouched. Using this method, it is easier to upgrade any add-on component when a new version is released.

For example, consider creating the SAP Service and Asset Manager application with the Crew Management and Field Operations Worker components. Both these components have an Overview.page as a common file, and other common files. Therefore, you create a new MyAggregatecomponent. You then add an Overview.page to the MyAggregatecomponent , where the Overview.page is a merged page from Crew Management and Field Operations Worker.

Note

The following procedure details how to merge the Field Operations Worker, Crew Management, and Meter Management components, along with custom changes. Use the procedure as an example. Your components and custom changes may vary.

Steps

Create a ZSAMComponent with an Overview.page.
Create the ZSAMComponent.cim file. Place this *.cim file in the base SAP Service and Asset Manager application, as shown in the following screenshot.
Note
Multiple *.cim files are executed in alphabetical order. In this case, the ZSAMComponent is the last one executed and overrides all other changes made by the other .cim files

Result

An example of the Overview page metadata of the ZSAMComponent after the merger of the Overview pages of the Field Operations Worker, Crew Management, and Meter Management components:

Sample overview page as described in the preceding text.

REFERENCE ONLY: Enable the Crew Management Component

Enable the Crew Management Component

ExerciseStart Exercise

Next lesson