Modeling a Mobile Entity Collection

Use

You model a Mobile Entity Collection (MEC) to create a collection of entities or data objects that are part of one or more software component versions (SWCVs) present in the DOE. You can also define projections, authorizations, and distribution model software component versions (DMSWCVs) for the participating data objects.

Procedure

1. Create a MEC

  1. Log on to the SAP NetWeaver Application Server.

  2. Choose transaction SDOE_MEC_DESIGN to launch the MEC Modeler .

  3. Enter the name of the MEC in the MEC Name field.

  4. Choose Create .

  5. On the MEC Overview tab, enter the description for the MEC.

  6. Choose Save .

The system assigns a version number and a status to the MEC.

2. Assign Data Objects

  1. Choose the Components tab.

  2. Enter the name of an SWCV that exists in the DOE, in the SWCV Caption text box.

  3. Choose Show Data Object .

    The system displays the list of data objects corresponding to the SWCV.

  4. To assign data objects, select the data object(s) and use the arrow keys to move the data object to the Assigned Data Objects list.

  5. Choose Save .

  6. To perform a consistency check, choose Start of the navigation pathMobile Entity  Next navigation step CheckEnd of the navigation path.

    If no valid or active back-end adapter has been assigned to the data object, the system displays a warning message. You can resolve this warning by creating a valid and active back-end adapter for the data object.

  7. Repeat steps two to six to include data objects from more than one SWCV.

    The system assigns the selected data objects to the MEC.

3. Assign a Distribution Model Software Component Version

  1. Choose the DMSWCVs tab.

  2. Select the Assign checkbox corresponding to the DMSWCV.

  3. Choose Start of the navigation pathMobile Entity  Next navigation step CheckEnd of the navigation path to perform a syntax check.

  4. Choose Save .

At the time of device registration, the assigned DMSWCV is assigned to the device.

More Information: Overriding an Assigned DMSWCV

4. Define a Design Time Projection

A projection is a subset of nodes or fields of selected data objects. There are certain fields that are mandatory while defining a projection, for example, Synckey , Psynckey , Task , Backend Keys , and StateID . You can define only one design time projection (DTP) for a MEC.

  1. Choose the Projections tab.

    The Defined MEC Projection pane displays all the data objects assigned to the MEC.

  2. If you want to remove a field from the Defined MEC Projection list, select the corresponding field(s) of the data object(s) and choose Remove Selected Fields .

  3. If you want to add a field from the Data Object Fields list, select the correpsonding field(s) of the data object(s) and choose Add Selected Fields ,

  4. Choose Save .

5. Optional: Define Runtime Projections

Runtime projections are a subset of the design time projection and you can define multiple runtime projections for each design time projection. By default, the system creates an active Runtime Projection (RTP) Default_Runtime_proj by reusing the fields from the DTP. You cannot change the fields of Default_Runtime_Proj. You work through the following steps only if you want to have different fields in the RTP.

  1. Choose Client Specific Configurations .

  2. In the Runtime Projections tab, choose Create .

  3. Enter the name of the RTP in the Projection Name field.

  4. If you want to add fields to the RTP from the Design Time Projection Fields pane, select the corresponding field(s) and choose Add Selected Fields .

  5. Choose Save .

  6. Repeat steps two to seven to create another RTP.

The RTP is applicable only in the current client.

6. Optional: Define a Runtime Header

A Runtime Header (RTH) contains the most relevant fields from a projection which are critical for the device users in terms of data. Whenever content is pushed to devices, the system downloads the field part of headers optimizing the bandwidth usage

  1. Choose Client Specific Configuration .

  2. Choose the Runtime Projections tab.

  3. Choose Create .

  4. Choose the Runtime Headers tab.

  5. Enter the name of the RTH in the Header Name field, and choose OK .

  6. If you want to add fields to the RTH from the Runtime Projection Fields pane, select the corresponding field(s) and choose Add Header Fields .

  7. Choose Save .

  8. Repeat steps five through nine to create another RTH.

The RTH is applicable only in the current client.

7. Optional: Client Specific Configuration of DMSWCV

If you want to choose a different DMSWCV from what is defined in the design time for a particular client, follow the steps given below:

  1. Choose Client Specific Configuration .

  2. Choose the DMSWCVs tab.

  3. Select the active checkbox for the corresponding DMSWCV.

  4. Choose Save .

8. Add Authorizations

  1. Choose the Authorizations tab.

  2. In the Authorization Object Name field, enter the name of the authorization that exists in the back-end system for the participating data objects.

  3. Enter a description in the Description field.

  4. Choose Add Object .

9. Optional: Add Custom Services

  1. Choose the Custom Services tab.

  2. Select the corresponding SWCV with the assigned data object.

  3. Choose Add Function Modules .

  4. In the Search function modules dialog box, enter the function module name.

  5. Choose Save .

  6. Choose Display Guids.

  7. Keep a note of the ESMBO ID / MEC Trans available in the list.

  8. Specify the back-end search BAPI for the MEC.

    More information: Specifying the RFC Destination for a Back-End Search BAPI