Show TOC

Background documentationTypes of MDP Views Locate this document in the navigation structure

 

MDP views can be classified into the following types:

  • Tabular view

  • Assignment view

  • Browse and collect view

  • Multi view

Tabular View

You use this view to create, modify, or delete InfoObject entries. Additionally, you can maintain KPI (Key Performance Indicator) entries in InfoCubes.

Example Example

The 0RMP_V1_STYLE_M maintenance view, delivered by default with your application, is an example of a tabular view created with the MAP-MDP application. This view displays a list of articles (styles) for the hierarchy node and material category specified in the selection criteria. A view also allows you to add new styles and change attributes of the listed styles.

The 0RAP_ASRT_PLAN maintenance view, delivered by default with your application, is another example of a tabular view created with the MAP-MDP application. This view allows you to maintain assortment versions. From this view, you can launch another view (0RAP_ASRT_DTAIL) which allows detailed maintenance of a selected assortment version.

End of the example.
Assignment View

You use this view to maintain assignments between two InfoObjects. For example, you can use a view to assign colors to an article. The definition of this view requires an assignment InfoObject, reference InfoObject, grouping InfoObject, and a main InfoObject. Every assignment choice becomes a new column where a checkbox can be toggled to create or delete assignments

An assignment view requires that you define the following on the Results Table Settings Customizing Screen:

  • Main InfoObject: used to define the rows (for example, it can identify the article 0MATERIAL).

  • Reference InfoObject: used to define the columns (for example, it can identify the color 0RT_COLCR).

  • Group InfoObject: used to define the range of valid values that can be used from the reference InfoObject (for example, it identifies the color range characteristic 0RT_COLRNGE)

  • Assign InfoObject: used to define the assignment between articles and sizes. An entry is created in this InfoObject for each assignment made.

Example Example

The 0RMP_V3_STYCO_A maintenance view, delivered by default with your application, is an example of an assignment view created with the MAP-MDP application. This view displays a list of styles for the hierarchy node and material category specified in the selection criteria. You use the maintenance view to assign colors to each displayed style by simply enabling the appropriate checkboxes. For this view:

  • Main InfoObject: used to specify a style (for example, 0MATERIAL)

  • Reference InfoObject: used to specify the color you want to assign to a style (for example, 0RT_COLCR)

  • Group InfoObject: used to contain the assignment of a style to a predefined range of colors (for example, 0RT_COLRNGE)

  • Assignment InfoObject: used to contain the association of a style with a specified color (for example, 0RT_STYCOCR)

End of the example.
Browse and Collect View

You use this view to assign objects from a repository to create assignments like in the Assignment view.

Note Note

The main difference between an assignment view and the browse and collect view resides in the layout: a browse and collect view uses two tables separated by the Assignment Target dropdown field. This dropdown can also be hidden from table settings in Customizing. There are also two pushbuttons to create and assign in the collect table.

End of the note.

  • The browse table displays all possible entries that can be assigned. It is based on the main InfoObject of table setting 1 in Customizing.

  • The Assignment Target dropdown list changes the target of the assignment. Only the assignments in the collect table that match the current settings are displayed. The Show All field displays all assignments for all assignment targets. It displays entries defined in the reference InfoObject of the settings for the second table. It also uses the group InfoObject to build the list of all possible values available in the dropdown list.

  • The collect table displays all the entries that are assigned to the current assignment target. It is based on the main InfoObject and the assign InfoObject of the Customizing settings for the second table.and should be kept identical.

  • The Assign pushbutton combines the selected entries in the Browse table with the current assignment target dropdown to create new entries in the Collect table. The Business Add-In (BAdI) BADI_UPARM_BRWS_CLT_ASSIGN from Enhancement Definition ES_UPARM must be implemented to generate new entries in the collect table from selected entries in the browse table and actual value of the assignment target dropdown.

  • The Unassign pushbutton deletes the selected entries in the collect table.

Example Example

The 0RAP_RANGE_PLAN maintenance view, delivered by default with your application, is an example of a browse and collect view created with the MAP-MDP application. This view allows the user to assign products to an assortment version. In this example 0CM_SKU is used as a repository and 0RT_AVRPRDS is used to save the assignment.

Result Table Settings: First Table

Main InfoObject: a product (for example, 0CM_SKU)

For the Result Table Settings: Second Table view:

  • Main InfoObject: Product Assignments to Assortment Versions for MAP to SOP (0RT_AVRPRDS)

  • Reference InfoObject: Assortment Version (0RT_ASRTVRS)

  • Group InfoObject: Assortment Version (0RT_ASRTVRS)

  • Assign InfoObject: Product Assignments to Assortment Versions for MAP-SOP (0RT_AVRPRDS)

To make this assignment work, the Business Add-In (BAdI) BADI_UPARM_BRWS_CLT_ASSIGN must be created for the view. The BAdI BADI_UPARM_READ_MASTER_DATA can also be implemented to control how the results are fetched from the database.

End of the example.
Multi View

You use this view to group multiple single views (tabular, assignment, or browse and collect) together. These views share the same selection criteria. A tab strip is created for each view that is included in the multi view.

  • Embedded View ID: Name of a single MDP view (tabular, assignment, or browse and collect) that defines one tab in the multi view.

  • Sequence Number: Determines the display sequence of the embedded views within the horizontal tab of the multi view.

  • Save Before Exit: When checked, this flag displays a dialog box to the user asking them to save any modification before exiting the current embedded view. After the save action is completed, all embedded views reload their results from the database to display the modifications. If you do not save the modifications, the results are not reloaded.

  • Save Before Enter: Similar to Save Before Exit, except the user sees this option when in an embedded view.

Example Example

The 0RAP_ASRT_DTAIL maintenance view, delivered by default with your application, is an example of a multi view created with the MAP-MDP application. This view regroups multiple single views together.

End of the example.