Show TOC

Procedure documentationAdding Rules to a Distribution Model Locate this document in the navigation structure

 

To filter the data object data that is to be sent to mobile devices, you need to add a rule either to the distribution model or to a distribution dependency. This allows you to define the criteria used for filtering the data.

Prerequisites

  • You have created a data object.

  • You have created a distribution model.

  • You have created a distribution dependency. (This prerequisite is optional depending at which level you want the rule to apply.)

Procedure

  1. Log on to the SAP NetWeaver Application Server and start the transaction SDOE_WB.

  2. From the Data Orchestration Engine Workbench, select the project in which you want to work.

    Note Note

    To display all projects, type * in the instance list field and press Enter.

    End of the note.

  3. Navigate to the distribution model or the distribution dependency for which you want to create a rule, click it with the secondary mouse button and choose   Add   Rule  .

    The Distribution Rule Wizard starts.

  4. Choose Continue.

  5. Under Rule Details, enter a name and description (optional) for the rule.

    The data object for which you create the rule is displayed in the Data Object Name field.

    Note Note

    The rule name must not contain any blanks.

    End of the note.

  6. Choose Continue.

  7. Under Rule Fields, specify the node attributes to be mapped and the operator to be used for the mapping (more information: Operators Used in Defining Rules).

    Note Note

    You can choose attributes from different nodes, selecting attributes from one node first and then choosing another node to select more attributes.

    End of the note.

  8. Choose Continue.

  9. Under Logic Selection, choose the mapping logic. Depending on the selected logic continue as follows:

    SubGen Mapping

    Device Attribute Mapping

    None

    1. Choose a receiver category type (RMM).

      Note Note

      Currently only MOBILE is supported.

      End of the note.

    The software component version is entered automatically.

    1. Choose the SubGen Data Object.

    The name of the data object's root node is entered automatically.

    1. Choose the Device Attribute Mapping pushbutton.

    2. In the Distribution Rule screen, choose the device attribute (as defined in the RMM customizing group), an operator and the SubGen data object attribute(s) to which you want to map it, and choose Save.

      Note Note

      Use the scroll buttons at the bottom of the screen to scroll through the values.

      Unless you have selected the BT operator, you always use the Attribute Low column to select the corresponding SubGen data object attribute.

      End of the note.

    3. Choose Save.

    1. Choose a receiver category type (RMM).

      Note Note

      Currently only MOBILE is supported.

      End of the note.

    The software component version is entered automatically.

    1. Choose Continue.

    Choose Continue.

    Note Note

    You can combine SubGen mapping and direct device attribute mapping in one rule. For an example, refer to Sample Project: Distribution Logic.

    End of the note.

    1. Choose Continue.

    2. Under Logic Details, you select the mapping type. Depending on the logic you have selected above, you have different options available:

    SubGen Mapping

    Option

    Action

    SubGen Data Object

    Map the attribute(s) in the SubGen data object to the node attribute(s) of the standard data object to be used as criteria for the distribution of the standard data object.

    Device Attribute

    Map the node attribute(s) of the standard data object to be used as distribution criteria directly to the corresponding device attribute(s).

    Constant Values

    Define a constant value for the node attribute(s) of the standard data object to be used as criteria for the distribution of the standard data object.

    Date Pattern

    Define a date pattern for the node attribute(s) of the standard data object to be used as distribution criteria. This option is only allowed for attributes of the data type DATS/TIMS/ACCP. The DOE distributes the data object only if the attribute value (a date or time) lies within the date pattern you define here.

    Note Note

    If you selected SubGen Mapping as the mapping logic, you must map at least one attribute of the SubGen data object here, choosing SubGen Data Object above.

    End of the note.

    Device Attribute Mapping

    Option

    Action

    Device Attribute

    Map the data object attribute(s) you selected under Rule Details directly to device (RMM) attribute(s). The DOE distributes the data object only if the attribute values match.

    Constant Values

    Define a constant value for the data object attribute(s) you selected under Rule Details. The attributes must have the specified values for the data object to be distributed.

    Date Pattern

    Define a date pattern for the data object attribute(s) you selected under Rule Details. This option is only allowed for attributes of the data type DATS/TIMS/ACCP. The DOE distributes the data object only if the data object attribute value (a date or time) lies within the date pattern you define here.

    None

    Option

    Action

    Constant Values

    Define a constant value for the data object attribute(s) you selected under Rule Details. The attributes must have the specified values for the data object to be distributed.

    Date Pattern

    Define a date pattern for the data object attribute(s) you selected under Rule Details. This option is only allowed for attributes of the data type DATS/TIMS/ACCP. The DOE distributes the data object only if the data object attribute value (a date or time) lies within the date pattern you define here.

    1. Choose Continue.

    2. If you selected the Constant Values or Date Pattern mapping type, select a device binding option and proceed as described in step 7 of Adding a Bulk Rule to a Distribution Model.

    3. If appropriate, schedule an additional rule evaluation job. To do this, choose Add Custom Job.

      The Distribution Rule screen is displayed.

      1. Enter an event name of your choice. For Start in the Schedule section, enter a date and time for rule evaluation to start. For No Start after, enter a date and time after which the job is no longer to be executed.

      2. In the Periodic Job section, choose an option for the recurring execution of rule evaluation, for example, weekly or monthly.

      3. You can also choose Other Options and define that you want rule evaluation to be executed, for example, every three weeks from the start date you have defined under Schedule.

      4. Choose Save.

    4. Choose Continue.

    5. Verify your entries, choose Continue, then choose Complete.

    6. Activate the rule.