Old Exercises Performing Advanced Extension

Objective

After completing this lesson, you will be able to old Exercises

To Extend SAP Service and Asset Manager Functionality with a New Entity

In the backend, to create a new entity that is set to be downloaded to the mobile app, perform the following steps.

Steps

  1. Develop oData mobile data object.

    1. Create Entity Reference structure.

    2. Create oMDO Class Handler with the following methods:

      MethodPurpose
      define_bo_entity_model()Define Business Object Entity Model
      get_oper_field_catalog_tables()Make Tables and mandatory Field available for selection
      get_data_filter_list()Make Fields available to configure Filters
      get_data_for_read_request()Business Logic to fetch data from SAP (Basic Object) – low volume and frequency-based fetch

      get_objkeys_by_distrib_rules()

      load_entity_details()

      Business Logic to fetch data from SAP (Standard Object) – high volume with exchange for delta fetches

      filter_objkeys_by_xchange_info()

      get_objkeys_for_delta_load()

      Filters & Object key when using Exchange
  2. Configure oData service and optional for new Z-Component.

    1. Register oData model.

      • Register Technical Model via /IWBEP/REG_MODEL.
      • Generic Model Provider Class /MFND/CL_CORE_ODATA_V2_MPC
    2. Register oData service.

      • Register Technical Model via /IWBEP/REG_SERVICE.
      • Generic Model Provider Class /MFND/CL_CORE_ODATA_V2_DPC
    3. Assign Model to oData service.

      TCode /IWBEP/REG_SERVICE - Maintain Service.

    4. Activate and expose service to gateway.

      TCode /IWFND/MAINT_SERVICE - Maintain Service (Add Service and assign System Alias)

    5. Assign oData service to mobile app.

      Via Config Panel (/SYCLO/CONFIGPANEL) assign oData service to mobile app.

  3. Configure oMDO object.

    1. Assign oMDO class.

    2. Configure filter and field selection.

    3. Configure Exchange object and Dependent Objects.

  4. Configure oData model.

    1. Create Entity and Entityset.

    2. Assign Entity to oMDO object.

    3. Configure associations.

    4. Configure navigational properties.

  5. Test service via /IWFND/GW_CLIENT.

  6. (Optional) When exchange is required, develop change detection (or exchange processing).

    1. Create exchange table and lock objects.

    2. Create EFI Include or Implement BADI/Enhancement.

    3. Create Exchange Class handler.

  7. (Optional) When exchange is required, configure change detection (or exchange processing).

    1. Create exchange object (configure filters and field selection).

    2. Assign exchange object to EFI Include/Event.

    3. Assign exchange object to oMDO.

REFERENCE ONLY: Extend SAP Service and Asset Manager Functionality (with a New Entity): Part 1 Back-end

Extend SAP Service and Asset Manager Functionality (with a New Entity): Part 1 Backend: Part 1

REFERENCE ONLY: Extend SAP Service and Asset Manager Functionality (with a New Entity): Part 2 MDK

Extend SAP Service and Asset Manager Functionality (with a New Entity): Part 2 MDK: Part 1

Processing of External Service

Companies procure external services when they cannot be fulfilled internally. The following forms of processing are available for external processing:

  • Processing with an external company as work center.
  • Processing with an individual purchase order.
  • Processing with service specifications.

Processing with an individual purchase order

You can use this form of processing to assign tasks to an external company based on individual purchase orders. These purchase orders can either be settled relative to resources or based on a fixed price for the total expected output. They can consist of items for material or for services.

You mark the operations for orders to be processed externally as operations to be processed externally using a corresponding control key (PM02).

Example scenarios

  • Example 1: You have agreed a direct labor hour rate of $ 80 and assume the work will take four hours to complete. In fact, five hours are required; a total cost of $ 400.

  • Example 2: You have agreed a fixed price of $ 10 per meter of cable laid and assume that 40 meters of cable will be used. In fact, only 35 meters are required; a total cost of $ 350.

  • Example 3: You have agreed a flat-rate price of $ 400 for the laying of 40 meters of cable, and assume the work will take four hours. In fact, 50 meters of cable were required and the work took five hours; a total cost of $ 400.

Note

In the subsequent exercises, you will extend the SAP Asset Manager to support processing of External Services using Purchase Orders.

REFERENCE ONLY: Create Work Order for External Processing Using Purchase Order

Create Work Order for External Processing using Purchase Order

Log in to track your progress & complete quizzes