Kontakt

Ansicht
Dokumentation

CRMV_FS_CUSTOMIZING - Define Views

CRMV_FS_CUSTOMIZING - Define Views

Fill RESBD Structure from EBP Component Structure   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

You can use this IMG activity to define

  • Views to be used in the fact sheet or summary, and
  • The More button as a special form of the elements of a view.

A view is defined by a data source and the representation of its data in the user interface. The data displayed in a view is dependent on the selected business object. You can create views as forms or lists. For display in the portal, the view is linked with an iView. Multiple iViews associated with a business object are combined in portal pages and are displayed as a fact sheet or summary.

The More button is used to go by object link navigation to a portal page with further information. Clicking on this button in an iView in the fact sheet or in the summary of a business object takes you to the details for this business object.

You have fulfilled the following preconditions:

  • You have decided on a data source. You can use either an existing data source or create a new one. A data source is an ABAP class that provides data displayed in the view. For more information, see the documentation for the Business Package for SAP CRM 5.0.

The following standard settings are valid:

  • In the standard system of the Business Package for SAP CRM 5.0, views are already defined in the portal roles. The More button is already defined in some views.
  • You can only create new views in your namespace (Z*, Y*). You can only change views that are in your namespace.
  • You can only maintain elements for the More button in your namespace (Z*, Y*).
  • For the element of the More button, you can only define the characteristics Object Type, Method, Tab Name, and Element Characteristic, whereby the Element Characteristic characteristic is only supported by the Invisible value. All other characteristics of this element are fixed and cannot be changed.
  • All table entries are client-specific.

Define a View of the 'List' Type

Use the following concrete example to define a list containing five columns and the 'More' button.

I. Define Element Group

  1. Double-click on Element Groups.
  2. Choose New Entries.
  3. Enter X_CRM_BTX_OPP_PRODUCT_ROOTin the Element Group field .
  4. Enter Opportunity: Product List in the Description field.

II. Define Layout

Element Without Hyperlink

  1. Double-click on Layout after you have chosen the element group created earlier.
  2. Choose New Entries.
  3. Enter ORDERED_PRODin the Element Name field .
This name corresponds to the field label in the return structure of the function module that provides the data.
  1. Skip the Is Group flag because this function is not supported yet.
  2. Enter Product IDin the Description field .
The description is used to identify the layout line better.
  1. Skip the Reference Group field because this function is not supported yet.
  2. Enter the value 10 in the Element Item field .
You use this characteristic to specify the sequence of the fields in the view.
  1. Choose the value Right-alignedin the Element Characteristics field .
In this case, the column header and the data in this column are right-aligned and are displayed as such.
  1. Skip the Label Char. field because the function is not supported by the list.
  2. In the DDIC or. Dynam. Rel. field, choose the Middle Labelvalue.
  3. Skip the Layout Type field because this function is not supported yet.
  4. Skip the New Lineand Unique i. Line flags because these functions are not supported by the list yet.
  5. Leave the Width of Elementfield empty.
You use this property to specify the percentage of the total width of the table occupied by the column.
  1. Skip the Height of Element field.
  2. Skip the Suppress Link flag.
  3. Set the To Be Sorted flag.
The List is sorted by the value in the Description field, here it is Product ID.
  1. Leave the Object Type, Method, Tab Name, Field Name → CRM ID, Field Name → CRM ObjType, Field Name → Method, Field with Tab and Text Key fields. Skip the O Type is BOR Type flag.

Element with Hyperlink

Field Value
Element Group X_CRM_BTX_OPP_PRODUCT_ROOT
Element Name DESCRIPTION
Description Description
Element Position 020
Field Name → CRM ObjType OPPORTUNITYCRM
Field Name → Method APPLICATION
Field with Tab OPP_HD_PRODUCTS

Element Without Hyperlink and 'More' Button

Field Value
Element Group X_CRM_BTX_OPP_PRODUCT_ROOT
Element Name PROD_HIER_DESCR
Description Category
Element Position 030

Field Value
Element Group X_CRM_BTX_OPP_PRODUCT_ROOT
Element Name QUANTITY
Description Quantity
Element Position 040

Field Value
Element Group X_CRM_BTX_OPP_PRODUCT_ROOT
Element Name EXP_REVENUE
Description Expected revenue
Element Position 050

Field Value
Element Group X_CRM_BTX_OPP_PRODUCT_ROOT
Element Name FS_MORE_BUTTON_FIELD
Description 'More' button
Element Position 100
Field Name → CRM ObjType OPPORTUNITYCRM
Field Name → Method DEFAULT
Field with Tab OPP_HD_PRODUCTS

III. Define view

  1. Double-click on Views.
  2. Choose New Entries.
  3. Enter X_CRM_BTX_LIST_PRODUCT_OPP_SAMPLEin the Name of Viewfield.
  4. Enter Opportunity: Product List in the Description field.
  5. Enter IF_CRM_FS_LIST_VIEW in the Name of Interface field because you want to create a view of the 'List' type .
  6. Enter CL_CRM_BSP_SUM_1O_LIST_PRODUCT in the Class Name field.
This SAP standard class provides data for the opportunity.
  1. Enter CRMT_BSP_SUM_1O_PROD_LIST_T in the Struct. or Type field.
This structure belongs to the CL_CRM_BSP_SUM_1O_LIST_PRODUCT class, in which display data is returned.
  1. Choose the value List in the View Layout field.
  2. Leave the Number of Columns field empty because the number of columns is defined through the elements of the element group.
  3. Enter the value 4in the Number of Lines field.
You can use this property to define the number of lines displayed below each other in the display.
  1. Enter X_CRM_BTX_OPP_PRODUCT_ROOT in the Element Group field.
This value creates the link with the element group that contains the definition of the single fields displayed in the view.

Defining a View of the 'Form' Type

On the basis of a concrete example, in the following you define a form containing five output fields and a blank line.

I. Defining the Element Group

  1. Double-click on Element Groups.
  2. Choose New Entries.
  3. Enter X_CRM_MD_BP_INFO_ROOT_EXAMPLE in the Element Group field.
  4. Enter Account Info in the Description field.

II. Defining the Layout

Output Field Without Field Label with Hyperlink

  1. After you have chosen the element group, double-click on Layout.
  2. Choose New Entries.
  3. Enter LINE0 in the Element Name field.
This name corresponds to the field label in the return structure of the function module that provides the data.
  1. Skip the Actual Group flag because this function is not supported yet.
  2. Enter Address Line 1in the Description field.
This description helps to identify the layout line better.
  1. Skip the Reference Groupfield because this function is not supported yet.
  2. Enter the value 10 in the Element Position field.
You use this property to specify the sequence of fields in the view.
  1. Select the value Left-Alignedin the Element Prop. field.
The data is displayed aligned to the left in the field.
  1. Choose the value Invisible in the ID Prop. field.
  2. Leave the DDIC or Dynam. ID field empty.
The entry in the Description field is displayed as a field label instead.
  1. Skip the Layout Type field because this function is not supported yet.
  2. Skip the New Line flag.
  3. Set the Unique in Line flag.
This forces the multiple-column format of this output field to be displayed in one line.
  1. Enter the value 1 in the Width of Element field.
  2. Skip the Height of Element field.
  3. Skip the Suppress Link and To Be Sorted flags.
  4. Enter ACCOUNTCRM in the Object Type field.
This value, together with the value in the Method field, is required to generate the hyperlink to the BSP application, in this case, Account.
  1. Enter APPLICATION in the Method field.
  2. Skip the Tab Name field.
  3. Enter NAVI_OBJECT_KEY in the Field Name → CRM ID field.
This field corresponds to the field in the return data record of the function module that contains the key for the chosen data record.
  1. Skip the Field Name → CRM ObjType, Field Name → Method, Field with Tab and Text Key fields. Skip the OType Is BOR Type flag.

Output Fields Without Field Label Without Hyperlink

Field Value
Element Name LINE2
Description Address line 2
Element Position 20
Element Prop. Left-aligned
ID Prop. Invisible
Unique in Line Selected
Width of Element 1

Field Value
Element Name LINE3
Description Address line 3
Element Position 30
Element Prop. Left-aligned
ID Prop. Invisible
Unique in Line Selected
Width of Element 1

Output Field Without Field Label with Suppressed Output

This field is suppressed if the function module in the backend does not provide a value to be displayed

Field Value
Element Name LINE4
Description Address line 4
Element Position 40
Element Prop. Empty cell
ID Prop. Invisible
DDIC or Dynam. ID Middle Label
Unique in Line NOT selected
Width of Element 1

Output Field with Field Label

Field Value
Element Name PHONE
Description Telephone
Element Position 60
Element Prop. Left-aligned
ID Prop. Left-aligned
DDIC or Dynam. ID Middle Label
Unique in Line NOT selected
Width of Element 1

Inserted Empty Line

You should add an empty line between the address header and telephone field. Because the function module does not provide the EMPTY_LINE1 value and the field label is invisible, an empty line is displayed.

Field Value
Element Name EMPTY_LINE1
Description Empty line
Element Position 50
Element Prop. Left-aligned
ID Prop. Invisible
DDIC or Dynam. ID Middle Label
Unique in Line Selected

III. Defining the View

  1. Double-click on Views.
  2. Choose New Entries.
  3. Enter X_CRM_MD_BP_INFO_EXAMPLEin the Name of View field.
  4. Enter Account-Infoin the Descriptionfield.
  5. Enter IF_CRM_FS_FORMULAR_VIEWin the Name Interface field because you want to create a 'Form'-type view.
  6. Enter CL_BSP_ACC_SUM_BP_INFOin the Classe Name field.
This SAP-standard class provides data for the Account.
  1. Enter CRMT_BSP_ACC_SUM_INFOin the Struct. or Type field.
This structure belongs to the CL_BSP_ACC_SUM_BP_INFO class, in which display data is returned.
  1. Choose the Form value in the View Layoutfield.
  2. Enter the value 1in the Number of Columnsfield.
This value specifies the number of field labels/value pairs displayed next to each other in the single columns of the view.
  1. Leave the Number of Linesfield empty because this function is not supported in the form.
  2. Enter X_CRM_MD_BP_INFO_ROOT_EXAMPLEin the Element Groupfield.
This value creates the link to the element group that contains the definition of the single fields displayed in the view.

Defining the 'More' button

  1. Choose the element group that belongs to the view you want to display in the More button .
  2. In the layout of this element group, create an element of this type or process an existing element.

Setting Up the Display of the 'More' Button in a View

You have the following options for setting up the More button in a view:

  1. Define the element of the More button in the element group of the view.
The More button is an element with the fixed element name FS_MORE_BUTTON_FIELD.
The jump target parameters are created in the element in the Method and Object Typefields as well as in Name if necessary. All other properties of this element, besides the Element Property,are fixed and cannot be changed, for example, button field labels, positioning and alignment of the button in the iView. In particular, the referenced properties Field with ID, Field with Object Type, Field with Method, and Field with Tab have no influence on the button. If you want to define the object link dynamically, the definition must be made in the data source.
  1. If you have specified at least one of the three parameters, the values in the data source are not taken into account. The following default values apply:
The object type is optional. If you do not specify an object type, the object type of the business object is used.
The method is optional. If you do not specify a method, the DEFAULT default value is used.
The tab nameis optional. If you do not specify a tab page, no tab page is selected i the object link navigation.
  1. If you have defined the element of the More button and have not specified any of the three parameters, the values are transferred from the data source.
  • Define the More button in the data source.
    • You must specify at least the object type and the ID of the business object.
    The method is optional. If you do not specify a method, the DEFAULT default value is used.
    The tab nameis optional. If you do not specify a tab page, no tab page is selected i the object link navigation.
    1. If you have defined the element for the More button and have specified at least one of the three parameters, the values in the data source are not taken into account.
    2. If you have defined the element for the More button and have not specified any of the three parameters, the values are transferred from the data source.
    Notes:
    • The two options for defining the object link navigation of the More button cannot be combined with each other.
    • If the data for determining the jump target is sufficient, the More button is displayed in the lower right in the iView.
    • If the data for determining the jump target is incomplete, the More button is displayed as inactive.
    • If you have not defined an element for the More button and if the data for determining the jump target for the More button in the data source is incomplete, the button is not displayed.
    • If the jump target of the object link navigation is a BSP application in the People-Centric UI, use the APPLICATION navigation method in both cases (see above) and when creating the jump target.
    • Specifying the tab page only makes sense if this function is supported in the target application, for example, in BSP applications in the People-Centric UI.

    Set suppressed display of 'More' button in a view

    1. Do not define the element for the button on the element group of the view or the button in the data source.
    2. Define the element for the More button and enter the invisible value in the Element Property field. This also lets you make the More button, which you have defined in the data source, invisible.
    Unique in Line

    Example of the 'More' Button

    Example of Displaying the 'More' Button in a View

    The example refers to the More button defined as an element in an element group (as described in the first case in the first section under "Activities").

    Field Value
    Element Group V_CRM_BTX_LEA_PRODUCT_ROOT
    Element Name FS_MORE_BUTTON_FIELD
    Object Type LEADCRM
    Method DEFAULT
    Tab Name BTX_PRODUCTS
    Element Char.

    Example of Suppressing the Display of the 'More' Button in a View

    The example refers to the More button defined in the data source. If you additionally define the More button as an element, you can suppress the display of the button (as described in the second case in the second section under "Activities").






    ABAP Short Reference   Fill RESBD Structure from EBP Component Structure  
    This documentation is copyright by SAP AG.

    Length: 34330 Date: 20240523 Time: 161730     sap01-206 ( 263 ms )
    Field Value
    Element Group V_CRM_BTX_LEA_PRODUCT_ROOT
    Element Name FS_MORE_BUTTON_FIELD
    Object Type
    Method
    Tab Name
    Element Char. Invisible